SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
From what I can see both on Google and by looking here http://support.asus.com/download/dow...Language=en-us , there is no Linux driver for that wireless NIC. You will have to try ndiswrapper, which "wraps" the windows driver and tries to use it for Linux. Never had to use NdisWrapper myself, but that will get you started finding the answer.
The mouse is usually a simple edit of /etc/X11/xorg.conf (usually you just add the last line)
***EDIT***
Sorry, just read your other post. Looks like this won't help. My guess is that you will need to choose the right protocol, though I have no idea what that is for your mouse.
***/EDIT***
For sound, as root:
Code:
alsaconf
alsamixer #un-mute the channels and set the volumes
alsactl store
Make sure to read the ndiswrapper documentation, because you need to feed it your Windows driver files (the .INF and .SYS files at a minimum).
After you've configured ndiswrapper, add this line to the end of /etc/rc.d/rc.modules so that ndiswrapper loads at every boot:
Code:
/sbin/modprobe ndiswrapper
Run
Code:
ndiswrapper -l
to check if the driver is installed correctly, and whether your hardware is being detected by ndiswrapper.
i downloaded the latest ndiswrapper from their site before you answered the post...
it installed fine and after half an hour of screwing around, i managed to connect to the network at my house...
then when i tried to use the internet, it worked for a bit, then froze my computer...i couldn't open a new terminal, ctrl-alt-del didn't work etc....i had to turn the comp off at the power. this happened twice
@Alien Bob
if i re-build your package and use your driver, will that stop Slackware from crashing???
and also, will running the ./ndiswrapper.SlackBuild create a package that i can see in the package manager of KDE???
I would suggest not using the latest ndiswrapper. The rc versions are causing a lot of trouble for people. Instead try the 1.2 version (you can get it from the ndiswrapper sourceforge site, just click on the show all files link).
if i re-build your package and use your driver, will that stop Slackware from crashing???
and also, will running the ./ndiswrapper.SlackBuild create a package that i can see in the package manager of KDE???
You can use the ndiswrapper.SlackBuild script to build any other version of ndiswrapper that you download, as long as you edit the VERSION variable that is inside that script, so that it matches the version of the ndiswrapper source tarball.
I.e. when you download ndiswrapper-1.2.tar.gz (as suggested by Hangdog42 because 1.4rc1 might be too unstable), you change
Code:
VERSION=1.4rc1
to
Code:
VERSION=1.2
and then start the script.
I never used KDE's graphical package manager, but I assume it will be able to handle the package you create with the script, because it is a normal Slackware package like all the others on the Slackware CD's.
I got my wireless working by using ndiswrapper. I compiled from scratch and built it around the drivers on the CD that came with the card following the instructions that are on the ndiswrapper page. It was pretty straight forward, and once I finished everything it worked flawlessly.
Still haven't got around to setting up WPA though, but I guess WEP is better than nothing, and it was easier to get setup properly.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.