sub=usb ?

Your pi is probably not getting enough power. Did you read the posts above ?

Which Pi?

Do you have a small rainbow box at the top right of the screen ?

Which snes emulator? (as an example).

I’ve also got issues with the Mad Catz SFIV Arcade Stick (identified as MadCatz PC USB Wired Stick 8818 by jstest). If I connect it to my Ubuntu 14.04 desktop and use jstest, all buttons work fine. When I connect it to my raspberry pi 2 with either raspbian wheezy or retropie 3.1, none of the buttons react in jstest. It is detected fine, and /dev/input/js0 is available, but none of the buttons work. Anybody got an idea what is wrong?

fightclub-

I think I have the same issue as yourself, when I run the lsusb command I find my product ID to be 0314:0326. There is no listed name next to it. I try and update the cmmndline.txt file with the product ID, but with no success. How did you phrase it exactly? I’ve tried adding the text to end of the first line, and on it’s own line. Ive attempted with “usbhid.quirks=0314:0326:0x040” and “usbhid.quirks=3014:0326”

Any thoughts? Programming NOOB, so apologies if this is blatantly dumb and obvious

I have a Raspberry Pi 2 B+ with RetroPie v3.0, trying to setup a 2 player joystick with a USB interface PCB kit off Amazon. “RA-PC-2-2-JAMMA-USB” is listed as a detail on the amazon website

What you do to can use autosave/autoload from usb?? I dont know what you do!? thanks & sorry for bad english ;)

EDIT:
Problem Solved!!
I solved the autosave/soad problem when I take the permisions for all users I edit the information of fstab (etc/fstab) using this:
UUID=1ADF-0D47 /mnt/usb1 vfat auto,users,rw,uid=pi,gid=pi 0 0
Myflash drive Mount Point Format Permisions for all users ((This I dont know really))

And now I can save & load when I like Thanks for the forum!!!

I have been experiencing issues with my PS3 style wired controllers. I have a Logitech F310 and a Nyko PS3 Core Controller. What I have experienced in Retropie 3.0 and 3.1 is that I am able to configure the controllers all except the R2 (trigger). I have found a way around this by going back into the config and setting this up manually. What I continue to have issues with now since upgrading to 3.1 is when in a game some buttons are totally unresponsive in some menu’s. Example, FF9 when running around world map everything works completely normal. Enter a zone and Triangle stops responding and other buttons done work. Previously in 3.0 this all worked but my menu’s would randomly keep jumping and changing as if a button was being pressed when it actually wasnt. I have tried PS3 drivers, and xbox drivers with no luck. I had to go back to my Logitech Precision game pad without analog sticks to be able to play any games. This seems more like driver issues as using the basic controller without analog sticks this works perfect!

Side note, I have done the Sudo Raspi-update
Added USB Power to the script
Changed GPU Mem higher and lower
Tried PS3/XBox Drivers
Tried multiple USB Ports
Ran auto config of controller and manual config

Anyone have any suggestions or ideas?

Thanks!

looks like i needed to update the cmdline.txt line with my product id that i got from lsusb.

i guess my xin-mo isnt the same as everyone elses. it does work now though.

also, you may want to specify to append that line vice creating a new line. if you create a new line, its not recognized.

[quote=107584]Try with this:

https://www.petrockblock.com/forums/topic/2-x-joystick-config/#post-106658

It’s better that changing Kernel.

[/quote]
efraimsangil,

i added the line to my cmdline.txt file. unfortunately, i dont see anything in /dev/input other than ‘mice’ and my xinmo is connected. is 0x16c0:0x05e1:0x040 the same for all xin-mo’s? when i run lsusb, i get Bus 001 Device 005: ID 0314:0326. ive tried 0x0314:0x0326:0x040 and that isnt recognized either.

i am running the newest retropie image with a full apt-get upgrade and thats it. no modified kernel.

any help?

I actually found that I was getting low power warnings from my Pi with the standard 2A supply and four USB controllers connected and ended up sourcing a 3.5A supply which really helped things out and seemed to supply enough power for the unit. In saying that I’m also relaying the connection through a few wires and a switch so it might not be all that’s going on here ;)

runs from usb

you can use a normal Pi sower supply (altho you may need to buy a Y cable via eBay) for the following..

via command line..

sudo nano /boot/config.txt

then right at the bottom add this…

max_usb_current=1

then press ctrl+x then Y then enter to save your edit

