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: The login screen is drawn on the screen.X attempts to put the card into one of its higher resolutions, such as the preferred resolution.gdm is started, which instantiates a new X session for the login screen to replace the framebuffer's graphics.The framebuffer is initialized with a purple background. If the kernel supports Mode Setting (KMS), it puts the video card into its preferred resolution using a frame buffer (vesafb).BIOS detects hard drive with a bootloader (grub) present and starts it.Here's what's going on under the hood during each of these steps: Here is a typical sequence of phases your system goes through as it boots: You may notice flickers during boot - these are indications that different processes are starting up and interacting with the GPU. This can happen for a bunch of different reasons as different processes run as your system boots up. Try disabling compiz ( sudo chmod a-x /usr/bin/compiz), logging in as a different user, or turning off DRI.īlank or black screens generally indicate a failure feeding data to the Graphics Processing Unit (GPU) in your video card. If it occurs *after* entering your password on the login page, you have some different class of issue, such as an issue with 3D / DRM. Obtaining register dumps (see below) may still be of value however. If you see a screen of a different color (brown, white, multi-colored corruption, etc.) you are seeing a different class of graphics bug.If the blank/black screen comes after your screen saver has been running, you may either have a screensaver-induced crash (see X/Backtracing) or a power management failure (See PowerManagement) If it occurs when closing your laptop lid, see the PipeA Quirk as a better possibility. See DebuggingKernelSuspend or UnderstandingSuspend If the blank/black screen occurs after resuming from suspend, you have a different class of bug. See X/Troubleshooting/Resolution instead. If you see "Out of Scan Range" or similar, you don't have this bug. The screen displays but is far too time and/or the backlight can't be adjusted.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |