60 replies to this topic

[V.T. Eric Layton]

I've spent the entire afternoon and evening trying to get my lappy to "see" my new wireless network in Slackware. I give up.

[securitybreach]

Can you give us some more details? Whats going on?

[sunrat]

Wireless card? Driver? Tried WICD?

[V.T. Eric Layton]

No network detected by wicd. No changes to wicd settings do anything. No decent instructions ANYWHERE online about modifying Slack's /etc/rc.d -> rc.inet1.conf rc.wireless.conf or rc.wpa_supplicant.conf.*sigh*Tired now.

[sunrat]

I hate wireless problems. Ceni works well in aptosid but I could never get my head around setting up roaming.

[securitybreach]

Can you post the output of lspci?

[V.T. Eric Layton]

Well... being that it's Slackware, which is designed specifically for sadistic, self-flagellating idiots who like PAIN and aggravation; it's never something simple.  

[securitybreach]

Yeah I was a Slacker for a few years so I know but this is probably just a module issue.

[V.T. Eric Layton]

root_Slackware/home/vtel57:# lspci00:00.0 Host bridge: ATI Technologies Inc RS690 Host Bridge00:01.0 PCI bridge: ATI Technologies Inc RS690 PCI to PCI Bridge (Internal gfx)00:05.0 PCI bridge: ATI Technologies Inc RS690 PCI to PCI Bridge (PCI Express Port 1)00:07.0 PCI bridge: ATI Technologies Inc RS690 PCI to PCI Bridge (PCI Express Port 3)00:12.0 SATA controller: ATI Technologies Inc SB600 Non-Raid-5 SATA00:13.0 USB Controller: ATI Technologies Inc SB600 USB (OHCI0)00:13.1 USB Controller: ATI Technologies Inc SB600 USB (OHCI1)00:13.2 USB Controller: ATI Technologies Inc SB600 USB (OHCI2)00:13.3 USB Controller: ATI Technologies Inc SB600 USB (OHCI3)00:13.4 USB Controller: ATI Technologies Inc SB600 USB (OHCI4)00:13.5 USB Controller: ATI Technologies Inc SB600 USB Controller (EHCI)00:14.0 SMBus: ATI Technologies Inc SBx00 SMBus Controller (rev 14)00:14.1 IDE interface: ATI Technologies Inc SB600 IDE00:14.2 Audio device: ATI Technologies Inc SBx00 Azalia (Intel HDA)00:14.3 ISA bridge: ATI Technologies Inc SB600 PCI to LPC Bridge00:14.4 PCI bridge: ATI Technologies Inc SBx00 PCI to PCI Bridge00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control01:05.0 VGA compatible controller: ATI Technologies Inc RS690M [Radeon X1200 Series]03:00.0 Ethernet controller: Broadcom Corporation BCM4401-B0 100Base-TX (rev 02)03:01.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 05)03:01.1 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 22)03:01.2 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 12)03:01.3 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev 12)0b:00.0 Network controller: Broadcom Corporation BCM4311 802.11b/g WLAN (rev 01)

[securitybreach]

Look at this Eric: http://www.linuxques...om-wifi-822046/

[amenditman]

Definitely a module problem.I had the same issue with every Broadcom based wifi chip I have ever used.wicd doesn't care much about the config stuff, if the module is installed and loaded, the interface is 'up', it does the rest including the roaming stuff.

[V.T. Eric Layton]

Yeah...  I was reading that thread over there while you were posting the link. I'll see what the driver will do.

[securitybreach]

Sounds good, let us know

[V.T. Eric Layton]

Well, urinate on it... that broadcom-sta SlackBuild isn't compiling. I'm going to bed now.

[securitybreach]

V.T. Eric Layton, on Oct 25 2010, 11:46 PM, said:

Well, urinate on it... that broadcom-sta SlackBuild isn't compiling. I'm going to bed now.

We will figure out something tomorrow or you could always put Arch on it http://wiki.archlinu...eless_Setup#b43

[LilBambi]

Oh, joy... another broadcom ....0b:00.0 Network controller: Broadcom Corporation BCM4311 802.11b/g WLAN (rev 01)Well, there's always usb wireless gizmos...

Quote