then restart you pi

1.: https://www.raspberrypi.org/forums/viewtopic.php?t=19900&p=450651

2.: switch the usb port or swap hands?

EDIT: Nevermind, found what I needed to change in the “ss” folder within the OpenElec root partition. This is now running off USB for me.

I got it going, well almost!
The one thing that is preventing this from working in the autoboot.txt on the recovery partition.

Initially it read: “boot_partition=7″

So I changed it to:”boot_partition=6”

(I moved the original partition to usb and deleted the original off the SD so now partition 7 is 6).

What happens now is that RetroPie boots fine. It can load OpenElec fine, but once you have loaded OpenElec and try to boot into RetroPie, your script alters autoboot.txt back to “boot_partition=7” thus locking the boot sequence onto OpenElec.

All I need to know now is where is the script and what line do I need to alter and I should be set, after which I will try to create two small image files and upload so there is an easy to install USB version if this.

I’m going to PM you in case you don’t see this for a few days… I’m eager if you can’t tell! ;)

Here’s my latest discoveries.
I created a back up of my USB stick using Win32DiskImager:

http://sourceforge.net/projects/win32diskimager/

For what ever reason, DD was fine when creating a bootable USB stick out of my pre-made SD image(s), but was not suitable to use making a back up of my USB stick to my new larger USB drive.

Anyhow, the Win32DiskImager backup worked perfectly! Now I am using Gparted to expand the Raspian and RetroPie partition, while moving OpenElec’s to the end. I’ll know if that worked here in a about an hour. “Note to self, purchase or steal super computer.”

“EDIT: Resize with Gparted works!!!! This method requires two Operating Systems, but it does indeed work until I or someone can figure out how to do the backup images and cloning with DD or Clonezilla if anything.”

I did notice that the image files can be compressed pretty well, assuming the partitions are not actually full such as the RetroPie image. Also, using the Img back up method, I realize it would be best to use as small as USB stick as possible to make your initial set up, create an image from that and the new SD (you can back up your large SD and move only the files you need to a smaller one), which will then greatly reduce the size of your image back ups and reduce the time spent creating your back ups. Now assuming it is possible to resize the new partitions created from the backup images, then once I or someone else figures out how to get your Dual Boot kit hosted on USB, a simple Win32DiskImager image could be uploaded and easily used.

Here is the hard drive I’m using… cheap compared to SD hugh? :)

http://www.ebay.com/itm/151745910857?_trksid=p2057872.m2749.l2649&ssPageName=STRK%3AMEBIDX%3AIT

[quote=104757]Hi!

You need to change the Linux kernel to use 2 joysticks using XinMo USB controller.

Try it!

Custom Kernel for Xinmo
https://www.dropbox.com/s/f610y6q91mfv9zb/custom_kernel_1.20150317-1.tar.gz?dl=0

[/quote]

Can you repost the kernel? its gone from dropbox. thanks!

They claim there is a speed boost, though most of those guys are saying this when using a USB 3 stick which I don’t own. Plus this does not make sense because the Pi only has USB 2.
That being said, it is faster than some SD cards, but the only speed boost I noticed was maybe a slightly quicker boot time, and some PSX games played less choppy or had the chop removed from them all together, I.E. Quake 2 when you open the first door to a large colorful room with an enemy in it. On the SD it struggles for a second, on the USB not at all.
Also this spares your large and fast SD and allows you to use your old slow and small SD since it is only required to boot.

Those small issues aside, yes, the SD cards can not handle as many read writes and will in the end fail long before a USB stick will. Also when ever you over clock your Pi (which I believe we all do for those emulation speeds), this still puts the SD card at risk. The risk is not as great as it was with the Pi 1, but it is still there.

I was able to boot off my other USB stick using the triple boot guide I posted in your other thread, but was not able to convert your work over either, at least not the dual boot image as it’s the one I’m most interested in running at this point as I don’t find Raspbian to be very practical.

So here is where I want to go:

A: Stick with your Dual Boot kit and use a USB to store my roms, saves, art and such. I just need to know how.

B: Go back and make my own Dual Boot from USB, and figure out a way to load up your boot screen on mine. I REALLY WANT THAT THING MAN!!!! :)

EDIT: C: I forgot your reboot scripts, I want to know how you do that also, then I’ll figure out custom themes last.

RetroPie installed and booting from USB?
byu/tonyt3rry inRetroPie