netgear WLAN Card & Prism54 driver

[Markus Schmidt]

Hi

I Have a netgear wlan card (PCMCIA) named WG511, the corresponding lspci output is:
0000:02:00.0 Network Controler: Intersil Corporation Intersil ISL3890
[PrismGT/Prism Duette](rev 01)

Therefore, Ubuntu (the every morning dist-upgraded version of dapper drake)
loads the prism54 module. (The problem was there in breezy, too) The interface
shows as eth1, but ignores all attemts to configure it via iwconfig. It don't
accept the essid, nor the key, and ifconfig shows a total crappy MAC Adress (not
the one thats printed on the card).
So i tried the Windows drivers via ndiswrapper, and after a "modprobe -r
prism54" and a "modprobe -i ndiswrapper" it works fine. (and shows up as wlan0)
The main Problem was to figure out that the driver is kind of "half broken"...
if there had been no eth1, i whould have tried the ndiswrapper first... little
bit confusing.

[Ben Collins (ben-collins)]

Can you attach the dmesg output when the prism54 driver is loaded?

[Markus Schmidt (m-schmidt)]

This is my first bug report, and i'm quite new in the Linux world, but willing
to learn. I hope this is what jou want:

root@schmidtl:/# dmesg | grep prism
[4294685.792000] Loaded prism54 driver, version 1.2
[4294853.614000] prism54: Your card/socket may be faulty, or IRQ line too busy :(
[4294877.356000] Unloaded prism54 driver

[Ben Collins (ben-collins)]

(In reply to comment #2)
> This is my first bug report, and i'm quite new in the Linux world, but willing
> to learn. I hope this is what jou want:

No, I actually need the entire output of dmesg. Thanks

[Markus Schmidt (m-schmidt)]

ok, sorry for beeing a bit late, here we go: I booted the PC without the card,
removed ndiswrapper module, inserted the card, and that's the result:
root@schmidtl:/home/mschmidt# dmesg
ing timer specific routine.. 5589.54 BogoMIPS (lpj=2794771)
[4294668.800000] Security Framework v1.0.0 initialized
[4294668.800000] SELinux: Disabled at boot.
[4294668.800000] Mount-cache hash table entries: 512
[4294668.800000] CPU: After generic identify, caps: bfebfbff 00000000 00000000
00000000 00004400 00000000 00000000
[4294668.800000] CPU: After vendor identify, caps: bfebfbff 00000000 00000000
00000000 00004400 00000000 00000000
[4294668.800000] CPU: Trace cache: 12K uops, L1 D cache: 8K
[4294668.800000] CPU: L2 cache: 512K
[4294668.800000] CPU: Hyper-Threading is disabled
[4294668.800000] CPU: After all inits, caps: bfebfbff 00000000 00000000 00000080
00004400 00000000 00000000
[4294668.800000] mtrr: v2.0 (20020519)
[4294668.800000] Enabling fast FPU save and restore... done.
[4294668.800000] Enabling unmasked SIMD FPU exception support... done.
[4294668.800000] Checking 'hlt' instruction... OK.
[4294668.804000] SMP alternatives: switching to UP code
[4294668.804000] checking if image is initramfs... it is
[4294669.233000] Freeing initrd memory: 6243k freed
[4294669.241000] not found!
[4294669.247000] CPU0: Intel Mobile Intel(R) Pentium(R) 4 CPU 2.80GHz
stepping 09
[4294669.247000] Total of 1 processors activated (5589.54 BogoMIPS).
[4294669.247000] ENABLING IO-APIC IRQs
[4294669.248000] ..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1
[4294669.359000] Brought up 1 CPUs
[4294669.359000] NET: Registered protocol family 16
[4294669.359000] EISA bus registered
[4294669.359000] ACPI: bus type pci registered
[4294669.359000] PCI: PCI BIOS revision 2.10 entry at 0xfd2fe, last bus=3
[4294669.359000] PCI: Using configuration type 1
[4294669.360000] ACPI: Subsystem revision 20050916
[4294669.363000] ACPI: Interpreter enabled
[4294669.363000] ACPI: Using IOAPIC for interrupt routing
[4294669.363000] ACPI: PCI Interrupt Link [LNKA] (IRQs *10)
[4294669.364000] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *11)
[4294669.364000] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 *11)
[4294669.364000] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 *11)
[4294669.365000] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 *11)
[4294669.365000] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 *11)
[4294669.365000] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 *11)
[4294669.366000] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 *11)
[4294669.366000] ACPI: PCI Root Bridge [PCI0] (0000:00)
[4294669.366000] PCI: Probing PCI hardware (bus 00)
[4294669.366000] ACPI: Assume root bridge [\_SB_.PCI0] bus is 0
[4294669.368000] Boot video device is 0000:00:02.0
[4294669.368000] PCI quirk: region d800-d87f claimed by ICH4 ACPI/GPIO/TCO
[4294669.368000] PCI quirk: region eec0-eeff claimed by ICH4 GPIO
[4294669.368000] PCI: Enabled i801 SMBus device
[4294669.368000] PCI: Ignoring BAR0-3 of IDE controller 0000:00:1f.1
[4294669.368000] PCI: Transparent bridge - 0000:00:1e.0
[4294669.368000] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
[4294669.370000] ACPI: PCI Interrupt...

[Akkana Peck (akkzilla)]

I also have a WG511 and can't get it to work with ubuntu (breezy). But I'm seeing different messages in dmesg:

[260861.820000] ACPI: PCI interrupt for device 0000:02:00.0 disabled
[260879.062000] PCI: Enabling device 0000:02:00.0 (0000 -> 0002)
[260879.062000] ACPI: PCI Interrupt 0000:02:00.0[A] -> Link [LNKB] -> GSI 9 (level, low) -> IRQ 9
[260914.260000] eth0: resetting device...
[260914.260000] eth0: uploading firmware...
[260914.480000] eth0: firmware version: 1.0.4.3
[260914.480000] eth0: firmware upload complete
[260914.754000] eth0: interface reset complete
[260925.791000] eth0: no IPv6 routers present

(let me know if you want the rest of dmesg too.)

I tried running iwconfig manually (the AP here has WEP) using the iwconfig command that works with an orinoco card, but it doesn't help.

This card used to work under a kernel.org 2.4.29 plus the appropriate firmware on sarge, so I know it's possible for the hardware to work with this laptop (which is a Vaio SR17). I haven't tried ndiswrapper.

[Ben Collins (ben-collins)]

Your messages look normal. No errors there. I would suggest trying dapper though as I can't do much for breezy.

[sam tygier (samtygier)]

is this releated to https://launchpad.net/distros/ubuntu/+source/linux-source-2.6.15/+bug/31502/

both have the symptom of ifconfig showing a junk MAC address

[Launchpad Janitor (janitor)]

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this linux-source-2.6.15 kernel bug to the new "linux" package. We appreciate your patience and understanding as we make this transition. Also, if you would be interested in testing the upcoming Intrepid Ibex 8.10 release, it is available at http://www.ubuntu.com/testing . Please let us know your results. 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.

[Ralph Janke (txwikinger)]

Unfortunately this bug report is being closed because we received no response to the last inquiry for information. However, the Intrepid Ibex 8.10 Beta release was most recently announced - http://www.ubuntu.com/testing/intrepid/beta . If you are able to confirm this is still an issue with this most recent release please feel free to reopen this report. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks.