Re: my favorite game
DUUUDE. I was so expecting my little processor not being able to handle this game (oolite) but it seems to do fine. --- 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
Re: Boot up from cold boot no network
I think I should stay with Ubuntu for now, but thanks. I've found it's often best to not overcomplicate things. On 9/23/22 15:54, Steve Litt via PLUG-discuss wrote: On Fri, 2022-09-23 at 12:04 -0700, 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. 2 to 5 minutes to shut down isn't unusual with systemd. Also, Ubuntu is ultra friendly and hardware tolerant, but there's a cost: Layers upon layers upon layers of abstraction, making troubleshooting a needle in a haystack. Also, NetworkManager is kind of twitchy and overly dependent on dbus. If you no longer need the training wheels Ubuntu provides, I suggest you switch to Devuan, or if you're comfortable with a close to the metal Linux with an excellent rolling release packaging system, Void Linux. Both of these get rid of systemd. I suggest you use runit as your init system: It's much better than sysvinit. Devuan has a package for it and Void comes with runit straight from the factory. If you use Devuan, you might want to use sysvinit as your PID1, and then supervise your daemons with runit. If your computer has a fixed IP address, you can set it with the upnet.sh shellscript performed as the last thing in the boot (put it in rc.local). For the long version of upnet.sh that's good to use with Qemu virtual machines, see http://troubleshooters.com/linux/qemu/nobs.htm#hostnetworking . For a short and to the point upnet.sh, see the following and modify as necessary: === #!/bin/sh # MAKE SURE IP FORWARDING IS ENABLED echo 1 > /proc/sys/net/ipv4/ip_forward # DEAL WITH HOSTNAME AND LOCALHOST hostname=`grep -v "^\s*#" /etc/hostname | head -n1` ip link set dev lo up # UNDO ANY POSSIBLE STUFF FROM PREVIOUS UPNET.SH ip link set dev tap0 down brctl delif br0 tap0 ip link del tap0 ip link set dev br0 down ip addr del 192.168.0.102/24 dev br0 ip addr del 192.168.0.2/24 dev br0 brctl delbr br0 ip link set dev enp40s0 down ip addr del 192.168.0.102/24 dev enp40s0 ip addr del 192.168.0.2/24 dev enp40s0 # BRING UP enp40s0 #ip addr add 192.168.0.2/24 dev enp40s0 #ip addr add 192.168.0.102/24 dev enp40s0 ip link set dev enp40s0 up #ip route add default via 192.168.0.1 ### GET br0 UP AND RUNNING WITH RIGHT IP ADDRESSES ip link add name br0 type bridge ip link set dev enp40s0 master br0 ip addr add 192.168.0.2/24 dev br0 ip addr add 192.168.0.102/24 dev br0 ip link set dev br0 up ip route add default via 192.168.0.1 ### DO THE TUN/TAP STUFF ip tuntap add tap0 mode tap brctl addif br0 tap0 #ip addr add 192.168.0.66/24 dev tap0 ip link set dev tap0 up == The nice thing about the preceding is it's portable between distros. You can even use it in Ubuntu to restore your static network connectivity if if vanishes. Note that if you're not using taps or bridges you can eliminate a lot of it, but you'll need to uncomment a couple things. Obviously, you'll need to change IP addresses to your desired network device name, static IP and default route. HTH, SteveT --- 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
Re: Boot up from cold boot no network
The onboard nic is a 82579LM Gigabit Network Connection (Lewisville) vendor: Intel Corporation The driver is e1000e. When this nic began acting up a few months ago, I started using the usb adapter. When it started acting up, I removed it and went back to the onboard nic. ip link showed : 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 so ip neighbor showed nothing. ip address: 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever tcpdump did nothing. Joseph Sinclair asked if I upgraded or downgraded the kernel. I hadn't upgraded the kernel unless it did that when I upgraded to Kubuntu 22.04. I ran journalctl -xe after it booted up without the network and with it. I wouldn't know what to look for. If anyone else wants to have a look, I've put version on google drive. without network https://drive.google.com/file/d/1tPf-2wzsAdN9YL1fbIt0gbJu082YCqUU/view?usp=sharing with network https://drive.google.com/file/d/1_dc12Loro0D4dCe8_kodqIj3GKTQOspf/view?usp=sharing On 9/23/22 14:00, Michael Butash via PLUG-discuss wrote: I've used a lot of usb-based devices, and still do technically with a thunderbolt dock for like the past 5 years, and not really run into this on either ubuntu or arch. I've run into some weirdness before though with wired or wireless nics. Basic linux network 101 applies... test it like a network engineer, layer 1-7. use "ip link" to see the state of of the physical nic, or verify layer 1 use "ip neighbor" to verify you see mac forwarding ala arp table, or layer 2/3 use "ip address" to verify exactly that, verifying dhcp or static configs take place for layer 3 use "iftop" or "tcpdump" to see what traffic is sending, and if any is coming back assuming your nic has link for layer 2-7 Aside from that probably a kernel/firmware thing. Use journalctl -xe or -b options to show you boot and logs (as root) of what happens around the events with your nic. It could be some firmware bug, realtek's used to be terrible cursed names, but really haven't a problem for me in the past 5-10 years I'd say, and you're hard pressed to find a usb nic that *isn't* a realtek. You can probably rmmod and insmod the realtek driver too as long as something isn't using it. If it's busted, it should not be used, but stranger things happen, especially if firmware is hung in a funky way, which is usually what would always happen with them. -mb On Fri, Sep 23, 2022 at 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 : > 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
Re: Boot up from cold boot no network
On Fri, 2022-09-23 at 12:04 -0700, 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. 2 to 5 minutes to shut down isn't unusual with systemd. Also, Ubuntu is ultra friendly and hardware tolerant, but there's a cost: Layers upon layers upon layers of abstraction, making troubleshooting a needle in a haystack. Also, NetworkManager is kind of twitchy and overly dependent on dbus. If you no longer need the training wheels Ubuntu provides, I suggest you switch to Devuan, or if you're comfortable with a close to the metal Linux with an excellent rolling release packaging system, Void Linux. Both of these get rid of systemd. I suggest you use runit as your init system: It's much better than sysvinit. Devuan has a package for it and Void comes with runit straight from the factory. If you use Devuan, you might want to use sysvinit as your PID1, and then supervise your daemons with runit. If your computer has a fixed IP address, you can set it with the upnet.sh shellscript performed as the last thing in the boot (put it in rc.local). For the long version of upnet.sh that's good to use with Qemu virtual machines, see http://troubleshooters.com/linux/qemu/nobs.htm#hostnetworking . For a short and to the point upnet.sh, see the following and modify as necessary: === #!/bin/sh # MAKE SURE IP FORWARDING IS ENABLED echo 1 > /proc/sys/net/ipv4/ip_forward # DEAL WITH HOSTNAME AND LOCALHOST hostname=`grep -v "^\s*#" /etc/hostname | head -n1` ip link set dev lo up # UNDO ANY POSSIBLE STUFF FROM PREVIOUS UPNET.SH ip link set dev tap0 down brctl delif br0 tap0 ip link del tap0 ip link set dev br0 down ip addr del 192.168.0.102/24 dev br0 ip addr del 192.168.0.2/24 dev br0 brctl delbr br0 ip link set dev enp40s0 down ip addr del 192.168.0.102/24 dev enp40s0 ip addr del 192.168.0.2/24 dev enp40s0 # BRING UP enp40s0 #ip addr add 192.168.0.2/24 dev enp40s0 #ip addr add 192.168.0.102/24 dev enp40s0 ip link set dev enp40s0 up #ip route add default via 192.168.0.1 ### GET br0 UP AND RUNNING WITH RIGHT IP ADDRESSES ip link add name br0 type bridge ip link set dev enp40s0 master br0 ip addr add 192.168.0.2/24 dev br0 ip addr add 192.168.0.102/24 dev br0 ip link set dev br0 up ip route add default via 192.168.0.1 ### DO THE TUN/TAP STUFF ip tuntap add tap0 mode tap brctl addif br0 tap0 #ip addr add 192.168.0.66/24 dev tap0 ip link set dev tap0 up == The nice thing about the preceding is it's portable between distros. You can even use it in Ubuntu to restore your static network connectivity if if vanishes. Note that if you're not using taps or bridges you can eliminate a lot of it, but you'll need to uncomment a couple things. Obviously, you'll need to change IP addresses to your desired network device name, static IP and default route. HTH, SteveT --- 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
Re: Boot up from cold boot no network
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 mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10 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 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 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 0xf720-f722 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: 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 syst
Re: Boot up from cold boot no network
I've used a lot of usb-based devices, and still do technically with a thunderbolt dock for like the past 5 years, and not really run into this on either ubuntu or arch. I've run into some weirdness before though with wired or wireless nics. Basic linux network 101 applies... test it like a network engineer, layer 1-7. use "ip link" to see the state of of the physical nic, or verify layer 1 use "ip neighbor" to verify you see mac forwarding ala arp table, or layer 2/3 use "ip address" to verify exactly that, verifying dhcp or static configs take place for layer 3 use "iftop" or "tcpdump" to see what traffic is sending, and if any is coming back assuming your nic has link for layer 2-7 Aside from that probably a kernel/firmware thing. Use journalctl -xe or -b options to show you boot and logs (as root) of what happens around the events with your nic. It could be some firmware bug, realtek's used to be terrible cursed names, but really haven't a problem for me in the past 5-10 years I'd say, and you're hard pressed to find a usb nic that *isn't* a realtek. You can probably rmmod and insmod the realtek driver too as long as something isn't using it. If it's busted, it should not be used, but stranger things happen, especially if firmware is hung in a funky way, which is usually what would always happen with them. -mb On Fri, Sep 23, 2022 at 12:04 PM T Zack Crawford via PLUG-discuss < plug-discuss@lists.phxlinux.org> 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
Re: Boot up from cold boot no network
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 : > >> 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 > signature.asc Description: OpenPGP digital signature --- 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
Re: Boot up from cold boot no network
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 : > 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
Boot up from cold boot no network
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
