From: Kelsey Hudson <khudson@compendium-tech.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: texas <texas@ludd.luth.se>, <linux-kernel@vger.kernel.org>
Subject: Re: Dual P4 Xeon i860 system - lockups in 2.4 & no boot in 2.2
Date: Fri, 1 Mar 2002 00:03:01 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.44.0202282353370.18512-100000@sol.compendium-tech.com> (raw)
In-Reply-To: <E16gbXt-0001s7-00@the-village.bc.nu>
On Fri, 1 Mar 2002, Alan Cox wrote:
> > Tried 2.2 again thinking it might work now with the fixed BIOS settings
> > but no, still getting the "Keyboard: Timeout - AT keyboard not present?"
> > and "hda: lost interrupt" messages. So I can't even boot 2.2 and I have no
>
> I guess that box is always assuming PnP or ACPI setup in which case 2.2
> will never work on it.
hmm. I guess this begs the question, is ACPI 100% working and stable now?
I've got a similar problem with add-in IDE controllers which add more than
8 IDE devices -- the 9th and higher devices are inaccessable with the same
"hd?: lost interrupt" messages (beginning with hdi). The machine in
question is a dual AthlonXP/MP 1900+ on that new Tyan S2466 mainboard. I
figured it was a BIOS issue, but if the BIOS demands that ACPI configure
stuff, then perhaps enabling ACPI is the key. I just wihs that BIOS
manufacturers would get a fucking clue and realize that not all of us are
going to be running that other ACPI-dependent OS on the board, and make a
BIOS that configures devices the old-fashioned way: doing the work itself.
Tyan also needs to realize that assigning the same address to two sensors
on the I2C bus just isn't a good idea...
Hopefully this fixes my problem. Thanks for the pointer! ;)
Kelsey Hudson khudson@ctica.com
Associate Software Engineer
Compendium Technologies, Inc (619) 725-0771
---------------------------------------------------------------------------
==== 0100101101001001010000110100101100100000010010010101010000100001 =====
next prev parent reply other threads:[~2002-03-01 8:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-27 19:29 texas
2002-02-27 20:04 ` Alan Cox
2002-02-27 21:23 ` texas
2002-02-27 21:53 ` Alan Cox
2002-02-28 3:07 ` texas
2002-03-01 1:25 ` Alan Cox
2002-03-01 2:54 ` texas
2002-02-28 18:53 ` texas
2002-03-01 1:09 ` Alan Cox
2002-03-01 8:03 ` Kelsey Hudson [this message]
2002-03-01 11:45 ` Alan Cox
2002-03-01 12:06 ` texas
2002-03-04 18:37 ` texas
2002-02-28 21:53 ` Bill Davidsen
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=Pine.LNX.4.44.0202282353370.18512-100000@sol.compendium-tech.com \
--to=khudson@compendium-tech.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=texas@ludd.luth.se \
/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®