Hello Jean-S�bastien Guay
Unload all kernelframebuffer-modules and it will work. To support more than 80x25 console, load vesafb and fbcon (and maybe others?) and give a kernel parameter (preferably in lilo.conf; run lilo afterwards!) vga=<anything from the list below>:
# VESA framebuffer console @ 800x600x64k # vga=788 # VESA framebuffer console @ 1024x768x64k # vga=791 # VESA framebuffer console @ 1280x1024x64k # vga=0x31B # VESA framebuffer console @ 1600x1200x64k # vga=0x31F # Normal VGA console # vga = normal # prompt # vga=ask
Hope that works...
Regards, Adrian.
Jean-S�bastien Guay wrote:
Hello,
I have an Alpha XL 366 and I'm having a weird problem (if it were a "non-weird problem", I probably wouldn't have to ask for advice here!).
When booting up, I can see the messages on my screen just fine. The display is in text mode, and I can see everything starting up. Then kdm starts, and I have a graphical login (which is what I want, most of the time). But from that point on, anytime the system switches to text mode (either because I press CTRL-ALT-F1, or because I'm shutting down the system), my monitor displays the message "H.V FREQUENCY OVER RANGE", and I can't see anything. I didn't think it was possible to have a frequency my monitor doesn't support in *text mode*... Normally, text mode is the lowest common denominator, and it's a fixed refresh rate that all monitors support...
Is there something in my XF86Config-4 that might help with this problem? I'll include it here. I just checked the horizontal and vertical frequencies I put in that file against the monitor's specs, and they're exactly the same...
[...]
