Belikin FSD6020 v2 non-functional in Ubuntu 4.10

Bug #12005 reported by Sesquipedality
6
Affects Status Importance Assigned to Milestone
pcmcia-cs (Ubuntu)
Fix Released
High
Andreas Mueller

Bug Description

The Belkin FSD6020 network card fails to work when inseted in a (cardbus) laptop
running 4.10. There seem to be a number of reasons why this is happening. The
v2 cards contain an atmel chipset (I have been able to definitively confirm this
is the case although the atmel kernel driver appears to load successfully), and
the Belkin card is not one listed in /etc/pcmcia/archive. Thus I added the
following to that file:

card "Belkin FSD6020 v2'
  pci 0x1bf, 0x3302
  bind "atmel_cs"

This appears, in conjunction with the atmel-firmware package from universe, to
work to a point, in that the card is recognised and the driver installs
correctly. (It would be useful if there were some indication that this package
is necessary.) However, configuring /etc/network/interfaces thus (actually done
using the GNOME networking setup tool):

iface eth1 inet dhcp
name Wireless LAN card
wireless_essid <essid>
wireless_key <key>

does not result in the card connecting to the wireless net. The following error
appears in syslog:

Jan 18 00:46:18 localhost cardmgr[3945]: + Error for wireless request "Set
Encode" (8B2A) :
Jan 18 00:46:18 localhost cardmgr[3945]: + invalid argument "<key>".

The following error is also reported twice, although its relevance is unclear:

Jan 18 00:46:18 localhost cardmgr[3945]: + sit0: unknown hardware address type 776

Revision history for this message
Matt Zimmerman (mdz) wrote :

The atmel-firmware package in universe is obsolete; the relevant firmware is
already included in the linux-restricted-modules, which is installed by default.

The "sit0" error is harmless.

The other errors seem to indicate that the driver does not support WEP.

At any rate, we can certainly add the relevant stanza to the pcmcia-cs package.
 Please do re-test without the atmel-firmware package; it should not be necessary.

Revision history for this message
Sesquipedality (sesquipedality) wrote :

Testing without the atmel-firmware package does indeed remove the spurious error
message. However, it's still failing to obtain a dhcp lease. I'm in the
fortunate position of having a hostap based AP, so I can see from the logs on
the AP that no attempt at wireless authentication is occurring.

Revision history for this message
Sesquipedality (sesquipedality) wrote :

Sorry this last was user error, the ommision of s: at the front of the key
appeared to be what was causing it.

However, since rebooting after removing the atmel-firmware package, cardmgr is
no longer recognising the card. I don't have time to debug now, but I'll have
another look tonight to see if I can work out what's wrong.

Revision history for this message
Matt Zimmerman (mdz) wrote :

(In reply to comment #3)
> Sorry this last was user error, the ommision of s: at the front of the key
> appeared to be what was causing it.
>
> However, since rebooting after removing the atmel-firmware package, cardmgr is
> no longer recognising the card. I don't have time to debug now, but I'll have
> another look tonight to see if I can work out what's wrong.

That would probably be due to bug #9035, which is already fixed in Hoary

Revision history for this message
Sesquipedality (sesquipedality) wrote :

Confirmed - as in bug 9034, the addition of the following to 'config' is also
necessary

device "atmel_cs"
  class "network" module "atmel_cs"

So to fix this bug in Hoary, it should be sufficient to add

card "Belkin FSD6020 v2"
  manfid 0x01bf,0x3302
  bind "atmel_cs"

to /etc/pcmcia/config.

Revision history for this message
Matt Zimmerman (mdz) wrote :

Thanks for testing.

Revision history for this message
Andreas Mueller (amu) wrote :

fixed in pcmcia-cs_3.2.5-8ubuntu5, added Added Belkin FSD6020 v2 etc/config

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.