ARpiCADE_5 - for Pi4 or Pi5

[cool_factor]

I found a ver 5 build that I hadnt reformatted yet. Im running paragon version 5 (theres apparently a vers 7 now). Black screen, wont boot at cabinet. Bring back to PC and leave unmounted and use verify function of paragon and get this. May or may not help but I figured Id post it.

Untitled.png (34.88 KiB) Viewed 2904 times

[cool_factor]

Heres the log when trying to let paragon fix it (appologize in advance if its useless info):

Error writing block 285 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 301 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 286 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 302 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 287 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 303 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 288 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 304 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 289 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 305 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 290 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 306 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 291 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 307 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 292 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 308 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 293 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 309 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 294 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 295 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 296 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 297 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 298 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 299 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 300 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 524288 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 524304 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 524289 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 524305 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 524290 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 524306 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 524291 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 524307 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 524292 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 524308 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 524293 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 524309 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 524294 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 524310 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 524295 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 524311 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 524296 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 524312 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 524297 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 524313 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 524298 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 524299 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 524315 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 524300 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 524316 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 524301 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 524302 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 524303 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 1048576 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 1048580 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 1048577 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 1048581 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 1048578 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 1048579 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 1048583 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 1058791 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 1058792 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 1059298 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 1059805 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 1060312 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 1060313 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 1060819 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 1060820 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 1061326 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 1061833 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 1062340 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 1062847 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 1063354 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 1063861 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 1064368 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 1572864 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 1572865 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 1572866 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 1572867 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 1572868 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 1572869 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 1572870 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 1572871 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 1588189 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 1588191 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 1587575 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 2097152 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 2097154 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 2097155 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 2097156 (Read-only file system) while writing block and inode bitmaps. Ignore error? yes

Error writing block 2097157 (Read-only file system). Ignore error? yes

Error writing block 2097158 (Read-only file system). Ignore error? yes

Error writing block 2097159 (Read-only file system). Ignore error? yes

Error writing block 2097164 (Read-only file system). Ignore error? yes

Error writing block 2097162 (Read-only file system). Ignore error? yes

Error writing block 1 (Read-only file system). Ignore error? yes

Error writing block 2097160 (Read-only file system). Ignore error? yes

Error writing block 2097161 (Read-only file system). Ignore error? yes

Error writing block 2097163 (Read-only file system). Ignore error? yes

Error writing block 1 (Read-only file system). Ignore error? yes


ARpiCADE_5: ***** FILE SYSTEM WAS MODIFIED *****
ARpiCADE_5: 156580/622160 files (0.3% non-contiguous), 1929509/2514944 blocks
Error writing block 1 (Read-only file system). Ignore error? yes



exit_code = 1

[dee2eR]

These days I only really have to get in to the linux side to add ROMLISTS. Well, 90% of the time it's that. If you could move the ROMLISTS folder to the Windows side... perhaps I could test with Paragon not running at all...

I can probably do that, however it may make editing the individual roms in the lists from inside Attract-Mode no longer possible (unless attract is run with sudo).

I'm curious though, what is the difference between your rom lists and the ones generated by the rom scanner? There shouldn't be much need to manually write romlists.

[dee2eR]

Heres the log when trying to let paragon fix it (appologize in advance if its useless info):
*much info*

I don't understand the log unfortunately. It is probably a list of blocks that it has modified or something. The real question is did it boot afterward or was it still borked?

[FrizzleFried]

These days I only really have to get in to the linux side to add ROMLISTS. Well, 90% of the time it's that. If you could move the ROMLISTS folder to the Windows side... perhaps I could test with Paragon not running at all...

I can probably do that, however it may make editing the individual roms in the lists from inside Attract-Mode no longer possible (unless attract is run with sudo).

I'm curious though, what is the difference between your rom lists and the ones generated by the rom scanner? There shouldn't be much need to manually write romlists.

My romlists contain multiple emulators in one list... i don't think your scanner does that? Or how about the ideas I had about making a 60-in-1, Bitkit, etc list? Or just Shumups... can you generate lists by category from within the system?

[dee2eR]

EDIT: I just looked at the Opacity code and I can't see WHY the 'shadow' breaks. I simply removed it. Is V5 running a newer version of Attract Mode? Should I bother going to the AM website to determine why it breaks the shadow and if it can be fixed?

Yeah, it would be a probably be newer version, ARpiCADE_5 is using Attract-Mode 2.7.0 (I don't know offhand what version older ARpiCADES have). Also all the supporting libs etc would be newer. And we're rendering in a different way than in previous ARpiCADE versions - ARpiCADE_5 is using Wayland, previous versions were direct to frame buffer on the console. It's possible any of that could also be the cause of the shadow rendering issue you're seeing.

[dee2eR]

My romlists contain multiple emulators in one list... i don't think your scanner does that? Or how about the ideas I had about making a 60-in-1, Bitkit, etc list? Or just Shumups... can you generate lists by category from within the system?

Ah, yes you mentioned that, my bad. The arpicade romscanner only combines various emulators into arcade games only, consoles only and all games but doesn't have any handling for custom categories...

I'll experiment with simlinks to the boot partition for romlists, it's probably do-able. Failing that I could add a service menu option to copy in custom romlists from the boot partition - actually that may be the better way if it works for you, would stop any issues caused by the 'pi' user not owning /boot/

[FrizzleFried]

I'm OK with whatever works... easiest... for you... for us.

[FrizzleFried]

Of course, when you remove the error screens ... please consider compiling high score saving back in... there is a different formatted highscore.dat file it seems...

https://highscore.mameworld.info/download.htm

This one covers .174 and higher.

[dee2eR]

Looking at that highscore dat readme it seems like MAME doesn't need to be recompiled for hiscore support anymore. Just need to add the datfile and activate it in plugins.ini

I'll actually try it on the weekend. Maybe I'm wrong.