Salix Forums

Cheers. I installed both with " spkg -u" Installing the new glibc returned some warnings about the following files having already been removed:
ld-2.13.so
libBrokenLocale-2.13.so
libanl-2.13.so
libc-2.13.so
etc.

I will try to run the Nvidia script again and see what happens,

Edit #1:
I'm baaack

The compile went well. The question of course is what happens if I want to use a SlackBuild or compile in the future, but at least I have X again.
The system still doesn't seem to be able to find my wireless card. I suppose I need to do something manually to get it up and running?
Edit #2:

Code: Select all

# slapt-get -u
---snip---
The following packages have been EXCLUDED:
  kernel-firmware kernel-headers kernel-huge kernel-modules kernel-source 
The following packages will be upgraded:
  gcc glibc 
2 upgraded, 0 reinstalled, 0 newly installed, 0 to remove, 5 not upgraded.
---snip---

Code: Select all

# slapt-get --upgrade -s
Reading Package Lists...Done
The following packages have been EXCLUDED:
  kernel-firmware kernel-headers kernel-huge kernel-modules kernel-source 
The following packages will be upgraded:
  gcc glibc 
2 upgraded, 0 reinstalled, 0 newly installed, 0 to remove, 5 not upgraded.
Need to get 10.9MB/22.6MB of archives.
After unpacking 2.1MB disk space will be freed.
gcc-4.6.2-x86_64-1 is to be upgraded to version 4.5.2-x86_64-2
glibc-2.14.1-x86_64-4 is to be upgraded to version 2.13-x86_64-5_slack13.37
Done

I think I need to upgrade to gcc-4.6.2 and glibc-2.14.1. Perhaps a manual install with "spkg -u", as when I compiled the Nvidia driver?

Congratulations!

You need the newer gcc (and maybe other bits like glibc) for situations like Nvidia where you are required to have the new kernel, *and* some step in the build is unusually fussy. It may never happen again. On the other hand, anything from Slackbuilds will be asuming you have all the 13.37 packages - and kernel. Generally developers avoid being more stringent than necessary in their requirements, to make life easier for the rest of us. In the case of the Nvidia driver, the kernel really was necessary because of new support it contains, and maybe gcc was too. My instinct would be to let the package manager return to 13.37 defaults for everything bar the kernel packages themselves. If you have trouble as a result you will be able to tell!

To put it another way, upgrading to current means living onthe edge, all the more so as there *is* no Salix current. Your video card has forced you to upgrade to the current kernel, but you're likely to have a smoother ride if you keep any other changes to a minumum.

Regarding the wireless card, what makes you think it is such a situation, that is, that it has anything to do with the C compiler? I'd say it's just something you need to tweak or download or load. Indeed, I vaguely remember your having some trouble with wireless a while back - if that isn't just my imagination, it may be worth trying to repeat whatever you did to fix it then. That might mean undoing some of the steps first, too.

I suggest opening a new thread!

That is, start by assuming this is an independent problem.

Hehe

It was actually the wireless card driver that forced me to upgrade the kernel. The Nvidia driver compiling was just a by product of the kernel upgrade. Take a look at the subject

As far as I know, the C compiler issue only relates to the kernel upgrade to Slackware current. That is also why I am unsure as to whether I should also upgrade using

Code: Select all

# spkg -u gcc-4.6.2-x86_64-1.txz

and

Code: Select all

# spkg -u glibc-2.14.1-x86_64-4.txz

or whether I should just do a

Code: Select all

# slapt-get --upgrade

Touché and hasta mañana

Here's your driver:

Code: Select all

root[cdrkit-1.1.6]# modprobe -l | grep rtl8192ce
kernel/drivers/net/wireless/rtlwifi/rtl8192ce/rtl8192ce.ko

Test by loading:

Code: Select all

modprobe -a rtl8192ce

... probably need to refresh wicd if that's what you're using.

