I am slowly figuring things out with this situation. If I boot into 42.3, knoppix 8.1 or windows 10 build 1703 from a cold, meaning uplugged machine I have internet. From either 42.3 or knoppix I can reboot (without turning off) into windows and have internet. The problem occurs when I reboot from windows into 42.3 or knoppix without unplugging, then I have no internet. Temporary hack for now is to turn off, unplug, and count to 20 when going from windows to 42.3 or knoppix. I can go from either 42.3 or knoppix to the other without unplugging and not lose internet. Just when you throw windows into the mix. Not sure why this happens but would love to get it fixed. Dave On Tue, Oct 10, 2017 at 10:13 AM, Anton Aylward wrote:

On 10/10/17 08:24 AM, Carlos E. R. wrote:

...

Or there may be a problem initializing your network hardware, and knopix knows how to do it, and the current package you have doesn't. So if you reboot from one to the other without powering off, it keeps. Might also happen with Windows.

Yes, Knoppix is probably the most resilient version of Linux I've ever encountered, though I've dropped off research in that area this last year or so. What Dave says makes me think that knoppix hasn't lost it :-)

I suspect that it might be a timing problem. It might be that a change, be it to the kernel or an initialization that the systemd predicates, doesn't let this particular start of the network driver initialize properly. The kernel, or systemd, has become too efficient, too fast, for this older hardware :-)

Maybe.

Also, check out

http://elixir.free-electrons.com/linux/v4.1/source/Documentation/networking/...

-- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon?

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Op dinsdag 10 oktober 2017 17:09:28 CEST schreef Dave Smith:

I am slowly figuring things out with this situation. If I boot into 42.3, knoppix 8.1 or windows 10 build 1703 from a cold, meaning uplugged machine I have internet. From either 42.3 or knoppix I can reboot (without turning off) into windows and have internet. The problem occurs when I reboot from windows into 42.3 or knoppix without unplugging, then I have no internet. Temporary hack for now is to turn off, unplug, and count to 20 when going from windows to 42.3 or knoppix. I can go from either 42.3 or knoppix to the other without unplugging and not lose internet. Just when you throw windows into the mix. Not sure why this happens but would love to get it fixed.

Dave

On Tue, Oct 10, 2017 at 10:13 AM, Anton Aylward

wrote:

...

On 10/10/17 08:24 AM, Carlos E. R. wrote:

...

Or there may be a problem initializing your network hardware, and knopix knows how to do it, and the current package you have doesn't. So if you reboot from one to the other without powering off, it keeps. Might also happen with Windows.

Yes, Knoppix is probably the most resilient version of Linux I've ever encountered, though I've dropped off research in that area this last year or so. What Dave says makes me think that knoppix hasn't lost it :-)

I suspect that it might be a timing problem. It might be that a change, be it to the kernel or an initialization that the systemd predicates, doesn't let this particular start of the network driver initialize properly. The kernel, or systemd, has become too efficient, too fast, for this older hardware :-)

Maybe.

Also, check out

http://elixir.free-electrons.com/linux/v4.1/source/Documentation/networkin g/e1000e.txt

--

A: Yes.

> Q: Are you sure? > >> A: Because it reverses the logical flow of conversation. >> >>> Q: Why is top posting frowned upon?

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Seen this long ago. I worked around it by using different static IP addresses for both Windows and openSUSE. -- Gertjan Lettink, a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Sat, 21 Oct 2017 10:21:42 -0500 "David C. Rankin" wrote:

Apparently the warm reboot leaves the nic in a state where it cannot accept the linux network card driver when booting between windoze and Linux. Of course, as you have found, going from Linux to windoze works just fine.

Surely the first thing a driver should do when starting up, is send whatever commands are necessary to the device to completely reset it to a known state. A driver that doesn't do that is buggy, and a NIC that doesn't allow a reset is also buggy. Avoid both! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 10/21/2017 04:54 PM, Carlos E. R. wrote:

Maybe because the driver considers that resetting is the job of the reset button.

The other problem is the "system" considering it is the only "system" in the machine, and thus thinking that a warm reboot is proper always and that it knows the current state of everything. That the previous running system was the same system and thus all is in the expected state.

I've worked with computers for 4 decades, including the old mini computers. A reset is always done as otherwise the software doesn't know the state of the hardware. That said, the Windows fast boot etc., does not properly shut down the system. I had to turn it off on my notebook computer. Otherwise Linux wouldn't boot. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org