USB ethernet adapter - possible problem with power management?

slv · 2017-02-01 09:24:29

Hello

I have small terminal Fujitsu S450. From GUI Preferences >Power Management I changed "idle time ..." to NEVER but after few hours I aboserved that I lost connection to my device (One of LED on ethernet adapter is on) bit I cant ping any host. I have to if down/up and everything started as expected.

How to premanently disable ability to deal with power management on ethernet adapters? or maybe this is other problem that I faced of?

There is one more thing that is strange for me. My terminal is far away from me. I observerd when I lunched from console "reboot" my device switched of insted of reboot. How to check that I have something wrong or not?

Regards
SLawek

Last edited by slv (2017-02-01 09:55:54)

Head_on_a_Stick · 2017-02-01 10:11:45

slv wrote:

after few hours I aboserved that I lost connection to my device

What is your hardware?

lspci -knn | grep -iA2 net

Please also post the output of:

/sbin/iwconfig

You may have to `apt install wireless-tools` to get that command.

when I lunched from console "reboot" my device switched of insted of reboot. How to check that I have something wrong or not?

You can use the systemd journal to investigate further, guide here:

https://www.digitalocean.com/community/ … stemd-logs

slv · 2017-02-01 17:23:36

Hello

Some info

slawek@debian:~$ lsusb
Bus 001 Device 004: ID 07d1:3c05 D-Link System EH103 Wireless G Adapter
Bus 001 Device 003: ID 058f:6387 Alcor Micro Corp. Flash Drive
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 002: ID 04d9:1400 Holtek Semiconductor, Inc. PS/2 keyboard + mouse controller
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 003: ID 046d:c06a Logitech, Inc. USB Optical Mouse
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
slawek@debian:~$ lspci -knn | grep -iA2 net
08:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 02)
Subsystem: Fujitsu Technology Solutions Device [1734:111c]
Kernel driver in use: r8169
slawek@debian:~$ /sbin/iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
eth1 no wireless extensions.

