Re: Microsoft mouse, ums and wsmouse
> > Sigh. Yet another Microsoft mouse with a botched report descriptor > > layout. > > > > I'm afraid that this device will not work under OpenBSD until enough > > information is found to make it work. > > This is weird. What do you mean by more information? I think I have > been able to use this mouse under freebsd, netbsd and Linux. I am > guessing all these OSes have code for this mouse. Not exactly. All these systems have various workarounds to try and support the various Microsoft mice. Unfortunately, every time they introduce a new mouse model, the workarounds don't apply. Now that's creative people, for sure: they always find new ways to be incompatible with the specification they contributed to. Anyways, FreeBSD seems to have a new heuristic since a few month, which might help. I'll try to give it a try soon. In the meantime your mouse will not work under OpenBSD. Miod
Re: Microsoft mouse, ums and wsmouse
So, What can I do to make this work? :) Luis Useche use...@gmail.com On Sun, Jul 26, 2009 at 5:51 PM, Miod Vallat wrote: > Hello, > >> I am new to OpenBSD and I was giving it a try by installing in my laptop. My >> problem is that my usb wireless mouse does not work on X or with wsmoused. >> From a message standpoint, everything seem normal. I got from dmesg: >> >> uhidev0 at uhub4 port 2 configuration 1 interface 0 "Microsoft Microsoft >> Wireless Optical Mouse\M-. 1.00" rev 2.00/0.07 addr 2 >> uhidev0: iclass 3/1, 23 report ids >> ums0 at uhidev0 reportid 17: 3 buttons, Z dir >> wsmouse1 at ums0 mux 0 >> uhid0 at uhidev0 reportid 18: input=0, output=0, feature=1 >> uhid1 at uhidev0 reportid 19: input=1, output=0, feature=0 >> uhid2 at uhidev0 reportid 20: input=1, output=0, feature=0 >> uhid3 at uhidev0 reportid 21: input=3, output=0, feature=0 >> uhid4 at uhidev0 reportid 23: input=0, output=0, feature=1 >> >> Which means that the mouse is detected and attached to the wsmouse driver as >> "wsmouse1". However, it does not work at all. I have been looking all day >> for a solution with no success. At this point I am clueless. >> > > Sigh. Yet another Microsoft mouse with a botched report descriptor > layout. > > I'm afraid that this device will not work under OpenBSD until enough > information is found to make it work. > > Miod
Re: Microsoft mouse, ums and wsmouse
> Sigh. Yet another Microsoft mouse with a botched report descriptor > layout. > > I'm afraid that this device will not work under OpenBSD until enough > information is found to make it work. This is weird. What do you mean by more information? I think I have been able to use this mouse under freebsd, netbsd and Linux. I am guessing all these OSes have code for this mouse. Luis.
Re: Microsoft mouse, ums and wsmouse
Hello, > I am new to OpenBSD and I was giving it a try by installing in my laptop. My > problem is that my usb wireless mouse does not work on X or with wsmoused. > From a message standpoint, everything seem normal. I got from dmesg: > > uhidev0 at uhub4 port 2 configuration 1 interface 0 "Microsoft Microsoft > Wireless Optical Mouse\M-. 1.00" rev 2.00/0.07 addr 2 > uhidev0: iclass 3/1, 23 report ids > ums0 at uhidev0 reportid 17: 3 buttons, Z dir > wsmouse1 at ums0 mux 0 > uhid0 at uhidev0 reportid 18: input=0, output=0, feature=1 > uhid1 at uhidev0 reportid 19: input=1, output=0, feature=0 > uhid2 at uhidev0 reportid 20: input=1, output=0, feature=0 > uhid3 at uhidev0 reportid 21: input=3, output=0, feature=0 > uhid4 at uhidev0 reportid 23: input=0, output=0, feature=1 > > Which means that the mouse is detected and attached to the wsmouse driver as > "wsmouse1". However, it does not work at all. I have been looking all day > for a solution with no success. At this point I am clueless. > Sigh. Yet another Microsoft mouse with a botched report descriptor layout. I'm afraid that this device will not work under OpenBSD until enough information is found to make it work. Miod
Re: Microsoft mouse, ums and wsmouse
In case this helps, I will attach my complete dmesg.
OpenBSD 4.5 (GENERIC.MP) #108: Sat Feb 28 14:58:58 MST 2009
dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP
cpu0: Intel(R) Core(TM)2 Duo CPU T5250 @ 1.50GHz ("GenuineIntel"
686-class) 1.50 GHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,EST,TM2,CX16,xTPR
real mem = 2137165824 (2038MB)
avail mem = 2058231808 (1962MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 08/15/07, BIOS32 rev. 0 @
0xffa10, SMBIOS rev. 2.4 @ 0xf7190 (45 entries)
bios0: vendor Dell Inc. version "A02" date 08/15/2007
bios0: Dell Inc. Inspiron 1420
acpi0 at bios0: rev 2
acpi0: tables DSDT FACP HPET APIC MCFG SLIC BOOT SSDT
acpi0: wakeup devices PCI0(S5) PCIE(S4) USB1(S0) USB2(S0) USB3(S0)
USB4(S0) USB5(S0) EHC2(S0) EHCI(S0) AZAL(S3) RP01(S3) RP02(S3)
RP03(S3) RP04(S3) RP05(S3) RP06(S5) LID_(S3) PBTN(S4) MBTN(S5)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 14318179 Hz
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: apic clock running at 166MHz
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM)2 Duo CPU T5250 @ 1.50GHz ("GenuineIntel"
686-class) 1.50 GHz
cpu1:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,EST,TM2,CX16,xTPR
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins
ioapic0: misconfigured as apic 0, remapped to apid 2
acpiprt0 at acpi0: bus 3 (PCIE)
acpiprt1 at acpi0: bus -1 (AGP_)
acpiprt2 at acpi0: bus 11 (RP01)
acpiprt3 at acpi0: bus 12 (RP02)
acpiprt4 at acpi0: bus -1 (RP03)
acpiprt5 at acpi0: bus 13 (RP04)
acpiprt6 at acpi0: bus -1 (RP05)
acpiprt7 at acpi0: bus 9 (RP06)
acpiprt8 at acpi0: bus 0 (PCI0)
acpicpu0 at acpi0: C3
acpicpu1 at acpi0: C3
acpitz0 at acpi0: critical temperature 87 degC
acpibtn0 at acpi0: LID_
acpibtn1 at acpi0: PBTN
acpibtn2 at acpi0: SBTN
acpiac0 at acpi0: AC unit offline
acpibat0 at acpi0: BAT0 model "DELL PR6937" serial 24 type LION oem "Sanyo"
acpivideo at acpi0 not configured
acpivideo at acpi0 not configured
acpivideo at acpi0 not configured
bios0: ROM list: 0xc/0xf000! 0xcf000/0x1000
cpu0: unknown Enhanced SpeedStep CPU, msr 0x0613092b06000613
cpu0: using only highest and lowest power states
cpu0: Enhanced SpeedStep 1000 MHz (1004 mV): speeds: 1500, 1000 MHz
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
pchb0 at pci0 dev 0 function 0 "Intel GM965 Host" rev 0x0c
vga1 at pci0 dev 2 function 0 "Intel GM965 Video" rev 0x0c
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
intagp0 at vga1
agp0 at intagp0: aperture at 0xe000, size 0x1000
inteldrm0 at vga1: apic 2 int 16 (irq 11)
drm0 at inteldrm0
"Intel GM965 Video" rev 0x0c at pci0 dev 2 function 1 not configured
uhci0 at pci0 dev 26 function 0 "Intel 82801H USB" rev 0x02: apic 2
int 20 (irq 10)
uhci1 at pci0 dev 26 function 1 "Intel 82801H USB" rev 0x02: apic 2
int 21 (irq 9)
ehci0 at pci0 dev 26 function 7 "Intel 82801H USB" rev 0x02: apic 2
int 22 (irq 7)
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1
azalia0 at pci0 dev 27 function 0 "Intel 82801H HD Audio" rev 0x02:
apic 2 int 21 (irq 9)
azalia0: codecs: Sigmatel STAC9228X, Conexant/0x2c06, using Sigmatel STAC9228X
audio0 at azalia0
ppb0 at pci0 dev 28 function 0 "Intel 82801H PCIE" rev 0x02: apic 2
int 16 (irq 0)
pci1 at ppb0 bus 11
ppb1 at pci0 dev 28 function 1 "Intel 82801H PCIE" rev 0x02: apic 2
int 17 (irq 0)
pci2 at ppb1 bus 12
wpi0 at pci2 dev 0 function 0 "Intel PRO/Wireless 3945ABG" rev 0x02:
apic 2 int 17 (irq 10), MoW1, address 00:18:de:be:50:48
ppb2 at pci0 dev 28 function 3 "Intel 82801H PCIE" rev 0x02: apic 2
int 19 (irq 0)
pci3 at ppb2 bus 13
ppb3 at pci0 dev 28 function 5 "Intel 82801H PCIE" rev 0x02: apic 2
int 17 (irq 0)
pci4 at ppb3 bus 9
bge0 at pci4 dev 0 function 0 "Broadcom BCM5906M" rev 0x02, BCM5906 A2
(0xc002): apic 2 int 17 (irq 10), address 00:1c:23:f8:62:90
brgphy0 at bge0 phy 1: BCM5906 10/100baseTX PHY, rev. 0
uhci2 at pci0 dev 29 function 0 "Intel 82801H USB" rev 0x02: apic 2
int 20 (irq 10)
uhci3 at pci0 dev 29 function 1 "Intel 82801H USB" rev 0x02: apic 2
int 21 (irq 9)
uhci4 at pci0 dev 29 function 2 "Intel 82801H USB" rev 0x02: apic 2
int 22 (irq 7)
ehci1 at pci0 dev 29 function 7 "Intel 82801H USB" rev 0x02: apic 2
int 20 (irq 10)
usb1 at ehci1: USB revision 2.0
uhub1 at usb1 "Intel EHCI root hub" rev 2.00/1.00 addr 1
ppb4 at pci0 dev 30 function 0 "Intel 82801BAM Hub-to-PCI" rev 0xf2
pci5 at ppb4 bus 3
"Ricoh 5C832 Firewire" rev 0x05 at pci5 dev 1 function 0 not configured
sdhc0 at pci5 dev 1 function 1 "Ricoh 5C822 SD/MMC" rev 0x22: apic 2
int 18 (irq 4)
sdmmc0 at sdhc0
"Ricoh 5C843 MMC" rev 0x12 at pci5 dev 1 function 2 not configured
"Ricoh 5C592 Memory Stick" rev
Re: Microsoft mouse, ums and wsmouse
On Wed, Jul 22, 2009 at 9:51 PM, Hendrickson, Kenneth wrote: > turn on wsmouse in /etc/rc.conf.local > > read /etc/rc.conf (but don't modify it) to see what it does I'm sorry I didn't mention it. The wsmoused is working and, in fact, my touchpad is perfectly fine for both: console and X. Another suggestion? Luis Useche use...@gmail.com
Re: Microsoft mouse, ums and wsmouse
turn on wsmouse in /etc/rc.conf.local read /etc/rc.conf (but don't modify it) to see what it does -Original Message- From: owner-m...@openbsd.org [mailto:owner-m...@openbsd.org] On Behalf Of Luis Useche Sent: Wednesday, July 22, 2009 5:47 PM To: misc@openbsd.org Subject: Microsoft mouse, ums and wsmouse Hi Guys, I am new to OpenBSD and I was giving it a try by installing in my laptop. My problem is that my usb wireless mouse does not work on X or with wsmoused. >From a message standpoint, everything seem normal. I got from dmesg: uhidev0 at uhub4 port 2 configuration 1 interface 0 "Microsoft Microsoft Wireless Optical Mouse\M-. 1.00" rev 2.00/0.07 addr 2 uhidev0: iclass 3/1, 23 report ids ums0 at uhidev0 reportid 17: 3 buttons, Z dir wsmouse1 at ums0 mux 0 uhid0 at uhidev0 reportid 18: input=0, output=0, feature=1 uhid1 at uhidev0 reportid 19: input=1, output=0, feature=0 uhid2 at uhidev0 reportid 20: input=1, output=0, feature=0 uhid3 at uhidev0 reportid 21: input=3, output=0, feature=0 uhid4 at uhidev0 reportid 23: input=0, output=0, feature=1 Which means that the mouse is detected and attached to the wsmouse driver as "wsmouse1". However, it does not work at all. I have been looking all day for a solution with no success. At this point I am clueless. Any help is very appreciated. Luis Useche use...@gmail.com
