Wirless driver for Puppy 202 with rtl8180
Wirless driver for Puppy 202 with rtl8180
Here's the rtl8180 driver for Puppy 202, patched for injection. Just click module_load to load the modules.
- Attachments
-
- rtl8180.tar.gz
- (61.48 KiB) Downloaded 355 times
- Sit Heel Speak
- Posts: 2595
- Joined: Fri 31 Mar 2006, 03:22
- Location: downwind
Thank you!
Just what I needed, works great with my rtl8180 based Topcom skyracer pc card 4011b.
How would I make this load automatically at boot?
I have tried adding some lines in rc.local but I am not getting it to work.
Being a linux noob, it would be great if someone could spell it out for me...
Thanks in advance.
Just what I needed, works great with my rtl8180 based Topcom skyracer pc card 4011b.
How would I make this load automatically at boot?
I have tried adding some lines in rc.local but I am not getting it to work.
Being a linux noob, it would be great if someone could spell it out for me...
Thanks in advance.
Add this to /etc/rc.d/rc.localHow would I make this load automatically at boot?
insmod /path-to-modules/ieee80211_crypt-r8180.ko
insmod /path-to-modules/ieee80211_crypt_wep-r8180.ko
insmod /path-to-modules/ieee80211-r8180.ko
insmod /path-to-modules/r8180.ko
ifconfig wlan0 up
Replace "/path-to-modules/" with the path to where you put them.
For example:
insmod /root/rtl8180-pup202/ieee80211_crypt-r8180.ko
When I insmod (or modprobe) these in 2.02, I get a "can not find module error;" however, everything works fine when I run the load_module script. Out of curiosity, why would this occur? The commands I type into the console match exactly the script except for the #!/bin/bash thing (whatever that does).
Probably because your not in the same directory as the modules when you try to load them. You need to cd to the directory that contains the modules then insmod them or give the path to them. For example, insmod /root/rtl8180/rtl8180.ko, that's not the correct names but you get the point.When I insmod (or modprobe) these in 2.02, I get a "can not find module error;" however, everything works fine when I run the load_module script. Out of curiosity, why would this occur? The commands I type into the console match exactly the script except for the #!/bin/bash thing (whatever that does).
You're right. What I did was, after extracting the tarball to .../net/wireless/rtl8180-pup202, I moved everything to the parent directory (.../net/wireless/) and then tried to insmod. This didn't work. After running insmod from the original rtl8180-pup202 directory everything was extracted to and not trying to move anything, it all worked fine. Thanks for the help.