From: "Jeff V. Merkey" <jmerkey@wolfmountaingroup.com>
To: "linux-os (Dick Johnson)" <linux-os@analogic.com>
Cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: Compaq Presario "reboot" problems
Date: Thu, 17 Nov 2005 11:39:07 -0700 [thread overview]
Message-ID: <437CCE4B.3020900@wolfmountaingroup.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0511171314440.10063@chaos.analogic.com>
Verified. I saw this problem a few weeks back and I am running Windows
2000 and 2003 on separate systems now. Windows 2000
is such a pig it needs its own system in any event.
Jeff
linux-os (Dick Johnson) wrote:
>With Linux-2.4.26 I reported that if a Compaq gets rebooted while
>running Linux-2.4.26, it will not be able to restart Windows 2000.
>It cam restart Linux fine. Today, I tried the same thing with
>Linux-2.6.13.4. It fails, too.
>
>The symptoms are that you just "reboot" Linux. When the GRUB loader
>comes up, I select my Windows-2000/professional. That M$ Crap comes
>up to where it's just about to start the high-resolution screen.
>Then it stops forever, no interrupts, no nothing. I need to disconnect
>power and remove the battery to recover.
>
>It appears as though Linux is still restarting as a "warm boot",
>rather than a cold boot (in other words, putting magic in the
>shutdown byte of CMOS) so the hardware doesn't get properly
>initialized. Would somebody please check this out. When changing
>operating systems, you need a cold-boot.
>
>Cheers,
>Dick Johnson
>Penguin : Linux version 2.6.13.4 on an i686 machine (5589.44 BogoMips).
>Warning : 98.36% of all statistics are fiction.
>.
>
>****************************************************************
>The information transmitted in this message is confidential and may be privileged. Any review, retransmission, dissemination, or other use of this information by persons or entities other than the intended recipient is prohibited. If you are not the intended recipient, please notify Analogic Corporation immediately - by replying to this message or by sending an email to DeliveryErrors@analogic.com - and destroy all copies of this information, including any attachments, without reading or disclosing them.
>
>Thank you.
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at http://www.tux.org/lkml/
>
>
>
next prev parent reply other threads:[~2005-11-17 19:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-17 18:51 Compaq Presario "reboot" problems linux-os (Dick Johnson)
2005-11-17 18:39 ` Jeff V. Merkey [this message]
2005-11-17 23:26 ` Ondrej Zary
2005-11-18 11:48 ` Denis Vlasenko
2005-11-19 13:39 ` Ondrej Zary
2005-11-18 11:51 ` Denis Vlasenko
2005-11-18 12:48 ` linux-os (Dick Johnson)
2005-11-18 14:15 ` linux-os (Dick Johnson)
2005-11-19 14:44 ` Denis Vlasenko
2005-11-21 17:52 ` linux-os (Dick Johnson)
2005-11-21 18:58 ` Stefan Seyfried
2005-11-22 14:09 ` linux-os (Dick Johnson)
2005-11-22 14:19 ` Denis Vlasenko
-- strict thread matches above, loose matches on Subject: below --
2005-11-18 15:14 Nick Warne
[not found] <59X9C-2Va-9@gated-at.bofh.it>
2005-11-19 5:05 ` Robert Hancock
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=437CCE4B.3020900@wolfmountaingroup.com \
--to=jmerkey@wolfmountaingroup.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-os@analogic.com \
/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