Testers wanted: major system upgrade (Pi3b+, KODI 17 and much more ...)

[chris256]

@gaetan Merci pour ta réponse mais le lien direct semble mener à la version rpi3 uniquement et pas à la version X86 64 bit que je cherche. Je l’ai relu plusieurs fois mais je suis peut-être passé à côté ?

[deo1789]

~~Hi,

I'm trying to upgrade from 1st beta but /recalbox/scripts/recalbox-upgrade.sh can't find the upgrade files, and I can't figure how to reconfigure the target URL (not proficient with script editing

Linux RECALBOX 4.14.62-v7 #1 SMP Fri Aug 24 00:07:55 UTC 2018 armv7l GNU/Linux

recalbox.log:
[ 385.38] ------------ Will process to a https://review-507-b*mp-b-0jn0c0-archive-review-prod.recalbox.com upgrade ------------
[ 385.54] Unable to get headers for http://archive.recalbox.com/updates/v1.0/https://review-507-b*mp-b-0jn0c0-archive-review-prod.recalbox.com/rpi3/boot.tar.xz

In Recalbox.conf:

------------ G - UPDATES ------------

Automatically check for updates at start (0,1)

updates.enabled=0

Update type : default to stable

updates.type=https://review-507-b*mp-b-0jn0c0-archive-review-prod.recalbox.com
#updates.type=stable

And I can access internet from the PI3 B+ (wget with the direct URL works):

wget https://review-507-b*mp-b-0jn0c0-archive-review-prod.recalbox.com/v1/upgrade/rpi3/boot.tar.xz?source=install

--2018-12-02 08:40:41-- https://review-507-b*mp-b-0jn0c0-archive-review-prod.recalbox.com/v1/upgrade/rpi3/boot.tar.xz?source=install
Resolving review-507-b*mp-b-0jn0c0-archive-review-prod.recalbox.com (review-507-b*mp-b-0jn0c0-archive-review-prod.recalbox.com)... 91.121.112.87
Connecting to review-507-b*mp-b-0jn0c0-archive-review-prod.recalbox.com (review-507-b*mp-b-0jn0c0-archive-review-prod.recalbox.com)|91.121.112.87|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 6278736 (6.0M) [application/octet-stream]
Saving to: 'boot.tar.xz?source=install'

boot.tar.xz?source=install 100%[===================================================================>] 5.99M 1.29MB/s in 4.7s

2018-12-02 08:40:46 (1.27 MB/s) - 'boot.tar.xz?source=install' saved [6278736/6278736]

Any idea?

regards,
philippe](url du lien)

[deo1789]

EDIT from above: something must have happened, no change on my side but update is now downloading (from emulationstation GUI)...

[OyyoDams]

Direct link for X86/64 (re)added on 1st post

[chris256]

@oyyodams Thanks for the link ! I'm going to test it right now.

[chris256]

@chris256 said in Testers wanted: major system upgrade (Pi3b+, KODI 17 and much more ...):

@oyyodams Thanks for the link ! I'm going to test it right now.

So I tested. There is what I noticed so far :

• no sound through HDMI, whatever I choose in the sound menu
• when I select Quit/shutdown, I have 'Booting recalbox' but it does not stop. I stop then through the web manager.
  Too bad, it was almost good...

And when I do Launch script on the web manager to generate a support archive, the wheel keeps turning and nothing happens. Moreover, I loose network connection to Recalbox if I do this.

If anyone is OK to have a look at it, I copied the logs contents from the web interface to a text file. Here are the lines that may be relevant :

• in messages : input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input5
• in es_log : lvl0: VolumeControl::init() - Failed to find mixer elements! - lvl0: VolumeControl::init() - Failed to find mixer elements!

On the good side, I tried one n64 game and it runs very fine... Thanks for the work anyway !!

[Ignus Fast]

Interestingly, this version fixed my issues with PSX games (glitching, poor frame rate), but N64 games no longer load at all, and I have the same HDMI audio issue previously mentioned.

In es log, I see the following, but N64 games (using both emulators) just drop right back to es.