802.11 Linux STA driverThese packages contain Broadcom's IEEE 802.11a/b/g/n hybrid Linux® device driver for use with Broadcom's BCM4311-, BCM4312-, BCM4313-, BCM4321-, and BCM4322-based hardware. There are different tars for 32-bit and 64-bit x86 CPU architectures. Make sure that you download the appropriate tar because the hybrid binary file must be of the appropriate architecture type. The hybrid binary file is agnostic to the specific version of the Linux kernel because it is designed to perform all interactions with the operating system through operating-system-specific files and an operating system abstraction layer file. All Linux operating-system-specific code is provided in source form, making it possible to retarget to different kernel versions and fix operating system related issues.NOTE: You must read the LICENSE.TXT file in the lib directory before using this software.Support questions for the latest version of these drivers may be directed to linux-wlan-client-support-list@broadcom.com.802.11 Linux STA

@broadcom site

[Urmas]

Dear "Wired in Tampa",Give us the output of...

~$ lspci -vvnn | grep 14e4

(https://help.ubuntu..../Driver/bcm43xx)

[Urmas]

V.T. Eric Layton, on Oct 26 2010, 05:38 AM, said:

Well... being that it's Slackware, which is designed specifically for sadistic, self-flagellating idiots who like PAIN and aggravation; it's never something simple.  

Um... isn't that sorta kinda the whole idea?

[onederer]

V.T. Eric Layton, on Oct 25 2010, 10:38 PM, said:

Well... being that it's Slackware, which is designed specifically for sadistic, self-flagellating idiots who like PAIN and aggravation; it's never something simple.  

Slack has never been known to be gentle! That's why I don't mess with it. To me, it feels too primitive.  From my experience, there are probably at most, no more than an handful of distros which are  really wireless friendly.  Those are the ones that I've had to stick with. Currently, I'm writing this with PCLOS/KDE.  It is no problem to use any distro when only CAT-5 cable networking is needed.  But if you want to tear your hair out, go ahead and try other distros.  I'd be glad to find out which ones that work that I haven't tackled in the past. I don't know if you remember this, but I've put out several posts in the past about this. It took me a very long time to find what works.  To my recollection, DESKTOPBSD, Freespire, PCLOS, are the ones that worked without a single sweat.  The others were a tough wrestling match.Cheers!

[V.T. Eric Layton]

@ Fran... Those are the same drivers that I was trying to compile from SlackBuild. I could compile them from source and install directly, I s'pose. It's the "Slack Way". @ Urmas... Memo from Wired in Tampa:I'm not on that system at this time. I'll post that requested data later. @ Onederer... UG! *thumping chest* ME LIKE Slackware!

[onederer]

V.T. Eric Layton, on Oct 26 2010, 09:37 AM, said:

@ Fran... Those are the same drivers that I was trying to compile from SlackBuild. I could compile them from source and install directly, I s'pose. It's the "Slack Way". @ Urmas... Memo from Wired in Tampa:I'm not on that system at this time. I'll post that requested data later. @ Onederer... UG! *thumping chest* ME LIKE Slackware!

U LIKE PAIN! eh?  Me no like missing dependencies hunting!  Make big headache!

[V.T. Eric Layton]

Urmas, on Oct 26 2010, 12:33 AM, said:

Dear "Wired in Tampa",Give us the output of...

~$ lspci -vvnn | grep 14e4

(https://help.ubuntu..../Driver/bcm43xx)

root_Slackware/home/vtel57:# lspci -vvnn | grep 14e403:00.0 Ethernet controller [0200]: Broadcom Corporation BCM4401-B0 100Base-TX [14e4:170c] (rev 02)0b:00.0 Network controller [0280]: Broadcom Corporation BCM4311 802.11b/g WLAN [14e4:4311] (rev 01)

[securitybreach]

Well you could try the official one from Broadcom: http://www.broadcom....1/linux_sta.phpYou will have compile it and insert the modules but should work fine on Slackware.

[LilBambi]

V.T. Eric Layton, on Oct 26 2010, 09:37 AM, said:

@ Fran... Those are the same drivers that I was trying to compile from SlackBuild. I could compile them from source and install directly, I s'pose. It's the "Slack Way".

That would be a good idea. There have been many times when JL has had to compile drivers/driver modules from source because of this type of thing.

[Urmas]

OK... will see what I can come up with...what is the output of "iwconfig" ?