Vassilis Virvilis wrote:

Antonino A. Daplas wrote:

quoted

Too many differences since the timings for the 2 modes are also
different.
If you can match the timings, as shown by fbset and xvidtune, this should
minimize the variation.

[snip]

quoted

savagefb does save the initial registers and reuses part of them when
setting
the mode, so if you can boot with vga= parameter that matches the
initial mode
of savagefb, it might help. Try this:

video=savagefb:1024x768-16@60 vga=0x317

thanks for the hand holding.

Let me reiterate to make sure I understood correctly.

Let's concentrate in one mode because trying all the modes is very time
consuming.
Since I am interested mainly in 640x480-16@xx that means vga=0x311. That
also
means I shouldn't fiddle with SVGATextMode before loading the savagefb
driver.
Right now I am doing a lot of mode3; SVGATextMode -x to restore the
console.

So I am booting with video=savagefb:640x480-16@60 vga=0x317 and prevent
SVGATextMode from running.

Now for mode setting. I will run X, xvidtune, fetch the mode. I will use
http://www.tldp.org/HOWTO/Framebuffer-HOWTO-18.html
instructions to convert the mode to a line fbset understands. Then
I will force my SDL test app to use the mode previously set by fbset
and then I will run the savagedump to compare with the X dump.

I will try the procedure above ASAP and report back unless you have any
objections in the methodology.

Much simpler if you just load X first with UseBIOS False then dump the regs.
Do the same with UseBIOS True.  You mentioned that X does not work if the
option UseBIOS is false.

Tony 


-------------------------------------------------------
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642