Skip to contentSkip to conversation

Bug Report in pc_keyb

DISCUSSION Russell C. Hay 3 participants 3 messages Feb 27, 2001

lore
Share & tools
lore
#0 lore raw

I'm not really sure who to send this too. Unfortunately, I don't really have much information on this bug, and I will provide more when I'm around the box in question. I have linux 2.2.16 running fine on the box. I am currently trying to upgrade to linux 2.4.2. However, after compiling 2.4.2 and installing in lilo and rebooting, I get the following error scrolling on my screen

"pc_keyb: controller jammed (0xFF)"

The box in question is a pentII with a supermicro motherboard. I don't know the exact model number of the motherboard. I think it is the p6sls board. I did some research on the error message, and apparently people have been getting this error on Alpha based systems too. Does anyone know how to resolve this issue or if it is a known bug that is planning to be fixed or something along those lines?

#1 lore raw
Quoted 6 lines · Russell C. Hay

I'm not really sure who to send this too. Unfortunately, I don't really have much information on this bug, and I will provide more when I'm around the box in question. I have linux 2.2.16 running fine on the box. I am currently trying to upgrade to linux 2.4.2. However, after compiling 2.4.2 and installing in lilo and rebooting, I get the following error scrolling on my screen

I'm working on a patch for pc_keyb which should hopefully address this problem. I'll send a copy to you for testing as soon as it's ready.

-ben

#2 lore raw
In reply to Russell C. Hay
Quoted 5 lines

in question. I have linux 2.2.16 running fine on the box. I am currently trying to upgrade to linux 2.4.2. However, after compiling 2.4.2 and installing in lilo and rebooting, I get the following error scrolling on my screen

Quoted 8 lines

"pc_keyb: controller jammed (0xFF)"

The box in question is a pentII with a supermicro motherboard. I don't know the exact model number of the motherboard. I think it is the p6sls board. I did some research on the error message, and apparently people have been getting this error on Alpha based systems too. Does anyone know how to resolve this issue or if it is a known bug that is planning to be fixed or something along those lines?

There are a few cases in the pc keyboard controller not currently honouring the delay protocol requirements (the keyboard controller was ancient when the original PC came out) and some chipsets use keyboard controllers or integrated keyboard support that still requires the delays. From checking the ps2 mouse open code Im sure there are several others uncaught.

A second possibility is its USB stuff confusing things, build without USB or with USB modular - I suspect the former