Well .. it may be a simple fix. Here is the messages and dmesg. Sep 14 17:33:32 pollux kernel: bcm43xx: set security called Sep 14 17:33:32 pollux kernel: bcm43xx: .level = 0 Sep 14 17:33:32 pollux kernel: bcm43xx: .enabled = 0 Sep 14 17:33:32 pollux kernel: bcm43xx: .encrypt = 0 Sep 14 17:33:32 pollux kernel: bcm43xx: PHY connected Sep 14 17:33:32 pollux firmware_helper[2624]: Loading of /lib/firmware/bcm43xx_microcode5.fw for bcm43xx driver failed: No such file or directory Sep 14 17:33:32 pollux kernel: bcm43xx: Error: Microcode "bcm43xx_microcode5.fw" not available or load failed. Sep 14 17:36:05 pollux kernel: ndiswrapper: driver bcmwl5a (Broadcom,02/10/2005, 3.100.35.1) loaded Sep 14 17:36:05 pollux kernel: wlan0: ndiswrapper ethernet device 00:0b:7d:1e:be:ee using driver bcmwl5a, 14E4:4320.5.conf Sep 14 17:59:51 pollux kernel: bcm43xx driver Sep 14 17:59:53 pollux kernel: bcm43xx: Chip ID 0x4306, rev 0x3 Sep 14 17:59:53 pollux kernel: bcm43xx: Number of cores: 5 Sep 14 17:59:53 pollux kernel: bcm43xx: Core 0: ID 0x800, rev 0x4, vendor 0x4243, enabled Sep 14 17:59:53 pollux kernel: bcm43xx: Core 1: ID 0x812, rev 0x5, vendor 0x4243, disabled Sep 14 17:59:53 pollux kernel: bcm43xx: Core 2: ID 0x80d, rev 0x2, vendor 0x4243, enabled Sep 14 17:59:53 pollux kernel: bcm43xx: Core 3: ID 0x807, rev 0x2, vendor 0x4243, disabled Sep 14 17:59:53 pollux kernel: bcm43xx: Core 4: ID 0x804, rev 0x9, vendor 0x4243, enabled Sep 14 17:59:53 pollux kernel: bcm43xx: PHY connected Sep 14 17:59:53 pollux kernel: bcm43xx: Detected PHY: Version: 2, Type 2, Revision 2 Sep 14 17:59:53 pollux kernel: bcm43xx: Detected Radio: ID: 2205017f (Manuf: 17f Ver: 2050 Rev: 2) Sep 14 17:59:53 pollux kernel: bcm43xx: Radio turned off Sep 14 17:59:53 pollux kernel: bcm43xx: Radio turned off Sep 14 18:02:36 pollux kernel: bcm43xx: set security called Sep 14 18:02:36 pollux kernel: bcm43xx: .level = 0 Sep 14 18:02:36 pollux kernel: bcm43xx: .enabled = 0 Sep 14 18:02:36 pollux kernel: bcm43xx: .encrypt = 0 Sep 14 18:02:36 pollux kernel: bcm43xx: PHY connected Sep 14 18:02:36 pollux firmware_helper[2484]: Loading of /lib/firmware/bcm43xx_microcode5.fw for bcm43xx driver failed: No such file or directory Sep 14 18:02:36 pollux kernel: bcm43xx: Error: Microcode "bcm43xx_microcode5.fw" not available or load failed. >On Thu, 2006-09-14 at 22:36 +0100, Patrick von der Hagen wrote: > Steven Haigh schrieb: > > Quoting James <jdickson@xxxxxxxxxx>: > >> Thanks.. I would love to use the bcm43xx module but it is flaky at best > >> on my Dell Latitude D800.. ndiswrapper works really well. > > > > I have the same on my Inspiron 8600. The rest of the machine works > I'll probably find some time at the weekend to finally file bug-reports > related to bcm43xx. > > Strangely engough the only three people reporting problems related to > bcm43xx are all running Dell-laptops, so I wonder whether that might be > related. > > I'd be happy if I could get some reports regarding bcm43xx so I can > perhaps include them when doing bug-reports. So I'd like to ask all > users running bcm43xx and Dell-laptops to send me some information > off-list, at least product-name and "works", "doesn't work", but of > course it would be better with additional information like lspci-output. > > But of course, every other reports on hardware using bcm43xx will be > very welcome, too. ;-) > > The problems I've seen so far: > - crash when starting NetworkManager > - crash when using NetworkManager to connect to a wlan > - crash when using wpa_supplicant to connect to a wlan > - crashes when being connected to my lan and not using wlan at all (last > syslog-messages are related to some reinitialisation of the bcm43xx-module) > > Finally I'd like to point out... > - I first tried bcm43xx when it was experimental and not included in the > standard-kernel > - Stability on my laptop has not improved, so I had no reason to > consider it anything but experimental. I have not realized that > others had more success running that driver. > - bcm43xx seems to change with every new fedora-kernel so I believed > "someone is currently working at bcm43xx, so they know there are > problems". That's why I did not file bug-reports regarding my problems. > - I do run the official Dell-firmware for my Precision M60 in Europe. > This is a firmware which the bcm43xx-fwcutter-Readme approves as being > successfully tested. > - I currently keep the last six fedora-kernels installed and so far at > least one of them has always been able to successfully run start-up, > while most lock up when starting NetworkManager and > NetworkManagerDispatcher. > > -- > CU, > Patrick. > -- fedora-test-list mailing list fedora-test-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list