[Bug 227464] New: openSUSE, 10.2, Incomplete xorg.conf file generated - unable to use x11
https://bugzilla.novell.com/show_bug.cgi?id=227464 Summary: openSUSE, 10.2, Incomplete xorg.conf file generated - unable to use x11 Product: openSUSE 10.2 Version: Final Platform: i586 OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: mszick@morethan.org QAContact: jsrain@novell.com Yes - I read the directions - and I would include the xorg.conf file if I had one - but if I had one, I would not need to file this bug report ;-) I noticed somewhere in the reading that SaX was trashing the xorg.conf file - This is to let you know that in the 10.2-GM-DVD* set released 12/07 it is still happening. Also - I can not find the setup utilities that normally ship with Xorg/X11 Also - The installation disk does not have a simple text editor to write my own xorg.conf file (if I knew how). I have not exaimined your Yast2 thingy, but if it uses a scripting engine, and this xorg.conf is not a hard-coded problem in the installer, then read on - The following has been verified by myself and fixed, in other distributions ... The situation: running kernel 2.6.18.2 in a small amount of free-memory, amount of swap does not matter - Running your installer in initrd puts anything with less the 0.5g of memory into this 'small free memory' catagory ... The scripting engine (and any other program) can be given a dirty page - python does detect this - I don't know what your system uses ... You can fix this by applying the 2.6.18.2-3.diff VM patch from kernel.org Also, you should apply the patches to bring the kernel upto 2.6.18.5 - the *.5 patch fixes some things with scsi and sata disks that could result in failures of your customer's install/operation. - - - - How to duplicate: Without the 2.6.18.2-3.diff patch in the kernel - With a "small memory x86 system" <=368Mb - Freshly formatted disks - Run the CD set of normal installation - Reboot - Observe that you are at a command line prompt - Run yast2 - exaimine the hardware reported - Learn that the system has properly identified keyboard, mouse, display board(s), monitor - Examine xorg.conf - see that only the first few, hardcoded lines are in the file. - - - - After hand-crafting an xorg.conf file on another system (thank you Debian), patch, rebuild kernel, rebuild install disk, repeat above - - - - - That is left as a tech-student exercise, I am still at the 'hand-craft' the xorg.conf file step. Mike -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=227464 mhorvath@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team- |kernel-maintainers@forge.provo.novell.com |screening@forge.provo.novell| |.com | Severity|Critical |Normal -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=227464 gregkh@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|kernel- |bnc-team-screening@forge.provo.novell.com |maintainers@forge.provo.nove| |ll.com | -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=227464 mhorvath@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team- |kernel-maintainers@forge.provo.novell.com |screening@forge.provo.novell| |.com | -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=227464 gregkh@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|kernel- |bnc-team-screening@forge.provo.novell.com |maintainers@forge.provo.nove| |ll.com | -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=227464 ms@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |mszick@morethan.org ------- Comment #2 from ms@novell.com 2006-12-21 07:19 MST ------- Hmm, what can I do here... if it is a sax problem you should be able to reproduce with the following commands: init 3 sax2 -r -a ---> the result is written to /etc/X11/xorg.conf ---> a log exists at /var/log/SaX.log Thanks -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=227464 ------- Comment #3 from mszick@morethan.org 2006-12-21 08:32 MST ------- Will set up some tests as above and report results. In the typical case, machine hangs before the log can be committed to disk. Recovering the filesystem does not recover the new log file. Problems using hand-crafted xorg.conf files seems to indicate the problem is with X11 for monitors that do not return DDC information. Seen with the ati wrapper and the i810 driver. (of course, no log file available) Not sure if that is also the installer's problem. Not sure if the X11 drivers or the monitor can do DDC on green. Either video card + a modern (returns DDC) display work. Both cards work (non-DDC monitor on either) under M$-WindowsXP-sp2 although the card marked primary must have the DDC monitor and the display settings for the non-DDC monitor/card set manually. Mike -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=227464 mszick@morethan.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|mszick@morethan.org | ------- Comment #4 from mszick@morethan.org 2006-12-21 09:47 MST ------- SaX: initializing please wait SaX: your current configuration will not be read in SaX: no X-Server running SaX: will start own server if needed SaX: ups lost card during probing... abort SaX: something went wrong while X was called with -probeonly SaX: try to call 'sax2 -p' and select a single device ? abort prompt# sax2 -p Chip: 0 is -> Intel I815 00:02:0 0x8086 0x1132 PCI i810 Chip: 1 is -> ATI 3D Rage Pro 215GP 01:02:0 0x1002 0x4750 AGP ati (Which is correct by the way) Monitor which returns DDC is on Chip 1 Motherboard BIOS : PhoenixBIOS Version 4.0 Release 6.0 HP Build: 04/11/01 9:10:45 IP.01.07US Settings: Video Primary: PCI Multi-Display: Enabled BIOS does not allow 'Multi-Display' to be enabled unless the non-embedded display is set as the BIOS primary. M$-WindowsXP will use either card/monitor as the primary monitor in either single or dual head display modes. (I.E: it switches to the card and non-DDC monitor when the graphic drivers load.) SaX.log: /************* SaX2 log : SaX2 version 8.1 - SVN Release: 1.49 2003/03/17 ************** SVN RELEASE : 1254 : DESCRIPTION : X11 configuration log file to collect information : about detection, startup and configuration. : There are three parts of logging: : --- : 1) INIT ( detection, 3D ) : 2) STARTUP ( xorg.conf, X11 log, glxinfo ) : 3) CONFIG ( config actions ) : --- : VERSION : SaX2 compiled for: [openSUSE 10.2 (i586)] PARAMETER : -r -a -r : LOG DATE : Thu Dec 21 10:18:29 CST 2006 *************/ ============================ Framebuffer Info: ---------------------------- Framebuffer not active 21-Dec 10:18:31 <I> Initializing... 21-Dec 10:18:34 <I> [ Sysp: Mouse detection data Mouse0 => Protocol : explorerps/2 Mouse0 => Device : /dev/input/mice Mouse0 => Buttons : 7 Mouse0 => Wheel : 1 Mouse0 => Emulate : 0 Mouse0 => Name : GenPS/2 Genius Mouse Mouse0 => VendorID : 0x0210 Mouse0 => DeviceID : 0x0015 Mouse0 => Profile : <undefined> Mouse0 => RealDevice : <undefined> Mouse0 => NutShell : 0 ] 21-Dec 10:18:35 <I> [ Sysp: Keyboard detection data Keyboard0 => XkbModel : pc104 Keyboard0 => XkbLayout : us Keyboard0 => Name : AT Translated Set 2 keyboard Keyboard0 => VendorID : 0x0211 Keyboard0 => DeviceID : 0x0001 Keyboard0 => Profile : <undefined> Keyboard0 => RealDevice : /dev/input/event1 ] 21-Dec 10:18:58 <I> [ Sysp: Server detection data Card0 => DomainId : 0x0 Card0 => BusId : 0x1 Card0 => SlotId : 0x02 Card0 => FuncId : 0x0 Card0 => Vendor : ATI Card0 => Device : 3D Rage Pro 215GP Card0 => VID : 0x1002 Card0 => DID : 0x4750 Card0 => Module : ati Card0 => BusType : AGP Card0 => Detected : 2 Card0 => Flag : DEFAULT Card0 => SUB-VID : 0x1002 Card0 => SUB-DID : 0x0080 Card0 => DrvProfile : <undefined> Card1 => DomainId : 0x0 Card1 => BusId : 0x0 Card1 => SlotId : 0x02 Card1 => FuncId : 0x0 Card1 => Vendor : Intel Card1 => Device : I815 Card1 => VID : 0x8086 Card1 => DID : 0x1132 Card1 => Module : i810 Card1 => BusType : PCI Card1 => Detected : 2 Card1 => Flag : DEFAULT Card1 => SUB-VID : 0x103c Card1 => SUB-DID : 0x1245 Card1 => DrvProfile : Depth24,NoDDC ] 21-Dec 10:19:03 <I> [ Sysp: XStuff detection data SaX: ups lost card during probing... abort ] What next to test? Mike -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=227464 ms@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sndirsch@novell.com Status|NEW |NEEDINFO Info Provider| |mszick@morethan.org ------- Comment #5 from ms@novell.com 2006-12-22 01:23 MST ------- The problem is there are two cards which in combination causes the X-Server to crash: Chip: 0 is -> Intel I815 00:02:0 0x8086 0x1132 PCI i810 Chip: 1 is -> ATI 3D Rage Pro 215GP 01:02:0 0x1002 0x4750 AGP ati i810 + ati driver doesn't work. I assume this is more or less a bug in either one or both drivers. As a workaround I would suggest to select one device only. To activate only the Intel chip call: sax2 -c 0 To activate only the ATI chip call: sax2 -c 1 -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=227464 ------- Comment #6 from mszick@morethan.org 2006-12-22 13:13 MST ------- Need clarification here ... 'ati' is not a driver - it is a wrapper which selects one of three drivers. What is the failure combination? ati wrapper + i810? one of the wrapped drivers + i810? Any of the four + i810? If the man pages are to be believed, not all three drivers share the same spelling of options. Does the wrapper fix that? such as: r128:radeon:ChipID -> BusID How about radeon:'Option DDCMode <default off>' and r128: no DDC option? What is the name of the other man page? 'man atimisc' finds nothing. Since I have one available for testing, let us narrow this down far enough to refer it out to the proper maintainer. In case your database does not have the HP C2746A monitor in it: (The sax2 never asks for monitor type or specs, even though it has the driver profile set at NoDDC. And this monitor does not do vga - so you have to ask, not just fall-back to vga) Section "Monitor" Identifier "HP C2746A" HorizSync 60-85 VertRefresh 50-90 EndSection Both cards can generate, and both monitors can display: *Driver mode "1280x1024": 109.0 MHz, 63.7 kHz, 59.9 Hz Modeline "1280x1024" 109.00 1280 1368 1496 1712 1024 1027 1034 1063 -hsync +vsync *Driver mode "1024x768": 94.5 MHz, 68.7 kHz, 84.9 Hz Modeline "1024x768" 94.50 1024 1096 1200 1376 768 771 775 809 -hsync +vsync How else can I help you narrow this down? Does X have a debug/non-dameon mode? Mike -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=227464
------- Comment #7 from sndirsch@novell.com 2006-12-22 14:24 MST -------
An usual failure combination is "
https://bugzilla.novell.com/show_bug.cgi?id=227464 ------- Comment #8 from mszick@morethan.org 2006-12-22 16:11 MST ------- Failure combination <any driver> + i810 :-< Not surprising - The Intel Corp (windows) driver has this i815 doing things that the X-i810 man page says can only be done i830 or newer. Which makes one suspect the author did not fully research the chip. Will try both of the individual sax2 (single card) configuration commands, save and compare logs, *.conf, X logs - maybe get a handle on the problem. Since openSUSE is expected to become one OS on a dual boot machine, with a Redmond product as the other - Plus this hardware setup works under WindowsXP-SP2 - Should a bug be opened on both the web page(s) that say the installer can configure dual displays and the sax2 man page which says the same? Perhaps re-open this as a bug on SaX2 as a feature request that it report the unusable driver configuration rather than simply aborting. Or even better, query the bios for the primary card, configure that one and report why it could not configure the other(s). Looking at its log file I think it already could do that. Mike -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=227464 ------- Comment #9 from mszick@morethan.org 2006-12-23 06:04 MST ------- No framebuffer running. No X-server running. Text console (display, kbd, mouse) on card 1. sax2 -c 0 --vesa 0:1280x1024@60 Did get some log file before file i/o stopped ... Noted: *) sax2 tried to configure card 1 despite the command line. (hello blank text console) *) sax2 log showed it _would_ have written xorg.conf with the default display as 640x480 - 1/3 the slowest hsync the monitor can display. *) X11 looks like it was alive and well in the i810 driver until it loaded libGLcore. Problem needs more testing, perhaps ssh'ing into the box and then running sax2 with a known working xorg.conf will lead to more information. (or less corrupted filesystem). Mike -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=227464 ------- Comment #10 from mszick@morethan.org 2006-12-24 08:21 MST ------- (In reply to comment #4)
SaX: initializing please wait SaX: your current configuration will not be read in
SaX: no X-Server running SaX: will start own server if needed SaX: ups lost card during probing... abort SaX: something went wrong while X was called with -probeonly SaX: try to call 'sax2 -p' and select a single device ? abort
prompt# sax2 -p Chip: 0 is -> Intel I815 00:02:0 0x8086 0x1132 PCI i810 Chip: 1 is -> ATI 3D Rage Pro 215GP 01:02:0 0x1002 0x4750 AGP ati
This _is_ _not_ the correct discripton for Chip 1 - Chip 1 is PCI _NOT_ AGP That is; _both_ video controllers are _PCI_ - a hardware requirement for dual monitor use of the Intel I81x chipset series.
(Which is correct by the way)
Wrong! Ignore above comment!
Monitor which returns DDC is on Chip 1
Motherboard BIOS : PhoenixBIOS Version 4.0 Release 6.0 HP Build: 04/11/01 9:10:45 IP.01.07US
Settings: Video Primary: PCI Multi-Display: Enabled
BIOS does not allow 'Multi-Display' to be enabled unless the non-embedded display is set as the BIOS primary.
This is not a flaky BIOS as I first thought, it is a hardware requirement. Ref: Intel 815 Chipset: Graphics Controller; Programmer's Reference Manual Section 2.3.1.1 Supported Single Monitor and Multi-monitor Configuratuinsl "For modern operating systems that have multiple monitor support, the primary graphics device must not be the Intel 815 chipset graphics controller or an AGP graphics card. These devices [internal gc or external AGP] can only serve as secondary graphics devices in a multi-monitor configuration. It is important to understand that there is no support for simultaneous operation of the internal graphics device and an AGP graphics card."
Note - this installation: The internal graphics device is PCI 0:2:0 The external graphics device is PCI 1:2:0 _and_ _not_ an AGP card (it is physically impossible to put an AGP card in this system). This configuration conforms to the first column of section "Multi-monitor" in configuration table on the page following the above quote. I.E: Primary monitor - Non-AGP (PCI) graphics card Secondary monitor - Internel Graphics With this hardware setup, it is important that sax2 detect the primary card as an ATI _PCI_ card not as an ATI _AGP_ card. (If your keeping score, this is problem #3 with sax2)
M$-WindowsXP will use either card/monitor as the primary monitor in either single or dual head display modes. (I.E: it switches to the card and non-DDC monitor when the graphic drivers load.)
SaX.log:
/************* SaX2 log : SaX2 version 8.1 - SVN Release: 1.49 2003/03/17 ************** SVN RELEASE : 1254 : DESCRIPTION : X11 configuration log file to collect information : about detection, startup and configuration. : There are three parts of logging: : --- : 1) INIT ( detection, 3D ) : 2) STARTUP ( xorg.conf, X11 log, glxinfo ) : 3) CONFIG ( config actions ) : --- : VERSION : SaX2 compiled for: [openSUSE 10.2 (i586)] PARAMETER : -r -a -r : LOG DATE : Thu Dec 21 10:18:29 CST 2006 *************/ ============================ Framebuffer Info: ---------------------------- Framebuffer not active
21-Dec 10:18:31 <I> Initializing... 21-Dec 10:18:34 <I> [ Sysp: Mouse detection data Mouse0 => Protocol : explorerps/2 Mouse0 => Device : /dev/input/mice Mouse0 => Buttons : 7 Mouse0 => Wheel : 1 Mouse0 => Emulate : 0 Mouse0 => Name : GenPS/2 Genius Mouse Mouse0 => VendorID : 0x0210 Mouse0 => DeviceID : 0x0015 Mouse0 => Profile : <undefined> Mouse0 => RealDevice : <undefined> Mouse0 => NutShell : 0 ] 21-Dec 10:18:35 <I> [ Sysp: Keyboard detection data Keyboard0 => XkbModel : pc104 Keyboard0 => XkbLayout : us Keyboard0 => Name : AT Translated Set 2 keyboard Keyboard0 => VendorID : 0x0211 Keyboard0 => DeviceID : 0x0001 Keyboard0 => Profile : <undefined> Keyboard0 => RealDevice : /dev/input/event1 ] 21-Dec 10:18:58 <I> [ Sysp: Server detection data Card0 => DomainId : 0x0 Card0 => BusId : 0x1 Card0 => SlotId : 0x02 Card0 => FuncId : 0x0 Card0 => Vendor : ATI Card0 => Device : 3D Rage Pro 215GP Card0 => VID : 0x1002 Card0 => DID : 0x4750 Card0 => Module : ati Card0 => BusType : AGP Card0 => Detected : 2 Card0 => Flag : DEFAULT Card0 => SUB-VID : 0x1002 Card0 => SUB-DID : 0x0080 Card0 => DrvProfile : <undefined>
Card1 => DomainId : 0x0 Card1 => BusId : 0x0 Card1 => SlotId : 0x02 Card1 => FuncId : 0x0 Card1 => Vendor : Intel Card1 => Device : I815 Card1 => VID : 0x8086 Card1 => DID : 0x1132 Card1 => Module : i810 Card1 => BusType : PCI Card1 => Detected : 2 Card1 => Flag : DEFAULT Card1 => SUB-VID : 0x103c Card1 => SUB-DID : 0x1245 Card1 => DrvProfile : Depth24,NoDDC ] 21-Dec 10:19:03 <I> [ Sysp: XStuff detection data SaX: ups lost card during probing... abort ]
What next to test?
Mike
-- 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.
https://bugzilla.novell.com/show_bug.cgi?id=227464 ms@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|mszick@morethan.org | ------- Comment #11 from ms@novell.com 2006-12-29 09:22 MST ------- What is that huge amount of information all about ? - The information of PCI or AGP in the sax2 -p output may be wrong because the heuristic to check that is not fool-proof. Anyway it doesn't matter because it's only information to the user and has exactly zero technical background. I will change that in the future as soon as it is possible to detect whether the card is PCI / AGP or PCIE. If this is not possible I will remove that information from the output. Anyway this has nothing to do with the problem mentioned in this bug report. So if you don't mind don't care for the moment, thanks - In reply to comment #9: sax2 -c 0 --vesa 0:1280x1024@60 why ---vesa ? Could you simply call: init 3 sax2 -r -c 0 -a and send the files: /var/log/SaX.log /etc/X11/xorg.conf and nothing more please :-) Thanks -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=227464 ms@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |mszick@morethan.org -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=227464 ------- Comment #12 from mszick@morethan.org 2006-12-29 09:54 MST ------- (In reply to comment #11)
What is that huge amount of information all about ?
Off topic, but easy - I have the time and hardware configuration available for testing.
- The information of PCI or AGP in the sax2 -p output may be wrong because the heuristic to check that is not fool-proof. Anyway it doesn't matter because it's only information to the user and has exactly zero technical background. I will change that in the future as soon as it is possible to detect whether the card is PCI / AGP or PCIE.
OK - they mark it as a known problem - why? Because of the quote from the Intel manual - PCI & AGP is not possible; PCI & PCI is, and is documented. So if you can't reliably detect which hardware configuration (PCI&PCI / PCI&AGP) your utility should not proceed beyond that point.
If this is not possible I will remove that information from the output. Anyway this has nothing to do with the problem mentioned in this bug report. So if you don't mind don't care for the moment, thanks
- In reply to comment #9: sax2 -c 0 --vesa 0:1280x1024@60
why ---vesa ?
Copied from the documentation - do we need a documentation bug also? The intent was that the utility would mark that as either the default or the only mode available. It did not, it set vga as the default mode. Monitor does not support vga and does not return DDC - so this option must be the controlling option.
Could you simply call:
init 3 sax2 -r -c 0 -a
and send the files:
/var/log/SaX.log /etc/X11/xorg.conf
and nothing more please :-)
Will try again, but I can not keep this machine in a testing mode forever unless you wish to purchase debug support. Mike
Thanks
-- 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.
https://bugzilla.novell.com/show_bug.cgi?id=227464 ------- Comment #13 from mszick@morethan.org 2006-12-30 08:56 MST ------- Created an attachment (id=111219) --> (https://bugzilla.novell.com/attachment.cgi?id=111219&action=view) Output of sax2 -r -c 0 -a Of note, the section 'XStuff detection data' is from the card 1 (ati) and that monitor (Philips) - not from card 0 (i815 and HP monitor). -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=227464 ------- Comment #14 from mszick@morethan.org 2006-12-30 09:05 MST ------- Created an attachment (id=111223) --> (https://bugzilla.novell.com/attachment.cgi?id=111223&action=view) Generated file of sax2 -r -c 0 -a Of note; Section "Monitor" written from information obtained over card 1 (ati) and its attached monitor, not from card 0 (i815) and the HP monitor. Same with sections screen and modes. The Section "Device" looks correct for card 0 First guess: the reading of the information from the wrong card and monitor prevented (or bypassed) the detection of missing information from the card marked "NoDDC" (A.K.A: -c 0). -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=227464 mszick@morethan.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|mszick@morethan.org | ------- Comment #15 from mszick@morethan.org 2006-12-30 09:07 MST ------- Attachments made as requested. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=227464 ms@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |DUPLICATE ------- Comment #16 from ms@novell.com 2007-01-05 08:18 MST ------- sorry but your guesses are not correct. The DDC information is obtained from the BIOS of the system by calling an interrupt (int10) your BIOS reports the same DDC information for both channels. The information here is from a Phillips device with ID:PHL0018 ... your BIOS doesn't have any information of a HP monitor. This is a BIOS bug. - the file you attached in comment #14 looks good to me it is as correct as it can be concerning the BIOS information problem. It contains one device section with the correct bus ID for the Intel card. It is a valid file - You are using the i810 Intel driver which depends on the BIOS completely. This includes resolution information as well. If your BIOS doesn't have the mode 1280x1024 it can't be displayed even if the configuration is correct. Please refer to bug: #201338 and check if patching the BIOS fixes your resolution problem... if this is the major problem we are talking about. 915resolution --help is also interesting in that area *** This bug has been marked as a duplicate of bug 201338 *** -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=227464 ------- Comment #17 from mszick@morethan.org 2007-01-05 10:19 MST ------- (In reply to comment #16)
sorry but your guesses are not correct. The DDC information is obtained from the BIOS of the system by calling an interrupt (int10) your BIOS reports the same DDC information for both channels. The information here is from a Phillips device with ID:PHL0018 ... your BIOS doesn't have any information of a HP monitor. This is a BIOS bug.
Interesting that WindowsXP - using the Intel i815 'final' driver, the same driver whose source was donated to X.org, works fine. At least as a single desktop spread across both monitors.
- the file you attached in comment #14 looks good to me it is as correct as it can be concerning the BIOS information problem. It contains one device section with the correct bus ID for the Intel card. It is a valid file
- You are using the i810 Intel driver which depends on the BIOS completely. This includes resolution information as well. If your BIOS doesn't have the mode 1280x1024 it can't be displayed even if the configuration is correct.
Please refer to bug: #201338 and check if patching the BIOS fixes your resolution problem... if this is the major problem we are talking about.
Please mark bug 201338 such that I can access and read it - it is currently marked 'Novell Employee Only' - need 'view only' access to read it. Mike
915resolution --help
is also interesting in that area
*** This bug has been marked as a duplicate of bug 201338 ***
-- 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.
participants (1)
-
bugzilla_noreply＠novell.com