On Sun, 10 Aug 2003, Daniel Flickinger wrote:
> I had the same problem starting about a year ago when I
> finally gave up and upgraded to X4. The problem appears
> to be that the X4 driver does not disable the console
> mouse and the two of them fight over the interrupts.
Well yea
Not to undermine what you guys said, but this is unrelated to the
original post I think. The problem I was having related to acpi, which
Shizuka pointed out. I'm not trying to play nanny here, just don't want
people to get confused =)
On Sun, 2003-08-10 at 21:16, Daniel Flickinger wrote:
> Se
Yes, adding hint.acpi.0.disabled="1" to /boot/device.hints fixed the
mouse problem.
While this is somewhat pleasing, it also leaves me with uncertainty. I
tried tweaking
basically every CMOS combination I could think of. Do you suppose this
is an
incompatability between the apci driver and my m
That indeed fixed the problem. It does appear like the problem relates
to a
specific BIOS version. I'm wondering if there's a certain set of people
I
should forward this information on to? It would be nice if a fix like
this could
find its way into the -current tree. Thank you Shizuka for y
--- Mike Bohan <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I have an Abit KT266 based motherboard and am having some trouble using
> the PS/2 mouse driver under XFree86. I have the protocol set to "auto",
> and the device set to /dev/psm0. This configuration has worked with
> this same Intell
--- Mike Bohan <[EMAIL PROTECTED]> wrote:
> That indeed fixed the problem. It does appear like the problem relates
> to a
> specific BIOS version. I'm wondering if there's a certain set of people
> I
> should forward this information on to? It would be nice if a fix like
I have reported thi
--- Mike Bohan <[EMAIL PROTECTED]> wrote:
> Yes, adding hint.acpi.0.disabled="1" to /boot/device.hints fixed the
> mouse problem.
Try this patch on acpi and see if it solves your problem.
--- sys/dev/acpica/acpi_pci_link.c.orig Thu Jan 2 02:48:49 2003
+++ sys/dev/acpica/acpi_pci_link.c Fr
