Broadcom Wireless - Debian

This is a discussion on Broadcom Wireless - Debian ; Hello. I'm trying to get a LinkSys Wireless G WPC54GS card to work, using the bcm43xx driver in the newer 2.6 kernels. I've got a certain distance, but I'm not there yet. This card has the Broadcom 4318 chipset which ...

+ Reply to Thread
Results 1 to 3 of 3

Thread: Broadcom Wireless

  1. Broadcom Wireless

    Hello.

    I'm trying to get a LinkSys Wireless G WPC54GS card to work, using the bcm43xx
    driver in the newer 2.6 kernels. I've got a certain distance, but I'm not there
    yet. This card has the Broadcom 4318 chipset which is supported by the version of
    the driver in the most recent kernel.

    The kernel is a hand-compiled version of 2.6.17. I have version 28-1 of
    wireless-tools from Debian unstable, and udev 0.093 also from Debian unstable.

    The card seeme to be correctly identified by the kernel on insertion:

    Jul 7 09:26:19 lapdog kernel: pccard: CardBus card inserted into slot 0
    Jul 7 09:26:19 lapdog kernel: PCI: Enabling device 0000:03:00.0 (0000 -> 0002)
    Jul 7 09:26:19 lapdog kernel: ACPI: PCI Interrupt 0000:03:00.0[A] -> Link [LNKA] -> GSI 11 (level, low) -> IRQ 11
    Jul 7 09:26:19 lapdog kernel: PCI: Setting latency timer of device 0000:03:00.0 to 64
    Jul 7 09:26:19 lapdog kernel: bcm43xx: Chip ID 0x4318, rev 0x2
    Jul 7 09:26:19 lapdog kernel: bcm43xx: Number of cores: 4
    Jul 7 09:26:19 lapdog kernel: bcm43xx: Core 0: ID 0x800, rev 0xd, vendor 0x4243, enabled
    Jul 7 09:26:19 lapdog kernel: bcm43xx: Core 1: ID 0x812, rev 0x9, vendor 0x4243, disabled
    Jul 7 09:26:19 lapdog kernel: bcm43xx: Core 2: ID 0x804, rev 0xc, vendor 0x4243, enabled
    Jul 7 09:26:19 lapdog kernel: bcm43xx: Core 3: ID 0x80d, rev 0x7, vendor 0x4243, enabled
    Jul 7 09:26:19 lapdog kernel: bcm43xx: PHY connected
    Jul 7 09:26:19 lapdog kernel: bcm43xx: Detected PHY: Version: 3, Type 2, Revision 7
    Jul 7 09:26:19 lapdog kernel: bcm43xx: Detected Radio: ID: 8205017f (Manuf: 17f Ver: 2050 Rev: 8)
    Jul 7 09:26:19 lapdog kernel: bcm43xx: Radio turned off
    Jul 7 09:26:19 lapdog kernel: bcm43xx: Radio turned off

    and the appropriate modules loaded by udev:

    ----------------------------------------------------------------------
    bcm43xx 414720 0
    ieee80211softmac 28032 1 bcm43xx
    ieee80211 31304 2 bcm43xx,ieee80211softmac
    ieee80211_crypt 6272 1 ieee80211
    yenta_socket 25484 2
    rsrc_nonstatic 12544 1 yenta_socket
    pcmcia 36268 0
    firmware_class 10112 2 bcm43xx,pcmcia
    ohci1394 32816 0
    ieee1394 93620 1 ohci1394
    pcmcia_core 40080 3 yenta_socket,rsrc_nonstatic,pcmcia
    ----------------------------------------------------------------------


    If I call iwconfig, I get this:

    wlang IEEE 802.11b/g ESSIDff/any Nickname:"Broadcom 4318"
    Mode:Managed Access Point: Invalid Bit Rate=1 Mb/s
    RTS thrff Fragment thrff
    Encryption keyff
    Link Quality:0 Signal level:0 Noise level:0
    Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
    Tx excessive retries:0 Invalid misc:0 Missed beacon:0

    (I have a udev rule to assign the name wlang to the interface.)

    The frustrating thing is that I can now *sometimes* get the thing to work, but only
    sometimes. If I bring up the interface by hand (ifconfig wlang up) and then do:

    iwlist wlang scan

    it will usually (but not always) detect the two access points that are within range:

    wlang Scan completed :
    Cell 01 - Address: NN:NN:NN:NN:NN:NN
    ESSID:"XXXXXXX"
    Protocol:IEEE 802.11bg
    Mode:Master
    Channel:6
    Encryption keyff
    Bit Rates:54 Mb/s
    Extra: Rates (Mb/s): 1 2 5.5 6 9 11 12 18 24 36 48 54
    Quality=100/100 Signal level=-197 dBm
    Extra: Last beacon: 302ms ago
    Cell 02 - Address: MM:MM:MM:MM:MM:MM
    ESSID:"YYYYYY"
    Protocol:IEEE 802.11b
    Mode:Master
    Channel:6
    Encryption keyff
    Bit Rates:11 Mb/s
    Extra: Rates (Mb/s): 1 2 5.5 11
    Quality=100/100 Signal level=-199 dBm
    Extra: Last beacon: 1086ms ago

    If I then do:

    iwconfig wlang essid XXXXXXX
    dhclient wlang

    about one time in 10 all goes well. But for the other times, no IP address is
    offered. This is what the crucial part of the logs show:

    Jul 7 09:35:31 lapdog kernel: SoftMAC: Sent Authentication Request to NN:NN:NN:NN:NN:NN.
    Jul 7 09:35:36 lapdog kernel: SoftMAC: Open Authentication with NN:NN:NN:NN:NN:NN failed, error code: 1
    Jul 7 09:35:36 lapdog kernel: SoftMAC: Authentication response received from NN:NN:NN:NN:NN:NN but no queue item exists.
    Jul 7 09:35:43 lapdog kernel: printk: 4 messages suppressed.
    Jul 7 09:35:52 lapdog kernel: printk: 26 messages suppressed.
    Jul 7 09:35:52 lapdog kernel: SoftMAC: Authentication response received from NN:NN:NN:NN:NN:NN but no queue item exists.
    Jul 7 09:35:59 lapdog kernel: printk: 6 messages suppressed.
    Jul 7 09:35:59 lapdog kernel: SoftMAC: Authentication response received from NN:NN:NN:NN:NN:NN but no queue item exists.
    Jul 7 09:35:59 lapdog kernel: SoftMAC: Authentication response received from NN:NN:NN:NN:NN:NN but no queue item exists.
    Jul 7 09:36:00 lapdog kernel: SoftMAC: Queueing Authentication Request to NN:NN:NN:NN:NN:NN
    Jul 7 09:36:00 lapdog kernel: SoftMAC: cannot associate without being authenticated, requested authentication
    Jul 7 09:36:00 lapdog kernel: SoftMAC: Sent Authentication Request to NN:NN:NN:NN:NN:NN.
    Jul 7 09:36:07 lapdog kernel: printk: 3 messages suppressed.
    Jul 7 09:36:07 lapdog kernel: SoftMAC: Open Authentication with NN:NN:NN:NN:NN:NN failed, error code: 1
    Jul 7 09:36:28 lapdog kernel: printk: 9 messages suppressed.
    Jul 7 09:36:28 lapdog kernel: SoftMAC: Authentication response received from NN:NN:NN:NN:NN:NN but no queue item exists.
    Jul 7 09:36:28 lapdog last message repeated 4 times
    Jul 7 09:36:37 lapdog kernel: printk: 9 messages suppressed.
    Jul 7 09:36:37 lapdog kernel: SoftMAC: Authentication response received from NN:NN:NN:NN:NN:NN but no queue item exists.
    Jul 7 09:36:44 lapdog kernel: printk: 6 messages suppressed.

    The one time over the past day or so that it worked:

    Jul 6 13:53:42 lapdog kernel: SoftMAC: Queueing Authentication Request to NN:NN:NN:NN:NN:NN
    Jul 6 13:53:42 lapdog kernel: SoftMAC: cannot associate without being authenticated, requested authentication
    Jul 6 13:53:42 lapdog kernel: SoftMAC: Sent Authentication Request to NN:NN:NN:NN:NN:NN.
    Jul 6 13:53:42 lapdog kernel: SoftMAC: Open Authentication completed with NN:NN:NN:NN:NN:NN
    Jul 6 13:53:42 lapdog kernel: SoftMAC: sent association request!
    Jul 6 13:53:42 lapdog kernel: SoftMAC: associated!
    Jul 6 13:54:01 lapdog dhclient: Internet Systems Consortium DHCP Client V3.0.1
    Jul 6 13:54:01 lapdog dhclient: Copyright 2004 Internet Systems Consortium.
    Jul 6 13:54:01 lapdog dhclient: All rights reserved.
    Jul 6 13:54:01 lapdog dhclient: For info, please visit http://www.isc.org/products/DHCP
    Jul 6 13:54:01 lapdog dhclient:
    Jul 6 13:54:02 lapdog dhclient: Listening on LPF/wlang/00:16:b6:4a:42:a8
    Jul 6 13:54:02 lapdog dhclient: Sending on LPF/wlang/00:16:b6:4a:42:a8
    Jul 6 13:54:02 lapdog dhclient: Sending on Socket/fallback
    Jul 6 13:54:04 lapdog dhclient: DHCPDISCOVER on wlang to 255.255.255.255 port 67 interval 6
    Jul 6 13:54:05 lapdog dhclient: DHCPOFFER from 192.168.1.1
    Jul 6 13:54:05 lapdog dhclient: DHCPREQUEST on wlang to 255.255.255.255 port 67
    Jul 6 13:54:05 lapdog dhclient: DHCPACK from 192.168.1.1
    Jul 6 13:54:05 lapdog dhclient: bound to 192.168.1.105 -- renewal in 41002 seconds.

    So it seems pretty clear that the problem is with the authentication procedure
    (both APs work fine with other wireless cards).

    Any ideas anyone?

    Thanks very much,

    Jim




    --
    To UNSUBSCRIBE, email to debian-laptop-REQUEST@lists.debian.org
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

  2. Re: LinkSys Wireless G WPC54GS (was Broadcom Wireless)

    I wrote:

    |> I'm trying to get a LinkSys Wireless G WPC54GS card to work,
    |> using the bcm43xx driver in the newer 2.6 kernels.

    Well, after a lot of work, and after getting help on the bcm43xx mailing
    list, I find that the true situation seems to be that this card is `sort
    of' supported in 2.6.17. By which I mean that with the bcm43xx driver it
    can associate with an access point in 1 or 2 attempts out of 10---that
    is, not reliably enough to be usable in real life. The problem seems to
    be with TX Power issues, and as far as I can tell, 2.6.18 will not fare
    any better with respect to those issues.

    These cards are marketed as the Linksys Wireless-G WPC54GS rev 2 (with
    Speed Booster). So caveat emptor. I really thought that I had done the
    searching needed to be sure that the card was supported.

    Jim


    --
    To UNSUBSCRIBE, email to debian-laptop-REQUEST@lists.debian.org
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

  3. Re: LinkSys Wireless G WPC54GS (was Broadcom Wireless)


    Hi Jim,

    The problems you describe could basically also be caused by a
    overloaded router (too many new requests, too many hits from outside,
    [especially masssive filesharing], together with intense firewall processing +-logging.
    Routers also use to have acess timeout to prevent DOS attacks.)
    Anyway, you would see that with other cards too, then, of course.
    But before throwing this one into ebay, you may have a last look into the
    driver sourcecode...sometimes there are model specific hints.

    greets,

    Marlin



    --
    To UNSUBSCRIBE, email to debian-laptop-REQUEST@lists.debian.org
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

+ Reply to Thread