Re: PS/2 mouse problems with -CURRENT

2003-01-22 Thread Igor Roboul
On Wed, Jan 22, 2003 at 12:49:04AM -0600, Chip Norkus wrote: > But try disabling ACPI and see if your PS/2 mouse suddenly works. ;) As you can see from my first post >> Same part of newer -CURRENT (I have disable ACPI, but I get same >> result with ACPI too): >> atkbdc0: at port 0x64,0x60 on isa

Re: PS/2 mouse problems with -CURRENT

2003-01-21 Thread Chip Norkus
On Wed Jan 22, 2003; 09:38AM +0300 Igor Roboul propagated the following: > On Fri, Jan 17, 2003 at 04:27:36PM +0300, Igor Roboul wrote: > > Hello, > > does anybody have problems with PS/2 mouse attached to PC with recent > > -CURRENT? > > > > Motherboard: MSI MS6337LE5 (i815 chipset) > > Mouse: Ge

Re: PS/2 mouse problems with -CURRENT

2003-01-21 Thread Igor Roboul
On Fri, Jan 17, 2003 at 04:27:36PM +0300, Igor Roboul wrote: > Hello, > does anybody have problems with PS/2 mouse attached to PC with recent > -CURRENT? > > Motherboard: MSI MS6337LE5 (i815 chipset) > Mouse: Genius NetScroll+ Can't belive that this promlem is specific to exUSSR :-) But who knows?

Re: PS/2 mouse problems with -CURRENT

2003-01-17 Thread Vitaly Markitantov
On Fri, Jan 17, 2003 at 04:27:36PM +0300, Igor Roboul wrote: > Hello, > does anybody have problems with PS/2 mouse attached to PC with recent > -CURRENT? > > Mouse is recognized by kernel and moused, but cursor is moving VERY > slow, no visible reaction to buttons etc. This happens in text mode >

PS/2 mouse problems with -CURRENT

2003-01-17 Thread Igor Roboul
Hello, does anybody have problems with PS/2 mouse attached to PC with recent -CURRENT? Mouse is recognized by kernel and moused, but cursor is moving VERY slow, no visible reaction to buttons etc. This happens in text mode and in X11. When in X11, it happens when Option "Device" "/dev/sysmou

Re: ps/2 mouse problems [boot -v messages]

2001-09-11 Thread David W. Chapman Jr.
On Wed, Sep 12, 2001 at 10:57:31AM +0900, Kazutaka YOKOTA wrote: > Please send ENTIRE output, if possilbe, rather than partial exerpt. > Also send "boot -v" output when the acpi module is not loaded. > Please also tell which motherboard you have. > It would be also useful to dump ACPI data blocks

Re: ps/2 mouse problems [boot -v messages]

2001-09-11 Thread Kazutaka YOKOTA
Please send ENTIRE output, if possilbe, rather than partial exerpt. Also send "boot -v" output when the acpi module is not loaded. Please also tell which motherboard you have. It would be also useful to dump ACPI data blocks using acpidump(8). >Here's some more info on my ps/

ps/2 mouse problems [boot -v messages]

2001-09-11 Thread David W. Chapman Jr.
Here's some more info on my ps/2 mouse problems I managed to dig up from boot -v and some other errors I wanted ot know if I should worry about. atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0047 atkbd: keyboa

ps/2 mouse problems

2001-07-14 Thread undergra
Hi, i have a ps/2 mouse and works perfectly with my FreeBSD 4.3-stable, but on my FreeBSD 5.0-current doesn't work. I see the line of the mouse on dmesg output (psm0: irq 12 on atkbdc0). When i type "moused -t ps/2 -p /dev/psm0" and "vidcontrol -m on" i don't see the mouse cursor. Any problem w

Workaround for PS/2 mouse problems with recent -current

2001-06-17 Thread Anton Berezin
Commenting out hint.atkbd.0.* and hint.psm.0.* fixed the problem that others reported. Little investigation showed that the new resource_find() function in kern/subr_bus.c finds two atkbd0 and two psm0, one of each from kern_envp, and the other one from static_hints; no wildcard matches were inv