Forum Replies Created
- karlossParticipant03/07/2014 at 13:02Post count: 177karlossParticipant03/06/2014 at 23:00Post count: 177karlossParticipant03/06/2014 at 10:23Post count: 177karlossParticipant03/06/2014 at 10:14Post count: 177karlossParticipant03/05/2014 at 12:53Post count: 177
ok, i’ll have a look tonight for you mate.karlossParticipant03/05/2014 at 00:30Post count: 177karlossParticipant03/04/2014 at 22:25Post count: 177
It should be easy, make a new folder in ROMs, open the es_systems file and copy the bottom entry and modify for your folder you created..
Then if you take the COMMAND line from Duke and put it in an sh file in the folder you created, it should work..like I said I will try and let u know, or you can try and let me know how it went :)
Sent from my Nexus 5 using TapatalkkarlossParticipant03/04/2014 at 22:23Post count: 177
I think I know what to do, I will write you a guide tomorrow if I’m right mate.
Sent from my Nexus 5 using TapatalkkarlossParticipant03/04/2014 at 22:21Post count: 177karlossParticipant03/04/2014 at 22:19Post count: 177karlossParticipant03/04/2014 at 22:18Post count: 177
That’s cool mate, I love it as well..
Sent from my Nexus 5 using TapatalkkarlossParticipant03/04/2014 at 22:14Post count: 177karlossParticipant03/04/2014 at 11:01Post count: 177karlossParticipant03/04/2014 at 07:56Post count: 177karlossParticipant03/04/2014 at 07:56Post count: 177karlossParticipant03/04/2014 at 07:55Post count: 177
I do something similar, but run the entire os from the USB, would that be something you would be interest in as I can post you the steps?
Sent from my Nexus 5 using TapatalkkarlossParticipant03/02/2014 at 23:22Post count: 177karlossParticipant02/28/2014 at 20:34Post count: 177karlossParticipant02/27/2014 at 10:12Post count: 177karlossParticipant02/26/2014 at 16:54Post count: 177karlossParticipant02/20/2014 at 07:57Post count: 177karlossParticipant02/20/2014 at 07:56Post count: 177
I seem to have made some progress, though I don’t know why I need to do it, and I run into another issue..
I used to be able to burn the 1.9.1 image plug in pads and they work fine, but this doesn’t seem the case..
But if I use the rpi-update and update the pi kernel, on reboot the pads start working again, the only problem is, none of the emulators work, they all complain about eeprom error (picodrive) and not being able to read config file (snescore)
I rebuilt the system with a source install last night, and thought the pads still work, none of the emulators started working.
do you have any idea, why i would now need to do this for the pads to work? and if there is a way i can do it without having to update and stuff? as that doesn’t seem to be working right for me..
karlkarlossParticipant02/18/2014 at 09:53Post count: 177
well, last night I tried using a different usb hub, and that made no difference at all, so it wasn’t the hub..
I just can’t work it out, I installed debian into a virtual machine and plugged the gamepads in, and they both worked fine, so they are not at fault.
is there anyway for me to force the joy0/1? what infuriates me the most is the fact everything was working one night, went to play the next day, and nothing works, and no matter what i try, they do not work on the pi any-more, i have even tried a different pi, and like i said, re-imaged the sdcard, but no change..i have always used these gamepads and never had a single issue with them before..i guess if no one has any idea i will have to give up and scrap the table..karlossParticipant02/17/2014 at 10:58Post count: 177
Could it be that my hub’s power isn’t working right, and though the device is being picked up on the pi, it is not being registered properly? i’m completly stumped at why this has as stopped working…
but it might answer why I get the same via the usb on pi and my hub?…i need my system to work again.. :(karlossParticipant02/16/2014 at 20:36Post count: 177
I have no idea why, but neither of my gamepads are now working or listed…they were listed and working fine last night, when i do lsusb i get
Bus 001 Device 002: ID 0424:9512 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.
Bus 001 Device 004: ID 05dc:a815 Lexar Media, Inc.
Bus 001 Device 005: ID 1a40:0101 Terminus Technology Inc. 4-Port HUB
Bus 001 Device 006: ID 0d8c:000e C-Media Electronics, Inc. Audio Adapter (Planet UP-100, Genius G-Talk)
Bus 001 Device 007: ID 0079:0006 DragonRise Inc. Generic USB Joystick
Bus 001 Device 008: ID 0079:0006 DragonRise Inc. Generic USB Joystick
and when I do ls /dev/input
pi@raspberrypi ~ $ ls /dev/input
So something has gone wrong, it seems strange that even reburing the sd-card hasn’t sorted it?
any ideas? I only managed about 4 days of my table act finished and now the controllers have stopped :(karlossParticipant02/16/2014 at 19:42Post count: 177karlossParticipant02/16/2014 at 19:08Post count: 177karlossParticipant02/14/2014 at 13:26Post count: 177karlossParticipant02/13/2014 at 11:04Post count: 177karlossParticipant02/13/2014 at 11:04Post count: 177karlossParticipant02/12/2014 at 17:55Post count: 177karlossParticipant02/12/2014 at 11:44Post count: 177karlossParticipant02/11/2014 at 15:26Post count: 177
Did anyone ever do this? when I reported this, I was running the 1.6 SD Image, and all was fine.
I have now rebuilt (finally got some time on table) and am using the 1.9.1 image, but the sound has lots of interference, and it was perfect before, petrock, has anything changed that could have caused this?
KarlkarlossParticipant10/29/2013 at 10:12Post count: 177
I use these, i think they are great..