I checked

/usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf.  The link you 
mentioned was the only line in the file.
 I commented out the line.  It now reads [keyfile]
#unmanaged-devices=*,except:type:wifi,except:type:gsm,except:type:cdma

I ran systemctl reload NetworkManager and shut down.  I booted the machine 
again, no network. I ran ifconfig and it didn't even shoe the network adapter.
delboy@ladmo:~$ ifconfig
lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 1289  bytes 103269 (103.2 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 1289  bytes 103269 (103.2 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

After I rebooted, the network was back and ifconfig showed lo and the ethernet 
adapter.

eno1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500        inet 192.168.1.2  netmask 255.255.255.0  broadcast 192.168.1.255        inet6 fe80::1480:79c7:4830:8495  prefixlen 64  scopeid 0x20<link>         ether 34:17:eb:d0:34:55  txqueuelen 1000  (Ethernet)        RX packets 1528  bytes 618600 (618.6 KB)        RX errors 0  dropped 0  overruns 0  frame 0        TX packets 1453  bytes 198021 (198.0 KB)        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0        device interrupt 20  memory 0xf7200000-f7220000

On 9/23/22 13:57, Joseph Sinclair via PLUG-discuss wrote:
I've discovered a similar issue just yesterday.  I hunted it down and found 
that the cause, for me at least, was in the static NetworkManager configuration.
NetworkManager configuration now marks *all* interfaces as unmanaged *except* 
WiFi and Cellular, basically all non-wireless interfaces are prevented from 
being activated.  Apparently some genius at Ubuntu decided nobody uses wired 
connections.
In /usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf, check the line that 
starts with "unmanaged-devices".  If it reads as follows, consider modifying or 
commenting out the line.
     unmanaged-devices=*,except=type:wifi,except=type:gsm,except=type:cdma

If you make changes, run "systemctl reload NetworkManager" to update the 
running daemon.


On 2022-09-23 12:04 PM, T Zack Crawford via PLUG-discuss wrote:
I am very interested in the answer because my desktop does the same thing if I 
tell it to hibernate, boot into my windows dual boot, and reboot back into 
linux. I can regain network access again by hibernating again and booting back 
into linux directly (no windows). Pretty annoying because it takes a solid 2-5 
minutes to shut down when hibernating. At least it still does the job, just 
with delay.

This only happens if I try hibernating and then boot into windows (not full 
shutdown, not hibernate and boot directly to linux). It has always happened 
since I enabled hibernation (arch wiki instructions). Having Systemd restart 
NetworkManager does nothing. Setting up a new network configuration with 
networkmanager does not solve it. This is with my motherboard ethernet and my 
wireless USB adapter. I spent some good energy trying to figure it out, but 
never did.


Did you update kernels today? What if you downgrade?

Put the solution as a boot script. Or at least bash profile instead of run 
commands (otherwise it will run every time you spawn a terminal shell)

Sep 23, 2022 11:14:35 Jim via PLUG-discuss<plug-discuss@lists.phxlinux.org>:

A few months ago my Dell Optiplex 7010 running Ubuntu 20.04 started booting up 
without the network.  I'd reboot the machine and  the network was there.  If I 
shut down the machine and turned it on again, no network.  I thought something 
was wrong with the built in ethernet adapter, so I bought a usb adapter, 
disabled the built in one and the problem went away until today.  Now it's 
happening with the usb ethernet adapter.  Rebooting the machine fixes the 
problem gets the network up and running.  If I start with a cold boot and 
reboot at the grub screen, I get the network.  I have 3 SSDs and 2 HDDs.  I 
have the same video card that I had before this problem first showed itself.  
It's a GeForce GT 710.

I looked online and found something telling of other people who have had this 
problem.  They disconnected video cards and went back to the built in video 
(display port), and removed hard drives that had been added later and this 
fixed the problem.  The ultimate solution was to replace the power supply.  I 
disconnected one SSD and the 2 HDDs.  I don't have anything that can use a 
display port, so I left the video card in place.  All I had connected were  2 
SSDs.  One it boots from and my home directory is on the other.  The problem 
still showed itself when I booted the machine, so I shut down and plugged in 
everything again.  This thing has a 240 watt power supply.  Do power supplies 
go band in such a way they don't produce the amount of power they used to?

Any ideas what it might be?  Is there a command that would tell the system to 
set up the network again?  If there is, I could put it in the .bashrc until I 
get this fixed.

Thanks

---------------------------------------------------
PLUG-discuss mailing list:PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
https://lists.phxlinux.org/mailman/listinfo/plug-discuss
---------------------------------------------------
PLUG-discuss mailing list:PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
https://lists.phxlinux.org/mailman/listinfo/plug-discuss


---------------------------------------------------
PLUG-discuss mailing list:PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
https://lists.phxlinux.org/mailman/listinfo/plug-discuss
---------------------------------------------------
PLUG-discuss mailing list: PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
https://lists.phxlinux.org/mailman/listinfo/plug-discuss

Reply via email to