Re: one more time -- broadcom wireless on f7 [SUCCESS!!]

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

 



On Wed, 15 Aug 2007, Martin Marques wrote:

> Robert P. J. Day escribió:
> > On Wed, 15 Aug 2007, Martin Marques wrote:
> >
> > > Robert P. J. Day escribió:
> > > >   and the successes keep piling up.  i used exactly the same recipe on
> > > > a different model gateway laptop (MX8711 versus MX7120) with a
> > > > different broadcom chip:
> > > >
> > > > * previous: BCM4318 [AirForce One 54g]
> > > > * new one:  BCM94311MCG wlan mini-PCI
> > > I have this exact one on my Compaq Presario, and Networkmarager just
> > > doesn't work with the WLAN.
> > >
> > > system-config-network and a network restart made it work.
> >
> > ok, there's another mystery i would like to clear up.  when you say
> > you used system-config-network, are you saying that you can actually
> > see the broadcom chip?
>
> No. I had to download the firmware and modprobe bcm43xx-80211.
>
> As a matter of fact: The documentation out there on the web is
> erroneous. It always talks about using the bcm43xx module, when for
> the BCM94311MCG wlan mini-PCI you have to use the new bcm43xx-80211.

ok, i'm confused again, because i got my other gateway laptop (with
that very broadcom mini-PCI chip) on the net using the same
instructions as before, and the same module -- i didn't have to do
anything with a "bcm43xx-80211" module.  (in fact, i just searched
under /lib/modules on a fresh f8-t1 install, and there isn't even a
module by that name.  are you sure that's the correct spelling?
where did it come from?)

> Once modprobe was correctly executed, the wlan0 interface gets up
> and you can configure it with system-config-network.
>
> P.D.: I did have to add this line to /etc/modprobe.conf
>
> alias wlan0 bcm43xx-mac80211
                      ^^^^^^^^

ok, i'm assuming *that's* the correct spelling, except that it has an
underscore, not a hyphen.   but i didn't have to do anything explicit
with that module since it was already loaded, so i don't understand
why you needed to do an explicit modprobe.

however, even with that module loaded and the firmware installed,
system-config-network doesn't show me that chip, so i'm back to doing
it the manual way, same as before.  if you got that broadcom chip to
show up in system-config-network, i'd love to know how.

rday
-- 
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA

http://crashcourse.ca
========================================================================
-- 
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