Re: 2.6.22-41 and bcm43xx

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

 



On 13/08/07, Jesus Jr M Salvo <jesus.m.salvo@xxxxxxxxx> wrote:
> On 13/08/07, Martin Marques <martin@xxxxxxxxxxxxxxx> wrote:
> > Jesus Jr M Salvo escribió:
> > > On 12/08/07, Jesus Jr M Salvo <jesus.m.salvo@xxxxxxxxx> wrote:
> > >> With the new kernel ( 2.6.22.1-41 x86_64 ), I started getting these
> > >> error messages during bootup ( which I did not receive in previous
> > >> kernels such as 2.6.21-1.3228:
> > >>
> >
> > [snip]
> > >>
> > >> bcm43xx-phy0 debug: Chip initialized
> > >> bcm43xx-phy0 debug: 32-bit DMA initialized
> > >> bcm43xx-phy0 debug: Wireless interface started
> > >> ADDRCONF(NETDEV_UP): wlan0: link is not ready
> > >>
> > >>
> > >> Any ideas ?
> > >>
> > >
> > > Forgot to mention my actual card. From lspci -vv:
> >
> > Those the wireless card work?
> >
> > Try updating the fireware to version 4 at least.
> >
>
> If I try a v4 firmware, I get the following:
>
> $ bcm43xx-fwcutter --identify bcmwl564.sys
> *** WARNING ***
> This file contains new version4
> firmware. v4 firmware is _not_ supported by
> the driver in mainline kernels. For v4 firmware
> you need latest bcm43xx development version
> (wireless-dev kernel tree). If you don't know what
> this warning is about, use a 3.xx.xx.xx driver version
> instead to extract the firmware.
>
>
>   filename   :  bcmwl564.sys
>   version    :  4.100.15.5
>   MD5        :  feaf7ec9f38a37945b6fb169617ec859
>   microcodes :  4 5 11 13
>   pcms       :  4 5
>
>   microcode  :  4
>   revision   :  0x0173
>   patchlevel :  0x0425
>   date       :  2006-10-04
>   time       :  21:02:04
>
>   microcode  :  5
>   revision   :  0x0173
>   patchlevel :  0x0425
>   date       :  2006-10-04
>   time       :  21:02:04
>
>   microcode  :  11
>   revision   :  0x0173
>   patchlevel :  0x0425
>   date       :  2006-10-04
>   time       :  21:02:04
>
>   microcode  :  13
>   revision   :  0x0173
>   patchlevel :  0x0425
>   date       :  2006-10-04
>   time       :  21:02:04
>
>
> .... and hence, avoided v4 firmware.
>

Come to think of it, I actually don't recall if I am using a v3
firmware or if I am already using   a v4 firmware, because the .sys
file above was from my notebook manufacturer's download driver site,
and it is the latest .... so I may already have v4 running. How do I
find out which version of firmware I am using ?

-- 
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [Fedora Magazine]     [Fedora News]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [SSH]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux