Monitor recognition at boot time

Hello folks,

      I was wondering whether some of you could have any
ideas about how
to identify a certain monitor plugged into my card's
secondary output at
boot time (before X starts) automatically.

The situation is the following: I have a laptop (Samsung
R65) with an
nVdidia GeForce Go 7400 in it. I like dual head setups and I
have one at
home and two at work, one of which is dedicated to the
laptop. The
problem is however, that at work the external CRT is _left
of_ my laptop, 
and at home the external (DFP) is _right of_ my laptop. So I
would love
to be able to manipulate xorg.conf with a script at boot
time. It would
just be very - convenient . But to
do this I would have to aquire
information about the monitor [1]. Is there any way to get
the EDID or
something similar out of the nvidia module or any other
program /before/
starting X?

Thanks in advance,
       Aleks

ad 1: I could also misuse information about the network
connection or
the like but then again, I don't always plug in/need the
second monitor...

Aleksandar L. Dimitrov wrote:
> The
> problem is however, that at work the external CRT is
_left of_ my laptop, 
> and at home the external (DFP) is _right of_ my laptop.
So I would love
> to be able to manipulate xorg.conf with a script at
boot time. 

What I do is maintain two xorg.conf files: xorg.conf.home
& xorg.conf.work.
Then I do not start X during startup.  Instead I log into
the console
and run
one of two scripts:  x-home or x-work, which simply copies
the corresponding
xorg.conf.* file to xorg.conf then starts xdm.

HTH,
Roy
-- 
gentoo-usergentoo.org mailing list

> What I do is maintain two xorg.conf files:
xorg.conf.home & xorg.conf.work.

Hm... that's what I wanted to avoid, since it's usually a
PITA to
maintain multiple instances of a config (I'm already doing
this with
sendmail...).

> Then I do not start X during startup.  Instead I log
into the console
> and run
> one of two scripts:  x-home or x-work, which simply
copies the corresponding
> xorg.conf.* file to xorg.conf then starts xdm.

Yes, that's pretty close to what I'm doing right at the
moment. But I
would really like to automate this process - that's why I
woul really
like to be able to acquire the EDID or something similar
(model specs or
just a unique binary value) at boot time, so I can invoke an
appropriate
script during system init.

*sigh* ... I guess I'll have to post to the unfriendly
nVnews forums
again.

Regards,
	Aleks

On Thu, 5 Jul 2007 14:37:02 +0200, Aleksandar L. Dimitrov
wrote:

> Yes, that's pretty close to what I'm doing right at the
moment. But I
> would really like to automate this process - that's why
I woul really
> like to be able to acquire the EDID or something
similar (model specs or
> just a unique binary value) at boot time, so I can
invoke an appropriate
> script during system init.

What about x11-misc/read-edid?


-- 
Neil Bothwick

I just got lost in thought. It was unfamiliar territory.

Aleksandar L. Dimitrov wrote:
> I would really like to automate this process - that's
why I woul
> really like to be able to acquire the EDID or something
similar
> (model specs or just a unique binary value) at boot
time, so I can 
> invoke an appropriate script during system init.

$ eix edid
* x11-misc/read-edid
     Available   :  1.4.1 ~1.4.1-r1
     Description :  program that can get information from a
pnp monitor.

Now pray that this works before having started X.

Benno
-- 
gentoo-usergentoo.org mailing list