@bkg2k

https://forum.recalbox.com/topic/16576/february-2019-beta-version/18

Issue still persists on latest build, Kodi also fails to start on x64 image (both by selecting it form menu and shortcut button Y). No error on es_launch_stdout.log

/recalbox/share/system/logs/es_launch_stderr.log

# cat es_launch_stderr.log 
usage: emulatorlauncher.pyc [-h] [-p1index P1INDEX] [-p1guid P1GUID]
                            [-p1name P1NAME] [-p1devicepath P1DEVICEPATH]
                            [-p1nbaxes P1NBAXES] [-p2index P2INDEX]
                            [-p2guid P2GUID] [-p2name P2NAME]
                            [-p2devicepath P2DEVICEPATH] [-p2nbaxes P2NBAXES]
                            [-p3index P3INDEX] [-p3guid P3GUID]
                            [-p3name P3NAME] [-p3devicepath P3DEVICEPATH]
                            [-p3nbaxes P3NBAXES] [-p4index P4INDEX]
                            [-p4guid P4GUID] [-p4name P4NAME]
                            [-p4devicepath P4DEVICEPATH] [-p4nbaxes P4NBAXES]
                            [-p5index P5INDEX] [-p5guid P5GUID]
                            [-p5name P5NAME] [-p5devicepath P5DEVICEPATH]
                            [-p5nbaxes P5NBAXES] -system SYSTEM [-rom ROM]
                            [-emulator EMULATOR] [-core CORE] [-ratio RATIO]
                            [-demo DEMO] [-netplay NETPLAY]
                            [-netplay_ip NETPLAY_IP]
                            [-netplay_port NETPLAY_PORT] [-hash HASH]
                            [-extra EXTRA]
emulatorlauncher.pyc: error: unrecognized arguments: ��
# 

Thanks again team recalbox.

@bkg2k

https://forum.recalbox.com/topic/16576/february-2019-beta-version/17

F710 controller working on latest beta thanks (recalbox.2019-02-23-beta.x86_64.)

	</inputConfig>
	<inputConfig type="joystick" deviceName="Logitech Gamepad F710" deviceGUID="030000006d0400001fc2000005030000" deviceNbAxes="4" deviceNbHats="1" deviceNbButtons="13">
		<input name="a" type="button" id="1" value="1" code="305" />
		<input name="b" type="button" id="0" value="1" code="304" />
		<input name="down" type="hat" id="0" value="4" code="16" />
		<input name="hotkey" type="button" id="10" value="1" code="316" />
		<input name="joystick1left" type="axis" id="0" value="-1" code="0" />
		<input name="joystick1up" type="axis" id="1" value="-1" code="1" />
		<input name="joystick2left" type="axis" id="2" value="-1" code="3" />
		<input name="joystick2up" type="axis" id="3" value="-1" code="4" />
		<input name="l2" type="button" id="6" value="1" code="312" />
		<input name="left" type="hat" id="0" value="8" code="16" />
		<input name="pagedown" type="button" id="5" value="1" code="311" />
		<input name="pageup" type="button" id="4" value="1" code="310" />
		<input name="r2" type="button" id="7" value="1" code="313" />
		<input name="right" type="hat" id="0" value="2" code="16" />
		<input name="select" type="button" id="8" value="1" code="314" />
		<input name="start" type="button" id="9" value="1" code="315" />
		<input name="up" type="hat" id="0" value="1" code="16" />
		<input name="x" type="button" id="3" value="1" code="308" />
		<input name="y" type="button" id="2" value="1" code="307" />
	</inputConfig>
</inputList>

Another issue (same hardware as previous post), this time with libcec not creating /dev/tty* for my usb cec adaptor. Possible udev issue (missing rule)?
I have had this adaptor working on the last stable on another box.
Thanks again.

# dmesg | grep -i cec
[    1.943138] usb 1-4: Product: CEC Adapter
[    3.267137] input: Pulse-Eight CEC Adapter as /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4:1.2/0003:2548:1002.0001/input/input14
[    3.267239] hid-generic 0003:2548:1002.0001: input,hidraw0: USB HID v1.10 Mouse [Pulse-Eight CEC Adapter] on usb-0000:00:14.0-4/input2
#

# cec-client
No device type given. Using 'recording device'
CEC Parser created - libCEC version 4.0.2
no serial port given. trying autodetect:
 path:     /sys/devices/pci0000:00/0000:00:14.0/usb1/1-4
 com port: /sys/devices/pci0000:00/0000:00:14.0/usb1/1-4

