yes i do have a usb somewhere but im going to try lan to send the info i just have to get a cat5 from work. if that doesnt work and i cant find my flash drive then i will go buy a new one cause thats just way to much stuff to type and write.

Have a quick look at the output from "dmesg" and see if the wireless is looking for a firmware.

If it is you might need to extract it with "fwcutter" (have a google for it) and put the firmware in /lib/firmware.

You might find this all a lot easier if you install "wicd" from /extra. Just make sure you follow the instructions to the letter and you should be on your way.

here is lspci and lsusb

root@darkstar:~# lspci
00:00.0 Host bridge: Advanced Micro Devices [AMD] RS780 Host Bridge Alternate
00:01.0 PCI bridge: Advanced Micro Devices [AMD] RS780 PCI to PCI bridge (int gfx)
00:05.0 PCI bridge: Advanced Micro Devices [AMD] RS780 PCI to PCI bridge (PCIE port 1)
00:06.0 PCI bridge: Advanced Micro Devices [AMD] RS780 PCI to PCI bridge (PCIE port 2)
00:11.0 SATA controller: ATI Technologies Inc SB700/SB800 SATA Controller [AHCI mode]
00:12.0 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller
00:12.2 USB Controller: ATI Technologies Inc SB700/SB800 USB EHCI Controller
00:13.0 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller
00:13.2 USB Controller: ATI Technologies Inc SB700/SB800 USB EHCI Controller
00:14.0 SMBus: ATI Technologies Inc SBx00 SMBus Controller (rev 42)
00:14.2 Audio device: ATI Technologies Inc SBx00 Azalia (Intel HDA) (rev 40)
00:14.3 ISA bridge: ATI Technologies Inc SB700/SB800 LPC host controller (rev 40)
00:14.4 PCI bridge: ATI Technologies Inc SBx00 PCI to PCI Bridge (rev 40)
00:14.5 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI2 Controller
00:16.0 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller
00:16.2 USB Controller: ATI Technologies Inc SB700/SB800 USB EHCI Controller
00:18.0 Host bridge: Advanced Micro Devices [AMD] K10 [Opteron, Athlon64, Sempron] HyperTransport Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K10 [Opteron, Athlon64, Sempron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K10 [Opteron, Athlon64, Sempron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K10 [Opteron, Athlon64, Sempron] Miscellaneous Control
00:18.4 Host bridge: Advanced Micro Devices [AMD] K10 [Opteron, Athlon64, Sempron] Link Control
01:05.0 VGA compatible controller: ATI Technologies Inc M880G [Mobility Radeon HD 4200]
01:05.1 Audio device: ATI Technologies Inc RS880 Audio Device [Radeon HD 4200]
02:00.0 Network controller: Broadcom Corporation Device 4727 (rev 01)
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02)
root@darkstar:~# lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 064e:f203 Suyin Corp.
Bus 001 Device 003: ID 0930:6545 Toshiba Corp. Kingston DataTraveler 2.0 Stick (4GB) / PNY Attache 4GB Stick
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 0bda:0158 Realtek Semiconductor Corp. USB 2.0 multicard reader
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
root@darkstar:~#

Your wifi device seems to be from a manufacturer "Broadcom" Device 4727 (rev 01).

If you know how to build slackbuilds, I would recommend to try installing broadcom-sta from slackbuilds for your version of slackware:

http://slackbuilds.org/result/?search=broadcom&sv=

I would also recommend promoting open-source compatible devices and to not encourage proprietory hardware providers (i.e. don't buy from them - don't support them - they will not provide support for you) - Broadcom do however provide a linux module for their wifi devices but you must read/accept their license for legal use/purposes.

Their source for their module is here:
http://www.broadcom.com/support/802.11/linux_sta.php

but best to stick to a slackbuild

I have never used a broadcom device so cannot provide you 100% guidance but this is the next step I would take.

edit:
once you have installed the slackbuild I would strongly recommend using 'wicd' from the './extra' directory from your slackware install disk (or online repository e.g. http://slackware.osuosl.org)

You can run 'wicd' from terminal/run command box by typing 'wicd-client' or just searching and selecting it from your menu in your desktop environment.

This is because your system currently has no support for your wifi device. Otherwise you would see 'wlan0' in the above list (that can differ but rarely).

Your system probably has no native module/driver for this hardware - as soon as the 'correct/right' module is installed you will see 'wlan0' in that list by typing iwconfig.

I had troubles initially with wifi and this link helped me but I am just a newbie: http://genek.net/LinuxAdventures/installsetup/wicd.html

ok i got a question dh2k. i went to that slackbuild link and do i download the source and slackbuild? im not familiar with slackware. im very new to it. the other problem is im not on the computer that actually has slackware on it so when i download can i put it on a flash drive? then put it on the other computer?

hello again im haveing trouble building the package i downloaded it put it on the computer with slackware and i cant figure out how to use make i tried the man pages and slackwiki on how to build a package it says. make install DESTDIR=/tmp/build is there somewhere that..... what i really need is an example what im putting in is make -f makefile wicd=/tmp/build is this correct cause its not working i dont really know how to explain it i guess i dont know what to put in the blanks or really where to begin???????? thanks

Here is the instructions on how to use a slackbuild.

make sure if
cat /sys/class/rfkill/*/state
give you 1, where
cat /sys/class/rfkill/*/type
is wlan
if not: echo 1 > /sys/class/rfkill/*/state

the other problem, my wlan0 up and running ( if configured static ip), but network unrechable
and if configured by dhcp, not get ip
what is wrong?

Try
lsmod | grep pcmcia

to see what, if any, modules are loaded and used by pcmcia

ok i tried chmod +x broadcom-sta.slackbuild and the error was no file or directory that site doesnt give much info like slackwiki but i cant do that either? make install doesnt work the error message for that is no rule target? i havent seen any of that on the info i have found and recieved oh and another thing if you look at some of the threads each instructions i was given is different one says to use makeinstall to install that into the /tmp/build this one you gave me says to use chmod so im really lost now????? the man pages of chmod is no more helpful what i mean by that is i dont speak computer geek which i hope nobody takes that the wrong way i just dont know the slang yet. So what does it mean by script? what script? I looked at the files and i didnt see anything with a script unless its called something else thanks

so I can provide more info about building aslackbuild software package - could you please confirm the version of slackware you are using?

If you are not sure - then from a terminal/command line please enter:

Here is a very quick - and brief - slackbuild guide:

1>
download the slackbuild -
and source files

They contain folder(s) and files archived and compressed for convenient downloading (commonly referred to as, slang: 'tarballed', commonly with .tar.gz extension)

2>
decompress and extract the slackbuild using the right click menu using a dolphin or konqueror file-managers (or any other file-manager you wish to use)

or from a termimnal:
(the switches/options above, -zxvf
- unzipped the tarball -z
- extract the tarball -x
- give us feedback on screen, verbosely -v
- do all this on the filename given -f)


3>
move the source file into the extracted slackbuild directory

4>
from a terminal as root user build the slackbuild package
if this does not build then try making the file executable, as normal user,

Code:

chmod +x app-name-.Slackbuild

THIS IS NOT ALWAYS NECESSARY as most slackbuilds should already be executable - warning - some are not but in my experience only very few.

5>
install the package
when package has built you will see the software-package in /tmp, something like this will be displayed
to be more exact something similar to this
as root user:
done. - feel free to delete the source and slackbuild and source, compressed and also extracted folders/files, if you want - it is not necessary to keep them.

This is a very brief guide to building slackbuild software packages. Please refer to other links above in this thread for more scope on this subject if required.





so to summarise:
1> download the slackbuild -
and source files
2> decompress and extract the slackbuild
3> move the source file into the extracted slackbuild directory
4> build the slackbuild package
5> install the package

It is case sensitive, try "broadcom-sta.Slackbuild" (uppercase S)

or even better "./bro" then hit the tab key (autocompletes - a great tip and you may wonder why you never heard of it sooner)

if there are 2 or more possibilites then double tap the tab key and it will list the possible autocomplete options.

Can be used anywhere - and so, so useful. Saves having to get things absolutely correct - makes command line a lot more user friendly.



Forget make, make install etc - thats installing from source - and rather advanced. There are much more user friendly options available for you - google src2pkg for an example - but again a bit beyond the scope of what you need just yet.


Creating a slackware software package using a slackbuild script is not the same as installing from source.

A slackbuild is simply a script which uses the software source to create an installable software package which is incredibly maintainable/manageable for a slackware system.
(software source which is in the same directory as a slackbuild script specific to the each other,
so you cannot use any slackbuild script with any software source)

By default the software package is always created in "/tmp/package-name.txz"

Then just install this package as root user