Re Re: another i810 crash when switching bewteen X and text console

> A question to the person who started this thread:

Yes, that's me.

> Does setting the "VideoRam" option in the "Device" section of the 
XFree86 configuration
file to 32000 and not running 865patch help?

No.

case 1 : 865patch not started and VideoRam set to 32000

Here are the useful lines in the logfile :
(II) I810(0): VESA VBE Total Mem: 12288 kB
[...]
(II) I810(0): Tweak BIOS image to 12288 kB VideoRAM
(II) I810(0): BIOS view of memory size can't be changed (this is not an 
error).
(--) I810(0): Pre-allocated VideoRAM: 8060 kByte
(**) I810(0): VideoRAM: 32000 kByte

The crash is still here when switching to text console. 

case 2 : 865patch started and VideoRam not set
Here are the useful lines in the logfile :
(II) I810(0): VESA VBE Total Mem: 31872 kB
[...]
(II) I810(0): detected 8060 kB stolen memory.
(WW) I810(0): Detected stolen memory (8000 kB) doesn't match what the BIOS 
reports (31872 kB)
(II) I810(0): I830CheckAvailableMemory: 441340 kB available
(--) I810(0): Pre-allocated VideoRAM: 8060 kByte
(==) I810(0): VideoRAM: 65536 kByte

Complete logfiles are attached (I recall this is a Dell Optiplex GX270).

So it seems that the builtin patch doesn't work here.

Moreover, the problem with the VideoRam parameter is that it is determined 
at install time
by the Redhat installer (anaconda).
So for example for the Dell GX270, it detects 4 kB of VideoRam (*), this 
amount can of course
be modified by the guy performing the installation, but the average 
end-user doesn't always
know the correct amount to select. Therefore the 865patch is (perhaps) a 
better solution.

(*) 8060 kByte rounded down to 4 kB ...

Loïc