public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: KERNEL BUG: console not working in linux
Date: 28 Nov 2000 10:14:11 -0800	[thread overview]
Message-ID: <900slj$9td$1@cesium.transmeta.com> (raw)
In-Reply-To: <E140Pc3-0003AI-00@the-village.bc.nu> <20001128011613.A317@fourier.home.intranet> <3A22EF3D.B97A0965@transmeta.com> <20001128103352.A377@fourier.home.intranet>

Followup to:  <20001128103352.A377@fourier.home.intranet>
By author:    Gianluca Anzolin <g.anzolin@inwind.it>
In newsgroup: linux.dev.kernel
>
> |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
> 

It's not "an Olivetti", it has a model number and God Knows What.
>From the looks of it they are using a 440FX chipset, which definitely
does not have this problem inherently (and almost certainly handles
port 92h correctly), so whomever wired up this motherboard was even
more of an idiot that I first thought.

If I were you I would take it back and demand a refund.  It isn't a PC
you have there.

	-hpa

-- 
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.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/

  reply	other threads:[~2000-11-28 18:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-26 21:28 KERNEL BUG: console not working in linux 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
2000-11-28 18:14               ` H. Peter Anvin [this message]
  -- strict thread matches above, loose matches on Subject: below --
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='900slj$9td$1@cesium.transmeta.com' \
    --to=hpa@zytor.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