Patrick,
I tried both mice with appropriate changes in device as well as protocol
but the crash messages are same "No Mouse found"
If I run the generated XF86Config.new with "-allowMouseFailOpen" then I
get X running on my screen but of course without any mouse!!!

Sudev

On Tue, 2003-03-11 at 13:13, Patrick Regnouf wrote:
> First of all, what kind of mouse do you have is it a PS/2 (little round
> plug) or is it serial? (9 or 25 pins trapezoidal plug).
> 
> if your mouse is PS/2 then modify the XF86Config file so that it reads
> 
> 
> Section "InputDevice"
>       Identifier  "Mouse0"
>       Driver      "mouse"
>       Option      "Protocol" "PS/2"
>       Option      "Device" "/dev/psaux"
> EndSection
> 
> if your mouse is serial,  chances are that the following lines will
> work:
> 
> 
> Section "InputDevice"
>       Identifier  "Mouse0"
>       Driver      "mouse"
>       Option      "Protocol" "Microsoft"
>       Option      "Device" "/dev/ttyS0"
> EndSection
> 
> the line
> 
>       Option      "Device" "/dev/ttyS0"
> 
> refers to what would be called under DOS/Windows COM1, if the mouse is
> on COM2 then replace ttyS0 by ttyS1 ...
> 
> Good luck
> 
> /Patrick
> 
> 
> 
> 
> 
> On Tue, 2003-03-11 at 05:52, Sudev Barar wrote:
> > I have generated XF86Config.new many times and with different mice. I am
> > unable to start X as it always gives 
> > "(EE) xf86OpenSerial: Cannot open device /dev/mouse
> >     No such file or directory"
> > 
> > I edited the configuration file that is generated and changes mouse
> > definition to /dev/psaux but no luck. I even changed the mouse to serial
> > mouse and definition to ttyS0 with now luck.
> > 
> > Now I was thinking of making a link by using
> > "ln -sf /dev/ttyS0 /dev/mouse"
> > but I find that listing of dev directory shows some sort of link already
> > for /dev/ttyS0 to /dev/tts/0 What does this maen? Any harm if I go ahead
> > and make link for /dev/mouse on /dev/ttyS0????
> > 
> > TIA
> > Sudev
> > 
> > 
> > On Thu, 2003-02-27 at 16:15, Patrick Regnouf wrote:
> > > Just modify your lts.conf so that LOCAL_APPS=Y, your station will mount
> > > the user's home directory via NFS so that you can copy the file there
> > > ;-)
> > > 
> > > /Patrick
> > > 
> > > 
> > > On Thu, 2003-02-27 at 10:02, Sudev Barar wrote:
> > > > On Tue, 2003-02-25 at 19:04, Patrick Regnouf wrote:
> > > > > you can try to boot up in level 3 and run the following sequence of
> > > > > commands
> > > > > 
> > > > > bash# export HOME=/tmp
> > > > > bash# /usr/X11R6/bin/XFree86 -configure
> > > > > 
> > > > > you should end up with a workable XF86Config.new in your tmp directory 
> > > > > then try 
> > > > > 
> > > > > bash# /usr/X11R6/bin/XFree86 -xf86config /tmp/XF86Config.new -indirect
> > > > > server
> > > > > 
> > > > > if this works, then transfer the newly created XF86Config to you server
> > > > > and adjust lts.conf accordingly
> > > > > 
> > > > Lovely, thanks for explaining it so nicely, worked like a charm. Now the
> > > > problem is I do not know how to transfer it to my server!!! In bash all
> > > > directories are being shown as read only below the "/opt/ltsp/i386/"
> > > > directory. And I do not know how to access the server root or any other
> > > > directory. Help please.
> > > > Sudev Barar



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_____________________________________________________________________
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

Reply via email to