http://bugzilla.novell.com/show_bug.cgi?id=586053
http://bugzilla.novell.com/show_bug.cgi?id=586053#c7
Felix Miata
(In reply to comment #1)
Display has no usable DDC or EDID.
Ancient monitor? Broken VGA cable or still using BNC cables? KVM switch part of the game?
Long ago I got a bunch of Dell/Trinitron P991s for free, about half of which for reasons unknown to me had non-working DDC/EDID. I kept three, and use primarily one with non-working in order to confirm the devs are not neglecting keeping X working as well as before for those with similarly handicapped displays.
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.
According the the motherboard manufacturer the graphics hardware is G31, though I see according to Xorg.0.log output there doesn't seem to be any such device. Who am I to disagree with the people who made it? http://www.biostar.com.tw/app/en/mb/content.php?S_ID=355
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.
It was precisely http://lists.opensuse.org/opensuse-factory/2009-12/msg00017.html and related SaX2 discussion following that brought X -configure to my attention. Though not as powerful as SaX2, it has worked on every attempt I've made to use it since, until this bug.
startx without xorg.conf brings up working 1024x768
1024x768 is the default resolution when DDC/EDID information is not available.
That constitutes an improvement over 800x600, which is what I remember has been the default for many moons since the jump from 640x480.
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.
This is where my memory of my lost response attempt is worst. I now only remember being unable to tell from the xrandr man page how to add the modes that formerly were available automatically just from providing via xorg.conf HorizSync and VertRefresh ranges, in part by not finding any description of the "name" parameter required as input for --newmode, and in part by not seeing for --fb whether size means device pixels, pt, mm, em or something else.
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?
Considering that X will start with no xorg.conf at all, it certainly makes no sense to me.
Anyway, I suggest to use xlog2xconf to create an xorg.conf and adjust this one to your needs.
This bug is my first exposure to the existence of this file. xlog2xconf has no manual entry, and no --help explanations for -e or -f or - options. I tried it on both i845G and iG31 systems, getting virtually useless 821 byte skeletons: Section "Device" Identifier "Builtin Default intel Device 0" Driver "intel" EndSection Section "Screen" Identifier "Builtin Default intel Screen 0" Device "Builtin Default intel Device 0" EndSection Section "Device" Identifier "Builtin Default fbdev Device 0" Driver "fbdev" EndSection Section "Screen" Identifier "Builtin Default fbdev Screen 0" Device "Builtin Default fbdev Device 0" EndSection Section "Device" Identifier "Builtin Default vesa Device 0" Driver "vesa" EndSection Section "Screen" Identifier "Builtin Default vesa Screen 0" Device "Builtin Default vesa Device 0" EndSection Section "ServerLayout" Identifier "Builtin Default Layout" Screen "Builtin Default intel Screen 0" Screen "Builtin Default fbdev Screen 0" Screen "Builtin Default vesa Screen 0" EndSection -- 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.