summaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authorrader <rader@88473608-6f18-0410-8b6c-91216bd3049c>2008-01-06 20:32:04 +0000
committerrader <rader@88473608-6f18-0410-8b6c-91216bd3049c>2008-01-06 20:32:04 +0000
commitdabfd6e398182e85568e53daeeae68a638348c4b (patch)
tree8645aec756a86f90d0259b5cc98476d0a802fae1 /README
parent858d95674eb19e0ca3a5bc24c516d746300753d0 (diff)
has ability to pop up windows
git-svn-id: svn+ssh://svn-nitpicker.cl.cam.ac.uk/linpicker/trunk@132 88473608-6f18-0410-8b6c-91216bd3049c
Diffstat (limited to 'README')
-rw-r--r--README33
1 files changed, 33 insertions, 0 deletions
diff --git a/README b/README
index cd6255d..4825c53 100644
--- a/README
+++ b/README
@@ -66,6 +66,39 @@ kernel /vmlinuz-2.6.22.9-61.fc6 ro root=LABEL=/1 video=vesafb:ywrap,mtrr vga=788
This fb driver is only activated at boot time and the settings cannot be
changed using fbset.
+The graphic modes are NOT in the list which you get if you boot with
+vga=ask and hit return. The mode you wish to use is derived from the
+VESA mode number. Here are those VESA mode numbers:
+
+ | 640x480 800x600 1024x768 1280x1024
+----+-------------------------------------
+256 | 0x101 0x103 0x105 0x107
+32k | 0x110 0x113 0x116 0x119
+64k | 0x111 0x114 0x117 0x11A
+16M | 0x112 0x115 0x118 0x11B
+
+The video mode number of the Linux kernel is the VESA mode number plus
+0x200.
+
+ Linux_kernel_mode_number = VESA_mode_number + 0x200
+
+So the table for the Kernel mode numbers are:
+
+ | 640x480 800x600 1024x768 1280x1024
+----+-------------------------------------
+256 | 0x301 0x303 0x305 0x307
+32k | 0x310 0x313 0x316 0x319
+64k | 0x311 0x314 0x317 0x31A
+16M | 0x312 0x315 0x318 0x31B
+
+To enable one of those modes you have to specify "vga=ask" in the
+lilo.conf file and rerun LILO. Then you can type in the desired
+mode at the "vga=ask" prompt. For example if you like to use
+1024x768x256 colors you have to say "305" at this prompt.
+
+For this code use mode 312 so the vga number will be 312.
+
You can also try loading a card-specific module as root
if you know your card's maker.
+