Bug 120551

Summary:	nofb, nomodeset and similar options not working
Product:	Other	Reporter:	Yill Din (justincase)
Component:	Other	Assignee:	other_other
Status:	NEW ---
Severity:	normal
Priority:	P1
Hardware:	All
OS:	Linux
Kernel Version:	3.16.0-4-amd64 (debian jessie)	Subsystem:
Regression:	No	Bisected commit-id:

Description Yill Din 2016-06-17 12:17:59 UTC

Hello,
i am using linux in qemu with -ncurses option. which enables me to access terminal without X, just using textmode SSH. But it needs virtualized OS to have no framebuffer, no graphic mode, but only the most basic BIOS driven console character/text output.

However something in userspace still loads the modules for framebuffer and sets console to graphic mode (which effectively makes it inacessible for me). Can you please fix nofb option, so i can be 100% sure that once i've used this option, my VC will never be set to graphic mode?

I've found workaround which was to delete

rm -rf /lib/modules/*/kernel/drivers/gpu/drm/
and regenerate ramdisk.

I think that when i use nofb it should really mean that there will be no graphic mode on text console until i reboot the system without nofb.

this was PITA for years as the sets of kernel options needed to force system to be purely text were changing. now it needs some sophisticated module blacklisting (that do not work for me either) or deleting. (i've also tried to blacklist some of drm modules from grub and they still were loaded... WTF??? i had to delete them completely! this DRM stuff seems to be quite annoying).

please fix the nofb option so it would really force the text mode only and dissable all graphics. if nofb is not suitable for this, please add another option to solve this problem once forever.