From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: KERNEL BUG: console not working in linux
Date: 27 Nov 2000 11:08:10 -0800 [thread overview]
Message-ID: <8vubeq$r5r$1@cesium.transmeta.com> (raw)
In-Reply-To: <E140Pc3-0003AI-00@the-village.bc.nu> <200011271849.eARInfc255418@saturn.cs.uml.edu>
Followup to: <200011271849.eARInfc255418@saturn.cs.uml.edu>
By author: "Albert D. Cahalan" <acahalan@cs.uml.edu>
In newsgroup: linux.dev.kernel
>
> >> 1) Why did they disable my videocard ?
> >
> > Because your machine is not properly PC compatible
>
> The same can be said of systems that don't support the
> standard keyboard controller for A20 control.
>
Yes, it can. Unfortunately, some "legacy-free" PCs apparently are
starting to take the tack that the KBC is legacy. Therefore, the use
of port 92h is mandatory on those systems.
Port 92h dates back to at the very least the IBM PS/2.
Either way, the video card of the original poster is broken in more
ways than that. Ports 0x00-0xFF are reserved for the motherboard
chipset and have been since the original IBM PC.
It would have been somewhat different if there had been a standard
BIOS function for enabling A20, but there isn't one.
Sometimes, in the PC world, you just have to draw a line and say "this
is too broken to use". I think the original posters' video card falls
in that category. Get a new video card, they're cheap these days.
-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/
next prev parent reply other threads:[~2000-11-27 19:38 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 [this message]
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
-- 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='8vubeq$r5r$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