On Fri, 2004-06-11 at 09:47, Brian Payst wrote: > Here's my config for a USB mouse for one client: > > MODULE_01 = usb-uhci > MODULE_02 = usbmouse > MODULE_03 = mousedev > MODULE_04 = usbkbd > MODULE_05 = keybdev > X_MOUSE_DEVICE = "/dev/input/mice" > X_MOUSE_PROTOCOL = "IMPS/2" > > > Jeff Self wrote: > > > I am having trouble getting a thin client to use a USB mouse. I've got > > it working if I put the following line under the default section of my > > lts.conf file: > > > > X_MOUSE_DEVICE = "/dev/input/mouse0" > > > > Then I load the following modules under one of the thin client sections: > > > > [tc001] > > MODULE_01 = /kernel/drivers/usb/usbcore.o > > MODULE_02 = /kernel/drivers/usb/host/uhci.o > > MODULE_03 = /kernel/drivers/input/input.o > > MODULE_04 = /kernel/drivers/input/mousedev.o > > MODULE_05 = /kernel/drivers/usb/usbmouse.o > > > > I'd rather keep my X_MOUSE_DEVICE in the default section set to > > "/dev/psaux" so I tried adding a line under [tc001] for X_MOUSE_DEVICE = > > "/dev/input/mouse0", and the system would then hang on bootup. > > > > Any suggestions? > >
Thanks. That worked. I'm thinking that I have to include both the X_MOUSE_DEVICE and X_MOUSE_PROTOCOL for the thin client settings. Using just X_MOUSE_DEVICE caused my system to hang on bootup. -- Jeff Self Dept. of Information Technology City of Newport News 757.926.3741 ------------------------------------------------------- This SF.Net email is sponsored by the new InstallShield X. >From Windows to Linux, servers to mobile, InstallShield X is the one installation-authoring solution that does it all. Learn more and evaluate today! http://www.installshield.com/Dev2Dev/0504 _____________________________________________________________________ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
