Jason Black

ok, I'm a dumbass, I just realized 5.0.0 rc1 was the kernel release. Not shocking it doesn't work. Gonna rebuild with a 4.1.x release. I'm betting that works better.

Every build, regardless of release says it's dirty. my local git is clean and committed. I'm guessing the kernel source the build process pulls from has some uncommitted work. Does anyone know which repo the build process pulls from?

I just attempted several builds of Build-Armbian, 5.67 bionic 5.0 rc1 with S9xxx board. None of them will boot. It's almost like it's not reading the DTB right. It just sits at the MXQPro logo screen. I've edited to extlinux.conf and the uEnv.ini and even created a dtb.img but it doesn't seem to make a difference. I've used this same dtb with builds produced by balbes150 and it worked fine. I'm a noob, but I'm not just trying to get this running. I plan to contribute to the project if possible. I was a software engineer in a past life. Any hints in the right direction would be much appreciated. For instance, is there a way to see the boot console so I can see i there is an error on boot attempt? Thanks in Advance. Jason Black

I just attempted several builds of Build-Armbian, 5.67 bionic 5.0 rc1 with S9xxx board. None of them will boot. It's almost like it's not reading the DTB right. It just sits at the MXQPro logo screen. I've edited to extlinux.conf and the uEnv.ini and even created a dtb.img but it doesn't seem to make a difference. I've used this same dtb with builds produced by @balbes150 and it worked fine. @Igor any ideas? I'm a noob, but I'm not just trying to get this running. I plan to contribute to the project if possible. I was a software engineer in a past life. Any hints in the right direction would be much appreciated. For instance, is there a way to see the boot console so I can see i there is an error on boot attempt? Thanks in Advance. Jason Black