Mike - EMAIL IGNORED wrote:
On Sat, 14 Jul 2007 06:46:58 -0600, Karl Larsen wrote:
Mike - EMAIL IGNORED wrote:
On Fri, 13 Jul 2007 23:26:54 +0100, Ian Malone wrote:
[...]
Not at all sure. However 'firmware' is a misleading term; I
think it's really microcode that the driver needs to load onto
the controller (which the WinXP driver will do).
Just found:
http://lists.infradead.org/pipermail/fedora-ppc/2006-March/000804.html
--
imalone
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.
Time to stop for the evening at -0400.
Mike.
Hi Mike, a couple of questions. I see your using NetworkManager. I
assume you stopped network
Yes, I set things up with chkconfig.
and also loaded both Network-- files.
If you mean:
bcm43xx-fwcutter -w /lib/firmware /mnt/cdrom/BCMWL5.SYS
bcm43xx-fwcutter -w /lib/firmware /mnt/cdrom/BCMWL564.SYS
yes, I did it. If you mean some other files, maybe not.
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.
Do not assume a darn thing. Do a lsmod and make sure it is in the
kernel. Now take the thing out of rc.local. NeworkManager will add it to
/etc/modprobe.conf and it will be taken care of.
Karl
When I try to activate it from the "Network Device Control" gui, I get:
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.
and this in /var/log/messages:
Jul 14 13:21:51 localhost dhclient: wmaster0: unknown hardware
address type 801
Jul 14 13:21:51 localhost dhclient: wmaster0: unknown hardware
address type 801 Jul 14 13:21:51 localhost dhclient:
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
Jul 14 13:21:54 localhost dhclient: DHCPDISCOVER on wlan0 to
255.255.255.255 port 67 interval 5
Jul 14 13:21:59 localhost dhclient: DHCPDISCOVER on wlan0 to
255.255.255.255 port 67 interval 14
Jul 14 13:22:13 localhost dhclient: DHCPDISCOVER on wlan0 to
255.255.255.255 port 67 interval 21
Jul 14 13:22:34 localhost dhclient: DHCPDISCOVER on wlan0 to
255.255.255.255 port 67 interval 18
Jul 14 13:22:52 localhost dhclient: No DHCPOFFERS received.
Watching the router, I see no sign of action. I note also that
WinXP on the same box makes the wireless connection with no problem.
Well your not set up right yet in Linux so it will not work. What does
nm-tool tell you about your setup?
Karl
Thanks for your help.
Mike.
