Re: No console anymore. How to figure this out.

On 3/17/26 10:49 AM, Dale wrote:
> On 3/17/26 8:31 AM, Michael wrote:
>> On Tuesday, 17 March 2026 05:11:04 Greenwich Mean Time Dale wrote:
>>> On 3/16/26 10:30 AM, Michael wrote:
>>>> You haven't yet showed 'grep DRM .config' of your running kernel.
>>> Here you go.
>>>
>>>
>>> root@Gentoo-1 /usr/src/linux # grep DRM .config
>>> CONFIG_DRM=y
>>> # CONFIG_DRM_DEBUG_MM is not set
>>> CONFIG_DRM_KMS_HELPER=y
>>> # CONFIG_DRM_PANIC is not set
>>> CONFIG_DRM_FBDEV_EMULATION=y
>>> CONFIG_DRM_FBDEV_OVERALLOC=100
>>> # CONFIG_DRM_LOAD_EDID_FIRMWARE is not set
>>> CONFIG_DRM_TTM=y
>>> CONFIG_DRM_TTM_HELPER=y
>>> # CONFIG_DRM_I2C_CH7006 is not set
>>> # CONFIG_DRM_I2C_SIL164 is not set
>>> # CONFIG_DRM_I2C_NXP_TDA998X is not set
>>> # CONFIG_DRM_I2C_NXP_TDA9950 is not set
>>> # CONFIG_DRM_RADEON is not set
>>> # CONFIG_DRM_AMDGPU is not set
>>> # CONFIG_DRM_NOUVEAU is not set
>>> # CONFIG_DRM_I915 is not set
>>> # CONFIG_DRM_XE is not set
>>> # CONFIG_DRM_VGEM is not set
>>> # CONFIG_DRM_VKMS is not set
>>> # CONFIG_DRM_VMWGFX is not set
>>> # CONFIG_DRM_GMA500 is not set
>>> # CONFIG_DRM_UDL is not set
>>> # CONFIG_DRM_AST is not set
>>> # CONFIG_DRM_MGAG200 is not set
>>> CONFIG_DRM_QXL=y
>> You probably don't need QXL unless you're running VM in QEMU?
>
> I've read about VM and that is a no.  I don't know what QEMU is for 
> sure.  I'm going with no on that as well.  ;-)
>
>>
>>> # CONFIG_DRM_VIRTIO_GPU is not set
>>> CONFIG_DRM_PANEL=y
>>> CONFIG_DRM_BRIDGE=y
>>> CONFIG_DRM_PANEL_BRIDGE=y
>>> # CONFIG_DRM_ANALOGIX_ANX78XX is not set
>>> # CONFIG_DRM_ETNAVIV is not set
>>> # CONFIG_DRM_BOCHS is not set
>>> # CONFIG_DRM_CIRRUS_QEMU is not set
>>> # CONFIG_DRM_GM12U320 is not set
>>> # CONFIG_DRM_SIMPLEDRM is not set
>>> # CONFIG_DRM_VBOXVIDEO is not set
>>> # CONFIG_DRM_GUD is not set
>>> # CONFIG_DRM_SSD130X is not set
>>> CONFIG_DRM_PANEL_ORIENTATION_QUIRKS=y
>>> # CONFIG_DRM_ACCEL is not set
>>> root@Gentoo-1 /usr/src/linux #
>> It looks OK to me, although others have experimented with SIMPLEFB and
>> EFIFB to get out of nvidia's clutches when dropping into a console.  I'd
>> leave your kernel as is for now.
>>
>> Your nvidia-drm option has modeset=0 as a default.  In the first
>> instance you could try reloading the nvidia_drm module with 'option
>> modeset=1' to see if this will restore your VT display, or set it in
>> your /etc/modprobe.d/, or in your GRUB's kernel CMDLINE:
>>
>> nvidia_drm.modeset=1
>>
>> and reboot.
>
>
> I added it to the kernel command line.  Easiest way to test and 
> reverse if needed.  I'll reboot later on.  I hope that works.
>
> Thanks.
>
> Dale
>
> :-)  :-)


I finally got around to rebooting.  I had Krename processing around 
60,000 files and it well . . . took a little bit.  Plus I been busy 
outside.  Anyway, kernel line looks like this now.



root@Gentoo-1 / # cat /proc/cmdline
BOOT_IMAGE=/kernel-6.12.31-2 
root=UUID=26e58ee4-9c8f-4efd-bbb3-215df71cf85e ro nvidia_drm.modeset=1
root@Gentoo-1 / #


I used tail -f to monitor dmesg and the messages file when I tested 
this.  I went to a console, black screen and monitor powers off. When I 
switch back to the GUI, dmesg and messages file report nothing new.  No 
errors or even info about the switch.

Well, one more thing that we know doesn't work.  Anything else?  I'd 
really like to have my console back.  That said, I'm getting in a lot of 
practice on booting and getting everything back to working. I can do it 
a little faster now.  LOL

Dale

:-)  :-)