PCLinuxOS won't recognize Linksys WUSB54GSC usb wireless network adapter

[barryc]

I have spent the better part of last weekend trying to get this network adapter installed.
I have a fully up to date installation of PCLinuxOS (kde4). Runs perfectly on integrated nvidia ethernet card wired
to a Verizon Fios router.  I have been experimenting with the above ups wifi card as I want
to install it on another desktop I just finished building for my grandson.  Neither computer
will recognize the card.  I tried setting up ndiswrapper with the Windows XP drivers that
came on the CD but the drake network setup device can't find the hardware and bounces
me out with a message that it can't find a valid ndiswrapper device or words to that effect.

The chipset, according to Linksys for the adapter is BCM4320 (Broadcom)
It is a BCM43xx 802.11 bg WLAN family chipset.

As far as I can tell after reading many posts and contacting Linksys, it should work using NDISwrapper.

Do any of you have this adapter working with PCLos and, if so, how did you set it up.

I can post all the various troubleshooting commands if you need more info.

If this is a lost cause, are there any sure fire wifi adapters, either usb or pci that I can use that
will work with the kernel driver?  (I am using kernel version 2.6.33.7-pclos6.bfs)

[muungwana]

Try to first update to the latest kernel, the latest one in the family of kernel you have is "2.6.33.7-pclos6.bfs"

There was an update that fixed a few bcm issues as mentioned in this thread: http://www.pclinuxos.com/forum/index.php/topic,79712.0.html

[barryc]

Thanks.  Whoops, made a typo.  That is the latest kernel.  I left out the 6 after pclos.  I Read Tex's post and the H open article.
Still scratching my head.  My install is currently fully updated.

[barryc]

Has anybody here run into this problem?  I can't tell if it's the adapter or the operating system.
From what I could find, the driver for this adapter is native to the new kernel.  Unfortunately, until
PCLos recognizes the adapter, it can't apply the driver.  Unless I'm missing something.
 

[Dragynn]

Whole buncha Broadcom packages in the repo, they might already be installed and not helping you, but thought i'd mention 'em.

b43-firmware 1.1-1pclos2010
b43legacy-firmware
bcm43xx-firmware
bcm43xx-fwcutter (tool for extracting firmware)
b43-fwcutter

[barryc]

Whole buncha Broadcom packages in the repo, they might already be installed and not helping you, but thought i'd mention 'em.

b43-firmware 1.1-1pclos2010
b43legacy-firmware
bcm43xx-firmware
bcm43xx-fwcutter (tool for extracting firmware)
b43-fwcutter

All of these are already installed except the "bcm43xx-fwcutter (tool for extracting firmware)

[muungwana]

i wonder what your system says about the card, unplug it, wait for five seconds and then plug it back in and then open the terminal and type this command and report its output

dmesg | tail -n 15

what does this other command give you

lsusb

[barryc]

i wonder what your system says about the card, unplug it, wait for five seconds and then plug it back in and then open the terminal and type this command and report its output

dmesg | tail -n 15

what does this other command give you

lsusb

[barry@BigBee ~]$ dmesg | tail -n 15
RPC: Registered tcp NFSv4.1 backchannel transport module.
Slow work thread pool: Starting up
Slow work thread pool: Ready
FS-Cache: Loaded
FS-Cache: Netfs 'nfs' registered for caching
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
NFSD: unable to find recovery directory /var/lib/nfs/v4recovery
NFSD: starting 90-second grace period
lp0: using parport0 (interrupt-driven).
lp0: console ready
ata1.00: configured for UDMA/133
ata1: EH complete
ata4.00: configured for UDMA/100
ata4: EH complete
[barry@BigBee ~]$

Here ya go.  Not very helpful is it.

[muungwana]

Did you type the command right after you inserted the usb network card? there should atleast be an entry from the kernel saying a usb device was plugged in

i asked for output of two commands, you only gave one

[barryc]

Did you type the command right after you inserted the usb network card? there should atleast be an entry from the kernel saying a usb device was plugged in

i asked for output of two commands, you only gave one

Oh, sorry, I missed the lsusb.  I redid the whole thing.
Here are the latest results:

