On Sat, 14 Jul 2007 19:07:32 +0100, Ian Malone wrote: > Mike - EMAIL IGNORED wrote: >> On Sat, 14 Jul 2007 06:46:58 -0600, Karl Larsen wrote: >> >>> Mike - EMAIL IGNORED wrote: > [...] >>>> Jul 13 21:50:16 mbrc35 NetworkManager: nm_device_is_802_3_ethernet: >>>> assertion `dev != NULL' failed >>>> Jul 13 21:50:16 mbrc35 NetworkManager: nm_device_is_802_11_wireless: >>>> assertion `dev != NULL' failed >>>> >>>> Note that I had changed the device name from the incorrect eth1 to >>>> wlan0. This required some hand file editing, because the change >>>> did not propagate to all gui places. It appears I am missing a >>>> device name somewhere. >>>> > > Did those messages appear before you made the changes from > eth1 to wlan0? I don't remember. It did say things like "no such device". [...] > > I really do think you should try it as eth1 first before > changing it, you may have introduced extra problems. > FWIW, my 3945abg appears as eth1 with one driver and wlan0 > with another (and both drivers will work provided the > correct interface is used). I hesitate to make that change, at least now. I think it got further along after the change. > > If that doesn't work it might be time to investigate ndiswrapper > or ask for help on the bcm43xx forum (http://bcm43xx.spugna.org/ > but it's currently offline). [...] If it is not fixed by Monday, I will look into these. Thanks, Mike.
