![]() E.g.:īefore you start, think back to when you first started noticing the behavior. You can disable vesafb in grub by passing it a nonsensical parameter. However this can misbehave sometimes (e.g. The kernel uses a framebuffer driver for this, such as -vesafb. For systems that support Kernel Mode Setting (KMS), this includes using the higher resolutions of the video card. The linux kernel uses the framebuffer for doing graphics prior to X starting up. ![]() Workaround C: Disable the VESA framebuffer from grub If that solves the issue, you can remove it from your /boot/grub/menu.lst as a workaround. To check this, in the grub menu edit the kernel line and remove 'splash' from the end of the line, and boot. This is because with plymouth in initrd, it's a bit racy. However, if plymouth dies at just the right time it can leave the system stuck on a blank vt, and can't recover. If Plymouth crashes during boot, X *should* still boot up, just that you'll be left looking at a black screen a lot longer than you'd like. See X/NonGraphicalBoot for additional ideas. You can disable the graphical bootscreen via:
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |