Re: Custom modeline in 10-monitor.conf?
On Sat, Dec 4, 2010 at 12:57 PM, Felix Miata mrma...@earthlink.net wrote: On 2010/12/04 12:23 (GMT-0800) Alan Coopersmith composed: Robert wrote: I upgraded xorg-server and I noticed it didn't read my settings. I figured that the new xorg probably must have deprecated the xorg.conf file, and that I would have to configure it in the new way of using /etc/X11/xorg.conf.d instead. /etc/X11/xorg.conf is not deprecated, and is still read by the upstream code. Some input device entries there are ignored since the advent of input hotplug, but that's been true since Xorg 1.4 or so. /etc/X11/xorg.conf.d extends /etc/X11/xorg.conf, but does not replace it. /etc/X11/xorg.conf.d is intended to replace .fdi files for input device configuration that were used by HAL for platforms which have moved off HAL. And sure enough, the arch linux wiki said that 10-monitor.conf is the new config file for monitor settings. That's a file created by your distro and a choice they've made to put monitor settings there. (Sorry, I don't know why your driver isn't honoring your modeline, but it shouldn't be because of the file you put it in. I would bet it has a lot more to do with the Intel driver doing modesetting in the kernel instead of Xorg since the advent of KMS.) In testing *buntu*, Factory, Cooker Rawhide I've been seeing more than just modelines being ignored in xorg.conf but not in xorg.conf.d/, and as yet have not found a pattern to help find out what is causing it. Could this really be some KMS kernel fault? see e.g. http://lists.x.org/archives/xorg-driver-ati/2010-November/018097.html What are those wanting custom user config and exporting XORGCONFIG to do it supposed to do when their alternate xorg.conf files are not obeyed like they used to be? I think I know what the reason might be (since I wrote the xorg.conf.d code). In order to maintain the input option semantics where each subsequent InputClass takes precedence over the previous, xorg.conf is the last .conf file read. However, this might conflict with the output option semantics where the first match found is used. So, my guess is that the modeline is being found in xorg.conf.d and doesn't continue to look for options. I haven't looked at it, but it wouldn't be hard to make the server keep looking for output sections to use instead of stopping at the first. My intention wasn't to allow multiple Device/Monitor/Screen sections in xorg.conf.d installed by the distro. It seems like 10-monitor.conf is being generated on the fly and these aren't generic settings. Device/Monitor/Screen aren't really built to have multiple sections like InputClass. -- Dan ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Custom modeline in 10-monitor.conf?
I upgraded xorg-server and I noticed it didn't read my settings. I figured that the new xorg probably must have deprecated the xorg.conf file, and that I would have to configure it in the new way of using /etc/X11/xorg.conf.d instead. And sure enough, the arch linux wiki said that 10-monitor.conf is the new config file for monitor settings. I looked at a couple of examples on the internet and it seemed easy. So I migrated my xorg.conf monitor settings to 10-monitor.conf, but my custom modelines doesn't work. I'll attach the 10-monitor.conf and the Xorg.0.log to this message. From what I can understand of this, it seems that it thinks it should use the modelines on the laptop monitor instead of the external monitor, and therefore discards them since they can't be used on that monitor. Did I configure something incorrectly? As you can see from the config file and the log, I'm using an Intel GMA 965 gpu. The reason I need these modelines is because the 965 is not powerful enough to output at 2048x1...@75hz, but it IS capable of outputting it at 2048x1...@70. The same is true with the other modelines I have. I tried asking on the arch linux forum since that's the distro I use, but no one answered so hopefully this is a better place to ask. Section Monitor IdentifierLaptop Monitor OptionDPMS EndSection Section Monitor IdentifierViewSonic P227f VendorNameViewSonic HorizSync30-130 VertRefresh50-160 OptionPreferredMode 2048x1...@70 OptionDPMS Modeline 2048x1...@70 317.78 2048 2216 2440 2832 1536 1537 1540 1603 -hsync +vsync Modeline 1920x1...@82 324.72 1920 2064 2288 2640 1440 1441 1444 1500 -hsync +vsync Modeline 1280x1...@100 185.24 1280 1344 1504 1728 1024 1025 1028 1072 +hsync +vsync Modeline 1280x1...@120 213.16 1280 1344 1504 1728 1024 1025 1028 1072 +hsync +vsync Modeline 1600x1...@100 270.00 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync EndSection Section Device IdentifierIntel X3100 Driverintel BusIDPCI:0:2:0 Option Monitor-VGA ViewSonic P227f Option Monitor-LVDS Laptop Monitor EndSection Section Screen IdentifierScreen0 DeviceIntel X3100 MonitorViewSonic P227f DefaultDepth24 SubSection Display Depth24 Modes 2048x1...@70 1920x1...@82 1600x1...@100 1280x1...@100 1280x1...@120 2048x1536 1920x1440 1796x1344 1600x1200 1280x1024 1152x864 1024x768 832x624 800x600 640x480 720x400 EndSubSection EndSection [ 2600.012] X.Org X Server 1.9.2 Release Date: 2010-10-30 [ 2600.014] X Protocol Version 11, Revision 0 [ 2600.015] Build Operating System: Linux 2.6.35-ARCH x86_64 [ 2600.016] Current Operating System: Linux lappis 2.6.36-ARCH #1 SMP PREEMPT Wed Nov 24 00:39:57 CET 2010 x86_64 [ 2600.017] Kernel command line: root=/dev/disk/by-uuid/69ff7721-e0f8-4dae-a229-ad9cfa3294aa ro fastboot quiet [ 2600.018] Build Date: 01 November 2010 10:29:19PM [ 2600.018] [ 2600.019] Current version of pixman: 0.20.0 [ 2600.020] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 2600.022] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 2600.025] (==) Log file: /var/log/Xorg.0.log, Time: Tue Nov 30 06:41:15 2010 [ 2600.026] (==) Using config directory: /etc/X11/xorg.conf.d [ 2600.028] (==) No Layout section. Using the first Screen section. [ 2600.028] (**) |--Screen Screen0 (0) [ 2600.028] (**) | |--Monitor ViewSonic P227f [ 2600.028] (**) | |--Device Intel X3100 [ 2600.028] (==) Automatically adding devices [ 2600.028] (==) Automatically enabling devices [ 2600.028] (WW) The directory /usr/share/fonts/OTF/ does not exist. [ 2600.028] Entry deleted from font path. [ 2600.028] (==) FontPath set to: /usr/share/fonts/misc/, /usr/share/fonts/TTF/, /usr/share/fonts/Type1/, /usr/share/fonts/100dpi/, /usr/share/fonts/75dpi/ [ 2600.028] (==) ModulePath set to /usr/lib/xorg/modules [ 2600.028] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 2600.028] (II) Loader magic: 0x7d3360 [ 2600.028] (II) Module ABI versions: [ 2600.028] X.Org ANSI C Emulation: 0.4 [ 2600.028] X.Org Video Driver: 8.0 [ 2600.028] X.Org XInput driver : 11.0 [ 2600.028] X.Org Server Extension : 4.0 [ 2600.029] (--) PCI:*(0:0:2:0) 8086:2a02:14c0:0026 rev 12, Mem @ 0xf800/1048576, 0xd000/268435456, I/O @ 0x1800/8 [ 2600.029] (--) PCI: (0:0:2:1) 8086:2a03:14c0:0026 rev 12, Mem @ 0xf810/1048576 [ 2600.029] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file
Re: Custom modeline in 10-monitor.conf?
Robert wrote: I upgraded xorg-server and I noticed it didn't read my settings. I figured that the new xorg probably must have deprecated the xorg.conf file, and that I would have to configure it in the new way of using /etc/X11/xorg.conf.d instead. /etc/X11/xorg.conf is not deprecated, and is still read by the upstream code. Some input device entries there are ignored since the advent of input hotplug, but that's been true since Xorg 1.4 or so. /etc/X11/xorg.conf.d extends /etc/X11/xorg.conf, but does not replace it. /etc/X11/xorg.conf.d is intended to replace .fdi files for input device configuration that were used by HAL for platforms which have moved off HAL. And sure enough, the arch linux wiki said that 10-monitor.conf is the new config file for monitor settings. That's a file created by your distro and a choice they've made to put monitor settings there. (Sorry, I don't know why your driver isn't honoring your modeline, but it shouldn't be because of the file you put it in. I would bet it has a lot more to do with the Intel driver doing modesetting in the kernel instead of Xorg since the advent of KMS.) -- -Alan Coopersmith-alan.coopersm...@oracle.com Oracle Solaris Platform Engineering: X Window System ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: Custom modeline in 10-monitor.conf?
On 2010/12/04 12:23 (GMT-0800) Alan Coopersmith composed: Robert wrote: I upgraded xorg-server and I noticed it didn't read my settings. I figured that the new xorg probably must have deprecated the xorg.conf file, and that I would have to configure it in the new way of using /etc/X11/xorg.conf.d instead. /etc/X11/xorg.conf is not deprecated, and is still read by the upstream code. Some input device entries there are ignored since the advent of input hotplug, but that's been true since Xorg 1.4 or so. /etc/X11/xorg.conf.d extends /etc/X11/xorg.conf, but does not replace it. /etc/X11/xorg.conf.d is intended to replace .fdi files for input device configuration that were used by HAL for platforms which have moved off HAL. And sure enough, the arch linux wiki said that 10-monitor.conf is the new config file for monitor settings. That's a file created by your distro and a choice they've made to put monitor settings there. (Sorry, I don't know why your driver isn't honoring your modeline, but it shouldn't be because of the file you put it in. I would bet it has a lot more to do with the Intel driver doing modesetting in the kernel instead of Xorg since the advent of KMS.) In testing *buntu*, Factory, Cooker Rawhide I've been seeing more than just modelines being ignored in xorg.conf but not in xorg.conf.d/, and as yet have not found a pattern to help find out what is causing it. Could this really be some KMS kernel fault? see e.g. http://lists.x.org/archives/xorg-driver-ati/2010-November/018097.html What are those wanting custom user config and exporting XORGCONFIG to do it supposed to do when their alternate xorg.conf files are not obeyed like they used to be? -- The wise are known for their understanding, and pleasant words are persuasive. Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://fm.no-ip.com/ ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: Custom modeline in 10-monitor.conf?
On 12/04/2010 09:23 PM, Alan Coopersmith wrote: Robert wrote: I upgraded xorg-server and I noticed it didn't read my settings. I figured that the new xorg probably must have deprecated the xorg.conf file, and that I would have to configure it in the new way of using /etc/X11/xorg.conf.d instead. /etc/X11/xorg.conf is not deprecated, and is still read by the upstream code. Some input device entries there are ignored since the advent of input hotplug, but that's been true since Xorg 1.4 or so. /etc/X11/xorg.conf.d extends /etc/X11/xorg.conf, but does not replace it. /etc/X11/xorg.conf.d is intended to replace .fdi files for input device configuration that were used by HAL for platforms which have moved off HAL. And sure enough, the arch linux wiki said that 10-monitor.conf is the new config file for monitor settings. That's a file created by your distro and a choice they've made to put monitor settings there. (Sorry, I don't know why your driver isn't honoring your modeline, but it shouldn't be because of the file you put it in. I would bet it has a lot more to do with the Intel driver doing modesetting in the kernel instead of Xorg since the advent of KMS.) Thank you for responding so quickly. Hmm I see. So it's distro specific. That seems rather unintuitive to be honest. But anyway, if I'm not mistaken, xf86-video-intel 2.12.0 also had KMS enabled, and I used that with the previous xorg together with these modelines just fine. When I upgraded, it upgraded both xorg, mesa, intel-dri and xf86-video-intel so it's kinda hard to tell where the issue is. I want to highlight these lines in the Xorg.0.log that seem strange: [ 2600.143] (II) intel(0): Output LVDS1 using monitor section ViewSonic P227f [ 2600.275] (II) intel(0): Output VGA1 has no monitor section It's supposed to be VGA1 that uses the monitor section ViewSonic P227f Is this also affected by the driver? I'm sorry I'm not very good with xorg and how it works :( ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