I'm not sure why that isn't happening automatically on boot (did you reboot?), but if not, then I think you just need to put the above command in one of the startup scripts.

mimosa wrote:Here's your driver:
Code: Select all
root[cdrkit-1.1.6]# modprobe -l | grep rtl8192ce
kernel/drivers/net/wireless/rtlwifi/rtl8192ce/rtl8192ce.ko
Test by loading:
Code: Select all
modprobe -a rtl8192ce
... probably need to refresh wicd if that's what you're using.

I'm not sure why that isn't happening automatically on boot (did you reboot?), but if not, then I think you just need to put the above command in one of the startup scripts.

Cheers. I still get nothing from wicd.

Maybe you just need to set wicd up with the wireless card. I think Edit --> preferences.

It would also be worth establishing whether the driver is being loaded automatically - reboot, lsmod | grep rtlXXX

mimosa wrote:Maybe you just need to set wicd up with the wireless card. I think Edit --> preferences.
It would also be worth establishing whether the driver is being loaded automatically - reboot, lsmod | grep rtlXXX

I hate to admit it, but you were correct about me not having set the wireless card up in wicd

Unfortunately, despite the driver loading after reboot, I am unable to connect using the wireless card, because I keep getting a "bad password" error.

Code: Select all

# lsmod | grep rtl8192ce
rtl8192ce              71535  0 
rtl8192c_common        55719  1 rtl8192ce
rtlwifi                90396  1 rtl8192ce
mac80211              227240  3 rtl8192ce,rtl8192c_common,rtlwifi

There is nothing that has changed in the wicd setup since I ran

Code: Select all

# modprobe -a rtl8192ce

setup my printer and rebooted. Weird.
Edit:
Now my wireless card is working again. Freaky.I didn't change a thing. BTW, I have posted some boot up warnings and errors that I am getting on a new thread here. I am not sure if the two things are related, but...

If you have encryption (a good idea) you will have a password that's set in the router, and you need to tell wicd about it. Also sometimes you may need to tell wicd whether wireless is wlan0, wlan1 or even something else. iwconfig or ifconfig will tell. Sounds like all's well now

but in case of recidivism those are some first steps.

EDIT

Did you check whether the driver is being loaded automatically on reboot?

Code: Select all

lsmod | grep rtl

There's no reason it shouldn't be.

Code: Select all

$ lsmod | grep rtl
rtl8192ce              71535  0 
rtl8192c_common        55719  1 rtl8192ce
rtlwifi                90396  1 rtl8192ce
mac80211              227240  3 rtl8192ce,rtl8192c_common,rtlwifi
cfg80211              168823  2 rtlwifi,mac80211

Code: Select all

# iwconfig
---snip---
wlan0     IEEE 802.11bgn  ESSID:"F4GEJPbR"  
          Mode:Managed  Frequency:2.462 GHz  Access Point: C4:3D:C7:34:39:C4   
          Bit Rate=144.4 Mb/s   Tx-Power=20 dBm   
          Retry  long limit:7   RTS thr=2347 B   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=63/70  Signal level=-47 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:63   Missed beacon:0
---snip---

The info is posted above. I will keep my fingers crossed and hope for the best.

Salix Forums

(Solved) Driver for Asus PCE-N15 wireless card needed.

Re: Driver for Asus PCE-N15 wireless card needed.

Re: Driver for Asus PCE-N15 wireless card needed.

Re: Driver for Asus PCE-N15 wireless card needed.

Re: Driver for Asus PCE-N15 wireless card needed.

Re: Driver for Asus PCE-N15 wireless card needed.

Re: Driver for Asus PCE-N15 wireless card needed.

Re: Driver for Asus PCE-N15 wireless card needed.

Re: Driver for Asus PCE-N15 wireless card needed.

Re: Driver for Asus PCE-N15 wireless card needed.

Re: Driver for Asus PCE-N15 wireless card needed.