Originally Posted by PabloTwo
I meant to issue the command in a terminal which xinput
"which" is the command and "xinput" is the argument to the command. "which" searches your $PATH directories for the argument. If found, it prints the path. If not, it prints the $PATH directories searched...
Really? If xinput was not installed on the Live CD, then bash would have reported "bash: xinput: command not found".
Sorry, my careless word use, I meant the output showed a non-functioning command.
I ran the two in Live Fedora13, "which xinput" and "xinput", and pasted the output below:
[liveuser@localhost ~]$ which xinput
/usr/bin/which: no xinput in (/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/liveuser/bin)
[liveuser@localhost ~]$ xinput
bash: xinput: command not found
So I suppose I do not have it. Plain and simple. Do I need to run it as a root user? I guess I shouldn't be surprised. If my b43XX wireless worked on everything it wouldn't be an issue....probably. However, I got online in LiveCD with PCLinuxOS and went to Synaptic, hit "reload", did a search for xinput as suggested by a forum member, found 5 new packages, installed 4 of them. The 5th was titled something for Lxde keyboards. Then I tried to run my mouse fixes which work on Live CD/DVD in Ubuntu and variations of it, Mint, Ultimate Edition, also works in live-Knoppix:
xinput --set-prop (device id# here) "Device Accel Constant Deceleration" 3
xinput --set-prop (device id# here) "Device Accel Adaptive Deceleration" 5
But it still didn't work in PCLinuxOS. So I listed the xinput commands now available after my 4-pack install with xinput --help
and compared it to Ubuntu's list and found at the very end, one command line that was not found in PCLinuxOS. This:
xinput set-prop <device> [--type=atom|float|int] [--format=8|16|32] <property> <val> [<val> ...]
Being sure it all runs in Live CD before an install can be good advice. I never tested anything with my first install LOL. Came out OK though. And there are probably fixes for that one missing command in PCLOS I didn't yet explore.
Originally Posted by PabloTwo
I use XFCE in F12. The "acceleration" slider controls speed of my mouse just fine. I would think that would work from the Live CD as well.
To be honest, I am not sure if I tried Fedora's Xfce, I don't think I did. I tried the Design Spin & Games Spin in Gnome. But I tried Xfce in a few other distros like PCLinuxOS, Xubuntu, DreamLinux, and probably more. Same result for each. You move the sliders back and forth, not only is the speed slightly fast for me but the mouse won't travel any faster or slower when you move the speed slider to a new position. The Xfce mouse controls in the GUI are different than Gnome's on each also. Makes me think...
What could it be? Since each Linux is modular with Core, Xorg, Desktop, Browser plus applications, the problem is a function of how Xorg interfaces with each desktop style and your mouse choice, with Xorg being the same in all? Not sure why my mouse is singled out. All 3 of my mice are at least 1000dpi: Logitech optical LX3, Microsoft Wireless 5000 and a Wired 4500 both BlueTrack technology. So could it be the dpi is moderately high? Gamers with higher dpi than mine have the problem too. (I give Microsoft credit for great mice and keyboards, better peripherals than Logitech, but I'm planning on not making it my primary OS, working on that now.)
What is your PC type and mouse type?
Boot Up Screen Text
I ran the Live CD and hit ESC at the splash to get the text, it says mostly this,
I didn't get it all exactly, I'd have to photograph it:
Welcome to Fedora
Interactive hit "I"
starting udev:udev-work 618...
usr/bin/vmouse-detect' unexpected exit with status 0x000b
udevd-work ': usr/bin/vmouse-detect' unexpected exit with status 0x000b