I have some news, there is no problem with reboot (I thought that - but I was wrong), problem is that USB ethernet adapter loose IP addres and this is reason why I thought that I can reboot my device (I haven't access to device).
now ifconfig shows

slawek@debian:~$ ifconfig
eth0      Link encap:Ethernet  HWaddr 00:80:c8:38:6c:f9
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:95 errors:0 dropped:0 overruns:0 frame:0
          TX packets:59 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:12613 (12.3 KiB)  TX bytes:20414 (19.9 KiB)

but why eth0 looses IP address? how to check why?

And I think that my problem is here ... but how to debug it?
I'm new to Linux ... so please give me more detailed leads.

Now I have ssh access (using second interface) to my device.

Head_on_a_Stick · 2017-02-01 18:01:26

Try:

sudo apt install firmware-realtek

You can also try blacklisting the r8169 module — r8168 will hopefully be loaded as an alternative and may offer an improvement.

https://wiki.archlinux.org/index.php/Ke … acklisting

If that does not improve things, add iommu=soft as a kernel command line parameter.

https://wiki.archlinux.org/index.php/Ne … 168.2F8411

Head_on_a_Stick · 2017-02-01 18:02:51

slv wrote:

but how to debug it?

I wrote:

You can use the systemd journal to investigate further, guide here:
https://www.digitalocean.com/community/ … stemd-logs

slv · 2017-02-01 18:41:34

Hello

Is "Journalctl" not to too big for my problem?
I checked /var/log messages, syslog, debug, but I can't find something related to usb ethernet adapter or IP address for it.

slawek@debian:~$ sudo apt install firmware-realtek
[sudo] password for slawek:
Reading package lists... Done
Building dependency tree
Reading state information... Done
firmware-realtek is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 7 not upgraded.

I havent access to GUI so I cant locate this package. What name I should use?

slawek@debian:~$ apt-get install Journalctl
E: Could not open lock file /var/lib/dpkg/lock - open (13: Permission denied)
E: Unable to lock the administration directory (/var/lib/dpkg/), are you root?
slawek@debian:~$ sudo apt-get install Journalctl
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package Journalctl

>If that does not improve things, add iommu=soft as a kernel command line parameter.

I will try tommorow because someone switched off router from eth0 and I can verify it now.

Unfortunetelly I can't put "normal" ethernet card to my device, so I need to use usb adapter. I have to solve problem with it.

Thank You for Your help and patience

Head_on_a_Stick · 2017-02-01 18:46:06

slv wrote:

Is "Journalctl" not to too big for my problem?

No, not at all, the output can be filtered in many ways.

Please read the guide I linked, it explains the options.

E: Unable to locate package Journalctl

The `journalctl` command is part of systemd and is already on your system.

You will need to run the command as root to view all of the messages, so use this just after a signal drop:

sudo journalctl -xe

Head_on_a_Stick · 2017-02-02 07:57:22

Apologies for my confusion earlier in the thread, I wasn't well yesterday

It may be possible to tweak some of the options for the kernel module being used to drive your USB wireless adapter.

This command will list all of the module options currently applied:

systool -v -m asix

That command may require root privileges.

slv · 2017-02-02 11:52:35

"iommu=soft" added to /etc/defult/grub and "update grub" lunched

Now we must wait some hours to problem occur again (or maybe not)

slawek@debian:~$ systool -v -m asix
Module = "asix"

  Attributes:
    coresize            = "30626"
    initsize            = "0"
    initstate           = "live"
    refcnt              = "0"
    srcversion          = "057E49239073DAE0CBDB4C8"
    taint               = ""
    uevent              = <store method only>
    version             = "22-Dec-2011"

  Sections:
    .data               = "0xf80cd000"
    .exit.text          = "0xf80ca52e"
    .gnu.linkonce.this_module= "0xf80cd4e0"
    .init.text          = "0xf80d0000"
    .note.gnu.build-id  = "0xf80cb000"
    .rodata             = "0xf80cb040"
    .rodata.str1.1      = "0xf80cc91b"
    .rodata.str1.4      = "0xf80cbf90"
    .strtab             = "0xf80d21e0"
    .symtab             = "0xf80d1000"
    .text               = "0xf80c7000"
    __mcount_loc        = "0xf80ccc04"
    __verbose           = "0xf80cd078"

slv · 2017-02-02 11:55:32

Hello

Some new informations about my problem with USB ethernet card acting as ETH0 - when it's in "broken state".

slawek@debian:~$ ifconfig eth0
eth0      Link encap:Ethernet  HWaddr 00:80:c8:38:6c:f9
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3817 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:1320682 (1.2 MiB)

slawek@debian:~$ sudo ifdown eth0
[sudo] password for slawek:
ifdown: interface eth0 not configured
slawek@debian:~$ sudo ifup eth0
Ignoring unknown interface eth0=eth0.
slawek@debian:~$ sudo /etc/init.d/networking restart
[ ok ] Restarting networking (via systemctl): networking.service.
slawek@debian:~$ ifconfig eth0
eth0      Link encap:Ethernet  HWaddr 00:80:c8:38:6c:f9
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3829 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:1324834 (1.2 MiB)

my /etc/network/interfaces looks like:

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

and etc/network/interfaces.d is empty

Head_on_a_Stick · 2017-02-02 12:26:29

Those `ifup` & `ifdown` commands will only work if the interface is listed in /etc/network/interfaces

You can do this if you want, this will eliminate NetworkManager and may improve things:

https://wiki.debian.org/NetworkConfigur … _Interface

Also, don't bother with the iommu=soft parameter, I originally thought that you were having problems with the Realtek card but clearly this is not the case.

I really do think that we need to see the journal contents.

Wait until the connection fails then run this command immediately afterwards:

sudo journalctl -xe

Any errors should show up in the output.

slv · 2017-02-03 08:00:14

Hello

My system is up for more than 12h ... without problem with usb ethernet adapter.
I don't know that to think about ... is my problem gone or not.

Head_on_a_Stick · 2017-02-03 09:39:37

We shall play the waiting game then

slv · 2017-02-03 09:44:40

Definitelly

On next week I'm on winter holiday so we will see what will happens.

slv · 2017-02-13 08:59:57

Hello

Uptime is ~9d - so I think that problem is solved (who now how...).

Thx for You support

Regards
Slawek

#1 2017-02-01 09:24:29

USB ethernet adapter - possible problem with power management?

#2 2017-02-01 10:11:45

Re: USB ethernet adapter - possible problem with power management?

#3 2017-02-01 17:23:36

Re: USB ethernet adapter - possible problem with power management?

#4 2017-02-01 18:01:26

Re: USB ethernet adapter - possible problem with power management?

#5 2017-02-01 18:02:51

Re: USB ethernet adapter - possible problem with power management?

#6 2017-02-01 18:41:34

Re: USB ethernet adapter - possible problem with power management?

#7 2017-02-01 18:46:06

Re: USB ethernet adapter - possible problem with power management?

#8 2017-02-02 07:57:22

Re: USB ethernet adapter - possible problem with power management?

#9 2017-02-02 11:52:35

Re: USB ethernet adapter - possible problem with power management?

#10 2017-02-02 11:55:32

Re: USB ethernet adapter - possible problem with power management?

#11 2017-02-02 12:26:29

Re: USB ethernet adapter - possible problem with power management?

#12 2017-02-03 08:00:14

Re: USB ethernet adapter - possible problem with power management?

#13 2017-02-03 09:39:37

Re: USB ethernet adapter - possible problem with power management?

#14 2017-02-03 09:44:40

Re: USB ethernet adapter - possible problem with power management?

#15 2017-02-13 08:59:57

Re: USB ethernet adapter - possible problem with power management?

Board footer