Re: Custom kernel... <sigh> apparently its not XFree86

From: Brendan S (Scratch User) (gobnat_at_optusnet.com.au)
Date: 07/17/04 

Date: Sat, 17 Jul 2004 15:44:29 +1000

Allen McIntosh wrote:
> In article <40f7de0c$0$18671$afc38c87@news.optusnet.com.au>,
> Brendan S (Scratch User) <gobnat@optusnet.com.au> wrote:
>
>>Apparently it has something to do with XFree86. (?)
>
> Set the initial runlevel to 3 instead of 5. This turns off
> XFree86. If the problem persists, it's got nothing to do with X.

ah, well the problems persist, so it's got nothing to do with X.
Hmmmm...
I'm stumped.

Any idea what I have to add in the config to get the usbcore module compiled? Maybe I should/could force it into the intitrd?

What happens is that these two lines spit out to console during the boot process:
atkbd.c: Unknown key pressed (translated set 2, code 0x0 on isa0060/serio0).
atkbd.c: Use 'setkeycodes 00 <keycode>' to make it known.

And once kudzu kicks it they just keep flooding the screen. I don't get a boot prompt/x session.

Setkeycodes doesn't work btw. I think you can't set a code for 0x0.

Brendan