On 20 Sep 2021 at 11:34, Roger Heflin wrote:
From: Roger Heflin <rogerheflin@xxxxxxxxx>
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@xxxxxxxxxxxxxxxxxxxxxxx>
Copies to: "Michael D. Setzer II" <mikes@xxxxxxxx>
Send reply to: Community support for Fedora
users <users@xxxxxxxxxxxxxxxxxxxxxxx>
> 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@xxxxxxxxxxxxxxxxxxxxxxx> 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@xxxxxxxxxxxxxxxxxxxxxxx
> > To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
> > 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@xxxxxxxxxxxxxxxxxxxxxxx
> > Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
> _______________________________________________
> users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
> 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@xxxxxxxxxxxxxxxxxxxxxxx
> Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
_______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
