netgear WG511v1 PCMCIA card: prism54pci Cannot read eeprom

[Ian Ohr]

kernel hackers be aware: At first glance this appears to be a bug in the driver p54. But I have discovered a workaround which suggests it's not. This is why I did not put this against the linux-source-2.6.20 package.

I have my system in a state now where if I boot the pc with the Netgear wireless card inserted, the output from dmesg shows:

[ 36.698584] 0000:03:00.0 (prism54pci): Cannot read eeprom!
[ 36.698656] prism54pci: probe of 0000:03:00.0 failed with error -22

The system does not show the network device wlan0. If I remove the card and re-insert it, problem solved, the card initialises, wlan0 appears and off I go to grab the latest ep. of lugradio.
I have also booted from cold *without* the card inserted, and then proceeded to insert it, this works and I'm on the internet in seconds.

I really need some help narrowing down the cause of this, obviously the environment the card is initialised in during boot is different to when it is inserted after boot.

[Javier Jardón (jjardon)]

Thanks for taking the time to report this bug. Unfortunately we can't fix it, because your description didn't include enough information.

 - The output from the uname -a > uname-a.log command
 - The output from the lspci -vvn > lspci-vvn.log command
 - The output from the lspci -vv > lscpi-vv.log command
 - The output from the dmesg > dmesg.log command (1.when you start the computer and 2.when unplug and plug the card)
 - The output of cat /proc/version > proc_version.log command

[Ian Ohr (munk3h)]

Posted vvn twice, sorry.

[cghubbell (cgh)]

Just wanted to add a "me too" to this bug. If any additional diagnosics would help I'd be glad to throw them into the mix.

[Javier Jardón (jjardon)]

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

[Ian Ohr (munk3h)]

Has this bug actually been marked as a duplicate of Bug# 90902?

[Ian Ohr (munk3h)]

Wait, I see it now under the bug title

[Ian Ohr (munk3h)]

The firmware suggested in 90902 is for usb hardware. There is only one listing there for pci firmware and according to an md5sum, this is no different to the firmware shipped with feisty. I don' think this is a duplicate of bug 90902. If it is then the fix proposed in 90902 won't work. Unless usb firmware is not specific to usb hardware, bug then why would it be prism54usb?

[mw99 (markwalker99)]

Possibly related to Bug #45295 given that we're talking a PCMCIA network card with a workaround of ejecting and re-inserting (not that that works reliably with my wg511 :-(

[mw99 (markwalker99)]

Ian, do you get any further useful-looking output in syslog? I'm going out on a limb by thinking "kernel BUG at drivers/pci/bus.c:127!" might help track this one down ;-) My syslog:

