http://bugzilla.novell.com/show_bug.cgi?id=557969 http://bugzilla.novell.com/show_bug.cgi?id=557969#c2 --- Comment #2 from Ulrich Windl 2009-11-24 12:28:54 CET --- Hardware: ATI Technologies Inc Rage 128 Pro Ultra TF Driver: ati

From the Xorg.0.log: (II) R128(0): Primary V_BIOS segment is: 0xc000 (--) R128(0): Chipset: "ATI Rage 128 Pro ULTRA TF (AGP)" (ChipID = 0x5446) (--) R128(0): Linear framebuffer at 0xf8000000 (--) R128(0): MMIO registers at 0xff8fc000 (--) R128(0): VideoRAM: 16384 kByte (128-bit SDR SGRAM 1:1) (**) R128(0): Using external CRT for display (II) R128(0): Primary Display == Type 3 [...]

(II) R128(0): VESA BIOS detected (II) R128(0): VESA VBE Version 2.0 (II) R128(0): VESA VBE Total Mem: 16384 kB (II) R128(0): VESA VBE OEM: ATI RAGE128 (II) R128(0): VESA VBE OEM Software Rev: 1.0 (II) R128(0): VESA VBE OEM Vendor: ATI Technologies Inc. (II) R128(0): VESA VBE OEM Product: R128 (II) R128(0): VESA VBE OEM Product Rev: 01.00 (II) Loading sub module "ddc" (II) LoadModule: "ddc" (II) Module "ddc" already built-in (II) R128(0): VESA VBE DDC supported (II) R128(0): VESA VBE DDC Level none (II) R128(0): VESA VBE DDC transfer in appr. 2 sec. (II) R128(0): VESA VBE DDC read failed (==) R128(0): Using gamma correction (1.0, 1.0, 1.0) [...] (II) Loading sub module "i2c" (II) LoadModule: "i2c" (II) Module "i2c" already built-in (II) R128(0): I2C bus "DDC" initialized. (II) R128(0): I2C device "DDC:E-EDID segment register" registered at address 0x60. (II) R128(0): I2C device "DDC:ddc2" registered at address 0xA0. (EE) R128(0): No DFP detected (II) R128(0): Monitor[0]: Using hsync range of 29.00-85.00 kHz (II) R128(0): Monitor[0]: Using vrefresh range of 50.00-160.00 Hz (II) R128(0): Clock range: 12.50 to 350.00 MHz However "hwinfo --monitor" reports: [...] Hardware Class: monitor Model: "HP D8907" Vendor: HWP "HP" Device: eisa 0x22cb "HP D8907" Serial ID: "KR12726942" [...] Size: 312x234 mm Detailed Timings #0: Resolution: 1024x768 Horizontal: 1024 1072 1168 1376 (+48 +144 +352) +hsync Vertical: 768 769 772 808 (+1 +4 +40) +vsync Frequencies: 94.50 MHz, 68.68 kHz, 85.00 Hz Driver Info #0: Max. Resolution: 1280x1024 Vert. Sync Range: 50-160 Hz Hor. Sync Range: 30-85 kHz Bandwidth: 94 MHz -- 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.

http://bugzilla.novell.com/show_bug.cgi?id=557969 http://bugzilla.novell.com/show_bug.cgi?id=557969#c4 --- Comment #4 from Ulrich Windl 2009-11-24 14:17:57 CET --- So it seems, you are no longer supporting CRT displays, as a "flat screen" would have worked? Let me remark that several people out there will stick to their CRTs because color representation is much better than that of these LCDs or plasmas. -- 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.

http://bugzilla.novell.com/show_bug.cgi?id=557969 http://bugzilla.novell.com/show_bug.cgi?id=557969#c6 --- Comment #6 from Stefan Dirsch 2009-11-24 13:29:56 UTC --- Also for having a closer look I would need the X logfile *without* any xorg.conf in place. -- 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.

http://bugzilla.novell.com/show_bug.cgi?id=557969 http://bugzilla.novell.com/show_bug.cgi?id=557969#c8 --- Comment #8 from Ulrich Windl 2009-11-25 08:04:37 CET --- Created an attachment (id=329364) --> (http://bugzilla.novell.com/attachment.cgi?id=329364) Log file for "Xorg :1 -config /dev/null vt11" -- 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.

http://bugzilla.novell.com/show_bug.cgi?id=557969 http://bugzilla.novell.com/show_bug.cgi?id=557969#c10 --- Comment #10 from Ulrich Windl 2009-11-26 08:15:47 CET --- Created an attachment (id=329587) --> (http://bugzilla.novell.com/attachment.cgi?id=329587) Log file, this time without specifying a config file, and having xorg.conf moved away The monitor is detected correctly, and resolutions higher than 800x600 are detected. -- 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.

http://bugzilla.novell.com/show_bug.cgi?id=557969 http://bugzilla.novell.com/show_bug.cgi?id=557969#c11 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|WONTFIX |INVALID --- Comment #11 from Stefan Dirsch 2009-11-26 07:42:14 UTC --- So there is no issue and has never been ... -- 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.

http://bugzilla.novell.com/show_bug.cgi?id=557969 http://bugzilla.novell.com/show_bug.cgi?id=557969#c13 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |INVALID --- Comment #13 from Stefan Dirsch 2009-11-27 09:08:16 UTC --- (In reply to comment #12)

(In reply to comment #11)

...

So there is no issue and has never been ...

Let me object: Issue #1: During installation a poor resolution (800x600) was selected

Chose a different one in boot menu. It depends on the graphic's card VESA BIOS, which one is available. 800x600 might be the highest one. We're still using fbdev driver for installation.

Issue #2: The user can not select a higher resolution Issue #3: "Detect Monitor" does not work (Issues #2 and #3 are inside the GNOME Display Manager)

This contradicts what you've written in comment #10.

Issue #4: X11 Configuration vanished from YaST. You'll have to know that SaX exists

The removal of sax2 from YaST has been done by intention and won't be changed. It's mentioned in the the release notes and also in our manual (PDF).

I think that this combination of issues disappoints the average user very much.

The average user also doesn't use 10 year old PC hardware. Also beginners are still reading release notes and manuals. -- 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.

http://bugzilla.novell.com/show_bug.cgi?id=557969 http://bugzilla.novell.com/show_bug.cgi?id=557969#c15 --- Comment #15 from Stefan Dirsch 2009-11-27 13:21:46 UTC --- (In reply to comment #14)

I did choose a better resolution in the boot menu. Comment #10 proves that you made the error: If Xorg can detect the proper resolution, and SaX can do it (comment #0), but the installation program cannot do it, there's something wrong.

I don't understand. We no longer create any xorg.conf on the installed system and you confirmed once more that Xorg without xorg.conf detects the proper resolution. The resolution you select in the boot menu is unrelated to the resolution, which is used afterwards. During installation the selected resolution from VESA BIOS is used (fbdev driver instead of native driver is running), afterwards the native (i.e. preferred for a CRT) resolution provided by the monitor. -- 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.