Prev: RESOLVED- Re: Problem running printer config programme
Next: Virtualbox compile errors on Slack 13.0 64?
From: jim dorey on 6 Sep 2009 17:55
Hans wrote:

> But wee do you save the xrandr options, xorg.conf or kde/Autostart ?
>

my xrandr.sh in autostart is

xrandr --output VGA-0 --mode 1152x864 --output DVI-0 --mode 1152x864
--right-of VGA-0

after i found out the extremely complicated, murderously hard setup for
xorg.conf...set everything up as if you only have one monitor, add the
second monitor section, but don't add it to the server layout, and add a
virtual screen size statement.

like this:
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1152x864" "1024x768" "800x600"
Virtual 2304 864
EndSubSection
EndSection

i haven't investigated, but it seems that direct render is supposed to
work on two screens if you do it right, but, i haven't checked. i only
really need direct when i'm gaming, and i don't game on my new monitor,
it's hard to see all the way over on the floor :P(new desk eventually).
From: ~kurt on 7 Sep 2009 00:18
Dan C <youmustbejoking(a)lan.invalid> wrote:
>
> As I said, it is no longer *required*, but can be used for specific
> changes/additions.

Are you sure that is not just for DVI connected monitors?

- Kurt
From: Dan C on 7 Sep 2009 01:18
On Sun, 06 Sep 2009 23:18:08 -0500, ~kurt wrote:

> Dan C <youmustbejoking(a)lan.invalid> wrote:
>>
>> As I said, it is no longer *required*, but can be used for specific
>> changes/additions.
>
> Are you sure that is not just for DVI connected monitors?

Am I sure that *what* isn't just for DVI connected monitors?

The "file is not required", or "can be used"?

Actually, I don't think it matters what kind of monitor you have
connected, as far as X and xorg.conf are concerned.


--
"Ubuntu" -- an African word, meaning "Slackware is too hard for me".
"Bother!" said Pooh, as he garotted another passing Liberal.
Usenet Improvement Project: http://twovoyagers.com/improve-usenet.org/
From: Henrik Carlqvist on 8 Sep 2009 01:31
Kees Theunissen <theuniss(a)rijnh.nl> wrote:
> (II) NV(0): Monitor name: DELL 1703FP
> (II) NV(0): Ranges: V min: 56 V max: 76 Hz, H min: 30 H max: 80 kHz, PixClock max 140 MHz

> As you can see: all relevant information about the monitor can be
> determined, even with plain six years old vga hardware. The vga
> connection isn't as plain anymore as it used to be in the really
> old times.

Yes, DDC is really great when it works. However, I wouldn't rely on DDC
working every day. Instead I would prefer a semi automatic configuration
step during install which tries to configure the monitor settings using
DDC. If DDC succeds the user would only have to approve the selected
resolution and if DDC fails the installation would have to fall back to
the user manually entering refresh rates. The drawback of only using DDC
during install is that if the monitor is replaced this configuration step
has to be repeated.

Even though virtual all monitors, graphic cards and drivers today support
DDC there are still cases when DDC is not useful during the startup of X:

1) If the VGA cable hasn't pin 12 and pin 15 wired. I happened to buy such
a crappy VGA cable only a few years ago. Also some KVM-switches does not
let the DDC signals pass through.

2) If a KVM-switch is connected between the monitor and the graphics card
and the KVM-switch currently has another computer connected to the monitor.

3) If the monitor is powered off when X is started (at least most monitors
seem to fail giving EDID information when powered off).

regards Henrik
--
The address in the header is only to prevent spam. My real address is:
hc3(at)poolhem.se Examples of addresses which go to spammers:
root(a)localhost postmaster(a)localhost

First  |  Prev  | 
Pages: 1 2 3
Prev: RESOLVED- Re: Problem running printer config programme
Next: Virtualbox compile errors on Slack 13.0 64?