mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Gianluca Anzolin <root@vger.kernel.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: KERNEL BUG: console not working in linux
Date: Tue, 28 Nov 2000 01:16:13 +0100	[thread overview]
Message-ID: <20001128011613.A317@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>
In-Reply-To: <8vubeq$r5r$1@cesium.transmeta.com>; from hpa@zytor.com on Mon, Nov 27, 2000 at 11:08:10AM -0800

Il giorno Mon, Nov 27, 2000 at 11:08:10AM -0800, H. Peter Anvin scrisse: 
|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.

I'd like to add only that the video card is integrated on the mainboard.
Maybe that register disables the integrated video card. I don't know.
Anyway I must also point out that on FreeBSD that register is used only
for IBM_L40 PC.
That said now I know how to make linux work again on this PC.
Let's see what will happen when 2.2.18 will come out as the new stable kernel.

Bye
	Gianluca

NB: the video card works without problems now. it's even found by lspci
(which couldn't find it before). I can also use any extended vga mode.
So the problem wasn't probably the video chipset.
-
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/

  parent reply	other threads:[~2000-11-27 23:45 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 [this message]
     [not found]           ` <3A22EF3D.B97A0965@transmeta.com>
2000-11-28  9:33             ` Gianluca Anzolin
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=20001128011613.A317@fourier.home.intranet \
    --to=root@vger.kernel.org \
    --cc=hpa@zytor.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

all inboxes | Powered by JetHome®