Re: [Karl Hammar <karl@kalle.csb.ki.se>] Re: installation problem

[Erich Mueller <em@gonzales.swb.de>]

On 30 May 2001, Adam Di Carlo wrote:

> 
> Please!  Retain the CC to the debian-boot list.

Sorry.

> 
> Erich Mueller <em@gonzales.swb.de> writes:
> > But it does not solve the problem at hand. The bios only offers USB chip
> > enable or disable and usb keyboard and usb mouse enable disable
> > functionality. I did not see any  legacy keyboard mentioned anywhere in
> > the menues.
> 
> What is this model machine again?

The case bears a Compaq Presario sticker Inside is a MSI 6330 LITE
(K7T) bios version 2.6 (in the meantime a version 2.7 has been made
available and apearantly retracted again, since I can no longer download
it(says not not avaiable when I ask for

http://msi-1.colt-isc.de/download/bios/63xx/K7T Pro-Turbo v2.7.zip
 

> 
> >  The keyboard actually doas work for the initial selection and help with
> > the functionkeys. No problem to do input at the first prompt when it asks
> > for selectors and boot parameters.
> 
> Hmm, ok, this is the syslinux stuff.
All input from keyboard works ok here still.

> 
> > The machine then proceeds with the boot
> > process  and some line come up stating no AT keyboard, keyboard timeout.
> > Then the boot continues until the first screen of acknowledgements
> > comes up and there it hangs waiting for input to continue past that
> > screen.
> 
> If you press ctrl-s while the kernel is booting (that's for pause),
> does the scrolling stop?  FYI, you can stop pausing with ctrl-q.

Only before the message about missing AT keyboard is shown.

> 
> I'm trying to figure out if it's a kernel issue or what...

I think it should be the kernel since keyboard input works before
reporting the keyboard timeout of the at style keyboard

> 
> > Seems like there is no curernt solution available for this. I have
> > another night at work and when I will have restored my mental
> > capabilities I will take the disk out of the machine and install on
> > another machine. (probably not before next weekend)
> 
> Well, please stick around for testing.  Keep an eye on the changelogs.

I will. 
 
> 
> Have you searched the web for others with this problem?

Partially. I will extend the searxch tonight to see if I can find more to
this topic.
 
> 
> There must be a way we can work around this... I suspect a kernel
> argument might do the trick, if not a hidden BIOS setting...

I am sure tehre is a way. Maybe 2.4 kernels?

thanks,
Erich