Problem with Gimx
Problem with Gimx
Hi, I have a problem with gimx. I have two computers on the gimx amd processor running at all times with no lag, and the other (laptop) with Intel gimx works up to 5 minutes, then jams and nothing is happening, I have to turn it on again. How can I work on a laptop? I installed ubuntu 12.04. The same version as on the other computer. Sorry, google translator.
Re: Problem with Gimx
What are the kernel & bluez version on all computers?
You can get them with the following commands:
You can get them with the following commands:
Code: Select all
uname -a
bluetoothd --version
GIMX creator
Re: Problem with Gimx
I am having this problem too, but i'm on Ubuntu 11.10, 3.0.0-32-generic, Bluez 4.96. GIMX compiled from the source.
I tried to install older packages of bluez but didn't solve.
After a while playing GIMX freezes e keep repeating the action you were performing. The dongle is still connected, if the terminal option is checked there is input reception but no transmission.
I tried to install older packages of bluez but didn't solve.
After a while playing GIMX freezes e keep repeating the action you were performing. The dongle is still connected, if the terminal option is checked there is input reception but no transmission.
Re: Problem with Gimx
The GIMX disconnects after 2 ~ 3 minutes after the freezing. (Please reconnect the controller message).
ps: Even if i close GIMX, it only shows the disconnect message after the 2 or 3 minutes.
I got the same freezing issue on Ubuntu 12.04.
My crashes with set flush timeout to 16 too. I tryied to undo the issue 170 changes, (i saw there was same flush timeout modification on the code) but it didn't work.
GIMX 0.51 works fine, so i think it's not my bt dongle.
I'm in a notebook too, i disabled my touchpad.
ps: Even if i close GIMX, it only shows the disconnect message after the 2 or 3 minutes.
I got the same freezing issue on Ubuntu 12.04.
My crashes with set flush timeout to 16 too. I tryied to undo the issue 170 changes, (i saw there was same flush timeout modification on the code) but it didn't work.
GIMX 0.51 works fine, so i think it's not my bt dongle.
I'm in a notebook too, i disabled my touchpad.
Last edited by EduardoP on Tue Jun 11, 2013 4:14 pm, edited 1 time in total.
Re: Problem with Gimx
I'm using GIMX from the source, and in this tutorial :
http://gimx.fr/wiki/index.php?title=Dev ... t_on_Linux
There is a step, that resulted in permission denied. With "sudo -i" i managed to create the rules but there was one line that resulted in a non exitent directory:
Is there something related? But i can compile and actually play without this step for 1 ~ 2 minutes.
http://gimx.fr/wiki/index.php?title=Dev ... t_on_Linux
There is a step, that resulted in permission denied. With "sudo -i" i managed to create the rules but there was one line that resulted in a non exitent directory:
Code: Select all
Set Input Device Permissions (required since r1277)
One way to give read permissions to GIMX is to create a special group, change /dev/input/event* group ownership to that group, and then make the gimx binaries setgid to that group.
chgrp input /dev/input/event* /dev/input/js*
Re: Problem with Gimx
No, there's nothing wrong, I guess there's no joystick connected to your PC.
GIMX creator
Re: Problem with Gimx
Hey i got it!!
I got GIMX from the source but didn't installed it yet, got and replaced the old files codes related to Flush timeout changes on issue 170. Like:
http://code.google.com/p/diyps3controll ... 2cap_con.c
http://code.google.com/p/diyps3controll ... 2cap_con.h
Then i installed GIMX, and it worked.
My bt dongle doesn't support a forced flush timeout, i don't know why, it crashes after a while.
I got GIMX from the source but didn't installed it yet, got and replaced the old files codes related to Flush timeout changes on issue 170. Like:
http://code.google.com/p/diyps3controll ... 2cap_con.c
http://code.google.com/p/diyps3controll ... 2cap_con.h
Then i installed GIMX, and it worked.
My bt dongle doesn't support a forced flush timeout, i don't know why, it crashes after a while.