wg511 pccard not loaded (regression: dapper -> edgy)

Ok, I've attached some more info. At this stage I'm thinking it is kernel-related: firmware is not being loaded (from: /lib/firmware/2.6.17-10-generic/isl3890) and the device not being enabled, despite the same module version.

I also found some confirmation of 2.6.17+ issues here: http://www.prism54.org/punbb/viewtopic.php?pid=6624

Patch at http://bugzilla.kernel.org/attachment.cgi?id=8798&action=view ought to fix this.

Ok, I've got the card working!

Following Matthew's suggestion (via Sarah Hobbs - thanks!)... pci=bios doesn't work but pci=conf1 does. The patch will be good for this working out of the box though.

---

<mjg59> Hobbsee: It's not appearing in lspci, so the driver will never bind
<mjg59> Hobbsee: dmesg shows that the card plugging is being detected, but shows no sign of the device itself appearing
<mjg59> Hobbsee: pci=bios may well work around it
<mjg59> Or pci=conf1

linux-source-2.6.17 (2.6.17-10.33) edgy; urgency=low

  * Fix build failure

  [2.6.17-10.32]

  * ia64: Fix merge error for CVE-2006-3741. Caused a FTBFS.
  * Re-add ipw2200 quiesce patch.
  * Revert "usb/unusual: Add Domain Tech as GO_SLOW".
  * general: Quieten some more messages.
  * prism2: Commented out devices from MODULE_DEV_TABLE that are supported by
    hostap.
    - Malone #62685
  * pcbios: Cherry pick fix for PCBIOS PCI probing:
    Upstream GIT-SHA: 954c0b7cd5b9aaa11fb67a0c011fcb5e5897385a
    - Malone #60231
  * sdhci: Cherry pick fix for some devices, avoid reset in certain cases.
    Upstream GIT-SHA: 8a4da1430f7f2a16df3be9c7b5d55ba4e75b708c
    - Malone #63553
  * ahci: Add Intel 2680 device.
    - Malone #64433
  * hdaps: Re-implement lost dapper patch for y-only axis swapping. Add X41 as
    y-only.
    - Malone #58742
  * Enable all V4L1 modules.
    - Malone #58742

 -- Ben Collins <email address hidden> Wed, 11 Oct 2006 17:05:07 -0400

Could someone explain in an easier language how to get this working? :-)
Or point me to a Forum thread explaining this.
Thanks.

First, check to see if your issue is actually caused by this bug. To do this, see if your card shows up when you run: lspci

eg, I get: 02:00.0 Network controller: Intersil Corporation ISL3890 [Prism GT/Prism Duette]/ISL3886 [Prism Javelin/Prism Xbow] (rev 01)

If it shows up, you just need to configure it properly - search ubuntuforums.org for the model name of your card.

If it does not show up, it might be due to this bug. This issue is fixed for me in edgy since the fix was commited (2.6.17-10.33), but to work around a dodgy BIOS you can try adding 'pci=bios' or 'pci=conf1' to your kernel cmdline by either adding it in grub on boot (search forums for this - basically press 'Esc' and 'e' to edit the options) or editing /boot/grub/menu.lst, looking for the kopt= line and adding the option:
[...]
## ## Start Default Options ##
## default kernel options
## default kernel options for automagic boot options
## If you want special options for specific kernels use kopt_x_y_z
## where x.y.z is kernel version. Minor versions can be omitted.
## e.g. kopt=root=/dev/hda1 ro
## kopt_2_6_8=root=/dev/hdc1 ro
## kopt_2_6_8_2_686=root=/dev/hdc2 ro
# kopt=root=UUID=... ro pci=conf1
[...]
Then run: sudo update-grub
...and it should work on reboot.

If it does not, something else is going on - search for another bug here or open your own bug, providing as much info as you can (see above for the kind of info).

I have the NetGear WG511T, It was working perfectly in Dapper I bought it plugged it in, and it worked out of the box.
But not in Edgy.

Tried the pci=conf1 and the pci=bios, but no luck.

An lspci shows the card detected:
03:00,0 Ethernet controller: Atheros Communications, Inc. AR5212 802.11abg NIC (rev 01)

dmesg shows card inserted:
[17180077.564000] pccard: CardBus card inserted into slot 0

I searched the forum for "WG511T edgy" (no quotes) but it did not come up with anything.

Is this the same bug or do I need to open a separate bug?

Ok, never mind, I searched for the chip set, and found that I needed to install restricted modules, now it is working.