Ah ... The UEFI branch has been removed from SolidRun's github.
Out of sheer luck I seemed to have unintentionally downloaded the UEFI branch(lsdk-19.09-sr-uefi) when it was still available back in January. (I don't know the exact date when they removed it)
I was reading somewhere that they might re-release a UEFI branch in a few weeks time.
Having said that, I was shocked when the UEFI build generated an image straight away and the generated image booted into GRUB menu right away. My problems happen after this point.
As mentioned in this article, I only built the boot image using that UEFI branch. The complete/linux build fails on the UEFI branch I have.
I found another user on github who had actually cloned that repo and still had the uefi branch in it, so that's a thing I tried, but the final image didn't seem to do anything. Liz's image boots, but I get memory errors trying to boot any kernel, which I'm thinking has to do with the ram speed that image was built for not matching mine (operating under an u-boot image I built myself is fine). I've spent the last few days hacking my way through the runme script and pulling different branches of things to mixed results, both in and out of docker. Closest I got on the master branch was a 20.04 UEFI loader that starts to boot up and then panics.
Anyway I'm still trying. Lol. I saw on Jon's Twitter new features coming down in it, so it has to be working somewhere.
So if I understood the directions correctly, if you have managed to get your hands on a brach with UEFI in it, you use that branch to build the BOOTLOADER_ONLY image.
This can be done by either setting the parameter BOOTLOADER_ONLY inside the runme.sh script or passed as a parameter: BOOTLOADER_ONLY=yes ./runme.sh
You will also need to set the DDR_SPEED.
The purpose of this image is only to boot the system with UEFI and not provide a working userspace filesystem (which is the default settings that uses u-boot)
If the image generation goes through, you should be able to boot the board into UEFI shell at the very least.
If you have a ubuntu-server.iso on a USB, it should take you upto the grub2 boot menu. where you chose to install/try ubuntu-server.
I probably should have chimed in that I found out what's going on.
The UEFI image here (which I've found out does work and I'm just having some weird kernel problems) is being passed around by the community at the moment while they get the new branch ready. There's a Discord chat you can get invited to if you reach out to SolidRun's support. Images built with the old UEFI branch don't work with the rev2 board. Currently I can get Fedora to boot on it and working on getting Debian Bullseye to boot.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Ah ... The UEFI branch has been removed from SolidRun's github.
Out of sheer luck I seemed to have unintentionally downloaded the UEFI branch(lsdk-19.09-sr-uefi) when it was still available back in January. (I don't know the exact date when they removed it)
I was reading somewhere that they might re-release a UEFI branch in a few weeks time.
Having said that, I was shocked when the UEFI build generated an image straight away and the generated image booted into GRUB menu right away. My problems happen after this point.
As mentioned in this article, I only built the boot image using that UEFI branch. The complete/linux build fails on the UEFI branch I have.
I am not sure if this helps.
What issues are you facing by the way ?
I found another user on github who had actually cloned that repo and still had the uefi branch in it, so that's a thing I tried, but the final image didn't seem to do anything. Liz's image boots, but I get memory errors trying to boot any kernel, which I'm thinking has to do with the ram speed that image was built for not matching mine (operating under an u-boot image I built myself is fine). I've spent the last few days hacking my way through the runme script and pulling different branches of things to mixed results, both in and out of docker. Closest I got on the master branch was a 20.04 UEFI loader that starts to boot up and then panics.
Anyway I'm still trying. Lol. I saw on Jon's Twitter new features coming down in it, so it has to be working somewhere.
Actually this must be why:
SoC: LX2160ACE Rev2.0 (0x87360020)
I notice in the latest runme.sh it implies that 19.09 is only for rev1. The image provided here is for 20.04 though, so still very curious.
So if I understood the directions correctly, if you have managed to get your hands on a brach with UEFI in it, you use that branch to build the BOOTLOADER_ONLY image.
This can be done by either setting the parameter BOOTLOADER_ONLY inside the runme.sh script or passed as a parameter: BOOTLOADER_ONLY=yes ./runme.sh
You will also need to set the DDR_SPEED.
The purpose of this image is only to boot the system with UEFI and not provide a working userspace filesystem (which is the default settings that uses u-boot)
If the image generation goes through, you should be able to boot the board into UEFI shell at the very least.
If you have a ubuntu-server.iso on a USB, it should take you upto the grub2 boot menu. where you chose to install/try ubuntu-server.
I probably should have chimed in that I found out what's going on.
The UEFI image here (which I've found out does work and I'm just having some weird kernel problems) is being passed around by the community at the moment while they get the new branch ready. There's a Discord chat you can get invited to if you reach out to SolidRun's support. Images built with the old UEFI branch don't work with the rev2 board. Currently I can get Fedora to boot on it and working on getting Debian Bullseye to boot.