https://bugzilla.novell.com/show_bug.cgi?id=211303 matz@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sndirsch@novell.com AssignedTo|sndirsch@novell.com |cgriffin@novell.com Severity|Blocker |Major Status|NEEDINFO |NEW Component|X.Org |Xen Info Provider|matz@novell.com | QAContact|sndirsch@novell.com |qa@suse.de ------- Comment #5 from matz@novell.com 2006-10-10 08:59 MST ------- This is very unfortunate. It indeed is the Xen kernel. With the -default one I get my 85 Hz back. One difference is, that it now detects the VBE bios again: (WW) I810(0): Bad V_BIOS checksum (II) I810(0): Primary V_BIOS segment is: 0xc000 (II) I810(0): VESA BIOS detected (II) I810(0): VESA VBE Version 3.0 (II) I810(0): VESA VBE Total Mem: 32448 kB (II) I810(0): VESA VBE OEM: Intel(r)Grantsdale-G Graphics Chip Accelerated VGA BIOS (II) I810(0): VESA VBE OEM Software Rev: 1.0 (II) I810(0): VESA VBE OEM Vendor: Intel Corporation (II) I810(0): VESA VBE OEM Product: Intel(r)Grantsdale-G Graphics Controller (II) I810(0): VESA VBE OEM Product Rev: Hardware Version 0.0 This would of course explain why it couldn't set the refresh under Xen, because obviously VBE method can't work without VBE. So this is a Xen regression, because in alpha4plus it still could detect the VBE. Interestingly only sometimes (after the third restart of the X server it was totally confused and stoped working, because the VBE was in some unexpected address) but still. Anyway, not really an X bug (except of course that it could detect that it wasn't able to see a VESA bios, so it shouldn't even try to use VBE method 3, and instead perhaps show a clear error message). Changing summary, assignee, component and severity. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.