hi Folks,

Lessons-learned posting for my problem...Posting starts here:

Back again...same problem, different day. Installed MEPIS 3.3-4 and FlightGear 
9.9.1, thinking the newer MEPIS would do a better job recognizing USB yoke 
and pedals. Not so.

<stuff deleted...stuff I had done...not critical to lesson learned>

[I sent] "Now, I need newbie help. Short cryptic answers cause another email 
asking  clarification, so if you can, give me some links to explore or  
step-by-step  things I can do. That would be much appreciated."

[This is critical...newbies need more than cryptic three-word "do-this" 
advice.]

From Alex Perry, came this calm reply: So it seems.  I suggest you look in 
this directory ...
        cd /sys/class/input
If you don't see a directories called "js0" and "js1", something's wrong.
I'll get to the rest (below) after your reply to that question.

[See? Good newbie advice! I could follow it!] 

Now, to be fair, I did get replies from  Mike Lowdon 
<[EMAIL PROTECTED]> and Didier <[EMAIL PROTECTED]>, who have been 
helpful in the past.

Alex: Following it along: > So it seems.  I suggest you look in this 
directory ...
>         cd /sys/class/input
> If you don't see a directories called "js0" and "js1", something's wrong.
Dick: here goes: 

[EMAIL PROTECTED] ls
event0  event2  input0  input2  js0  mice
event1  event3  input1  input3  js1  mouse0

Looks like js0 and ks1 are in there...

 Alex: > Yep.  Each of those directories should contain a file called "dev".
> Verify they're as expected and contain one line with two numbers:
>       cat /sys/class/input/js*/dev
> The response should be something like:
>       13:0
>       13:1
>
> You should have a directory "/dev/input" so, if you don't,
> just create it.  You have to be root to do this, of course.
>       mkdir -p /dev/input
>       cd /dev/input
Dick: I asked if the dev/input was under sys/class/input/js*/dev, and her 
answered:
Alex: No, that is off the root, not underneath /sys/class

Alex clarified: 
>>> You should have a directory "/dev/input" so, if you don't,
> > > just create it.  You have to be root to do this, of course.
> > >     mkdir -p /dev/input
> > >     cd /dev/input
> > >
> > > This is where the magic device files for the joystick should be.
> > > If the contents of those two files was as I indicated, try typing:
> > >     ls -l | grep 13,
> > > Notice the trailing comma.  Look in the output for the "13,  0":

Dick: here's what we got:

[EMAIL PROTECTED] ls -l | grep 13,
crw-rw----  1 root root 13, 64 2006-02-14 13:29 event0
crw-rw----  1 root root 13, 65 2006-02-14 13:29 event1
crw-rw----  1 root root 13, 66 2006-02-15 12:43 event2
crw-rw----  1 root root 13, 67 2006-02-15 12:43 event3
crw-rw-r--  1 root root 13,  0 2006-02-15 12:43 js0
crw-rw-r--  1 root root 13,  1 2006-02-15 12:43 js1
crw-rw----  1 root root 13, 63 2006-02-14 13:28 mice
crw-rw----  1 root root 13, 32 2006-02-14 13:28 mouse0

Looks like the js0 and js1 is in there...now, the next step?

Dick: Well OK!  I created the dir, and ls'd it, and it had content! So, I 
fired up FlightGear, and the throttle, flaps,  yoke, hat, and pedals work. I 
have to figure out how to get the other buttons back to the default 
setting...
If you have a file that does that, great. Otherwise, I will see if I can get 
into the documentation and set the buttons.

So, patient guidance to the newbie has worked really well!!! Many thanks to 
Alex Perry!

Cheers,
Dick





-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642
_______________________________________________
Flightgear-users mailing list
Flightgear-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-users

Reply via email to