Re: PPPoE and ADSL problem (1 solution)

From: Jacob Westenbach (westy528_at_yahoo.com)
Date: 12/03/03 

Date: Wed, 03 Dec 2003 19:11:33 GMT

"Stephen Harris" <cyberdiction@hotmail.com> wrote in message
news:Ie6zb.30652$2m3.8688@newssvr29.news.prodigy.com...
>
> "Jacob Westenbach" <westy528@yahoo.com> wrote in message
> news:K85zb.73721$do1.66364@twister.austin.rr.com...
> > "Tero Pihlajakoski" <tepihlaj@nopaju.spamoulu.fi> wrote in message
> > news:bqief1$21f$1@ousrvr3.oulu.fi...
> > > ---
> > >
> > > Hi,
> > >
> > > I recently re-installed linux as a second operating system along
WinXP.
> I
> > > had huge problems getting up the internet connection (For finnish

> > > [ much snipped ]

> > > Does anyone know a more flexible way to solve this? I want to be able
to
> > > 'restart' windows and boot directly to Linux.
> > >
> > I hate to be the bearer of bad news, but you'll have to do a complete
> > shutdown from Win and then boot into Linux. As you've already
discovered,
> > Win leaves the NIC in a state of limbo that I've never found a way to
> > resolve w/o a cold start of the machine. Fortunately, going from Linux
to
> > Win does not have the same problem.

>
> These conclusions don't seem quite right to me. You will find plenty
> of evidence of win xp and linux dual booting and linux having connection
> problems of a more advanced nature such as can only use numerical
> ip addresses not alphabetical, which means the connection is made but
> there is a hosts file un/mis configured. There is no need to turn off
> computer.

I obviously did not make my msg understandable. Either Win or Linux boot
and run perfectly from a coldstart. This would seem to rule out a
configuration problem on either side. BUT, if you first boot into Win and
subsequently wish to launch Linux, selecting "ReStart" rather than
"Shutdown" in Win results in Linux being unable to init the NIC properly.
At that point, /sbin/ifconfig shows the NIC with a valid (static in this
case) IP, route -n returns the expected values, BUT communication via the
NIC is impossible. Everything results in a "network unreachable" error.

Doing a shutdown/coldstart sequence either between the Win -> Linux change
or once Linux is as described above is the only thing I have found to
prevent/correct the problem.

JW

Relevant Pages

  • SmartUPS1000, WinNT & Linux
    ... I tried to install powerchute over the linux box but it keep asking me ... connection beetwen the linux box and the ups. ... the nt box and get when the shutdown should happen... ...
    (comp.os.linux.hardware)
  • Re: [SLE] Configuring a systems time - which files to edit?
    ... >> I hope it is not the CMOS battery. ... What I cannot understand is that on booting linux ... On a shutdown the system time and hardware time are ... so therefore for the clock to be wrong linux must not be ...
    (SuSE)
  • Re: [SLE] shutting down at failsafe login
    ... >> the login prompt, ... The proper way to shutdown a Unix/Linux system from non-graphical mode ... In Linux, ... One reason to use the shutdown command rather than halt or init 6 or the ...
    (SuSE)
  • Re: SuSE 11.1: Novell first to bring old windows 98 code to Linux
    ... Novell now introduces this feature to Linux. ... Sadly I kept losing consoles to umount attempts (and ... "shutdown -r now") before I thought of using sync. ...
    (alt.os.linux.suse)
  • Re: Linux is so cool!
    ... There's an option to shutdown the computer from the gdm screen. ... >> Linux is so AWESOME man! ... How can I reboot or turn off computer? ... I'm an expert Windows ...
    (Fedora)