opening a connection to the CEC adapter...
DEBUG:   [              11]     Broadcast (F): osd name set to 'Broadcast'
ERROR:   [            3514]     error opening serial port '/sys/devices/pci0000:00/0000:00:14.0/usb1/1-4': Is a directory
ERROR:   [            3514]     could not open a connection (try 1)
ERROR:   [            6349]     error opening serial port '/sys/devices/pci0000:00/0000:00:14.0/usb1/1-4': Is a directory
ERROR:   [            6349]     could not open a connection (try 2)
ERROR:   [            8239]     error opening serial port '/sys/devices/pci0000:00/0000:00:14.0/usb1/1-4': Is a directory
ERROR:   [            8239]     could not open a connection (try 3)
ERROR:   [            9499]     error opening serial port '/sys/devices/pci0000:00/0000:00:14.0/usb1/1-4': Is a directory
ERROR:   [            9499]     could not open a connection (try 4)
unable to open the device on port /sys/devices/pci0000:00/0000:00:14.0/usb1/1-4
NOTICE:  [           10504]     connection opened
ERROR:   [           10504]     could not start CEC communications
#

Many thanks for this build, it installs on my ASUS VivoMini VC65-C1 (i5-8400T, Intel HD Graphics 630) whereas the previous beta did not.

It seems that recalbox-configgen is not configuring my F710 joypad in dreamcast/reicast (works fine so far in other emulators bundled in the build) I have tried re mapping the controller with no change.

my controllerP1.cfg

[compat]
btn_trigger_left = 0
axis_dpad1_y = 1
btn_trigger_right = 0
axis_dpad1_x = 0

[emulator]
mapping_name = Logitech Gamepad F710
btn_escape = 0

[dreamcast]
btn_b = 0
btn_a = 0
btn_x = 0
btn_start = 0
btn_y = 0
axis_y = 0
axis_x = 0

my emu.cfg

[audio]
backend = auto
disable = 0

[config]
Debug.SerialConsoleEnabled = 0
Dreamcast.Broadcast = 4
Dreamcast.Cable = 3
Dreamcast.RTC = -2113930091
Dreamcast.Region = 3
Dynarec.Enabled = 1
Dynarec.idleskip = 1
Dynarec.unstable-opt = 0
aica.LimitFPS = 1
aica.NoBatch = 0
aica.NoSound = 0
bios.UseReios = 0
pvr.MaxThreads = 3
pvr.Subdivide = 0
pvr.SynchronousRendering = 0
pvr.rend = 0
rend.UseMipmaps = 1
rend.WideScreen = 0
ta.skip = 0

[input]
enable_x11_keyboard = 1
evdev_device_id_1 = 5
evdev_device_id_2 = 6
evdev_device_id_3 = -1
evdev_device_id_4 = -1
evdev_mapping_1 = /recalbox/share/system/configs/reicast/controllerP1.cfg
evdev_mapping_2 = /recalbox/share/system/configs/reicast/controllerP2.cfg

[pvr]
nox11 = 0

[reios]
ElfFile = 

[testing]
ta.HashCheckFile = 
ta.HashLogFile = 

[validate]
OpenGlChecks = 0

[x11]
fullscreen = 0
height = 480
width = 640

https://forum.recalbox.com/topic/14398/menu-and-kodi-is-not-full-screen-on-old-netbook/4

Here may be of help

Cheers thanks

I have complied a x86_64 dev build from master, using docker and the generic config which built and installed fine.

I`m wondering when the next stable is released can I upgrade to it, or do I need to reinstall the stable image when released ?

Reason being is that I have tried the Christmas beta , but the target box has no ethernet access whereas the dev build (built 9th Jan) has working ethernet. So I cant investigate/report issues with the Christmas build.

Thanks.

@felipeadms said in How to convert changes made in recalbox to .IMG?:

@paradadf I understand, but even then I would like to know how to compile the changes made to a ".img" file image. Do you know how to do that?

@felipeadms

You could shrink your created image if your handy with linux by mounting the image as loopback, resizing it, then truncating it.

https://softwarebakery.com/shrinking-images-on-linux

@strodown Many thanks for the image. Would you mind explaining how you compiled the image ? Did you add the nvidia buildroot to the build then build it via the recallbox docker ? If so l would like to compile an image for the nvidia legacy blob to test it on a old pc I have. Cheers.