need help with xorg.conf
in [Debian]
|
From: Mark Allums on 13 Mar 2010 00:40 On 3/12/2010 12:11 PM, Stephen Powell wrote: > On Fri, 12 Mar 2010 10:58:08 -0500 (EST), Paul E Condon wrote: >> On 20100312_092355, Stephen Powell wrote: >>> >>> Paul, please provide the following information: >>> (5) The contents of /var/log/Xorg.0.log >> There follows 858 lines of the above named file: > > OK, we learn a lot from the /var/log/Xorg.0.log file. > And things are all downhill from there. > > The bottom line: the problem is not with your monitor. The problem is that > the savage driver wants to use the video BIOS to set the video mode. > > The single most important thing you must have in any xorg.conf file is > > Option "UseBIOS" "off" > > This goes in the "Device" section. If you need more help, let me know, > and I'll try to come up with a specific xorg.conf file for you. First of all, thanks for the running commentary, it is well done. Second, it shows that X tends to ignore stuff it finds inconvenient. From one other post, we see that xorg.conf is optional these days, and from a different post (from OP), we see that a somewhat obscure setting is required if you *do* use an xorg.conf file. (Option "UseBIOS" "off" worked.) This shows the tendency of Linux more and more these days to eschew the old philosophy of using simple, user-edited configurations, and instead try to add more and more "magic". Not sure I like this trend. Mark Allums -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/4B9B2254.4030006(a)allums.com
From: Ron Johnson on 13 Mar 2010 01:10 On 2010-03-12 23:27, Mark Allums wrote: > On 3/12/2010 12:11 PM, Stephen Powell wrote: >> On Fri, 12 Mar 2010 10:58:08 -0500 (EST), Paul E Condon wrote: >>> On 20100312_092355, Stephen Powell wrote: >>>> >>>> Paul, please provide the following information: > > >>>> (5) The contents of /var/log/Xorg.0.log >>> There follows 858 lines of the above named file: >> >> OK, we learn a lot from the /var/log/Xorg.0.log file. > > >> And things are all downhill from there. >> >> The bottom line: the problem is not with your monitor. The problem is >> that >> the savage driver wants to use the video BIOS to set the video mode. >> >> The single most important thing you must have in any xorg.conf file is >> >> Option "UseBIOS" "off" >> >> This goes in the "Device" section. If you need more help, let me know, >> and I'll try to come up with a specific xorg.conf file for you. > > > > First of all, thanks for the running commentary, it is well done. > Second, it shows that X tends to ignore stuff it finds inconvenient. Inconvenient, or "can't handle"? Better error/informational messages would help, though. > From one other post, we see that xorg.conf is optional these days, and > from a different post (from OP), we see that a somewhat obscure setting > is required if you *do* use an xorg.conf file. (Option "UseBIOS" "off" > worked.) > > This shows the tendency of Linux more and more these days to eschew the > old philosophy of using simple, user-edited configurations, and instead > try to add more and more "magic". Not sure I like this trend. > As long as there's a manual override, I don't mind the magic. After all, self-configuration (i.e. minimizing the work of the user) is what computers are supposed to do! -- Ron Johnson, Jr. Jefferson LA USA "If God had wanted man to play soccer, he wouldn't have given us arms." Mike Ditka -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/4B9B2BF6.8060304(a)cox.net
From: Stephen Powell on 13 Mar 2010 14:20 On Fri, 12 Mar 2010 23:09:27 -0500 (EST), Tony Nelson wrote: > On 10-03-12 13:11:14, Stephen Powell wrote: >> On Fri, 12 Mar 2010 10:58:08 -0500 (EST), Paul E Condon wrote: >>> ... >>> (--) SAVAGE(0): probed videoram: 32768k >> >> Plenty of video RAM to do true color mode even at 1366x768 >> resolution. >> >> 1366x768x24/1024 = 24588k; 1366x768x32/1024 = 32784k. >> Hmm. If we have to use 32 bits of RAM per pixel, we may not have >> enough. We'll see about that later. >> ... > > You did the math wrong. Use bytes, not bits. Also allow for 3 > buffers. > > (1366*768*3*3)/1024 = 9220K > (1366*768*4*3)/1024 = 12294K I did indeed do the math incorrectly! What a schoolboy mistake! I neglected to convert from bits to bytes. But I don't understand your version either. The correct math, by the way I have traditionally done it, is 1366*768*3/1024 = 3073.5k 1366*768*4/1024 = 4098k This is based on a formula obtained from "Upgrading and Repairing PCs", Sixth Edition, by Scott Mueller, page 443. (This book is quite dated, having been copyrighted in 1996.) Where did you get the stuff about three buffers? Does this have something to do with 3D graphics acceleration? -- .''`. Stephen Powell <zlinuxman(a)wowway.com> : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/1624648332.18895011268507830796.JavaMail.root(a)md01.wow.synacor.com
From: Hugo Vanwoerkom on 13 Mar 2010 14:40 Ron Johnson wrote: > On 2010-03-12 23:27, Mark Allums wrote: >> On 3/12/2010 12:11 PM, Stephen Powell wrote: >>> On Fri, 12 Mar 2010 10:58:08 -0500 (EST), Paul E Condon wrote: >>>> On 20100312_092355, Stephen Powell wrote: >>>>> >>>>> Paul, please provide the following information: >> >> >>>>> (5) The contents of /var/log/Xorg.0.log >>>> There follows 858 lines of the above named file: >>> >>> OK, we learn a lot from the /var/log/Xorg.0.log file. >> >> >>> And things are all downhill from there. >>> >>> The bottom line: the problem is not with your monitor. The problem >>> is that >>> the savage driver wants to use the video BIOS to set the video mode. >>> >>> The single most important thing you must have in any xorg.conf file is >>> >>> Option "UseBIOS" "off" >>> >>> This goes in the "Device" section. If you need more help, let me know, >>> and I'll try to come up with a specific xorg.conf file for you. >> >> >> >> First of all, thanks for the running commentary, it is well done. >> Second, it shows that X tends to ignore stuff it finds inconvenient. > > Inconvenient, or "can't handle"? > > Better error/informational messages would help, though. > >> From one other post, we see that xorg.conf is optional these days, >> and from a different post (from OP), we see that a somewhat obscure >> setting is required if you *do* use an xorg.conf file. (Option >> "UseBIOS" "off" worked.) >> >> This shows the tendency of Linux more and more these days to eschew >> the old philosophy of using simple, user-edited configurations, and >> instead try to add more and more "magic". Not sure I like this trend. >> > > As long as there's a manual override, I don't mind the magic. After > all, self-configuration (i.e. minimizing the work of the user) is what > computers are supposed to do! > I run a 2-seater: 2 graphics cards (nVidia GeForce 6200), 2 monitors, 2 keyboards and 2 mice for 2 separate users. The latest xserver-xorg from Sid (1:7.5+3) freezes the system solid after about 6 minutes *always*. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=567700 'X -configure' sees the 2 cards and the 2 monitors but not the 2 keyboards and the 2 mice and has no clue that it is a 2-seater. Upgrading I have no choice but to pin X to the last version that works faultlessly: 1:7.4+4 But that will eventually get me into trouble of course... Hugo -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/hngpip$k0l$1(a)dough.gmane.org
From: Stephen Powell on 13 Mar 2010 14:40
On Sat, 13 Mar 2010 00:13:38 -0500 (EST), Mark Allums wrote: > I am asking such silly-seeming questions because xorg.conf these days > tends to be ignored by the Xservers if it seems inconvenient to the > driver+server. That is, in my experience, if the monitor is > plug-and-play, then X goes by whatever the monitor hardware reports, and > xorg.conf might as well not exist. I wouldn't say that the X server *ignores* xorg.conf. But it is true that configuration statements such as HorizSync and VertRefresh are ignored in a monitor section if the monitor is plug-and-play. The values reported by the monitor are used instead. I'm not sure I like that behavior. One could argue that point either way, I suppose. On the one hand, one could argue that the monitor knows best, and if it reports its characteristics via EDID, they should be used. On the other hand, one may wish to override these values for the purpose of experimentation. Being an engineer, I want to be able to override things for the purpose of experimentation. But the designers of X are probably more interested in preventing damage to the monitor. Therefore, they took the other approach. In the solution to the problem at hand, I did not override any monitor characteristics. I simply told the driver to use a different (non-default) algorithm for setting the video mode. -- .''`. Stephen Powell <zlinuxman(a)wowway.com> : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/1616584946.18897901268508719875.JavaMail.root(a)md01.wow.synacor.com |