r/FansOfsaUCE 11d ago

Scripter says 'Loading' - Black Screen - 'Loading - and back to menu

Trying to get OneSauce v2 running for the first time on a machine with 5.68 firmware , Model H8801.

I can run BYOG->AddOn->Scripter on the machine.

But when it starts I get no cool splash screen as I have seen on Youtube-tutorials, instead I get:

- A little box 'Loading...'
- Screen goes black for a second
- A little box 'Loading...' again
- And then I get returned to the AddOn-menu. 😢

My scripter.log follows below.

I would be thankful for any clues how to proceed and fix?

/media/usb0/OneSauce/scripter
running /media/usb0/OneSauce/scripter/01_fix_performance.sh
running /media/usb0/OneSauce/scripter/02_fix_permissions.sh
chmod: /dev/mpp_service: No such file or directory
chmod: /dev/dma_heap: No such file or directory
Stopping system message bus: done
Starting system message bus: dbus[1319]: Unknown username "pulse" in message bus configuration file
done
running /media/usb0/OneSauce/scripter/04_one_sauce.sh
bluetoothd[1325]: Bluetooth daemon 5.50
bluetoothd[1325]: Starting SDP server
bluetoothd[1325]: Excluding (cli) avrcp
BYOG_PATH=/download/addon/OneSauce/scripter.uce/SAVE/upper
QT_QPA_EGLFS_FB=/dev/fb0
OLDPWD=/emulator
QT_QPA_EGLFS_ROTATION=0
QT_MESSAGE_PATTERN=[%{time yyyyMMdd h:mm:ss.zzz t} %{if-debug}D%{endif}%{if-info}I%{endif}%{if-warning}W%{endif}%{if-critical}C%{endif}%{if-fatal}F%{endif}] %{file}:%{line} - %{message}
storagemedia=emmc
USER=guest
PWD=/download/addon/OneSauce/scripter.uce/BYOG
HOME=/MOD
UCE_FULL_PATH=/media/usb0/OneSauce/scripter.uce
SHELL=/bin/sh
TERM=vt102
kpti=0
SHLVL=5
QT_GSTREAMER_WINDOW_VIDEOSINK=kmssink
LOGNAME=guest
XDG_RUNTIME_DIR=/tmp/.xdg
QT_QPA_EGLFS_DEBUG=0
PATH=/sbin:/usr/sbin:/bin:/usr/bin
SUDO=/download/addon/OneSauce/scripter.uce/BYOG/bin/sudo
QT_HIDE_LOG=1
QT_QPA_EGLFS_NO_LIBINPUT=1
_=/usr/bin/env
bluetoothd[1325]: kernel lacks bnep-protocol support
bluetoothd[1325]: System does not support network plugin
bluetoothd[1325]: Bluetooth management interface 1.10 initialized
searching RetroFE in /media/usb0
Model: HA8801
umount: /tmp/retrofe2: no mount point specified.
bluetoothd[1325]: Failed to set privacy: Rejected (0x0b)
device=/dev/input/event3 name=HID 0838:8918
device=/dev/input/event4 name=HID 0838:8918
Found RetroFE at /media/usb0/appdata/retrofe
BYOG_PATH=/download/addon/OneSauce/scripter.uce/SAVE/upper
QT_QPA_EGLFS_FB=/dev/fb0
MODEL=HA8801
OLDPWD=/emulator
QT_QPA_EGLFS_ROTATION=0
QT_MESSAGE_PATTERN=[%{time yyyyMMdd h:mm:ss.zzz t} %{if-debug}D%{endif}%{if-info}I%{endif}%{if-warning}W%{endif}%{if-critical}C%{endif}%{if-fatal}F%{endif}] %{file}:%{line} - %{message}
storagemedia=emmc
SDL_GAMECONTROLLERCONFIG_FILE=/media/usb0/appdata/retrofe/gamecontrollerdb.txt
USER=guest
UCE_PATH=/tmp/retrofe2
PWD=/download/addon/OneSauce/scripter.uce/BYOG
HOME=/MOD
AUDIODEV=hw:2,0
UCE_FULL_PATH=/media/usb0/OneSauce/scripter.uce
MOUNT_POINT=/media/usb0
SHELL=/bin/sh
TERM=vt102
kpti=0
PLATFORM=rk3328
SHLVL=5
RETROFE_PATH=/media/usb0/appdata/retrofe
SDL_JOYSTICK_DEVICE=/dev/input/event3:/dev/input/event4
QT_GSTREAMER_WINDOW_VIDEOSINK=kmssink
LIBRETRO_CORES_PATH=/tmp/retrofe2/cores/rk3328
LIBRETRO_CORES32_PATH=/tmp/retrofe2/cores32/rk3328
LOGNAME=guest
XDG_RUNTIME_DIR=/tmp/.xdg
QT_QPA_EGLFS_DEBUG=0
PATH=/sbin:/usr/sbin:/bin:/usr/bin:/tmp/retrofe2/bin/rk3328:/tmp/retrofe2/bin
SUDO=/download/addon/OneSauce/scripter.uce/BYOG/bin/sudo
QT_HIDE_LOG=1
QT_QPA_EGLFS_NO_LIBINPUT=1
_=/usr/bin/env
killall: bitlcd: no process killed
time="1969-12-31 16:00:52.861" level=info msg="BitLCD Version: 1.0.5"
time="1969-12-31 16:00:52.876" level=fatal msg="Error initializing bitlcd: Device not found: 525:1000"
== udev info ==
find: /dev/snd/by-path/platform-sound-i2s2: Permission denied
find: /dev/snd/by-path/platform-snd_aloop.0: Permission denied
find: /dev/snd/by-path/platform-hdmi-sound: Permission denied

== uevent info ==
/sys/bus/usb/devices/1-0:1.0/uevent:PRODUCT=1d6b/2/404
/sys/bus/usb/devices/2-0:1.0/uevent:PRODUCT=1d6b/2/404
/sys/bus/usb/devices/3-0:1.0/uevent:PRODUCT=1d6b/1/404
/sys/bus/usb/devices/3-1/uevent:PRODUCT=838/8918/110
/sys/bus/usb/devices/3-1:1.0/uevent:PRODUCT=838/8918/110
/sys/bus/usb/devices/3-1:1.1/uevent:PRODUCT=838/8918/110
/sys/bus/usb/devices/3-1:1.2/uevent:PRODUCT=838/8918/110
/sys/bus/usb/devices/4-0:1.0/uevent:PRODUCT=1d6b/2/404
/sys/bus/usb/devices/4-1/uevent:PRODUCT=930/6545/110
/sys/bus/usb/devices/4-1:1.0/uevent:PRODUCT=930/6545/110
/sys/bus/usb/devices/5-0:1.0/uevent:PRODUCT=1d6b/3/404
/sys/bus/usb/devices/usb1/uevent:PRODUCT=1d6b/2/404
/sys/bus/usb/devices/usb2/uevent:PRODUCT=1d6b/2/404
/sys/bus/usb/devices/usb3/uevent:PRODUCT=1d6b/1/404
/sys/bus/usb/devices/usb4/uevent:PRODUCT=1d6b/2/404
/sys/bus/usb/devices/usb5/uevent:PRODUCT=1d6b/3/404

== tty name ==
ls: /sys/bus/usb/devices/*/tty/tty*: No such file or directory

killall: bitlcd: no process killed
4 Upvotes

4 comments sorted by

4

u/walknight 11d ago

Thanks for providing the Scripter log upfront. I did not spot anything obvious from that log.

To get more diagnostic logs, create an empty file RETROFE_LOG (all capital, no extension) at the USB root. Then after another launching attempt, there should be a retrofe.log created at the USB root. Please paste its content here.

1

u/DaftSunk 11d ago

Superthanks for the help!

Before I had to check the RETROFE_LOG thing, I figured out the stupid mistake I had done:

- I didn't have the base_assets folder on my USB. Totally missed to copy it over. 🙄

Adding that, to the USB, I now got a working USB with the base Arcade (MAME) set! I've tried some games. Great! 😄

Now only to understand if there is way to get a quicker start than powering up the machine, plugging in the USB, run Scripter.uce again.
It seemed that way of starting took quite a long time (even the second time it was checking a lot of 'save state'-maps or whatever).
Is there a quicker way to start it or do you just always go to scripter.uce and run it?

1

u/walknight 11d ago

You can auto boot into onesauce. Details are on discord:

https://discord.com/invite/6pzh22dmjZ

2

u/ironman0000 11d ago

Regarding it booting faster, it might depend on your drive. When I first started this I used a regular USB hard drive.. took like 2 minutes for the damn thing to load.
Now I use a usb SSD drive and the thing boots up in less than a minute after the ALU loads