Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #268219 > unrolled thread

Ethernet not working on a Dell notebook

Started byfrantal@libero.it
First post2024-03-13 10:20 +0100
Last post2024-03-14 17:50 +0100
Articles 11 — 4 participants

Back to article view | Back to linux.debian.user

Contents

  Ethernet not working on a Dell notebook frantal@libero.it - 2024-03-13 10:20 +0100
    Re: Ethernet not working on a Dell notebook Marco Moock <mm@dorfdsl.de> - 2024-03-13 10:50 +0100
    Re: Ethernet not working on a Dell notebook Franco Martelli <martellif67@gmail.com> - 2024-03-13 16:00 +0100
      Re: Ethernet not working on a Dell notebook Max Nikulin <manikulin@gmail.com> - 2024-03-13 16:10 +0100
      Re: Ethernet not working on a Dell notebook frantal@libero.it - 2024-03-13 16:20 +0100
        Re: Ethernet not working on a Dell notebook Marco Moock <mm@dorfdsl.de> - 2024-03-13 16:30 +0100
        Re: Ethernet not working on a Dell notebook Franco Martelli <martellif67@gmail.com> - 2024-03-13 18:20 +0100
          Re: Ethernet not working on a Dell notebook frantal@libero.it - 2024-03-13 18:30 +0100
            Re: Ethernet not working on a Dell notebook Franco Martelli <martellif67@gmail.com> - 2024-03-13 20:40 +0100
              Re: Ethernet not working on a Dell notebook Franco Martelli <martellif67@gmail.com> - 2024-03-14 15:00 +0100
                Re: Ethernet not working on a Dell notebook Franco Martelli <martellif67@gmail.com> - 2024-03-14 17:50 +0100

#268219 — Ethernet not working on a Dell notebook

Fromfrantal@libero.it
Date2024-03-13 10:20 +0100
SubjectEthernet not working on a Dell notebook
Message-ID<IhsWd-gkxl-5@gated-at.bofh.it>

[Multipart message — attachments visible in raw view] — view raw

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...

So I give a try to ask to ChatGPT what does it mean that command and this was the answer:

<The 'sudo mii-tool enp19s0 -F 10baseT-FD' command is used to configure the settings of an Ethernet network interface on a Linux system. Here is a detailed explanation of each part of the command:
- sudo: This prefix is used to execute the next command with privileges
superuser (root). It is required to change network settings, which require privileges
high.
- mii-tool: This is a command that allows you to check and configure network interfaces
Ethernets that support the MII (Media IndependentInterface) interface. It is particularly useful
to configure low-level network settings.
- enp19s0: This is the name of the network interface you want to configure. The names of
Network interfaces may vary depending on the system, but in this case, enp19s0 is the name
assigned to a specific Ethernet interface.
- F 10baseT-FD: This option specifies the type of Ethernet connection you want
configure. 10baseT-FD indicates that you are configuring the interface to use a
10 Mbps Ethernet connection in Full Duplex mode.
Full Duplex means the interface can transmit and receive data simultaneously,
improving network performance.
In summary, the sudo mii-tool enp19s0 -F 10baseT-FD command configures the enp19s0 Ethernet network interface to use a 10 Mbps connection in Full Duplex mode. This can be useful for optimizing network performance or troubleshooting connectivity issues.>

[toc] | [next] | [standalone]

#268220

FromMarco Moock <mm@dorfdsl.de>
Date2024-03-13 10:50 +0100
Message-ID<Ihtpg-gkGy-3@gated-at.bofh.it>
In reply to#268219
Am 13.03.2024 um 10:19:04 Uhr schrieb frantal@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 1710321544muell@cartoonies.org

[toc] | [prev] | [next] | [standalone]

#268226

FromFranco Martelli <martellif67@gmail.com>
Date2024-03-13 16:00 +0100
Message-ID<Ihyff-go4Y-15@gated-at.bofh.it>
In reply to#268219
On 13/03/24 at 10:19, frantal@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

