debian-mini-odroid-c1 icon indicating copy to clipboard operation
debian-mini-odroid-c1 copied to clipboard

Screen black out during boot up

Open mislam opened this issue 10 years ago • 5 comments

I have noticed the framebuffer init script is forwarding the output to the display after kernel file system in mounted. That is why the screen remains black (empty) during boot up until the login prompt pops up. Just like every other Linux OS, how can I display the console output to the monitor while booting?

mislam avatar Mar 13 '15 03:03 mislam

I believe hardkernel's official distros also have this limitation. I don't know of a way to enable it earlier in the boot process.

tomuta avatar Mar 13 '15 14:03 tomuta

Hi

So I played a bit around with my patch. I can usually see the kernel messages. However I tried upgrading to Debian Jessie. The normal upgrade works quiet fine. However after I have regenerated the initrd and the corresponding uInitrd, the screen stays blank during boot, I see no kernel messages or initrd messages at all. I have no idea what is going wrong there. Is there maybe something in the Jessie initrd that requires a newer kernel than 3.10? Booting Debian Jessie with the old initrd works find and I did not see any problems with systemd or related stuff so far.

Did someone manage to get Debian Jessie running using this script?

eriktews avatar Apr 09 '15 10:04 eriktews

I had issues building a Jessie image as it was unable to mount the root file system. I was able to use a serial console to see that and changed the fstab file from using UUID to the /dev/mmcblk nomenclature, but I haven't taken the time to determine what the root of the problem is yet.

Robert

On Thursday, April 9, 2015, Erik Tews [email protected] wrote:

Hi

So I played a bit around with my patch. I can usually see the kernel messages. However I tried upgrading to Debian Jessie. The normal upgrade works quiet fine. However after I have regenerated the initrd and the corresponding uInitrd, the screen stays blank during boot, I see no kernel messages or initrd messages at all. I have no idea what is going wrong there. Is there maybe something in the Jessie initrd that requires a newer kernel than 3.10? Booting Debian Jessie with the old initrd works find and I did not see any problems with systemd or related stuff so far.

Did someone manage to get Debian Jessie running using this script?

— Reply to this email directly or view it on GitHub https://github.com/tomuta/debian-mini-odroid-c1/issues/15#issuecomment-91180712 .

n5qm avatar Apr 09 '15 12:04 n5qm

So using my patch, do you get a screen output of the problem, or do you just see the problem on the serial line?

eriktews avatar Apr 09 '15 13:04 eriktews

I am getting the boot output on hdmi with your patch, which is why I merged your pull request. Thanks! I haven't tried jessie yet, but I suspect it has to do with the fact that jessie is using systemd, so the init scripts that are normally run would not work. However, I don't think this explains why it can't boot using the uuid.

tomuta avatar Apr 09 '15 18:04 tomuta