Console Goes Blank When Booting 2.6.15-rc5
As Jesper Juhl has reported, if I boot 2.6.15-rc5 with vga=normal, everything is fine. If I boot using my preferred size (vga=794), the console goes blank. Because I'm a touch typist, I can login and start X and everything is copacetic, but as soon as I leave X, I'm back to the blank screen. From X, if I flip over to a VC, the VC display is garbled and has artifacts from the X display.
This worked fine with 2.6.14.3, and I didn't change the console, framebuffer, or vesa options between the two kernels. Not sure how to proceed, but I sure would like my high res console screens back.
Thanks,
Kurt
Signature · 2 lines
"What's another word for Thesaurus?" -- Steven Wright
Quoted 10 lines · Kurt Wall
As Jesper Juhl has reported, if I boot 2.6.15-rc5 with vga=normal, everything is fine. If I boot using my preferred size (vga=794), the console goes blank. Because I'm a touch typist, I can login and start X and everything is copacetic, but as soon as I leave X, I'm back to the blank screen. From X, if I flip over to a VC, the VC display is garbled and has artifacts from the X display.
This worked fine with 2.6.14.3, and I didn't change the console, framebuffer, or vesa options between the two kernels. Not sure how to proceed, but I sure would like my high res console screens back.
Can you recheck your .config and make sure thatCONFIG_FRAMEBUFFER_CONSOLE=y
If that does not work, please post your dmesg and .config file.
Tony
Quoted 8 lines · Antonino A. Daplas
Quoted 7 lines · Kurt Wall
As Jesper Juhl has reported, if I boot 2.6.15-rc5 with vga=normal, everything is fine. If I boot using my preferred size (vga=794), the console goes blank. Because I'm a touch typist, I can login and start X and everything is copacetic, but as soon as I leave X, I'm back to the blank screen. From X, if I flip over to a VC, the VC display is garbled and has artifacts from the X display.
Quoted 6 lines
Quoted 3 lines
This worked fine with 2.6.14.3, and I didn't change the console, framebuffer, or vesa options between the two kernels. Not sure how to proceed, but I sure would like my high res console screens back.
Can you recheck your .config and make sure that
CONFIG_FRAMEBUFFER_CONSOLE=y
Oops. It was defined as a module. Compiling it statically gave me the console back. Interestingly, I still lose the first 102 lines of console output. After the all-important boot logo displays, I see nothing until this line:
"Console: switching to colour frame buffer device 160x64"
It's all there in the ring buffer, of course. Thanks, Antonino.
Kurt
Signature · 2 lines
The mosquito is the state bird of New Jersey. -- Andy Warhol
Quoted 12 lines · Kurt Wall
Quoted 11 lines · Antonino A. Daplas
Quoted 10 lines · Kurt Wall
As Jesper Juhl has reported, if I boot 2.6.15-rc5 with vga=normal, everything is fine. If I boot using my preferred size (vga=794), the console goes blank. Because I'm a touch typist, I can login and start X and everything is copacetic, but as soon as I leave X, I'm back to the blank screen. From X, if I flip over to a VC, the VC display is garbled and has artifacts from the X display.
This worked fine with 2.6.14.3, and I didn't change the console, framebuffer, or vesa options between the two kernels. Not sure how to proceed, but I sure would like my high res console screens back.
Quoted 7 lines
Quoted 2 lines
Can you recheck your .config and make sure that
CONFIG_FRAMEBUFFER_CONSOLE=yOops. It was defined as a module. Compiling it statically gave me the console back. Interestingly, I still lose the first 102 lines of console output. After the all-important boot logo displays, I see nothing until this line:
Yes, that should be expected behavior with vesafb. The adapter was set very early during the boot process, when machine is still in real mode, vgacon will never load, and you will only see any semblance of display until the framebuffer console is loaded. You should see different behavior with chipset-specific drivers, ie, you will have vgacon momentarily until fbcon takes over.
Tony