Closed thefunkdoctor closed 1 year ago
It will be nearly impossible to help without logs
i recently picked up a radxa zero 2gb version it works flawlessly with emuelec 4.4 and 4.5 while the 1gb version freezes on those versions, so perhaps its just the lack of ram
i recently picked up a radxa zero 2gb version it works flawlessly with emuelec 4.4 and 4.5 while the 1gb version freezes on those versions, so perhaps its just the lack of ram
1GB might not be enough for 1080p on 3D emulators. But another thing to consider would be heat?
both units i tested had heatsinks
they also never went above 66 degrees in desktop testing so i dont imagine they would overheat emulating. Seeing as my 1gb model will run all day on emuelec 4.3 ive even let it play through a few anime episodes on the media player no problem
Then no idea, sorry. I do not have a 1gb device to test this, nor do you provide any type of logs.
You need to provide emuelec.log which is the one that is catching the issues for games, not the ES log. or you can use the setup menu to gather the logs and send the url.
is this correct
Apr 29 06:51:42 EMUELEC systemd[1]: Finished Wait for Kernel Time Synchronisation.
Apr 29 06:51:42 EMUELEC systemd[1]: Reached target System Time Synchronized.
Apr 29 06:51:42 EMUELEC systemd[1]: Started Discard unused blocks once a week.
Apr 29 06:51:42 EMUELEC systemd[1]: Reached target Timer Units.
Apr 29 06:51:42 EMUELEC systemd[1]: Startup finished in 3.955s (kernel) + 16.291s (userspace) = 20.247s.
Apr 29 06:51:42 EMUELEC nmbd[3443]: [2022/04/29 06:51:42.966508, 0] ../../lib/util/become_daemon.c:135(daemon_ready)
Apr 29 06:51:42 EMUELEC nmbd[3443]: daemon_ready: daemon 'nmbd' finished starting up and ready to serve connections
Apr 29 06:51:42 EMUELEC nmbd[3443]: [2022/04/29 06:51:42.990728, 0] ../../source3/nmbd/nmbd_namequery.c:109(query_name_response)
Apr 29 06:51:42 EMUELEC nmbd[3443]: query_name_response: Multiple (2) responses received for a query on subnet 192.168.0.28 for name WORKGROUP<1d>.
Apr 29 06:51:42 EMUELEC nmbd[3443]: This response was from IP 192.168.0.10, reporting an IP address of 192.168.0.10.
Apr 29 06:51:43 EMUELEC python[4004]: Traceback (most recent call last):
Apr 29 06:51:43 EMUELEC python[4004]: File "/usr/lib/python3.9/site-packages/dbus/bus.py", line 177, in activate_name_owner
Apr 29 06:51:43 EMUELEC python[4004]: File "/usr/lib/python3.9/site-packages/dbus/bus.py", line 361, in get_name_owner
Apr 29 06:51:43 EMUELEC python[4004]: File "/usr/lib/python3.9/site-packages/dbus/connection.py", line 652, in call_blocking
Apr 29 06:51:43 EMUELEC python[4004]: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get owner of name 'org.bluez': no such name
Apr 29 06:51:43 EMUELEC python[4004]: During handling of the above exception, another exception occurred:
Apr 29 06:51:43 EMUELEC python[4004]: Traceback (most recent call last):
Apr 29 06:51:43 EMUELEC python[4004]: File "/usr/bin/batocera/batocera-bluetooth-agent", line 446, in
this was a log today on a fresh sd card
i select a psp game and then it freezes when attempting to start
the file we usually need with emulator crashing issues is in /emuelec/logs/emuelec.log . Anyway this issue may be outdated as it's for 4.4, If it's still an issue open up another thread.
I have had no issues running 4.3 for awhile on my radxa zero 1gb
Attempted a fresh 4.4 install and everything seems to work the same except games wont load
specifically psp/n64/saturn or any 3d game seems to freeza the console once its about to load in game
i can usually start the game, get through the menus
but once i go to choose a level it freezes mid loading
i wonder if it is somehow related to saving issue as im getting alot of corrupted save data
any help is appreciated