LinuxQuestions.org
Go Job Hunting at the LQ Job Marketplace
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
LinkBack Search this Thread
Old 01-27-2012, 08:39 PM   #1
frankbell
Guru
 
Registered: Jan 2006
Location: Virginia, USA
Distribution: Slackware, Debian, Mageia, Mint
Posts: 6,903

Rep: Reputation: 1284Reputation: 1284Reputation: 1284Reputation: 1284Reputation: 1284Reputation: 1284Reputation: 1284Reputation: 1284Reputation: 1284
Broadcom Trouble Dell 1545n Slackware Current


I'm having trouble getting my Broadcom wireless working in my Dell 1545n laptop with Slackware Current. Wired works fine.

I have tried the broadcom-sta and b43-fwcutter from Slackbuilds twice with no luck. I did follow the instructions to update the /etc/modprobe.d/b43-blacklist.conf file as described on the Slackbuilds broadcom-sta page.

Here is the output of uname -a:

Code:
Linux hammerhead 2.6.38.7-smp #2 SMP Sat May 21 23:13:29 CDT 2011 i686 Genuine Intel(R) CPU             585  @ 2.16GHz GenuineIntel GNU/Linux
and of lspci -vnn | grep 14e4 per the instructions at LinuxWireless.

Code:
0c:00.0 Network controller [0280]: Broadcom Corporation BCM4312 802.11b/g LP-PHY [14e4:4315] (rev 01)
The system threw no error messages throughout the process.

I did get the Broadcom working perfectly on my Dell Mini 9 with Salix following the instructions from the Salix website. That machine seems to have a similar chipset. Here's the info from the Mini 9:

Code:
03:00.0 Network controller [0280]: Broadcom Corporation BCM4312 802.11b/g LP-PHY [14e4:4315] (rev 01)
	Subsystem: Broadcom Corporation Device [14e4:04b5]
Any suggestions would be most welcome.

Edit: The Salix box is running v. 13.37.

Last edited by frankbell; 01-27-2012 at 08:43 PM.
 
Old 01-28-2012, 01:39 AM   #2
ukiuki
Senior Member
 
Registered: May 2010
Location: Planet Earth
Distribution: Debian
Posts: 1,020

Rep: Reputation: 284Reputation: 284Reputation: 284
You may just need the firmware, i had similar problem once and all was missing was the firmware.
Try this: http://www.omattos.com/node/6

Regards
 
Old 01-28-2012, 08:42 PM   #3
frankbell
Guru
 
Registered: Jan 2006
Location: Virginia, USA
Distribution: Slackware, Debian, Mageia, Mint
Posts: 6,903

Original Poster
Rep: Reputation: 1284Reputation: 1284Reputation: 1284Reputation: 1284Reputation: 1284Reputation: 1284Reputation: 1284Reputation: 1284Reputation: 1284
Thanks. The Slackbuilds broadcom-sta claimed to have the firmware but maybe it didn't like me.

The omattos link doesn't seem to like me either, at least not right now.

I'll probably won't be able to dig into this again until Tuesday. I'll certainly let you know what happens.

Last edited by frankbell; 01-29-2012 at 09:01 PM.
 
Old 01-29-2012, 05:34 PM   #4
doomey
LQ Newbie
 
Registered: Nov 2009
Location: on orbit around the sun and around the center of the galaxy
Distribution: slackware64
Posts: 24

Rep: Reputation: 2
you were not very clear: did you install b43-fwcutter and b43-firmware (in that order) from slackbuilds?
try doing that and don't forget to remove the blacklisting of b43 and ssb from blacklist.conf.

or you could try donwloading the latest sta driver (be careful of arch, 32 or 64), unpacking it to some directory, cd there, and then run:
Code:
make clean && make && make install && depmod -a
if you use the sta driver, then leave b43 and ssb blacklisted.

and don't forget to restart.
 
1 members found this post helpful.
Old 01-29-2012, 08:55 PM   #5
frankbell
Guru
 
Registered: Jan 2006
Location: Virginia, USA
Distribution: Slackware, Debian, Mageia, Mint
Posts: 6,903

