56 replies to this topic

[V.T. Eric Layton]

root_Slackware/home/vtel57:# iwconfiglo		no wireless extensions.eth0	  no wireless extensions.wlan0	 IEEE 802.11bg  Mode:Managed  Access Point: Not-Associated   		  Tx-Power=0 dBm   		  Retry  long limit:7   RTS thr:off   Fragment thr:off		  Encryption key:off		  Power Management:off

[securitybreach]

Ok it looks like the drivers may be installed. Can you post the output of:

lsmod | grep b3*

[V.T. Eric Layton]

root_Slackware/home/vtel57:# lsmod | grep b3*Module				  Size  Used byi2c_algo_bit			5143  1 radeonfreq_table			  2475  2 cpufreq_ondemand,powernow_k8b43				   178613  0 mac80211			  171226  1 b43cfg80211			  128711  2 b43,mac80211b44					28552  0 ssb					47271  2 b43,b44usbhid				 37516  0 hid					75699  1 usbhidmmc_core			   54106  3 b43,ssb,sdhcipcmcia				 30280  2 b43,ssbrtc_lib				 1922  1 rtc_coreled_class			   2785  2 b43,sdhcimii					 3914  1 b44i2c_core			   18679  6 radeon,drm_kms_helper,drm,i2c_algo_bit,videodev,i2c_piix4battery				 9884  0 dcdbas				  5800  1 dell_laptopbutton				  4922  0

[Urmas]

OK, a couple of slackware/Broadcom threads... I'm "just posting them" because as of now I'm not sure how far you've gotten with this one:Kernel stuff: http://www.linuxques...-6-35-a-827646/WPA supplicant stuff: http://www.linuxforu...slack-13-a.htmlSlackware – Take your cigarette from its holder,And burn your initials in my shoulder.Fracture my spine,And swear that you're mine,As we dance to the masochism tango. EDIT: Looks indeed like the drivers are there, so fuggedabout the first link.

[securitybreach]

Well it looks like the driver is installed and running. Have a look at this wired-and-wireless-networking-interfering-on-dell-inspiron-1300-slackware-13

[Urmas]

What bothers me is that it sees nothing... as user, try:

$ iwlist wlan0 scan

[securitybreach]

Well the link I gave above talks about that specific card having issues with eth0 and wifi interfering with each other. Mainly post #9 on that link http://www.linuxques...85/#post3794057

Quote

I just tried, that was even simpler:1) Add this line at the end of /etc/modprobe.d/blacklist.conf:

b44

2) Add this line at the end of /etc/rc.d/rc.local:

/sbin/modprobe b44

3) Make sure this file be executable:

chmod +x /etc/rc.d/rc.local

No need to restart rc.inet1.And you shouldn't undergo any boot delay, so no need for my stupid scriptSlackware network scripts are really well designed after all

[V.T. Eric Layton]

Reading here. Reading there. Thanks for the help, guys. Stand by...

[Urmas]

Innocent bystanders, that's us...   Methinks Josh has got this licked.

[V.T. Eric Layton]

Before I do anything, I'm going to follow Eric Hameleer's setup on his wiki and see if I can get it to work that way.This may take awhile. I'll be back on here later with the results.Thanks...

[Urmas]

V.T. Eric Layton, on Oct 26 2010, 08:03 PM, said:

This may take awhile.

Says he...    

[securitybreach]

V.T. Eric Layton, on Oct 26 2010, 01:03 PM, said:

Before I do anything, I'm going to follow Eric Hameleer's setup on his wiki and see if I can get it to work that way.This may take awhile. I'll be back on here later with the results.Thanks...

Sounds good. I just got another drive(2tb) so I will be formating partitions, moving data and reinstalling today. Fun fun fun.

[V.T. Eric Layton]

