[4.1-stable] FAQ

[voljega]

@Substring @rockaddicted @acris

Hello I updated arcade documentation on the wiki for 4.1 final but there are a few links wich I don't know how to update, between github wiki and the moving of the code to gitlab where I can't find anymore the recalbox-buildroot project.

How to update the following links for FBA 0.2.97.139 ?
https://raw.githubusercontent.com/recalbox/recalbox-buildroot/rb-4.0.X/board/recalbox/fsoverlay/recalbox/share_init/roms/fba_libretro/fba_libretro_gamelist.txt
https://raw.githubusercontent.com/recalbox/recalbox-buildroot/rb-4.0.X/board/recalbox/fsoverlay/recalbox/share_init/roms/fba_libretro/fba_0.2.97.37.dat

[Substring]

@voljega said in [4.1-stable] FAQ:

fba_libretro_gamelist.txt

https://gitlab.com/recalbox/recalbox/blob/master/package/recalbox-romfs/recalbox-romfs-fba_libretro/roms/fba_libretro/clrmamepro/fba_libretro_gamelist.txt

fba_0.2.97.37.dat

https://gitlab.com/recalbox/recalbox/blob/master/package/recalbox-romfs/recalbox-romfs-fba_libretro/roms/fba_libretro/clrmamepro/FB Alpha v0.2.97.39.dat

[voljega]

@substring thanks !

[paradadf]

@voljega you posted links of the 4.0.X branch... aren‘t those files already up to date on gitlab and the 4.1 branch on github? Or has something changed?

[voljega]

@paradadf the links I posted here were the one used before (from github) and I wanted to update them for 4.1 and so @Substring gave me corresponding the giblab links

As far as I know, the project code completely moved to Gitlab and isn't maintened on Github anymore ?

[Substring]

@voljega someday we may setup the sync from gitlab to github, but that's not a priority. For everything that is code related, it moved to gitlab, yes

[Matra]

I'm guessing that the MD5 tag in the manager for the dc_flash.bin will be updated at some point?

It asks for dc_flash.bin MD5: d6e11a23f1fa01cddb5dfccf7e4cc8d7
but this post states
0a93f7940c455905bea6e392dfde92a4 dc_flash.bin

I can't find the former but I do have the latter. When upgrading it doesn't show the dc bios MD5 in the online manager but gave them a tick (tried uploading a 'bad' bios and it still gave that a tick too!).

I had originally uploaded
dc_boot.bin MD5: d552d8b577faa079e580659cd3517f86
dc_flash.bin MD5: 74e3f69c2bb92bc1fc5d9a53dcf6ffe2
which seemed to work ok but maybe this is why I'm getting the occasional DC related bug???

[Substring]

@matra can't tell ... What I know at least is that the DC emulation is far from being perfect

[paradadf]

@voljega please, read my questions again. I personally updated those files on the 4.1 branch in github, so there is no need to update them as for my understanding. The links you posted are from the 4.0.X branch, thus outdated.

[voljega]

@paradadf well the links came from the wiki arcade doc and those were clearly obsolete

[Substring]

@paradadf that's why i gave him the right links so that he can update the wiki

[paradadf]

@voljega @Substring my bad, I understood it the wrong way! Sorry guys!

[gmgman]

I'm sorry if this night sound dump, but I'm trying to install recalbox on pc. I burnt the recalbox image onto a 4gb usb stick, but how do I start it in Windows?

[Substring]

@gmgman the USB key a an OS itself, you must boot on it ! And 4GB is too small you need 8 GB at least

[Javier Sandoval]

@gmgman said in [4.1-stable] FAQ:

I'm sorry if this night sound dump, but I'm trying to install recalbox on pc. I burnt the recalbox image onto a 4gb usb stick, but how do I start it in Windows?

Most old computers have an option to boot when your start the computer, like pres f9 or press f12 for boot menu, there you can choose your usb key and if you did it right it will bot the usb key, on newer computers its diferent, you can also go into bios and look for boot optios and set your usb key there as your first boot option, and allthoug 4gb its not much, you should be able to test recalbox ok, i did that in my computer and it worked fine, then i installed into the hardrive.

[RK.aus.S]

Hi there

Not sure if this belongs in this thread, but contrary to the compatibility list for Wifi dongles; the TP-Link TL-WN822N Ver. 4.0 is not working at all (at least on my RPi3, see details in my thread in the Troubleshooting Forum). I got other Wifi dongles running without any problems, therefore I think I did setup my Recalbox correctly (blacklisting on-board adapter).

Is this something you take care of it at all? (Means, can I hope that it could be solved?)
How can I support you to get this issue solved?

Kind regards
Roman

[rockaddicted]

@rk-aus-s hello this kind of dongle have often different subversion with different chipset.... So v1 can work and v2 don't.
I think I have one of this dongle in my apartment. I'll test that if I have a moment.

[RK.aus.S]

@rockaddicted Thanks a lot. My Version is v4 - so it seams to be the newest release of this adapter. If you need some logs - I would send you every log you want!

[rockaddicted]

@rk-aus-s So I done a quick search and the realtek chipset inside this dongle needs a custom driver until kernel v4.7.
We are actually on kernel v4.4.13, so you will have retry after a technical upgrade of recalbox in the next weeks.

[RK.aus.S]

@rockaddicted Thank you very much for this fast and competently answer.