From: Gianluca Anzolin <g.anzolin@inwind.it>
To: "H. Peter Anvin" <hpa@transmeta.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: KERNEL BUG: console not working in linux
Date: Tue, 28 Nov 2000 10:33:53 +0100 [thread overview]
Message-ID: <20001128103352.A377@fourier.home.intranet> (raw)
In-Reply-To: <E140Pc3-0003AI-00@the-village.bc.nu> <200011271849.eARInfc255418@saturn.cs.uml.edu> <8vubeq$r5r$1@cesium.transmeta.com> <20001128011613.A317@fourier.home.intranet> <3A22EF3D.B97A0965@transmeta.com>
In-Reply-To: <3A22EF3D.B97A0965@transmeta.com>; from hpa@transmeta.com on Mon, Nov 27, 2000 at 03:33:17PM -0800
|No, the problem is the utterly braindamaged way the motherboard chose to
|enable/disable it (*especially* if it's PCI... sheech, port 92h isn't
|exactly something new in that timeframe.)
|
|What PC/motherboard is this, anyway?
It's an olivetti, but maybe they bought the mainboard elsewhere I don't
know. Anyway you can find the lspci -xvv in
http://www.gest.unipd.it/~iig0573/lspci.txt
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-28 9:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-26 21:28 Gianluca Anzolin
2000-11-26 23:53 ` Jorge Nerin
2000-11-27 14:05 ` Gianluca Anzolin
2000-11-27 14:50 ` Alan Cox
2000-11-27 18:49 ` Albert D. Cahalan
2000-11-27 19:08 ` H. Peter Anvin
2000-11-27 19:27 ` Petr Vandrovec
2000-11-28 1:36 ` Andries Brouwer
2000-11-28 1:40 ` H. Peter Anvin
2000-11-28 3:14 ` Andries Brouwer
2000-11-28 3:23 ` H. Peter Anvin
2000-11-27 19:52 ` Albert D. Cahalan
2000-11-27 19:59 ` H. Peter Anvin
2000-11-28 0:16 ` Gianluca Anzolin
[not found] ` <3A22EF3D.B97A0965@transmeta.com>
2000-11-28 9:33 ` Gianluca Anzolin [this message]
2000-11-28 18:14 ` H. Peter Anvin
2000-11-28 4:09 Dunlap, Randy
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=20001128103352.A377@fourier.home.intranet \
--to=g.anzolin@inwind.it \
--cc=hpa@transmeta.com \
--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®