SVP, de l'aide ...
Posts made by Erebos
-
RE: Pb config commandes
@Erebos said in Pb config commandes:
GameControllerConfig:
missing (see 'gamecontrollerdb.txt' or SDL_GAMECONTROLLERCONFIG)Bizare cela non ?
-
RE: Pb config commandes
sdl2-jstest -e 0
error: failed to read gamecontrollerdb.txt: Invalid RWops
Joystick Name: 'Xin-Mo Dual Arcade'
Joystick Path: '/dev/input/event0'
Joystick GUID: 03000000c0160000e105000001010000
Joystick Number: 0
Number of Axes: 2
Number of Buttons: 10
Number of Hats: 0
Number of B***s: 0
GameControllerConfig:
missing (see 'gamecontrollerdb.txt' or SDL_GAMECONTROLLERCONFIG)
Axis code 0: 0
Axis code 1: 1
Button code 0: 288
Button code 1: 289
Button code 2: 290
Button code 3: 291
Button code 4: 292
Button code 5: 293
Button code 6: 294
Button code 7: 295
Button code 8: 296
Button code 9: 297Entering joystick test loop, press Ctrl-c to exit
SDL_JOYDEVICEADDED which:0
SDL_JOYDEVICEADDED which:1
SDL_CONTROLLERDEVICEADDED which:0
SDL_CONTROLLERDEVICEADDED which:1 -
RE: Pb config commandes
sdl2-jstest --list
error: failed to read gamecontrollerdb.txt: Invalid RWops
Found 2 joystick(s)Joystick Name: 'Xin-Mo Dual Arcade'
Joystick Path: '/dev/input/event0'
Joystick GUID: 03000000c0160000e105000001010000
Joystick Number: 0
Number of Axes: 2
Number of Buttons: 10
Number of Hats: 0
Number of B***s: 0
GameControllerConfig:
Name: 'Xin-Mo Xin-Mo Dual Arcade'
Mapping: '03000000c0160000e105000001010000,Xin-Mo Xin-Mo Dual Arcade,a:b4,b:b3,back:b6,dpdown:b12,dpleft:b13,dpright:b14,dpup:b11,guide:b9,leftshoulder:b2,leftx:a0,lefty:a1,rightshoulder:b5,start:b7,x:b1,y:b0,platform:Linux'
Axis code 0: 0
Axis code 1: 1
Button code 0: 288
Button code 1: 289
Button code 2: 290
Button code 3: 291
Button code 4: 292
Button code 5: 293
Button code 6: 294
Button code 7: 295
Button code 8: 296
Button code 9: 297Joystick Name: 'Xin-Mo Dual Arcade'
Joystick Path: '/dev/input/event1'
Joystick GUID: 03000000c0160000e105000001010000
Joystick Number: 1
Number of Axes: 2
Number of Buttons: 12
Number of Hats: 0
Number of B***s: 0
GameControllerConfig:
Name: 'Xin-Mo Xin-Mo Dual Arcade'
Mapping: '03000000c0160000e105000001010000,Xin-Mo Xin-Mo Dual Arcade,a:b4,b:b3,back:b6,dpdown:b12,dpleft:b13,dpright:b14,dpup:b11,guide:b9,leftshoulder:b2,leftx:a0,lefty:a1,rightshoulder:b5,start:b7,x:b1,y:b0,platform:Linux'
Axis code 0: 0
Axis code 1: 1
Button code 0: 288
Button code 1: 289
Button code 2: 290
Button code 3: 291
Button code 4: 292
Button code 5: 293
Button code 6: 294
Button code 7: 295
Button code 8: 296
Button code 9: 297
Button code 10: 298
Button code 11: 299 -
RE: Pb config commandes
Event: time 1712412674.028571, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90001
Event: time 1712412674.028571, type 1 (EV_KEY), code 288 (BTN_TRIGGER), value 1
Event: time 1712412674.028571, -------------- SYN_REPORT ------------
Event: time 1712412674.124600, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90001
Event: time 1712412674.124600, type 1 (EV_KEY), code 288 (BTN_TRIGGER), value 0
Event: time 1712412674.124600, -------------- SYN_REPORT ------------
Event: time 1712412674.332609, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90002
Event: time 1712412674.332609, type 1 (EV_KEY), code 289 (BTN_THUMB), value 1
Event: time 1712412674.332609, -------------- SYN_REPORT ------------
Event: time 1712412674.444641, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90002
Event: time 1712412674.444641, type 1 (EV_KEY), code 289 (BTN_THUMB), value 0
Event: time 1712412674.444641, -------------- SYN_REPORT ------------
Event: time 1712412675.100713, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90003
Event: time 1712412675.100713, type 1 (EV_KEY), code 290 (BTN_THUMB2), value 1
Event: time 1712412675.100713, -------------- SYN_REPORT ------------
Event: time 1712412675.236739, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90003
Event: time 1712412675.236739, type 1 (EV_KEY), code 290 (BTN_THUMB2), value 0
Event: time 1712412675.236739, -------------- SYN_REPORT ------------
Event: time 1712412675.620784, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90004
Event: time 1712412675.620784, type 1 (EV_KEY), code 291 (BTN_TOP), value 1
Event: time 1712412675.620784, -------------- SYN_REPORT ------------
Event: time 1712412675.716809, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90004
Event: time 1712412675.716809, type 1 (EV_KEY), code 291 (BTN_TOP), value 0
Event: time 1712412675.716809, -------------- SYN_REPORT ------------
Event: time 1712412676.404896, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90005
Event: time 1712412676.404896, type 1 (EV_KEY), code 292 (BTN_TOP2), value 1
Event: time 1712412676.404896, -------------- SYN_REPORT ------------
Event: time 1712412676.516926, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90005
Event: time 1712412676.516926, type 1 (EV_KEY), code 292 (BTN_TOP2), value 0
Event: time 1712412676.516926, -------------- SYN_REPORT ------------
Event: time 1712412676.948981, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90006
Event: time 1712412676.948981, type 1 (EV_KEY), code 293 (BTN_PINKIE), value 1
Event: time 1712412676.948981, -------------- SYN_REPORT ------------
Event: time 1712412677.077114, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90006
Event: time 1712412677.077114, type 1 (EV_KEY), code 293 (BTN_PINKIE), value 0
Event: time 1712412677.077114, -------------- SYN_REPORT ------------
Event: time 1712412679.197298, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90007
Event: time 1712412679.197298, type 1 (EV_KEY), code 294 (BTN_BASE), value 1
Event: time 1712412679.197298, -------------- SYN_REPORT ------------
Event: time 1712412679.253306, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90007
Event: time 1712412679.253306, type 1 (EV_KEY), code 294 (BTN_BASE), value 0
Event: time 1712412679.253306, -------------- SYN_REPORT ------------
Event: time 1712412680.341499, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90009
Event: time 1712412680.341499, type 1 (EV_KEY), code 296 (BTN_BASE3), value 1
Event: time 1712412680.341499, -------------- SYN_REPORT ------------
Event: time 1712412680.421521, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90009
Event: time 1712412680.421521, type 1 (EV_KEY), code 296 (BTN_BASE3), value 0
Event: time 1712412680.421521, -------------- SYN_REPORT ------------
Event: time 1712412680.981539, type 4 (EV_MSC), code 4 (MSC_SCAN), value 9000a
Event: time 1712412680.981539, type 1 (EV_KEY), code 297 (BTN_BASE4), value 1
Event: time 1712412680.981539, -------------- SYN_REPORT ------------
Event: time 1712412681.045623, type 4 (EV_MSC), code 4 (MSC_SCAN), value 9000a
Event: time 1712412681.045623, type 1 (EV_KEY), code 297 (BTN_BASE4), value 0
Event: time 1712412681.045623, -------------- SYN_REPORT ------------
Event: time 1712412681.949682, type 3 (EV_ABS), code 1 (ABS_Y), value 1
Event: time 1712412681.949682, -------------- SYN_REPORT ------------
Event: time 1712412682.109705, type 3 (EV_ABS), code 1 (ABS_Y), value 0
Event: time 1712412682.109705, -------------- SYN_REPORT ------------
Event: time 1712412682.509762, type 3 (EV_ABS), code 1 (ABS_Y), value -1
Event: time 1712412682.509762, -------------- SYN_REPORT ------------
Event: time 1712412682.685786, type 3 (EV_ABS), code 1 (ABS_Y), value 0
Event: time 1712412682.685786, -------------- SYN_REPORT ------------
Event: time 1712412683.117839, type 3 (EV_ABS), code 0 (ABS_X), value -1
Event: time 1712412683.117839, -------------- SYN_REPORT ------------
Event: time 1712412683.285871, type 3 (EV_ABS), code 0 (ABS_X), value 0
Event: time 1712412683.285871, -------------- SYN_REPORT ------------
Event: time 1712412683.749935, type 3 (EV_ABS), code 0 (ABS_X), value 1
Event: time 1712412683.749935, -------------- SYN_REPORT ------------
Event: time 1712412683.910009, type 3 (EV_ABS), code 0 (ABS_X), value 0
Event: time 1712412683.910009, -------------- SYN_REPORT ------------ -
RE: Pb config commandes
evtest
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0: Xin-Mo Xin-Mo Dual Arcade
/dev/input/event1: Xin-Mo Xin-Mo Dual Arcade
/dev/input/event2: vc4
/dev/input/event3: vc4
Select the device event number [0-3]: 0
Input driver version is 1.0.1
Input device ID: bus 0x3 vendor 0x16c0 product 0x5e1 version 0x101
Input device name: "Xin-Mo Xin-Mo Dual Arcade"
Supported events:
Event type 0 (EV_SYN)
Event type 1 (EV_KEY)
Event code 288 (BTN_TRIGGER)
Event code 289 (BTN_THUMB)
Event code 290 (BTN_THUMB2)
Event code 291 (BTN_TOP)
Event code 292 (BTN_TOP2)
Event code 293 (BTN_PINKIE)
Event code 294 (BTN_BASE)
Event code 295 (BTN_BASE2)
Event code 296 (BTN_BASE3)
Event code 297 (BTN_BASE4)
Event type 3 (EV_ABS)
Event code 0 (ABS_X)
Value 0
Min -1
Max 1
Event code 1 (ABS_Y)
Value 0
Min -1
Max 1
Event type 4 (EV_MSC)
Event code 4 (MSC_SCAN)
Properties:
Testing ... (interrupt to exit) -
RE: Pb config commandes
boot$ evtest
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0: Xin-Mo Xin-Mo Dual Arcade
/dev/input/event1: Xin-Mo Xin-Mo Dual Arcade
/dev/input/event2: vc4
/dev/input/event3: vc4
/dev/input/event4: GPIO Controller 1
/dev/input/event5: GPIO Controller 2 -
RE: Pb config commandes
Si ca peut aider :
/boot$ dmesg | grep "usb"
[ 0.175020] usbcore: registered new interface driver usbfs
[ 0.175079] usbcore: registered new interface driver hub
[ 0.175141] usbcore: registered new device driver usb
[ 0.175513] usb_phy_generic phy: supply vcc not found, using dummy regulator
[ 0.175710] usb_phy_generic phy: dummy supplies not allowed for exclusive requests
[ 1.418753] usbcore: registered new interface driver r8152
[ 1.418814] usbcore: registered new interface driver lan78xx
[ 1.418878] usbcore: registered new interface driver smsc95xx
[ 1.468939] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.15
[ 1.468960] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.468975] usb usb1: Product: xHCI Host Controller
[ 1.468988] usb usb1: Manufacturer: Linux 5.15.92-v8 xhci-hcd
[ 1.469000] usb usb1: SerialNumber: 0000:01:00.0
[ 1.470721] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.15
[ 1.470742] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.470757] usb usb2: Product: xHCI Host Controller
[ 1.470770] usb usb2: Manufacturer: Linux 5.15.92-v8 xhci-hcd
[ 1.470783] usb usb2: SerialNumber: 0000:01:00.0
[ 1.474121] usbcore: registered new interface driver uas
[ 1.474210] usbcore: registered new interface driver usb-storage
[ 1.725490] usb 1-1: new high-speed USB device number 2 using xhci_hcd
[ 1.876072] usb 1-1: New USB device found, idVendor=2109, idProduct=3431, bcdDevice= 4.21
[ 1.876081] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[ 1.876087] usb 1-1: Product: USB2.0 Hub
[ 2.173481] usb 1-1.1: new low-speed USB device number 3 using xhci_hcd
[ 2.281062] usb 1-1.1: New USB device found, idVendor=16c0, idProduct=05e1, bcdDevice= 1.00
[ 2.281070] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 2.281076] usb 1-1.1: Product: Xin-Mo Dual Arcade
[ 2.281081] usb 1-1.1: Manufacturer: Xin-Mo
[ 4.453015] usbcore: registered new interface driver usbhid
[ 4.453047] usbhid: USB HID core driver
[ 4.469383] input: Xin-Mo Xin-Mo Dual Arcade as /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.1/1-1.1:1.0/0003:16C0:05E1.0001/input/input0
[ 4.470131] input: Xin-Mo Xin-Mo Dual Arcade as /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.1/1-1.1:1.0/0003:16C0:05E1.0001/input/input1
[ 4.470480] xinmo 0003:16C0:05E1.0001: input,hidraw0: USB HID v1.01 Joystick [Xin-Mo Xin-Mo Dual Arcade] on usb-0000:01:00.0-1.1/input0
[ 4.573189] usbcore: registered new interface driver brcmfmac -
RE: Pb config commandes
J'ai cela qui a été généré dans le fichier de config :
Configurations generated by Recalbox
emulationstation.theme.recalbox-next.gameclipview=0 - DEFAULT
emulationstation.theme.recalbox-next.systemview=1-vertical left
emulationstation.theme.recalbox-next.colorset=1-light blue colors
emulationstation.theme.recalbox-next.iconset=1-standard icons
emulationstation.theme.recalbox-next.region=us
emulationstation.theme.recalbox-next.gamelistview=1-standard gamelist
emulationstation.theme.recalbox-next.menuset=1-light blue icons
system.firsttimeuse=0
emulationstation.pad0=03000000c0160000e105000001010000:Xin-Mo Dual Arcade
emulationstation.pad1=03000000c0160000e105000001010000:Xin-Mo Dual Arcade -
Pb config commandes
Bonjour,
j'ai changé mon RPi3b vers un RPi 4 avec une 9.1 : Changement RPI3 (DragonBlaze) vers RPI4 (ReclBox 9.1)
J'ai remis les branchements à l'identique mais mes boutons + joystick de ma borne sont tous mappé n'importe comment.
Je ne peux pas trouver le bouton pour rentrer dans les parametres de config des sticks + boutons ... merci de me dire comment faire, je suis bloqué.Cdlt
-
RE: RecalBox 9.1 - PI4B - Pb WIFI et GPIO
@Nazgulh Il les détectais avant et là il met manquant, pourtant j'ai bien pris le bon pack placé au bon endroit.
De plus, la config manette est à refaire à chaque démarrage ... bizarre(le WIFI ne marche tjrs pas non plus mais j'ai branché réseau pour que les drivers du Xi-mo se donwload au démarrage/
-
RE: RecalBox 9.1 - PI4B - Pb WIFI et GPIO
@Nazgulh Top merci.
J'ai connecté grace a un long cable en reseau. Ca a fonctionné pour configurer l'interface Xing Mao (un truc comme ca).
Bon pas facile et soucis pour config mais passons.Par contre j'ai un jeux Saturn qui se lancait avant .... et ne se lance plus maintenant en me disant manque un fichier de Bios .... comment a-t-il pu disparaitre ????
-
RE: RecalBox 9.1 - PI4B - Pb WIFI et GPIO
@Nazgulh OUi mais j'ai que des manettes de switch
-
RE: RecalBox 9.1 - PI4B - Pb WIFI et GPIO
@Nazgulh Salut, désolé pas répondu avant car bcp de boulot.
Oui pas de soucis je l'ai branché en filaire et j'ai editer en ssh ca pas de soucis.
Mais apparemment il prend pas en compte la config.C'est la toute derniere version, la 9.1 pour RPI4B
Ca me fait chier de devoir formater (pas d'autre carte sous la main de vide) car j'ai deja mis les ROMS ...
A ce jour pas de solution sauf essayer de trouver un grand cable reseau pour booter le RPI4 sur la borne avec le GPIO et donc pouvoir avoir les driver et ensuite comme ca pouvoir aller config le WIFI direct sur la borne.
-
RE: RecalBox 9.1 - PI4B - Pb WIFI et GPIO
@Nazgulh Salut, c'est fait, je m'en suis aperçu mais pas mieux. Si je mets la carte dans un RPI qui fonctionne en WIFI ca ne fonctionne pas. Donc ca vient bien de la config.
Est-ce que Recalbox surcharge la config car le fichier "wpa_supplicant" du PI dans /etc n'a pas les infos ... et pas modifiable car en Read_Only système.
-
RecalBox 9.1 - PI4B - Pb WIFI et GPIO
Bonjour j'ai un soucis, le WIFI n'est pas détecté même après modif des fichiers de conf dans le share. Et j'ai une erreur et impossible de configurer mon interface GPIO car je pense comme pas de WIFI, pas de download.
Dans le recalbox log :
[recalbox-config.sh] [CONFIG] ---- recalbox-config.sh ----
[ 9.16] [recalbox-config.sh] [MODULES] rmmod: can't unload module 'mk_arcade_joystick_rpi': No such file or directory
[ 9.17] [recalbox-config.sh] [MODULES] [ 9.19] : loading module mk_arcade_joystick_rpi args = map=1,2
[ 17.27] [S26recalboxsystem] [CONTROLLERS] starting xarcade2jsticket aussi ca :
[ 69.87] [S09wifi] [WIFI] /boot/recalbox-backup.conf not found
Dans le ES_log :
[2024/01/04 12:39:31.545] (WARN!) : [Locale] /usr/bin/locale/lang/en_US/LC_MESSAGES/emulationstation2.mo not found.
[2024/01/04 12:39:31.545] (WARN!) : [Locale] /usr/bin/locale/lang/en/LC_MESSAGES/emulationstation2.mo not found.
[2024/01/04 12:39:31.545] (WARN!) : [Locale] /usr/share/locale/en_US/LC_MESSAGES/emulationstation2.mo not found.
[2024/01/04 12:39:31.546] (INFO ) : [Locale] Using /usr/share/locale/en/LC_MESSAGES/emulationstation2.mo
[2024/01/04 12:39:31.547] (ERROR) : [SDL2] Fatal error initializing SDL 2Config WIFI du recalbox.conf :
system.hostname=RECALBOX
wifi.enabled=1
country-code
wifi.region=FR
;wifi.ssid=Livebox-XXXX (masqué volontairement)
;wifi.key=xxxxxx (masqué volontairement)Merci par avance pour votre aide
-
RE: Montée de version de 18.02.09 vers 18.03.30 : Risques et incompatibilités
Selon les besoins si je peux aider en montant en compétence au début, sauf python c'est pas trop mon truc. A voir. Le temps ben ça dépend, à voir. Possible de voir ça en privé.
-
RE: Montée de version de 18.02.09 vers 18.03.30 : Risques et incompatibilités
Linux, shell et C, excellent niveau.
C++ ca va mais je suis très Java.
Python et makefile .... pas grand chose. ^^MP si besoin de discuter ^^
-
RE: Montée de version de 18.02.09 vers 18.03.30 : Risques et incompatibilités
@oyyodams pas de soucis je sais que vous faites le max sur votre temps perso de maniere gratuite et encore une fois un grand merci a vous !
Je vais faire la maj ce soir, elle semble sans risque.Longue vie a recalbox et a votre team.
Ps : je suis ingé info et si jamais vous avez besoin d’aide je suis pret a vous aider selon mon temps.