In general, I don't add any earlyprink kernel parameter at boot.
A few years ago, playing with a laptop, I was forced to add 'earlyprintk=vga' to debug eventual bootstrap problems. Without that, I only had "loading kernel, loading initrd" and then a black screen, say until OpenRC starts.
Now I am running in the same issue with a desktop.
So, the question is, why sometimes I must explicitly add that parameter, while in other cases I don't?
Can anyone help me understand?
Regards,
HUjuice
earlyprintk, is it necessay?
Message
earlyprintk, is it necessay?
Those who lack character must at least have a method.
Chi non ha carattere, deve pur avere un metodo.
Chi non ha carattere, deve pur avere un metodo.
- NeddySeagoon
- Administrator
- Posts: 56089
- Joined: Sat Jul 05, 2003 9:37 am
- Location: 56N 3W
hujuice,
There is also a default setting of earlyprintkernel in the kernel configuration.
The command line option overrides that default.
Nothing on the console from the kernel is usually one of two things.
1. No console driver configured in the kerlel
2. A broken drm framebuffer, often because it needs fimware and the firmware is missing.
There is also a default setting of earlyprintkernel in the kernel configuration.
The command line option overrides that default.
Nothing on the console from the kernel is usually one of two things.
1. No console driver configured in the kerlel
2. A broken drm framebuffer, often because it needs fimware and the firmware is missing.
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.