I've been doing testing on a setup for my G4L project to get both legacy and UEFI booting working on a single setup. Have that working just fine now with help from this list. Been testing with my Dell 9020 machine that has Windows 10 as the hard disks OS that it came with. My 5 other machines have Fedora 33. Everything works fine, except. Sometimes I miss hitting the F12 key to select the flash for UEFI or standard USB boot from flash. Thus the machine boots to windows. Problem, if I do a restart after the windows boots and go to the my projects linux, it loads fine, but it will not get IP from dhcpd server of my wifi router. Have to do a full power off on system. Then it will boot ok. Found a web site that seemed to identify problem as windows doing something to the nic on shutdown that causes the issue. The sites solution was the echo a 1 to the reset value for the PCI device for the nic. Came up with a process that does that easy, but doesn't seem to work. Might be after some time, the issue resolves, but thought the reset would be a quick solution. Shutting down the interface with ifconfig doesn't reset it either? Wonder if there is a command line process that someone knows of? I can manually set an ipaddress, and that works fine, but you have to know the network range. Don't have network manager in the build, so right now solution is to do a poweroff, and then power back on. Thanks. Got the UEFI booting just fine, and have regular boot running with grub4dos just fine. Systems using same exact kernel and ramdisk on the flash.
Thanks again. Have a great day.
I would look at the various settings that ethtool controllers.
You might dump all of the ethtool settings when it is working, and then do the same when it is not working and see if there is a setting.
I have seen before were OS'es seem to assume some state in the nic cards (clean powerup) and when that state is not right(reboot with power up) they don't set set and either it does not work or it fails in weird ways.
the ethtool -t offline is often useful because it seems to reset the nic, it is useful when the "reset" is not supported or does not work. There is also a reset. The biggest issue with the ethtool settings is not all nic cards support and/or have code for all of the functions so it is somewhat trial and error.
On Mon, Sep 20, 2021 at 11:05 AM Michael D. Setzer II via users users@lists.fedoraproject.org wrote:
I've been doing testing on a setup for my G4L project to get both legacy and UEFI booting working on a single setup. Have that working just fine now with help from this list. Been testing with my Dell 9020 machine that has Windows 10 as the hard disks OS that it came with. My 5 other machines have Fedora 33. Everything works fine, except. Sometimes I miss hitting the F12 key to select the flash for UEFI or standard USB boot from flash. Thus the machine boots to windows. Problem, if I do a restart after the windows boots and go to the my projects linux, it loads fine, but it will not get IP from dhcpd server of my wifi router. Have to do a full power off on system. Then it will boot ok. Found a web site that seemed to identify problem as windows doing something to the nic on shutdown that causes the issue. The sites solution was the echo a 1 to the reset value for the PCI device for the nic. Came up with a process that does that easy, but doesn't seem to work. Might be after some time, the issue resolves, but thought the reset would be a quick solution. Shutting down the interface with ifconfig doesn't reset it either? Wonder if there is a command line process that someone knows of? I can manually set an ipaddress, and that works fine, but you have to know the network range. Don't have network manager in the build, so right now solution is to do a poweroff, and then power back on. Thanks. Got the UEFI booting just fine, and have regular boot running with grub4dos just fine. Systems using same exact kernel and ramdisk on the flash.
Thanks again. Have a great day. _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
On 20 Sep 2021 at 11:34, Roger Heflin wrote:
From: Roger Heflin rogerheflin@gmail.com Date sent: Mon, 20 Sep 2021 11:34:09 -0500 Subject: Re: Warm boot after Windows 10 boot - I'm not getting a dhcpd address from router? To: Community support for Fedora users users@lists.fedoraproject.org Copies to: "Michael D. Setzer II" mikes@guam.net Send reply to: Community support for Fedora users users@lists.fedoraproject.org
I would look at the various settings that ethtool controllers.
You might dump all of the ethtool settings when it is working, and then do the same when it is not working and see if there is a setting.
I have seen before were OS'es seem to assume some state in the nic cards (clean powerup) and when that state is not right(reboot with power up) they don't set set and either it does not work or it fails in weird ways.
the ethtool -t offline is often useful because it seems to reset the nic, it is useful when the "reset" is not supported or does not work. There is also a reset. The biggest issue with the ethtool settings is not all nic cards support and/or have code for all of the functions so it is somewhat trial and error.
Thanks for the quick reply. Think I figured out my error. I had got it to work, and wrote it down. Then I build a new iso where I typed in what I had written down. This is what it was suppose to be: echo 1 > $(find . | grep $(lspci | grep -i ethernet | cut -f1 -d\ ) |grep reset)
But I had note put the space between the 1 and the >, so was getting an error about argument.
So, have tested it after a warm boot from Windows, and it does reset the ethernet pci controller. Might need to modify it to handle machines that might have more than one nic. Once had a server that had 9 ethernet nics in it, but that was long ago.
Thanks again.
On Mon, Sep 20, 2021 at 11:05 AM Michael D. Setzer II via users users@lists.fedoraproject.org wrote:
I've been doing testing on a setup for my G4L project to get both legacy and UEFI booting working on a single setup. Have that working just fine now with help from this list. Been testing with my Dell 9020 machine that has Windows 10 as the hard disks OS that it came with. My 5 other machines have Fedora 33. Everything works fine, except. Sometimes I miss hitting the F12 key to select the flash for UEFI or standard USB boot from flash. Thus the machine boots to windows. Problem, if I do a restart after the windows boots and go to the my projects linux, it loads fine, but it will not get IP from dhcpd server of my wifi router. Have to do a full power off on system. Then it will boot ok. Found a web site that seemed to identify problem as windows doing something to the nic on shutdown that causes the issue. The sites solution was the echo a 1 to the reset value for the PCI device for the nic. Came up with a process that does that easy, but doesn't seem to work. Might be after some time, the issue resolves, but thought the reset would be a quick solution. Shutting down the interface with ifconfig doesn't reset it either? Wonder if there is a command line process that someone knows of? I can manually set an ipaddress, and that works fine, but you have to know the network range. Don't have network manager in the build, so right now solution is to do a poweroff, and then power back on. Thanks. Got the UEFI booting just fine, and have regular boot running with grub4dos just fine. Systems using same exact kernel and ramdisk on the flash.
Thanks again. Have a great day. _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
On 9/20/21 11:13 AM, Michael D. Setzer II via users wrote:
So, have tested it after a warm boot from Windows, and it does reset the ethernet pci controller. Might need to modify it to handle machines that might have more than one nic. Once had a server that had 9 ethernet nics in it, but that was long ago.
If it's needed at every boot, make a one-liner script out of it that runs at boot. Even if it's only needed after warm boots, it can't hurt to have it run after cold ones too.
On Tue, 2021-09-21 at 02:04 +1000, Michael D. Setzer II via users wrote:
Sometimes I miss hitting the F12 key to select the flash for UEFI or standard USB boot from flash. Thus the machine boots to windows.
You might have a hardware solution for that. On my UEFI, it can provide the boot menu, and it can configure the timeout. No fighting with GRUB or Windows configuration. (Though in my case, the choices are really only boot Linux or an install DVD-ROM).
Problem, if I do a restart after the windows boots and go to the my projects linux, it loads fine, but it will not get IP from dhcpd server of my wifi router. Have to do a full power off on system. Then it will boot ok.
I have motherboards with wonky ethernet, too:
If the cable is unplugged, or an ethernet switch gets de-powered, the network must be stopped, then restarted, manually (I use the network icon in the MATE taskbar to disconnect, wait a moment, then reconnect to a network). It just repeatedly hiccups if you don't do that. On one PC the network interface is manually preconfigured with a static IP, on the other it uses DHCP.
On 21 Sep 2021 at 18:47, Tim via users wrote:
Subject: Re: Warm boot after Windows 10 boot - I'm not getting a dhcpd address from router? To: users@lists.fedoraproject.org Date sent: Tue, 21 Sep 2021 18:47:44 +0930 Send reply to: Community support for Fedora users users@lists.fedoraproject.org From: Tim via users users@lists.fedoraproject.org Copies to: Tim ignored_mailbox@yahoo.com.au
On Tue, 2021-09-21 at 02:04 +1000, Michael D. Setzer II via users wrote:
Sometimes I miss hitting the F12 key to select the flash for UEFI or standard USB boot from flash. Thus the machine boots to windows.
You might have a hardware solution for that. On my UEFI, it can provide the boot menu, and it can configure the timeout. No fighting with GRUB or Windows configuration. (Though in my case, the choices are really only boot Linux or an install DVD-ROM).
Problem, if I do a restart after the windows boots and go to the my projects linux, it loads fine, but it will not get IP from dhcpd server of my wifi router. Have to do a full power off on system. Then it will boot ok.
I have motherboards with wonky ethernet, too:
If the cable is unplugged, or an ethernet switch gets de-powered, the network must be stopped, then restarted, manually (I use the network icon in the MATE taskbar to disconnect, wait a moment, then reconnect to a network). It just repeatedly hiccups if you don't do that. On one PC the network interface is manually preconfigured with a static IP, on the other it uses DHCP.
I have 5 machines that are linux only, and just the one that is Windows. Been using it to test setup of my G4L project for regular usb boot using grub4dos, and UEFI boot using grub2. Both work fine, but the issue is windows puts the nic in some state when it does a warm restart that messages the dhcpc setup from the linux client. Added the following line to the script that does the dhcpc setup.
echo 1 > $(find /sys | grep $(lspci | grep -i ethernet | cut -f1 -d\ ) |grep reset)
finds the pci device for the ethernet, and then sets the reset to 1
That seems to handle the process of fixing what windows breaks.. Will have to look at modifying it to handle systems that might have more than 1 ethernet device?
Thanks for the reply.
--
uname -rsvp Linux 3.10.0-1160.42.2.el7.x86_64 #1 SMP Tue Sep 7 14:49:57 UTC 2021 x86_64
Boilerplate: All unexpected mail to my mailbox is automatically deleted. I will only get to see the messages that are posted to the mailing list.
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure