Unix/Linux Go Back    


Hardware Device drivers, hardware compatibility issues, motherboards, disk drives, graphics cards and other hardware related topics.

Problematic RTL8188EE Wireless Network Adapter

Hardware


Tags
rtl8188ee wireless adapter problems

Closed    
 
Thread Tools Search this Thread Display Modes
    #8  
Old Unix and Linux 05-25-2015
RogerBaran's Unix or Linux Image
RogerBaran RogerBaran is offline
Registered User
 
Join Date: May 2015
Last Activity: 11 November 2015, 7:31 AM EST
Location: San Antonio, TX
Posts: 20
Thanks: 10
Thanked 0 Times in 0 Posts
Duuuuuuhhhh. No I didn't. Let me do that....

---------- Post updated at 06:42 PM ---------- Previous update was at 06:29 PM ----------

After restarting NetworkManager I got:

Code:
root@redbrick /home/redbrick: systemctl status NetworkManager
● NetworkManager.service - Network Manager
   Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled)
   Active: active (running) since Mon 2015-05-25 18:38:04 CDT; 1min 55s ago
 Main PID: 4735 (NetworkManager)
   CGroup: /system.slice/NetworkManager.service
           ├─4735 /usr/sbin/NetworkManager --no-daemon
           └─4965 /sbin/dhclient -d -q -sf /usr/libexec/nm-dhcp-helper -pf /var/run/dhclient-eno1.pid -lf /var/lib/NetworkManager/dhclient-81788e24-85a9-4795-a271-b...

May 25 18:39:54 redbrick NetworkManager[4735]: <info>  (eno1): device state change: ip-config -> ip-check (reason 'none') [70 80 0]
May 25 18:39:54 redbrick NetworkManager[4735]: <info>  Activation (eno1) Stage 5 of 5 (IPv4 Commit) complete.
May 25 18:39:54 redbrick NetworkManager[4735]: <info>  (eno1): device state change: ip-check -> secondaries (reason 'none') [80 90 0]
May 25 18:39:54 redbrick NetworkManager[4735]: <info>  (eno1): device state change: secondaries -> activated (reason 'none') [90 100 0]
May 25 18:39:54 redbrick NetworkManager[4735]: <info>  NetworkManager state is now CONNECTED_LOCAL
May 25 18:39:54 redbrick dhclient[4965]: bound to 10.19.58.7 -- renewal in 1623 seconds.
May 25 18:39:54 redbrick NetworkManager[4735]: <info>  NetworkManager state is now CONNECTED_SITE
May 25 18:39:54 redbrick NetworkManager[4735]: <info>  Policy set 'eno1' (eno1) as default for IPv4 routing and DNS.
May 25 18:39:54 redbrick NetworkManager[4735]: <info>  Activation (eno1) successful, device activated.
May 25 18:39:55 redbrick NetworkManager[4735]: <info>  NetworkManager state is now CONNECTED_GLOBAL

Nothing in here about the wireless side and I cannot use the interface to turn it on. It goes on for just a half-sec and then goes off again...

BTW, I really appreciate your engaging in this issue with me. Linux

---------- Post updated at 06:46 PM ---------- Previous update was at 06:42 PM ----------

Notice the following information provided when I attempt to run:

Code:
root@redbrick /home/redbrick: ifdown wlo1 ; ifup wlo1

(process:5140): libnm-glib-WARNING **: async_got_type: could not read properties for /org/freedesktop/NetworkManager/ActiveConnection/3: Method "Get" with signature "ss" on interface "org.freedesktop.DBus.Properties" doesn't exist

