MicroSD Retropie On
-
@mitu
Doubly doubted, on another sdcard the reicast source is not built correctly and the binaries are corrupted. -
@Efriim Can you post the compilation log, from
$HOME/RetroPie-Setup/logs
, on pastebin.com ? -
@mitu
Good idea. I didn't know where to look for the log. I had packed up my things but it is a good thing I decided to unpack because I forgot my powersupply.500kb limit
https://pastebin.com/Br5fJtec part1 lines 1-500
https://pastebin.com/gJSZWPaJ part2 501-xxline 405: part1
/home/pi/RetroPie-Setup/tmp/build/reicast/shell/linux/../../core/deps/libelf/elf32.cpp:137:10: warning: ISO C++ forbids converting a string constant to ‘char*’ [-Wwrite-strings] return "<corrupted>";
Actual errors when running reicast.
./reicast.sh ./reicast.sh: line 88: 3320 Trace/breakpoint trap "$rootdir/emulators/reicast/bin/reicast" "${params[@]}" > /dev/null ./reicast Config dir is: /home/pi/.reicast/ Data dir is: /home/pi/.reicast/ Personality: 00C00000 Updated personality: 00800000 found libbcm_host rpi2: bcm_init ARM VFP-Run Fast (NFP) enabled ! Linux paging: 4096 00001000 00000FFF MAP 00800000 w/ 25165824 MAP 20000000 w/ 25165824 MAP 04000000 w/ 16777216 MAP 06000000 w/ 16777216 MAP 0C000000 w/ 0 vmem reserve: base: 539F0000, aram: 739f0000, vram: 579F0000, ram: 5F9F0000 Mem alloc successful! EGL config: 0x1, 0x1, 0x1 640x480 SIGSEGV @ 0 -> (nil) was not in vram, dynacode:0 Fatal error : segfault in fault_handler -> /home/pi/RetroPie-Setup/tmp/build/reicast/shell/linux/../../core/linux/common.cpp : 107 Trace/breakpoint trap
line 601, part2: l100
is the only instance of ../core/linux/common.cpp -
That error doesn't mean that the binary is 'corrupted', it's just that it's crashing due to other circumstances.
-
-
@Efriim said in MicroSD Retropie On:
405 mean that elf32.cc is corrupt
No, that's a compilation warning - not an error - for the following line from the source code.
-
Reicast source is still not working in retropie packages.
And here is safe shutdown script for retroflag cases and more, https://github.com/crcerror/retroflag-picase
Install safeshutdown:
wget -O - "https://raw.githubusercontent.com/crcerror/retroflag-picase/master/install.sh" | sudo bash
And some extra scriptmodule packages
Exult - Ultima VII
wget -O ~/RetroPie-Setup/scriptmodules/ports/exult.sh - "https://raw.githubusercontent.com/amigagamer/ExultRetropie/master/exult.sh"
Extra scripts
https://github.com/zerojay/RetroPie-Extra -
@Efriim said in MicroSD Retropie On:
Reicast source is still not working in retropie packages.
I'll give it a shot later to see how it works - does the binary work ? Is there any specific game you tried ?
-
@mitu
The binary works fine. I hear that the reicast source was updated is why I wanted to build the latest. -
OK, so when installing from source, I get the same crash, so something must have been changed upstream. I'll try to get a bisect working.
-
Seems like an upstream issue, which is solved, but not yet merged - https://github.com/RetroPie/RetroPie-Setup/issues/2700 (leading to the a bug report on the Reicast repo - https://github.com/reicast/reicast-emulator/issues/1537).
Bisecting the issue points to an older commit (a808a8f3).
-
@mitu
Yeah it looks like I had problems installing the source a few months ago too.I had a couple questions. In my fstab
UUID=1A92-F7C1 /home/pi/RetroPie/memorycard vfat defaults,noatime,users,rw,uid=pi,gid=pi 0 0
I thought this would mount on availability, do you know what options are added, for automount and so that it wont hang a startup process during boot for 180 seconds, when the usb is unplugged?
My other question, I don't know probably couldn't answer, on my last retropie installation, I had a startup time of around 15 seconds. I think i have done everything that I did on my last installation but I can still only get 18 seconds. Any ideas?
-
I had a couple questions. In my fstab
UUID=1A92-F7C1 /home/pi/RetroPie/memorycard vfat defaults,noatime,users,rw,uid=pi,gid=pi 0 0
I thought this would mount on availability, do you know what options are added, for automount and so that it wont hang a startup process during boot for 180 seconds, when the usb is unplugged?
Automount is handled by the
usbautomount
service. If you don't have the disk permanently attached, then it's best to use theusbautomount
service.My other question, I don't know probably couldn't answer, on my last retropie installation, I had a startup time of around 15 seconds. I think i have done everything that I did on my last installation but I can still only get 18 seconds. Any ideas?
Startup times can be diagnosed with
systemd-analyze
- look into it to determine where the system spends it's time. -
The disk I plan on leaving attached. I'll look into options for mount; is option "nofail" supposed to mean that it will give up trying to mount if it is non-available?
systemd-analyze blame
the top four are nmbd.service 10.8s and hciuart.service 6.4s
then raspi-config.service 1.3s and smbd.service 1sone is the net bios name server i was pretty sure I dont use that so i disabled it with
sudo systemctl stop nmbd
sudo systemctl disable nmbd
I do use bluetooth, It seems like it is unusually slow. Reading dmesg:
uart-pl011 3f201000.serial: no DMA platform data
brcmfmac: power management disabled
and brcmfmac: brcmf_c_preinit_dcmds; look like firmware warningsraspi-config is probably nominal, though I don't know what it is calling or doing at startup.
I use samba smbd.service.
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.