From: Ondrej Zary <linux@rainbow-software.org>
To: "linux-os (Dick Johnson)" <linux-os@analogic.com>
Cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: Compaq Presario "reboot" problems
Date: Fri, 18 Nov 2005 00:26:02 +0100 [thread overview]
Message-ID: <437D118A.3000306@rainbow-software.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0511171314440.10063@chaos.analogic.com>
linux-os (Dick Johnson) wrote:
> 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.
No, it does not. I know that my desktop PC reboots with a beep (and
shows CPU information) from Linux - and it does not beep when rebooting
from Windows 98.
Some BIOSes don't like when some devices are in some state. One example
is my DTK FortisPro TOP-5A notebook - when rebooted from Linux, it hangs
during POST - the fix was to add setpci <someting> to shutdown scripts
to zero-out some cardbus controller registers.
--
Ondrej Zary
next prev parent reply other threads:[~2005-11-17 23:25 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
2005-11-17 23:26 ` Ondrej Zary [this message]
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=437D118A.3000306@rainbow-software.org \
--to=linux@rainbow-software.org \
--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