lost my ethernet, beginning troubleshooting

brent

Rhetorical question #1. What good is systemctl? Can't even turn on a service...
sudo systemctl list-unit-files --type=service --state=enabled,disabled
ModemManager.service disabled enabled
NetworkManager-dispatcher.service enabled enabled
NetworkManager-wait-online.service enabled enabled
NetworkManager.service enabled enabled

OK...ModemManager, eh? Well if it's all I got right now...
systemctl stop ModemManager.service
~ $ sudo systemctl start ModemManager.service
$ sudo systemctl reload ModemManager.service
Failed to reload ModemManager.service: Job type reload is not applicable for unit ModemManager.service.
~ $ sudo systemctl restart ModemManager.service
~ $ sudo systemctl clean ModemManager.service
Failed to clean unit ModemManager.service: Unit is not inactive or has pending job.
~ $ sudo systemctl status ModemManager.service
● ModemManager.service - Modem Manager
Loaded: loaded (/usr/lib/systemd/system/ModemManager.service; disabled; vendor preset: enabled)
Active: active (running) since Sun 2022-04-24 11:41:37 MST; 1min 36s ago
Main PID: 5636 (ModemManager)
Tasks: 3 (limit: 19054)
Memory: 2.6M
CPU: 54ms
CGroup: /system.slice/ModemManager.service
└─5636 /usr/sbin/ModemManager

Apr 24 11:41:37 workstation systemd[1]: Stopping Modem Manager...
Apr 24 11:41:37 workstation ModemManager[5609]: <info> ModemManager is shut down
Apr 24 11:41:37 workstation ModemManager[5636]: <info> ModemManager (version 1.18.2) starting in system bus...
Apr 24 11:41:37 workstation systemd[1]: ModemManager.service: Deactivated successfully.
Apr 24 11:41:37 workstation systemd[1]: Stopped Modem Manager.
Apr 24 11:41:37 workstation systemd[1]: Starting Modem Manager...
Apr 24 11:41:37 workstation systemd[1]: Started Modem Manager.
Apr 24 11:41:39 workstation ModemManager[5636]: <info> [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0>
Apr 24 11:41:39 workstation ModemManager[5636]: <info

??????
How could it simultaneously be active and inactive?
There is no --verbose flag in systemctl so I don't know if I actually did anything...
I have the Intel e1000e ethernet driver. I have to find a command to see if it's active. I journey on.

Inxi says the driver is fine I think:
Network:
Device-1: Intel Ethernet I218-V driver: e1000e
IF: eno1 state: up speed: 1000 Mbps duplex: full mac: <filter>

brent

gonna chase some clues at the bottom of this output:
sudo systemctl status NetworkManager

● NetworkManager.service - Network Manager
Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled)
Drop-In: /usr/lib64/systemd/system/NetworkManager.service.d
└─NetworkManager-ovs.conf
Active: active (running) since Sun 2022-04-24 10:59:19 MST; 1h 0min ago
Docs: man:NetworkManager(8)
Main PID: 872 (NetworkManager)
Tasks: 5 (limit: 19054)
Memory: 17.5M
CPU: 8.522s
CGroup: /system.slice/NetworkManager.service
├─ 872 /usr/sbin/NetworkManager --no-daemon
├─1752 /usr/bin/dhclient -d -q -sf /usr/lib64/network-manager/nm-dhcp-helper -pf /var/run/NetworkManager/dhclient-wlp6>
└─6061 /usr/bin/dhclient -d -q -sf /usr/lib64/network-manager/nm-dhcp-helper -pf /var/run/NetworkManager/dhclient-eno1>