Original Poster
Rep: Reputation: 1284Reputation: 1284Reputation: 1284Reputation: 1284Reputation: 1284Reputation: 1284Reputation: 1284Reputation: 1284Reputation: 1284
Quote:
Originally Posted by doomey View Post
you were not very clear: did you install b43-fwcutter and b43-firmware (in that order) from slackbuilds?
As described, I did the broadcom-sta, then the b43-fwcutter. I did it once befire, then, after consulting with a member of my LUG, tried it again. I figured it was time to seek advice from a wider circle.

I'll try the bw43-firmware a whirl on Tuesday.

Thanks.

Last edited by frankbell; 01-29-2012 at 09:02 PM.
 
Old 01-31-2012, 08:27 PM   #6
frankbell
Guru
 
Registered: Jan 2006
Location: Virginia, USA
Distribution: Slackware, Debian, Mageia, Mint
Posts: 6,903

Original Poster
Rep: Reputation: 1284Reputation: 1284Reputation: 1284Reputation: 1284Reputation: 1284Reputation: 1284Reputation: 1284Reputation: 1284Reputation: 1284
Update--real life caught up with me. I'll update when I escape from it.
 
Old 02-01-2012, 10:40 AM   #7
onebuck
Moderator
 
Registered: Jan 2005
Location: Midwest USA, Central Illinois
Distribution: SlackwareŽ
Posts: 10,893
Blog Entries: 1

Rep: Reputation: 1308Reputation: 1308Reputation: 1308Reputation: 1308Reputation: 1308Reputation: 1308Reputation: 1308Reputation: 1308Reputation: 1308Reputation: 1308
Member response

Hi,

One note for 'sta', sometimes the device is recognized as a eth device instead of wlan. Your device may be assigned eth1 or another eth(depend on devices in system).

Look at Linux-Wireless which shows for your '14e4:4315' Broadcom 4312 will use either the 'sta' or 'b43' driver but you will need the firmware.

device list contains list of manufacture supported wireless.

Maybe this old post will help: Slackware 13.0 RC2 X86_64 Broadcom bcm4312 problems

HTH!
 
1 members found this post helpful.
Old 02-05-2012, 08:05 PM   #8
frankbell
Guru
 
Registered: Jan 2006
Location: Virginia, USA
Distribution: Slackware, Debian, Mageia, Mint
Posts: 6,903

Original Poster
Rep: Reputation: 1284Reputation: 1284Reputation: 1284Reputation: 1284Reputation: 1284Reputation: 1284Reputation: 1284Reputation: 1284Reputation: 1284
Thank you all for your responses.

I finally got it working using the STA driver during the interminable garbage in between the actual play of the game in the US NFL Super Bowl.

I took a methodical approach, changing one thing at a time.

After making each change, I would reboot, test ifconfig and iwconfig, then make another change.

Once the wlan0 appeared in iwconfig, it gave me

Quote:
Operation not possible due to RF-kill
in response to

Quote:
ifconfig wlan0 up
I looked that up and found it meant that the hardware switch (on this computer, the F3 key) was toggled off. I toggled it on and bingo! wireless.

Once again, thank you all for your help.

Last edited by frankbell; 02-05-2012 at 08:06 PM.
 
  


Reply

Tags
14e:4315, broadcom, dell, slackware


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Google Earth and Ubuntu 10.04 Dell 1545n laptop frankbell Linux - Software 4 12-06-2010 09:23 PM
[SOLVED] Image/icon trouble after slackware-current upgrade camphor Slackware 5 01-23-2010 04:57 AM
Slackware 12.2 -- Dell e1405 Wifi "Broadcom BCM4311" DirkDD Linux - Newbie 5 03-27-2009 07:26 AM
Slackware, Broadcom NIC Internet Trouble Chryzmo Slackware 6 09-10-2005 06:18 PM
Slackware-current network initialization trouble Danus ex Slackware 3 05-31-2005 08:37 PM


All times are GMT -5. The time now is 08:15 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration