Re: No console anymore. How to figure this out.
Dale <[email protected]>
| Newsgroups | gmane.linux.gentoo.user |
|---|---|
| Message-ID | <[email protected]> |
On 3/16/26 10:49 AM, Alan Mackenzie wrote: > Hello again, Dale. > > On Mon, Mar 16, 2026 at 10:03:26 -0500, Dale wrote: >> On 3/16/26 6:18 AM, Alan Mackenzie wrote: > [ .... ] > >>> Not much of one, but could you please check that >>> CONFIG_FRAMEBUFFER_CONSOLE is enabled in your kernel? It's found at >>> Device Drivers/Graphics support/Console display driver >>> support/Framebuffer Console support. >>> Without this, a there is no console to display on the framebuffer. But >>> seeing as how you see boot messages, it's probably set anyway. But maybe >>> you're seeing the boot messages through grub's text handling, I don't >>> know. Switching the display from boot loader to kernel, then from one >>> framebuffer to another is complicated, and probably not wholly defined. >>> But it's got to worth the time for a quick check. >>>> Thanks. >> I did a search for it. This is the part of the screen, in case some >> other setting is wrong in that section. I edited it to make it not line >> wrap. Nothing important missing tho. > > >> (80) Initial number of console screen columns >> (25) Initial number of console screen rows >> [*] Framebuffer Console support >> [*] Enable legacy fbcon hardware acceleration code >> [*] Enable Scrollback Buffer in System RAM <=========== >> (128) Scrollback Buffer Size (in KB) >> [*] Enable a working GPM for scrolled back scrollback buffer in >> System RAM >> -*- Map the console to the primary display device >> [ ] Framebuffer Console Rotation >> [ ] Framebuffer Console Deferred Takeover > > >> That look like the same as a working system you have? > It does, but ... > >> Thanks for the help. As you said, it only takes a minute to check. :-D > Just as a matter of interest, could you please try disabling "Enable > Scrollback Buffer in System RAM". This is an option I am completely > familiar with (having written it), and it might be there's a bug in it > which has only just been triggered by the new nvidia-drivers. > > It's got to be worth a try. > >> Dale >> :-) :-) Working on this next. I got the kernel built and ready. Now to reboot. May do that after I update this weekend. Dale :-) :-)