|
||||||
| Forums FAQ | Members List | Search | Today's Posts | Mark Forums Read |
| Hardware Questions about drivers, peripheral cabling, configuration |
![]() |
|
|
|
LinkBack | Thread Tools | Display Modes |
|
|||
|
so i have finally found the right driver for my rtl8187b wireless card (i used this link "What I did on my vacation from reality » RTL8187B drivers and patches")
but now this is what i must do every time i login! Code:
su Code:
cd /home/tj/rtl8187b-modified Code:
./wlan0up in Ubuntu i could add this to my /etc/rc.local Code:
/home/tj/rtl8187b-modified/wlan0up ifconfig wlan0 up dhclient wlan0 exit 0 so my question is what can i do to make my wireless start automatically? is there another file that i can add those lines to? |
|
|||
|
i don't see the knetworkmanager anywhere in yast package manager
is it availible for gnome? |
|
||||
|
You need to use the gnome equiv..
NetworkManager-gnome
__________________
Box: Linux 2.6.27.25-170.2.72 i686 PAE | Fedora 10 | KDE4.2.4 | M2N4-SLI | AMD 64 X2 5200+ | nVidia 8500GT | 4GB RAM Lap: openSUSE 11.1 | Celeron 550 | (KDE4.2.95)"139" RC1 | Intel 965 GM | Lenovo R61e | 3GB RAM |
|
|||
|
ok i dont think this idea is going to work
my network manager is already configured to auto connect and everything the problem is that wlan0 isnt even recognized as a device until after i run the ./wlan0up script heres the contents of wlan0up Code:
#!/bin/bash if test "`dirname $0`" != "."; then cd `dirname $0` fi SYSTEM=`uname -r|cut -d. -f1,2` if [ $SYSTEM = 2.4 ] then cd ieee80211 insmod ieee80211_crypt-rtl.o insmod crypto-rtl.o insmod michael_mic-rtl.o insmod aes-rtl.o insmod ieee80211_crypt_wep-rtl.o insmod ieee80211_crypt_tkip-rtl.o insmod ieee80211_crypt_ccmp-rtl.o insmod ieee80211-rtl.o cd ../rtl8187 insmod r8187.o else cd ieee80211/ insmod ieee80211_crypt-rtl.ko insmod ieee80211_crypt_wep-rtl.ko insmod ieee80211_crypt_tkip-rtl.ko insmod ieee80211_crypt_ccmp-rtl.ko insmod ieee80211-rtl.ko cd ../rtl8187/ insmod r8187.ko $@ fi cd ../ |
|
||||
|
Quote:
Also, check in Yast that you have it ticked to start at boot
__________________
Drop in and visit some time. |
|
|||
|
it worked!
thank you |
|
|||
|
Ok i spoke too soon
today i rebooted my computer and i noticed that the boot time is outrageously long i booted with with no splash so i could see what was happening as soon as /etc/init.d/boot.local gets loaded there are a bunch of lines that look like this DHCP Request blah blah blah blah DHCP Request blah blah blah blah DHCP Request blah blah blah blah DHCP Request blah blah blah blah DHCP Request blah blah blah blah DHCP Request blah blah blah blah DHCP Request blah blah blah blah DHCP Request blah blah blah blah (blah blah blah blah is actuall like adresses and stuff obviously) (i dont have a digital camera so i cant get a picture) then after about 40-60 seconds it will say DHCP failed and it will continue to boot when it finishes loading up the desktop my wireless works fine (it just sucks that it takes an extra minute to boot, and its not necessary) so what can i do now? i have heard something about moving the modules into a certain directory so that they get loaded automatically but how would i go about doing this? and how would i get ifconfig wlan0 up and dhclient wlan0 to run? |
|
||||
|
See what happens if you change the setting from "start at boot" to "start manually" but leave the "ifup wlan0" line in /etc/init.d/boot.local.
I'm hoping the line "ifup wlan0" will trigger all that dhcp stuff at a later time, although I'm really not sure -- try it.
__________________
Drop in and visit some time. |
![]() |
|
| Bookmarks |
| Thread Tools | |
| Display Modes | |
|
|