Since nobody reply after Jaunty released. I've been using Jaunty (x86_64) with, prism54 (isl3890) pcmcia, prism54 module and p54pci module. Both modules still getting problem until the latest patches (2.6.28-15-generic) and latest firmware from http://daemonizer.de/prism54/prism54-fw/.
Here is the output from p54pci module: [ 1196.510172] p54pci 0000:03:00.0: enabling device (0000 -> 0002) [ 1196.510186] p54pci 0000:03:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18 [ 1196.510204] p54pci 0000:03:00.0: setting latency timer to 64 [ 1196.510396] p54pci 0000:03:00.0: firmware: requesting isl3886 [ 1196.545866] p54: LM86 firmware [ 1196.545872] p54: FW rev 2.17.2.0 - Softmac protocol 7.6 [ 1197.652065] phy1: Cannot boot firmware! [ 1197.652135] p54pci 0000:03:00.0: PCI INT A disabled [ 1197.652162] p54pci: probe of 0000:03:00.0 failed with error -110 Here is the output from prism54 module: [ 1268.644653] Loaded prism54 driver, version 1.2 [ 1268.644721] prism54 0000:03:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18 [ 1273.428435] eth1: resetting device... [ 1273.428456] eth1: uploading firmware... [ 1273.478087] prism54 0000:03:00.0: firmware: requesting isl3890 [ 1273.525538] eth1: firmware version: 1.0.4.3 [ 1273.525595] eth1: firmware upload complete [ 1273.848045] eth1: timeout waiting for mgmt response 250, triggering device [ 1273.948064] eth1: timeout waiting for mgmt response 225, triggering device [ 1274.048051] eth1: timeout waiting for mgmt response 200, triggering device [ 1274.148054] eth1: timeout waiting for mgmt response 175, triggering device [ 1274.248042] eth1: timeout waiting for mgmt response 150, triggering device [ 1274.348038] eth1: timeout waiting for mgmt response 125, triggering device [ 1274.448055] eth1: timeout waiting for mgmt response 100, triggering device ... and so on. After unloading prism54 module will lead to kernel panic and system rebooting. Thanks. -- prism54 module freezes system with 2.6.22-10 https://bugs.launchpad.net/bugs/134593 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
