I just wanted to not that synaptics works now for me. I found out by accident after installing an ati driver from updates-testing when trying to get the latest f8 kernel. I needed to switch to vesa and scrolling and normal mouse operations returned with an xorg.conf I have back the rawhide ati with "radeon" as the driver and synaptics is still functional. Jim
On Tue, 2007-12-04 at 17:46 -0500, Jim Cornette wrote:
I just wanted to not that synaptics works now for me. I found out by accident after installing an ati driver from updates-testing when trying to get the latest f8 kernel. I needed to switch to vesa and scrolling and normal mouse operations returned with an xorg.conf I have back the rawhide ati with "radeon" as the driver and synaptics is still functional.
Cool. Good info to have. Now just to get synaptics auto-setup in the case where you don't have an xorg.conf
Jeremy
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Jim Cornette wrote:
I just wanted to not that synaptics works now for me. I found out by accident after installing an ati driver from updates-testing when trying to get the latest f8 kernel. I needed to switch to vesa and scrolling and normal mouse operations returned with an xorg.conf I have back the rawhide ati with "radeon" as the driver and synaptics is still functional.
Finally got round to pulling this onto my laptop & although synaptics is mostly working now, the "extra" mouse keys on my thinkpad T60 (the group of three above the pad) are not working. The two below the pad are working just fine.
Anyone else seeing this, or have suggestions to debug?
xorg-x11-server-common-1.4.99.1-0.13.fc9.x86_64 xorg-x11-server-Xorg-1.4.99.1-0.13.fc9.x86_64 xorg-x11-drv-mouse-1.2.3-3.fc9.x86_64 synaptics-0.14.4-12.fc9.x86_64
Regards, Bryn.
On Fri, 2007-12-14 at 10:26 +0000, Bryn M. Reeves wrote:
Finally got round to pulling this onto my laptop & although synaptics is mostly working now, the "extra" mouse keys on my thinkpad T60 (the group of three above the pad) are not working. The two below the pad are working just fine.
Anyone else seeing this, or have suggestions to debug?
See if you get any output from /dev/input/event* when you press them.
Dnia 2007-12-14, o godz. 10:26:51 "Bryn M. Reeves" breeves@redhat.com napisał(a):
Finally got round to pulling this onto my laptop & although synaptics is mostly working now, the "extra" mouse keys on my thinkpad T60 (the group of three above the pad) are not working. The two below the pad are working just fine.
Anyone else seeing this, or have suggestions to debug?
The keys above the touchpad are the mouse buttons of the "joystick", not the touchpad. If it's disabled in the BIOS, the buttons shouldn't work. I remember being surprised when the joystick and its buttons stopped working when I plugged PS/2 mouse in :) Anyhow, even if it's enabled, it's the secound mouse device, which Xorg should detect by itself, unless you have a static xorg.conf telling it to you the touchpad exclusively.
Lam
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Leszek Matok wrote:
The keys above the touchpad are the mouse buttons of the "joystick", not the touchpad. If it's disabled in the BIOS, the buttons shouldn't work. I remember being surprised when the joystick and its buttons stopped working when I plugged PS/2 mouse in :) Anyhow, even if it's enabled, it's the secound mouse device, which Xorg should detect by itself, unless you have a static xorg.conf telling it to you the touchpad exclusively.
Thanks Lam, I wondered if it was something like this. The device is enabled in the BIOS and was working fine with the same xorg.conf before the mass X update.
Removing the explicit InputDevice section for the synaptics gives me working "joystick" buttons but I loose the synaptics functionality. I'm guessing that with a bit of fiddling they can both be made to work.
Previously this "just worked" however.
Regards, Bryn.
Bryn M. Reeves wrote:
Removing the explicit InputDevice section for the synaptics gives me working "joystick" buttons but I loose the synaptics functionality. I'm guessing that with a bit of fiddling they can both be made to work.
Previously this "just worked" however.
I have a USB mouse connected which works when running without an xorg.conf file in tandem with the pointer only for the touchpad. With the xorg.conf file, the USB mouse does not work but the synaptics functions as before the X problem. Secondary pointing devices might need attention when running with an xorg.conf file.
Jim
Regards, Bryn.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Jim Cornette wrote:
Bryn M. Reeves wrote:
Removing the explicit InputDevice section for the synaptics gives me working "joystick" buttons but I loose the synaptics functionality. I'm guessing that with a bit of fiddling they can both be made to work.
Previously this "just worked" however.
I have a USB mouse connected which works when running without an xorg.conf file in tandem with the pointer only for the touchpad. With the xorg.conf file, the USB mouse does not work but the synaptics functions as before the X problem. Secondary pointing devices might need attention when running with an xorg.conf file.
Right, this is what I am seeing too. I've been playing around with different combinations of InputDevice this morning without success but the testing is being slowed by another problem I'm hitting with the intel driver - I'll open a separate BZ for that.
Cheers, Bryn.
On Fri, Dec 14, 2007 at 12:22:15PM +0000, Bryn M. Reeves wrote:
I have a USB mouse connected which works when running without an xorg.conf file in tandem with the pointer only for the touchpad. With the xorg.conf file, the USB mouse does not work but the synaptics functions as before the X problem. Secondary pointing devices might need attention when running with an xorg.conf file.
Right, this is what I am seeing too. I've been playing around with different combinations of InputDevice this morning without success but the testing is being slowed by another problem I'm hitting with the intel driver - I'll open a separate BZ for that.
I opened a bug on this and referenced this thread since I couldn't find any existing bug:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Chuck Anderson wrote:
I opened a bug on this and referenced this thread since I couldn't find any existing bug:
I got this working via the config file in the end & didn't have a chance to go back and figure out why it didn't "just work" anymore.
Regards, Bryn.