Arthur Marsh wrote, on 01/07/09 03:21:
Robert Millan wrote, on 01/07/09 00:10:
These patches might be helpful in case someone runs in trouble with the
new loader. They instrument Linux to obtain a screen_info structure
dump,
which can be used to compare the output of "linux16" vs "linux".
This is with a Radeon 9200SE [RV280], which I think has 128 MiB of RAM.
I applied these to a kernel 2.6.30 and built and installed the kernel.
I set vga=0x311 on the linux command line
linux16 gave me a dump in green text and went no further:
all typos and omissions (usually because values were 0x0) are mine:
orig_x = 0x0 orig_y = 0x4
ext_mem_k = 0xffc0
video_mode = 0x3
cols = 0x50
egabx = 0x3
wnes ? = 0x19
points = 0x10
640x480x16
fb_base = 0xd8000000
fbsize = 0x100
fb_line_length = 0x500
red size 0x5 red pos 0xb
green size 0x6 green pos 0x5
blue size 0x5 blue pos 0x0
reserved size 0x0 pos 0x0
vesapm 0xc000:0x57aa
pages 0x18
vesa attr 0xbb
linux told me to set vgamode=640x480x16;640x480 then that it was
booting anyway, no dump of screen_info
when I tried booting with:
set vgamode=640x480x16;640x480
I received the error message about 640x480 not being a recognised
command.
Regards,
Arthur.
when using linux instead of linux16, the differences I noted were:
Firstly, linux shows the text white, with a press any key to continue
message.
linux16 showed the text green, and locked up, when I pressed any keys.
On the linux boot:
org_y = 0x9
ext_mem_k = 0x8000
egabx = 0x0
width / height / depth 0x0x0
lfb_base 0x0
lfbsize = 0x100
cloffset = 0x1000
clfb line length = 0x0
then everything from red-size onwards being 0x0.
Arthur.