On Saturday 25 March 2006 17:09, Jurij Smakov wrote:
> Hi,
>
> Is it USB keyboard/mouse? Could you please post the output of lsmod
> command after boot with a working kernel and a broken one?
>
> I'm fairly certain that something is wrong with your local
> configuration, rather than with the kernel, otherwise we would already be
> knee-deep in bug reports :-).

Thank you for your interest!

I solved the problem by consulting the linux kernel traffic list where this 
was well documented as a problem with latest kernels on some motherboards.

it seems to be a bug in handling  of Non-usb keyboard by a usb type method on 
my motherboard (gigabyte amd mp dual 2400+ processor server board).

This can be handled by a change in bios settings.

In short - as soon as i configured by bios to __not___ support USB keyboards, 
the 2.6.15 kernel works.

Here is a copy of earlier postings:

further info on 2.6.15 kernel bug affecting ps2 keyboard and mouse on isa 
subsystem
From: 
Mitchell Laks <[EMAIL PROTECTED]>
  To: 
[EMAIL PROTECTED]
  Date: 
03/16/06 11:36 am
   
Dear Gurus,

Here is some dmesg information from 2.6.15 kernel 
that gives me more clues what is going on.

isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
i8042.c: Can't read CTR while initializing i8042.
pnp: Device 00:0b does not supported disabling.
pnp: Device 00:0a does not supported disabling.

note that on 2.6.8.2 kernel booting it refers to serio as involved with 
keyboard and mouse

dmesg on an sid system with the 2.6.8 kernel tells me the following

serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
input: AT Translated Set 2 keyboard on isa0060/serio0
atkbd.c: Spurious ACK on isa0060/serio0. Some program, like XFree86, might be 
trying access hardware directly.
atkbd.c: Spurious ACK on isa0060/serio0. Some program, like XFree86, might be 
trying 
input: PS/2 Generic Mouse on isa0060/serio1

I found kernel traffic discussing this issue. Here are simple examples:

1) 
http://lkml.org/lkml/2006/1/14/208

Re: PROBLEM: PS/2 keyboard does not work with 2.6.15

3) 
http://www.ussg.iu.edu/hypermail/linux/kernel/0601.1/1433.html
Re: PROBLEM: PS/2 keyboard does not work with 2.6.15
From: Alan Stern 

3) 

http://www.ussg.iu.edu/hypermail/linux/kernel/0505.3/0846.html
***********quoted info**********
In 2.6.12-rc5-mm1, I can't use my psaux mouse, but it worked perfectly fine in 
both 2.6.12-rc5 and in 2.6.12-rc4-mm2.

In 2.6.12-rc5-mm1 , dmesg says:

PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
Failed to disable AUX port, but continuing anyway... Is this a SiS?
If AUX port is really absent please use the 'i8042.noaux' option.
serio: i8042 KBD port at 0x60,0x64 irq 1

This is what dmesg says in both 2.6.12-rc4-mm2 and 2.6.12-rc5 :

PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1

I am using a Shuttle FT61 motherboard. Is there any more information necessary 
to debug this?
**************************

*********************************

resolved bug
From: 
Mitchell Laks <[EMAIL PROTECTED]>
  To: 
[EMAIL PROTECTED]
  Date: 
03/16/06 11:52 am
   
Dear Installer team:

I am sorry I bothered the team. After I found and read the correct threads in 
the kernel traffic I see that it was a bios incompatibility problem with the 
latest kernels 

in my Gigabyte ga-7dpxdwp motherboard.

I had to disable usb keyboard and usb mouse support in the bios and then the 
debian kernels 2.6.15 worked fine as well as the new  installer.

Go  team  Debian!

Tell me where and how to post  the info to make this available to others. I 
will post on debian-user tonight.

Mitchell Laks
 


>
> Best regards,
>
> Jurij Smakov                                        [EMAIL PROTECTED]
> Key: http://www.wooyd.org/pgpkey/                   KeyID: C99E03CC


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to