Description of problem: An Encore ENUWI-G2 wireless USB adapter, which contains the Realtek RTL8187B chipset, fails to hold a connection for more than about 5 to 10 minutes. NetworkManager still recognizes it as connected, but no packets appear to go through. Version-Release number of selected component (if applicable): kernel-2.6.27.7-134.fc10.i686 How reproducible: Every time. Steps to Reproduce: 1. Plug in adapter, connect with NetworkManager 2. Connect to a network, start utilizing Actual results: Dies after about 7 to 10 minutes. Expected results: Connection stays active.
Can you re-check this with the latest kernel? I'm using 2.6.27.9-159.fc10.i686 and getting slightly different results. Now the connection stays up, and associated, but no packets can go through at all. Even if I reconnect, it's still dead as a dodo. If it's the same for you on the latest kernel I'll upload logs etc.
[root@cobwebs ~]# lsusb Bus 002 Device 002: ID 0bda:8197 Realtek Semiconductor Corp. RTL8187B Wireless Adapter [root@cobwebs ~]# uname -a Linux cobwebs.darkglobe.int 2.6.27.9-159.fc10.i686 #1 SMP Tue Dec 16 15:12:04 EST 2008 i686 i686 i386 GNU/Linux Strangely it seems to have no problem associating with the wireless network, still thinks its connected, and gets an IP address... but I can't even ping the default gateway or any other ip address on the network. I *can* ping its external ip address on wlan0
Created attachment 328781 [details] dmesg output
Created attachment 328783 [details] ifconfig output
Created attachment 328784 [details] iwconfig output
Created attachment 328785 [details] /var/log/messages output
Just one more user facing the same issue. http://fedoraforum.org/forum/showthread.php?t=208382
Actually, 2.6.27.9-159.fc10.i686 seems to be working perfectly fine for me.
Connection sharing with this adapter now seems to work according to NetworkManager, however a kerneloops.org message box pops up after I do it. This only happened the first time, though. Will actually test connection sharing tomorrow when I have access to another wireless machine.
Glad to hear it. If it ends up working for you best close this bug, and I'll raise a new one.