Apr 24 11:57:54 workstation NetworkManager[872]: <info> [1650826674.6068] dhcp4 (eno1): nameserver '192.168.0.1'
Apr 24 11:57:54 workstation NetworkManager[872]: <info> [1650826674.6068] dhcp4 (eno1): nameserver '205.171.2.25'
Apr 24 11:57:54 workstation NetworkManager[872]: <info> [1650826674.6068] dhcp4 (eno1): domain name 'Home'
Apr 24 11:57:54 workstation NetworkManager[872]: <info> [1650826674.6068] dhcp4 (eno1): state changed unknown -> extended, address>
Apr 24 11:57:54 workstation NetworkManager[872]: <info> [1650826674.6082] device (eno1): state change: ip-config -> ip-check (reas>
Apr 24 11:57:54 workstation NetworkManager[872]: <info> [1650826674.6112] device (eno1): state change: ip-check -> secondaries (re>
Apr 24 11:57:54 workstation NetworkManager[872]: <info> [1650826674.6114] device (eno1): state change: secondaries -> activated (r>
Apr 24 11:57:54 workstation dhclient[6061]: bound to 192.168.0.15 -- renewal in 34364 seconds.
Apr 24 11:57:54 workstation NetworkManager[872]: <info> [1650826674.6946] device (eno1): Activation: successful, device activated.
Apr 24 11:57:55 workstation NetworkManager[872]: <info> [1650826675.1093] policy: set 'Profile 1' (eno1) as default for IPv4 routi>
lines 1-25/25 (END)

brent

driver and connection look healthy here as well:
~ lshw
*-network
description: Ethernet interface
product: Ethernet Connection (2) I218-V
vendor: Intel Corporation
physical id: 19
bus info: pci@0000:00:19.0
logical name: eno1
version: 05
serial: 44:8a:5b:d1:fd:6d
size: 1Gbit/s
capacity: 1Gbit/s
width: 32 bits
clock: 33MHz
capabilities: pm msi bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=e1000e driverversion=5.15.32-213.current duplex=full firmware=0.1-4 ip=192.168.0.15 latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s
resources: irq:38 memory:f7200000-f721ffff memory:f7238000-f7238fff ioport:f040(size=32)
*-usb:1
description: USB controller
product: 8 Series/C220 Series Chipset Family USB EHCI #2
vendor: Intel Corporation
physical id: 1a
bus info: pci@0000:00:1a.0
version: 05
width: 32 bits
clock: 33MHz
capabilities: pm debug ehci bus_master cap_list
configuration: driver=ehci-pci latency=0
resources: irq:16 memory:f7237000-f72373ff

Network Manager applet shows a wired connection but won't show the profile when clicked on.

All signs are I have a healthy wired internet......but netstat show NO packets gived/received....no internet...no pinging of anykind....
....where in the pipeline am I not looking?

elfprince

brent Router reboot?

brent

tried that last night but after all the moves I've made today, it will not hurt to reboot OS and Modem. I think Artix bit me and assumed control of the hardware (network manager).
Windows and Artix share a disk but even if I unplugged separate-disk-Solus for all this nothing could shield it from someone going rogue in the intel modem card....

....sudo modprobe e1000e allegedly makes the driver wake up (e1000e is the Intel modem driver).
systemctl has no --verbose so no knowing if any of my moves hurt or helped...

when in doubt reboot🙂....
a drum roll and a lager please.....

Axios

brent Every os has its issues even win7 on this new computer I got.
Just getting tired of the wierd ones..

brent

Axios Just getting tired of the weird ones..

me too. is exhausting anymore

brent

Played with the Solus problem this in the morning. walked away. had to work from Windows (vomit) half the day and figure out why arch is being surly...
...anyways I took @elfprince 's advice of a simple modem reboot/unplug/let gremlins leave....when I returned to Solus my Wired Connection was restored. Even though it shared the Intel Modem Driver, Windows was never affected by the absence of packets and connection elsewhere. Of course😉.
Dig it.
Kindly mark SOLVED, thank you.

Harvey

Root cause could have been many things as I do not have the complete context but I will take this time to remind people dual booting with Windows you need to disable fast startup or it can cause issues with devices not working in Linux. Additionally sleep states can cause data loss when dual booting https://wiki.archlinux.org/title/Dual_boot_with_Windows#Fast_Startup_and_hibernation

Which is one of the many reasons I recommend using VMs where possible instead of dual/multi booting.

brent

Harvey in this case its win on one drive and solus on another drive and a 'dual boot' that exists only in quotation marks because boot order is only decided by boot menu window on an F11 spam after boot. If I ignore that then Solus boots up default. Also, my power settings in both operating systems have sleep/hibernate/screen saver disabled. No sleep/hibernate ever. Also my bios has no Secure Boot setting to enable/disable. My MSI bios is a weirdo bios that claims it is both UEFI and Legacy Enabled but in reality is just UEFI.
But Win and Artix (arch) do share a drive and are a true dual boot (both separated in boot menu that I have to manually call up) and what's interesting about your link is this:
"Windows cannot read filesystems such as ext4 by default that are commonly used for Linux. These filesystems do not have to be considered, unless you install a Windows driver for them.....The only issue with regards to disabling UEFI Secure Boot support is that it requires physical access to the system to disable secure boot option in the firmware setup, as Microsoft has explicitly forbidden presence of any method to remotely or programmatically (from within OS) disable secure boot in all Windows 8/8.1 and above pre-installed systems" (emphasis mine).

What is my point? If Windows can shield itself from outside Firmware Interference then that would explain any network disabling that arch (or it's idiot user myself) did not effect Windows. And that IS the reason it affected Solus one innocent disk away.

You are right (wetgeek says it all the time) that the only good way to distrohop is VM...but there is no romance or adventure in VM...I'm getting at the age where I'm getting sick of the headaches though🙂

tomscharbach

brent I'm getting at the age where I'm getting sick of the headaches though🙂

When it comes to computers, pain-avoidance is a good thing. LTS (Linux Tinkerer's Syndrome) is not compatible with pain-avoidance. Save the romance for the object of your desire, sky dive for adventure. 😆

brent

tomscharbach LTS (Linux Tinkerer's Syndrome) is not compatible with pain-avoidance

that should have been in big shiny letters, repeated as mantra, and lit up in the sky with klieg lights before I signed up for this post-windows tour...🙂 edit.....and I still would have done it my way...

tomscharbach

brent I still would have done it my way ...

I think that just about every Linux user goes through an Linux Tinkerer's Syndrome stage sooner or later. I did, despite 30+ years experience in a professional IT setting where "thoroughly understand what you are doing before you do it" was hammered into my head over and over again. After I burned myself enough times during the LTS stage, I eventually returned to a marginal level of sanity, reserving my LTS adventures to VM's.