ethernet LAN problem | Atheros with LM 21.3 & LMDE 6 | after suspend no IP addresses

Questions about Wi-Fi and other network devices, file sharing, firewalls, connection sharing etc
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Post Reply
jepe
Level 1
Level 1
Posts: 13
Joined: Sat Apr 21, 2018 12:00 pm

ethernet LAN problem | Atheros with LM 21.3 & LMDE 6 | after suspend no IP addresses

Post by jepe »

hi,

EDIT: see post #3 first (BREAKING), a live USB stick with LM 19.3 produces the same faulty behavior.

notes:
I'm talking about WIRED connection, LAN, ethernet, apparently related to an atheros ethernet card.
I've checked the problem PC with :
21.3 Virginia (kernel 5.x), LMDE 6 (k6), DEBIAN 12 (k6) -- the same "thing" happens.

I also have another machine at hand with LM 21.3 XFCE and the problem doesn't happen.
That machine has a different ethernet adapter, of course. (Realtek 8111/8168/something)
Whereas this machine (the problematic machine has: Qualcomm Atheros AR8152 v2.0 Fast Ethernet (rev c1)

-----------------------------------------------------------

I have 2 SSDs, one has Linux mint 20.3 the other 21.3, dual boot...
the machine has Qualcomm Atheros AR8152 v2.0 Fast Ethernet (rev c1) (built in an Asrock board)

So, I can say that:
the same machine works fine with LM 20.3 but produces LAN problem after sleep with LM 21.3.

Instead of LM 21.3 XFCE 64 bit, I have also tried LMDE 6, and DEBIAN 12 -- with the exact same results.


What happens:
LAN works perfectly. The "Connection has been established" messages pops up as usual...
Then sleep, and after sleep it takes a long time for the network manager to get the connection. but even when that happens, it is not an actual connection... i.e. no connection to the internet.. (browser doesn't reach the internet, ping command doesn't either)

Just after boot, I can disconnect and reconnect "WIRED CONNECTION 1", it works perfectly, within a second, quickly.
After sleep, it takes a long time, but when it says connection has been established, it doesn't work....
There are no IP addresses obtained.


Weird thing: I boot to the other "instance", the 20.3 machine, and all works well.
Network Settings also appear to be identical (speaking of 20.3 / 21.3)

I hope this can be worked out...
thanks very much for your help in advance....
please tell me what details you need in order to be able to help...


here's the system report (LMDE 6):

Code: Select all

System:
  Kernel: 6.1.0-18-amd64 arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 Desktop: Cinnamon v: 6.0.4
    tk: GTK v: 3.24.38 wm: muffin vt: 7 dm: LightDM v: 1.26.0 Distro: LMDE 6 Faye
    base: Debian 12.1 bookworm
Machine:
  Type: Desktop Mobo: ASRock model: G41M-VS3. serial: <superuser required>
    BIOS: American Megatrends v: P1.80 date: 05/18/2012
CPU:
  Info: dual core model: Intel Core2 Duo E8500 bits: 64 type: MCP smt: <unsupported> arch: Penryn
    rev: A cache: L1: 128 KiB L2: 6 MiB
  Speed (MHz): avg: 3158 min/max: N/A cores: 1: 3158 2: 3158 bogomips: 12632
  Flags: ht lm nx pae sse sse2 sse3 sse4_1 ssse3 vmx
Graphics:
  Device-1: Intel 4 Series Integrated Graphics vendor: ASRock 4 driver: i915 v: kernel arch: Gen-5
    ports: active: VGA-1 empty: none bus-ID: 00:02.0 chip-ID: 8086:2e32 class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.9 driver: X: loaded: modesetting
    unloaded: fbdev,vesa dri: crocus gpu: i915 display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1280x1024 s-dpi: 96 s-size: 338x270mm (13.31x10.63") s-diag: 433mm (17.03")
  Monitor-1: VGA-1 model: Samsung SyncMaster serial: <filter> res: 1280x1024 hz: 60 dpi: 86
    size: 376x301mm (14.8x11.85") diag: 482mm (19") modes: max: 1280x1024 min: 720x400
  API: OpenGL v: 2.1 Mesa 22.3.6 renderer: Mesa Intel G41 (ELK) direct-render: Yes
Audio:
  Device-1: Intel NM10/ICH7 Family High Definition Audio vendor: ASRock driver: snd_hda_intel
    bus-ID: 1-1:2 v: kernel chip-ID: 1210:000a bus-ID: 00:1b.0 class-ID: fe01 chip-ID: 8086:27d8
    class-ID: 0403
  Device-2: DigiTech Lexicon Alpha type: USB driver: snd-usb-audio
  API: ALSA v: k6.1.0-18-amd64 status: kernel-api
  Server-1: PipeWire v: 0.3.65 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin
Network:
  Device-1: Qualcomm Atheros AR8152 v2.0 Fast Ethernet vendor: ASRock driver: atl1c v: kernel pcie:
    speed: 2.5 GT/s lanes: 1 port: ec00 bus-ID: 01:00.0 chip-ID: 1969:2062 class-ID: 0200
  IF: enp1s0 state: up speed: 100 Mbps duplex: full mac: <filter>
Drives:
  Local Storage: total: 447.14 GiB used: 65.02 GiB (14.5%)
  ID-1: /dev/sda vendor: Kingston model: SA400S37240G size: 223.57 GiB speed: <unknown> type: SSD
    serial: <filter> rev: 0100 scheme: MBR
  ID-2: /dev/sdb vendor: Kingston model: SA400S37240G size: 223.57 GiB speed: <unknown> type: SSD
    serial: <filter> rev: J4.3 scheme: GPT
Partition:
  ID-1: / size: 23.2 GiB used: 8.68 GiB (37.4%) fs: ext4 dev: /dev/sdb2
  ID-2: /boot/efi size: 1.8 GiB used: 24 KiB (0.0%) fs: ext4 dev: /dev/sdb1
  ID-3: /home size: 48.02 GiB used: 3.14 GiB (6.5%) fs: ext4 dev: /dev/sdb3
Swap:
  ID-1: swap-1 type: partition size: 8.95 GiB used: 768 KiB (0.0%) priority: -2 dev: /dev/sda8
  ID-2: swap-2 type: partition size: 14.89 GiB used: 0 KiB (0.0%) priority: -3 dev: /dev/sdb6
USB:
  Hub-1: 1-0:1 info: Full speed or root hub ports: 2 rev: 1.1 speed: 12 Mb/s chip-ID: 1d6b:0001
    class-ID: 0900
  Device-1: 1-1:2 info: DigiTech Lexicon Alpha type: Audio driver: snd-usb-audio interfaces: 4
    rev: 1.1 speed: 12 Mb/s power: 500mA chip-ID: 1210:000a class-ID: fe01
  Device-2: 1-2:3 info: Lenovo Optical Mouse type: Mouse driver: hid-generic,usbhid interfaces: 1
    rev: 1.1 speed: 1.5 Mb/s power: 100mA chip-ID: 17ef:600e class-ID: 0301
  Hub-2: 2-0:1 info: Full speed or root hub ports: 2 rev: 1.1 speed: 12 Mb/s chip-ID: 1d6b:0001
    class-ID: 0900
  Device-1: 2-2:2 info: Dell KB216 Wired Keyboard type: Keyboard,HID driver: hid-generic,usbhid
    interfaces: 2 rev: 2.0 speed: 1.5 Mb/s power: 100mA chip-ID: 413c:2113 class-ID: 0300
  Hub-3: 3-0:1 info: Full speed or root hub ports: 2 rev: 1.1 speed: 12 Mb/s chip-ID: 1d6b:0001
    class-ID: 0900
  Hub-4: 4-0:1 info: Full speed or root hub ports: 2 rev: 1.1 speed: 12 Mb/s chip-ID: 1d6b:0001
    class-ID: 0900
  Hub-5: 5-0:1 info: Full speed or root hub ports: 8 rev: 2.0 speed: 480 Mb/s chip-ID: 1d6b:0002
    class-ID: 0900
Sensors:
  System Temperatures: cpu: 48.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Repos:
  Packages: pm: dpkg pkgs: 2080
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
    1: deb https: //quantum-mirror.hu/mirrors/linuxmint/packages faye main upstream import backport
    2: deb http: //ftp.bme.hu/debian bookworm main contrib non-free non-free-firmware
    3: deb http: //ftp.bme.hu/debian bookworm-updates main contrib non-free non-free-firmware
    4: deb http: //security.debian.org/ bookworm-security main contrib non-free non-free-firmware
    5: deb http: //ftp.bme.hu/debian bookworm-backports main contrib non-free non-free-firmware
Info:
  Processes: 192 Uptime: 25m wakeups: 0 Memory: 7.51 GiB used: 2.53 GiB (33.8%) Init: systemd
  v: 252 target: graphical (5) default: graphical Compilers: gcc: 12.2.0 alt: 12 Client: Unknown
  python3.11 client inxi: 3.3.26

- - -
here are 2 screen shots, the earlier with broken connection (@ 15:23),
the later with fresh & good connection after boot up (@ 15:26)

after waking up from sleep
after waking up from sleep
just after boot up
just after boot up
Last edited by jepe on Fri Mar 29, 2024 10:07 am, edited 14 times in total.
jepe
Level 1
Level 1
Posts: 13
Joined: Sat Apr 21, 2018 12:00 pm

#2: ethernet LAN problem | new install: 21.3 | LAN works but after suspend no IP addresses, no internet connection

Post by jepe »

okay, ip addr show:

before sleep (when it works):
(see those 2 lines)

Code: Select all

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute 
       valid_lft forever preferred_lft forever
2: enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 00:25:22:cc:3b:89 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.6/24 brd 192.168.1.255 scope global dynamic noprefixroute enp1s0
       valid_lft 86192sec preferred_lft 86192sec
         inet6 fe80::2834:b56b:38b0:642d/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
inet 192.168.1.6/24 brd 192.168.1.255 scope global dynamic noprefixroute enp1s0
valid_lft 86192sec preferred_lft 86192sec


these lines are missing from the after-sleep state

and after sleep (when it doesn't):

Code: Select all

ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 00:25:22:cc:3b:89 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::2834:b56b:38b0:642d/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
Last edited by jepe on Fri Mar 29, 2024 12:45 pm, edited 1 time in total.
jepe
Level 1
Level 1
Posts: 13
Joined: Sat Apr 21, 2018 12:00 pm

#3: ethernet LAN problem | Atheros with LM 21.3 & LMDE 6 | after suspend no IP addresses

Post by jepe »

BREAKING:
I have also tested LM 19.3 on a live usb stick, and it produced the same behavior.

so the LM version as a source of the problem can be ruled out :( (:) :) )

NOW I have saved the journalctl -b | grep enp1s0 output...
(I've put some space between some sections... )

Code: Select all

journalctl -b  | grep  enp1s0
Mar 29 14:35:20 my-machine-003 kernel: atl1c 0000:01:00.0 enp1s0: renamed from eth0
Mar 29 14:35:23 my-machine-003 NetworkManager[616]: <info>  [1711719323.1726] manager: (enp1s0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
Mar 29 14:35:23 my-machine-003 NetworkManager[616]: <info>  [1711719323.1730] device (enp1s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')


Mar 29 14:35:23 my-machine-003 kernel: atl1c 0000:01:00.0: atl1c: enp1s0 NIC Link is Up<100 Mbps Full Duplex>
Mar 29 14:35:23 my-machine-003 NetworkManager[616]: <info>  [1711719323.1889] device (enp1s0): carrier: link connected
Mar 29 14:35:23 my-machine-003 NetworkManager[616]: <info>  [1711719323.1901] device (enp1s0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')


Mar 29 14:35:23 my-machine-003 NetworkManager[616]: <info>  [1711719323.1915] device (enp1s0): Activation: starting connection 'ETHER #1' (62074d09-1b3f-44ea-85c4-91e0019bbb41)
Mar 29 14:35:23 my-machine-003 NetworkManager[616]: <info>  [1711719323.1915] device (enp1s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Mar 29 14:35:23 my-machine-003 NetworkManager[616]: <info>  [1711719323.1922] device (enp1s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Mar 29 14:35:23 my-machine-003 NetworkManager[616]: <info>  [1711719323.1939] device (enp1s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')


Mar 29 14:35:23 my-machine-003 NetworkManager[616]: <info>  [1711719323.1958] dhcp4 (enp1s0): activation: beginning transaction (timeout in 45 seconds)
Mar 29 14:35:23 my-machine-003 NetworkManager[616]: <info>  [1711719323.2338] dhcp4 (enp1s0): state changed new lease, address=192.168.1.7
Mar 29 14:35:23 my-machine-003 NetworkManager[616]: <info>  [1711719323.2343] policy: set 'ETHER #1' (enp1s0) as default for IPv4 routing and DNS
Mar 29 14:35:23 my-machine-003 avahi-daemon[539]: Joining mDNS multicast group on interface enp1s0.IPv4 with address 192.168.1.7.
Mar 29 14:35:23 my-machine-003 avahi-daemon[539]: New relevant interface enp1s0.IPv4 for mDNS.
Mar 29 14:35:23 my-machine-003 avahi-daemon[539]: Registering new address record for 192.168.1.7 on enp1s0.IPv4.
Mar 29 14:35:23 my-machine-003 avahi-daemon[539]: Joining mDNS multicast group on interface enp1s0.IPv6 with address fe80::2834:b56b:38b0:642d.
Mar 29 14:35:23 my-machine-003 avahi-daemon[539]: New relevant interface enp1s0.IPv6 for mDNS.
Mar 29 14:35:23 my-machine-003 avahi-daemon[539]: Registering new address record for fe80::2834:b56b:38b0:642d on enp1s0.*.
Mar 29 14:35:23 my-machine-003 NetworkManager[616]: <info>  [1711719323.2840] device (enp1s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Mar 29 14:35:23 my-machine-003 NetworkManager[616]: <info>  [1711719323.2996] device (enp1s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Mar 29 14:35:23 my-machine-003 NetworkManager[616]: <info>  [1711719323.2997] device (enp1s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Mar 29 14:35:23 my-machine-003 NetworkManager[616]: <info>  [1711719323.3003] device (enp1s0): Activation: successful, device activated.
Mar 29 14:35:25 my-machine-003 NetworkManager[616]: <info>  [1711719325.3219] dhcp6 (enp1s0): activation: beginning transaction (timeout in 45 seconds)
Mar 29 14:35:25 my-machine-003 NetworkManager[616]: <info>  [1711719325.3415] dhcp6 (enp1s0): state changed new lease



Mar 29 14:36:37 my-machine-003 NetworkManager[616]: <info>  [1711719397.3862] device (enp1s0): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed')
Mar 29 14:36:37 my-machine-003 NetworkManager[616]: <info>  [1711719397.4731] device (enp1s0): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed')
Mar 29 14:36:37 my-machine-003 avahi-daemon[539]: Withdrawing address record for fe80::2834:b56b:38b0:642d on enp1s0.
Mar 29 14:36:37 my-machine-003 avahi-daemon[539]: Leaving mDNS multicast group on interface enp1s0.IPv6 with address fe80::2834:b56b:38b0:642d.
Mar 29 14:36:37 my-machine-003 avahi-daemon[539]: Interface enp1s0.IPv6 no longer relevant for mDNS.
Mar 29 14:36:37 my-machine-003 NetworkManager[616]: <info>  [1711719397.4867] dhcp4 (enp1s0): canceled DHCP transaction
Mar 29 14:36:37 my-machine-003 NetworkManager[616]: <info>  [1711719397.4868] dhcp4 (enp1s0): activation: beginning transaction (timeout in 45 seconds)
Mar 29 14:36:37 my-machine-003 NetworkManager[616]: <info>  [1711719397.4868] dhcp4 (enp1s0): state changed no lease
Mar 29 14:36:37 my-machine-003 NetworkManager[616]: <info>  [1711719397.4870] dhcp6 (enp1s0): canceled DHCP transaction
Mar 29 14:36:37 my-machine-003 NetworkManager[616]: <info>  [1711719397.4871] dhcp6 (enp1s0): activation: beginning transaction (timeout in 45 seconds)
Mar 29 14:36:37 my-machine-003 NetworkManager[616]: <info>  [1711719397.4871] dhcp6 (enp1s0): state changed no lease
Mar 29 14:36:37 my-machine-003 avahi-daemon[539]: Withdrawing address record for 192.168.1.7 on enp1s0.
Mar 29 14:36:37 my-machine-003 avahi-daemon[539]: Leaving mDNS multicast group on interface enp1s0.IPv4 with address 192.168.1.7.
Mar 29 14:36:37 my-machine-003 avahi-daemon[539]: Interface enp1s0.IPv4 no longer relevant for mDNS.
Mar 29 14:36:37 my-machine-003 NetworkManager[616]: <info>  [1711719397.5394] device (enp1s0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')





Mar 29 14:38:38 my-machine-003 NetworkManager[616]: <info>  [1711719518.9417] device (enp1s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Mar 29 14:38:38 my-machine-003 kernel: atl1c 0000:01:00.0: atl1c: enp1s0 NIC Link is Up<100 Mbps Full Duplex>
Mar 29 14:38:38 my-machine-003 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): enp1s0: link becomes ready
Mar 29 14:38:38 my-machine-003 NetworkManager[616]: <info>  [1711719518.9462] device (enp1s0): carrier: link connected
Mar 29 14:38:38 my-machine-003 NetworkManager[616]: <info>  [1711719518.9463] device (enp1s0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
Mar 29 14:38:38 my-machine-003 NetworkManager[616]: <info>  [1711719518.9501] device (enp1s0): Activation: starting connection 'ETHER #1' (62074d09-1b3f-44ea-85c4-91e0019bbb41)
Mar 29 14:38:38 my-machine-003 NetworkManager[616]: <info>  [1711719518.9502] device (enp1s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Mar 29 14:38:38 my-machine-003 NetworkManager[616]: <info>  [1711719518.9506] device (enp1s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Mar 29 14:38:38 my-machine-003 NetworkManager[616]: <info>  [1711719518.9510] device (enp1s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Mar 29 14:38:38 my-machine-003 NetworkManager[616]: <info>  [1711719518.9591] dhcp4 (enp1s0): activation: beginning transaction (timeout in 45 seconds)
Mar 29 14:38:38 my-machine-003 avahi-daemon[539]: Joining mDNS multicast group on interface enp1s0.IPv6 with address fe80::2834:b56b:38b0:642d.
Mar 29 14:38:38 my-machine-003 avahi-daemon[539]: New relevant interface enp1s0.IPv6 for mDNS.
Mar 29 14:38:38 my-machine-003 avahi-daemon[539]: Registering new address record for fe80::2834:b56b:38b0:642d on enp1s0.*.
Mar 29 14:38:41 my-machine-003 NetworkManager[616]: <info>  [1711719521.6357] dhcp6 (enp1s0): activation: beginning transaction (timeout in 45 seconds)
Mar 29 14:39:26 my-machine-003 NetworkManager[616]: <info>  [1711719566.7492] device (enp1s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Mar 29 14:39:26 my-machine-003 NetworkManager[616]: <info>  [1711719566.7789] device (enp1s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Mar 29 14:39:26 my-machine-003 NetworkManager[616]: <info>  [1711719566.7791] device (enp1s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Mar 29 14:39:26 my-machine-003 NetworkManager[616]: <info>  [1711719566.7796] device (enp1s0): Activation: successful, device activated.
Post Reply

Return to “Networking”