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?
Dmitry Torokhov wrote:
>On Thursday 26 May 2005 21:47, Andrew Morton wrote:
>
>
>>Michael Krufky <[email protected]> wrote:
>>
>>
>>>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.
>>>
>>>
>>Not much point in telling me - I don't work on input code ;)
>>
>>Cc's added...
>>
>>
>>
>>>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
>>>
>>>
>>Did you try the 'i8042.noaux' option?
>>
>>
>>
>>>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?
>>>
>>>
>>I'd agree that this is a regression and that we should identify the code
>>change which caused this and fix it up.
>>
>>Guys?
>>
>>
>>
>
>I plead innocence - bk-input.patch has not changed for at least a month...
>
>Michael, could you please try applying:
>
>http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc5/2.6.12-rc5-mm1/broken-out/bk-input.patch
>
>directly to 2.6.12-rc5 and see if it still breaks?
>
>
>
I applied bk-input.patch directly to 2.6.12-rc5, and it did NOT break it
this time. Looks like either a different patch is the culprit, or the
combination of this patch and another.
--
Michael Krufky
On Thursday 26 May 2005 23:06, Michael Krufky wrote:
> Dmitry Torokhov wrote:
>
> >On Thursday 26 May 2005 21:47, Andrew Morton wrote:
> >
> >
> >>Michael Krufky <[email protected]> wrote:
> >>
> >>
> >>>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.
> >>>
> >>>
> >>Not much point in telling me - I don't work on input code ;)
> >>
> >>Cc's added...
> >>
> >>
> >>
> >>>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
> >>>
> >>>
> >>Did you try the 'i8042.noaux' option?
> >>
> >>
> >>
> >>>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?
> >>>
> >>>
> >>I'd agree that this is a regression and that we should identify the code
> >>change which caused this and fix it up.
> >>
> >>Guys?
> >>
> >>
> >>
> >
> >I plead innocence - bk-input.patch has not changed for at least a month...
> >
> >Michael, could you please try applying:
> >
> >http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc5/2.6.12-rc5-mm1/broken-out/bk-input.patch
> >
> >directly to 2.6.12-rc5 and see if it still breaks?
> >
> >
> >
> I applied bk-input.patch directly to 2.6.12-rc5, and it did NOT break it
> this time. Looks like either a different patch is the culprit, or the
> combination of this patch and another.
>
Please try adding bk-acpi to the mix.
--
Dmitry
Dmitry Torokhov wrote:
>On Thursday 26 May 2005 23:06, Michael Krufky wrote:
>
>
>>Dmitry Torokhov wrote:
>>
>>
>>
>>>On Thursday 26 May 2005 21:47, Andrew Morton wrote:
>>>
>>>
>>>
>>>
>>>>Michael Krufky <[email protected]> wrote:
>>>>
>>>>
>>>>
>>>>
>>>>>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.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>Not much point in telling me - I don't work on input code ;)
>>>>
>>>>Cc's added...
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>>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
>>>>>
>>>>>
>>>>>
>>>>>
>>>>Did you try the 'i8042.noaux' option?
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>>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?
>>>>>
>>>>>
>>>>>
>>>>>
>>>>I'd agree that this is a regression and that we should identify the code
>>>>change which caused this and fix it up.
>>>>
>>>>Guys?
>>>>
>>>>
>>>>
>>>>
>>>>
>>>I plead innocence - bk-input.patch has not changed for at least a month...
>>>
>>>Michael, could you please try applying:
>>>
>>>http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc5/2.6.12-rc5-mm1/broken-out/bk-input.patch
>>>
>>>directly to 2.6.12-rc5 and see if it still breaks?
>>>
>>>
>>>
>>>
>>>
>>I applied bk-input.patch directly to 2.6.12-rc5, and it did NOT break it
>>this time. Looks like either a different patch is the culprit, or the
>>combination of this patch and another.
>>
>>
>>
>
>Please try adding bk-acpi to the mix.
>
>
>
Combination of both bk-input and bk-acpi applied to 2.6.12-rc5 still
doesn't break it. What next?
--
Michael Krufky