Keyboard Scancode Problems

Keyboard Scancode Problems

[Udo A. Steinberg]

Hi all,

With all the latest kernels (at least since 2.4.0-test12)
I have had occasional problems with a PS/2 keyboard when
switching back and forth between X and text consoles.

In most cases the problem occurs when switching from X to
a text console, which renders the keyboard totally unusable.
Pressing any key results in ^W ^E and other garbage.
Sometimes pressing Ctrl fixes the problem, other times not
even SysRq works.

The kernel logs the following stuff:

keyboard: unrecognized scancode (70) - ignored
keyboard: unrecognized scancode (66) - ignored
keyboard: unknown scancode e0 71
keyboard: unknown scancode e0 70

and so forth. I cannot reliably reproduce it though.

Can someone enlighten me whether this is a keyboard problem,
X problem or something wrong with the kernel's console stuff?

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

Any reason why we can't auto-start LVM (vg's) in the kernel?

[List User]

Is there any reason why we can't auto-detect/bring up volume-groups in the
kernel instead of creating a ramdisk volume to do a vgscan and then mount a
rootlv?

Just trying to see if there is a way (or would make sense) to skip the
ramdisk stage in mounting a root logical volume.

Steve

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

Re: Any reason why we can't auto-start LVM (vg's) in the kernel?

[Andreas Dilger]

Steve, writes:
> Is there any reason why we can't auto-detect/bring up volume-groups in the
> kernel instead of creating a ramdisk volume to do a vgscan and then mount a
> rootlv?

Um, yes, because it won't work.  The user tools do the I/O of LVM state
information to the disk.  The kernel LVM module has no concept of how
LVM information is stored on disk.

> Just trying to see if there is a way (or would make sense) to skip the
> ramdisk stage in mounting a root logical volume.

Need to re-write (or at least seriously enhance) the LVM kernel code to do
this.  Sorry.

Cheers, Andreas
-- 
Andreas Dilger  \ "If a man ate a pound of pasta and a pound of antipasto,
                 \  would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/               -- Dogbert
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: Keyboard Scancode Problems

[Pierre Rousselet]

"Udo A. Steinberg" wrote:
 
> keyboard: unrecognized scancode (70) - ignored
> keyboard: unrecognized scancode (66) - ignored
> keyboard: unknown scancode e0 71
> keyboard: unknown scancode e0 70

which key do you press to generate such scancodes ?
#showkey -s

-- 
------------------------------------------------
 Pierre Rousselet <pierre.rousselet@wanadoo.fr>
------------------------------------------------
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: Keyboard Scancode Problems

[Stefan Frank]

Hi Udo!

On Thu, 01 Feb 2001, Udo A. Steinberg wrote:

> 
> Hi all,
> 
> With all the latest kernels (at least since 2.4.0-test12)
> I have had occasional problems with a PS/2 keyboard when
> switching back and forth between X and text consoles.
> 
> In most cases the problem occurs when switching from X to
> a text console, which renders the keyboard totally unusable.
> Pressing any key results in ^W ^E and other garbage.
> Sometimes pressing Ctrl fixes the problem, other times not
> even SysRq works.
> 
> The kernel logs the following stuff:
> 
> keyboard: unrecognized scancode (70) - ignored
> keyboard: unrecognized scancode (66) - ignored
> keyboard: unknown scancode e0 71
> keyboard: unknown scancode e0 70
> 
> and so forth. I cannot reliably reproduce it though.
> 
> Can someone enlighten me whether this is a keyboard problem,
> X problem or something wrong with the kernel's console stuff?
> 

I had the same problem when upgrading from 2.4.0-test10 to 2.4.0,
altough my keyboard worked for about half a year without problems. 
But, what a coincidence, it turned out to be a hardware problem. Two pins
of the PS/2 connector were moved inside the connector, thus they didn't
connect to the keyboard controller. I replaced the keyboard cable and
all is well. Did you try to replace the keyboard ?

Regards, Stefan


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