| 2007-04-16 12:32:17 |
Ian Ohr |
bug |
|
|
added bug |
| 2007-04-16 12:33:33 |
Ian Ohr |
description |
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 agalinux-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. |
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. |
|
| 2007-04-25 01:04:06 |
Javier Jardón |
None: status |
Unconfirmed |
Needs Info |
|
| 2007-04-25 01:04:06 |
Javier Jardón |
None: assignee |
|
torkiano |
|
| 2007-04-25 01:04:06 |
Javier Jardón |
None: statusexplanation |
|
|
|
| 2007-04-28 12:36:17 |
Ian Ohr |
bug |
|
|
added attachment 'uname-a.log' (uname-a.log) |
| 2007-04-28 12:36:55 |
Ian Ohr |
bug |
|
|
added attachment 'lspci-vvn.log' (lspci-vvn.log) |
| 2007-04-28 12:37:14 |
Ian Ohr |
bug |
|
|
added attachment 'lspci-vvn.log' (lspci-vvn.log) |
| 2007-04-28 12:38:17 |
Ian Ohr |
bug |
|
|
added attachment 'lspci-vv.log' (lspci-vv.log) |
| 2007-04-28 12:38:50 |
Ian Ohr |
bug |
|
|
added attachment 'dmesg-1.log' (dmesg-1.log) |
| 2007-04-28 12:39:08 |
Ian Ohr |
bug |
|
|
added attachment 'dmesg-2.log' (dmesg-2.log) |
| 2007-04-28 18:23:40 |
Javier Jardón |
marked as duplicate |
|
90902 |
|
| 2007-05-05 15:11:57 |
Ian Ohr |
removed duplicate marker |
90902 |
|
|
| 2007-05-06 00:22:50 |
Javier Jardón |
None: status |
Needs Info |
Confirmed |
|
| 2007-05-06 00:22:50 |
Javier Jardón |
None: assignee |
torkiano |
ubuntu-kernel-team |
|
| 2007-05-06 00:22:50 |
Javier Jardón |
None: statusexplanation |
Has this bug actually been marked as a duplicate of Bug# 90902? |
|
|
| 2008-05-02 14:48:25 |
Javier Jardón |
bug |
|
|
assigned to linux (Ubuntu) |
| 2008-05-04 06:01:15 |
michiel roeleveld |
bug |
|
|
added attachment 'dmesg.log' (dmesg.log) |
| 2008-05-04 06:02:42 |
michiel roeleveld |
bug |
|
|
added attachment 'lspci-vvnn.log' (lspci-vvnn.log) |
| 2008-05-04 06:03:01 |
michiel roeleveld |
bug |
|
|
added attachment 'lsusb.log' (lsusb.log) |
| 2008-05-04 06:03:19 |
michiel roeleveld |
bug |
|
|
added attachment 'proc_version_signature.log' (proc_version_signature.log) |
| 2008-05-04 06:05:51 |
michiel roeleveld |
bug |
|
|
added attachment 'uname-a.log' (uname-a.log) |
| 2008-05-17 12:45:30 |
michiel roeleveld |
bug |
|
|
added attachment 'patch_p54pci.patch' (patch_p54pci.patch) |
| 2008-08-13 18:18:20 |
Leann Ogasawara |
linux: status |
New |
Incomplete |
|
| 2008-08-13 18:18:20 |
Leann Ogasawara |
linux: statusexplanation |
|
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. |
|
| 2008-08-13 18:18:34 |
Leann Ogasawara |
linux-source-2.6.20: status |
Confirmed |
Won't Fix |
|
| 2009-02-07 20:19:34 |
logari81 |
bug |
|
|
added attachment 'lsusb -vv' (lsusb -vv) |
| 2009-02-07 20:20:08 |
logari81 |
bug |
|
|
added attachment 'dmesg-before' (dmesg-before) |
| 2009-02-07 20:20:42 |
logari81 |
bug |
|
|
added attachment 'dmesg-after' (dmesg-after) |
| 2009-03-05 20:31:19 |
Leann Ogasawara |
linux: bugtargetdisplayname |
linux (Ubuntu) |
linux-firmware (Ubuntu) |
|
| 2009-03-05 20:31:19 |
Leann Ogasawara |
linux: bugtargetname |
linux (Ubuntu) |
linux-firmware (Ubuntu) |
|
| 2009-03-05 20:31:19 |
Leann Ogasawara |
linux: statusexplanation |
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. |
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. |
|
| 2009-03-05 20:31:19 |
Leann Ogasawara |
linux: title |
Bug #106987 in linux (Ubuntu): "netgear WG511v1 PCMCIA card: prism54pci Cannot read eeprom" |
Bug #106987 in linux-firmware (Ubuntu): "netgear WG511v1 PCMCIA card: prism54pci Cannot read eeprom" |
|
| 2010-02-04 02:02:36 |
Jeremy Foshee |
linux-firmware (Ubuntu): status |
Incomplete |
Invalid |
|
