I have the feeling I've mistyped something and have looked at it too often.
I just did a fresh install of Arch, on a box that had a relatively new installation of it.
Last time, just using the generic Arch kernel, if I added the vga=773 to my kernel line, it would boot up using framebuffer.
However, this time, my Arch section looks like this
# (3) Arch Linux
title Arch Linux [/boot/vmlinuz26]
kernel /boot/vmlinuz26 root=/dev/hdb2 ro vga=773
When I boot, after the decompressing the kernel I get
You have passed an undefined mode, hit space to continue or return for a list of modes.
I'm not sure what I missed, or if I accidently left something out during the installation (most of the base packages, a few things like lilo, nano, wireless stuff eliminated).
I haven't yet tried installing a custom kernel and including framebuffer support. I'm just wondering if I've forgotten something obvious.
Thanks for any help
Solved, in a way, anyway. Changing it to vga=788 gives me 800x600 which works well on the monitor I have (a 15" LCD).
Not sure why the 1024x768 isn't working, but this is ok.
For my 1024 x 768 laptop monitor, I use:
in my lilo.conf for the framebuffer.
Hrmm 792 didn't work either. I guess that something in there, either monitor or video card can't support 1024x768.
Actually, that's alright--on another install, running a Slack derivative,
booting with lilo, I get 1024x768 and it's a bit small for my aging eyes.
Try using video=vesafb:1024x768-32 instead of the vga= line. Remember to change vesafb to whatever fb-device you are using.
vga=0x318 doesn't work?
No the 0x numbers didn't work either. However, as I said, I'm going to leave it at 800x600 which I actually find better for my eyes than 1024x768. (In console, in X I need the 1024x768, which I get with no problem.)
I do thank everyone for their suggestions, but at present, I'm just going to leave it at 788.