Hi,
recently I've seen a few problems with several laptops and if one are so
unfortunate that one needs to reboot into Windows after a session in linux.
Normal restart of windows never have a problem on the same machines, but if
you go from Linux to for instance Windows by shutdown -r or reboot it will
freeze half way into the booting process.
A power cycle will hower fix this.
Anyone got an idea about where to start looking?
Best regards
Arnvid Karstad
I have this problem with my Dell Inspiron 7000. I just use "shutdown -h
now" and then power back up. Someone told me it was a BIOS issue once
upon a time, but I've never messed with it. Not that big of a problem
for me.
Ben Pharr
On Fri, Apr 05, 2002 at 03:09:48PM +0200, Arnvid Karstad wrote:
> Hi,
>
> recently I've seen a few problems with several laptops and if one are so
> unfortunate that one needs to reboot into Windows after a session in linux.
> Normal restart of windows never have a problem on the same machines, but if
> you go from Linux to for instance Windows by shutdown -r or reboot it will
> freeze half way into the booting process.
>
> A power cycle will hower fix this.
>
> Anyone got an idea about where to start looking?
>
> Best regards
>
> Arnvid Karstad
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
quoting Alan Cox (on linux-scsi):
Always power off a PC between OS changes. It shouldnt be needed but
it often is.
On Fri, 5 Apr 2002, Benjamin Pharr wrote:
> I have this problem with my Dell Inspiron 7000. I just use "shutdown -h
> now" and then power back up. Someone told me it was a BIOS issue once
> upon a time, but I've never messed with it. Not that big of a problem
> for me.
>
> Ben Pharr
>
>
> On Fri, Apr 05, 2002 at 03:09:48PM +0200, Arnvid Karstad wrote:
> > Hi,
> >
> > recently I've seen a few problems with several laptops and if one are so
> > unfortunate that one needs to reboot into Windows after a session in linux.
> > Normal restart of windows never have a problem on the same machines, but if
> > you go from Linux to for instance Windows by shutdown -r or reboot it will
> > freeze half way into the booting process.
> >
> > A power cycle will hower fix this.
> >
> > Anyone got an idea about where to start looking?
> >
> > Best regards
> >
> > Arnvid Karstad
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to [email protected]
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at http://www.tux.org/lkml/
> >
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
On Fri, 5 Apr 2002, Arnvid Karstad wrote:
> Hi,
>
> recently I've seen a few problems with several laptops and if one are so
> unfortunate that one needs to reboot into Windows after a session in linux.
> Normal restart of windows never have a problem on the same machines, but if
> you go from Linux to for instance Windows by shutdown -r or reboot it will
> freeze half way into the booting process.
>
> A power cycle will hower fix this.
>
> Anyone got an idea about where to start looking?
>
> Best regards
>
> Arnvid Karstad
I have this same problem on my Compaq Presario. I think that this
is because the BIOS was shadowed and used some writable-RAM somewhere.
Linux seems to do a 'warm-boot'. The result being that some of the
stuff that the BIOS counts on was wiped out by Linux, i.e.,
stuff from E000:0000 -> E000:FFFF (the BIOS is normally at F000:0000).
My 'fix' is to cold-boot, i.e., processor reset during the shutdown.
Cheers,
Dick Johnson
Penguin : Linux version 2.4.18 on an i686 machine (797.90 BogoMips).
Windows-2000/Professional isn't.
On Fri, 5 Apr 2002, Richard B. Johnson wrote:
> On Fri, 5 Apr 2002, Arnvid Karstad wrote:
>
> > Hi,
> >
> > recently I've seen a few problems with several laptops and if one are so
> > unfortunate that one needs to reboot into Windows after a session in linux.
> > Normal restart of windows never have a problem on the same machines, but if
> > you go from Linux to for instance Windows by shutdown -r or reboot it will
> > freeze half way into the booting process.
> >
> > A power cycle will hower fix this.
> >
> > Anyone got an idea about where to start looking?
> >
> > Best regards
> >
> > Arnvid Karstad
>
> I have this same problem on my Compaq Presario. I think that this
> is because the BIOS was shadowed and used some writable-RAM somewhere.
> Linux seems to do a 'warm-boot'. The result being that some of the
> stuff that the BIOS counts on was wiped out by Linux, i.e.,
> stuff from E000:0000 -> E000:FFFF (the BIOS is normally at F000:0000).
>
> My 'fix' is to cold-boot, i.e., processor reset during the shutdown.
FWIW, I also have a Presario, and reboot frequently between Windbloz
and Linux with zero problems. I've seen many many many problems wrt
Compaq (mostly crap bios) and Linux over the years, but ATM, I don't
have any. (I put total >$20k into a 386-20 believe it or not.. was
shit hot box at the time:)
-Mike
At 14:09 05/04/02, Arnvid Karstad wrote:
>recently I've seen a few problems with several laptops and if one are so
>unfortunate that one needs to reboot into Windows after a session in linux.
>Normal restart of windows never have a problem on the same machines, but
>if you go from Linux to for instance Windows by shutdown -r or reboot it
>will freeze half way into the booting process.
>A power cycle will hower fix this.
>Anyone got an idea about where to start looking?
The Microsoft Windows sourcecode would be a good start but oh wait you
can't get that. D'oh! You are fscked! Just power cycle and as you have seen
you will be fine.
The reason for the problems is that Windows is expecting the hardware to be
in a certain state at boot which is not present after Linux reboots because
it has initialized the devices differently.
On my laptop the reverse is true. When rebooting from Windows to Linux
XFree86 no longer works (garbled display) but power cycling is fine. I
could look into this and force the hardware to reinitialize in Linux or I
could just power cycle. I chose the power cycle as I have better things to
do...
But in your case the way to fix this would be to make the windows driver
initialize the hardware properly and I doubt very much you would have much
success getting MS to do this for you. They will probably tell you to stop
using Linux and your problems will go away...
Best regards,
Anton
--
"I've not lost my mind. It's backed up on tape somewhere." - Unknown
--
Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @)
Linux NTFS Maintainer / WWW: http://linux-ntfs.sf.net/
IRC: #ntfs on irc.openprojects.net / ICQ: 8561279
WWW: http://www-stu.christs.cam.ac.uk/~aia21/