Homepage Forums Search Search Results for 'usb'

Viewing 35 results - 71 through 105 (of 3,655 total)
  • Author
    Search Results
  • #121709
    nonorius
    Participant

    Hello,
    yes it seems better with keyboard only…but not playable.
    now is it due to ps3 or bluetooth?
    As I have the issue on pi2, I would say to the ps3 pad but not sure…
    I am trying to understand how to play with the ps3 pad without bluetooth beign just usb wired.
    Thanks anyway !

    #121701
    sabrecheeky
    Participant

    Yes, I’m using a PS3 controller over Bluetooth. It could be that, perhaps a clash with the inbuilt bluetooth on the Pi3 (I still use a usb Bluetooth receiver).

    #121680

    In reply to: Dreamcast

    Anonymous
    Inactive

    If I remap the Controller via EmulationStation, then it is also remapped for Reicast, but then only the analogue stick of one controller is working and I’m stuck at date settings and so I have to remap the Reicast controls manually again.

    The device ID’s in emu.cfg match my controllers.
    First one is the USB Keyboard, second one is the first X360 wireless controller and the following three are the theoretically three another X360 controllers. So the device ID’s of my two X360 wireless controllers are 2 and 3 and if I use the script, provided here:
    https://github.com/reicast/reicast-emulator/blob/3ed2985d510733062e295f8d343cc717f158b4c7/shell/linux/tools/reicast-joyconfig.py

    then both controllers are working with ID 2 and 3, but it shows no effect in Reicast and still only one Controller is working.

    As I wrote in my last post, I tried to give ID 3 another mapping file (with the same values as for controller 1), but this also does not work, so I’m confused and wonder, if anybody has got two working USB Controllers with the latest Reicast release.
    If so – please tell me and explain how :-)

    IMHO it could be a USB / USB device ID problem of the Reicast emulator itself.

    #121678
    sabrecheeky
    Participant

    I am having similar issues, but mine is freezing within seconds mainly on PSP (both lr-PPSSPP and PPSSPP) and PS1 games on my new Pi3.

    I had a nice set on my Pi2; NOOBS launcher with Ubuntu MATE, OpenELEC and RetroPie – a 10A 6 port (2.4A per port) USB power supply powering the Pi, Ethernet to Wifi adapter and 2.5in 500GB HDD. RetroPie (3.2 iirc) run great on that. All the games ran from the SD card, except the PSP and PS1 games from the HDD (all my own homemade rips which work great on the Pi2 and other machines).

    I have tried to copy this set up on my new Pi3. Ubuntu runs like a dream, and OpenELEC similarly flawlessly, but this RetroPie issue has me stumped. I thought it might be the power supply so I bought an official (looking!) 2.5A supply – no fix. I changed over to an independently powered 3.5in HDD (3TB, one partition formatted to ext4 and mounted in fstab), still no luck. Tried a adding a heatsink too, no joy.

    Reading other posts, perhaps there is a fair bit of variation in quality in the manufacturing of Pi3’s. I tried overloading (no overclocking, don’t do overclocking!) my Pi3 in Ubuntu to see if I could get it to freeze. I run all four cores at 100% (using ‘stress’) for half an hour with no ill effects, except a quite hot heat sink ><.

    I’m not very technical, so any thoughts or ideas on where I’m going wrong would be greatly appreciated ^^

    #121671
    nonorius
    Participant

    I tried with max_usb_current=1
    same behaviour…
    It seems to happen more frequently with snes.

    #121666
    InsecureSpike
    Participant

    could try this

    sudo nano /boot/config.txt

    right at the bottom add

    max_usb_current=1

    #121649
    lechuder
    Participant

    I have the same problem. My rpi3 with retropie 3.6 and bluetooth inside doesnt see my wireless xbox controller. I’ve been installed bluetooh driver but it ‘s see only bluetooth of tv. I don’t know what to do. Can I connected my xbox wireless controller with rpi3 by builted bluetooth inside or I must buy a wireless Receiver usb to connected?

    jope
    Participant

    I would like to know if there is any good tutorials for wireless DualShock4 controller (I have a bt dongle and running retropie 3.6) or do I just use it with the usb cord.

    nonorius
    Participant

    Hello all,

    I am a bit desperate as I do not find any solution to my problem: after few minutes of game(2 to 20 minutes) my Raspberry is freezing (screen + ssh blocked : has to stop by unpluging the powe supply).
    I tried almost everything I think:
    => change power supply (current : 3A)
    => change sd card (sandisk class 10 8 & 64 gb)
    => re-install several times Retropie 3.6 on my different cards
    => switch network from ethernet to wifi and vice & versa
    => it’s occuring on both my Raspberry pi 2 & 3 but more frequently on raspberry 3 it seems. mybe more playing supernes and megadrive (not sure)
    => I tried to put roms only on a usb key

    Now to me it remains:
    => maybe configuration of the hdmi (where?)
    => bluetooth issue? I am using a ps3 pad via bluetooth.

    In conclusion my two raspberry are not usable…
    Do you know this issue?

    Thanks in advance for your help!

    #121628
    marcwallace
    Participant

    Hi,

    Firstly, thanks for replying! I’ve tried to go into wifi config in Retro pie and unfortunately no networks are displayed, there should be over 10 e.g. neighbours etc.

    trying sudo ifconfig wlan0 up just gives me error while getting interface flags: no such device.

    In the pi I have plugged in a usb keyboard, it’s also hooked up to a joystick setup that me and a mate have built and a usb gamepad. I had no wi fi before plugging in the custom joystick setup and the gamepad / keyboard were plugged in then. There’s no hub plugged in, I do have a 2.1 setup plugged into the headphone socket.

    Ifconfig only shows eth01 and lo.

    #121621
    meneerjansen
    Participant

    What you might try:

    In Emulationstation/RetroPie go to: Retropie (i.e. the setup menu) –> Configure WiWi –> choose ‘Connect to WiFi network’

    You’ve probably done that already and apparently it won’t work. Unfortunately for you is that this dialog screen already does “every Linux trick” in the book to connect.

    Since successfully connecting to your beloved Pi the first time: did you change something w/ regard to hardware? Like connecting other USB devices? An USB hub? In my experience WiFi can eat a lot of power and due to extra hardware your Pi might be under powered now.

    P.S. The way I force my Pi to connect to WiFi is:

    sudo ifconfig wlan0 up
    And then wait a minute.

    Check IP address and if your connection is up w/:

    ifconfig
    Good luck! :)

    P.S. Thanks to Buzz I corrected the typo in wlan0.

    #121613
    charco
    Participant

    Great advice, thanks guys! I hadn’t thought of a USB pen drive as I thought roms couldn’t be loaded off them. Maybe there were issues with an older version of RetroPie that have since been resolved.

    With the Pi 3 having wifi and bluetooth that frees up USB ports too. I’ll look into a new high capacity pen drive so :)

    #121599
    shoothere
    Participant

    I would second InsecureSpike’s advice. Also if an update goes boink you don’t have to copy all the roms/saves/scrapes again, just a new SD card and go go go!

    It is much cheaper as well and USB sticks are not very big so size shouldn’t be a problem either.

    #121598
    InsecureSpike
    Participant

    i’d suggest a smaller gb sd card say 4gb – 8gb (x2) then get your self a 128gb usb drive, as using such a large sd card could run into issues if corrupted, then all your roms will be lost,
    with a usb drive you can keep all the retropie system bits on the sd card and have your roms on the usb drive, separate & safe

    these are what i use, the SD cards seem to take lots of rewriting too,

    4gb Kingston SD card

    http://www.ebay.co.uk/itm/221391598329?_trksid=p2055119.m1438.l2649&ssPageName=STRK%3AMEBIDX%3AIT

    128gb Kingston USB drive

    http://www.ebay.co.uk/itm/371052738512?_trksid=p2055119.m1438.l2649&ssPageName=STRK%3AMEBIDX%3AIT

    pollyannaish
    Participant

    Hi! New to RetroPie but these forums have been incredibly helpful already in getting me set up & going.

    I am running RetroPie 3.6 on a Pi3.

    I was struggling to get the cheap Bluetooth off-brand PS3 controllers I bought working with my config — I actually screwed something up and had to reimage the MicroSD card, but finally got it working, with one weird glitch. For some reason, the sixad service starts up, but fails with the following errors (from /var/log/sixad):

    Can’t get device info: No such device
    No bluetooth adapters found on the system!
    sixad will now quit

    If I *then* either ssh in or quit to the terminal prompt, and enter the following:
    sudo /etc/init.d/sixad restart

    the sixad process will start up just fine, and I can pair both controllers.

    Is there some pi3 bluetooth service that needs to start up before sixad is run? How might I reorder them? (My Linux setup skills are extremely rusty :)

    Note: To get these working, I used the “Clone support Shanwan” version under the “Install/pair PS3 controllers” menu in retropie_setup.sh — otherwise the devices wouldn’t pair. This was true even though when I connected them via USB, they appeared as “Gasia” controllers. I also had to install pi-bluetooth, of course, but that seemed to work fine.

    #121577
    nathaninho
    Participant

    @meneerjansen OOOOK!!! I have connected my raspi only with the NEOGEOstick and… YEEES!!! It is detected as a keyboard, because, Emulestation only detecs my SNES YSB pad, but when I go to Retropie SETUP, I can use the NEOGEOstick for menu navigation.

    The problem is that in “Configure keyboard for use with RetroArch” menu, I press buttons, but the configuration is not changing. The joystick is the cursor, first button is “OK”, and the second one is the “CANCEL” in menus…

    Now, we have a new beginning… :)

    PS: When I execute lsusb with and without the NGstick only one line appears (when stick is connected):

    Bus 001 Device 007: ID 1292:4e47 Innomedia

    Then, something is detected…lol

    nerdythor
    Participant

    Alright… so my Pi keeps freezing/hanging whenever I’m playing a SNES game. I just installed it using BerryBoot so I could have a larger repository for ROMs.

    My setup is as follows

    Pi3->Plugable Powered USB hub-> Vertex 500GB SSD.

    Has anyone else had any issues with the newest berryboot version? If so how’d y’all fix it?

    #121555
    gamesfan
    Participant

    Step 1: Take the SD card from the RaspberryPI and put it in your PC.
    Step 2: Download Win32DiskImager, Point to your SD card and click READ. This will make a BACKUP of your SD card. You can currupt the hell out of it by shutting down incorrectly, presonaly I run my builds from USB flash drives as they are far more stable.
    Step 3: Now that you have your backup, put the car back into the Raspberry.

    Now, this is the issue with buying something (premade), we dont know if they jacked with the menus, settings etc. But I will assume they didnt.

    The first step is to see what emulator core the other systems are using, I find the libereto the easiest to configure as there is a controller menu. It SHOULD display what emulator it is using, or ask you to press any key once a game launches. If it doesnt, someone messed with the runcommand.sh.

    If you do this, see what core its using and follow the wiki to configure the controls for that core. If it is liberato by chance then we can go to the next step

    Step 4: Is there a display at the bottom when you load a game that shows what controller configuration it is using? If so, connect your Raspberry pi to your routher and SSH into it via putty or connect to its samba shares via \\RETROPIE\ from your windows explorer.

    Go into configurations and find your controller CFG files, you can edit them with a text editior. From there you can assign your buttons.

    If it is a Xarcade, it uses MAME standard confgs like 5 , 6 for coin and 1 and 2 for P1 and P2 start.

    You may find that pressing COIN 1 and (SOMEOTHER) button bring up the Retroarch config menu.. This will allow you to create \ save emulator \ game specific key remap files.

    Of course if this seems daunting, you can always upgrade to the latest version using the setup scripts.

    You can also start fresh copy the ROMS and BIOS off first through \\RETROPIE and start with a new image, configure it yourself so you understand what is going on and then put the roms back on.

    If all else fails you can always restore from your backup you made earlier.

    Does the person you bought it from provide support?

    #121552

    In reply to: Dreamcast

    dgtliqd
    Participant

    Hi vretro,

    You’re correct to assume that the device ID needs to match your controller in order to be recognized by reicast. It “usually” does a good job of identifying, but if it doesn’t, and you’re not sure what your device ID is, you need to go to the console (command line) and type: evtest | grep BTN

    you’ll get something like this returned:

    Available devices:
    /dev/input/event0: Xgaming X-Arcade
    /dev/input/event1: Xgaming X-Arcade
    /dev/input/event2: Logitech USB Receiver
    /dev/input/event3: Logitech USB Receiver
    /dev/input/event4: Xarcade-to-Gamepad Device 1
    /dev/input/event5: Xarcade-to-Gamepad Device 2
    /dev/input/event6: SNES-to-Keyboard Device

    The ‘event#’ corresponds to the device ID mapped to each of your controllers. You can then type the number of the controller you want the button mapping for and press enter, and you’ll be shown the values that correspond to each button on your controller. Hopefully this helps you get your controller set up.

    #121543
    meneerjansen
    Participant

    P.S. One last thing you might try: disconnect your keyboard and connect only the Neo Geo controller and a “real” USB controller. Reboot the Pi and operate the Pi w/ said controller. Then try to set up a keyboard again. Maybe the NeoGeo controller will be selected now…

    #121541
    meneerjansen
    Participant

    [quote=121524] @meneerjansen Thank you for your time

    The Retroarch keyboard configuration doesnt detect my AES stick, only my wireless keyboard… [/quote]
    That is very unfortunate. Then it might behave like a mouse… Any way if you’re certain that it is detected by Linux (use ‘lsusb’) then my magician’s high hat is empty now.

    I’ve seen the controller you mention on Amazon and it is pretty amazing! Pity it don’t work in Linux. Good luck in finding another controller you like. :)

    rissien73
    Participant

    Hello everyone and thanks for a great forum….. I am in need of help and have trawled forums/websites for several weeks but cant seem to find a solution. I have purchased a pi2 enabled arcade cabinet which has two joysticks and 3 buttons per player. It is running retropie 3.2 ( I think ). My problem is that the controls work fine for MAME and Fba but I am unable to use the Nintendo or Sega emulators as the keybindings are all over the place. eg on Nintendo the LH joystick works but the buttons for the game are split between player 1 and player 2 buttons, also I am unable to exit the emulator and have to power cycle the pi to quit. The controls are wired to an ipac 2 which then goes into the pi by usb. I have read soooo much I am now officially confused and would love any guidance to sort this issue out. many Thanks in advance.

    #121534

    In reply to: Dreamcast

    vretro
    Participant

    Is it possible that the secret to our issues originate with the device id’s being used within emu.cfg

    Below is how my emu.cfg looks:

    [input]
    evdev_device_id_1 = 0
    evdev_device_id_2 = 1
    evdev_device_id_3 = -1
    evdev_device_id_4 = -1
    evdev_mapping_1 = /opt/retropie/configs/dreamcast/mappings/controller_USB,2-axis8-buttongamepad.cfg
    evdev_mapping_2 = /opt/retropie/configs/dreamcast/mappings/controller_USB,2-axis8-buttongamepad.cfg
    joystick_device_id = -1

    When I did a fresh install, my controllers were not added to the mappings folder when I first launched Reicast and the default evade_device id’s were different. It seems that -1 is used to indicate “missing” controllers. I had two attached.

    I haven’t had success swapping these numbers around, yet.

    Should there be a second (third or fourth) joystick_device_id for each controller too?

    Does Reicast controllers get configured via EmulationStation like some other systems?

    #121502
    meneerjansen
    Participant

    [quote=121498]will need some[/quote]

    [quote=121498]Thank you again @meneerjansen

    I have installed the Joystick package, but i have the newest version. Then, with th jstest /dev/input/js0 command, I dont see my gamepad (when I connect the SNES USB Pad yes), but I dont have any error only the following message:

    jstest: No such file or directory

    Then, I think that I will need some driver…
    [/quote]
    The error message “No such file or directory” means that there is no “js0”, that is: there is no game controller detected. Indeed, this means that you need a driver specific for this controller. It may be already have been developed by the Linux community, it may have been released by the manufacturer of your controller. Which manufacturer is it, which type is it and what’s the support page of the manufacturer? Said Linux driver should be downloadable from there. If it’s not… Well, then I think it is marketed very much towards Windows or special (Windows) software that comes with the hardware.

    P.S. From the top post: in Windows, you (only) seem to be able to play games w/ your ‘AES stick’ from your ‘NeoGeo X Gold system’ w/ a piece of software called “Xpadder”. From the Xpadder website: “Xpadder allows you to map keyboard keys and mouse button actions to your game controller buttons”. This means that Windows does NOT recognize this controller as a game device (i.e. not as a joystick or controller) but as a keyboard. That’s a bummer. But, I can play games fairly well in Emulationstation w/ a keyboard. What you have to do to operate Emulationstation (and therefore your Pi) w/ a keyboard is:

    1. In RetroPie/Emulationstation go to: “RetroPie (the config menu) –> RetroPie setup –> Setup/configuration (to be used post install) –> Configure Retroarch controller –> Configure keyboarc for use with RetroArch”.
    2. It should pop up a wizard that asks you to press keys on your keyboard (to use instead of a controller).
    3. Then press keys on your ‘AES stick’. Realize that RetroPie probably “thinks” that your controller actually is a keyboard.

    Good luck :)

    #121498
    nathaninho
    Participant

    Thank you again @meneerjansen

    I have installed the Joystick package, but i have the newest version. Then, with th jstest /dev/input/js0 command, I dont see my gamepad (when I connect the SNES USB Pad yes), but I dont have any error only the following message:

    jstest: No such file or directory

    Then, I think that I will need some driver…

    :)

    #121477
    meneerjansen
    Participant

    [quote=121457] @meneerjansen thank you!!!

    Here, people says that Win detects the stick as a POV switch instead of a X and Y axis.

    And here there are more info, but I dont undertand very well

    http://www.neo-geo.com/forums/showthread.php?259552-Neo-Geo-X-Controller-on-Raspberry-Pi&highlight=Raspberry
    [/quote]
    1. I’m fairly experienced Linux user but even I don’t get what some of the forum users are babbling about in the links you posted. They may not know what the hell they’re talking about or they’re simply not giving enough info.

    2. In one of the links somebody used the same test utility that I recommended.

    Remember: many controllers behave according to the harware USB standard set by engineers a and will be recognized by your operating system (Android, Linux, Windows, etc.) automatically! If your manufacturer did not abide to said standard it is a gamble if the controller will work or not. Microsoft Windows tends to come out of the box with some drivers for exotic hardware because Windows is so popular the the manufacturers make sure their stuff works, even though its exotic and weird.

    On Android, Linux or MacOS you might not be that lucky. And again: the ONLY one that knows is the manufacturer of your hardware! So check its forum or website to find out if it needs a special driver or not.

    In my experience it doesn’t matter if the controller says that it is a POV (one of my faux SNES USB controllers is like that). You can solve that w/ the controller config screen in RetroPie/Emulation station. What DOES matter is if Linux can “see” your controller and if it recognizes that it is a Game Controller. Again, test w/:

    jstest /dev/input/js0
    Additionally you might want to check if the controller is connected properly with the command:

    lsusb
    That will list all connected USB devices, if it has a driver loaded or not.

    Good luck :)

    #121464
    InsecureSpike
    Participant

    https://www.raspberrypi.org/forums/viewtopic.php?f=29&t=44177&hilit=move%2broot%2bfs%2busb%2btutorial&sid=2503f9ffe9afaa2edb49aef4537a862a

    but I’d probably stay away of doing that way, as if you develop a fault in you file system, you’ll need to probably start all over again.
    I’d suggest just running your roms from your pi drive!

    #121454
    pi-guy
    Participant

    -Wireless Only Portion
    Well, kind of good news for those with the steam controller. It appears that the mouse pad portion of the steam controller works with retropie – bad news is emulation station doesn’t use a mouse :)

    When in retropie and over wireless, if you run your finger over the right d-pad area it lightly vibrates just like on a desktop and these files show up in /dev/input/by-id:
    usb-Valve_Software_Steam_Controller-event-mouse
    usb-Valve_Software_Steam_Controller-mouse

    I did add the /lib/udev/rules.d/99-steam-controller-perms.rules file and contents, rebooted, and plugged in the steam wireless stick on reboot.
    However, js0 or any js* for that matter doesn’t exist when only the steam controller is plugged in.

    -Wired Only Portion
    So, after messing around with the wireless and getting no where, I plugged it in using a micro usb to usb cable and rebooted again. Once in emulation station I went to configure input it found the device….but as a keyboard….the ONLY buttons and pads/sticks that seem to work for me right now are:
    A Button
    Start Button
    Select Button
    Left D-Pad (I think you can also configure the stick as the same…kind of a clone thing between the stick and left d-pad)
    And that’s it….no B button….give me at least the B button so I can play NES roms :)

    -More
    FYI – I’m running a Pi3 with keyboard and built-in wifi enabled, can’t promise good performance on a Pi2 with the stuff below per the URL below.

    So I found this tid-bit URL

    Hoped on putty and performed a sudo pip install libusb1 (I don’t know what version of php I have or came on the retropie 3.6 image, but giving it a go anyways…remember I backed up! *My install is fairly clean, I did install the Descent I & II ports, updated RP scripts, and that’s about it (aside from adding my roms)

    Next, in my home directory I did a wget https://github.com/ynsta/steamcontroller/archive/master.tar.gz
    and

    tar xf master.tar.gz
    cd steamcontroller-master
    sudo python setup.py install

    then
    sudo nano /etc/udev/rules.d/99-steam-controller.rules
    and added the following inside the empty file

    # replace game group by a valid group on your system
    # Steam controller keyboard/mouse mode
    SUBSYSTEM=="usb", ATTRS{idVendor}=="28de", GROUP="games", MODE="0660"
    
    # Steam controller gamepad mode
    KERNEL=="uinput", MODE="0660", GROUP="games", OPTIONS+="static_node=uinput"

    Then reloaded udev
    sudo udevadm control --reload

    Then

    cd /steamcontroller-master/scripts
    sc-xbox.py start

    But got a bunch of errors with a lot of “enum” words in it, so I felt lucky and installed the part of the website (above) that listed “enum” in it:
    sudo pip install enum34
    It said something about the requirement already being satisfied, so I figured I was s***-out-of-luck. But for giggles I did the following:

    sudo udevadm control --reload
    sc-xbox.py start

    and low-and-behold no messages…looking good so far…didn’t think I’d get this far.
    So, the thing is I’ve got a 70″ screen mounted to the wall with no media center underneath, everything I use is either HD antenna, PLEX, or Roku, I cut the cable years ago and prefer a clean look. So, I’m not keen on having a keyboard hanging off the Pi3 mounted behing the TV, so my next step (after testing) is to setup the python script to auto-start. So, I’m going to edit my rc.local file
    sudo nano /etc/rc.local
    and add the following (change your paths if needed) after all the commented lines but BEFORE the exit 0 line.
    /home/pi/steamcontroller-master/scripts/sc-xbox.py start
    after saving the file I stopped the process I kicked off earlier and tested the rc.local file by:

    sc-xbox.py stop
    /etc/rc.local

    Just to make sure no errors popped up, kept the steam controller plugged in (hardwire) and I’m ready for a reboot to see if it started.
    Wow, now when I go to Configure Input in emulation station I get a “1 gamepad detected”, I hold “A” on the joystick and it see’s it as a XBOX 360 Gamepad…that’s what I call progress.
    The controller is VERY touch sensitive, and I can’t seem to get the right bottom trigger or left thumb press to be defined.
    I’ll work on it a bit tomorrow, see if I’m doing something wrong and take a look at the python script…I’m a bit of a script kiddie (is that saying even still used?).
    Played a quick level in Super Mario on the NES (still wired joystick), exited with start-select like normal, then unplugged joystick and plugged the wireless stick in…this is where you get all warm and creamy….even without a reboot…the joystick works great and immediately over wireless…just need to turn the controller back on after unplugging the usb cable.
    I’m sooo thrilled and taken waaayy to much room in this forum…hope this helps someone.

    I’m thinking of writing a script to make this process much faster, I’m not the coder of the “steamcontroller-master” app, kudos to that person for making my life easier, but I can certainly make setting up a Steam Controller on a RPi much faster (I think).

    *Edit:
    Here’s my config file, all buttons working and configured to use the thumbstick instead of the left d-pad for moving (I don’t like the sensitivity of the pads, so I swapped the d-pad for the thumbstick), just backup and overwrite your sudo nano /opt/retropie/configs/all/retroarch-joypads/MicrosoftX-Box360pad.cfg with this info:

    input_device = "Microsoft X-Box 360 pad"
    input_driver = "udev"
    input_r_y_plus_axis = "+4"
    input_l3_btn = "9"
    input_r_x_minus_axis = "-3"
    input_r_axis = "+5"
    input_save_state_axis = "+5"
    input_l2_btn = "4"
    input_start_btn = "7"
    input_exit_emulator_btn = "7"
    input_l_y_minus_btn = "h0leftanalogup"
    input_l_axis = "+2"
    input_load_state_axis = "+2"
    input_up_axis = "-1"
    input_r_y_minus_axis = "-4"
    input_a_btn = "0"
    input_b_btn = "1"
    input_reset_btn = "1"
    input_down_axis = "+1"
    input_r2_btn = "5"
    input_l_x_plus_btn = "h0leftanalogright"
    input_l_y_plus_btn = "h0leftanalogdown"
    input_right_axis = "+0"
    input_state_slot_increase_axis = "+0"
    input_x_btn = "2"
    input_menu_toggle_btn = "2"
    input_select_btn = "6"
    input_enable_hotkey_btn = "6"
    input_l_x_minus_btn = "h0leftanalogleft"
    input_y_btn = "3"
    input_left_axis = "-0"
    input_state_slot_decrease_axis = "-0"
    input_r_x_plus_axis = "+3"
    #121449
    briangilbert
    Participant

    I have a piDrive on a rPI3:
    https://www.kickstarter.com/projects/2073955313/pidrive-low-power-msata-ssd-for-the-raspberry-pi

    and have followed the steps at:
    http://www.mictronics.de/2016/03/install-and-run-an-existing-image-from-pidrive/3/

    To try and make the retropie image boot directly from the hard drive, but the resizing script just ran forever (4hours until I killed it)

    After rebooting I see the retropie boot screen, but after that I’m thrown to a prompt.

    df shows the following:

    Filesystem     1K-blocks    Used Available Use% Mounted on
    /dev/root        2371536 2284240         0 100% /
    devtmpfs          372268       0    372268   0% /dev
    tmpfs             376588       0    376588   0% /dev/shm
    tmpfs             376588    5296    371292   2% /run
    tmpfs               5120       4      5116   1% /run/lock
    tmpfs             376588       0    376588   0% /sys/fs/cgroup
    /dev/mmcblk0p1    129776   21046    108730  17% /boot
    /dev/sda1          58234   19952     38282  35% /media/usb1

    I’m hoping someone may be able to help me figure out how to get this working?

    #121445
    xd3l
    Participant

    I have done a fresh install of RetroPie on my Pi 3, this time using only a class 10 SD card. I installed Baldur’s gate (after 3 attempts), copied over the files, and it just works.

    I am going to try to duplicate this on my Pi 2 which also has a fresh install of RetroPie and see if I can get the same results, after which I am going to transfer the root partition to a USB stick and see what fruit that yields.

    sid723
    Participant

    Anyone have experience with the JUYAO Dual Joystick USB interface board?

    #121379
    dankcushions
    Participant

    weirdly i noticed this issue seems to only happen when i’m NOT connecting my controllers via a USB hub. not a thorough test but yeah.

    meneerjansen
    Participant

    If I were you I’d spend my time and energy on finding a good power supply first. Very strange inexplicable things happen on an under-powered Pi. I have some adapters that say “2 Ampère” but they don’t work w/ the Pi. Those USB power adapters are pretty cheap on DealExtreme etc. Buy another.

    Succes. :)

    #121353
    meneerjansen
    Participant
    1. Can you provide us w/ a link to the website of the manufacturer and the support page of this particular stick?
    2. It is important that the stick’s hardware or chip sends a signal via USB “saying” to the operating system (i.e. Windows or Linux) that it actually is a joysick (as opposed to a keyboard, a mouse or …).

    If, and only if, this joystick “behaves” like any normal USB game device (i.e. does NOT need any special proprietary drivers to work (see website of manufacturer) then you can test on the Command Line Interface (CLI) of your Pi if it is detected. Do:

    1. Make sure you’ve connected only the joystick you want to test: directly to the Pi, not via an USB hub.
    2. Install the package ‘Joystick’ w/: “sudo apt-get install joystick”.
    3. Test joystick/determine numbers of your buttons etc.: jstest /dev/input/js0.

    If you do not see a lot of ‘axis’ and ‘button’ messages but an error message then your stick is not detected by Linux (RetroPie is a Linux application).

    If your joystick needs a driver (see website of manufacturer!!!) then you’d better pray that there is a Linux driver that is easily compiled from source code. The Pi runs an ARM platform and most computers are Intel/AMD based. So most “easy to install” drivers (read: pre-compiled binary drivers) are for that platform. However, sometimes a driver or special software does not need to be downloaded from the manufacturers website because the Linux community compiled a driver for it (open source driver or by reverse engineering etc. like the Soundblaster Live audio cards etc.). Then you might be able to install the necessary diver and utility w/ apt-get install driver_name_of_your_joystick. Anyway only the manufacturer can make things clear for us!!

    Succes. :)

    dudesdude
    Participant

    I fixed my issue.

    For anyone else who uses a Pi 3 or Retropie 3.6 here is how to make both gamepads be detected.

    Go to sudo nano /boot/cmdline.txt.

    Do exactly what DuckClimber says in his usbquirks post.

    So, go to the end of the first line, hit the spacebar after the last word in the first line.

    Paste this usbhid.quirks=0x16c0:0x05e1:0x040

    Warning: Your usbid may be different.

    Use lsusb to check.

    From here if you already configured a gamepad (I did in my case so the config menu was not coming back up in emulationstation) delete this file.

    This is the command exactly.

    sudo rm /home/pi/.emulationstation/es_input.cfg

    Reboot.

    In the commandline type reboot

    Now when you reboot you should have the configuration menu come up and two game pads should be detected.

    If you ever need to check your joysticks, install this.

    sudo apt-get install joystick

    Then to test your joysticks, do this.

    jstest /dev/input/js0

    and

    jstest /dev/input/js1

    Results will be something like this.

    Axes: 0: 0 1: 0: Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:off 7:off

Viewing 35 results - 71 through 105 (of 3,655 total)