Mike - EMAIL IGNORED wrote:
On Sat, 14 Jul 2007 06:46:58 -0600, Karl Larsen wrote:
Mike - EMAIL IGNORED wrote:
Thanks for this reference. I did the recommended things, but
I still have a configuration error. If I boot with the
wireless on, I get:
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?
When you use modprobe does the proper module get loaded into your
kernel? On my laptop that works great NetworkManager calls both the
ethernet port and WiFi ports eth0. It works so I don't care.
When I ran:
modprobe bcm43xx
from the command line, it didn't say anything, so I assume it worked.
Later, I added it to rc.local, and I assume it is ok.
May want to see if there's any output in dmesg from this.
What does /sbin/ifconfig say?
Error for wireless request "Set Mode" (8B06) :
SET failed on device wlan0 ; Invalid argument.
Error for wireless request "Set Bit Rate" (8B20) :
SET failed on device wlan0 ; Operation not supported.
Determining IP information for wlan0... failed.
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).
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).
--
imalone
