Question about Debian to Slackware guide

Anonymo · 06-07-2006, 11:24 PM

I have the usb adapter listed here in this article

http://funcation.blogspot.com/

will it work with Slackware if it is written for Debian?

Code:

 Linksys WUSB54GC Wireless USB Adapter -- install on Debian 2.6.8 kernel
Most of this info came from posts on Ralinktech.com forums

    * my base system consisted of a "minimal" debian install from debian-31r1-i386-netinst.iso
    * apt-get install kernel-source-2.6.8 kernel-headers-2.6.8-2-386 unzip gcc-3.4 gcc make wireless-tools

    * cd /usr/src
    * tar -xvjf kernel-source-2.6.8.tar.bz2
    * mv kernel-source-2.6.8 linux-2.6.8
    * get linux driver from RaLink web site

      wget http://www.ralinktech.com/drivers/Linux/RT73_Linux_STA_Drv1.0.3.0.tar.gz

    * tar -xvzf RT73_Linux_STA_Drv1.0.3.0.tar.gz
    * cd RT73_Linux_STA_Drv1.0.3.0/Module
    * cp Makefile.6 Makefile
    * vi /usr/src/RT73_Linux_STA_Drv1.0.3.0/Module/rtmp_def.h

      ... after the #define RTVID3 and RTPID3 lines insert:
       
      #define RTVID4              0x13b1                 // Linksys WUSB54GC
      #define RTPID4              0x0020

      ... after the "{USB_DEVICE(RTVID3,RTPID3)}, \" line insert:

       {USB_DEVICE(RTVID4,RTPID4)}, \

      ... save and exit
      wq!

    * make

    * cp rt73.ko /lib/modules/2.6.8-2-386/kernel/drivers/net/wireless/
    * insmod /lib/modules/2.6.8-2-386/kernel/drivers/net/wireless/rt73.ko
    * depmod -a
    * modprobe rt73 (should be redundant ?)

    * vi /etc/modprobe.conf

      alias rausb0 rt73

    * vi /etc/network/interfaces

      auto rausb0
      iface rausb0 inet static
        address 192.168.0.20
        netmask 255.255.255.0
        gateway 192.168.0.1
        broadcast 192.168.0.255
      up sh /etc/network/do_wep &

    * vi vi /etc/network/do_wep

      #!/bin/sh
      ifconfig rausb0 up
      iwconfig rausb0 essid eeeeeee key restricted xxxxxxx nick nnnnnnn
      ifup rausb0

    * chmod 755 /etc/network/do_wep
    * /etc/init.d/networking restart

cwwilson721 · 06-07-2006, 11:37 PM

Personally, I would go to the serialmonkey site, and see if one of their drivers will work. (I had horrible luck with ralink. Not saying it won't work, but I had better luck with serialmonkey's drivers)

Either way, get the driver, read the documentation for whatever driver you get, and compile/install it. Don't rely on Debian install instructions, the one's on the driver sites are the ones you need.

Anonymo · 06-08-2006, 09:34 PM

I am going to try the 2570 driver

make
checkinstall

the module is what i am going to do?

how do I manually mount the adapter?

cwwilson721 · 06-08-2006, 10:02 PM

Have card inserted

Then

Code:

modprobe rt2570
/etc/rc.d/rc.inet1 ra0_start

(Assuming ra0 is the interface. To check which it is, type 'iwconfig')

After the 'start' command above, type 'ifconfig'
If there is no DHCP address on the interface, type 'dhcpcd ra0'

To make it come up at boot, edit /etc/rc.d/rc.inet1.conf, and edit the settings for your card.

Bruce Hill · 12-18-2006, 06:02 PM

Just found this post in a search, and thought I'd add some information.

My customer has a TP-LINK TL-WN321G Wireless USB Adapter.

He is running Ubuntu 6.06 TLS (Dapper Drake) and following the Ubuntu wiki instructions he couldn't get it to work. He was also using ndiswrapper. So, I decided to see if I could get it to work with Slackware. (If it doesn't work with Slackware, it's a candidate for /dev/null IMO.)

Specs:

Code:

mingdao@titus:~$ cat /etc/slackware-version 
Slackware 11.0.0
mingdao@titus:~$ uname -a
Linux titus 2.6.18.1 #5 PREEMPT Tue Oct 31 06:35:31 CST 2006 i686 pentium4 i386 GNU/Linux

The driver from Ralink you mentioned, and their instructions, didn't seem right (nor did they work for me).

I had also downloaded the driver from serialmonkey and was reading it's README file when Alien Bob suggested it. That was enough for me.

Easy as falling off a horse. These are simple instructions taken from my .bash_history files:

Code:

