Rick Bilonick wrote: > On Tue, 2007-12-11 at 16:50 +0000, Julius Smith wrote: >> Greetings, >> >> I tried using b43-firmware-download under F8 (uname -r says >> 2.6.23.8-63.fc8) on my HP dv2000 laptop. I've had wireless working in >> the past on F6 using the bcm* driver, but so far not b43 (or anything >> else) under F8. >> >> The firmware seems to be installed in /lib/firmware, and sha1sum is >> happy, but when I try to bring up the interface (using the System / >> Administration / Network "Activate" button), the DHCP fails to get an >> IP address. (It succeeds if I reboot the same laptop in Windows XP.) >> >> I find the following in /var/log/messages: >> ... >> Dec 10 11:08:06 localhost kernel: b43-phy0: Broadcom 4311 WLAN found >> ... >> Dec 10 11:08:21 localhost NetworkManager: <info> wlan0: Device is >> fully-supported using driver 'b43-pci-bridge'. >> Dec 10 11:08:21 localhost NetworkManager: <info> (wlan0): exporting >> device as /org/freedesktop/NetworkManager/Device/4 >> Dec 10 11:08:21 localhost NetworkManager: <info> Now managing >> wireless (802.11) device 'wlan0'. >> Dec 10 11:08:21 localhost NetworkManager: <info> Bringing up device wlan0 >> Dec 10 11:08:22 localhost kernel: Registered led device: b43-phy0:tx >> Dec 10 11:08:22 localhost kernel: Registered led device: b43-phy0:rx >> Dec 10 11:08:23 localhost kernel: input: Unspecified device as >> /class/input/input10 >> Dec 10 11:08:23 localhost kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready >> Dec 10 11:08:23 localhost NetworkManager: <info> Deactivating device wlan0. >> Dec 10 11:08:24 localhost kernel: ADDRCONF(NETDEV_CHANGE): wlan0: link >> becomes ready >> Dec 10 11:08:25 localhost NetworkManager: <info> Trying to start the >> supplicant... >> Dec 10 11:08:25 localhost NetworkManager: <info> (eth0) supplicant >> interface is now in state 1 (from 0). >> Dec 10 11:08:25 localhost NetworkManager: <info> (wlan0) supplicant >> manager is now in state 1 (from 0). >> Dec 10 11:08:25 localhost avahi-daemon[2509]: Registering new address >> record for fe80::214:a5ff:fee6:2150 on wlan0.*. >> Dec 10 11:08:25 localhost NetworkManager: <info> (eth0) supplicant >> interface is now in state 2 (from 1). >> Dec 10 11:08:25 localhost NetworkManager: <info> (wlan0) supplicant >> interface is now in state 2 (from 1). >> ... >> Dec 10 11:10:57 localhost gconfd (root-3137): starting (version >> 2.20.1), pid 3137 user 'root' >> Dec 10 11:10:57 localhost gconfd (root-3137): Resolved address >> "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only >> configuration source at position 0 >> Dec 10 11:10:57 localhost gconfd (root-3137): Resolved address >> "xml:readwrite:/root/.gconf" to a writable configuration source at >> position 1 >> Dec 10 11:10:57 localhost gconfd (root-3137): Resolved address >> "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only >> configuration source at position 2 >> Dec 10 11:10:58 localhost system-config-network[3127]: rm >> //etc/sysconfig/networking/profiles//default/resolv.conf >> Dec 10 11:10:58 localhost system-config-network[3127]: ln >> //etc/resolv.conf >> //etc/sysconfig/networking/profiles//default/resolv.conf >> Dec 10 11:11:10 localhost system-config-network[3127]: -+ >> //etc/modprobe.conf #011eth0 alias forcedeth >> Dec 10 11:11:10 localhost system-config-network[3127]: chmod 0644 >> //etc/sysconfig/networking/devices/ifcfg-wlan0 >> Dec 10 11:11:10 localhost system-config-network[3127]: chmod 0644 >> //etc/sysconfig/networking/devices/ifcfg-eth0 >> Dec 10 11:11:13 localhost dhclient: wmaster0: unknown hardware address type 801 >> Dec 10 11:11:13 localhost dhclient: wmaster0: unknown hardware address type 801 >> Dec 10 11:11:13 localhost dhclient: DHCPDISCOVER on wlan0 to >> 255.255.255.255 port 67 interval 4 >> Dec 10 11:11:17 localhost dhclient: DHCPDISCOVER on wlan0 to >> 255.255.255.255 port 67 interval 5 >> Dec 10 11:11:22 localhost dhclient: DHCPDISCOVER on wlan0 to >> 255.255.255.255 port 67 interval 12 >> Dec 10 11:11:34 localhost dhclient: DHCPDISCOVER on wlan0 to >> 255.255.255.255 port 67 interval 14 >> Dec 10 11:11:48 localhost dhclient: DHCPDISCOVER on wlan0 to >> 255.255.255.255 port 67 interval 9 >> Dec 10 11:11:57 localhost dhclient: DHCPDISCOVER on wlan0 to >> 255.255.255.255 port 67 interval 11 >> Dec 10 11:12:08 localhost dhclient: DHCPDISCOVER on wlan0 to >> 255.255.255.255 port 67 interval 6 >> Dec 10 11:12:14 localhost dhclient: No DHCPOFFERS received. >> >> >> By the way, following some other email, I placed the following line in >> /etc/modprobe.conf: >> >> alias wlan0 b43 >> >> Please let me know if you see my problem. >> >> Thanks, >> Julius >> > > This is similar to what happens when I try to use the latest Fedora 6 > kernels. I know I need to update to Fedora 8 but my fear is that the > bcm4318 won't work with Fedora 8 whether I use ndiswrapper or the native > driver. It works fine with the old Fedora 6 kernel I've retained and > ndiswrapper. I don't need to install Fedora 8 only to find out bcm4318 > won't work at all. At least it works in my current set up. > > Is anyone familiar with using ndiswrapper and the bcm4318 under Fedora > 8? > > Rick B. > You shouldn't have any trouble at all with the native driver. With the newer kernels (.23 specifically) I have trouble getting ndiswrapper to play nice due to the changes in the wireless stack. -- Recedite, plebes! Gero rem imperialem! Mark Haney Sr. Systems Administrator ERC Broadband (828) 350-2415 Call (866) ERC-7110 for after hours support -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