[toc] | [prev] | [next] | [standalone]

#268228

FromMax Nikulin <manikulin@gmail.com>
Date2024-03-13 16:10 +0100
Message-ID<Ihyp2-gorE-55@gated-at.bofh.it>
In reply to#268226
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.

[toc] | [prev] | [next] | [standalone]

#268230

Fromfrantal@libero.it
Date2024-03-13 16:20 +0100
Message-ID<IhyyJ-govi-15@gated-at.bofh.it>
In reply to#268226
Asking to CahtGPT was just for curiosity hoping for an eventual addressing where to go....
About commands you suggest, hereunder the answer:
<root@debian:/home/frantal# sudo systemctl status networking.service
× networking.service - Raise network interfaces
     Loaded: loaded (/lib/systemd/system/networking.service; enabled; preset: e>
     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]: <info>  [1710327320.4031] dhcp4 (en>
mar 13 11:55:20 debian NetworkManager[569]: <info>  [1710327320.4152] dhcp4 (en>
mar 13 11:55:20 debian NetworkManager[569]: <info>  [1710327320.4177] policy: s>
mar 13 11:55:20 debian NetworkManager[569]: <info>  [1710327320.4366] device (e>
mar 13 11:55:20 debian NetworkManager[569]: <info>  [1710327320.4932] device (e>
mar 13 11:55:20 debian NetworkManager[569]: <info>  [1710327320.4938] device (e>
mar 13 11:55:20 debian NetworkManager[569]: <info>  [1710327320.4949] manager: >
mar 13 11:55:20 debian NetworkManager[569]: <info>  [1710327320.4958] device (e>
mar 13 11:55:20 debian NetworkManager[569]: <info>  [1710327320.4996] manager: >
mar 13 14:55:18 debian NetworkManager[569]: <info>  [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]: <info>  [1660002503.0709] NetworkMa>
ago 09 01:48:23 debian NetworkManager[545]: <info>  [1660002503.0710] Read conf>
ago 09 01:48:23 debian systemd[1]: Started Network Manager.
ago 09 01:48:23 debian NetworkManager[545]: <info>  [1660002503.0836] bus-manag>
ago 09 01:48:23 debian NetworkManager[545]: <info>  [1660002503.0968] manager[0>
ago 09 01:48:23 debian NetworkManager[545]: <info>  [1660002503.0968] monitorin>
ago 09 01:48:23 debian NetworkManager[545]: <info>  [1660002503.2567] hostname:>
ago 09 01:48:23 debian NetworkManager[545]: <info>  [1660002503.2567] hostname:>
ago 09 01:48:23 debian NetworkManager[545]: <info>  [1660002503.2574] dns-mgr[0>
ago 09 01:48:23 debian NetworkManager[545]: <info>  [1660002503.2590] rfkill0: >
ago 09 01:48:23 debian NetworkManager[545]: <info>  [1660002503.2593] manager[0>
ago 09 01:48:23 debian NetworkManager[545]: <info>  [1660002503.2593] manager[0>
ago 09 01:48:23 debian NetworkManager[545]: <info>  [1660002503.2739] Loaded de>
ago 09 01:48:23 debian NetworkManager[545]: <info>  [1660002503.2818] Loaded de>
ago 09 01:48:23 debian NetworkManager[545]: <info>  [1660002503.2872] Loaded de>
ago 09 01:48:23 debian NetworkManager[545]: <info>  [1660002503.2891] Loaded de>
ago 09 01:48:23 debian NetworkManager[545]: <info>  [1660002503.2942] Loaded de>
ago 09 01:48:23 debian NetworkManager[545]: <info>  [1660002503.2947] manager: >
ago 09 01:48:23 debian NetworkManager[545]: <info>  [1660002503.2949] manager: >
ago 09 01:48:23 debian NetworkManager[545]: <info>  [1660002503.2951] manager: >
ago 09 01:48:23 debian NetworkManager[545]: <info>  [1660002503.2953] dhcp-init>
ago 09 01:48:23 debian NetworkManager[545]: <info>  [1660002503.2997] settings:>

 
> Il 13/03/2024 15:52 CET Franco Martelli <martellif67@gmail.com> ha scritto:
> 
>  
> On 13/03/24 at 10:19, frantal@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

[toc] | [prev] | [next] | [standalone]

#268231

FromMarco Moock <mm@dorfdsl.de>
Date2024-03-13 16:30 +0100
Message-ID<IhyIh-goyD-11@gated-at.bofh.it>
In reply to#268230
Am 13.03.2024 um 16:14:22 Uhr schrieb frantal@libero.it:

> mar 13 11:55:20 debian NetworkManager[569]: <info>  [1710327320.4031]
> dhcp4 (en> mar 13 11:55:20 debian NetworkManager[569]: <info>
> [1710327320.4152] dhcp4 (en>

Use journalctl --no-pager -t NetworkManager
to get the complete lines.

-- 
Gruß
Marco

Send spam to 1710342862muell@cartoonies.org

[toc] | [prev] | [next] | [standalone]

#268237

FromFranco Martelli <martellif67@gmail.com>
Date2024-03-13 18:20 +0100
Message-ID<IhAqJ-gpCw-3@gated-at.bofh.it>
In reply to#268230
On 13/03/24 at 17:51, frantal@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 <iommu=soft amd_iommu>?
> 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

[toc] | [prev] | [next] | [standalone]

#268238

Fromfrantal@libero.it
Date2024-03-13 18:30 +0100
Message-ID<IhAAq-gpFR-11@gated-at.bofh.it>
In reply to#268237
Hello,
I did
I tried to modify as suggested.I couldn't use sudo update-grub 
So I gave this command:
<root@debian:/home/frantal# sudo grub-mkconfig -o /boot/grub/grub.cfg
/usr/sbin/grub-mkconfig: 9: /etc/default/grub: amd_iommu: not found>
I think there is an error in the procedure....
Waiting for suggestions...
Francesco


> Il 13/03/2024 18:10 CET Franco Martelli <martellif67@gmail.com> ha scritto:
> 
>  
> On 13/03/24 at 17:51, frantal@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 <iommu=soft amd_iommu>?
> > 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

[toc] | [prev] | [next] | [standalone]

#268243

FromFranco Martelli <martellif67@gmail.com>
Date2024-03-13 20:40 +0100
Message-ID<IhCCe-gqSJ-7@gated-at.bofh.it>
In reply to#268238
On 13/03/24 at 18:20, frantal@libero.it wrote:
> Hello,
> I did
> I tried to modify as suggested.I couldn't use sudo update-grub
> So I gave this command:
> <root@debian:/home/frantal# sudo grub-mkconfig -o /boot/grub/grub.cfg
> /usr/sbin/grub-mkconfig: 9: /etc/default/grub: amd_iommu: not found>
> 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

[toc] | [prev] | [next] | [standalone]

#268260

FromFranco Martelli <martellif67@gmail.com>
Date2024-03-14 15:00 +0100
Message-ID<IhTMJ-gEK8-3@gated-at.bofh.it>
In reply to#268243
On 14/03/24 at 09:07, frantal@libero.it wrote:
> Hi,
> good morning. This is the command:
> <root@debian:/home/frantal# cat /etc/default/grub | head -10
> 
> # If you change this file, run 'update-grub' afterwards to update
> # /boot/grub/grub.cfg.
> # For full documentation of the options in this file, see:
> #   info -f grub -n 'Simple configuration'
> 
> GRUB_DEFAULT=0
> GRUB_TIMEOUT=5
> GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /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

[toc] | [prev] | [next] | [standalone]

#268263

FromFranco Martelli <martellif67@gmail.com>
Date2024-03-14 17:50 +0100
Message-ID<IhWrf-gGmq-7@gated-at.bofh.it>
In reply to#268260
On 14/03/24 at 17:03, frantal@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

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web