Message-ID: <089b01c36b0f$67d723e0$24ee4ca5@DIAMONDLX60>
From: "Norman Diamond" <ndiamond@wta.att.ne.jp>
To: "Russell King" <rmk@arm.linux.org.uk>
Cc: <linux-kernel@vger.kernel.org>
References: <032c01c36a36$2335ea20$24ee4ca5@DIAMONDLX60> <20030824133026.D16635@flint.arm.linux.org.uk>
Subject: Re: Bad serio/atkbd configuration possible (was: Re: Compilation errors in 2.6.0-test4, serial as modules)
Date: Mon, 25 Aug 2003 22:46:17 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1066
Lines: 24

"Russell King" <rmk@arm.linux.org.uk> replied to me:

> It's not serial, but serio.

The compile errors in 2.6.0-test4 were serio.

The boot-time errors in 2.6.0-test1 through test3, and then in test4 after I
changed the keyboard stuff back from "m" to "y", are that module serial is
not found.  These are not serio, but serial.  As far as I can tell, the
serial stuff other than keyboard and mouse are still modules, so I don't
know what is not being found.  Those messages scroll off the screen very
quickly during boot, and they don't get logged, so I can't report them
exactly.

One other message that I've seen during boot is that boot logging is
disabled because the console doesn't differ from the console.  I don't
exactly understand this one either, but it's sure telling the truth about
disabling boot logging.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/