Re: need help with xorg.conf
On Sun, 14 Mar 2010 00:21:29 -0500 (EST), Paul E Condon wrote: On 20100313_223702, Stephen Powell wrote: I've done some digging. Apparently, there is an Option statement That is valid for at least some drivers: Option NoDDC that can be put into the Device section, but it is not documented in the man page for xorg.conf. I'll have to play around to see if I can get it to work. But that will have to wait for tomorrow. It's time for me to go to bed. The option UseBIOS documented in man savage, not in man xorg.conf There is a list of driver man pages in man xorg.conf Yes, I know. But I'm not talking about the UseBIOS option right now. I'm talking about the NoDDC option. I did find it documented on the Internet. For example, see this link - http://www.x.org/archive/X11R6.8.0/doc/rendition5.html. The option was still under development then, and was documented as a previews of coming attractions option. The NoDDC option is referred to in man savage, but the NoDDC option is not a savage-specific option. It is a generic option for the Device section and should be documented in man xorg.conf. I have also seen bug reports complaining about the lack of documentation for the NoDDC option. For example, http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=364610. The above bug report implies that NoDDC is specific to the s3virge driver, but it is actually a generic option that apparently works with all drivers. I just tried it on my machine with the nv driver for an Nvidia video card. It works great! I can now override the DDC2/EDID-probed values if I want or need to! But why is the option not documented? Is that X.Org's version of a disclaimer? The man pages for radeon and savage allude to it, but don't document it. The man page for rendition actually documents it, but as a soon-to-be-implemented feature rather than as a production option. Oh well, at least it works. Sorry to rain on your parade, Ron, -- er, I mean shine sun on your funeral procession -- but you lose this time. -- .''`. Stephen Powellzlinux...@wowway.com : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/354927792.19005391268584194840.javamail.r...@md01.wow.synacor.com
Re: need help with xorg.conf
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 Powellzlinux...@wowway.com : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1624648332.18895011268507830796.javamail.r...@md01.wow.synacor.com
Re: need help with xorg.conf
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 Powellzlinux...@wowway.com : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1616584946.18897901268508719875.javamail.r...@md01.wow.synacor.com
Re: need help with xorg.conf
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-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/hngpip$k0...@dough.gmane.org
Re: need help with xorg.conf
On Sat, 13 Mar 2010 00:27:48 -0500 (EST), Mark Allums wrote: 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 option is specific to the savage driver and is only needed if the monitor's resolution is not supported by the video BIOS. 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. I hear you. For me, I don't mind if the software is smart enough to figure some things out on its own. But I want a way to override things if the defaults are not to my liking. As I mentioned in another post, there are some things, such as HorizSync and VertRefresh, that cannot be overridden for a plug-and-play monitor. I don't like that trend at all. -- .''`. Stephen Powellzlinux...@wowway.com : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1278354342.18901591268510248894.javamail.r...@md01.wow.synacor.com
Re: need help with xorg.conf
Stephen Powell writes: But the designers of X are probably more interested in preventing damage to the monitor. It is rather unlikely that any monitor modern enough to have EDID would be damaged by incorrect synch. It would just shut down if it was sent something it couldn't deal with. -- John Hasler -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87iq90xaye@thumper.dhh.gt.org
Re: need help with xorg.conf
On Sat, 13 Mar 2010 14:45:13 -0500 (EST), John Hasler wrote: Stephen Powell writes: But the designers of X are probably more interested in preventing damage to the monitor. It is rather unlikely that any monitor modern enough to have EDID would be damaged by incorrect synch. It would just shut down if it was sent something it couldn't deal with. One would hope so. But the X server does, in fact, ignore any HorizSync, VertRefresh, Option MaxClock, and a number of other monitor configuration statements when this information is obtained from EDID data. And I don't like that. I want to be able to override things. I want it to use the EDID data if there are no corresponding explicit configuration statements. But an explicit configuration statement should always, in my opinion, be able to override any probed value. -- .''`. Stephen Powellzlinux...@wowway.com : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1254453288.18911201268513890614.javamail.r...@md01.wow.synacor.com
Re: need help with xorg.conf
On 2010-03-13 13:57, Stephen Powell wrote: [snip] if the defaults are not to my liking. As I mentioned in another post, there are some things, such as HorizSync and VertRefresh, that cannot be overridden for a plug-and-play monitor. I don't like that trend at all. Incorrect values might bzzt the monitor?? -- 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-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4b9c04d7.8050...@cox.net
Re: need help with xorg.conf
On Sat, 13 Mar 2010 14:17:10 -0500 (EST), Stephen Powell wrote: 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? I did some more research and answered my own question. I decided to consult a much more recent version of Upgrading and Repairing PCs. In particular, I consulted the Seventeenth Edition, which was copyrighted in 2006, ten years later than the Sixth Edition. It does indeed have to do with 3D graphics. The three buffers are the front buffer, back buffer, and Z buffer. So multiply the numbers above by 3, which is what you said. That's assuming that double buffering is used. But if triple buffering is used, multiply by 4, not 3. -- .''`. Stephen Powellzlinux...@wowway.com : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/993838866.18918121268517038668.javamail.r...@md01.wow.synacor.com
Re: need help with xorg.conf
On Sat, 13 Mar 2010 16:34:15 -0500 (EST), Ron Johnson wrote: On 2010-03-13 13:57, Stephen Powell wrote: As I mentioned in another post, there are some things, such as HorizSync and VertRefresh, that cannot be overridden for a plug-and-play monitor. I don't like that trend at all. Incorrect values might bzzt the monitor?? Possibly, but not likely. In the early days, some of the cheapest monitors did not have protection circuitry that will shut them down if they are driven beyond safe limits. But as another poster pointed out, any monitor modern enough to support plug-and-play (DDC2/EDID) is almost certain to have internal protection circuitry that will shut it down if driven outside of safe limits. Nevertheless, in the unlikely event that I fry my monitor by overriding the EDID specs, I asked for it, didn't I? I'm an engineer. Give me full control. If I fry my monitor, I have no-one to blame but myself. -- .''`. Stephen Powellzlinux...@wowway.com : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1449666297.18920291268517968815.javamail.r...@md01.wow.synacor.com
Re: need help with xorg.conf
Stephan Powell writes: But an explicit configuration statement should always, in my opinion, be able to override any probed value. I agree. It might damage the monitor would not really be an excuse even if there were vulnerable EDID monitors. Newbies are not going to put modelines in xorg.conf: they will never have heard of it. Software should do as it is told. -- John Hasler -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87eijnyj85@thumper.dhh.gt.org
Re: need help with xorg.conf
On 2010-03-13 16:06, Stephen Powell wrote: On Sat, 13 Mar 2010 16:34:15 -0500 (EST), Ron Johnson wrote: On 2010-03-13 13:57, Stephen Powell wrote: As I mentioned in another post, there are some things, such as HorizSync and VertRefresh, that cannot be overridden for a plug-and-play monitor. I don't like that trend at all. Incorrect values might bzzt the monitor?? Possibly, but not likely. In the early days, some of the cheapest monitors did not have protection circuitry that will shut them down if they are driven beyond safe limits. But as another poster pointed out, any monitor modern enough to support plug-and-play (DDC2/EDID) is almost certain to have internal protection circuitry that will shut it down if driven outside of safe limits. Nevertheless, in the unlikely event that I fry my monitor by overriding the EDID specs, I asked for it, didn't I? Stephen, Stephen, Stephen. There's a butt-load more lawyers than there are engineers, and there's 1500 metric ass loads more stupid people than there are engineers. I want control!!! OK, you have control. Bzzt. Why didn't you protect me from myself? I'm an engineer. 0.29% of the population. Give me full control. If I fry my monitor, I have no-one to blame but myself. Three words: hot McDonalds coffee. -- 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-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4b9c0f60.5060...@cox.net
Re: need help with xorg.conf
Stephen Powell writes: But I want a way to override things if the defaults are not to my liking. As I mentioned in another post, there are some things, such as HorizSync and VertRefresh, that cannot be overridden for a plug-and-play monitor. You _could_ cut off pin 12 on the connector... -- John Hasler -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87aaubyio2@thumper.dhh.gt.org
Re: need help with xorg.conf
Ron Johnson writes: Incorrect values might bzzt the monitor?? No way are there any monitors new enough to support EDID but still vulnerable to wrong synch. That problem was solved before EDIDwas invented. Besides, maybe I _want_ to bzzt my monitor. -- John Hasler -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87634zyijq@thumper.dhh.gt.org
Re: need help with xorg.conf
On Sat, 13 Mar 2010 17:19:12 -0500 (EST), Ron Johnson wrote: On 2010-03-13 16:06, Stephen Powell wrote: Nevertheless, in the unlikely event that I fry my monitor by overriding the EDID specs, I asked for it, didn't I? Stephen, Stephen, Stephen. There's a butt-load more lawyers than there are engineers, and there's 1500 metric ass loads more stupid people than there are engineers. I want control!!! OK, you have control. Bzzt. Why didn't you protect me from myself? I'm an engineer. 0.29% of the population. Give me full control. If I fry my monitor, I have no-one to blame but myself. Three words: hot McDonalds coffee. Yes, I've heard of that stupid case. But McDonalds didn't solve that problem by serving cold coffee. They put a disclaimer on the lids saying, Caution: coffee is hot. A disclaimer should be able to solve this problem too. -- .''`. Stephen Powellzlinux...@wowway.com : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/963033316.18925651268520285376.javamail.r...@md01.wow.synacor.com
Re: need help with xorg.conf
On Sat, 13 Mar 2010 17:13:17 -0500 (EST), John Hasler wrote: Stephen Powell writes: But I want a way to override things if the defaults are not to my liking. As I mentioned in another post, there are some things, such as HorizSync and VertRefresh, that cannot be overridden for a plug-and-play monitor. You _could_ cut off pin 12 on the connector... Well, I suppose I *could*. But I don't like that solution. Changing the software to allow overrides is what I want. -- .''`. Stephen Powellzlinux...@wowway.com : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/2117529271.18926321268520707655.javamail.r...@md01.wow.synacor.com
Re: need help with xorg.conf
On 3/13/2010 4:51 PM, Stephen Powell wrote: On Sat, 13 Mar 2010 17:13:17 -0500 (EST), John Hasler wrote: Stephen Powell writes: But I want a way to override things if the defaults are not to my liking. As I mentioned in another post, there are some things, such as HorizSync and VertRefresh, that cannot be overridden for a plug-and-play monitor. You _could_ cut off pin 12 on the connector... Well, I suppose I *could*. But I don't like that solution. Changing the software to allow overrides is what I want. No need to destroy a cable. Just create an adapter. Pin 12 goes in, but doesn't come out.* MAA * Roaches check in, but they don't check out. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4b9c4c30.5040...@allums.com
Re: need help with xorg.conf
On Sat, 13 Mar 2010 21:38:40 -0500 (EST), Mark Allums wrote: On 3/13/2010 4:51 PM, Stephen Powell wrote: On Sat, 13 Mar 2010 17:13:17 -0500 (EST), John Hasler wrote: Stephen Powell writes: But I want a way to override things if the defaults are not to my liking. As I mentioned in another post, there are some things, such as HorizSync and VertRefresh, that cannot be overridden for a plug-and-play monitor. You _could_ cut off pin 12 on the connector... Well, I suppose I *could*. But I don't like that solution. Changing the software to allow overrides is what I want. No need to destroy a cable. Just create an adapter. Pin 12 goes in, but doesn't come out. Yes, that would be better. I'm sure I would have to hand-make such a device. I doubt that I could find such a thing at my local computer store. But still, philosophically, configuration statements should be able to override probed values. I've done some digging. Apparently, there is an Option statement That is valid for at least some drivers: Option NoDDC that can be put into the Device section, but it is not documented in the man page for xorg.conf. I'll have to play around to see if I can get it to work. But that will have to wait for tomorrow. It's time for me to go to bed. -- .''`. Stephen Powellzlinux...@wowway.com : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/188411216.18955951268537822903.javamail.r...@md01.wow.synacor.com
Re: need help with xorg.conf
On 20100313_223702, Stephen Powell wrote: On Sat, 13 Mar 2010 21:38:40 -0500 (EST), Mark Allums wrote: On 3/13/2010 4:51 PM, Stephen Powell wrote: On Sat, 13 Mar 2010 17:13:17 -0500 (EST), John Hasler wrote: Stephen Powell writes: But I want a way to override things if the defaults are not to my liking. As I mentioned in another post, there are some things, such as HorizSync and VertRefresh, that cannot be overridden for a plug-and-play monitor. You _could_ cut off pin 12 on the connector... Well, I suppose I *could*. But I don't like that solution. Changing the software to allow overrides is what I want. No need to destroy a cable. Just create an adapter. Pin 12 goes in, but doesn't come out. Yes, that would be better. I'm sure I would have to hand-make such a device. I doubt that I could find such a thing at my local computer store. But still, philosophically, configuration statements should be able to override probed values. I've done some digging. Apparently, there is an Option statement That is valid for at least some drivers: Option NoDDC that can be put into the Device section, but it is not documented in the man page for xorg.conf. I'll have to play around to see if I can get it to work. But that will have to wait for tomorrow. It's time for me to go to bed. The option UseBIOS documented in man savage, not in man xorg.conf There is a list of driver man pages in man xorg.conf -- Paul E Condon pecon...@mesanetworks.net -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100314052129.ge2...@big.lan.gnu
Re: need help with xorg.conf
On 2010-03-13 16:44, Stephen Powell wrote: On Sat, 13 Mar 2010 17:19:12 -0500 (EST), Ron Johnson wrote: On 2010-03-13 16:06, Stephen Powell wrote: Nevertheless, in the unlikely event that I fry my monitor by overriding the EDID specs, I asked for it, didn't I? Stephen, Stephen, Stephen. There's a butt-load more lawyers than there are engineers, and there's 1500 metric ass loads more stupid people than there are engineers. I want control!!! OK, you have control. Bzzt. Why didn't you protect me from myself? I'm an engineer. 0.29% of the population. Give me full control. If I fry my monitor, I have no-one to blame but myself. Three words: hot McDonalds coffee. Yes, I've heard of that stupid case. But McDonalds didn't solve that problem by serving cold coffee. They put a disclaimer on the lids saying, Caution: coffee is hot. A disclaimer should be able to solve this problem too. People want hot coffee. Only 0.29% of the population wants to maybe fry their LCD. Besides, (probably understating) 95% of people use either Windows or Mac, and want their LCDs auto-configured. Manufacturers play the odds, and apparently so do the X Dev Team. I'd ask them why. -- 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-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4b9c7fe1.4030...@cox.net
Re: need help with xorg.conf
On 03/12/10 07:42, Paul E Condon wrote: I have a cheap flat screen monitor on one of my computers. I works nicely, but not perfectly with Lenny. But in a much inferior way when I switch to Squeeze. In particular: The screen is 1366x768 according to the user manual that came with it. Under Lenny, X chooses to run it at 1280x768 which is OK, but Under Squeeze, X chooses 1024x768 which makes things that should be circle into broad elipses. And wastes a lot of the resolution on over-size characters. I would like to try composing some configuration lines and inserting them in a conf file, xorg.conf, I think, but I'm not sure. Some quidance would be greatly appreciated. Hello Paul, As of my experience the automatic configuration did not work so I manually configured the resolution following these steps (NOTEs : change the values to suit your hardware and be sure the video card supports the resolution and try to also follow xorg.conf man page ---) 1 - I found the suggested monitor resolution (1920x1...@60hz) in the User Manual 2 - I used the gtf utility to calculate a vesa compliant ModeLine, running at the command prompt the following: gtf 1920 1080 60 3 - I Inserted in xorg.conf (section Monitor) the ModeLine that I got in step 2 (naming it 1920x1080_60.00) 4 - I set up VertRefresh e HorizSync (section Monitor) according to the monitor specs 5 - I inserted in xorg.conf (section Screen, subsection Display) in the Modes option listing the already found 1920x1080_60.00 ModeLine cheers d -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/blu0-smtp33c1066e4c76d2c7a307eadc...@phx.gbl
Re: need help with xorg.conf
On Thu, 11 Mar 2010 23:42:16 -0700, Paul E Condon wrote: (...) The screen is 1366x768 according to the user manual that came with it. Under Lenny, X chooses to run it at 1280x768 which is OK, but Under Squeeze, X chooses 1024x768 which makes things that should be circle into broad elipses. And wastes a lot of the resolution on over-size characters. I would like to try composing some configuration lines and inserting them in a conf file, xorg.conf, I think, but I'm not sure. I would try first to get the recommended resolution (1366x...@60) by using xrandr on-the-fly to test things: http://wiki.debian.org/XStrikeForce/HowToRandR12 Once accomplished that, you can go on with another fancy settings on xorg.conf file. Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2010.03.12.09.54...@gmail.com
Re: need help with xorg.conf
On 2010-03-12 03:31, daniele wrote: On 03/12/10 07:42, Paul E Condon wrote: I have a cheap flat screen monitor on one of my computers. I works nicely, but not perfectly with Lenny. But in a much inferior way when I switch to Squeeze. In particular: The screen is 1366x768 according to the user manual that came with it. Under Lenny, X chooses to run it at 1280x768 which is OK, but Under Squeeze, X chooses 1024x768 which makes things that should be circle into broad elipses. And wastes a lot of the resolution on over-size characters. I would like to try composing some configuration lines and inserting them in a conf file, xorg.conf, I think, but I'm not sure. Some quidance would be greatly appreciated. Hello Paul, As of my experience the automatic configuration did not work so I manually configured the resolution following these steps (NOTEs : change the values to suit your hardware and be sure the video card supports the resolution and try to also follow xorg.conf man page ---) 1 - I found the suggested monitor resolution (1920x1...@60hz) in the User Manual 2 - I used the gtf utility to calculate a vesa compliant ModeLine, running at the command prompt the following: gtf 1920 1080 60 3 - I Inserted in xorg.conf (section Monitor) the ModeLine that I got in step 2 (naming it 1920x1080_60.00) 4 - I set up VertRefresh e HorizSync (section Monitor) according to the monitor specs 5 - I inserted in xorg.conf (section Screen, subsection Display) in the Modes option listing the already found 1920x1080_60.00 ModeLine What monitor, video card, video driver and x.org version do you use? This auto-configured perfectly: - Hanns-G HH251 - Nvidia 7300SE - nividia v190.42 blob - every Sid x.org since Nov-2009 -- 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-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4b9a11c7.9020...@cox.net
Re: need help with xorg.conf
On Fri, 12 Mar 2010 09:54:49 + (UTC) Camaleón noela...@gmail.com wrote: Hello Camaleón, I would try first to get the recommended resolution (1366x...@60) by using xrandr on-the-fly to test things: IM(admittedly limted)E, if X doesn't get the resolution right, xrandr won't be able to detect it any better. Here, X runs at 1280x1024, but the monitor is capable of 1680x1050 xrandr outputs; Screen 0: minimum 640 x 480, current 1280 x 1024, maximum 1280 x 1024 default connected 1280x1024+0+0 0mm x 0mm 1280x1024 0.0* 1024x7680.0 800x600 0.0 640x480 0.0 Note the maximum is incorrect. In fact, doing X -configure resulted in errors, so I've got to write an xorg.conf file to sort the issue out. -- Regards _ / ) The blindingly obvious is / _)radnever immediately apparent You're the psychotic daughter of a psychotic mother Pure Mania - The Vibrators signature.asc Description: PGP signature
Re: need help with xorg.conf
On Fri, 12 Mar 2010 12:35:16 +, Brad Rogers wrote: On Fri, 12 Mar 2010 09:54:49 + (UTC) Camaleón wrote: Hello Camaleón, I would try first to get the recommended resolution (1366x...@60) by using xrandr on-the-fly to test things: IM(admittedly limted)E, if X doesn't get the resolution right, xrandr won't be able to detect it any better. To be sincere, nowadays that X in dinamically setup, I'm not sure. I had previous experiences with xorg configuration that couldn't properly detect the display resolution but just by forcing it (writing up in xorg.conf file) it just worked :-? Here, X runs at 1280x1024, but the monitor is capable of 1680x1050 Also, using a digital output -DVI instead VGA- (if available) can help X to detect the screen size and adjust it accordingly. xrandr outputs; Screen 0: minimum 640 x 480, current 1280 x 1024, maximum 1280 x 1024 default connected 1280x1024+0+0 0mm x 0mm 1280x1024 0.0* 1024x7680.0 800x600 0.0 640x480 0.0 Note the maximum is incorrect. In fact, doing X -configure resulted in errors, so I've got to write an xorg.conf file to sort the issue out. Another thing to look into is the driver in use. Different drivers deliver different results. Yes, I know that not everyone likes using closed drivers but is just another option to test. Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2010.03.12.14.13...@gmail.com
Re: need help with xorg.conf
On Fri, 12 Mar 2010 01:42:16 -0500 (EST), Paul E Condon wrote: I have a cheap flat screen monitor on one of my computers. I works nicely, but not perfectly with Lenny. But in a much inferior way when I switch to Squeeze. In particular: The screen is 1366x768 according to the user manual that came with it. Under Lenny, X chooses to run it at 1280x768 which is OK, but Under Squeeze, X chooses 1024x768 which makes things that should be circle into broad elipses. And wastes a lot of the resolution on over-size characters. I would like to try composing some configuration lines and inserting them in a conf file, xorg.conf, I think, but I'm not sure. Some quidance would be greatly appreciated. Paul, please provide the following information: (1) Make and model of your computer (2) Make and model of your video card (3) Make and model of your monitor (4) Your existing /etc/X11/xorg.conf file (5) The contents of /var/log/Xorg.0.log -- .''`. Stephen Powellzlinux...@wowway.com : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/25097827.18615101268403835097.javamail.r...@md01.wow.synacor.com
Re: need help with xorg.conf
On 20100312_092355, Stephen Powell wrote: On Fri, 12 Mar 2010 01:42:16 -0500 (EST), Paul E Condon wrote: I have a cheap flat screen monitor on one of my computers. I works nicely, but not perfectly with Lenny. But in a much inferior way when I switch to Squeeze. In particular: The screen is 1366x768 according to the user manual that came with it. Under Lenny, X chooses to run it at 1280x768 which is OK, but Under Squeeze, X chooses 1024x768 which makes things that should be circle into broad elipses. And wastes a lot of the resolution on over-size characters. I would like to try composing some configuration lines and inserting them in a conf file, xorg.conf, I think, but I'm not sure. Some quidance would be greatly appreciated. Paul, please provide the following information: (1) Make and model of your computer Compaq Presario S3200NX (sn MX31028632) (2) Make and model of your video card integrated graphics on mother board (3) Make and model of your monitor Acer X163W (4) Your existing /etc/X11/xorg.conf file there is no such file. this is a new install done yesterday and I have not yet attempted any hacking (5) The contents of /var/log/Xorg.0.log There follows 858 lines of the above named file: X.Org X Server 1.7.5 Release Date: 2010-02-16 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.32-trunk-686 i686 Debian Current Operating System: Linux cmpq 2.6.32-trunk-686 #1 SMP Sun Jan 10 06:32:16 UTC 2010 i686 Kernel command line: root=UUID=5a02e986-8aa3-4790-aa3f-41f7f565533f ro quiet Build Date: 16 February 2010 08:37:23AM xorg-server 2:1.7.5-1 (bgog...@debian.org) Current version of pixman: 0.16.4 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Fri Mar 12 08:23:27 2010 (II) Loader magic: 0x81e7020 (II) Module ABI versions: X.Org ANSI C Emulation: 0.4 X.Org Video Driver: 6.0 X.Org XInput driver : 7.0 X.Org Server Extension : 2.0 (++) using VT number 7 (--) PCI:*(0:1:0:0) 5333:8d04:1462:3908 S3 Inc. VT8375 [ProSavage8 KM266/KL266] rev 0, Mem @ 0xe100/524288, 0xd800/134217728, BIOS @ 0x/65536 (==) Using default built-in configuration (30 lines) (==) --- Start of built-in configuration --- Section Device Identifier Builtin Default savage Device 0 Driver savage EndSection Section Screen Identifier Builtin Default savage Screen 0 Device Builtin Default savage 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 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 ServerLayout Identifier Builtin Default Layout Screen Builtin Default savage Screen 0 Screen Builtin Default vesa Screen 0 Screen Builtin Default fbdev Screen 0 EndSection (==) --- End of built-in configuration --- (==) ServerLayout Builtin Default Layout (**) |--Screen Builtin Default savage Screen 0 (0) (**) | |--Monitor default monitor (**) | |--Device Builtin Default savage Device 0 (==) No monitor specified for screen Builtin Default savage Screen 0. Using a default monitor configuration. (**) |--Screen Builtin Default vesa Screen 0 (1) (**) | |--Monitor default monitor (**) | |--Device Builtin Default vesa Device 0 (==) No monitor specified for screen Builtin Default vesa Screen 0. Using a default monitor configuration. (**) |--Screen Builtin Default fbdev Screen 0 (2) (**) | |--Monitor default monitor (**) | |--Device Builtin Default fbdev Device 0 (==) No monitor specified for screen Builtin Default fbdev Screen 0. Using a default monitor configuration. (==) Automatically adding devices (==) Automatically enabling devices (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. Entry deleted from font path. (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1,
Re: need help with xorg.conf
On Fri, 12 Mar 2010 14:13:04 + (UTC) Camaleón noela...@gmail.com wrote: Hello Camaleón, On Fri, 12 Mar 2010 12:35:16 +, Brad Rogers wrote: IM(admittedly limted)E, if X doesn't get the resolution right, xrandr won't be able to detect it any better. To be sincere, nowadays that X in dinamically setup, I'm not sure. My experience relates to now. However, what I'm seeing is an improvement on what I got about 6 months ago, when X woudn't even start on this hardware. I had previous experiences with xorg configuration that couldn't properly detect the display resolution but just by forcing it (writing up in xorg.conf file) it just worked :-? Which is what I'll be doing tonight, probably. Also, using a digital output -DVI instead VGA- (if available) can help X to detect the screen size and adjust it accordingly. Sadly, not an option; No DVI o/p on this machine. Another thing to look into is the driver in use. Different drivers deliver different results. Yes, I know that not everyone likes using closed drivers but is just another option to test. I'm not that bothered about whenther I use nv or nvidia, so yes, that opens another avenue for me to explore. -- Regards _ / ) The blindingly obvious is / _)radnever immediately apparent To the ends of the earth, you look for sense in it No Time To Be 21 - The Adverts signature.asc Description: PGP signature
Re: need help with xorg.conf
More information On 20100312_092355, Stephen Powell wrote: On Fri, 12 Mar 2010 01:42:16 -0500 (EST), Paul E Condon wrote: I have a cheap flat screen monitor on one of my computers. I works nicely, but not perfectly with Lenny. But in a much inferior way when I switch to Squeeze. ... snip Both Lenny and Squeeze on this computer are recent, clean installations, each in its own separate partition. Both installations were done with tasksel set for Desktop Environment and Base System. The log file is from the Squeeze install, which is the one that I am most desireous of fixing. -- Paul E Condon pecon...@mesanetworks.net -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100312160501.gg4...@big.lan.gnu
Re: need help with xorg.conf
On 20100312_102211, John W Foster wrote: -Original Message- From: Paul E Condon pecon...@mesanetworks.net To: debian-user@lists.debian.org snip Hi Paul: I read thru the install log from xorg it looks like everything is doing as it should. I am wondering if this new flat screen is a letterbox shaped screen or a standard shaped screen. I suspect this is an aspect ratio issue rather than a screen resolution issue though it may be a combination of both. I have little experience with the letterbox screens but I am planing to buy one soon am studying the list other tings for compatibility as I do not want to incur this type of issue. Please post your solution when you get it going correctly. Best wishes! -- John Foster The pixels are specified to be 0.252mm(H)x0.252mm(V), which implies an aspect ratio of 1366:768. This is close to 16:9, but not exact. To be exact would have to be e.g. 1366:768.375 or 1365.333:768. Both have fractional number of pixels, which of course is impossible. So there must be some 'engineering hack'. I have no idea what ugly hacks are done to make beautiful Xwindows design concept fit with ugly real world of integer arithmetic ;-) What really puzzles me is the fact that two recent installs of X arrive at different kludge solutions -on-the-same-hardware-. -- Paul E Condon pecon...@mesanetworks.net -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100312165417.gh4...@big.lan.gnu
Re: need help with xorg.conf
-Original Message- From: Paul E Condon pecon...@mesanetworks.net To: debian-user@lists.debian.org Subject: need help with xorg.conf Date: Thu, 11 Mar 2010 23:42:16 -0700 I have a cheap flat screen monitor on one of my computers. I works nicely, but not perfectly with Lenny. But in a much inferior way when I switch to Squeeze. In particular: The screen is 1366x768 according to the user manual that came with it. Under Lenny, X chooses to run it at 1280x768 which is OK, but Under Squeeze, X chooses 1024x768 which makes things that should be circle into broad elipses. And wastes a lot of the resolution on over-size characters. I would like to try composing some configuration lines and inserting them in a conf file, xorg.conf, I think, but I'm not sure. Some quidance would be greatly appreciated. -- Paul E Condon pecon...@mesanetworks.net Hi Paul: I read thru the install log from xorg it looks like everything is doing as it should. I am wondering if this new flat screen is a letterbox shaped screen or a standard shaped screen. I suspect this is an aspect ratio issue rather than a screen resolution issue though it may be a combination of both. I have little experience with the letterbox screens but I am planing to buy one soon am studying the list other tings for compatibility as I do not want to incur this type of issue. Please post your solution when you get it going correctly. Best wishes! -- John Foster -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1268410931.28649.5.ca...@brutus
Re: need help with xorg.conf
John W Foster wrote: -Original Message- From: Paul E Condon pecon...@mesanetworks.net To: debian-user@lists.debian.org Subject: need help with xorg.conf Date: Thu, 11 Mar 2010 23:42:16 -0700 I have a cheap flat screen monitor on one of my computers. I works nicely, but not perfectly with Lenny. But in a much inferior way when I switch to Squeeze. In particular: The screen is 1366x768 according to the user manual that came with it. Under Lenny, X chooses to run it at 1280x768 which is OK, but Under Squeeze, X chooses 1024x768 which makes things that should be circle into broad elipses. And wastes a lot of the resolution on over-size characters. I would like to try composing some configuration lines and inserting them in a conf file, xorg.conf, I think, but I'm not sure. Some quidance would be greatly appreciated. X --configure (as root); alter the xorg.conf as desired, test it with X --config xorg.conf.filename, and if you like it, copy the file in /etc/X11/ as xorg.conf -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4b9a7949.70...@gmail.com
Re: need help with xorg.conf
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: (1) Make and model of your computer Compaq Presario S3200NX (sn MX31028632) (2) Make and model of your video card integrated graphics on mother board (3) Make and model of your monitor Acer X163W (4) Your existing /etc/X11/xorg.conf file there is no such file. this is a new install done yesterday and I have not yet attempted any hacking (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. Your Integrated graphics card is (--) PCI:*(0:1:0:0) 5333:8d04:1462:3908 S3 Inc. VT8375 [ProSavage8 KM266/KL266] rev 0, Mem @ 0xe100/524288, 0xd800/134217728, BIOS @ 0x/65536 I thought at first that the stuff within parentheses might be the chipset. But I found out later that I was wrong. We'll see why in a minute. X chose the savage driver. It lists the chipsets which it supports. (II) SAVAGE: driver (version 2.3.1) for S3 Savage chipsets: Savage4, Savage3D, Savage3D-MV, Savage2000, Savage/MX-MV, Savage/MX, Savage/IX-MV, Savage/IX, ProSavage PM133, ProSavage KM133, Twister PN133, Twister KN133, SuperSavage/MX 128, SuperSavage/MX 64, SuperSavage/MX 64C, SuperSavage/IX 128, SuperSavage/IX 128, SuperSavage/IX 64, SuperSavage/IX 64, SuperSavage/IXC 64, SuperSavage/IXC 64, ProSavage DDR, ProSavage DDR-K I'm not sure what to make of this next section. First it says it's defaulting to 16 bit color. (II) SAVAGE(0): Creating default Display subsection in Screen section Builtin Default savage Screen 0 for depth/fbbpp 16/16 (==) SAVAGE(0): Depth 16, (--) framebuffer bpp 16 (==) SAVAGE(0): RGB weight 565 But then it says it's going to use true color mode, which requires at least 24 bits! (==) SAVAGE(0): Default visual is TrueColor And then we have this little tidbit. (==) SAVAGE(0): Using video BIOS to set modes That's trouble. If it uses this method, then you're limited to the video modes that are pre-defined in the video BIOS. And if 1366x768 isn't one of them, too bad. (--) SAVAGE(0): Chip: id 8d04, ProSavage DDR-K There's the actual chipset: ProSavage DDR-K, which is one of the supported chipsets for this driver. (It's the last one listed.) (--) 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. It did find the DDC2/EDID information about your monitor though: (II) SAVAGE(0): Manufacturer: ACR Model: 15 Serial#: 2441181409 (II) SAVAGE(0): Year: 2009 Week: 18 (II) SAVAGE(0): EDID Version: 1.3 (II) SAVAGE(0): Analog Display Input, Input Voltage Level: 0.700/0.700 V (II) SAVAGE(0): Sync: Separate (II) SAVAGE(0): Max Image Size [cm]: horiz.: 34 vert.: 19 (II) SAVAGE(0): Gamma: 2.20 (II) SAVAGE(0): DPMS capabilities: Off; RGB/Color Display (II) SAVAGE(0): Default color space is primary color space (II) SAVAGE(0): First detailed timing is preferred mode (II) SAVAGE(0): redX: 0.637 redY: 0.333 greenX: 0.284 greenY: 0.596 (II) SAVAGE(0): blueX: 0.154 blueY: 0.083 whiteX: 0.313 whiteY: 0.329 These are the VESA standard modes that the monitor supports: (II) SAVAGE(0): Supported established timings: (II) SAVAGE(0): 720x...@70hz (II) SAVAGE(0): 640x...@60hz (II) SAVAGE(0): 640x...@67hz (II) SAVAGE(0): 640x...@72hz (II) SAVAGE(0): 640x...@75hz (II) SAVAGE(0): 800x...@56hz (II) SAVAGE(0): 800x...@60hz (II) SAVAGE(0): 800x...@72hz (II) SAVAGE(0): 800x...@75hz (II) SAVAGE(0): 832x...@75hz (II) SAVAGE(0): 1024x...@60hz (II) SAVAGE(0): 1024x...@70hz (II) SAVAGE(0): 1024x...@75hz More monitor stuff: (II) SAVAGE(0): Manufacturer's mask: 0 (II) SAVAGE(0): Supported standard timings: (II) SAVAGE(0): #0: hsize: 1280 vsize 720 refresh: 60 vid: 49281 (II) SAVAGE(0): Supported detailed timing: (II) SAVAGE(0): clock: 85.5 MHz Image Size: 344 x 193 mm (II) SAVAGE(0): h_active: 1366 h_sync: 1435 h_sync_end 1578 h_blank_end 1790 h_border: 0 (II) SAVAGE(0): v_active: 768 v_sync: 771 v_sync_end 781 v_blanking: 798 v_border: 0 (II) SAVAGE(0): Ranges: V min: 50 V max: 75 Hz, H min: 30 H max: 80 kHz, PixClock max 160 MHz (II) SAVAGE(0): Monitor name: Acer X163W (II) SAVAGE(0): Serial No: LBF080014210 (II) SAVAGE(0): EDID (in hex): (II) SAVAGE(0): 000004721500e1788191 (II) SAVAGE(0): 12130103682213782e1e95a355489827 (II) SAVAGE(0): 155054bfee0081c00101010101010101 (II) SAVAGE(0): 010101010101662156a851001e30458f (II) SAVAGE(0): 3a0058c1101c00fd00324b1e (II) SAVAGE(0): 501a20202020202000fc0041 (II) SAVAGE(0):
Re: need help with xorg.conf
Wow! Thanks. But I need more help. See below. On 20100312_131114, 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: (1) Make and model of your computer Compaq Presario S3200NX (sn MX31028632) (2) Make and model of your video card integrated graphics on mother board (3) Make and model of your monitor Acer X163W (4) Your existing /etc/X11/xorg.conf file there is no such file. this is a new install done yesterday and I have not yet attempted any hacking (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. Your Integrated graphics card is (--) PCI:*(0:1:0:0) 5333:8d04:1462:3908 S3 Inc. VT8375 [ProSavage8 KM266/KL266] rev 0, Mem @ 0xe100/524288, 0xd800/134217728, BIOS @ 0x/65536 I thought at first that the stuff within parentheses might be the chipset. But I found out later that I was wrong. We'll see why in a minute. X chose the savage driver. It lists the chipsets which it supports. (II) SAVAGE: driver (version 2.3.1) for S3 Savage chipsets: Savage4, Savage3D, Savage3D-MV, Savage2000, Savage/MX-MV, Savage/MX, Savage/IX-MV, Savage/IX, ProSavage PM133, ProSavage KM133, Twister PN133, Twister KN133, SuperSavage/MX 128, SuperSavage/MX 64, SuperSavage/MX 64C, SuperSavage/IX 128, SuperSavage/IX 128, SuperSavage/IX 64, SuperSavage/IX 64, SuperSavage/IXC 64, SuperSavage/IXC 64, ProSavage DDR, ProSavage DDR-K I'm not sure what to make of this next section. First it says it's defaulting to 16 bit color. (II) SAVAGE(0): Creating default Display subsection in Screen section Builtin Default savage Screen 0 for depth/fbbpp 16/16 (==) SAVAGE(0): Depth 16, (--) framebuffer bpp 16 (==) SAVAGE(0): RGB weight 565 But then it says it's going to use true color mode, which requires at least 24 bits! (==) SAVAGE(0): Default visual is TrueColor And then we have this little tidbit. (==) SAVAGE(0): Using video BIOS to set modes That's trouble. If it uses this method, then you're limited to the video modes that are pre-defined in the video BIOS. And if 1366x768 isn't one of them, too bad. (--) SAVAGE(0): Chip: id 8d04, ProSavage DDR-K There's the actual chipset: ProSavage DDR-K, which is one of the supported chipsets for this driver. (It's the last one listed.) (--) 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. It did find the DDC2/EDID information about your monitor though: (II) SAVAGE(0): Manufacturer: ACR Model: 15 Serial#: 2441181409 (II) SAVAGE(0): Year: 2009 Week: 18 (II) SAVAGE(0): EDID Version: 1.3 (II) SAVAGE(0): Analog Display Input, Input Voltage Level: 0.700/0.700 V (II) SAVAGE(0): Sync: Separate (II) SAVAGE(0): Max Image Size [cm]: horiz.: 34 vert.: 19 (II) SAVAGE(0): Gamma: 2.20 (II) SAVAGE(0): DPMS capabilities: Off; RGB/Color Display (II) SAVAGE(0): Default color space is primary color space (II) SAVAGE(0): First detailed timing is preferred mode (II) SAVAGE(0): redX: 0.637 redY: 0.333 greenX: 0.284 greenY: 0.596 (II) SAVAGE(0): blueX: 0.154 blueY: 0.083 whiteX: 0.313 whiteY: 0.329 These are the VESA standard modes that the monitor supports: (II) SAVAGE(0): Supported established timings: (II) SAVAGE(0): 720x...@70hz (II) SAVAGE(0): 640x...@60hz (II) SAVAGE(0): 640x...@67hz (II) SAVAGE(0): 640x...@72hz (II) SAVAGE(0): 640x...@75hz (II) SAVAGE(0): 800x...@56hz (II) SAVAGE(0): 800x...@60hz (II) SAVAGE(0): 800x...@72hz (II) SAVAGE(0): 800x...@75hz (II) SAVAGE(0): 832x...@75hz (II) SAVAGE(0): 1024x...@60hz (II) SAVAGE(0): 1024x...@70hz (II) SAVAGE(0): 1024x...@75hz More monitor stuff: (II) SAVAGE(0): Manufacturer's mask: 0 (II) SAVAGE(0): Supported standard timings: (II) SAVAGE(0): #0: hsize: 1280 vsize 720 refresh: 60 vid: 49281 (II) SAVAGE(0): Supported detailed timing: (II) SAVAGE(0): clock: 85.5 MHz Image Size: 344 x 193 mm (II) SAVAGE(0): h_active: 1366 h_sync: 1435 h_sync_end 1578 h_blank_end 1790 h_border: 0 (II) SAVAGE(0): v_active: 768 v_sync: 771 v_sync_end 781 v_blanking: 798 v_border: 0 (II) SAVAGE(0): Ranges: V min: 50 V max: 75 Hz, H min: 30 H max: 80 kHz, PixClock max 160 MHz (II) SAVAGE(0): Monitor name: Acer X163W (II) SAVAGE(0): Serial No: LBF080014210 (II) SAVAGE(0): EDID (in hex): (II) SAVAGE(0): 000004721500e1788191 (II) SAVAGE(0): 12130103682213782e1e95a355489827 (II) SAVAGE(0):
Re: need help with xorg.conf
On Fri, Mar 12, 2010 at 01:11:14PM -0500, Stephen Powell wrote: [...] OK, we learn a lot from the /var/log/Xorg.0.log file. Your Integrated graphics card is (--) PCI:*(0:1:0:0) 5333:8d04:1462:3908 S3 Inc. VT8375 [ProSavage8 KM266/KL266] rev 0, Mem @ 0xe100/524288, 0xd800/134217728, BIOS @ 0x/65536 I thought at first that the stuff within parentheses might be the chipset. But I found out later that I was wrong. We'll see why in a minute. X chose the savage driver. It lists the chipsets which it supports. (II) SAVAGE: driver (version 2.3.1) for S3 Savage chipsets: Savage4, Savage3D, Savage3D-MV, Savage2000, Savage/MX-MV, Savage/MX, Savage/IX-MV, Savage/IX, ProSavage PM133, ProSavage KM133, [... snip a lot of great stuff...] After tossing out all the modes that aren't supported by the video BIOS, or that won't work for some other reason, it decides to reduce the virtual screen size. (--) SAVAGE(0): Virtual size is 1024x768 (pitch 1024) 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. I just wanted to say this is just a fantastic explanation of the log file. nice job. A signature.asc Description: Digital signature
Re: need help with xorg.conf
Andrew Sackville-West wrote: On Fri, Mar 12, 2010 at 01:11:14PM -0500, Stephen Powell wrote: [...] OK, we learn a lot from the /var/log/Xorg.0.log file. Your Integrated graphics card is (--) PCI:*(0:1:0:0) 5333:8d04:1462:3908 S3 Inc. VT8375 [ProSavage8 KM266/KL266] rev 0, Mem @ 0xe100/524288, 0xd800/134217728, BIOS @ 0x/65536 I thought at first that the stuff within parentheses might be the chipset. But I found out later that I was wrong. We'll see why in a minute. X chose the savage driver. It lists the chipsets which it supports. (II) SAVAGE: driver (version 2.3.1) for S3 Savage chipsets: Savage4, Savage3D, Savage3D-MV, Savage2000, Savage/MX-MV, Savage/MX, Savage/IX-MV, Savage/IX, ProSavage PM133, ProSavage KM133, [... snip a lot of great stuff...] After tossing out all the modes that aren't supported by the video BIOS, or that won't work for some other reason, it decides to reduce the virtual screen size. (--) SAVAGE(0): Virtual size is 1024x768 (pitch 1024) 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. I just wanted to say this is just a fantastic explanation of the log file. nice job. A +1 X 10 Wayne -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4b9aa054.10...@gmail.com
[SOLVED] need help with xorg.conf
On Fri, 12 Mar 2010 14:36:07 -0500 (EST), Paul E Condon wrote: Wow! Thanks. You're welcome. I'm glad I could help. But I need more help. See below. ... The log file that you examined was for the Squeeze installation, which had no file named /etc/X11/xorg.conf. So, at first, I was wondering what else must I put in the file? Surely something that identified a Device section, at least. Then I remembered that there was a file, /etc/X11/xorg.conf, in the Lenny installation. When I looked at it, I realized that it was a skeletal generic xorg.conf file that just introduced generic names for required sections. I put your Option line in that, and Lenny went from 1280x768 to the ideal 1366x768 ! I copied that file into the Squeeze partition and it also worked there !!! And !!! we have your wonderful commentary on the /var/log/Xorg.0.log text, for study in how to solve X problems by reading the log. I wonder why there is no generic /etc/X11/xorg.conf installed by Squeeze. X.Org has been working hard for a long time to produce a self-configuring server. They finally succeeded. The Lenny version still requires manual configuration of the keyboard and mouse. The Squeeze version is, for the most part, self-configuring. But even the Squeeze version needs manual configuration tweaking sometimes. And why there is not your magic line pre-configured in /etc/X11/xorg.conf in Lenny. Here is an excerpt from the man page for the savage driver that explains why UseBIOS defaults to yes. -- Option UseBIOS boolean Enable or disable use of the video BIOS to change modes. Ordinarily, the savage driver tries to use the video BIOS to do mode switches. This generally produces the best results with the mobile chips (/MX and /IX), since the BIOS knows how to handle the critical but unusual timing requirements of the various LCD panels supported by the chip. To do this, the driver searches through the BIOS mode list, looking for the mode which most closely matches the xorg.conf mode line. Some purists find this scheme objectionable. If you would rather have the savage driver use your mode line timing exactly, turn off the UseBios option. Note: Use of the BIOS is required for dualhead operation. Default: on (use the BIOS). -- Since your chipset is not one of the /MX or /IX chipsets, and since the modeline to use came directly from the monitor itself, I was confident that we could safely bypass the BIOS and alter the VGA registers directly. Here is a link to a web page that gives an xorg.conf file for Lenny. http://www.wowway.com/~zlinuxman/tp600.htm#ConfigX This is for use in an IBM ThinkPad 600. You can't copy it verbatim, as it is tweaked for this specific laptop. But it may provide a useful template for you. -- .''`. Stephen Powellzlinux...@wowway.com : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/554150029.18715711268425133416.javamail.r...@md01.wow.synacor.com
Re: need help with xorg.conf
On Fri, 12 Mar 2010 14:36:27 -0500 (EST), Andrew Sackville-West wrote: I just wanted to say this is just a fantastic explanation of the log file. nice job. Well, there was other stuff in the log that I skipped over because it wasn't relevant to the problem. But thanks. I am grateful to those from whom I learned this stuff. -- .''`. Stephen Powellzlinux...@wowway.com : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/921643445.18718681268425719673.javamail.r...@md01.wow.synacor.com
Re: need help with xorg.conf
On Fri, Mar 12, 2010 at 11:36:27AM -0800, Andrew Sackville-West wrote: On Fri, Mar 12, 2010 at 01:11:14PM -0500, Stephen Powell wrote: [...] OK, we learn a lot from the /var/log/Xorg.0.log file. Your Integrated graphics card is (--) PCI:*(0:1:0:0) 5333:8d04:1462:3908 S3 Inc. VT8375 [ProSavage8 KM266/KL266] rev 0, Mem @ 0xe100/524288, 0xd800/134217728, BIOS @ 0x/65536 I thought at first that the stuff within parentheses might be the chipset. But I found out later that I was wrong. We'll see why in a minute. X chose the savage driver. It lists the chipsets which it supports. (II) SAVAGE: driver (version 2.3.1) for S3 Savage chipsets: Savage4, Savage3D, Savage3D-MV, Savage2000, Savage/MX-MV, Savage/MX, Savage/IX-MV, Savage/IX, ProSavage PM133, ProSavage KM133, [... snip a lot of great stuff...] After tossing out all the modes that aren't supported by the video BIOS, or that won't work for some other reason, it decides to reduce the virtual screen size. (--) SAVAGE(0): Virtual size is 1024x768 (pitch 1024) 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. I just wanted to say this is just a fantastic explanation of the log file. nice job. 'Twas a truly great read, even for the clueless. -- Kind Regards, Freeman http://bugs.debian.org/release-critical/ -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100312210618.ga4...@europa.office
Re: need help with xorg.conf
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 -- TonyN.:' mailto:tonynel...@georgeanelson.com ' http://www.georgeanelson.com/ -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1268453367.1424...@localhost.localdomain
Re: need help with xorg.conf
On 3/12/2010 10:22 AM, John W Foster wrote: -Original Message- From: Paul E Condonpecon...@mesanetworks.net To: debian-user@lists.debian.org Subject: need help with xorg.conf Date: Thu, 11 Mar 2010 23:42:16 -0700 I have a cheap flat screen monitor on one of my computers. I works nicely, but not perfectly with Lenny. But in a much inferior way when I switch to Squeeze. In particular: The screen is 1366x768 according to the user manual that came with it. Under Lenny, X chooses to run it at 1280x768 which is OK, but Under Squeeze, X chooses 1024x768 which makes things that should be circle into broad elipses. And wastes a lot of the resolution on over-size characters. I would like to try composing some configuration lines and inserting them in a conf file, xorg.conf, I think, but I'm not sure. Some quidance would be greatly appreciated. I never heard of 1366x768, this seems non-standard to me. A wide screen monitor might be 1440x900. What is the diagonal measurement in inches or centimeters? What is the aspect ratio? 4:3, 3:2, 16:10, 16:9? (1366x768 is physically 16:9 assuming square pixels) 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. For the record, my experiences have been with early Squeeze and Sid. Mark Allums (Also, Virtualbox, but my difficulties with X under vbox, I attributed to vbox, since the vbox X driver needs help knowing what the size of the view is---and why it's important to install the additions helper.) -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4b9b1f02.3050...@allums.com
Re: need help with xorg.conf
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-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4b9b2254.4030...@allums.com
Re: need help with xorg.conf
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-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4b9b2bf6.8060...@cox.net
need help with xorg.conf
I have a cheap flat screen monitor on one of my computers. I works nicely, but not perfectly with Lenny. But in a much inferior way when I switch to Squeeze. In particular: The screen is 1366x768 according to the user manual that came with it. Under Lenny, X chooses to run it at 1280x768 which is OK, but Under Squeeze, X chooses 1024x768 which makes things that should be circle into broad elipses. And wastes a lot of the resolution on over-size characters. I would like to try composing some configuration lines and inserting them in a conf file, xorg.conf, I think, but I'm not sure. Some quidance would be greatly appreciated. -- Paul E Condon pecon...@mesanetworks.net -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100312064216.ge4...@big.lan.gnu
Re: need help with xorg.conf
On 2010-03-12 00:42, Paul E Condon wrote: I have a cheap flat screen monitor on one of my computers. I works nicely, but not perfectly with Lenny. But in a much inferior way when I switch to Squeeze. In particular: The screen is 1366x768 according to the user manual that came with it. Under Lenny, X chooses to run it at 1280x768 which is OK, but Under Squeeze, X chooses 1024x768 which makes things that should be circle into broad elipses. And wastes a lot of the resolution on over-size characters. I would like to try composing some configuration lines and inserting them in a conf file, xorg.conf, I think, but I'm not sure. Some quidance would be greatly appreciated. Move away your existing xorg.conf and then try again. Log in as a separate user and see what happens. When moving from a 1280x1024 monitor to one that's 1980x1024, I got really really concerned because the new monitor only functioned at 1280x1024. Then I logged in as root, and it was 1980x1024. Very puzzling! Finally, I thought to peek in the Control Panel, and saw that the Display (or whatever GNOME calls it) -- for *myself* -- was set to 1280x1024. Two seconds later, I'm at 1980x1024. -- 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-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4b99ebff.4070...@cox.net
Re: need help with xorg.conf
On Thu, Mar 11, 2010 at 11:42:16PM -0700, Paul E Condon wrote: I have a cheap flat screen monitor on one of my computers. I works nicely, but not perfectly with Lenny. But in a much inferior way when I switch to Squeeze. In particular: The screen is 1366x768 according to the user manual that came with it. Under Lenny, X chooses to run it at 1280x768 which is OK, but Under Squeeze, X chooses 1024x768 which makes things that should be circle into broad elipses. And wastes a lot of the resolution on over-size characters. I would like to try composing some configuration lines and inserting them in a conf file, xorg.conf, I think, but I'm not sure. Some quidance would be greatly appreciated. -- Paul E Condon pecon...@mesanetworks.net Switch to a text mode virtual terminal (away from X) e.g. Alt-F1 Login as / become root with sudo killall kdm / gdm (killing your running X session). Run X -configure This will endeavour to force the X configuration programs to do a best guess as to your hardware and dump an xorg.conf.new in your home directory as the root user. If you run the command given 'X -config /root/xorg.conf.new' and get the familiar grey background and X shaped cursor (bare X, no window manager) it's working. At that point you can copy the xorg.conf.new file to /etc/X11/xorg.conf and carry on / use it as a basis for your own customisation. All the best, AndyC -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100312075159.ga15...@galactic.demon.co.uk
Re: up-to-date Sid, Need help with xorg.conf
On Fri,05.Jun.09, 17:03:57, Curt Howland wrote: Hi. Running up-to-date Sid. I bought a new monitor, and it seems somewhat limited in its screen modes. The manual gives some particulars, but I can't seem to get dpkg-reconfigure to give me the old interactive way of defining Xwindows. Because it's not needed anymore, especially with new monitors. So, I'm stuck creating my own screen/modline, and I could use a bit of help. The values I want to use are 1360x768, 47.7KHz h., 60Hz v. 24/32 bits of course. Is this the native resolution of the monitor? Xorg should be able to detect and use it automatically. Anyone want to take a stab at it? We can work it through off-list and I'll post a solution when we have it. Try without xorg.conf. Mine has only: Section Device Identifier Configured Video Device Driver nvidia EndSection Regards, Andrei -- If you can't explain it simply, you don't understand it well enough. (Albert Einstein) signature.asc Description: Digital signature
Re: : up-to-date Sid, Need help with xorg.conf
Please reply to the list. Curt Howland wrote: There should be no need for a modeline at all. xorg should detect its available modes and select the best one automatically. Wouldn't that be nice? Too bad it doesn't. What does xrandr say when you run it? It should list detected modes. -- Is it really you, Fuzz, or is it Memorex, or is it radiation sickness? -- Sonic Disruptors comics Eduardo M KALINOWSKI edua...@kalinowski.com.br -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
[Solved] Re: up-to-date Sid, Need help with xorg.conf
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 So trying to make the VGA input on a Sharp TV work, we have the following: Using these elements from Wayne Topa: On Friday 05 June 2009 Wayne Topa linux...@gmail.com wrote: The DFP is for an LCD. Section Device ... Option Metamodes 1680x1050, 1280x1024. 1280x1024 EndSection Section Monitor Identifier Generic Monitor Option DPMS HorizSync 24-831 VertRefresh 56-75 EndSection And starting with Andrew's generic xorg.conf so I'd have the right sections: On Saturday 06 June 2009, Andrew M.A. Cater amaca...@galactic.demon.co.uk was heard to say: Once you're sure no X is running, as root issue the command Xorg -configure This will attempt to generate an old style xorg.conf file based on the Xorg best guess It was otherwise empty of details except the SiS driver definition, but it was good to make sure that the correct headings existed for everything in the new file. So it turned out the answer was to put the screen's input h/v frequencies and their matching pixel MetaModes, as detailed in the manual one at a time, into the xorg.conf and startx until something worked... Option Metamodes 1280x1024 HorizSync 64 VertRefresh 60 ...is the highest resolution for which everything worked. Sadly, the 1360x768 h.47.7 v.60 ends up putting a refresh out of sync error in Xorg.0.log, so the ancient SiS onboard video is living up to its ancientness. And not specifying the frequencies but only the 1360x768 launches X just fine, but puts the screen into an invalid frequencies error. Oh well. On Sat Jun 6 07:54:01 2009, Eduardo M KALINOWSKI edua...@kalinowski.com.br wrote: Please reply to the list. I didn't want the completely obvious statement that autoconfig wasn't working to go to the list. But if that's the way you want it, There should be no need for a modeline at all. xorg should detect its available modes and select the best one automatically. Wouldn't that be nice? Too bad it doesn't. What does xrandr say when you run it? It should list detected modes. Thank you. In fact it does list the widescreen 1360x768 mode I want, but the frequency requirements of the screen do not allow it to be used. So much for a gnarly wide-screen display. I guess I have one more good reason to upgrade this box to an HDMI-output machine. I'm sure this wouldn't have happened with hardware anywhere near new. Thank you to everyone who chimed in with suggestions. The Command Line Rules where automagical stuff fails. Curt- -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iQEVAwUBSisFKy9Y35yItIgBAQLfhwf+JK+Vd/jRMHNlPYe72kgRwkAqbE2J0L/T H0TdGpaE9VemMkjc6d3nMQa5+f+vzXczgd1Wyazv6dV7nGiZoI8VY1unNLp+lKaq u3xy5GaxPrC47Fy9Yi+t0+EysFdBa4vzfb2g3L6wO5ukxV2nPEzwokH9XDbn6eSs NmJpijbkHT2VRNgHXOVy9lRP72Hcx+4fSQpL3CKIiQej6nZjYMSzsOEFsY5R437z adTQ3StjJwqjlVWC/zDlWcSvBigWsyPA+6Pz36tOAvVmH2gYuW6AckZ23VSk/YDw +7pgSQ1DN9ruOk89FZAtEExsMRG0qz/v5cAN/xgwNdIr4zd5iq/jUw== =4a1X -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
up-to-date Sid, Need help with xorg.conf
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi. Running up-to-date Sid. I bought a new monitor, and it seems somewhat limited in its screen modes. The manual gives some particulars, but I can't seem to get dpkg-reconfigure to give me the old interactive way of defining Xwindows. So, I'm stuck creating my own screen/modline, and I could use a bit of help. The values I want to use are 1360x768, 47.7KHz h., 60Hz v. 24/32 bits of course. Anyone want to take a stab at it? We can work it through off-list and I'll post a solution when we have it. Curt- - -- The Magistrate, enrobed in taxes, condemns the thief in stolen rags. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iQEVAwUBSimIPS9Y35yItIgBAQIqmgf9EI6miJHfplBsYkBYrIuIt4BjEq9RdEML EhzdwAmjfQ99x47z4+dw75lBb7xnKdTHHuROmQjMPkuEKoofs7Ji3D+A/gFYynXa Wkmuiu2IVo188Sx02fuCpkPnRXsBtET64v7YrhayFd2e3uQlKshIbPJ4LG77jO1n hcjlpKWIKXtqmdDILbRJuDXBTYs4RtoKPKv3xMZfSK+gr8BoQGdrAXg2b6jLAMoj zJ8dpzb7pPvsekblYSeQkxVSXBUCW43Qq2jARHoOt0sPzG1xL4etHQhdLCgAG95j V7m59Fuj0QdlTxiKatvY2DRveikPXf/hs6fl9Sm1jxgh0TH+EW1LuA== =JSVt -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: up-to-date Sid, Need help with xorg.conf
Curt Howland wrote: Hi. Running up-to-date Sid. I bought a new monitor, and it seems somewhat limited in its screen modes. The manual gives some particulars, but I can't seem to get dpkg-reconfigure to give me the old interactive way of defining Xwindows. So, I'm stuck creating my own screen/modline, and I could use a bit of help. The values I want to use are 1360x768, 47.7KHz h., 60Hz v. 24/32 bits of course. Anyone want to take a stab at it? We can work it through off-list and I'll post a solution when we have it. There should be no need for a modeline at all. xorg should detect its available modes and select the best one automatically. -- It is easier to get forgiveness than permission. Eduardo M KALINOWSKI edua...@kalinowski.com.br -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: up-to-date Sid, Need help with xorg.conf
On Fri, Jun 05, 2009 at 06:54:55PM -0300, Eduardo M KALINOWSKI wrote: Curt Howland wrote: So, I'm stuck creating my own screen/modline, and I could use a bit of help. The values I want to use are 1360x768, 47.7KHz h., 60Hz v. 24/32 bits of course. Anyone want to take a stab at it? We can work it through off-list and I'll post a solution when we have it. There should be no need for a modeline at all. xorg should detect its available modes and select the best one automatically. If all else fails, kill any running X and kill kdm/gdm/xdm. [Use a command line from a VT] Once you're sure no X is running, as root issue the command Xorg -configure This will attempt to generate an old style xorg.conf file based on the Xorg best guess Your xorg.conf file is /root/xorg.conf.new To test the server, run 'X -config /root/xorg.conf.new' If you do that, you should end up with the classic grey screen with a large X shaped cursor. No window manager, but at least you know the X server is running fine. If that works, then copy the /root/xorg.conf.new file to /etc/X11/xorg.conf If it doesn't, then at least you've got the best guess config to hand edit. I dictated this command to someone over the phone the other day to configure a PowerMac where he'd tried and failed. I discovered the command myself and used it on a rack mounted server where the configuration was guessed correctly but the console switch wouldn't work with the modelines - I needed the xorg.conf config file to hand substitute vesa for ati to see anything at all under X :) Hope this helps, Andy -- It is easier to get forgiveness than permission. Eduardo M KALINOWSKI -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
