Re: Ethernet not working on a Dell notebook
On 16/03/2024 16:18, fran...@libero.it wrote: root@debian:/home/frantal# networkctl WARNING: systemd-networkd is not running, output will be incomplete. OK, so all devices are under control of NetworkManager and there is no modification of its global configuration. root@debian:/home/frantal# lspci 13:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03) In https://lists.debian.org/msgid-search/uspugc$u42$1...@ciao.gmane.io I asked for lspci -vnn -s 13:00.0 and if the "firmware-realtek" package is installed https://lists.debian.org/msgid-search/ut0d7u$o4o$1...@ciao.gmane.io What is the reason to install r8168 and what is its origin? r8168-dkms? From realtek site directly? Have you tried kernel installed from bookworm-backports? I hope the following should provide informative log for a suitable time frame. - Unplug ethernet cable - Start journalctl as root (e.g. "sudo -i" at first) journalctl -o short-precise -f | tee /tmp/cable.log - Plug in the cable - Wait ~15 seconds - Kill the process by [Ctrl+C] If unrelated system activity happened at this moment then it is better to repeat. The result should be saved to /tmp/cable.log (or another file you like). P.S. The "reply to list" button on the mail list archive pages should properly set In-Reply-To message headers to keep discussion within a thread. Does your mailer support it?
Re: Ethernet not working on a Dell notebook
> advantage. Plugged in cable is detected immediately. With dhclient running > by ifupdown, it may take some minutes till next DHCP request is sent. [ It can take *many* minutes. ] You can use `ifplugd` to make it react to plugging/unplugging the cable, in case you don't want to use NetworkManager. Stefan
Re: Ethernet not working on a Dell notebook
On 15/03/24 at 03:53, Max Nikulin wrote: On 13/03/2024 23:53, Franco Martelli wrote: On 13/03/24 at 16:06, Max Nikulin wrote: On 13/03/2024 21:52, Franco Martelli wrote: They can coexist. NetworkManager in default configuration ignores interfaces under control of ifupdown (/etc/network/interfaces). Detailed messages from NetworkManager related to carrier change events are missed in the posted log file, so the interface is configured by ifupdown. Sorry Max I always knew that they cannot, my mistake… My fault was that I tried to find NetworkManager manager messages in dmesg log. I have never tried to enable control of ifupdown interfaces in NetworkManager. In my opinion, on laptops commenting out interface in /etc/network/interfaces and so delegating it to NetworkManager has a clear advantage. Plugged in cable is detected immediately. With dhclient running by ifupdown, it may take some minutes till next DHCP request is sent. Thanks for clarification, I never installed NetworkManager so this it seemed to me new. The system may have significant changes in respect to defaults. Concerning NetworkManager, the following commands might give some additional info networkctl nmcli device nmcli connection /usr/sbin/NetworkManager --print-config I am unsure if the line in /etc/network/interfaces had some effect since device name is enp19s0 and the file contained eth0. On 13/03/2024 16:52, fran...@libero.it wrote: [ 2.771916] r8168: module verification failed: signature and/or required key missing - tainting kernel tells that not r8169 from default kernel is used. What is the reason to install r8168 and what is its origin? r8168-dkms? From realtek site directly? These questions are greats, sadly it's so hard to help Francesco (fran...@libero.it) he misses also the concept of variable assignment: https://lists.debian.org/debian-user/2024/03/msg00332.html I asked concerning more detailed lspci output and firmware package, but I have got no response. If firmware is installed then I would try backports kernel. If cabling issues have been ruled out then perhaps it is time to ask in a realtek-related mailing list/forum/bugtracker. I dunno, there are so many things unanswered… https://wiki.archlinux.org/title/Talk:Network_configuration/Ethernet So after configured the interfaces, you could try to add "iommu=soft amd_iommu" to the kernel command-line Even if it might help, do not forget to disable it if it has no effect. To verify cat /proc/cmdline It had no effect, I already told to restore to Francesco but I haven't verified https://lists.debian.org/debian-user/2024/03/msg00336.html he told that he has reverted the changes: https://lists.debian.org/debian-user/2024/03/msg00362.html -- Franco Martelli
Re: Ethernet not working on a Dell notebook
On 13/03/2024 23:53, Franco Martelli wrote: On 13/03/24 at 16:06, Max Nikulin wrote: On 13/03/2024 21:52, Franco Martelli wrote: They can coexist. NetworkManager in default configuration ignores interfaces under control of ifupdown (/etc/network/interfaces). Detailed messages from NetworkManager related to carrier change events are missed in the posted log file, so the interface is configured by ifupdown. Sorry Max I always knew that they cannot, my mistake… My fault was that I tried to find NetworkManager manager messages in dmesg log. I have never tried to enable control of ifupdown interfaces in NetworkManager. In my opinion, on laptops commenting out interface in /etc/network/interfaces and so delegating it to NetworkManager has a clear advantage. Plugged in cable is detected immediately. With dhclient running by ifupdown, it may take some minutes till next DHCP request is sent. The system may have significant changes in respect to defaults. Concerning NetworkManager, the following commands might give some additional info networkctl nmcli device nmcli connection /usr/sbin/NetworkManager --print-config I am unsure if the line in /etc/network/interfaces had some effect since device name is enp19s0 and the file contained eth0. On 13/03/2024 16:52, fran...@libero.it wrote: [2.771916] r8168: module verification failed: signature and/or required key missing - tainting kernel tells that not r8169 from default kernel is used. What is the reason to install r8168 and what is its origin? r8168-dkms? From realtek site directly? I asked concerning more detailed lspci output and firmware package, but I have got no response. If firmware is installed then I would try backports kernel. If cabling issues have been ruled out then perhaps it is time to ask in a realtek-related mailing list/forum/bugtracker. https://wiki.archlinux.org/title/Talk:Network_configuration/Ethernet So after configured the interfaces, you could try to add "iommu=soft amd_iommu" to the kernel command-line Even if it might help, do not forget to disable it if it has no effect. To verify cat /proc/cmdline
Re: Ethernet not working on a Dell notebook
Am 14.03.2024 um 17:13:12 Uhr schrieb fran...@libero.it: > After rebooting the problem remains. What does dmesg say? -- Gruß Marco Send spam to 1710432792mu...@cartoonies.org
Re: Ethernet not working on a Dell notebook
On 14/03/24 at 17:03, fran...@libero.it wrote: Hello, I did as indicated, but the connection needs the command sudo mii-tool enp19s0 -F 10baseT-FD to enable. revert the change to /etc/default/grub remove -iommu=soft amd_iommu- strings: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" run again: ~# update-grub then reboot the system. I'm not confident with NetworkManager, maybe others readers have a solution for this issue, try to ask again for help posting the output of the following command: ~# journalctl --no-pager -b -t NetworkManager -- Franco Martelli
Fwd: Re: Ethernet not working on a Dell notebook
I remove auto eth0 After rebooting the problem remains. source /etc/network/interfaces.d/* # The loopback network interface auto lo iface lo inet loopback > > -- Messaggio originale -- > Da: Marco Moock > A: debian-user@lists.debian.org > Data: 14/03/2024 09:38 CET > Oggetto: Re: Ethernet not working on a Dell notebook > > > Am 14.03.2024 schrieb fran...@libero.it: > > > auto eth0 > > remove that.
Re: Ethernet not working on a Dell notebook
On 14/03/24 at 09:07, fran...@libero.it wrote: Hi, good morning. This is the command: /dev/null || echo Debian` GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" iommu=soft amd_iommu GRUB_CMDLINE_LINUX=""> Nope the line: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" iommu=soft amd_iommu ↑ must be: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash iommu=soft amd_iommu" ↑ then post the output of the following command: ~# update-grub whether no error message, then reboot the system. -- Franco Martelli
Re: Ethernet not working on a Dell notebook
Am 14.03.2024 schrieb fran...@libero.it: > auto eth0 remove that.
Re: Ethernet not working on a Dell notebook
root@debian:/home/frantal# dmesg |grep r8169 root@debian:/home/frantal# sudo dmesg |grep r8169 root@debian:/home/frantal# cat /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/* # The loopback network interface auto lo iface lo inet loopback auto eth0 > Il 14/03/2024 09:19 CET Marco Moock ha scritto: > > > How is /etc/network/interfaces now configured? > > Unconfigure your interface there and only use the NetworkManager. > > Then it should log about autoneg. > > What does > dmesg |grep r8169 > print?
Re: Ethernet not working on a Dell notebook
Here again the answer of journalctl: p19s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed') mar 14 09:02:25 debian NetworkManager[565]: [1710403345.7907] dhcp4 (enp19s0): activation: beginning transaction (timeout in 45 seconds) mar 14 09:02:25 debian NetworkManager[565]: [1710403345.8003] dhcp4 (enp19s0): state changed new lease, address=192.168.1.12 mar 14 09:02:25 debian NetworkManager[565]: [1710403345.8017] policy: set 'Connessione via cavo 1' (enp19s0) as default for IPv4 routing and DNS mar 14 09:02:25 debian NetworkManager[565]: [1710403345.8140] device (enp19s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') mar 14 09:02:25 debian NetworkManager[565]: [1710403345.8709] device (enp19s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') mar 14 09:02:25 debian NetworkManager[565]: [1710403345.8716] device (enp19s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') mar 14 09:02:25 debian NetworkManager[565]: [1710403345.8725] manager: NetworkManager state is now CONNECTED_SITE mar 14 09:02:25 debian NetworkManager[565]: [1710403345.8732] device (enp19s0): Activation: successful, device activated. mar 14 09:02:25 debian NetworkManager[565]: [1710403345.8750] manager: NetworkManager state is now CONNECTED_GLOBAL root@debian:/home/frantal# > Il 13/03/2024 21:06 CET Marco Moock ha scritto: > > > Am 13.03.2024 um 17:53:40 Uhr schrieb Franco Martelli: > > > Sadly the useful information of the command output is truncated, > > could you post it again maximizing the window before you copy? For > > the journalctl command use this synta > > Call journalctl with --no-pager and the full line will be shown and > wrapped where needed. > > -- > Gruß > Marco > > Send spam to 1710348820mu...@cartoonies.org
Re: Ethernet not working on a Dell notebook
How is /etc/network/interfaces now configured? Unconfigure your interface there and only use the NetworkManager. Then it should log about autoneg. What does dmesg |grep r8169 print?
Re: Ethernet not working on a Dell notebook
Am 13.03.2024 um 17:53:40 Uhr schrieb Franco Martelli: > Sadly the useful information of the command output is truncated, > could you post it again maximizing the window before you copy? For > the journalctl command use this synta Call journalctl with --no-pager and the full line will be shown and wrapped where needed. -- Gruß Marco Send spam to 1710348820mu...@cartoonies.org
Re: Ethernet not working on a Dell notebook
On 13/03/24 at 18:20, fran...@libero.it wrote: Hello, I did I tried to modify as suggested.I couldn't use sudo update-grub So I gave this command: I think there is an error in the procedure Waiting for suggestions... What is the output of: ~# cat /etc/default/grub | head -10 -- Franco Martelli
Re: Ethernet not working on a Dell notebook
Hello, I did I tried to modify as suggested.I couldn't use sudo update-grub So I gave this command: I think there is an error in the procedure Waiting for suggestions... Francesco > Il 13/03/2024 18:10 CET Franco Martelli ha scritto: > > > On 13/03/24 at 17:51, fran...@libero.it wrote: > > Sorry what is the procedure to add "iommu=soft > >> amd_iommu" to the kernel command-line? > > It is the first time I work with kernel. > > I went to /etc/default/grub and on the line GRUB_CMDLINE_LINUX_DEFAULT I > > have ="quiet splash" > > Have I to add ? > > Thanks for the help > > Francesco > > Your line in /etc/default/grub becomes: > > GRUB_CMDLINE_LINUX_DEFAULT="quiet splash iommu=soft amd_iommu" > > then run: > > ~# update-grub > > then reboot the system. > > HTH > -- > Franco Martelli
Re: Ethernet not working on a Dell notebook
On 13/03/24 at 17:51, fran...@libero.it wrote: Sorry what is the procedure to add "iommu=soft amd_iommu" to the kernel command-line? It is the first time I work with kernel. I went to /etc/default/grub and on the line GRUB_CMDLINE_LINUX_DEFAULT I have ="quiet splash" Have I to add ? Thanks for the help Francesco Your line in /etc/default/grub becomes: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash iommu=soft amd_iommu" then run: ~# update-grub then reboot the system. HTH -- Franco Martelli
Re: Ethernet not working on a Dell notebook
'managed') mar 11 16:48:25 debian NetworkManager[626]: [1710172105.9482] manager: NetworkManager state is now CONNECTING mar 11 16:48:25 debian NetworkManager[626]: [1710172105.9850] device (wlp18s0b1): set-hw-addr: reset MAC address to C4:17:FE:D7:54:E2 (preserve) mar 11 16:48:26 debian NetworkManager[626]: [1710172106.0060] device (wlp18s0b1): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mar 11 16:48:26 debian NetworkManager[626]: [1710172106.0072] device (wlp18s0b1): Activation: (wifi) access point 'TIM-21837165' has security, but secrets are required. mar 11 16:48:26 debian NetworkManager[626]: [1710172106.0073] device (wlp18s0b1): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed') mar 11 16:48:26 debian NetworkManager[626]: [1710172106.0082] sup-iface[6f24c84b1a640cf6,1,wlp18s0b1]: wps: type pbc start... mar 11 16:48:26 debian NetworkManager[626]: [1710172106.0095] device (wlp18s0b1): supplicant interface state: disconnected -> interface_disabled mar 11 16:48:26 debian NetworkManager[626]: [1710172106.0132] device (wlp18s0b1): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed') mar 11 16:48:26 debian NetworkManager[626]: [1710172106.0146] device (wlp18s0b1): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mar 11 16:48:26 debian NetworkManager[626]: [1710172106.0159] device (wlp18s0b1): Activation: (wifi) connection 'TIM-21837165' has security, and secrets exist. No new secrets needed. mar 11 16:48:26 debian NetworkManager[626]: [1710172106.0160] Config: added 'ssid' value 'TIM-21837165' mar 11 16:48:26 debian NetworkManager[626]: [1710172106.0161] Config: added 'scan_ssid' value '1' mar 11 16:48:26 debian NetworkManager[626]: [1710172106.0162] Config: added 'bgscan' value 'simple:30:-70:86400' mar 11 16:48:26 debian NetworkManager[626]: [1710172106.0163] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK' mar 11 16:48:26 debian NetworkManager[626]: [1710172106.0164] Config: added 'psk' value '' mar 11 16:48:26 debian NetworkManager[626]: [1710172106.0285] device (wlp18s0b1): supplicant interface state: interface_disabled -> inactive mar 11 16:48:26 debian NetworkManager[626]: [1710172106.0798] device (wlp18s0b1): supplicant interface state: inactive -> authenticating mar 11 16:48:26 debian NetworkManager[626]: [1710172106.2434] device (wlp18s0b1): supplicant interface state: authenticating -> disconnected mar 11 16:48:26 debian NetworkManager[626]: [1710172106.3441] device (wlp18s0b1): supplicant interface state: disconnected -> scanning mar 11 16:48:26 debian NetworkManager[626]: [1710172106.4593] device (wlp18s0b1): supplicant interface state: scanning -> authenticating mar 11 16:48:26 debian NetworkManager[626]: [1710172106.4715] device (wlp18s0b1): supplicant interface state: authenticating -> associating mar 11 16:48:26 debian NetworkManager[626]: [1710172106.5200] device (wlp18s0b1): supplicant interface state: associating -> associated mar 11 16:48:26 debian NetworkManager[626]: [1710172106.5376] device (wlp18s0b1): supplicant interface state: associated -> 4way_handshake mar 11 16:48:26 debian NetworkManager[626]: [1710172106.6023] device (wlp18s0b1): supplicant interface state: 4way_handshake -> completed mar 11 16:48:26 debian NetworkManager[626]: [1710172106.6024] device (wlp18s0b1): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "TIM-21837165" mar 11 16:48:26 debian NetworkManager[626]: [1710172106.6031] device (wlp18s0b1): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed') mar 11 16:48:26 debian NetworkManager[626]: [1710172106.6051] dhcp4 (wlp18s0b1): activation: beginning transaction (timeout in 45 seconds) mar 11 16:48:26 debian NetworkManager[626]: [1710172106.6245] dhcp4 (wlp18s0b1): state changed new lease, address=192.168.1.228 mar 11 16:48:26 debian NetworkManager[626]: [1710172106.6263] policy: set 'TIM-21837165' (wlp18s0b1) as default for IPv4 routing and DNS mar 11 16:48:26 debian NetworkManager[626]: [1710172106.6442] device (wlp18s0b1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') mar 11 16:48:26 debian NetworkManager[626]: [1710172106.7091] device (wlp18s0b1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') mar 11 16:48:26 debian NetworkManager[626]: [1710172106.7099] device (wlp18s0b1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') mar 11 16:48:26 debian NetworkManager[626]: [1710172106.7109] manager: NetworkManager state is now CONNECTED_SITE mar 11 16:48:26 debian NetworkManager[626]: [1710172106.7123] device (wlp18s0b1): Activation: successful, device activated. mar 11 16:48:26 debian NetworkManager[626]: [1710172106.7141] manager: NetworkManager state is now
Re: Ethernet not working on a Dell notebook
Am 13.03.2024 um 16:14:22 Uhr schrieb fran...@libero.it: > mar 13 11:55:20 debian NetworkManager[569]: [1710327320.4031] > dhcp4 (en> mar 13 11:55:20 debian NetworkManager[569]: > [1710327320.4152] dhcp4 (en> Use journalctl --no-pager -t NetworkManager to get the complete lines. -- Gruß Marco Send spam to 1710342862mu...@cartoonies.org
Re: Ethernet not working on a Dell notebook
Asking to CahtGPT was just for curiosity hoping for an eventual addressing where to go About commands you suggest, hereunder the answer: Active: failed (Result: exit-code) since Wed 2024-03-13 11:54:42 CET; 4h 1> Docs: man:interfaces(5) Process: 536 ExecStart=/sbin/ifup -a --read-environment (code=exited, statu> Process: 635 ExecStopPost=/usr/bin/touch /run/network/restart-hotplug (code> Main PID: 536 (code=exited, status=1/FAILURE) CPU: 80ms mar 13 11:54:41 debian systemd[1]: Starting networking.service - Raise network > mar 13 11:54:42 debian ifup[536]: ifup: unknown interface eth0 mar 13 11:54:42 debian systemd[1]: networking.service: Main process exited, cod> mar 13 11:54:42 debian systemd[1]: networking.service: Failed with result 'exit> mar 13 11:54:42 debian systemd[1]: Failed to start networking.service - Raise n> root@debian:/home/frantal# sudo systemctl status NetworkManager.service ● NetworkManager.service - Network Manager Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; prese> Active: active (running) since Wed 2024-03-13 11:54:42 CET; 4h 13min ago Docs: man:NetworkManager(8) Main PID: 569 (NetworkManager) Tasks: 3 (limit: 9340) Memory: 14.6M CPU: 1.326s CGroup: /system.slice/NetworkManager.service └─569 /usr/sbin/NetworkManager --no-daemon mar 13 11:55:20 debian NetworkManager[569]: [1710327320.4031] dhcp4 (en> mar 13 11:55:20 debian NetworkManager[569]: [1710327320.4152] dhcp4 (en> mar 13 11:55:20 debian NetworkManager[569]: [1710327320.4177] policy: s> mar 13 11:55:20 debian NetworkManager[569]: [1710327320.4366] device (e> mar 13 11:55:20 debian NetworkManager[569]: [1710327320.4932] device (e> mar 13 11:55:20 debian NetworkManager[569]: [1710327320.4938] device (e> mar 13 11:55:20 debian NetworkManager[569]: [1710327320.4949] manager: > mar 13 11:55:20 debian NetworkManager[569]: [1710327320.4958] device (e> mar 13 11:55:20 debian NetworkManager[569]: [1710327320.4996] manager: > mar 13 14:55:18 debian NetworkManager[569]: [1710338118.8885] dhcp4 (en> root@debian:/home/frantal# sudo journalctl -u NetworkManager.service ago 09 01:48:22 debian systemd[1]: Starting Network Manager... ago 09 01:48:23 debian NetworkManager[545]: [1660002503.0709] NetworkMa> ago 09 01:48:23 debian NetworkManager[545]: [1660002503.0710] Read conf> ago 09 01:48:23 debian systemd[1]: Started Network Manager. ago 09 01:48:23 debian NetworkManager[545]: [1660002503.0836] bus-manag> ago 09 01:48:23 debian NetworkManager[545]: [1660002503.0968] manager[0> ago 09 01:48:23 debian NetworkManager[545]: [1660002503.0968] monitorin> ago 09 01:48:23 debian NetworkManager[545]: [1660002503.2567] hostname:> ago 09 01:48:23 debian NetworkManager[545]: [1660002503.2567] hostname:> ago 09 01:48:23 debian NetworkManager[545]: [1660002503.2574] dns-mgr[0> ago 09 01:48:23 debian NetworkManager[545]: [1660002503.2590] rfkill0: > ago 09 01:48:23 debian NetworkManager[545]: [1660002503.2593] manager[0> ago 09 01:48:23 debian NetworkManager[545]: [1660002503.2593] manager[0> ago 09 01:48:23 debian NetworkManager[545]: [1660002503.2739] Loaded de> ago 09 01:48:23 debian NetworkManager[545]: [1660002503.2818] Loaded de> ago 09 01:48:23 debian NetworkManager[545]: [1660002503.2872] Loaded de> ago 09 01:48:23 debian NetworkManager[545]: [1660002503.2891] Loaded de> ago 09 01:48:23 debian NetworkManager[545]: [1660002503.2942] Loaded de> ago 09 01:48:23 debian NetworkManager[545]: [1660002503.2947] manager: > ago 09 01:48:23 debian NetworkManager[545]: [1660002503.2949] manager: > ago 09 01:48:23 debian NetworkManager[545]: [1660002503.2951] manager: > ago 09 01:48:23 debian NetworkManager[545]: [1660002503.2953] dhcp-init> ago 09 01:48:23 debian NetworkManager[545]: [1660002503.2997] settings:> > Il 13/03/2024 15:52 CET Franco Martelli ha scritto: > > > On 13/03/24 at 10:19, fran...@libero.it wrote: > > Hello, > > > > thanks for your answers. > > > > I used the cable with other notebooks and it worked. > > > > In any case I used another cable to test it, but I had the same > > reactions, no connection! > > > > Today I had to give the command 3 times before having a connection... > > Do you have configured both NetworkManager and Debian > /etc/network/interfaces? They cannot coexist, instead to ask to ChatGPT > try this reading: > > https://wiki.debian.org/it/NetworkConfiguration > > What is it the output of the following commands? > > ~$ sudo systemctl status networking.service > > ~$ sudo systemctl status NetworkManager.service > > ~$ sudo journalctl -u NetworkManager.service > > -- > Franco Martelli
Re: Ethernet not working on a Dell notebook
On 13/03/2024 21:52, Franco Martelli wrote: Do you have configured both NetworkManager and Debian /etc/network/interfaces? They cannot coexist, They can coexist. NetworkManager in default configuration ignores interfaces under control of ifupdown (/etc/network/interfaces). Detailed messages from NetworkManager related to carrier change events are missed in the posted log file, so the interface is configured by ifupdown.
Re: Ethernet not working on a Dell notebook
On 13/03/24 at 10:19, fran...@libero.it wrote: Hello, thanks for your answers. I used the cable with other notebooks and it worked. In any case I used another cable to test it, but I had the same reactions, no connection! Today I had to give the command 3 times before having a connection... Do you have configured both NetworkManager and Debian /etc/network/interfaces? They cannot coexist, instead to ask to ChatGPT try this reading: https://wiki.debian.org/it/NetworkConfiguration What is it the output of the following commands? ~$ sudo systemctl status networking.service ~$ sudo systemctl status NetworkManager.service ~$ sudo journalctl -u NetworkManager.service -- Franco Martelli
Re: Ethernet not working on a Dell notebook
Here the "long" output of the 2 requested commands: [0.306974] pci :14:00.0: proprietary Ricoh MMC controller disabled (via FireWire function) [0.306975] pci :14:00.0: MMC cards are now supported by standard SDHCI controller [0.306977] pci :14:00.0: [1180:e822] type 00 class 0x080500 [0.307030] pci :14:00.0: reg 0x10: [mem 0xfbc03000-0xfbc030ff] [0.307351] pci :14:00.0: supports D1 D2 [0.307353] pci :14:00.0: PME# supported from D0 D1 D2 D3hot [0.307710] pci :14:00.1: [1180:e230] type 00 class 0x088000 [0.307752] pci :14:00.1: reg 0x10: [mem 0xfbc02000-0xfbc020ff] [0.308059] pci :14:00.1: supports D1 D2 [0.308061] pci :14:00.1: PME# supported from D0 D1 D2 D3hot [0.308288] pci :14:00.3: [1180:e832] type 00 class 0x0c0010 [0.308330] pci :14:00.3: reg 0x10: [mem 0xfbc0-0xfbc007ff] [0.308520] pci :14:00.3: Enabling fixed DMA alias to 00.0 [0.308626] pci :14:00.3: supports D1 D2 [0.308627] pci :14:00.3: PME# supported from D0 D1 D2 D3hot D3cold [0.308936] pci :00:1c.3: PCI bridge to [bus 14] [0.308945] pci :00:1c.3: bridge window [mem 0xfbc0-0xfbcf] [0.309128] pci :00:1c.4: PCI bridge to [bus 15] [0.309134] pci :00:1c.4: bridge window [io 0xc000-0xcfff] [0.309139] pci :00:1c.4: bridge window [mem 0xfb20-0xfbbf] [0.309146] pci :00:1c.4: bridge window [mem 0xd210-0xd2af 64bit pref] [0.309197] pci_bus :20: extended config space not accessible [0.309300] pci :00:1e.0: PCI bridge to [bus 20] (subtractive decode) [0.309325] pci :00:1e.0: bridge window [io 0x-0x0cf7 window] (subtractive decode) [0.309328] pci :00:1e.0: bridge window [io 0x0d00-0x window] (subtractive decode) [0.309330] pci :00:1e.0: bridge window [mem 0x000a-0x000b window] (subtractive decode) [0.309332] pci :00:1e.0: bridge window [mem 0xc000-0x window] (subtractive decode) [0.310457] ACPI: PCI: Interrupt link LNKA configured for IRQ 11 [0.310553] ACPI: PCI: Interrupt link LNKB configured for IRQ 5 [0.310635] ACPI: PCI: Interrupt link LNKC configured for IRQ 3 [0.310728] ACPI: PCI: Interrupt link LNKD configured for IRQ 4 [0.310820] ACPI: PCI: Interrupt link LNKE configured for IRQ 0 [0.310913] ACPI: PCI: Interrupt link LNKF configured for IRQ 0 [0.311006] ACPI: PCI: Interrupt link LNKG configured for IRQ 10 [0.311087] ACPI: PCI: Interrupt link LNKH configured for IRQ 11 [0.311783] iommu: Default domain type: Translated [0.311783] iommu: DMA domain TLB invalidation policy: lazy mode [0.311783] pps_core: LinuxPPS API ver. 1 registered [0.311783] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti [0.311783] PTP clock support registered [0.311783] EDAC MC: Ver: 3.0.0 [0.312445] NetLabel: Initializing [0.312447] NetLabel: domain hash size = 128 [0.312448] NetLabel: protocols = UNLABELED CIPSOv4 CALIPSO [0.312483] NetLabel: unlabeled traffic allowed by default [0.312485] PCI: Using ACPI for IRQ routing [0.328550] PCI: Discovered peer bus ff [0.328552] PCI: root bus ff: using default resources [0.328553] PCI: Probing PCI hardware (bus ff) [0.328612] PCI host bridge to bus :ff [0.328614] pci_bus :ff: root bus resource [io 0x-0x] [0.328617] pci_bus :ff: root bus resource [mem 0x-0xf] [0.328619] pci_bus :ff: No busn resource found for root bus, will use [bus ff-ff] [0.328621] pci_bus :ff: busn_res: can not insert [bus ff] under domain [bus 00-ff] (conflicts with (null) [bus 00-ff]) [0.328643] pci :ff:00.0: [8086:2c62] type 00 class 0x06 [0.328746] pci :ff:00.1: [8086:2d01] type 00 class 0x06 [0.328839] pci :ff:02.0: [8086:2d10] type 00 class 0x06 [0.328916] pci :ff:02.1: [8086:2d11] type 00 class 0x06 [0.329004] pci :ff:02.2: [8086:2d12] type 00 class 0x06 [0.329100] pci :ff:02.3: [8086:2d13] type 00 class 0x06 [0.329201] pci_bus :ff: busn_res: [bus ff] end is updated to ff [0.329204] pci_bus :ff: busn_res: can not insert [bus ff] under domain [bus 00-ff] (conflicts with (null) [bus 00-ff]) [0.329210] PCI: pci_cache_line_size set to 64 bytes [0.329358] e820: reserve RAM buffer [mem 0x0009d400-0x0009] [0.329361] e820: reserve RAM buffer [mem 0xbf594000-0xbfff] [0.329363] e820: reserve RAM buffer [mem 0xbf80-0xbfff] [0.329398] pci :01:00.0: vgaarb: setting as boot VGA device [0.329398] pci :01:00.0: vgaarb: bridge control possible [0.329398] pci :01:00.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none [0.329398] vgaarb: loaded [0.333298] hpet0: at MMIO 0xfed0, IRQs 2, 8, 0, 0, 0, 0, 0, 0 [0.25] hpet0: 8 comparat
Re: Ethernet not working on a Dell notebook
Am 13.03.2024 um 10:19:04 Uhr schrieb fran...@libero.it: > So I give a try to ask to ChatGPT what does it mean that command and > this was the answer: This was already clear. The question is now: Why does autoneg fail? Please check dmesg and journalctl for any messages from Networkmanager. -- Gruß Marco Send spam to 1710321544mu...@cartoonies.org
Re: Ethernet not working on a Dell notebook
On 12/03/2024 15:11, fran...@libero.it wrote: 13:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03) lspci -vnn -s 13:00.0 should give more detailed info concerning your network adapter. Finally while trying to find the solution I tried this command and after some seconds I was online: sudo mii-tool enp19s0 -F 10baseT-FD Perhaps it is obvious, but do you have the firmware-realtek package installed? Inspect journalctl output, NetworkManager should log negotiation failures.
Re: Ethernet not working on a Dell notebook
Am 12.03.2024 um 10:17:05 Uhr schrieb fran...@libero.it: > it is connected via a Switch (Netgear) to the modem-router. > If I use this cable with other computers it works without problems. Please test another cable and another switch if available. We need to track down the problem. -- Gruß Marco Send spam to 1710235025mu...@cartoonies.org
Re: Ethernet not working on a Dell notebook
fran...@libero.it writes: > sudo mii-tool enp19s0 -F 10baseT-FD > > The problem is that every time I shut off the notebook Ito have ethernet > connection again I have to give that command by terminal. Is > there the possibility to make default this ethernet module? Thanks and regards You can specify ethtool commands to be run in /etc/network/interfaces, see /usr/share/doc/ethtool/README.Debian for details. I'm not sure if that'll work with NetworkManager, though. But, having to force 10baseT probably indicates other issues like a bad cable, as Marco said.
Re: Ethernet not working on a Dell notebook
Am 12.03.2024 um 09:11:20 Uhr schrieb fran...@libero.it: > Finally while trying to find the solution I tried this command and > after some seconds I was online: > > sudo mii-tool enp19s0 -F 10baseT-FD That seems to be an autoneg problem. Please tell us more about your cabling (direct, via sockets etc.) and the device (switch, router) the laptop is connected to. -- kind regards Marco Send spam to 1710231080mu...@cartoonies.org
