Need help troubleshooting NIC (ethernet card) on Manjaro KDE

andrewysk · August 12, 2021, 11:41pm

`journalctl --boot 0 --unit NetworkManager.service --no-hostname --no-pager`

-- Journal begins at Mon 2020-03-30 22:08:21 CEST, ends at Fri 2021-08-13 01:05:55 CEST. --
Aug 12 19:39:07 systemd[1]: Starting Network Manager...
Aug 12 19:39:12 NetworkManager[488]: <info>  [1628789952.2426] NetworkManager (version 1.32.4-1) is starting... (for the first time)
Aug 12 19:39:12 NetworkManager[488]: <info>  [1628789952.3325] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 20-connectivity.conf)
Aug 12 19:39:14 systemd[1]: Started Network Manager.
Aug 12 19:39:14 NetworkManager[488]: <info>  [1628789954.2328] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
Aug 12 19:39:14 NetworkManager[488]: <info>  [1628789954.3868] manager[0x557d9d363040]: monitoring kernel firmware directory '/lib/firmware'.
Aug 12 19:39:14 NetworkManager[488]: <info>  [1628789954.8233] hostname: hostname: using hostnamed
Aug 12 19:39:14 NetworkManager[488]: <info>  [1628789954.8233] hostname: hostname changed from (none) to "user1-pc"
Aug 12 19:39:14 NetworkManager[488]: <info>  [1628789954.8239] dns-mgr[0x557d9d31b250]: init: dns=default,systemd-resolved rc-manager=symlink
Aug 12 19:39:14 NetworkManager[488]: <info>  [1628789954.8913] manager[0x557d9d363040]: rfkill: Wi-Fi hardware radio set disabled
Aug 12 19:39:14 NetworkManager[488]: <info>  [1628789954.8913] manager[0x557d9d363040]: rfkill: WWAN hardware radio set disabled
Aug 12 19:39:16 NetworkManager[488]: <info>  [1628789956.1741] Loaded device plugin: NMWwanFactory (/usr/lib/NetworkManager/1.32.4-1/libnm-device-plugin-wwan.so)
Aug 12 19:39:16 NetworkManager[488]: <info>  [1628789956.2949] Loaded device plugin: NMWifiFactory (/usr/lib/NetworkManager/1.32.4-1/libnm-device-plugin-wifi.so)
Aug 12 19:39:16 NetworkManager[488]: <info>  [1628789956.9109] Loaded device plugin: NMTeamFactory (/usr/lib/NetworkManager/1.32.4-1/libnm-device-plugin-team.so)
Aug 12 19:39:16 NetworkManager[488]: <info>  [1628789956.9798] Loaded device plugin: NMAtmManager (/usr/lib/NetworkManager/1.32.4-1/libnm-device-plugin-adsl.so)
Aug 12 19:39:17 NetworkManager[488]: <info>  [1628789957.1948] Loaded device plugin: NMBluezManager (/usr/lib/NetworkManager/1.32.4-1/libnm-device-plugin-bluetooth.so)
Aug 12 19:39:17 NetworkManager[488]: <info>  [1628789957.3168] Loaded device plugin: NMOvsFactory (/usr/lib/NetworkManager/1.32.4-1/libnm-device-plugin-ovs.so)
Aug 12 19:39:17 NetworkManager[488]: <info>  [1628789957.3172] manager: rfkill: Wi-Fi enabled by radio killswitch; disabled by state file
Aug 12 19:39:17 NetworkManager[488]: <info>  [1628789957.3173] manager: rfkill: WWAN enabled by radio killswitch; disabled by state file
Aug 12 19:39:17 NetworkManager[488]: <info>  [1628789957.3173] manager: Networking is enabled by state file
Aug 12 19:39:17 NetworkManager[488]: <info>  [1628789957.3683] dhcp-init: Using DHCP client 'internal'
Aug 12 19:39:17 NetworkManager[488]: <info>  [1628789957.4073] settings: Loaded settings plugin: keyfile (internal)
Aug 12 19:39:17 NetworkManager[488]: <info>  [1628789957.7545] device (lo): carrier: link connected
Aug 12 19:39:17 NetworkManager[488]: <info>  [1628789957.7549] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1)
Aug 12 19:39:17 NetworkManager[488]: <info>  [1628789957.7558] manager: (enp0s25): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
Aug 12 19:39:17 NetworkManager[488]: <info>  [1628789957.8320] settings: (enp0s25): created default wired connection 'Wired connection 1'
Aug 12 19:39:17 NetworkManager[488]: <info>  [1628789957.8324] device (enp0s25): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Aug 12 19:39:18 NetworkManager[488]: <info>  [1628789958.2637] manager: (enp3s0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/3)
Aug 12 19:39:18 NetworkManager[488]: <info>  [1628789958.2647] settings: (enp3s0): created default wired connection 'Wired connection 2'
Aug 12 19:39:18 NetworkManager[488]: <info>  [1628789958.2651] device (enp3s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Aug 12 19:39:19 NetworkManager[488]: <info>  [1628789959.1437] ovsdb: Could not connect: No such file or directory
Aug 12 19:39:19 NetworkManager[488]: <info>  [1628789959.1439] ovsdb: disconnected from ovsdb
Aug 12 19:39:20 NetworkManager[488]: <info>  [1628789960.7767] device (enp0s25): carrier: link connected
Aug 12 19:39:20 NetworkManager[488]: <info>  [1628789960.7770] device (enp0s25): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
Aug 12 19:39:20 NetworkManager[488]: <info>  [1628789960.7776] policy: auto-activating connection 'Wired connection 1' (c48347d3-1020-3aac-b2d3-add97d4904fd)
Aug 12 19:39:20 NetworkManager[488]: <info>  [1628789960.7781] device (enp0s25): Activation: starting connection 'Wired connection 1' (c48347d3-1020-3aac-b2d3-add97d4904fd)
Aug 12 19:39:20 NetworkManager[488]: <info>  [1628789960.7781] device (enp0s25): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Aug 12 19:39:20 NetworkManager[488]: <info>  [1628789960.7784] manager: NetworkManager state is now CONNECTING
Aug 12 19:39:20 NetworkManager[488]: <info>  [1628789960.7785] device (enp0s25): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Aug 12 19:39:20 NetworkManager[488]: <info>  [1628789960.7791] device (enp0s25): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Aug 12 19:39:20 NetworkManager[488]: <info>  [1628789960.8258] dhcp4 (enp0s25): activation: beginning transaction (timeout in 45 seconds)
Aug 12 19:39:20 NetworkManager[488]: <info>  [1628789960.9613] dhcp4 (enp0s25): state changed unknown -> expire
Aug 12 19:39:21 NetworkManager[488]: <info>  [1628789961.5487] modem-manager: ModemManager not available
Aug 12 19:39:21 NetworkManager[488]: <info>  [1628789961.7286] modem-manager: ModemManager now available
Aug 12 19:39:23 NetworkManager[488]: <info>  [1628789963.0474] dhcp6 (enp0s25): activation: beginning transaction (timeout in 45 seconds)
Aug 12 19:39:23 NetworkManager[488]: <info>  [1628789963.0643] dhcp6 (enp0s25): state changed unknown -> bound
Aug 12 19:39:23 NetworkManager[488]: <info>  [1628789963.4043] dhcp4 (enp0s25): state changed expire -> bound, address=192.168.0.137
Aug 12 19:39:23 NetworkManager[488]: <info>  [1628789963.4052] device (enp0s25): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Aug 12 19:39:23 NetworkManager[488]: <info>  [1628789963.4721] device (enp0s25): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Aug 12 19:39:23 NetworkManager[488]: <info>  [1628789963.4723] device (enp0s25): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Aug 12 19:39:23 NetworkManager[488]: <info>  [1628789963.4729] manager: NetworkManager state is now CONNECTED_LOCAL
Aug 12 19:39:23 NetworkManager[488]: <info>  [1628789963.4735] manager: NetworkManager state is now CONNECTED_SITE
Aug 12 19:39:23 NetworkManager[488]: <info>  [1628789963.4736] policy: set 'Wired connection 1' (enp0s25) as default for IPv4 routing and DNS
Aug 12 19:39:23 NetworkManager[488]: <info>  [1628789963.4738] policy: set 'Wired connection 1' (enp0s25) as default for IPv6 routing and DNS
Aug 12 19:39:23 NetworkManager[488]: <info>  [1628789963.6642] device (enp0s25): Activation: successful, device activated.
Aug 12 19:39:23 NetworkManager[488]: <info>  [1628789963.9295] manager: NetworkManager state is now CONNECTED_GLOBAL
Aug 12 19:39:24 NetworkManager[488]: <info>  [1628789964.5569] manager: startup complete
Aug 12 19:39:57 NetworkManager[488]: <info>  [1628789997.1213] agent-manager: agent[b4c46b489e30fb24,:1.16/org.kde.plasma.networkmanagement/1000]: agent registered
Aug 12 20:09:13 NetworkManager[488]: <info>  [1628791753.8710] dhcp4 (enp0s25): state changed bound -> extended, address=192.168.0.137
Aug 12 20:39:13 NetworkManager[488]: <info>  [1628793553.8629] dhcp4 (enp0s25): state changed extended -> extended, address=192.168.0.137
Aug 12 21:09:13 NetworkManager[488]: <info>  [1628795353.8507] dhcp4 (enp0s25): state changed extended -> extended, address=192.168.0.137
Aug 12 21:39:13 NetworkManager[488]: <info>  [1628797153.8450] dhcp4 (enp0s25): state changed extended -> extended, address=192.168.0.137
Aug 12 22:06:07 NetworkManager[488]: <info>  [1628798767.8368] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Aug 12 22:06:07 NetworkManager[488]: <info>  [1628798767.8369] manager: NetworkManager state is now ASLEEP
Aug 12 22:06:18 NetworkManager[488]: <info>  [1628798778.8218] manager: sleep: wake requested (sleeping: yes  enabled: yes)
Aug 12 22:06:18 NetworkManager[488]: <info>  [1628798778.8219] device (enp0s25): state change: activated -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Aug 12 22:06:18 NetworkManager[488]: <info>  [1628798778.8220] dhcp4 (enp0s25): canceled DHCP transaction
Aug 12 22:06:18 NetworkManager[488]: <info>  [1628798778.8220] dhcp4 (enp0s25): state changed extended -> terminated
Aug 12 22:06:18 NetworkManager[488]: <info>  [1628798778.8222] dhcp6 (enp0s25): canceled DHCP transaction
Aug 12 22:06:18 NetworkManager[488]: <info>  [1628798778.8222] dhcp6 (enp0s25): state changed bound -> terminated
Aug 12 22:06:18 NetworkManager[488]: <info>  [1628798778.9457] manager: NetworkManager state is now CONNECTED_GLOBAL
Aug 12 22:06:19 NetworkManager[488]: <info>  [1628798779.1429] manager: NetworkManager state is now DISCONNECTED
Aug 12 22:06:19 NetworkManager[488]: <info>  [1628798779.1437] device (enp3s0): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')

`journalctl --boot 0 --unit ModemManager.service --no-hostname --no-pager`

-- Journal begins at Mon 2020-03-30 22:08:21 CEST, ends at Fri 2021-08-13 02:02:14 CEST. --
Aug 12 19:39:17 systemd[1]: Starting Modem Manager...
Aug 12 19:39:19 ModemManager[538]: <info>  ModemManager (version 1.16.8) starting in system bus...
Aug 12 19:39:21 systemd[1]: Started Modem Manager.
Aug 12 19:39:24 ModemManager[538]: <info>  [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:19.0': not supported by any plugin
Aug 12 19:39:24 ModemManager[538]: <info>  [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:1e.0/0000:03:00.0': not supported by any plugin
Aug 12 22:06:07 ModemManager[538]: <info>  [sleep-monitor] system is about to suspend
Aug 12 22:06:18 ModemManager[538]: <info>  [sleep-monitor] system is resuming
Aug 12 22:06:21 ModemManager[538]: <info>  [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:19.0': not supported by any plugin
Aug 12 22:06:21 ModemManager[538]: <info>  [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:1e.0/0000:03:00.0': not supported by any plugin
Aug 12 23:37:13 ModemManager[538]: <info>  [sleep-monitor] system is about to suspend
Aug 12 23:38:20 ModemManager[538]: <info>  [sleep-monitor] system is resuming
Aug 12 23:38:23 ModemManager[538]: <info>  [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:19.0': not supported by any plugin
Aug 12 23:38:23 ModemManager[538]: <info>  [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:1e.0/0000:03:00.0': not supported by any plugin
Aug 12 23:38:28 ModemManager[538]: <info>  [sleep-monitor] system is about to suspend
Aug 12 23:39:35 ModemManager[538]: <info>  [sleep-monitor] system is resuming
Aug 12 23:39:37 ModemManager[538]: <info>  [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:19.0': not supported by any plugin
Aug 12 23:39:37 ModemManager[538]: <info>  [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:1e.0/0000:03:00.0': not supported by any plugin
Aug 12 23:39:40 ModemManager[538]: <info>  [sleep-monitor] system is about to suspend
Aug 12 23:40:47 ModemManager[538]: <info>  [sleep-monitor] system is resuming
Aug 12 23:40:50 ModemManager[538]: <info>  [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:19.0': not supported by any plugin
Aug 12 23:40:50 ModemManager[538]: <info>  [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:1e.0/0000:03:00.0': not supported by any plugin
Aug 12 23:41:06 ModemManager[538]: <info>  [sleep-monitor] system is about to suspend
Aug 12 23:42:13 ModemManager[538]: <info>  [sleep-monitor] system is resuming
Aug 12 23:42:15 ModemManager[538]: <info>  [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:19.0': not supported by any plugin
Aug 12 23:42:15 ModemManager[538]: <info>  [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:1e.0/0000:03:00.0': not supported by any plugin
Aug 13 01:28:22 ModemManager[538]: <info>  caught signal, shutting down...
Aug 13 01:28:22 systemd[1]: Stopping Modem Manager...
Aug 13 01:28:22 ModemManager[538]: <info>  ModemManager is shut down
Aug 13 01:28:22 systemd[1]: ModemManager.service: Deactivated successfully.
Aug 13 01:28:22 systemd[1]: Stopped Modem Manager.

I have read through the whole log… but can’t really grasp what most of the log means… however according to the time of nic issue occurs… these lines of log should be written when the nic issue reoccurance

Aug 12 22:06:07 NetworkManager[488]: <info>  [1628798767.8368] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Aug 12 22:06:07 NetworkManager[488]: <info>  [1628798767.8369] manager: NetworkManager state is now ASLEEP
Aug 12 22:06:18 NetworkManager[488]: <info>  [1628798778.8218] manager: sleep: wake requested (sleeping: yes  enabled: yes)
Aug 12 22:06:18 NetworkManager[488]: <info>  [1628798778.8219] device (enp0s25): state change: activated -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Aug 12 22:06:18 NetworkManager[488]: <info>  [1628798778.8220] dhcp4 (enp0s25): canceled DHCP transaction
Aug 12 22:06:18 NetworkManager[488]: <info>  [1628798778.8220] dhcp4 (enp0s25): state changed extended -> terminated
Aug 12 22:06:18 NetworkManager[488]: <info>  [1628798778.8222] dhcp6 (enp0s25): canceled DHCP transaction
Aug 12 22:06:18 NetworkManager[488]: <info>  [1628798778.8222] dhcp6 (enp0s25): state changed bound -> terminated
Aug 12 22:06:18 NetworkManager[488]: <info>  [1628798778.9457] manager: NetworkManager state is now CONNECTED_GLOBAL
Aug 12 22:06:19 NetworkManager[488]: <info>  [1628798779.1429] manager: NetworkManager state is now DISCONNECTED
Aug 12 22:06:19 NetworkManager[488]: <info>  [1628798779.1437] device (enp3s0): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')

andrewysk · August 12, 2021, 11:52pm

Aug 12 22:06:18 NetworkManager[488]: <info>  [1628798778.9457] manager: NetworkManager state is now CONNECTED_GLOBAL

Does this log means it is connected to internet ?

Aug 12 22:06:19 NetworkManager[488]: <info>  [1628798779.1437] device (enp3s0): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')

Here is the device sleeping ?? That’s why nic down ? and not responding to “nmcli” command ?

megavolt · August 13, 2021, 12:15am

ok…

No idea which device this is: enp0s25 but enp3s0 is the one I saw in your inxi output (maybe the same device, but only renamed?)… however, I see this here:

It could be problem with ipv6, please disable it completely.

andrewysk · August 13, 2021, 12:20am

No, i have 2 ethernet card… 1 is the used, the other one is working but not used (enp3s0) . So the one show in inxi is the NIC that is plugged in (enp0s25) .

megavolt · August 13, 2021, 12:34am

So about “sleeping” problem… I guess it is the correct direction, but I have no idea how to awake it manually…

To see which port has which name… plugin the cable and type:

ip address show up

andrewysk · August 13, 2021, 12:36am

enp0s25 state UP ← i bet state UP means the NIC is plugged in.
enp3s0 state DOWN

ip address has same output as ip address show up

megavolt · August 13, 2021, 12:39am

Could you also post this info:

sudo ethtool enp0s25

megavolt · August 13, 2021, 12:41am

Yes… it means it is plugged in and connected.

andrewysk · August 13, 2021, 12:53am

[How to Disable IPv6 on Linux](Disable ipv6)
I did as in the instruction to disabled permanently ipv6 already.
Is this instruction on the website is good set of instruction ?

andrewysk · August 13, 2021, 12:55am

Apparently i don’t have this ethtool … install the package ?

andrewysk · August 13, 2021, 1:00am

$ sudo ethtool enp0s25
Settings for enp0s25:
        Supported ports: [ TP ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Supported pause frame use: No
        Supports auto-negotiation: Yes
        Supported FEC modes: Not reported
        Advertised link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Advertised pause frame use: No
        Advertised auto-negotiation: Yes
        Advertised FEC modes: Not reported
        Speed: 1000Mb/s
        Duplex: Full
        Auto-negotiation: on
        Port: Twisted Pair
        PHYAD: 1
        Transceiver: internal
        MDI-X: on (auto)
        Supports Wake-on: pumbg
        Wake-on: g
        Current message level: 0x00000007 (7)
                               drv probe link
        Link detected: yes

megavolt · August 13, 2021, 1:16am

This must be related to Wake on LAN, since it is activated:

You can deactivate it temporary with:

sudo ethtool -s enp0s25 wol d

But this is strange:

andrewysk:

Aug 12 22:06:18 NetworkManager[488]: <info>  [1628798778.9457] manager: NetworkManager state is now CONNECTED_GLOBAL
Aug 12 22:06:19 NetworkManager[488]: <info>  [1628798779.1429] manager: NetworkManager state is now DISCONNECTED

It has established a connection with enp0s25 but then 1sec after it is disconnected

andrewysk · August 13, 2021, 6:23am

Is there more verbose option for this log ? like… networkmanager or modemmanager -vvv verbose log which can shows most detail log ?

megavolt · August 13, 2021, 12:19pm

sudo nano /etc/NetworkManager/NetworkManager.conf

and put this in there:

[logging]
level=DEBUG

networkmanager.conf(5) - Linux man page

And restart the NetworkManager:

sudo systemctl restart NetworkManager

Also for the module, to increase kernel messages:

modinfo e100

sudo systemctl stop NetworkManager
sudo rmmod e100
sudo modprobe e100 debug=all
sudo systemctl start NetworkManager

The messages are here:

journalctl --dmesg --boot 0

(--follow if you need the logs of now)

andrewysk · August 28, 2021, 1:01pm

I have being on and off trying to understand what were the function of each steps you told me to do but i don’t get a solid answer from search.

modinfo e100

You told me to run " $ modinfo e100 " … from my studies, “modinfo” is just a simple command to show info of each load/unload able module in kernel. So, “e100” must be one of those module/ driver for network, because

$ modinfo e100
filename:       /lib/modules/5.12.19-1-MANJARO/kernel/drivers/net/ethernet/intel/e100.ko.xz

Then you want me to stop network manager, because any adding or subtration of “drivers/ module” can’t be done when it is in use.
Then you “unload” the module using “$ rmmod”
Then you load the e100 module with additional parameter “debug=all”

sudo modprobe e100 debug=all

1st of all, i have read thru a couple of modprobe command website; no “debug=all” available under “modprobe” command.
2ndly, i have not able to find a clear explaination of “e100” module on internet

Can you please explain ?
Thank you.

megavolt · August 28, 2021, 1:15pm

Shame on me It was a bit late, but correct is:

sudo modprobe e100 debug=16

The parameters come from:

modinfo e100

parm:           debug:Debug level (0=none,...,16=all) (int)
parm:           eeprom_bad_csum_allow:Allow bad eeprom checksums (int)
parm:           use_io:Force use of i/o access mode (int)

What clear explanation do you think of?

Something like this? The kernel’s command-line parameters — The Linux Kernel documentation

andrewysk · August 28, 2021, 11:04pm

I see… So “modinfo” does contribute some good data, i thought just for “fun” lol.

I meant how do you know it is “e100” modules that is todo with ethernet driver ? which, one can change priority of logging related to the module ? I can’t even locate e100 using the command:

$ lsmod | grep e100
$ whereis e100       
e100:
$ whatis e100  
e100: nothing appropriate.
$ pacman -Q e100
error: package 'e100' was not found

$ find /lib/modules/$(uname -r) -type f -name '*.ko*' | more | grep e100
/lib/modules/5.12.19-1-MANJARO/kernel/drivers/net/ethernet/intel/e100.ko.xz
/lib/modules/5.12.19-1-MANJARO/kernel/drivers/net/ethernet/intel/e1000e/e1000e.ko.xz
/lib/modules/5.12.19-1-MANJARO/kernel/drivers/net/ethernet/intel/e1000/e1000.ko.xz
/lib/modules/5.12.19-1-MANJARO/kernel/drivers/misc/eeprom/ee1004.ko.xz

I mean what if next time i got similar issue and wanted to get more log of other problem such bluetooth , or wifi or display module ? How one know which module is doing what related ?

megavolt · August 30, 2021, 2:10am

Because of your inxi output:

Here is a little trick:

sudo lspci -vvv -k -nn | sed -n "/Ethernet controller/,/Kernel modules/p"

It shrinks the output of lspci from line which contains “Ethernet controller” until the last line, which contains “Kernel modules”.

However… there you see pci devices in detail.

inxi is just a bit more compact:

inxi --network-advanced --admin --filter --width 80

Ok i try to keep it simple:

You have a problem with your audio device. Check which module is loaded for this device:

sudo lspci -v -k | sed -n "/Audio device/,/Kernel modules/p"

Example output:

00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD] FCH Azalia Controller (rev 01)
	Subsystem: ASUSTeK Computer Inc. Device 8445
	Flags: bus master, slow devsel, latency 32, IRQ 16
	Memory at fe100000 (64-bit, non-prefetchable) [size=16K]
	Capabilities: [50] Power Management version 2
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel
01:00.1 Audio device: NVIDIA Corporation GP107GL High Definition Audio Controller (rev a1)
	Subsystem: ZOTAC International (MCO) Ltd. Device 1454
	Flags: bus master, fast devsel, latency 0, IRQ 19
	Memory at fe080000 (32-bit, non-prefetchable) [size=16K]
	Capabilities: [60] Power Management version 3
	Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+
	Capabilities: [78] Express Endpoint, MSI 00
	Capabilities: [100] Advanced Error Reporting
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel

Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel

So now you know which driver/module is used.

Now check which parameter are available:

modinfo snd_hda_intel | grep parm

Lets say you have a problem with the power save function. Here you can disable it:

# unload the module
sudo rmmod snd_hda_intel

# check if it is still up:
lsmod | grep snd_hda_intel

# then load the module with a specific parameter
sudo modprobe snd_hda_intel power_save=0

Keep sure you restart at least all applications which depends on it. Fo example pulseaudio:

systemctl restart --user pulseaudio.service

This is only temporary. If you need this permanent to load on boot, add file for example here:

sudo nano /etc/modprobe.d/intel-no-powersave.conf

and put there

option  snd_hda_intel power_save=0

or blacklist the module

blacklist snd_hda_intel

so that it will be blocked and maybe another driver which fits the chipID will be loaded automatically.

Every module has its own parameters, so here you have to check what is possible.

To locate the filename, use modinfo:

modinfo e100 | grep filename

andrewysk · August 30, 2021, 12:51pm

This is the best, most comprehensive and friendly help i got since on manjaro forum.
Really appreciate your time and help.

Add in : lsmod & modinfo to find the dependencies
https://www.xmodulo.com/how-to-check-kernel-module-dependencies-on-linux.html

system · September 2, 2021, 2:52am

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.