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
