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
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'
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 d
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 i
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, th
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
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
>
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 t
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...
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
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 xor
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.
>
>
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
>
>13
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
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
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.
--
Jo
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
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/Xo
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 b
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
>> res
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
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
On 3/12/2010 10:22 AM, John W Foster wrote:
-Original Message-
From: Paul E Condon
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
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.
>
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:390
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
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 wond
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/52
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, 0xd8
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 co
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
>
John W Foster wrote:
-Original Message-
From: Paul E Condon
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
-Original Message-
From: Paul E Condon
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
On 20100312_102211, John W Foster wrote:
> -Original Message-
> From: Paul E Condon
> To: debian-user@lists.debian.org
> 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 scr
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.
On Fri, 12 Mar 2010 14:13:04 + (UTC)
Camaleón 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"
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 parti
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
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 g
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 bette
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
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 elipse
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
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 ma
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 Len
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
-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 wrote:
> The DFP is for an LCD.
>
> Section "Device"
...
> Option "Metamodes" "1680x1050,
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
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.
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 ta
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 o
-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 stu
52 matches
Mail list logo
