From owner-freebsd-current@FreeBSD.ORG Sun Aug 10 09:38:21 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5367A37B401 for ; Sun, 10 Aug 2003 09:38:21 -0700 (PDT) Received: from caboose.shortcircut.org (cpe-66-189-87-244.ma.charter.com [66.189.87.244]) by mx1.FreeBSD.org (Postfix) with ESMTP id DB2E443F85 for ; Sun, 10 Aug 2003 09:38:17 -0700 (PDT) (envelope-from bogin@yokels.org) Received: from steam (unknown [10.0.1.2]) by caboose.shortcircut.org (Postfix) with ESMTP id 97114267622; Sun, 10 Aug 2003 12:38:32 -0400 (EDT) From: Mike Bohan To: Shizuka Kudo In-Reply-To: <20030810153530.12285.qmail@web11408.mail.yahoo.com> References: <20030810153530.12285.qmail@web11408.mail.yahoo.com> Message-Id: <1060533218.12813.49.camel@diesel> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.3 Date: 10 Aug 2003 12:33:38 -0400 Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.1 cc: freebsd-current@freebsd.org Subject: Re: Problem with PS/2 mouse driver in XFree86 4.3.0 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Aug 2003 16:38:21 -0000 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 your intuitive thinking, otherwise I surely never would have found a practical solution. -Mike Bohan On Sun, 2003-08-10 at 11:35, Shizuka Kudo wrote: > --- Mike Bohan 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 Fri Feb 28 15:18:55 2003 > @@ -461,7 +461,10 @@ > return_ACPI_STATUS (error); > } > > +/* > if (!(sta & (ACPI_STA_PRESENT | ACPI_STA_FUNCTIONAL))) { > +*/ > + if (!(sta & ACPI_STA_ENABLE)) { > ACPI_DEBUG_PRINT((ACPI_DB_ERROR, > "PCI interrupt link is not functional - %s\n", > acpi_name(handle))); > > > > 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 motherboard? The behavior > > I bet you might have problem with parallel port as well. My machine suffered > from this behaviour when someone made the change as shown on the patch. I just > reverted that one. If the patch solves your problem, I believe that this is > related to BIOS not chipset. I have a Celeron on i815ep and the acpi message is > shown below. I just notice that you have a similar acpi signature like mime. > > acpi0: on motherboard > pcibios: BIOS version 2.10 > Using $PIR table, 10 entries at 0xc00fded0 > > Good luck. > > > makes > > it appear as if something else is fighting over the same resources that > > the mouse uses. > > This would explain why it can only access the device once a second. > > When BIOS > > initializes, it does not list any other device with an IRQ of 12 (which > > I believe is the mouse interface). > > Does anyone have any experience with devices such as mice flaking out > > with apci? > > Thanks again! > > > > -Mike Bohan > > > > > > On Sun, 2003-08-10 at 04:02, Shizuka Kudo wrote: > > > > > --- Mike Bohan 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 Intellimouse in the past. The symptoms are that that when the > > > > mouse is moved, the cursor is only updated about once a second. After > > > > searching google, I found the following URL in which another person > > > > experienced the same problem (from freebsd-bugs). Apparently it only > > > > shows up on certain chipsets (VIA based). I tried several other PS/2 > > > > mice, to no avail (same outcome). My system is running a day old > > > > -current build, but this other fellow reported the problem in 5.0 (does > > > > not affect 4.x). I'm wondering if anyone else has experienced this > > > > problem, and if so, are there any work-arounds? I've attached my > > > > 'dmesg' output, in the hopes that the information will be of value. > > > > Thank you in advance! > > > > > > > > > > Does disabling acpi make your mouse working? > > > > > > > URL: > > > > http://lists.freebsd.org/pipermail/freebsd-bugs/2003-April/000426.html > > > > > > > > -Mike Bohan > > > > > > > > Copyright (c) 1992-2003 The FreeBSD Project. > > > > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > > > > The Regents of the University of California. All rights > > > > reserved. > > > > FreeBSD 5.1-CURRENT #3: Fri Aug 8 09:10:54 EDT 2003 > > > > root@censored:/usr/obj/usr/src/sys/CABOOSE > > > > Preloaded elf kernel "/boot/kernel/kernel" at 0xc0424000. > > > > Preloaded elf module "/boot/kernel/acpi.ko" at 0xc0424244. > > > > Timecounter "i8254" frequency 1193182 Hz > > > > CPU: AMD Athlon(tm) processor (1333.91-MHz 686-class CPU) > > > > Origin = "AuthenticAMD" Id = 0x644 Stepping = 4 > > > > > > > > > > > > > > Features=0x183fbff > > > > AMD Features=0xc0440000 > > > > real memory = 268369920 (255 MB) > > > > avail memory = 256196608 (244 MB) > > > > Pentium Pro MTRR support enabled > > > > npx0: on motherboard > > > > npx0: INT 16 interface > > > > acpi0: on motherboard > > > > pcibios: BIOS version 2.10 > > > > Using $PIR table, 8 entries at 0xc00fdef0 > > > > acpi0: power button is handled as a fixed feature programming model. > > > > Timecounter "ACPI-fast" frequency 3579545 Hz > > > > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 > > > > acpi_cpu0: on acpi0 > > > > acpi_tz0: on acpi0 > > > > acpi_button0: on acpi0 > > > > acpi_button1: on acpi0 > > > > pcib0: port > > > > 0x5000-0x500f,0x4080-0x40ff,0x4000-0x407f,0xcf8-0xcff on acpi0 > > > > pci0: on pcib0 > > > > pcib0: slot 8 INTA is routed to irq 10 > > > > pcib0: slot 9 INTA is routed to irq 5 > > > > pcib0: slot 11 INTA is routed to irq 10 > > > > agp0: mem 0xe8000000-0xebffffff at > > > > device 0.0 on pci0 > > > > pcib1: at device 1.0 on pci0 > > > > pci1: on pcib1 > > > > pcib0: slot 1 INTA is routed to irq 11 > > > > pcib1: slot 0 INTA is routed to irq 11 > > > > pci1: at device 0.0 (no driver attached) > > > > dc0: port 0xd000-0xd0ff mem > > > > 0xef000000-0xef0003ff irq 10 at device 8.0 on pci0 > > > > dc0: Ethernet address: 00:04:5a:40:b5:0d > > > > miibus0: on dc0 > > > > ukphy0: on miibus0 > > > > ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > > > > dc1: port 0xd400-0xd4ff mem > > > > 0xef001000-0xef0010ff irq 5 at device 9.0 on pci0 > > > > dc1: Ethernet address: 00:a0:cc:34:54:93 > > > > miibus1: on dc1 > > > > dcphy0: on miibus1 > > > > dcphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > > > > dc2: <82c169 PNIC 10/100BaseTX> port 0xd800-0xd8ff mem > > > > 0xef002000-0xef0020ff irq 10 at device 11.0 on pci0 > > > > dc2: Ethernet address: 00:a0:cc:d6:ea:b4 > > > > miibus2: on dc2 > > > > bmtphy0: on miibus2 > > > > bmtphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > > > > isab0: at device 17.0 on pci0 > > > > isa0: on isab0 > > > > atapci0: port 0xdc00-0xdc0f at device > > > > 17.1 on pci0 > > > > ata0: at 0x1f0 irq 14 on atapci0 > > > > ata1: at 0x170 irq 15 on atapci0 > > > > fdc0: port > > > > 0x3f7,0x3f2-0x3f5 irq 6 drq 2 on acpi0 > > > > fdc0: FIFO enabled, 8 bytes threshold > > > > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > > > > atkbdc0: port 0x64,0x60 irq 1 on acpi0 > > > > atkbd0: flags 0x1 irq 1 on atkbdc0 > > > > kbd0 at atkbd0 > > > > psm0: irq 12 on atkbdc0 > > > > psm0: model IntelliMouse, device ID 3 > > > > orm0: