You are not logged in.
Hi eve.!
I've recently installed the base version of arch (X will follow soon...). Everything seems to work properly, except when i set vga=361 as the default resolution (by adding it in the grub menu after "ro"): before booting the kernel, grub prompt me "undefined video mode:169" and ask me to press enter to select a resolution or any other button to go on. At this point, if i choose to manually select the resolution (and i choose mode "361" or "t") everything works flawlessly, otherwise if i let it go for his own it screws up my keyboard and i must restart the system "manually".
I know it's not important to have a proper resolution in the terminal, but i want everything to be perfect;)
Last edited by Cape (2009-02-25 20:57:25)
Offline
in the menu.lst file, I don't remember if there were VGA codes in the 300s. I use a 792 = 1024x768 and 16M colors and it works for me.
Check your menu.lst file and see what codes are available. AFAIK, If that code is not supported on your system, grub takes you to a different screen (to select a new code) where the codes are different.
There's no such thing as a stupid question, but there sure are a lot of inquisitive idiots !
Offline
grub reads that number as a hexadecimal number, 361 is 865 in decimal
Offline
grub reads that number as a hexadecimal number, 361 is 865 in decimal
In which case, 169 hex would yield the 361 you want in decimal. However, if you're original value is returning the error
when i set vga=361 as the default resolution (by adding it in the grub menu after "ro"): before booting the kernel, grub prompt me "undefined video mode:169"
it leads me to believe its converting it...however, it may still be throwing an error from that conversion. try "vga=169" just for kicks and see if it cooperates, and post back with the result.
Here is some additional information which suggests needing certain hardware support (361 is specifically mentioned, although the water is muddied slightly with conversion values)
http://bbs.archlinux.org/viewtopic.php?id=58787
unfortunately, I cant help more than this but it may steer you towards a solution. I would do some testing but I am unable to with my current work laptop lol.
I know it's not important to have a proper resolution in the terminal, but i want everything to be perfect;)
its perfectly understandable to seek perfection
good luck!
Offline
Yes, it's a bit confusing really. I just put vga=792 and it worked fine. But after first having given an invalid value to vga parameter, I was asked to pick a code from a list, and this code had to be 318 which is hex for 792.
Offline
MMM...,
I tried with vga=865 and it worked fine!
Probably the programmers got confused and added a hex translation where it's not needed?
Offline