You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have just tried to run gilbraltar with the latest qemu, which now has a raspi4b machine and it hung without any output. I tried this on a 4.14.1 switch, as well as 5.1.1 with --update-invariant. In both cases the img was generated successfully.
Do you have any suggestions of how I can move forward with fixing this? Yeah, I know, you did all of this work quite a long time ago! Still, if you can think of anything off the top of your head then it would be pretty useful.
Cheers
Nick
The text was updated successfully, but these errors were encountered:
Hi @nickbetteridge, currently we only support OCaml 4.14 and I'm waiting that ocaml-solo5 is upgrade to OCaml 5 to do the same into gilbraltar. I just bought a Raspberry Pi 5 and I will try to play with it as soon as I receive it. Thanks to try to play on it, I'm currently not full about works but I have some pending PR on my side but I suspect that I will be able to relook on it in August and try to fix.
More generally, a few options should be necessary to launch the system with qemu because, at present, a modification of cmdline.txt (read by the raspberry Pi firmware) is also necessary. In this case, booting in "old" mode is explicitly requested, so perhaps (surely) it's necessary to specify this for qemu too.
Hi @dinosaure - thanks for the feedback! I'm certainly looking forward to the ocaml-solo5 with ocaml 5.2 release and getting gilbraltar to work - I'm interested to see how well picos+lwt works. I'll take a look at cmdline.txt and see if this is the issue that led to qemu not working. This is an excellent repo for mirage baremetal - thanks for all of the obvious hard work that went into it!
Greetings!
I have just tried to run gilbraltar with the latest qemu, which now has a
raspi4b
machine and it hung without any output. I tried this on a 4.14.1 switch, as well as 5.1.1 with --update-invariant. In both cases the img was generated successfully.Do you have any suggestions of how I can move forward with fixing this? Yeah, I know, you did all of this work quite a long time ago! Still, if you can think of anything off the top of your head then it would be pretty useful.
Cheers
Nick
The text was updated successfully, but these errors were encountered: