John Baldwin wrote:
> >> And do you have the following line in /boot/device.hints?
> >> hint.psm.0.irq="12"
> > i have ibm 570e, with the same PS/2 mouse problem, Ohh. worse..
> > Fatal trap 12: page fault while in kernel mode
> > fault virtual address = 0x3a
> > fault code = supe
On Sat, Sep 08, 2001 at 07:32:17PM +0900, Kazutaka YOKOTA wrote:
> Your forgot to put the following lines in device.hints.
>
> hint.atkbdc.0.at="isa"
> hint.atkbdc.0.port="0x60"
>
> See /sys/i386/conf/GENERIC.hints.
no, I didn't forget. It wasn't required before now and I had 1 string less in u
Thank you for your report.
>On Sat, Sep 08, 2001 at 12:15:59AM +0900, Kazutaka YOKOTA wrote:
>> Please send me the entire dmesg output after you boot
>> the system with "boot -v" at the loader prompt.
>ok.
>>
>> And do you have the following line in /boot/device.hints?
>> hint.psm.0.irq="12"
>ye
On 07-Sep-01 Donny Lee wrote:
> Kazutaka YOKOTA wrote:
>> Please send me the entire dmesg output after you boot
>> the system with "boot -v" at the loader prompt.
>>
>> And do you have the following line in /boot/device.hints?
>> hint.psm.0.irq="12"
>
> i have ibm 570e, with the same PS/2 mous
Kazutaka YOKOTA wrote:
> Please send me the entire dmesg output after you boot
> the system with "boot -v" at the loader prompt.
>
> And do you have the following line in /boot/device.hints?
> hint.psm.0.irq="12"
i have ibm 570e, with the same PS/2 mouse problem, Ohh. worse..
Fatal trap 12: p
Please send me the entire dmesg output after you boot
the system with "boot -v" at the loader prompt.
And do you have the following line in /boot/device.hints?
hint.psm.0.irq="12"
Kazu
>I don't know why, but
>NOW I have broken PS/2 mouse _without_ acpi module :(
>VAIO Z505HS.
>
>atkbdc0: at p
On Thu, Sep 06, 2001 at 08:51:44PM +0900, Kazutaka YOKOTA wrote:
I don't know why, but
NOW I have broken PS/2 mouse _without_ acpi module :(
VAIO Z505HS.
atkbdc0: at port 0x60,0x64 irq 1 on isa0
atkbd0: flags 0x1 irq 1 on atkbdc0
kbd0 at atkbd0
kbd0: atkbd0, AT 101/102 (2), config:0x1, flags:0
Thanks Yokota-san for tracking down the problem.
> As reported in this list by several people, you may be seeing that
> your PS/2 mouse is not detected after the recent ACPI update.
>
> This seems to be caused by ACPI in some BIOS assigns IRQ 12 (mouse
> interrupt) to both the PS/2 mouse device
