Realtek rtl8192u driver locks up system (Puppy 4.3.0, fresh install)
Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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.
Realtek rtl8192u driver locks up system (Puppy 4.3.0, fresh install)
Hi, all. I've got a Puppy system running version 4.3.0 that I'm trying to get on the home network. I'm using a D-Link DWA-130 (H/W revision C), which has a Realtek RTL8192U chipset. I got the drivers off of D-Link's website, and they compiled and installed just fine, but when either a) I try to connect to the network, or b) while I'm browsing the web, the system locks up completely. No mouse, no keyboard, no Ctrl-Alt-Bksp to get out of X, nothing.
I'll outline my steps:
Install Puppy using a "Full" HDD install (not "Frugal").
Copy the "devx_430.sfs" file (which I got from the Puppy website) from a thumb drive to the "my-documents" folder (although the exact location proabably doesn't matter).
Mount it, cd to the mounted directory and execute "cp -a --remove-destination ./* /" and "sync".
Copy the kernel source for 2.6.30.5 ("kernel_src-2.6.30.5-patched.sfs4.sfs") to the same directory.
Mount it and execute the same commands as before.
Copy the folder containing the RTL8192U drivers ("rtl8192u_linux_2.6.0006.1031.2008") to the root directory (i.e. "/").
cd to the folder in the terminal and run "make", "make install".
Reboot the machine.
Set up networking using the Puppy Internet Connection Wizard.
HERE'S WHERE IT SCREWS UP: It connects, but after a while (e.g. just after logging into LQ through it, as a test) it freezes the entire system.
I have to do a hard reboot ("panic button"), then a soft reboot (for some odd reason the usb module won't load after a hard reboot, so the mouse won't work) to get the system working again, only to have it lock up again once it connects to the network.
Are these drivers broken? Outdated? Is there anything I can do to fix this?
EDIT: I should add that this only occurs when the adapter is plugged in. If I boot the system with it unplugged, it works fine (probably because it never loads the kernel module).
Last edited by MrCode; 01-21-2010 at 06:17 PM.
Reason: removed sig, to save page space
UPDATE: Maybe this could be a hardware issue? The unit is a little warm when I unplug it. I'm not seeing anything significant in the logs (unless there's something important that gets written RIGHT when it freezes, and it gets erased when I hard-reboot )
EDIT: It seems that the whole system doesn't freeze, it's just the mouse/kbd that won't work. I dropped down to console before it had a chance to freeze, and when it "froze", the cursor in the console was still blinking, but I had no keyboard input.
EDIT of EDIT: Scratch that. I ran a "cat /dev/urandom" while waiting for it to freeze and it died (screen frozen, PC speaker going "eeeeeeeeee..."), presumably while attempting to connect to the network.
I'm still quite stumped as to why this is happening, though.
Last edited by MrCode; 01-21-2010 at 06:17 PM.
Reason: removed sig, to save page space
I apologize for all the bumps, but I'm really having a hard time with this. I've Googled everything I can think of and the only relevant thing I can find is my own post...should I just bite the bullet and try getting a new adapter?
Last edited by MrCode; 01-21-2010 at 06:16 PM.
Reason: removed sig, to save page space
There is a directory: /var/log. And where are some log files.
I know about the log files. Unfortunately I can't get the log files from the system directly (I can't seem to get it to cat /var/log/messages to my thumb drive properly just before it locks up), but I suppose I can manually post the last portion that I can see from the terminal just before it locks up:
Code:
Jan 21 21:54:13 (none) local0.debug dhcpcd[5001]: wlan0: sending DHCP_DISCOVER with xid 0x4d1dfc54
Jan 21 21:54:16 (none) local0.debug dhcpcd[5001]: wlan0: sending DHCP_DISCOVER with xid 0x4d1dfc54
Jan 21 21:54:19 (none) local0.debug dhcpcd[5001]: wlan0: sending DHCP_DISCOVER with xid 0x4d1dfc54
Jan 21 21:54:22 (none) local0.debug dhcpcd[5001]: wlan0: sending DHCP_DISCOVER with xid 0x4d1dfc54
Jan 21 21:54:25 (none) local0.debug dhcpcd[5001]: wlan0: sending DHCP_DISCOVER with xid 0x4d1dfc54
Jan 21 21:54:28 (none) local0.debug dhcpcd[5001]: wlan0: sending DHCP_DISCOVER with xid 0x4d1dfc54
Jan 21 21:54:30 (none) local0.debug dhcpcd[5001]: wlan0: sending ARP probe #1
Jan 21 21:54:30 (none) local0.debug dhcpcd[5001]: wlan0: sending ARP probe #2
Jan 21 21:54:30 (none) local0.debug dhcpcd[5001]: wlan0: sending ARP probe #3
Jan 21 21:54:30 (none) local0.debug dhcpcd[5001]: wlan0: sending ARP claim #1
Jan 21 21:54:31 (none) local0.debug dhcpcd[5001]: wlan0: sending ARP claim #2
Jan 21 21:54:31 (none) local0.info dhcpcd[5001]: wlan0: adding IP address xxx.xxx.xxx.xxx/xx
Jan 21 21:54:31 (none) local0.debug dhcpcd[5001]: wlan0: no dns information to write
Jan 21 21:54:31 (none) local0.debug dhcpcd[5001]: wlan0: exec "/etc/dhcpcd.sh" "/var/lib/dhcpcd/dhcpcd-wlan0.info" "up"
Jan 21 21:54:31 (none) local0.debug dhcpcd[5001]: wlan0: waiting on selecto for 10 seconds
Jan 21 21:54:41 (none) local0.debug dhcpcd[5001]: wlan0: sending DHCP_DISCOVER with xid 0x176940e7
Jan 21 21:54:41 (none) local0.debug dhcpcd[5001]: wlan0: waiting on select for 20 seconds
This is all I could get before the system froze on me. I hope it's enough... I don't see anything in there that would indicate a hardware problem, but maybe I wouldn't, simply because it's a hardware problem...?
I'm sorry if I seem impatient...I hope I'm not being too annoying
Ok, I don't understand this "I can't get the log files from the system directly", you can do it under root.
And that file has time stamps, so you can figure out, when you rebooted.
So reboot, and after you plug your dongle and be able to go online,
type "dhcpcd -x wlan0"
Check after with ps -A| grep dhcpcd, if you really kill it, if not kill it with "kill"
May be this helps.
Ok, I don't understand this "I can't get the log files from the system directly", you can do it under root.
It's not that I don't have priveleges to access the log files (in Puppy, you're root by default), it's that I really can't get the whole thing. What I'm trying to do is see if there's anything written to the log file literally right before the system freezes, and I can't time the writing of the file properly to match the freezing of the system, because it seems unpredictable to me (yes, I'm actually trying to do it by simply issuing "cat /var/log/messages > /mnt/sdb1/messages.txt", which exists on the thumb drive). When I tried to access the log file on this machine (cat /media/PORTABLE/messages.txt), I got some of the file, and an "unexpected I/O error". I'm guessing it screwed up writing the file because it locked up during the file writing process.
Quote:
So reboot, and after you plug your dongle and be able to go online,
type "dhcpcd -x wlan0"
At this point I can't even get online. It acts like it's connecting to the network (acquiring an IP address by the looks of what little log info I posted above; it does this automatically), then it simply dies...no mouse, no keyboard, display frozen (whether in X or console).
This is seeming more and more like a hardware issue to me, but I'm still undecided.
Either that, or I must be doing something really stupid, but I don't know what that is...
Again, I apologize if I seem rude...I'm not trying to be.
What do you use to connect to internet? Network manager?
After you reboot, please type "lsmod" and save it, then plug your wireless and type again "lsmod", compare them, what new was loaded?
As soon as you connect you wireless type "dmesg | tail -n 100". Do not post output it directly here, post it to http://pastebin.com/, post here a URL to pastebin page.
The machine froze just after getting this output, so I hope it gets close enough to the problem.
Some more info (in case it's needed ): My network is using WPA encryption (according to the router settings, clients can either use WPA-TKIP or WPA2-AES), and the adapter supposedly supports both WPA and WPA2 encryption, but there was a dialog in the initial setup that was telling me that it didn't detect WPA support. Maybe the driver doesn't support WPA/WPA2?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
)
): My network is using WPA encryption (according to the router settings, clients can either use WPA-TKIP or WPA2-AES), and the adapter supposedly supports both WPA and WPA2 encryption, but there was a dialog in the initial setup that was telling me that it didn't detect WPA support. Maybe the driver doesn't support WPA/WPA2?