lvl2: Configure emulators command : -p1index 0 -p1guid 030000004c0500006802000011810000 -p1name "Sony PLAYSTATION(R)3 Controller" -p1nbaxes 6 -p1devicepath /dev/input/event14
lvl2: Controllers config : -p1index 0 -p1guid 030000004c0500006802000011810000 -p1name "Sony PLAYSTATION(R)3 Controller" -p1nbaxes 6 -p1devicepath /dev/input/event14
lvl2: python /usr/lib/python2.7/site-packages/configgen/emulatorlauncher.pyc -p1index 0 -p1guid 030000004c0500006802000011810000 -p1name "Sony PLAYSTATION(R)3 Controller" -p1nbaxes 6 -p1devicepath /dev/input/event14 -system n64 -rom /recalbox/share/roms/n64/Cruis'n\ USA\ (USA)\ (Rev\ B).z64 -emulator default -core default -ratio auto
lvl2: Creating surface...
lvl2: Created window successfully.
lvl2: Added known joystick Sony PLAYSTATION(R)3 Controller (instance ID: 0, device index: 0)
lvl2: SDL AUDIO Initialized

Sorry, one last thing - about half the time, my USB keyboard won't come up when es starts up. That's also new to this version. The PS3 controller always works, though.

[chris256]

@ignus-fast Hi ! Are you using X86 version or RPI ? Because n64 runs fine for me on this version. About HDMI audio, what is your problem ? On my side I don’t have sound through HDMI...

[Ignus Fast]

I apologize for not being specific - this is the x86 version. I'm still running the previous version on my Pi because I don't have a backup of that drive yet - figured I'd experiment with the PC.

I see 6 available devices for audio - 2 chipset, and 4 HDMI. But none of them produce any sound, and all constantly reset the ES volume to 0.

I'll have to back up my Pi drive so I can get physical with it.

[chris256]

@ignus-fast Thank you for your feedback about audio. I have exactly the same issue as you do. Sorry I can’t help you but may be a developer will have a look at it. Have a nice day!

[OyyoDams]

@toniosj @moguai I've just tested NAS access over wifi on the latest build, and I can confirm it works.

Here is my /boot/recalbox-boot.conf:

sharedevice=NETWORK

sharenetwork_smb1=SHARE@192.168.1.94:Games/recalbox:username=recalbox,password=******

[chris256]

@oyyodams @toniosj @moguai For those having problems, it may be related to the smb version. You could try adding vers=1.0 at the end of the line, for instance:

sharedevice=NETWORK
sharenetwork_smb1=SHARE@192.168.1.94:Games/recalbox:username=recalbox,password=******,vers=1.0

[lhari84]

@chris256
Just because I'm interested using this feature in future:
Which SMB versions are supported? I've disabled SMB1 on my NAS for security reasons, is SMB2 or even SMB3 supported too?
Thanks

[vincent-84]

@vincent-84

@vincent-84 said in Testers wanted: major system upgrade (Pi3b+, KODI 17 and much more ...):

@vincent-84 said in Testers wanted: major system upgrade (Pi3b+, KODI 17 and much more ...):

@OyyoDams
since the last release, ES always crash after the introductive video (black screen with the version of the release).
I've try with a direct upgrading (from ES) first, and then I reflash my SD card with the same result.

Any idea about that issue ?

that's came after coping my old bios and roms folders

@OyyoDams
this is my issue with this last release (when I try to start ES from root) :

"#lv10: /recalbox/share/system/.emulationstation/es_system.cfg files does not exist! [je confirme]
lv10: System "favorites" is missing name, path, extension, or command!
terminate called after throwing an instance of 'boost: : exception_detail: :clone_impl <boost: :exception_detail: :error_info_injector<boost: :property_tree: :ptree_bad_path> >'
what(): No such node (gamelist)

[paradadf]

@lhari84 this might answer your question regarding samba versions. I haven’t tested it myself though.
https://forum.recalbox.com/topic/11528/smb-v2-support/5

[lhari84]

@paradadf Great, thanks!

[kos]

Prompt why on the Chinese gamepad analog sticks work as a simple cross? When pressing home button it on the computer and retropie all switches and recalbox not be switched. What could be the problem? image url)

[pkerga]

This post is deleted!

[pkerga]

@vincent-84 said in Testers wanted: major system upgrade (Pi3b+, KODI 17 and much more ...):

@OyyoDams
since the last release, ES always crash after the introductive video (black screen with the version of the release).
I've try with a direct upgrading (from ES) first, and then I reflash my SD card with the same result.

Any idea about that issue ?

same issue

[voljega]

@matthieu24 did you read the first post ?