mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Anton Altaparmakov <aia21@cam.ac.uk>
To: "Arnvid Karstad" <arnvid@karstad.org>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: Problems rebooting from linux to windows...
Date: Fri, 05 Apr 2002 15:41:28 +0100	[thread overview]
Message-ID: <5.1.0.14.2.20020405153618.01fefd20@pop.cus.cam.ac.uk> (raw)
In-Reply-To: <20020405130948.17108.qmail@nextgeneration.speedroad.net>

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/


      parent reply	other threads:[~2002-04-05 14:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-05 13:09 Arnvid Karstad
2002-04-05 13:17 ` Benjamin Pharr
2002-04-05 13:23   ` Tigran Aivazian
2002-04-05 13:39 ` Richard B. Johnson
2002-04-05 17:14   ` Mike Galbraith
2002-04-05 14:41 ` Anton Altaparmakov [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5.1.0.14.2.20020405153618.01fefd20@pop.cus.cam.ac.uk \
    --to=aia21@cam.ac.uk \
    --cc=arnvid@karstad.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®