What status/flag requires three restarts?
Hullo dere! Can somebody suggest why this would be happening the way it is? Laptop, dual-boot WinNT and SuSE 8.0. Network connection is a PCMCIA card. AT THE OFFICE I can boot in either OS, and switch back and forth all day long, and the network connection is ready and working as soon as either OS finishes loading. AT HOME If I take the laptop home, I connect to my home network, and boot into either NT or Linux, and I have the network connection (this is an improvement, more later...). BACK AT THE OFFICE If I boot into NT, I have network access immediately. When I boot into Linux, -- IF I HAVE ATTEMPTED TO CONNECT FROM LINUX AT HOME -- then there's no connection (can't browse, can't ping anything, etc.) HOWEVER If I cycle back and forth, then on the THIRD boot into Linux, the connection reappears. No other action is required. I just need to boot into Linux two times before the third time gives me a fully functional network connection again. If I take the laptop home but NEVER BOOT LINUX while I'm home, then there's no problem with the network connection upon return to the office. (No cycling required.) What would be going on, that this happens so reliably? I mentioned, above, that the fact that I can get a Linux network connection at home (with this laptop) is a recent development, and I have made NO setting changes. The only changes that have occurred have been a few YOU updates over the past 6 weeks or so. Before September, I didn't get a Linux network connection at home, but it always worked fine in either OS at the office. Anybody got a good guess as to what's going on? Thanks, /kevin (still hopelessly puzzled after all these years)
On Mon, 21 Oct 2002 12:03:45 -0400
Kevin McLauchlan
When I boot into Linux, -- IF I HAVE recently ATTEMPTED TO CONNECT FROM LINUX AT HOME -- then there's no connection (can't browse, can't ping anything, etc.)
HOWEVER If I cycle back and forth Win->Lin->Win->Lin->Win..., then on the THIRD boot into Linux, the connection reappears. No other action is required. I just need to boot into Linux two times before the third time gives me a fully functional network connection again.
If I take the laptop home but NEVER BOOT LINUX while I'm home, then there's no problem with the network connection upon return to the office. (No cycling required.)
What would be going on, that this happens so reliably?
So, I stumped everybody with this odd problem? Or the explanation was too convoluted and nobody understood what I was trying to say? The usual response to these things is something like: "Check the whozit line in your /etc/frammistan.rc file" And then I respond: "But... I don't HAVE a frammistan.rc file". And then I do a Google search that yields 51 porn sites and two hits about a 1996 accounting software that is no longer supported since the author had a sex change. Cheers, /kevin
On Thursday 24 October 2002 02.10, KMcLauchlan wrote:
"Check the whozit line in your /etc/frammistan.rc file"
You should know better than that. /etc/frammistan.rc hasn't been used since 6.4. Seriously, I suspect it's the dhcp cache. If you're running dhcpcd, run "dhcpcd -k" and then start the network again. If you're running dhcp-client look at the manpage for the option to clear the cache. I don't have it installed at the moment, so I can't check. //Anders
participants (3)
-
Anders Johansson
-
Kevin McLauchlan
-
KMcLauchlan