Do you still need atkbd.reset=1?
No, i don't. i've just tried it, because when keyboard was not working,
the only error report was produced by this option.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info a
Wiktor, can you try atkbd.dumbkbd=1?
Here you are full dmesg (see attachment). i've been typing alphabet
after kernel boot.
atkbd.dumpkbd.gz
Description: application/gzip
It still looks OK. It seems to be a very ancient keyboard. Can you try with
a newer one? That'd tell us whether it's the controller or the keyboard
that is giving problems.
What keyboard model is it? What machine?
Machine info attached as a part of /dev/proc. i've tried with another AT
keyboard an
On Fri, Jan 28, 2005 at 09:46:41AM -0500, Dmitry Torokhov wrote:
> On Fri, 28 Jan 2005 15:31:21 +0100, Vojtech Pavlik <[EMAIL PROTECTED]> wrote:
> > On Tue, Jan 25, 2005 at 08:37:34PM +0100, Wiktor wrote:
> > > Hi,
> > >
> > > here you are gzip-ed dmesg from booting 2.6.8.1 - i've been playing
> >
On Fri, Jan 28, 2005 at 08:39:42PM +0100, Wiktor wrote:
> Hi, IT WORKED!
>
> >Please try i8042.noaux=1. You say you're using a serial mouse in your
> >other e-mail, so the system may not have an AUX port yet the kernel
> >thinks it does. This may cause the keyboard to stop responding.
>
> comman
On Fri, Jan 28, 2005 at 09:22:20PM +0100, Wiktor wrote:
> Hi,
>
> >We do test AUX port and your port appears to be perfectly functional
> >from the kernel point of view - it porperly responds to AUX_LOOP
> >commands, does not claim to support MUX mode and KBC properly sets
> >status register when
On Fri, Jan 28, 2005 at 08:49:03PM +0100, Wiktor wrote:
> Hi,
>
> >Could you please try editing drivers/input/serio/i8042.c and add
> >udelay(20) before and after calls to i8042_write_data() in
> >i8042_kbd_write() and i8042_command().
>
> of course i could, will it make kernel not detect smoked
On Fri, Jan 28, 2005 at 08:22:32PM +0100, Wiktor wrote:
> Hi,
>
> >This dmesg looks like the keyboard works perfectly OK. Do new lines
> >appear in dmesg when you press keys while the system is running?
>
> .no? no, they don't. i've new dmesg for you - it reports
> timeouts while try
On Fri, Jan 28, 2005 at 02:27:20PM -0500, Dmitry Torokhov wrote:
> On Fri, 28 Jan 2005 20:22:32 +0100, Wiktor <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > >This dmesg looks like the keyboard works perfectly OK. Do new lines
> > >appear in dmesg when you press keys while the system is running?
> >
>
Hi,
We do test AUX port and your port appears to be perfectly functional
from the kernel point of view - it porperly responds to AUX_LOOP
commands, does not claim to support MUX mode and KBC properly sets
status register when asked to disable interface...
ok, but how AUX block KBD port? if procesor
On Fri, 28 Jan 2005 20:49:03 +0100, Wiktor <[EMAIL PROTECTED]> wrote:
> Hi,
>
> > Could you please try editing drivers/input/serio/i8042.c and add
> > udelay(20) before and after calls to i8042_write_data() in
> > i8042_kbd_write() and i8042_command().
>
> of course i could, will it make kernel n
Hi,
Could you please try editing drivers/input/serio/i8042.c and add
udelay(20) before and after calls to i8042_write_data() in
i8042_kbd_write() and i8042_command().
of course i could, will it make kernel not detect smoked AUX port?
(problem is solved by i8042.noaux=1 cause my hardware has smoked
Hi, IT WORKED!
Please try i8042.noaux=1. You say you're using a serial mouse in your
other e-mail, so the system may not have an AUX port yet the kernel
thinks it does. This may cause the keyboard to stop responding.
command line "linux-new init=/bin/bash i8042.noaux=1 atkbd.reset=1"
booted 2.6.8.
On Fri, 28 Jan 2005 20:22:32 +0100, Wiktor <[EMAIL PROTECTED]> wrote:
> Hi,
>
> >This dmesg looks like the keyboard works perfectly OK. Do new lines
> >appear in dmesg when you press keys while the system is running?
>
> .no? no, they don't. i've new dmesg for you - it reports
> timeo
Hi,
This dmesg looks like the keyboard works perfectly OK. Do new lines
appear in dmesg when you press keys while the system is running?
.no? no, they don't. i've new dmesg for you - it reports
timeouts while trying to perform keyboard reset (by atkbd.reset=1).
after detection pressin
Vojtech Pavlik wrote:
On Fri, Jan 21, 2005 at 04:27:53PM +0100, Wiktor wrote:
Hi,
my AT keyboard is dead on 2.6 series. Tests on other machines proves
that this is my-hardware-specyfic problem (exacly the same binnary works
on different mainboards with PS/2 keyboard and another AT keyboard). 2.4
On Fri, 28 Jan 2005 15:31:21 +0100, Vojtech Pavlik <[EMAIL PROTECTED]> wrote:
> On Tue, Jan 25, 2005 at 08:37:34PM +0100, Wiktor wrote:
> > Hi,
> >
> > here you are gzip-ed dmesg from booting 2.6.8.1 - i've been playing
> > keyboard while booting, maybe interrupt reports will help you. also my
> >
On Tue, Jan 25, 2005 at 08:37:34PM +0100, Wiktor wrote:
> Hi,
>
> here you are gzip-ed dmesg from booting 2.6.8.1 - i've been playing
> keyboard while booting, maybe interrupt reports will help you. also my
> .config part follows:
> CONFIG_INPUT=y
> CONFIG_INPUT_MOUSEDEV=y
> CONFIG_SOUND_GAMEPOR
On Fri, Jan 21, 2005 at 04:27:53PM +0100, Wiktor wrote:
> Hi,
>
> my AT keyboard is dead on 2.6 series. Tests on other machines proves
> that this is my-hardware-specyfic problem (exacly the same binnary works
> on different mainboards with PS/2 keyboard and another AT keyboard). 2.4
> series w
Hi,
here you are gzip-ed dmesg from booting 2.6.8.1 - i've been playing
keyboard while booting, maybe interrupt reports will help you. also my
.config part follows:
CONFIG_INPUT=y
CONFIG_INPUT_MOUSEDEV=y
CONFIG_SOUND_GAMEPORT=y
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
CONFIG_INPUT_KEYBOARD=y
CONFIG_KE
On Fri, 21 Jan 2005 20:07:51 +0100, Wiktor <[EMAIL PROTECTED]> wrote:
> Dmitry Torokhov wrote:
> > Hi,
> >
> > What kernel version are you using? Have you tried 2.6.8.1? - it looks
> > like changes in 2.6.9-rc2-bk3 caused problems on some hardware.
> >
>
> Hi,
>
> it looks like 2.6.10 (which I wa
Dmitry Torokhov wrote:
Hi,
What kernel version are you using? Have you tried 2.6.8.1? - it looks
like changes in 2.6.9-rc2-bk3 caused problems on some hardware.
Hi,
it looks like 2.6.10 (which I was using) - serio ports are detected ok
(both on 0x60,0x64, keyboard irq 1, aux irq 12), keyboard also
On Fri, 21 Jan 2005 16:27:53 +0100, Wiktor <[EMAIL PROTECTED]> wrote:
> Hi,
>
> my AT keyboard is dead on 2.6 series. Tests on other machines proves
> that this is my-hardware-specyfic problem (exacly the same binnary works
> on different mainboards with PS/2 keyboard and another AT keyboard). 2.4
Hi,
my AT keyboard is dead on 2.6 series. Tests on other machines proves
that this is my-hardware-specyfic problem (exacly the same binnary works
on different mainboards with PS/2 keyboard and another AT keyboard). 2.4
series works correctly. On 2.6 kernel seems to not hear what keyboard
wants
24 matches
Mail list logo