May 15 22:54:54 thinkpad kernel: [ 121.168000] pccard: card ejected from slot 0
May 15 22:54:59 thinkpad kernel: [ 125.452000] pccard: CardBus card inserted into slot 0
May 15 22:54:59 thinkpad kernel: [ 125.452000] PCI: Enabling device 0000:02:00.0 (0000 -> 0002)
May 15 22:54:59 thinkpad kernel: [ 125.452000] ACPI: PCI Interrupt 0000:02:00.0[A] -> Link [LNKA] -> GSI 11 (level, low) -> IRQ 11
May 15 22:54:59 thinkpad kernel: [ 125.452000] PCI: Setting latency timer of device 0000:02:00.0 to 64
May 15 22:54:59 thinkpad kernel: [ 125.580000] p54: LM86 firmware
May 15 22:55:01 thinkpad kernel: [ 127.768000] 0000:02:00.0 (prism54pci): Cannot read eeprom!
May 15 22:55:01 thinkpad kernel: [ 127.768000] ACPI: PCI interrupt for device 0000:02:00.0 disabled
May 15 22:55:01 thinkpad kernel: [ 127.768000] prism54pci: probe of 0000:02:00.0 failed with error -22
May 15 22:55:01 thinkpad kernel: [ 127.768000] pci 0000:02:00.0: Error adding device, continuing
May 15 22:55:01 thinkpad kernel: [ 127.768000] ------------[ cut here ]------------
May 15 22:55:01 thinkpad kernel: [ 127.768000] kernel BUG at drivers/pci/bus.c:127!
May 15 22:55:01 thinkpad kernel: [ 127.768000] invalid opcode: 0000 [#1]
May 15 22:55:01 thinkpad kernel: [ 127.768000] SMP
May 15 22:55:01 thinkpad kernel: [ 127.768000] Modules linked in: ipv6 nvram uinput savage drm ppdev speedstep_lib cpufreq_userspace cpufreq_powersave cpufreq_ondemand cpufreq_conservative cpufreq_stats freq_table sony_acpi pcc_acpi dev_acpi tc1100_wmi sbs ac container asus_acpi video dock ibm_acpi backlight i2c_ec button battery lp fuse prism54pci prism54common mac80211 cfg80211 irtty_sir sir_dev snd_cs46xx gameport snd_ac97_codec ac97_bus snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_dummy snd_seq_oss nsc_ircc pcmcia irda snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq crc_ccitt snd_timer psmouse i2c_piix4 snd_seq_device pcspkr parport_pc parport serio_raw i2c_core snd soundcore snd_page_alloc intel_agp shpchp pci_hotplug yenta_socket rsrc_nonstatic pcmcia_core agpgart af_packet tsdev evdev ext3 jbd mbcache ide_cd cdrom ide_disk ata_generic libata scsi_mod uhci_hcd usbcore piix generic e100 mii thermal processor fan fbcon tileblit font bitblit softcursor vesafb capability commoncap
May 15 22:55:01 thinkpad kernel: [ 127.768000] CPU: 0
May 15 22:55:01 thinkpad kernel: [ 127.768000] EIP: 0060:[pci_bus_add_devices+271/288] Not tainted VLI
May 15 22:55:01 thinkpad kernel: [ 127.768000] EFLAGS: 00010246 (2.6.20-15-generic #2)
May 15 22:55:01 thinkpad kernel: [ 127.768000] EIP is at pci_bus_add_devices+0x10f/0x120
May 15 22:55:01 thinkpad kernel: [ 127.768000] eax: c9026008 ebx: c9026000 ecx: 00000046 edx: 00000000
May 15 22:55:01 thinkpad kernel: [ 127.768000] esi: d66eba14 edi: d66eba14 ebp: d66eba00 esp: d0fe1f38
May 15 22:55:01 thinkpad kernel: [ 127.768000] ds: 007b es: 007b ss: 0068
May 15 22:55:01 thinkpad kernel: [ 127.768000] Process pccardd (pid: 3224, ti=d0fe0000 task=d1e73050 ta...

[Colin Macdonald (cbm755)]

On Hardy 2.6.24-11 with an SMC2835W I still experience this problem:

000:02:00.0 (prism54pci): cannot read eeprom!
ACPI: PCI interrupt for device 0000:02:00.0 disabled
prism54pci: probe of 0000:02:00.0 failed with error -22

But on Gentoo with vanilla 2.6.24.3 on the same laptop, the card works (well it works as poorly as it ever did: I think there is loose solder in the antenna connection but that has nothing to do with this bug).

firmware md5 from Gentoo:
8bd4310971772a486b9784c77f8a6df9 isl3890

firmware md5 from Ubuntu:
8bd4310971772a486b9784c77f8a6df9 isl3890

[michiel roeleveld (michielroeleveld)]

Hi, I reported a duplicate bug (#120978) and was asked to post my logs here. I hope this will help.

[michiel roeleveld (michielroeleveld)]

I've tested it with a dowloaded Ubuntu 8.04 (Hardy heron) cd.

[michiel roeleveld (michielroeleveld)]

I've tested the pcmcia card in another laptop and there is works. That system was running Ubuntu 7.10. I hope this helps

[michiel roeleveld (michielroeleveld)]

I have solved the problem for my wireless card. I have increased the delay in the appropriate driver see the attached patch.

[blast (blastg)]

Hi all

I had same problem with a Sitecom WL-140 v2 and Ubuntu 8.04 kernel 2.6.24-19-generic.

I solved after many search and test using ndiswrapper + windows drivers, then putting p54pci and p54common in /etc/modprobe.d/blacklist and ndiswrapper to /etc/modules.

It works like a charm now...

Best regards
blast

[Leann Ogasawara (leannogasawara)]

Hi Guys,

Care to confirm this is still an issue with the latest Alpha for the upcoming Intrepid Ibex 8.10. You should be able to test via a LiveCD - http://www.ubuntu.com/testing. Please let us know your results.

Michiel - you mentioned increasing the mdelay() in the driver resolved your issue in Hardy. If the issue still exists with Intrepid, could you verify if this patch is still valid in fixing the issue for Intrepid?

Also, we'll keep this open against the actively developed kernel but against 2.6.20 this will be closed. Thanks.

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

[Launchpad Janitor (janitor)]

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

[logari81 (logari81)]

I am not sure if I should open a new report, but the here reported issue is still present in intrepid. On a fresh installation of Intrepid the following wifi-stick:

Bus 005 Device 004: ID 0846:4210 NetGear, Inc. WG121 WiFi (v2)

results to the following error in dmesg:

[ 22.528195] prism54usb: eeprom read failed!
[ 22.528219] prism54usb: probe of 5-7:1.0 failed with error -22

Regarding the information I have found here:

http://wireless.kernel.org/en/users/Drivers/p54

I could assume it was a firmware issue. Running:

sudo wget -O /lib/firmware/isl3890usb "http://jbnote.free.fr/prism54usb/data/firmwares/p54u_2.5.6.0.arm"

fixed the problem.

I have also checked that Jaunty alpha4 still includes the same firmware as Intrepid, thus I expect that the problem is still there, also in jaunty.

[Leann Ogasawara (leannogasawara)]

Thaks for the note kostas. It might be best for you to open a separate bug for now. Only because I see you have a slightly different device and driver than the original bug reporter. We can easily mark bugs as duplicates later on if necessary. I can follow up with you at the new bug report and try to bring it to the attention of the kernel team.

@Ian, since you are the original bug reporter, care to comment if the same firmware workaround kostas mentioned works for you.

[Jeremy Foshee (jeremyfoshee)]

set invalid for closure per failure to get a response from the reporter.

-JFo