LinuxMCE Forums
General => Users => Topic started by: caiman on October 12, 2007, 05:37:08 pm
-
Got a gyration GO air mouse (http://wiki.linuxmce.org/index.php/Gyration_Go_2.4_air_mouse (http://wiki.linuxmce.org/index.php/Gyration_Go_2.4_air_mouse)).
Everything is working fine except absolute controls. From the wiki:
If you're using UI2's 3 button navigation model, all the normal media control options on the traditional remote are replaced with one button: media (ie the left soft button or F6). Press this and then move the pointer up and down for your skip functions (ie ch+, ch-, skip fwd, skip back), and move the pointer left and right for speed control (ie rewind, fast forward). The further you move, the faster the media playback changes. If you keep the button held down (the left soft button or F6), then your movement is absolute, not relative, and instead of the traditional jog shuttle-type control, moving to the right goes to the end of your media, and moving left to the beginning
Relative controls (one short click on the MEDIA or AMBIANCE button) works fine. If I leave the MEDIA or AMBIANCE (F6 or F8) button pressed to enter obsolute controls mode, for example to find a specific scene in a video file, the prompt on the screen starts blinking and I don't get to the actual scene access feature.
Has anyone got experience with this ?
-
I think I have the same issue. Never really got around to looking into it. When I hold the button (instead of releasing it) the cursor and OSD start flickering in a wierd way after moving it. However it does work when holding F6 or F8 on the keyboard.
I just blamed the older graphics card (and older nvidia driver version) since nobody else reported this problem I wanted to test it on a few other configurations as well first. The laptop I use it with has a geforce2go graphics card iirc.
-
Hi Zaerc,
I have a GeForce 7600 GT. I would more think of a problem with the Gyration/mouse hardware or driver. It seems it's sending the info into bulks rather than a continuous stream. I get the problem as well sometimes when I do a brief press (to go into relative control mode), then move the cursor to the right to fast forward the movie. When this happens, I have to press the left button a couple of times and try again, it works.
But absolute controls has never worked with the gyro.
I wonder if the fiirechief has the same problem ?
-
I just got a gyro mouse, the gyration version shown in the demo. The absolute scrolling doesn't work for me either. It sometimes comes on, and sometimes doesn't. I was looking for specific instructions on how to use it, but I guess it still a little buggy?
-
bump.. just wondering if anyone had found out anymore info on this topic
-
just a few extra infos since I've got the same problem:
When I recieved my new Gyro Mouse I just plugged it in the running system, wich caused, that the three buttons could not be used, BUT when I hit the F6 or F8 on the keyboard, I could control the absolute volume or media position...
After a reboot, the three buttons on the mouse are working, but there is no way to scroll absolutely neither with holding down the buttons or the F6 or F8 key on my keyboard...
Don't know if this helps, but I'm also looking forward to someone helping us out...
augalex
-
I guess this bug should be reported in mantis then.
-
You report it, Zaerc?
You're the one with more know-how....
augalex
-
submitted.
-
the solution is supposedly to : 'You need to reload the router after adding the gyro dongle, to let orbiter initialize the hid module.'
i got this from the mantis update...will see if it works before i have to go to work >:(
yeah so i:
deleted the gyromouse from the system via the admin panel
reloaded the router
plugged in the dongle.
let it download and install the software.
reloaded the router when it was done.
noticed it installing something called usbraw
when it was done, reloaded again but still nothing.
if anyone else has any uck, please let us know.
-
I have reopened it, since "reloading the router" doesn't solve anything.
-
I have reopened it, since "reloading the router" doesn't solve anything.
Thanks
-
Hi guys,
I added my steps in the mantis, but I'm still running 7.04, and the answer from Ender was:
"Did you try this with 0710beta's ? The issue you are describing was happening with 0704 if the user activated manually the repeated keys while Orbiter was running."
Anybody got the problem still under 7.10, or is it solved?
greetz augalex
-
Hi guys,
I added my steps in the mantis, but I'm still running 7.04, and the answer from Ender was:
"Did you try this with 0710beta's ? The issue you are describing was happening with 0704 if the user activated manually the repeated keys while Orbiter was running."
Anybody got the problem still under 7.10, or is it solved?
greetz augalex
im wondering too since it doesnt seem that we are going to get a straight answer / fix for 7.04.
-
I'm a bit amazed they claim to be unable to reproduce this, I've never seen this work properly at all. Anyway I posted some more info as well, hope that helps a bit to figure this out.
-
Had this problem in 0704, 0710B2 and 0710B3.
-
Just wondering if something happened,
couldn't make or even find some progress in this case...
augalex
-
That's very odd... I actually got it working out of the box when running 0704. I do remember having a problem with it once, but it was related to the video drivers...
-
That's very odd... I actually got it working out of the box when running 0704. I do remember having a problem with it once, but it was related to the video drivers...
which video drivers are you using?
-
I was messing around with several different versions of nVidia drivers using different settings. Basically what was happening was direct rendering wasn't fully working so the GL menu that popped up blinked constantly.
-
I was messing around with several different versions of nVidia drivers using different settings. Basically what was happening was direct rendering wasn't fully working so the GL menu that popped up blinked constantly.
thats exactly my problem. and about the best description of how to go about fixing it...what were the final drivers you wound up using?
-
Still got the same issue with 0710beta4, nvidia driver 169.07
According to glxinfo, direct rendering is enabled.
/usr/pluto/bin# DISPLAY=:0 glxinfo | grep direct
direct rendering: Yes
dopey, when you were seeing the problem, was glxinfo reporting direct rendering as enabled ?
Sam
-
I honestly don't remember. It was a long time ago. I'm pretty sure I commented on it somewhere in the forums, but like I said, it was a long time ago.
That said, I'm pretty sure UI2 won't even load if DRI is disabled, so it most likely was.
I just installed b4 about two weeks ago, but I haven't got the damn thing stable yet... so I haven't really done any playing of media to say whether or not I get that issue with a vanilla b4 install or not.
Question, is compositing working? You should see a line such as below in /var/log/Xorg.0.log
NVIDIA(0): Enabling 32-bit ARGB GLX visuals
-
Still seeing the same old problem here, while:
root@moon19:~# DISPLAY=:0 glxinfo | grep direct
direct rendering: Yes
root@moon19:~# grep 'ARGB GLX visuals' /var/log/Xorg.0.log
(**) NVIDIA(0): Enabling 32-bit ARGB GLX visuals.
-
Same here...
dcerouter_64249:/tftpboot# grep 'ARGB GLX visuals' /var/log/Xorg.0.log
(**) NVIDIA(0): Enabling 32-bit ARGB GLX visuals.
-
Actually the Nvidia drivers will always display that message if you attempt to enable compositing. The error messages, if any, would be below it.
Other possibilities are enabling options that your video card doesn't support. What is your video card and what options are enabled in the video card device section of xorg.conf? Also, in the previous log mentioned, what does it say about AGP (is it using apgart or the internal nvapg)? Sometimes switching those improves things greatly. What kind of FPS do you get in glxgears? That may not be an official benchmark, but it usually gives you a clue as to if something is wrong with OpenGL.
In my experience, the older your Nvidia video card the more problems you will find with the updated drivers. If you have at least a 7x series you really shouldn't have any issues with video on 0710. The 6x series is supposed to be supported... but I've had tons of issues with them in the past using updated drivers. If you have an 8x series... you shouldn't have any problem at all... they just work and damn well... In short Nvidia wants you to buy the new hardware so they support the old stuff less and less.
-
There are no errors in the log below that line.
I strongly doubt the problem is really in the display drivers as holding F6 or F8 on the keyboard instead does work properly.
-
I would have to agree, I didn't realize that F6 and F8 worked for you. With my problem they exhibited the same symptom.
Once I can get to replacing that one HD in my RAID I can test on my systems, but that's a bit of a chore and my real job has got me working overtime lately. I honestly haven't done this before... I usually use LVM for such things, but Ubuntu doesn't use that by default so this RAID was creating using LVM. I'm going to have to do some research on the Ubuntu way to replacing a bad HD in a RAID array. I'm sure it's not incredibly difficult, it's just something I have to research and very carefully do (I'm always extra careful when it comes to my data).
But I digress... does this happen on all MD's, or is it different based on the hardware it's running on? This really does seem like an OpenGL issue, when dealing with the cursor. I remember, back in the day, I had to deal with such bugs with things blinking as the cursor moves... although I was using MS crap... still the same concept though. Basically the cursor move updated the image before, after, and as the image was "flipping" into view. In other words two things where trying to draw in the same location at the same time.
-
Hi Dopey,
have look at http://www.gagme.com/greg/linux/raid-lvm.php#failure (http://www.gagme.com/greg/linux/raid-lvm.php#failure) if you use mdadm. For pure LVM, check http://tldp.org/HOWTO/LVM-HOWTO/removeadisk.html (http://tldp.org/HOWTO/LVM-HOWTO/removeadisk.html)
I have not tried the gyration on another MD, will try. To me this looks like the gyration is not transmitting continuously or, if it works for you, like the driver of the giration transmits the info in bursts instead of a continuous flow, which appears like the button is pressed multiple times and not maintained pressed. I am not sure if there are options to the gyration driver, will investigate.
Sam
-
I now have this problem with the fiire remote in RC2 - absolute scrolling doesn't work.
If I hold the media key and scroll left / right the media just fastforwards / rewinds just the same as pressing the media key once.
I'm sure it worked in 0704 when I tested it.
I am using the current beta nVidia graphics driver, but not seeing any GUI flickering etc, so dont think it's that! I'm gonna install the latest stable driver anyway to check.
Did anyone resolve this with the Gyro Mouse?
-
I also see this problem with 0710 and would love to hear if there is a fix! I am using the nvidia driver and UI2 with overlay. Thanks.