Well, I did everything in Hameleer's tutorial. I configured rc.inet1.conf. I configured wpa_supplicant. No joy. The system doesn't see any wireless anything. :(What now? Suggestions?

[Urmas]

Post #32 by Josh?Thinking out loud here... two separate issues – hardware configuration and connection configuration. And, as per Josh' discovery, you have a possible wired/wireless "collision snafu" that needs to be addressed before the wireless card can see anything.

[onederer]

In a console try: modprobe (your wireless card name); sudo ip link set wlan(#) upsudo iwconfig wlan(#) essid any (name of your network) dhclient wlan(your wireless card #)Then either set IP manually, or get it via DHCPPing gw (router) to see if it is working.See if you get any response with this.  I've used it on the OS's that won't cooperate using any GUI driver version.My card is an Atheros version (ath5k)

[V.T. Eric Layton]

Urmas, on Oct 26 2010, 02:16 PM, said:

Post #32 by Josh?Thinking out loud here... two separate issues – hardware configuration and connection configuration. And, as per Josh' discovery, you have a possible wired/wireless "collision snafu" that needs to be addressed before the wireless card can see anything.

I missed that post somehow. Trying that now.

[V.T. Eric Layton]

Holy Moley Rockin' Rolly!  :bounce:Everything is so easy once you know how to do it. I'm sitting here with my lappy in my lap and communicating with the world wirelessly in my SLACKWARE installation. 'Bout darn time, too. SHEEEESH! Here's how I finally got it working this evening: While I was running some errands earlier this evening, I thought to myself that I ought to read the dmesg output and see if there was anything interesting in there. There was...

Quote

b43 ssb0:0: firmware: requesting b43-open/ucode5.fwb43-phy0 ERROR: Firmware file "b43/ucode5.fw" not foundb43-phy0 ERROR: Firmware file "b43-open/ucode5.fw" not foundb43-phy0 ERROR: You must go to http://wireless.kern...#devicefirmware and download the correct firmware for this driver version. Please carefully read all instructions on this website.

Well, I went to that website mentioned there and learned what a pain in the rectal area Broadcom wireless cards can be when using Linux. A mention of something on that site (b43-fwcutter) reminded me of something I'd read at LQ.org, or somewhere this past couple days, about needing that app to use the proprietary drivers from Broadcom (and you thought Nvidia's install script was a pain, huh?). I did a search for "b43-fwcutter Slackware" and the first hits were the SlackBuilds for this app and for the Broadcom driver. I downloaded both and compiled/installed. While I was following the directions at the wireless.kernel.org site for using fwcutter, I happened to notice the wireless light was already on on my lappy. Hmm... don't know for sure at what stage it started working, but it did. I rebooted... still JOY! MUCH JOY!I want to thank Josh, Urmas, Fran (on IRC), Bob, and everyone else who helped with this fiasco. I'm tired now. I still love Slackware. It can be a challenge sometimes. In this case, I think the problem should be credited to Broadcom, though. Slack would have been relatively easy to set up with any other card. :yes:Off I go...I'm going to power down now. Maybe I'll go sit in my recliner in the bedroom and see how the range is on this thing.

[V.T. Eric Layton]

In recliner in bedroom now. Range good!

[ChipDoc]

It probably works fine at your neighbor's house too.  Congratulations, Eric!  

[V.T. Eric Layton]

I knew I'd get it eventually. It can be frustrating at times, though. 99.9% of what I did was command line, too. That usually turns off most newer Linux adventurers. This latest crop of fresh penguin faces definitely prefers the GUI. There aren't many old command line dogs like me left around these days.

[ChipDoc]

V.T. Eric Layton, on Oct 26 2010, 11:14 PM, said:

I knew I'd get it eventually. It can be frustrating at times, though. 99.9% of what I did was command line, too. That usually turns off most newer Linux adventurers. This latest crop of fresh penguin faces definitely prefers the GUI. There aren't many old command line dogs like me left around these days.

Liking it is one thing.  I like it.  Of course I'm also an OldFart.  But knowing it well enough to actually USE it is quite another.  I think I'm still several weeks away from that point.

[V.T. Eric Layton]

There's command line stuff that I learn every day... and Slackware has been my primary operating system for four years now. Heck, who'm I fooling? I use the command line for most things in all the distros I have installed on my system, not just Slack. I'm a glutton for pain.

[securitybreach]

Awesome!!! Glad you got it working Eric

[V.T. Eric Layton]

Me too!

[securitybreach]

I knew you would get it up and running eventually.