http://bugzilla.novell.com/show_bug.cgi?id=586053 http://bugzilla.novell.com/show_bug.cgi?id=586053#c2 Stefan Dirsch <sndirsch@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |mrmazda@earthlink.net --- Comment #2 from Stefan Dirsch <sndirsch@novell.com> 2010-03-06 07:36:09 UTC --- (In reply to comment #2)
Display has no usable DDC or EDID.
Ancient monitor? Broken VGA cable or still using BNC cables? KVM switch part of the game?
00:00.0 Host bridge: Intel Corporation 82G33/G31/P35/P31 Express DRAM Controller (rev 10) 00:02.0 VGA compatible controller: Intel Corporation 82G33/G31 Express Integrated Graphics Controller (rev 10) running kernel is 2.6.33-rc7-3-default (M2) due to bug 586044 sax2 -p finds Chip: 0 is -> Intel G33 00:02:0 0x8086 0x29c2 PCI Intel
Running default kernel 2.6.33 shouldn't be an issue here. Graphics hardware is Intel G33.
sax2 & sax2 -c0 run before initial attempt to startx or runlevel 5 aborted
/var/log/SaX.log ?
X -configure following sax2 failure locked up the machine
I don't think that's still supported. Often conflicting or broken drivers are tried to be loaded.
startx without xorg.conf brings up working 1024x768
1024x768 is the default resolution when DDC/EDID information is not available.
No evidence in YaST2 of any means to configure my normally used 1600x1200
See http://lists.opensuse.org/opensuse-factory/2009-12/msg00017.html
Krandrtray won't let me chose any resolution above 1024x768
Probably krandrtry can't add new modes. Should be possible by using xrandr, even higher than the initial one.
sax2 after exiting a 1024x768 X session works to allow specifying 2048x1536@60hz display @ 1600x1200, but then startx exits: (EE) intel(0): No Kernel modesetting driver detected. (EE) Screen(s) found, but none have a usable configuration Fatal server error: no screens found
Makes no sense. SaX2 itself starts an intel-based driver, on which the configuration interface is running. The error message means that KMS (Kernel mode setting) is not active, i.e. intel-agp and i915 kernel modules have not been loaded. intel meanwhile only supports KMS. So why should have been SaX2 able to start before? Anyway, I suggest to use xlog2xconf to create an xorg.conf and adjust this one to your needs. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.