Timeline for What is vt.handoff=7 parameter in grub.cfg?
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 23, 2020 at 1:37 | comment | added | Maxim Blinov | @guntbert that one is dead too... | |
| Jun 25, 2018 at 13:21 | comment | added | Colin Watson |
@user1823664, I think you've confused the old distro-specific runlevel 3 (which was a "no X" runlevel on Red Hat and its derivatives, but not on Debian and its derivatives) with virtual terminal numbers. vt.handoff=3 would simply tell the kernel to maintain the current contents of video memory on virtual terminal 3 at startup; this might happen to confuse something into booting without X, but if it does it would be an accident at best.
|
|
| May 2, 2018 at 3:08 | comment | added | user1823664 | If vt.handoff is assigned 3, will one boot into command line mode (no X)? | |
| Sep 13, 2015 at 11:05 | comment | added | Colin Watson |
gfxpayload=keep and vt.handoff=7 are two parts of the same overall scheme; gfxpayload=keep tells GRUB not to switch the video mode back to the firmware default before booting the kernel, and vt.handoff=7 tells the Linux kernel to behave as in my answer above. I don't know where your error message comes from.
|
|
| Sep 12, 2015 at 12:04 | comment | added | Sam Brightman | So this is separate from the gfxpayload=keep option in GRUB? i.e. if you get a desirable graphics mode in GRUB menu, and you get the aubergine blank screen and the correct desktop but get "Mode Not Supported" instead of the Plymouth splash, then this is Plymouth's fault? | |
| May 21, 2012 at 15:01 | comment | added | Serrano Pereira | @deblanck: Edit /etc/grub.d/10_linux as explained here | |
| Mar 28, 2012 at 16:35 | comment | added | user52456 | How i may sacefully unable the option "vt.handoff=7" from my grub.cfg configuration,so,that be it never adding again? | |
| Apr 11, 2011 at 9:41 | history | answered | Colin Watson | CC BY-SA 3.0 |