Discussion:
Xorg oddity.
(too old to reply)
Anton Aylward
2014-10-18 21:55:36 UTC
Permalink
Raw Message
I have a working and acceptable full-res X running, including all the
eye candy like rotating box,, fading windows etc etc etc.

but, but but ...

The logs tell me things like

<quote>
[145070.025] (II) intel(0): Output VGA1 has no monitor section
</quote>

Well of course it doesn't!
My monitor is a Flatron and I have the definition:

<quote>

Section "Monitor"
Identifier "LG1"
Vendorname "LG"
Modelname "LG 1953 S"
</quote>

and of course that ties in with "Screen' definition etc.

Oh, and it complains

<quote>
[145070.025] (II) intel(0): Output VIRTUAL1 has no monitor section
</quote>

Where did that come from?

Are these hard wired into the intel driver or something?
I make no mention of VGA or VIRTUAL in my xorg.conf.d

The EDID seems to be working OK.
--
I start with the premise that the function of leadership is to produce
more leaders, not more followers
- Ralph Nader
--
To unsubscribe, e-mail: opensuse+***@opensuse.org
To contact the owner, e-mail: opensuse+***@opensuse.org
Felix Miata
2014-10-19 02:14:46 UTC
Permalink
Raw Message
Post by Anton Aylward
I have a working and acceptable full-res X running, including all the
eye candy like rotating box,, fading windows etc etc etc.
but, but but ...
The logs tell me things like
<quote>
[145070.025] (II) intel(0): Output VGA1 has no monitor section
</quote>
Well of course it doesn't!
<quote>
Section "Monitor"
Identifier "LG1"
Vendorname "LG"
Modelname "LG 1953 S"
</quote>
and of course that ties in with "Screen' definition etc.
Oh, and it complains
<quote>
[145070.025] (II) intel(0): Output VIRTUAL1 has no monitor section
</quote>
Where did that come from?
Quite some months back I went looking for docs on why VIRTUAL1 exists and how
to make use of it, but never found anything useful.
Post by Anton Aylward
Are these hard wired into the intel driver or something?
I make no mention of VGA or VIRTUAL in my xorg.conf.d
I think outputs showing up in Xorg.0.log actually depend on BIOS
implementation and settings. You can see in
http://fm.no-ip.com/Tmp/Linux/Xorg/xorg.0.log-big41-os132-intel1280x1024 I
have even more "outputs" than you mentioned, but what I think is going on is
that we're seeing all the outputs that the gfxchip *could* support if each of
the possibles were physically implemented on the motherboard, plus VIRTUAL1.
To generate that log just a bit ago I originally had a Radeon installed in
the PCIe slot and used the BIOS to force use of the onboard Intel. In that
configuration, the only output in Xorg.0.log
http://fm.no-ip.com/Tmp/Linux/Xorg/xorg.0.log-big41-os132rc-intel1280x1024
was VGA1. To get the log containing multiple outputs I had to restore the
BIOS to default setting and remove the Radeon.
Post by Anton Aylward
The EDID seems to be working OK.
If you're vexed by X not playing nice (on your GX755?), and simply want your
display's native resolution (1280x1024?), the following should be all you
need in your xorg.conf:

Section "Device"
Identifier "Default Device"
Driver "intel"
Option "AccelMethod" "UXA"
EndSection

Section "Monitor"
Identifier "Default Monitor"
EndSection

Section "Screen"
Identifier "Default Screen"
Device "Default Device"
Monitor "Default Monitor"
EndSection

Identifiers can be any foo you want, but they must be consistent within the
config file.

If you've not already seen them, you might want to look at
http://bugzilla.opensuse.org/show_bug.cgi?id=901506 and the upstream bug.

Common displays shouldn't need any xorg.conf* at all to work correctly from
EDID, but until the fixed Intel driver shows up, I've been doing my manual
Intel config via xrandr in a startup script.

If that minimalist xorg.conf fails to work for you, and you're using KDE, you
might be fighting against KScreen. Try in kdedrc adding:

[Module-kscreen]
autoload=false

Kscreen at least used to when new ignore manual X configs and do whatever it
pleased.
--
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata *** http://fm.no-ip.com/
--
To unsubscribe, e-mail: opensuse+***@opensuse.org
To contact the owner, e-mail: opensuse+***@opensuse.org
Anton Aylward
2014-10-19 13:09:14 UTC
Permalink
Raw Message
Post by Felix Miata
Post by Anton Aylward
I have a working and acceptable full-res X running, including all the
eye candy like rotating box,, fading windows etc etc etc.
but, but but ...
[snip]
Quite some months back I went looking for docs on why VIRTUAL1 exists and how
to make use of it, but never found anything useful.
For something that has been around a long time the documentation of X is
very superficial. Lots of stuff on parameters, little stuff on these
issues.
Post by Felix Miata
Post by Anton Aylward
Are these hard wired into the intel driver or something?
I make no mention of VGA or VIRTUAL in my xorg.conf.d
you seem to be answering "yes" to that in a roundabout way.
Post by Felix Miata
I think outputs showing up in Xorg.0.log actually depend on BIOS
implementation and settings.
I think you mean the chip/card bios rather that the bios I normally set
up, clock, disk etc.
Post by Felix Miata
You can see in
http://fm.no-ip.com/Tmp/Linux/Xorg/xorg.0.log-big41-os132-intel1280x1024 I
have even more "outputs" than you mentioned, but what I think is going on is
that we're seeing all the outputs that the gfxchip *could* support if each of
the possibles were physically implemented on the motherboard, plus VIRTUAL1.
Oh my. And it seems you don't have control over the names. These are
'assumptions" and have nothing to do with what's in xorg.conf.

