How to use Realtek RTL8192EU USB Wireless?
@rcrsn51: Finally after a month and a half of trying everything I could think of, except of course the exact pet package I needed for "my" kernel, my wireless is up and running(the cd that comes with those adapters with what they say are linux drivers is useless if you have Puppy). Using the pet package you made, it took me less than 5 minutes from start of install to completion. rcrsn51, sir, thank you for taking the time out of your life to not only teach me something, but to write the pet package I needed. I appreciate it more than I could ever describe in a sentence.
Regards
mtzlplex
Regards
mtzlplex
Excellent. Thank you to both mtzlplex and MarcHoppe for staying with this exercise. I now have a good idea of how to build this driver for other Puppies.
For interested observers, the rtl8192eu source code is from here.
For interested observers, the rtl8192eu source code is from here.
Yes I second your gratitude towards rcrsn51 !
Anyway just as an update, this morning after a cold boot and subsequent reboot I've had to manually re-connect my wireless interface. It's not hard to do and only takes a minute but perhaps I've done something wrong and forgot to save something or forgot to set something to "automatic". I'll keep poking around and see if I can find a solution...
Anyway just as an update, this morning after a cold boot and subsequent reboot I've had to manually re-connect my wireless interface. It's not hard to do and only takes a minute but perhaps I've done something wrong and forgot to save something or forgot to set something to "automatic". I'll keep poking around and see if I can find a solution...
There are many reports of Puppy WiFi connection managers that "forget" their settings.
Look at PeasyWiFi. It never forgets.
Look at PeasyWiFi. It never forgets.
Ok I've installed Peasy WiFi 3.7 and have attempted to set up a connection. Here's what I get (password xxxx out not that it would matter since no one here is in range):
ctrl_interface=/var/run/wpa_supplicant
ap_scan=1
update_config=1
network={
ssid="NETGEAR65"
scan_ssid=1
psk="XXXXXXX"
proto=WPA2
key_mgmt=WPA-PSK
pairwise=CCMP TKIP
group=CCMP TKIP
}
Unfortunately connection has failed each time. Profile would appear to be set up properly but obviously I'm doing something wrong. I am able to get reconnected by using Simple Network Setup so the network is up. I'll keep working at it but Peasy WiFi seems to be pretty straight forward...not too sure what I've missed.
ctrl_interface=/var/run/wpa_supplicant
ap_scan=1
update_config=1
network={
ssid="NETGEAR65"
scan_ssid=1
psk="XXXXXXX"
proto=WPA2
key_mgmt=WPA-PSK
pairwise=CCMP TKIP
group=CCMP TKIP
}
Unfortunately connection has failed each time. Profile would appear to be set up properly but obviously I'm doing something wrong. I am able to get reconnected by using Simple Network Setup so the network is up. I'll keep working at it but Peasy WiFi seems to be pretty straight forward...not too sure what I've missed.
From the Config Button:
export INTERFACE=wlan0
export TIMEOUT=0
export DRIVER=8192eu
export PROFILEPATH=/etc/pwf/wifi
export OPTION=""
export STATIC=""
export GATEWAY=""
Status:
IP on wlan 0:192.168.1.1
Quality = 100/100
Kernel Mode 8192eu
WPA Supplicant COMPLETED
Everything appears to be correct. IP Address is correct. I'll try to connect again this morning. Like I said I am able to connect by using Simple Network Setup and am connected through there now,
export INTERFACE=wlan0
export TIMEOUT=0
export DRIVER=8192eu
export PROFILEPATH=/etc/pwf/wifi
export OPTION=""
export STATIC=""
export GATEWAY=""
Status:
IP on wlan 0:192.168.1.1
Quality = 100/100
Kernel Mode 8192eu
WPA Supplicant COMPLETED
Everything appears to be correct. IP Address is correct. I'll try to connect again this morning. Like I said I am able to connect by using Simple Network Setup and am connected through there now,
No. Leave that entry as "wext". This "driver" is wpa_supplicant's internal driver, not the WiFi adapter's driver.MarcHoppe wrote:export DRIVER=8192eu
Are you getting a green "connected" message from PWF?
Usually, 192.168.1.1 would be the IP address of your router, not one that would be given to a client.
Check the file /etc/resolv.conf. Does it contain a valid "nameserver" line?
In what way is the connection failing? Try the command: ping 8.8.8.8
Last edited by rcrsn51 on Wed 16 Mar 2016, 16:08, edited 3 times in total.
No. or at least I don't see any green connected messagercrsn51 wrote: Are you getting a green "connected" message from PWF?
It's actually .2 not .1 on the end.rcrsn51 wrote:Usually, 192.168.1.1 would be the IP address of your router, not one that would be given to a client.
# Generated by dhcpcd from wlan0rcrsn51 wrote:Check the file /etc/resolv.conf. Does it contain a valid "nameserver" line?
# /etc/resolv.conf.head can replace this line
nameserver 192.168.1.1
# /etc/resolv.conf.tail can replace this line
"dhcpcd already running on 32360" perhaps because I'm connected using Simple Network Setup.
Let me start all over and try again. This will knock me off connection for a few moments.
By the way how do you Copy/Paste From/To the urxvt terminal ? Right click doesn't work and control c /control v don't work.
Let me start all over and try again. This will knock me off connection for a few moments.
By the way how do you Copy/Paste From/To the urxvt terminal ? Right click doesn't work and control c /control v don't work.
Ok I tried again with a freshly made Profile and still get Connection Failed. I'm on my main Windows Internet computer now.
Not too sure what I can be doing wrong. Everything seems so simple and straight forward..........
Ran dhcpcd wlan0 again and got the message rebinding 192. etc etc......
Tried again same result.
Not too sure what I can be doing wrong. Everything seems so simple and straight forward..........
Ran dhcpcd wlan0 again and got the message rebinding 192. etc etc......
Tried again same result.
Last edited by MarcHoppe on Wed 16 Mar 2016, 16:39, edited 1 time in total.