Error: Connection activation failed: Creating object for path '/org/freedesktop/NetworkManager/ActiveConnection/3' failed in libnm-glib.
root@redbrick /home/redbrick: ifconfig
eno1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 10.19.58.7  netmask 255.255.255.0  broadcast 10.19.58.255
        inet6 fe80::d2bf:9cff:fe8a:3141  prefixlen 64  scopeid 0x20<link>
        ether d0:bf:9c:8a:31:41  txqueuelen 1000  (Ethernet)
        RX packets 17834  bytes 11801582 (11.2 MiB)
        RX errors 0  dropped 55  overruns 0  frame 0
        TX packets 14598  bytes 1834307 (1.7 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 0  (Local Loopback)
        RX packets 380  bytes 30696 (29.9 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 380  bytes 30696 (29.9 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

virbr0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 192.168.122.1  netmask 255.255.255.0  broadcast 192.168.122.255
        ether 82:0c:61:4e:7d:0d  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Are we onto something here???
Sponsored Links
    #9  
Old Unix and Linux 05-26-2015
hicksd8 hicksd8 is offline Forum Advisor  
Registered User
 
Join Date: Feb 2012
Last Activity: 23 January 2017, 2:52 AM EST
Location: Devon, UK
Posts: 1,331
Thanks: 156
Thanked 327 Times in 275 Posts
I've heard that the early Pavilion BIOS's could be buggy. Have you got the latest BIOS?

Is there anything in the BIOS such as "allow the O/S to turn off this device"? If so, disallow that to keep the wifi adapter power on.

Failing that, it's to do with the suspend function of your O/S and finding a way to not power down the wifi adapter.

(O/S's failing to reconnect through wifi adapters which have been powered off and then back on is quite common).
The Following User Says Thank You to hicksd8 For This Useful Post:
RogerBaran (05-26-2015)
Sponsored Links
    #10  
Old Unix and Linux 05-26-2015
RogerBaran's Unix or Linux Image
RogerBaran RogerBaran is offline
Registered User
 
Join Date: May 2015
Last Activity: 11 November 2015, 7:31 AM EST
Location: San Antonio, TX
Posts: 20
Thanks: 10
Thanked 0 Times in 0 Posts
I do believe that I saw something while going through the journal errors about the bios... I need to go back and look at it again.
Thank you very much for the reply!Linux

---------- Post updated at 12:09 PM ---------- Previous update was at 09:12 AM ----------

After a reboot I could get the the wifi interface to go up and down and it was able to reconnect as required in spite of the following errors...


Code:
root@redbrick /home/redbrick: ifdown wlo1
root@redbrick /home/redbrick: ifup wlo1
Error: Connection activation failed.
root@redbrick /home/redbrick: ifdown wlo1
root@redbrick /home/redbrick: ifup wlo1
Error: Timeout 90 sec expired.

So, it definitely looks like a standby process specifically turning off the wifi card and the resume process either cant or doesn't turn it back on...

---------- Post updated at 12:21 PM ---------- Previous update was at 12:09 PM ----------

BTW I did try to change the parameters on the modules and switch the power control to software controlled on; but I could not get the hardware control to turn off...
I now have a file in /etc/modprobe.d that contains those entries so that they are effective every boot.

Code:
root@redbrick /home/redbrick: modprobe rtl8188ee ips=0 swlps=1 hwlps=0
root@redbrick /home/redbrick: modinfo rtl8188ee | grep parm
parm:           swenc:Set to 1 for software crypto (default 0)
parm:           ips:Set to 0 to not use link power save (default 1)
parm:           swlps:Set to 1 to use SW control power save (default 0)
parm:           fwlps:Set to 1 to use FW control power save (default 1)
parm:           msi:Set to 1 to use MSI interrupts mode (default 1)
parm:           debug:Set debug level (0-5) (default 0) (int)
parm:           disable_watchdog:Set to 1 to disable the watchdog (default 0)

I think I will try setting debug to 5 and the MSI parameter to 0 and trying again....
    #11  
Old Unix and Linux 05-26-2015
Corona688 Corona688 is offline Forum Staff  
Mead Rotor
 
Join Date: Aug 2005
Last Activity: 20 January 2017, 5:46 PM EST
Location: Saskatchewan
Posts: 21,780
Thanks: 1,027
Thanked 4,038 Times in 3,746 Posts
It may not be possible to fix a buggy driver by fiddling with a buggy driver. The problem may be the driver itself. A kernel upgrade might help or might not, but would be rather drastic.

It's quite possible the problem is specific to your model of laptop, as well. Manufacturers have a choice of how they attach the wiring to the wireless adaptor, and put whatever workarounds they need into the Windows driver, and Linux has to find out the difference the hard way. (This is why laptop hardware so often has its own particular drivers instead of using the manufacturer's generic ones.) Search for discussions on your exact laptop model.
The Following User Says Thank You to Corona688 For This Useful Post:
RogerBaran (05-26-2015)
Sponsored Links
    #12  
Old Unix and Linux 05-26-2015
RogerBaran's Unix or Linux Image
RogerBaran RogerBaran is offline
Registered User
 
Join Date: May 2015
Last Activity: 11 November 2015, 7:31 AM EST
Location: San Antonio, TX
Posts: 20
Thanks: 10
Thanked 0 Times in 0 Posts
Quote:
Originally Posted by Corona688 View Post
It may not be possible to fix a buggy driver by fiddling with a buggy driver. The problem may be the driver itself. A kernel upgrade might help or might not, but would be rather drastic.
lol yep. I think you are right! Linux
Well, it looks like my options are to:
1. Wait it out -- maybe they will get this eventually straightened out,
2. Replace the wifi card in the laptop to a known good one
3. Get a different laptop
4. Live with it

I couldn't change some of the parameters using modprobe -- they wouldn't take.

---------- Post updated at 12:51 PM ---------- Previous update was at 12:47 PM ----------

@Corona688
Thanks for your help. I like working things out and having someone there to bounce ideas off of as I work toward a resolution.

By the way, I did get my disaster recovery script almost finished -- turns out I do not have to create all of the partitions from scratch using sgdisk... Linux
Sponsored Links
    #13  
Old Unix and Linux 05-26-2015
Corona688 Corona688 is offline Forum Staff  
Mead Rotor
 
Join Date: Aug 2005
Last Activity: 20 January 2017, 5:46 PM EST
Location: Saskatchewan
Posts: 21,780
Thanks: 1,027
Thanked 4,038 Times in 3,746 Posts
Replacing the wifi card in your laptop probably isn't an option. Most laptops are programmed to freak out and refuse to boot if you do so, due to FCC regulations. Weird workarounds like disconnecting the detect pin until it boots have been done, but won't work with modern PCIE cards as far as I know.

Using a USB or other kind of external card is okay of course.
Sponsored Links
    #14  
Old Unix and Linux 05-26-2015
RogerBaran's Unix or Linux Image
RogerBaran RogerBaran is offline
Registered User
 
Join Date: May 2015
Last Activity: 11 November 2015, 7:31 AM EST
Location: San Antonio, TX
Posts: 20
Thanks: 10
Thanked 0 Times in 0 Posts
Yeah, after some research I'm finding out that there is a whitelist in the BIOS that only allows certain types of cards to be plugged in. typically this involves buying one of their way more expensive cards to replace it.
Sponsored Links
Closed

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Linux More UNIX and Linux Forum Topics You Might Find Helpful
Thread Thread Starter Forum Replies Last Post
Configuring a D-Link DWA-130 Wireless Adapter ryan352333 Hardware 0 01-28-2011 05:11 PM
my wireless usb adapter connect to net but the signal is very weak rsd220 IP Networking 5 02-19-2010 07:27 PM
How to active this network adapter? rainbow_bean AIX 1 08-15-2009 09:32 PM
change network adapter ariec AIX 1 06-04-2008 04:03 PM
hacmp network adapter re-define johnf AIX 1 05-17-2006 10:10 AM



All times are GMT -4. The time now is 04:35 AM.