[barry@BigBee ~]$ dmesg | tail -n 15
usb 1-2.1: SerialNumber: 8057
usbcore: registered new interface driver cdc_ether
usbcore: registered new interface driver rndis_host
cfg80211: Calling CRDA to update world regulatory domain
cfg80211: World regulatory domain updated:
    (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
    (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
    (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
    (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
    (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
    (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
wlan0: register 'rndis_wlan' at usb-0000:00:02.2-2.1, Wireless RNDIS device, BCM4320b based, 00:18:f8:30:25:0e
usbcore: registered new interface driver rndis_wlan
wlan0: couldn't set packet filter: 0000000d
wlan0: couldn't set packet filter: 0000000d


[barry@BigBee ~]$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 001 Device 004: ID 058f:6362 Alcor Micro Corp. Hi-Speed 21-in-1 Flash Card Reader/Writer (Internal/External)
Bus 001 Device 005: ID 046d:0821 Logitech, Inc.
Bus 001 Device 006: ID 04b8:0812 Seiko Epson Corp. MFP Composite Device
Bus 001 Device 007: ID 13b1:0026 Linksys
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 046d:c313 Logitech, Inc.
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
[barry@BigBee ~]$

This is the correct info.  I had two consoles open and I copied the wrong info.  The above is the latest
and correct info.  I see the Linksys showing up in lsusb and the correct chipset reference in the dmesg info.
Is that a tiny candle light I see at the end of the tunnel?

[muungwana]

Did you unplug the device and plug it back in before typing the first command?

Again, there should atleast be an entry form the kernel that a usb device is attached, we arent seeing any from your output for some reason. This could mean  the device is defective, do you have a windows box, does it work there?

If it is plugged in, log in as root from the terminal and then do the following

1. Run the command "service syslog restart" to make sure system log service is running
2. Unplug the device, wait for five seconds, plug in back in, wait for five seconds
3. Run this command and give its output here

cat /var/log/syslog | tail -n 50
while on the terminal log

[barryc]

Sorry for the confusion.  See my revised post right above your reply.
I copied wrong data originally.  Latest info is accurate.  I had removed the
adapter and replugged it in and repeated the procedure for both demsg and lsusb.
Looks like it found the usb device and it shows up as Linksys in lsusb.

[muungwana]

as you can see in your revised output, the kernel can see the card, loaded up hopefully a correct driver and it gave it "wlan0" address, this is good.

Now, follow the instruction in my above post. The earlier one was to see if the kernel was seeing the card or not, above instructions will show us if the interface asked for an IP address using DHCP

The above will most likely give an output with errors but its nice to know what it will produce. I google the last two error msgs and it looked like there is a bug on the driver you are using.

just google "couldn't set packet filter: 0000000d" and you will see discussions on the bug you are hitting.

Possible solutions could be raising the problem to pclinuxos developers wait for them to patch the driver or wait for an updated kernel with a driver that worked correctly.

[barryc]

Ok.  Here's the latest syslog info:

[root@BigBee ~]# service syslog restart
Shutting down kernel logger:                                                                          [  OK  ]
Shutting down system logger:                                                                          [  OK  ]
Starting system logger:                                                                               [  OK  ]
Starting kernel logger:                                                                               [  OK  ]
[root@BigBee ~]# cat /var/log/syslog | tail -n 50
Dec 22 23:59:17 BigBee printerdrake[2814]: running: update-alternatives --display lprm
Dec 22 23:59:17 BigBee printerdrake[2814]: symlinked file /usr/bin/lprm-cups to /etc/alternatives/lprm
Dec 22 23:59:17 BigBee printerdrake[2814]: running: update-alternatives --display lp
Dec 22 23:59:17 BigBee printerdrake[2814]: symlinked file /usr/bin/lp-cups to /etc/alternatives/lp
Dec 22 23:59:17 BigBee printerdrake[2814]: running: update-alternatives --display cancel
Dec 22 23:59:17 BigBee printerdrake[2814]: symlinked file /usr/bin/cancel-cups to /etc/alternatives/cancel
Dec 22 23:59:17 BigBee printerdrake[2814]: running: update-alternatives --display lpstat
Dec 22 23:59:17 BigBee printerdrake[2814]: symlinked file /usr/bin/lpstat-cups to /etc/alternatives/lpstat
Dec 22 23:59:17 BigBee printerdrake[2814]: running: update-alternatives --display accept
Dec 22 23:59:17 BigBee printerdrake[2814]: symlinked file /usr/sbin/accept-cups to /etc/alternatives/accept
Dec 22 23:59:17 BigBee printerdrake[2814]: running: update-alternatives --display disable
Dec 22 23:59:17 BigBee printerdrake[2814]: symlinked file /usr/sbin/disable-cups to /etc/alternatives/disable
Dec 22 23:59:17 BigBee printerdrake[2814]: running: update-alternatives --display enable
Dec 22 23:59:17 BigBee printerdrake[2814]: symlinked file /usr/sbin/enable-cups to /etc/alternatives/enable
Dec 22 23:59:17 BigBee printerdrake[2814]: running: update-alternatives --display lpc
Dec 22 23:59:18 BigBee printerdrake[2814]: symlinked file /usr/sbin/lpc-cups to /etc/alternatives/lpc
Dec 22 23:59:18 BigBee printerdrake[2814]: running: update-alternatives --display lpmove
Dec 22 23:59:19 BigBee printerdrake[2814]: symlinked file /usr/sbin/lpmove-cups to /etc/alternatives/lpmove
Dec 22 23:59:19 BigBee printerdrake[2814]: running: update-alternatives --display reject
Dec 22 23:59:19 BigBee printerdrake[2814]: symlinked file /usr/sbin/reject-cups to /etc/alternatives/reject
Dec 22 23:59:19 BigBee printerdrake[2814]: running: /sbin/chkconfig --list
Dec 22 23:59:21 BigBee klogd: lp0: using parport0 (interrupt-driven).
Dec 22 23:59:21 BigBee klogd: lp0: console ready
Dec 22 23:59:22 BigBee hp[3647]: io/hpmud/pp.c 627: unable to read device-id ret=-1
Dec 22 23:59:24 BigBee python: io/hpmud/pp.c 627: unable to read device-id ret=-1
Dec 22 23:59:25 BigBee printerdrake[2814]: created directory /dev/usb (and parents if necessary)
Dec 22 23:59:25 BigBee last message repeated 14 times
Dec 22 23:59:25 BigBee printerdrake[2814]: running: foomatic-printjob -s cups -C start EPSONSPhR320
Dec 22 23:59:25 BigBee printerdrake[2814]: ### Program is exiting ###
Dec 22 23:59:25 BigBee printerdrake[2814]: ### Program is exiting ###
Dec 22 23:59:25 BigBee autosetupprintqueues[1268]: ### Program is exiting ###
Dec 22 23:59:26 BigBee klogd: ata1.00: configured for UDMA/133
Dec 22 23:59:26 BigBee klogd: ata1: EH complete
Dec 22 23:59:27 BigBee klogd: ata4.00: configured for UDMA/100
Dec 22 23:59:27 BigBee klogd: ata4: EH complete
Dec 22 23:59:48 BigBee net_applet[3824]: ### Program is starting ###
Dec 23 00:01:01 BigBee CROND[4131]: (root) CMD (nice -n 19 run-parts --report /etc/cron.hourly)
Dec 23 00:01:02 BigBee anacron[4141]: Anacron started on 2010-12-23
Dec 23 00:01:02 BigBee anacron[4141]: Jobs will be executed sequentially
Dec 23 00:01:02 BigBee anacron[4141]: Normal exit (0 jobs run)
Dec 23 00:02:14 BigBee ntpd[3096]: synchronized to LOCAL(0), stratum 10
Dec 23 00:02:14 BigBee ntpd[3096]: kernel time sync status change 0001
Dec 23 00:02:35 BigBee klogd: Kernel logging (proc) stopped.
Dec 23 00:02:35 BigBee klogd: Kernel log daemon terminating.
Dec 23 00:02:36 BigBee exiting on signal 15
Dec 23 00:02:36 BigBee syslogd 1.5.0: restart.
Dec 23 00:02:36 BigBee klogd: klogd 1.5.0, log source = /proc/kmsg started.
Dec 23 00:02:43 BigBee klogd: usb 1-6: USB disconnect, address 5
Dec 23 00:02:43 BigBee klogd: wlan0: unregister 'rndis_wlan' usb-0000:00:02.2-6, Wireless RNDIS device, BCM4320b based
Dec 23 00:03:14 BigBee ntpd[3096]: synchronized to 65.182.224.39, stratum 2
[root@BigBee ~]#


I have rebooted and tried to set up the wireless (wlan0) and it shows up in the menus until the very end after entering the SSID and Wep key:
then NetDrake hangs and can't seem to allow it log on.  Something is wacky but the driver is present and seems to be recognized.
I did experiment with different usb ports on my computer.  Don't know if that would make a difference but is about the only thing left (other
than a buggy driver) that could be causing the commotion.

[muungwana]

The second from last entry of the log says what driver the kernel is using to handle the card and what card address is given to this card. We already knew this info from earlier "dmesg" command and hence this output is not very informative.

The card is recognized and a driver is loaded to handle it, the problem is with the buggy driver and this can be tricky as drivers usually ship with a kernel and using a different version of a driver usually means using a different version of the kernel.

There these 3 kernels in the repository,2.6.31.12-pclos1,2.6.32.24-pclos1.xxx and 2.6.33.7-pclos6.xxx.

You are using the last one, try to install the first two and see if they will work with your card.

Make sure first "dkms" service is set to start at boot time in services section of pcc and boot from the first two kernels after installing them and then run the dmsg command again and see if you will get the same error msg.