Cant get raspberry pi to work

Need help? Ask here and someone will help
Post Reply
steel_3d
Posts: 9
Joined: Sun Jul 17, 2016 3:56 am

Cant get raspberry pi to work

Post by steel_3d »

My setup works fine with gimx on pc with diy adapter. PS4 recognizes my G27 and everything's fine.

However, I can't get the rpi 3 to work. I'm quite sure everything is set up and connected correctly. But gimx just hangs after some error messages.

Shell log below:

----------

## Only the wheel and ds4 plugged in, no diy adapter:

pi@raspberrypi:~ $ /usr/bin/gimx -p /dev/ttyUSB0 -c /home/pi/LogitechG27_G29.xml --nograb
controller #1: option -p with value `/dev/ttyUSB0'
now reading arguments for controller #2
global option -c with value `/home/pi/LogitechG27_G29.xml'
grab flag is unset
native mode is already enabled for HID device 01:01:03 (PID=c29b)
src/linux/async.c:94 open failed with error: No such file or directory
Check the wiring (maybe you swapped Rx and Tx?).
No controller detected.
adapter_detect failed

##Plugged in diy adapter as well:

pi@raspberrypi:~ $ ps cax | grep gimx
pi@raspberrypi:~ $ /usr/bin/gimx -p /dev/ttyUSB0 -c /home/pi/LogitechG27_G29.xml --nograb
controller #1: option -p with value `/dev/ttyUSB0'
now reading arguments for controller #2
global option -c with value `/home/pi/LogitechG27_G29.xml'
grab flag is unset
native mode is already enabled for HID device 01:01:03 (PID=c29b)
Detected USB adapter: G29 PS4.
using default refresh period: 5.00ms

Message from syslogd@raspberrypi at Jul 17 04:16:09 ...
kernel:[ 678.306291] Internal error: Oops - BUG: 0 [#1] SMP ARM

Message from syslogd@raspberrypi at Jul 17 04:16:09 ...
kernel:[ 678.306560] Process gimx (pid: 1958, stack limit = 0xb8898210)

Message from syslogd@raspberrypi at Jul 17 04:16:09 ...
kernel:[ 678.306571] Stack: (0xb8899cc8 to 0xb889a000)

Message from syslogd@raspberrypi at Jul 17 04:16:09 ...
kernel:[ 678.306586] 9cc0: 00000000 b686cc44 b9aa5450 b9aa5448 b9aa5000 80860100

Message from syslogd@raspberrypi at Jul 17 04:16:09 ...
kernel:[ 678.306603] 9ce0: 20000013 00000000 b8899d1c b8899cf8 80498bf8 80082488 00001000 b90a1000

Message from syslogd@raspberrypi at Jul 17 04:16:09 ...
kernel:[ 678.306619] 9d00: b686cc04 00000000 b9aa4000 b9aa544c b8899d44 b8899d20 80498d18 80498b64

Message from syslogd@raspberrypi at Jul 17 04:16:09 ...
kernel:[ 678.306636] 9d20: 80498c70 b91e2000 b686cc04 b91e2190 00000000 b1a3b000 b8899d54 b8899d48

Message from syslogd@raspberrypi at Jul 17 04:16:09 ...
kernel:[ 678.306652] 9d40: 80490f90 80498c7c b8899d7c b8899d58 8044d078 80490f78 00000001 b686cc00

Message from syslogd@raspberrypi at Jul 17 04:16:09 ...
kernel:[ 678.306669] 9d60: b8abd720 b1b0c300 b686cdd0 b1a3b000 b8899dac b8899d80 7f2da364 8044d000

Message from syslogd@raspberrypi at Jul 17 04:16:09 ...
kernel:[ 678.306685] 9d80: 7f2da220 7f2db3b4 80954b10 b686cdd0 b8abd720 b1b0c300 00000000 b8899f5c

Message from syslogd@raspberrypi at Jul 17 04:16:09 ...
kernel:[ 678.306702] 9da0: b8899ddc b8899db0 8015baf8 7f2da22c 00000000 b8abd720 b1b0c300 b1b0c308

Message from syslogd@raspberrypi at Jul 17 04:16:09 ...
kernel:[ 678.306718] 9dc0: 8015ba18 b8abd720 00000000 00000000 b8899e04 b8899de0 801553a0 8015ba24

Message from syslogd@raspberrypi at Jul 17 04:16:09 ...
kernel:[ 678.306735] 9de0: b1b0c300 b1b0c308 b1bbbe80 b8899eb0 00000000 00000000 b8899e24 b8899e08

Message from syslogd@raspberrypi at Jul 17 04:16:09 ...
kernel:[ 678.306751] 9e00: 801565c0 801551c4 b1954500 00000000 00000800 b95d1110 b8899eac b8899e28

Message from syslogd@raspberrypi at Jul 17 04:16:09 ...
kernel:[ 678.306768] 9e20: 80164c28 8015655c 00000000 00000000 584d4947 35393120 00302038 00000000

Message from syslogd@raspberrypi at Jul 17 04:16:09 ...
kernel:[ 678.306784] 9e40: 00000000 00000000 fffffdfa b8898000 00000000 b1b0c300 00000000 00000024

Message from syslogd@raspberrypi at Jul 17 04:16:09 ...
kernel:[ 678.306800] 9e60: 00000041 00000000 00000000 00000000 00000004 b8abd720 b91cb910 b9692220

Message from syslogd@raspberrypi at Jul 17 04:16:09 ...
kernel:[ 678.306817] 9e80: 00000001 00000014 b8899f5c b8899eb0 00000001 8000fd08 b8898000 00000000

Message from syslogd@raspberrypi at Jul 17 04:16:09 ...
kernel:[ 678.306833] 9ea0: b8899f4c b8899eb0 80166940 80164724 b91cb910 b9692220 e1915a01 00000006

Message from syslogd@raspberrypi at Jul 17 04:16:09 ...
kernel:[ 678.306850] 9ec0: ae53001b 801747a8 00000000 b95e1c38 b8abd720 00000101 00000004 000004ce

Message from syslogd@raspberrypi at Jul 17 04:16:09 ...
kernel:[ 678.306866] 9ee0: 00000000 00000000 00000000 b8899ef0 00000000 00010000 00000800 00000100

Message from syslogd@raspberrypi at Jul 17 04:16:09 ...
kernel:[ 678.306882] 9f00: b8899f3c b8899f10 801747a8 80173f20 00000800 00000800 ffffff9c ae530000

Message from syslogd@raspberrypi at Jul 17 04:16:09 ...
kernel:[ 678.306899] 9f20: ae530000 00000000 00000002 ffffff9c 00000014 ffffff9c ae530000 00000005

Message from syslogd@raspberrypi at Jul 17 04:16:09 ...
kernel:[ 678.306915] 9f40: b8899f94 b8899f50 80156918 801668dc b8899f6c b8899f60 80158d9c 00000800

Message from syslogd@raspberrypi at Jul 17 04:16:09 ...
kernel:[ 678.306931] 9f60: b8890000 00000024 00000100 00000001 00000000 00000001 0024bfa8 00000005

Message from syslogd@raspberrypi at Jul 17 04:16:09 ...
kernel:[ 678.306948] 9f80: 8000fd08 b8898000 b8899fa4 b8899f98 80156a08 8015680c 00000000 b8899fa8

Message from syslogd@raspberrypi at Jul 17 04:16:09 ...
kernel:[ 678.306970] 9fa0: 8000fb40 801569e8 00000000 00000001 7efb2534 00000800 7fffffee 7efb2545

Message from syslogd@raspberrypi at Jul 17 04:16:09 ...
kernel:[ 678.306987] 9fc0: 00000000 00000001 0024bfa8 00000005 00000020 000329c8 76f77000 00000000

Message from syslogd@raspberrypi at Jul 17 04:16:09 ...
kernel:[ 678.307003] 9fe0: 00000000 7efb2520 76aedea4 76ad14a4 80000010 7efb2534 00000000 00000000

Message from syslogd@raspberrypi at Jul 17 04:16:09 ...
kernel:[ 678.307333] Code: e1a0100e e1a00004 ebfffeea eaffff8d (e7f001f2)

## It hangs here.

## Looking at the running processes in a new shell, I get:

pi@raspberrypi:~ $ ps cax | grep gimx
1958 pts/0 Zl+ 0:00 gimx <defunct>
pi@raspberrypi:~ $ sudo kill -9 1958
pi@raspberrypi:~ $ ps cax | grep gimx
pi@raspberrypi:~ $ ps cax | grep gimx

## Killed the process above, then started gimx again in the other shell:

...

Message from syslogd@raspberrypi at Jul 17 04:16:09 ...
kernel:[ 678.307333] Code: e1a0100e e1a00004 ebfffeea eaffff8d (e7f001f2)

Killed
pi@raspberrypi:~ $ /usr/bin/gimx -p /dev/ttyUSB0 -c /home/pi/LogitechG27_G29.xml --nograb
controller #1: option -p with value `/dev/ttyUSB0'
now reading arguments for controller #2
global option -c with value `/home/pi/LogitechG27_G29.xml'
grab flag is unset
native mode is already enabled for HID device 01:01:03 (PID=c29b)
Detected USB adapter: G29 PS4.
using default refresh period: 5.00ms

## This time it hangs without any error, but the PS4 still doesn't see the wheel.
## Checking the process from the other shell:

pi@raspberrypi:~ $ ps cax | grep gimx
2031 pts/0 Sl+ 0:00 gimx

-----------

Any ideas? I appreciate you help!

Steve
steel_3d
Posts: 9
Joined: Sun Jul 17, 2016 3:56 am

Re: Cant get raspberry pi to work

Post by steel_3d »

All that time wasted, and apparently I just needed to update raspbian! Even though I have a few month old raspbian image. WTF??
For future reference to others, don't skip these steps when setting up your OS!

sudo apt-get update && sudo apt-get upgrade
sudo apt-get install rpi-update
sudo rpi-update
sudo reboot

Problem solved.

It would be nice if the wiki called out the update as a necessary step rather than optional.
Post Reply