Re: broadcom wireless driver
lucas <ashenphoenix <at> sdf.org>
2013-05-07 06:57:22 GMT
Andrew Kane (et al.),
So, for the record (I don't know if these get archived), I finally got my
Broadcom wireless card working, thanks in part to your help. The -vv flag
for lspci really helped me out, as it allowed me to see what module the
PCI was actually using, regardless of what should have been loaded. And
mentioning the udev rules led me to check the modprobe.conf files, which
have a blacklist; I blacklisted the other modules I didn't want running,
and things are running smoothly now.
Thanks again!
On Thu, 2 May 2013, Andrew Kane wrote:
> Date: Thu, 2 May 2013 18:05:44 -0700
> From: Andrew Kane <googoleyes <at> gmail.com>
> To: lucas <ashenphoenix <at> sdf.org>
> Subject: Re: [GSLUG-general] broadcom wireless driver
>
> Aw, nuts, please disregard that last- I didn't realise I was replying to you
> and not the list. Sorry about that.
>
>
> On Thu, May 2, 2013 at 6:05 PM, Andrew Kane <googoleyes <at> gmail.com> wrote:
> I think you may have conflated two different checks: the
> 'interface' is wlan0 or eth1 or similar, and should appear in
> 'ip link show'. If you see an interface that corresponds to the
> device, then you know that the kernel has managed to identify it
> (possibly incorrectly). It's good that you see the device in
> lspci, but it's important to check the chipset id. Unfortunately
> lspci has different syntax from lsusb, which gives you the
> chipset ids by default. I've not been able to convince lspci to
> give up this information, though I know I've done it before.
> Presumably this information is somewhere in /sys/ but I don't
> know where exactly.
> I think /sys/bus/pci/devices/[$BUS_ID]/vendor and ./device are the two
> parts of the ID (at least they are two hexadecimal numbers of the
> right length). These numbers are what the kernel uses to identify
> devices and what you need when authoring a udev rule to specify a
> module to load for a specific device. lspci -vv will also tell you
> which driver the kernel is currently using for the device.
> Good luck!
>
>
> On Thu, May 2, 2013 at 5:32 PM, lucas <ashenphoenix <at> sdf.org> wrote:
> re: sayli.karmarkar: I am using Fedora 17. I found
> Broadcom-wl on the computer already, but it didn't seem to
> want to work. I may look into it again, if you haven't
> had problems with it. Maybe I missed something.
>
> re: googoleyes: the interface shows up when I lspci and I
> am pretty sure that I took all the other modules that
> would interfere out of operation, just unattached them
> from the kernel, I didn't rid the directory tree of them
> or anything - I will check udev rules when I get home to
> see if anything is still getting in the way.
>
> Thanks for the suggestions.
>
>
> On Mon, 29 Apr 2013, Sayli Karmarkar wrote:
>
> Date: Mon, 29 Apr 2013 22:55:00 -0700
> From: Sayli Karmarkar
> <sayli.karmarkar <at> gmail.com>
> To: lucas <ashenphoenix <at> sdf.org>
> Cc: gslug-general <at> gslug.org
> Subject: Re: [GSLUG-general] broadcom wireless
> driver
>
> Lucas,
>
> Which version of fedora are you using? Have
> you already tried installing
> broadcom-wl? I think it is available in
> RPMFusion repos-http://download1.rpmfusion.org/nonfree/fedora/releases/16/Everything/x86_6
> 4
> /os/repoview/broadcom-wl.html
>
> I have used it for all pre-F17 OSs on my dell
> laptop and worked fine. For
> F17 and later, it worked without installing
> broadcom-wl.
>
>
> On Mon, Apr 29, 2013 at 5:32 PM, lucas
> <ashenphoenix <at> sdf.org> wrote:
> Hey,
>
> I just recently put Fedora on a Dell
> laptop and can't get a
> wireless connection. After wandering
> around the internet for a
> bit, I found out that the Dell wireless
> PCI needs a particular
> driver, Broadcom, that doesn't come with
> Fedora; I installed the
> module, depmod-and-modprobed it to
> attach it to the kernel, and
> now nothing is happening. Still.
>
> I don't know what exactly I am doing
> wrong, or if there is
> another step that I don't know about -
> someone on SDF suggested
> needing to reconfigure the kernel system
> controls, but I
> couldn't find what to toggle. I am
> hoping that either someone
> else has run into this dilemma and that
> I might be able to learn
> from their experience or there is some
> wizard out there who can
> bestow some of their infinite kernel
> wisdom on me and help out a
> fledgling.
>
> Anything helps. Really.
>
> Thanks.
>
>
> ashenphoenix <at> sdf.org
> SDF Public Access UNIX System -
> http://sdf.org
>
> --
> --
> --
> GSLUG-general mailing list
>
> http://www.gslug.org/wiki/index.php/Mailing_Lists
>
>
>
>
>
>
> --
> ~SayliK
>
> --
> --
> --
> GSLUG-general mailing list
> http://www.gslug.org/wiki/index.php/Mailing_Lists
>
>
>
>
>
>
> ashenphoenix <at> sdf.org
> SDF Public Access UNIX System - http://sdf.org
>
> --
> --
> --
> GSLUG-general mailing list
> http://www.gslug.org/wiki/index.php/Mailing_Lists
>
>
>
>
>
>
> --
> <a href="http://www.fsf.org/fb"><img
> src="http://static.fsf.org/nosvn/no-facebook-me.png" alt="Not f'd ? you
> won't find me on Facebook" /></a>
>
>
>
>
> --
> <a href="http://www.fsf.org/fb"><img
> src="http://static.fsf.org/nosvn/no-facebook-me.png" alt="Not f'd ? you won't
> find me on Facebook" /></a>
>
>
ashenphoenix <at> sdf.org
SDF Public Access UNIX System - http://sdf.org
--
--
--
--
GSLUG-general mailing list
http://www.gslug.org/wiki/index.php/Mailing_Lists
RSS Feed