DEFAULT /boot/vmlinuz initrd=/boot/core.gz loglevel=3 cde vga=895 logo.nologo=1 console=/dev/null
Now splash screen is modify successfully. But the effect is not perfect.There are something else in splash screen.[code][ 36.176529] pcm512x 1-004d: Failed to get supply 'AVDD': -517
[ 36.176536] pcm512x 1-004d: Failed to get supplies: -517
[ 36.191753] pcm512x 1-004d: Failed to get supply 'AVDD': -517[/code]
[ 36.176529] pcm512x 1-004d: Failed to get supply 'AVDD': -517
[ 36.176536] pcm512x 1-004d: Failed to get supplies: -517
[ 36.191753] pcm512x 1-004d: Failed to get supply 'AVDD': -517
...I can see you did not use the tc-install application I recommended. That application would never have addedCode: [Select]DEFAULT /boot/vmlinuz initrd=/boot/core.gz loglevel=3 cde vga=895 logo.nologo=1 console=/dev/null
...
... But the effect is not perfect.There are something else in splash screen. ...Well, we have a few choices here:
Console 0
it might suppress some of those syslinux messages.Loading /boot/vmlinuz......
Loading /boot/core-e.gz..................ready
are disappeared,but thisStart booting from USB device..
SYSLINUX 4.07 EDD 2013-07-25 Copyright (C) 1994-2013 H. Peter Anvin et al
are still exist2. No attachments/links of binary extensionsFound here:
... I found that the picture is not displayed every time, and sometimes it is only a black screen.Since you are booting from a USB device, add a waitusb boot code:
loglevel=3 cde vga=895 logo.nologo=1 console=/dev/null waitusb=5
and see if that helps.... I try to solve the problem of image gets shifted first. Let me know if you have any ideas, thanks.If you are booting using a VM, Hypervisor, or some other intermediary, see if booting on bare metal helps.
If you are booting using a VM, Hypervisor, or some other intermediary, see if booting on bare metal helps.I'm currently testing on bare metal(my old pc).
... I found that the picture is not displayed every time, and sometimes it is only a black screen.To solve this problem, I deleted
console=/dev/null
and the log display fb0 No such file or directory
Because sometimes fb0 does not complete initialization.Then I put the code in tc-config file after "$WAITUSB" about line 126. It can show logo everytime.
... To solve this problem, I deleted ...
... Because sometimes fb0 does not complete initialization. ...
...Where did you get that value of 895 for the vga code from? Try one of the values listed here (maybe 795):Code: [Select]loglevel=3 cde vga=895 logo.nologo=1 console=/dev/null waitusb=5
...
vga=ask
to get the 895,and it's 1920*1080 resolution. I will try 795 later.loglevel=3 cde vga=786 logo.nologo=1 waitusb=5
Startup log still showing fb0 No such file or directory