The more integrated the mobo and chipsets become the less control we
seem to have.
Post by Felix Miata
To generate that log just a bit ago I originally had a Radeon installed in
the PCIe slot and used the BIOS to force use of the onboard Intel. In that
configuration, the only output in Xorg.0.log
http://fm.no-ip.com/Tmp/Linux/Xorg/xorg.0.log-big41-os132rc-intel1280x1024
was VGA1. To get the log containing multiple outputs I had to restore the
BIOS to default setting and remove the Radeon.
Post by Anton Aylward
The EDID seems to be working OK.
If you're vexed by X not playing nice (on your GX755?), and simply want your
display's native resolution (1280x1024?), the following should be all you
Section "Device"
Identifier "Default Device"
Driver "intel"
Option "AccelMethod" "UXA"
EndSection
Section "Monitor"
Identifier "Default Monitor"
EndSection
Section "Screen"
Identifier "Default Screen"
Device "Default Device"
Monitor "Default Monitor"
EndSection
Yes, in terms of probing and autoconfig, xorg has become very smart.
Post by Felix Miata
Identifiers can be any foo you want, but they must be consistent within the
config file.
I've assumed that, and that's why this VGA1 thing threw me.
Post by Felix Miata
If you've not already seen them, you might want to look at
http://bugzilla.opensuse.org/show_bug.cgi?id=901506 and the upstream bug.
Common displays shouldn't need any xorg.conf* at all to work correctly from
EDID, but until the fixed Intel driver shows up, I've been doing my manual
Intel config via xrandr in a startup script.
I'll try taking out all the extra modelines I have put in that I worked
out carefully with xrandr and cvt.
Post by Felix Miata
If that minimalist xorg.conf fails to work for you, and you're using KDE, you
[Module-kscreen]
autoload=false
Kscreen at least used to when new ignore manual X configs and do whatever it
pleased.
I'll watch out for that.

OBTW: multi screen sometimes involves a workspace defined by something
like a
<quote>
50-screen.conf- Defaultdepth 24
50-screen.conf: # Virtual 3600 2160
</quote>
where the parameters are the x+x and y+y of the two screens (and
perhaps a bit more). Maybe that is where the "VIRTUAL1" comes from.
--
Every organization must be prepared to abandon everything it does to
survive in the future.
- Peter Drucker
--
To unsubscribe, e-mail: opensuse+***@opensuse.org
To contact the owner, e-mail: opensuse+***@opensuse.org
Felix Miata
2014-10-19 15:20:12 UTC
Permalink
Raw Message
Post by Anton Aylward
I'll try taking out all the extra modelines I have put in that I worked
out carefully with xrandr and cvt.
I don't get why it seems to be as common as it is that people manually
generate modelines to put into xorg.conf. I can't remember ever solving a
problem doing so in the eons since Xorg replaced XFree86 (and most CRTs were
replaced by flat panels). Xorg does what cvt does automatically given either
valid EDID and/or HozizSync and VertRefresh.
--
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata *** http://fm.no-ip.com/
--
To unsubscribe, e-mail: opensuse+***@opensuse.org
To contact the owner, e-mail: opensuse+***@opensuse.org
jdd
2014-10-19 15:28:22 UTC
Permalink
Raw Message
Post by Felix Miata
I don't get why it seems to be as common as it is that people manually
generate modelines to put into xorg.conf. I can't remember ever solving a
problem doing so in the eons since Xorg replaced XFree86 (and most CRTs were
replaced by flat panels). Xorg does what cvt does automatically given either
valid EDID and/or HozizSync and VertRefresh.
for example get again control altr +/- to change screen definition, for
example, I really miss this one

jdd
--
To unsubscribe, e-mail: opensuse+***@opensuse.org
To contact the owner, e-mail: opensuse+***@opensuse.org
Anton Aylward
2014-10-19 17:14:06 UTC
Permalink
Raw Message
Post by Felix Miata
Post by Anton Aylward
I'll try taking out all the extra modelines I have put in that I worked
out carefully with xrandr and cvt.
I don't get why it seems to be as common as it is that people manually
generate modelines to put into xorg.conf. I can't remember ever solving a
problem doing so in the eons since Xorg replaced XFree86 (and most CRTs were
replaced by flat panels). Xorg does what cvt does automatically given either
valid EDID and/or HozizSync and VertRefresh.
There are a class of situation where EDID does not work.
The one I have is that I'm using a KVM switch and it does not do the
EDID stuff properly as you switch back and forth. It is even worse if
one of the machines on the switch is Windows!
--
When nothing is sure, everything is possible.
- Margaret Drabble
--
To unsubscribe, e-mail: opensuse+***@opensuse.org
To contact the owner, e-mail: opensuse+***@opensuse.org
Felix Miata
2014-10-19 17:28:03 UTC
Permalink
Raw Message
Post by Anton Aylward
I don't get ... or HozizSync and VertRefresh.
There are a class of situation where EDID does not work.
The one I have is that I'm using a KVM switch and it does not do the
EDID stuff properly as you switch back and forth. It is even worse if
one of the machines on the switch is Windows!
--
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata *** http://fm.no-ip.com/
--
To unsubscribe, e-mail: opensuse+***@opensuse.org
To contact the owner, e-mail: opensuse+***@opensuse.org
Loading...