Re: bcm4318 - Can It Work with Newer Kernels?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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


On Nov 22, 2007 12:36 PM, John W. Linville <linville@xxxxxxxxxx> wrote:
> On Wed, Nov 21, 2007 at 11:05:29AM -0500, Rick Bilonick wrote:
> > On Wed, 2007-11-21 at 10:50 -0500, John W. Linville wrote:
> >
> > > One or both of us is confused...
> > >
> > > If you are using ndiswrapper, then it does not matter what (if
> > > anything) you have in /lib/firmware.  I can offer you no support
> > > with ndiswrapper.
>
> > uname -r shows:
> >
> > 2.6.20-1.2962.fc6
> >
> > This is the "old" kernel where ndiswrapper works. When I upgraded to a
> > newer (and all newer) F6 kernels, ndiswrapper no longer works. First I
> > received error messages about mismatched versions of iwlist (or
> > wireliess tools). I've installed at least 5 newer kernels (keeping the
> > one that the wireless works). I don't get the original error message but
> > then started to get messages about firmware. (ndiswrapper was updated to
> > the latest version - I expected everything to continue working after
> > updating the kernels and other files).
> >
> > Will ndiswrapper work with the version 3 firmware under F8?
>
> Again, ndiswrapper doesn't use /lib/firmware.  Those messages are not
> coming from ndiswrapper.  Please forget about ndiswrapper unless/until
> you have actually tried using b43 on an F7, F8, or Rawhide kernel.
>
> The b43 driver requires version 4 firmware.  Using an F8 kernel,
> the firmware needs to be extracted with b43-fwcutter.
>
> Once you install or upgrade to F8, the easiest method I can offer
> you to get this working is to download and install this package:
>
>         http://fedora.tuxdriver.com/rfc/b43-firmware-download-351.126-1.fc8.noarch.rpm
>
> Then you will need to establish a wired connection to the Internet.
> Afterwards you can either reboot (presuming your wired configuration
> was configured with system-config-network) or run the following command
> (as root):
>
>         b43-firmware-download
>
> I'm sorry, but I can't be confident that even the latest FC6 kernels
> will support your card.  I also doubt that the rpm above will work
> on anything earlier than at least F7.  Your best bet to get your
> 4318 working is to use a modern Fedora installation.  If your 4318
> doesn't work with the stock F8 kernels then you can always fall back
> on ndiswrapper, which I presume will still work (although I cannot
> support it).
>
> John
> --
> John W. Linville
> linville@xxxxxxxxxx
>
>
> --
> fedora-list mailing list
> fedora-list@xxxxxxxxxx
> To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
>


[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux