Date: Wed, 25 Mar 2009 00:36:28 -0600 From: Tim Judd <tajudd@gmail.com> To: Polytropon <freebsd@edvax.de> Cc: freebsd-questions@freebsd.org, Neal Hogan <nealhogan@gmail.com> Subject: Re: xorg-server-1.5.3_7, /usr/ports/UPDATING, mouse Message-ID: <1237962988.33722.6.camel@t60.local.zz> In-Reply-To: <20090325034501.c5caff1d.freebsd@edvax.de> References: <ab7b49bc0903231304s7b99689et1f4c1fca4efc4bec@mail.gmail.com> <1237948175.14299.6.camel@t60.local.zz> <20090325034501.c5caff1d.freebsd@edvax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 2009-03-25 at 03:45 +0100, Polytropon wrote: > On Tue, 24 Mar 2009 20:29:35 -0600, Tim Judd <tajudd@gmail.com> wrote: > > So I don't think the hal has the concept of joining the keyboard and > > mouse together to a single usb device. The pair works beautifully in > > the console... so I'm not sure if this is a bug worthy of reporting, or > > if I should research it more and try to discover the solution with a > > logitech pair that is known to work in the console to work in hal. s/single usb device/single usb plug/ > > Does the combination result in two devices (ukbd0, ums0)? Maybe > it's possible to instruct HAL to use the devices explicitely, by > "hard coding" them into some configuration file? Yes, FreeBSD/devd/devfs had created a kbd0 and ums0 HAL just didn't seem to recognize ums0 being listed too.. maybe because before it setup kbd0, ums0 appeared and it just got left behind? maybe because it already linked kbd0 to the plug/jack it was plugged into, it ignored the second device (this case, the mouse)? I even tried (by of course powerdown first) the USB+Mouse PS2 plug (both as original plug onto the Logitech pair) in case it might have picked up the PS2 and let it run with that --- it didn't find the PS2 mouse (by "found" I mean Xorg adding/enabling that device so the cursor moves). I was more concerned today (@work) to get my desktop operational. I can try later to diagnose, pick apart, etc etc the flaws of dbus and/or hal to submit a report. I felt it was necessary to announce this shortcoming, in case the OP was trying to use the same kind of device.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1237962988.33722.6.camel>