You are not logged in.
Pages: 1
Hi-I have been trying out many distros lately on my Acer Aspire laptop and have noticed that on Saline and Semplice (both Debian based)my broadcom wifi is detected without any setup issues.
Is there any chance that #! can do the same in future?
I have been running Statler, and now Waldorf on my netbook for getting on 2 years-would like to install it on my Acer Aspire laptop as well but the broadcom issue is stopping me.
Last edited by ronaldo99 (2012-08-09 21:19:18)
Offline
Whether your Broadcom card is supported OOTB depends on the chipset...
while ( ! ( succeed = try() ) );
We've earned a reputation as a nice, friendly community; please help us keep it that way.
Offline
I use an Acer Aspire One which doesn't work out of the box, but is very simple to set up with a couple of package downloads.
i wonder if i missed the warning
Skinny Puppy, Love in Vein
Offline
Thanks for your comments-I have tried both live/fully installed #! on my laptop with no success already.
I have downloaded the exact same broadcom packages that are loaded(and work for me) in the Saline and Semplice repos and still no joy with wifi.
Not a problem as I finished up installing Saline, but would have preffered#! as it is my favorite.
Offline
Well, just for the record: http://wiki.debian.org/wl.
i wonder if i missed the warning
Skinny Puppy, Love in Vein
Offline
I will try to install again today as I really prefer #! over the other debian based distros I have tried.
I just cant understand why Semplice/Saline/Solus all recognise my laptops broadcom setup without any changes/downloads having to be made.
Offline
^ and note that Statler = Squeeze, and Waldorf = Wheezy (just for the record
)
True, pidsley. Not to get off track and to clarify: As part of the Debian naming convention, Wheezy is one of the "Toy Story" characters, after which Debian names its releases -- to say nothing of Sid, the kid next door who did, well, "experiments" on toys, being the testing area for Debian. IMHO, this is the best naming convention of all distros.
Corenominal takes the first letter of the Debian release and matches it with a "Muppet Show" character, with Waldorf and Statler being the old guys in the balcony. This is the second best naming convention of all distros 
Sorry, but I have no solution to this problem. When wireless problems arise, I take the conch shell, climb the highest mountain and sound the alarm, hoping xaos52 will hear it.
Res publica non dominetur | Larry the CrunchBang Guy speaks of the pompetous of CrunchBang
Offline
I just cant understand why Semplice/Saline/Solus all recognise my laptops broadcom setup without any changes/downloads having to be made.
They may ship the broadcom firmware/modules as part of their distro. You could try running
lsmodwhen you are in one of the distros that works with your wireless to see what modules are loaded.
You could also run
dmesg | tailto see the last part of the dmesg log to see if that gives you any clues.
Sorry, but I have no solution to this problem. When wireless problems arise, I take the conch shell, climb the highest mountain and sound the alarm, hoping xaos52 will hear it.
(off-topic) Where is the good doctor? He hasn't posted for at least a week...
Last edited by pidsley (2012-08-09 16:08:28)
Want Waldorf, but with sid and systemd? Try Darkside.
Offline
Installed Statler and used help and instructions given by pidsley and safetycopy.
Everything sorted - many thanks for your patience.
Now got #! on both netbook and laptop - magic
Offline
@ronaldo99: Glad to hear it!
i wonder if i missed the warning
Skinny Puppy, Love in Vein
Offline
@ronaldo99: I'm downloading Semplice alpha 2 now, because support for the Broadcom 4311 in my laptop in #!/Debian has typically been very poor. Wireless disconnects and reconnects regularly even when I'm sitting in the same room as the wireless router, for example.
• Support #! • Waldorf • Debian sid • Xubuntu • siduction • Peppermint • OpenBox • Xfce • LXDE •
Offline
guys i would like to say something (before it goes to solve) that may help others in the future if you have trouble with broadcom get b43fwcutter and the firmware from the site then (while on ethernet) then activate b43fwcutter by dragging the firmware that you got over it (yes i know much like windows) if i remember correctly a terminal should open up for a second spit out some lines of text then close after that reboot and all should be good (note im doing it all from memory but thats how i got my wifi to work on many distros) 
As a programmer i often ask myself could i get out of taking spanish in school because i know two languages Python and lua
Offline
Sorry I missed the Broadcom party.
I was blessed/cursed with Broadcom wifi for at least 7 years and did a lot of ndiswrapper solutions early on.
@Crunchy's solution is also a practical one.
These days most of this is supported and here is my method ..Usually.
May be of some help to someone.
run
lspci -vthe last couple of returns will have your NICs including wifi info.
Head for http://wiki.debian.org/WiFi/
page down to find your appropriate Wifi Chip.
and click on the link (right Column) for the complete instructions
With Broadcom your choices can be (Depending on Chip) Ndiswrapper, wl, b43xx, or brcm80211,
Never had a Broadcom wifi that failed completely with Linux. Only degrees of time involved to light it up.
Last edited by sqlpython (2012-08-10 03:42:12)
OHCG #!, Jessie,, Siduction-13.1, Bridge- , Slackware, Sabayon XI, Calculate 13.4
Offline
Pages: 1
Copyright © 2012 CrunchBang Linux.
Proudly powered by Debian. Hosted by Linode.
Debian is a registered trademark of Software in the Public Interest, Inc.