9 May
2010
9 May
'10
5:37 p.m.
Am 09.05.2010 19:23, schrieb Pierre Schmitz:
I noticed the same. But this is caused by the mkinitcpio update and not the kernel. In my case "logo.nologo" in the kernel parameter line was causing this.
That is plan bullshit. The mkinitcpio update didn't even _touch_ the init file, it is entirely unchanged.