1 - mkdir -p ~/build/ralink/ && cd ~/build/ralink/ (I did everything from here)
2 - wget http://rt2x00.serialmonkey.com/rt73-cvs-daily.tar.gz
3 - tar xvvf rt73-cvs-daily.tar.gz
4 - cd rt73-cvs-2006121815/Module/
5 - make
6 - su
Password: (everything else is to be done as root)
7 - make install
8 - modprobe rt73
9 - vim /etc/rc.d/rc.inet1.conf (edit for rausb0)
10 - /etc/rc.d/rc.inet1 rausb0_start

When you install the driver, it writes "alias ra0 rt73" to /etc/modprobe.d/modprobe.conf. I changed it to "alias rausb0 rt73" and rebooted; and it works just fine.

I wanted to add this addition:

Code:

root@titus:~# iwconfig rausb0
rausb0    RT73 WLAN  ESSID:"<munged>"  Nickname:"titus"
          Mode:Managed  Frequency=2.457 GHz  Access Point: <munged>   
          Bit Rate=54 Mb/s   
          RTS thr:off   Fragment thr:off
          Encryption key:off
          Link Quality=58/100  Signal level:-74 dBm  Noise level:-107 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

cwwilson721 · 12-19-2006, 02:44 PM

I love serialmonkey.

BTW, try the RutilT utility (Link is on the serialmonkey download page. IMNHO it works better/more than the one included...)

Bruce Hill · 12-19-2006, 06:34 PM

My little tutorial is for the RT73 driver. I assume the utility does not
work for that one, since I read this from the serialmonkey downloads page:

Quote:

Downloads

From Rt2x00Wiki

We currently are hosting all of our source downloads from Sourceforge. You can find the latest source packages below. We currently are not offering any binary packages

Latest BETA rt2400 driver: v1.2.2-b3

Latest BETA rt2500 driver: v1.1.0-b4

Latest BETA rt2570 driver: v1.1.0-b2

Latest BETA rt61 driver: v1.1.0-b1

A full history of our source releases can be found in our SourceForge projects files repository.

A Graphical Utility is available to configure the drivers above: RutilT download

For those that want to stay on the "bleeding edge" then you can get nightly CVS tarballs of our repository below. These tarballs are generated every hour.

If the tarballs are empty then that means SourceForge CVS is currently having problems. Please try again later

rt2400 PCI/PCMCIA nightly CVS tarball: rt2400-CVS

rt2500 PCI/PCMCIA nightly CVS tarball: rt2500-CVS

rt2570 USB nightly CVS tarball: rt2570-CVS

rt61 PCI/PCMCIA nightly CVS tarball: rt61-CVS

rt73 USB nightly CVS tarball: rt73-CVS

rt2x00 nightly CVS tarball: rt2x00-CVS - EXPERIMENTAL !!!!

Have you tried RutilT with RT73?

Another reason is that I don't use the mouse when the kbd is available.

cwwilson721 · 12-19-2006, 07:55 PM

AFAIK, it will work with 90% of wireless devices.

It just has "extra" stuff for ralink chips.

Heres the link

Arkerless · 02-03-2007, 01:16 AM

Quote:

Originally Posted by Bruce Hill

Just found this post in a search, and thought I'd add some information.

I just tried this on slackware 11. With the cvs from serialmonkeys, and with the beta driver from the other website, both are flunking out for me at the make stage. I have this wierd feeling I should know what this means, but for the life of me I can't quite remember it. Any pointers?

~/build/ralink/rt73-cvs-2007020300/Module$ make
make[1]: Entering directory `/usr/src/linux-2.4.33.3'
gcc -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -o scripts/split-include scripts/split- include.c
/usr/lib/gcc/i486-slackware-linux/3.4.6/../../../../i486-slackware-linux/bin/ld: cannot open output file scripts/split-include: Permission denied
collect2: ld returned 1 exit status
make[1]: *** [scripts/split-include] Error 1
make[1]: Leaving directory `/usr/src/linux-2.4.33.3'
rt73.o failed to build!
make: *** [module] Error 1

The directories all seem to have the correct permissions set, so why am I getting permission denied? This is a fresh install with almost nothing added to it.

H_TeXMeX_H · 02-03-2007, 12:20 PM

Run this as root then try again:

Code:

chmod -R a+rwx,go-w /usr/src/linux-2.4.33.3

cwwilson721 · 02-03-2007, 12:40 PM

I ALWAYS make/install the driver as root, never had an issue. But the one time I tried as user....

H_TeXMeX_H · 02-03-2007, 01:00 PM

Quote:

Originally Posted by cwwilson721

I ALWAYS make/install the driver as root, never had an issue.

Yeah, you could do that too. (usually I make it as user and install as root)

Arkerless · 02-04-2007, 11:20 PM

Quote:

Originally Posted by H_TeXMeX_H

Run this as root then try again:

Code:

chmod -R a+rwx,go-w /usr/src/linux-2.4.33.3

I tried this, as root, and then exited and tried make again. Same error

I really don't want to be running make as root, but I also really want to get this driver working, so I did it. Hope I don't regret it. Shouldn't ever be necessary to be root to compile I thought.

Anyhow, seems to be working. Thanks all.