Re: [gentoo-user] xorg-server

Re: [gentoo-user] xorg-server

[David W Noon]

[-- Attachment #1: Type: text/plain, Size: 901 bytes --]

On Mon, 27 Dec 2010 21:30:01 +0100, Mick wrote about Re: [gentoo-user]
xorg-server:

>It seems that the settings in /usr/share/X11/xorg.conf.d/10-evdev.conf
>cause evdev to capture the touchpad and keyboard devices and leave no
>chance to synaptics and kbd drivers (there's also a bug with the
>synaptics driver which is worked around by adding MatchDevicePath
>"/dev/input/event*" in /usr/share/X11/xorg.conf.d/50-synaptics.conf).

This is because the 10-evdev.conf file is processed first.

>This is my /usr/share/X11/xorg.conf.d/50-synaptics.conf:

Try renaming 10-evdev.conf to 55-evdev.conf.  This will let the
synaptics driver have first look at the hardware.
-- 
Regards,

Dave  [RLU #314465]
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
dwnoon@ntlworld.com (David W Noon)
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] xorg-server

[Mick]

[-- Attachment #1: Type: Text/Plain, Size: 870 bytes --]

On Monday 27 December 2010 21:39:42 David W Noon wrote:
> On Mon, 27 Dec 2010 21:30:01 +0100, Mick wrote about Re: [gentoo-user]
> 
> xorg-server:
> >It seems that the settings in /usr/share/X11/xorg.conf.d/10-evdev.conf
> >cause evdev to capture the touchpad and keyboard devices and leave no
> >chance to synaptics and kbd drivers (there's also a bug with the
> >synaptics driver which is worked around by adding MatchDevicePath
> >"/dev/input/event*" in /usr/share/X11/xorg.conf.d/50-synaptics.conf).
> 
> This is because the 10-evdev.conf file is processed first.
> 
> >This is my /usr/share/X11/xorg.conf.d/50-synaptics.conf:
> Try renaming 10-evdev.conf to 55-evdev.conf.  This will let the
> synaptics driver have first look at the hardware.

Thanks, I'll give that a spin, but it wouldn't fix the keyboard problem 
though.
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] xorg-server

[David W Noon]

[-- Attachment #1: Type: text/plain, Size: 936 bytes --]

On Wed, 29 Dec 2010 10:40:02 +0100, Konstantinos Agouros wrote about
Re: [gentoo-user] xorg-server:

>In <20101227175826.1bbafaef@karnak.local> dwnoon@ntlworld.com (David W
>Noon) writes:
[snip]
>>2) Add a configuration file /etc/X11/xorg.conf.d/10-evdev.conf
>
>># Configuration for evdev-controlled input devices.
>>Section "InputClass"
>>        Identifier      "keyboard"
>>        Driver          "evdev"
>>        Option          "XkbLayout" "gb"
>>        Option          "XkbModel" "pc105"
>>        Option          "XkbOptions" "terminate:ctrl_alt_bksp"
>You got this working with xorg-server 1.9? This is the one piece that's
>not working for me.

Yes.  Everything is working just fine.
-- 
Regards,

Dave  [RLU #314465]
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
dwnoon@ntlworld.com (David W Noon)
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

[gentoo-user] xorg-server

[Jorge Almeida]

I was going to update world and I just noticed a few strange details.
For example, xorg-server  has a new (?) USE variable "elogind" which
appears to be enabled by default. I suppose I can block it in
package.use, but I'm curious about what it does. In
https://packages.gentoo.org/useflags/elogind
I found
"Use elogind to get control over framebuffer when running as regular user"

Could someone explain what this entails? What happened before this USE
variable was created? What will I miss if I disable it?

Jorge Almeida

Re: [gentoo-user] xorg-server

[tastytea]

[-- Attachment #1: Type: text/plain, Size: 958 bytes --]

On 2020-04-14T19:16+0100
Jorge Almeida <jjalmeida@gmail.com> wrote:

> I was going to update world and I just noticed a few strange details.
> For example, xorg-server  has a new (?) USE variable "elogind" which
> appears to be enabled by default. I suppose I can block it in
> package.use, but I'm curious about what it does. In
> https://packages.gentoo.org/useflags/elogind
> I found
> "Use elogind to get control over framebuffer when running as regular
> user"
> 
> Could someone explain what this entails? What happened before this USE
> variable was created? What will I miss if I disable it?

ConsoleKit2 is unmaintained, elogind is the replacement. If you don't
use systemd, read `eselect news read new` or
<https://www.gentoo.org/support/news-items/2020-04-14-elogind-default.html>.

> Jorge Almeida
> 

tastytea

-- 
Get my PGP key with `gpg --locate-keys tastytea@tastytea.de` or at
<https://tastytea.de/tastytea.asc>.

[-- Attachment #2: Digitale Signatur von OpenPGP --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

Re: [gentoo-user] xorg-server

[Jorge Almeida]

On Tue, Apr 14, 2020 at 7:29 PM tastytea <tastytea+gentoo@tastytea.de> wrote:
>
> On 2020-04-14T19:16+0100
> Jorge Almeida <jjalmeida@gmail.com> wrote:
>

> > "Use elogind to get control over framebuffer when running as regular
> > user"
> >
> > Could someone explain what this entails? What happened before this USE
> > variable was created? What will I miss if I disable it?
>
> ConsoleKit2 is unmaintained, elogind is the replacement. If you don't
> use systemd, read `eselect news read new` or
> <https://www.gentoo.org/support/news-items/2020-04-14-elogind-default.html>.
>
OK, I get it. I don't use ConsoleKit2, and I have "-consolekit" in
make.conf, so it's just a matter of adding "-elogind" to make.conf. I
understand why suddenly updating world wanted to pull PAM.
What I still would like to understand is what are the consequences of
[not] enabling this stuff regarding xorg-server. What kind of control
over the framebuffer is meant by the USE description quoted above?

Thanks

Jorge

Re: [gentoo-user] xorg-server

[Dale]

Jorge Almeida wrote:
> On Tue, Apr 14, 2020 at 7:29 PM tastytea <tastytea+gentoo@tastytea.de> wrote:
>> On 2020-04-14T19:16+0100
>> Jorge Almeida <jjalmeida@gmail.com> wrote:
>>
>>> "Use elogind to get control over framebuffer when running as regular
>>> user"
>>>
>>> Could someone explain what this entails? What happened before this USE
>>> variable was created? What will I miss if I disable it?
>> ConsoleKit2 is unmaintained, elogind is the replacement. If you don't
>> use systemd, read `eselect news read new` or
>> <https://www.gentoo.org/support/news-items/2020-04-14-elogind-default.html>.
>>
> OK, I get it. I don't use ConsoleKit2, and I have "-consolekit" in
> make.conf, so it's just a matter of adding "-elogind" to make.conf. I
> understand why suddenly updating world wanted to pull PAM.
> What I still would like to understand is what are the consequences of
> [not] enabling this stuff regarding xorg-server. What kind of control
> over the framebuffer is meant by the USE description quoted above?
>
> Thanks
>
> Jorge
>
>


I'm not sure I can answer all your questions but I'll try to provide
some info.  Since it seems you are not using consolekit, PAM or friends,
you must do everything manually when it comes to permissions.  Whether
it is consolekit or elogind, it basically allows users to do certain
things that normally only root can do.  Example, mount USB sticks etc. 
It seems, to me at least, that it also allows graphical environments to
use elogind to manage the session when logged in as well.  I started a
thread about this a while back that should be archived somewhere. 

I'll also add this for those who use elogind already, OP, this may
interest you as well.  I did my usual Sunday upgrade last night.  When
you logout of whatever GUI you use, restart elogind before logging back
in.  I don't recall seeing elogind in the list, it was a long list, but
it seems something upgraded that needs elogind restarted to work right. 
Here is what I noticed that wasn't right.  I could not mount anything
external, USB sticks or my external backup drive.  It would give me a
error about permissions.  Logging into Konsole took minutes instead of
seconds to accept my password.  Logging into the GUI took a long time
to, much longer than usual. Any program that asks for a password, it to
took forever to start if it started at all.  Some just died off and went
to /dev/null.  As soon as I could, I logged out, went to the boot
runlevel, restarted elogind since it is in the boot runlevel and
everything went back to normal.  OP, this may give you some idea what
all elogind does or has a effect on. 

If you have consolekit, PAM, elogind and such disabled, I'm not sure
what if anything will change.  I'd think by disabling elogind, you would
be back to like you was before it *attempted* to add it.  In other
words, nothing changes.  That's my thinking. 

Dale

:-)  :-) 

Re: [gentoo-user] xorg-server

[Jorge Almeida]

On Tue, Apr 14, 2020 at 9:22 PM Dale <rdalek1967@gmail.com> wrote:
>
> Jorge Almeida wrote:

> >>> "Use elogind to get control over framebuffer when running as regular
> >>> user"
> >>>



>
> If you have consolekit, PAM, elogind and such disabled, I'm not sure
> what if anything will change.  I'd think by disabling elogind, you would
> be back to like you was before it *attempted* to add it.  In other
> words, nothing changes.  That's my thinking.

Yes, that seems right. I just added "-elogind" to make.conf and that's
it. But I'm really curious about the framebuffer stuff. As for other
stuff (mounting USB, etc), doing it by hand it's fine.
>
Cheers

Jorge

Re: [gentoo-user] xorg-server

[David W Noon]

[-- Attachment #1: Type: text/plain, Size: 1232 bytes --]

On Mon, 27 Dec 2010 12:20:02 +0100, John wrote about [gentoo-user]
xorg-server:

>I have just upgraded to xorg-server 1.9.2
>but unfortunately my keyboard is not recognising gb layout

You have at least 2 courses of action:

1) Add a udev rule in /etc/udev/rules.d/10-local.rules

# A rule to define our keyboard layout.
KERNEL=="event*", ENV{ID_INPUT_KEYBOARD}=="?*", ENV{xkblayout}="gb",
ENV{xkbmodel}="pc105"

2) Add a configuration file /etc/X11/xorg.conf.d/10-evdev.conf

# Configuration for evdev-controlled input devices.
Section "InputClass"
        Identifier      "keyboard"
        Driver          "evdev"
        Option          "XkbLayout" "gb"
        Option          "XkbModel" "pc105"
        Option          "XkbOptions" "terminate:ctrl_alt_bksp"
        MatchIsKeyboard "on"
EndSection

Section "InputClass"
        Identifier      "pointer"
        Driver          "evdev"
        MatchIsPointer  "on"
EndSection



I used both, just to be sure, to be sure.
-- 
Regards,

Dave  [RLU #314465]
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
dwnoon@ntlworld.com (David W Noon)
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] xorg-server

[John]

[-- Attachment #1: Type: text/plain, Size: 1383 bytes --]

On Mon, 27 Dec 2010 17:58:26 +0000
David W Noon <dwnoon@ntlworld.com> wrote:

> On Mon, 27 Dec 2010 12:20:02 +0100, John wrote about [gentoo-user]
> xorg-server:
> 
> >I have just upgraded to xorg-server 1.9.2
> >but unfortunately my keyboard is not recognising gb layout
> 
> You have at least 2 courses of action:
> 
> 1) Add a udev rule in /etc/udev/rules.d/10-local.rules
> 
> # A rule to define our keyboard layout.
> KERNEL=="event*", ENV{ID_INPUT_KEYBOARD}=="?*", ENV{xkblayout}="gb",
> ENV{xkbmodel}="pc105"
> 
> 2) Add a configuration file /etc/X11/xorg.conf.d/10-evdev.conf
> 
> # Configuration for evdev-controlled input devices.
> Section "InputClass"
>         Identifier      "keyboard"
>         Driver          "evdev"
>         Option          "XkbLayout" "gb"
>         Option          "XkbModel" "pc105"
>         Option          "XkbOptions" "terminate:ctrl_alt_bksp"
>         MatchIsKeyboard "on"
> EndSection
> 
> Section "InputClass"
>         Identifier      "pointer"
>         Driver          "evdev"
>         MatchIsPointer  "on"
> EndSection
> 
> 
> 
> I used both, just to be sure, to be sure.

Have tried all suggestions and all works ok now.

Should we still be using xorg.conf as a few years
ago or not using a xorg.conf file unless we have to?

Thanks

-- 
John D Maunder
john@articwolf.myzen.co.uk

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

Re: [gentoo-user] xorg-server

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 277 bytes --]

On Mon, 27 Dec 2010 18:45:21 +0000, John wrote:

> Should we still be using xorg.conf as a few years
> ago or not using a xorg.conf file unless we have to?

Or use files in xorg.conf.d, which makes maintenance easier.


-- 
Neil Bothwick

SCSI: System Can't See It

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] xorg-server

[Mick]

[-- Attachment #1: Type: Text/Plain, Size: 1707 bytes --]

On Monday 27 December 2010 19:20:30 Neil Bothwick wrote:
> On Mon, 27 Dec 2010 18:45:21 +0000, John wrote:
> > Should we still be using xorg.conf as a few years
> > ago or not using a xorg.conf file unless we have to?
> 
> Or use files in xorg.conf.d, which makes maintenance easier.

The xorg 1.9 has not behaved very nicely on my laptops, while it has been 
trouble free on my desktops.

It seems that the settings in /usr/share/X11/xorg.conf.d/10-evdev.conf cause 
evdev to capture the touchpad and keyboard devices and leave no chance to 
synaptics and kbd drivers (there's also a bug with the synaptics driver which 
is worked around by adding MatchDevicePath "/dev/input/event*" in 
/usr/share/X11/xorg.conf.d/50-synaptics.conf).

The solution I found was to add:

 Option "AllowEmptyInput" "off" 

in Section "ServerLayout" in /etc/X11/xorg.conf and then comment out the 
touchpad and keyboard sections of the /usr/share/X11/xorg.conf.d/10-evdev.conf 
file.

After that was taken care of, the keyboard settings in xorg.conf and the 
synaptics settings in /usr/share/X11/xorg.conf.d/50-synaptics.conf started 
being recognised.

This is my /usr/share/X11/xorg.conf.d/50-synaptics.conf:

Section "InputClass"
        Identifier "touchpad catchall"
        Driver "synaptics"
        MatchIsTouchpad "on"
        MatchDevicePath "/dev/input/event*"
        Option  "VertEdgeScroll" "true"
        Option  "HorizEdgeScroll" "true"
        Option  "TapButton1" "1"
        Option  "ClickButton1" "1"
        Option  "VertTwoFingerScroll" "true"
        Option  "HorizTwoFingerScroll" "true"
        Option  "AccelFactor" "0.0010"
EndSection
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] xorg-server

[Konstantinos Agouros]

In <20101227175826.1bbafaef@karnak.local> dwnoon@ntlworld.com (David W Noon) writes:

>--Sig_/Hxy_r1egAtvobeT/s7/L0.O
>Content-Type: text/plain; charset=US-ASCII
>Content-Transfer-Encoding: quoted-printable

>On Mon, 27 Dec 2010 12:20:02 +0100, John wrote about [gentoo-user]
>xorg-server:

>>I have just upgraded to xorg-server 1.9.2
>>but unfortunately my keyboard is not recognising gb layout

>You have at least 2 courses of action:

>1) Add a udev rule in /etc/udev/rules.d/10-local.rules

># A rule to define our keyboard layout.
>KERNEL=3D=3D"event*", ENV{ID_INPUT_KEYBOARD}=3D=3D"?*", ENV{xkblayout}=3D"g=
>b",
>ENV{xkbmodel}=3D"pc105"

>2) Add a configuration file /etc/X11/xorg.conf.d/10-evdev.conf

># Configuration for evdev-controlled input devices.
>Section "InputClass"
>        Identifier      "keyboard"
>        Driver          "evdev"
>        Option          "XkbLayout" "gb"
>        Option          "XkbModel" "pc105"
>        Option          "XkbOptions" "terminate:ctrl_alt_bksp"
You got this working with xorg-server 1.9? This is the one piece that's
not working for me.

Konstantin
-- 
Dipl-Inf. Konstantin Agouros aka Elwood Blues. Internet: elwood@agouros.de
Altersheimerstr. 1, 81545 Muenchen, Germany. Tel +49 89 69370185
----------------------------------------------------------------------------
"Captain, this ship will not survive the forming of the cosmos." B'Elana Torres

Re: [gentoo-user] xorg-server

[Mick]

[-- Attachment #1: Type: Text/Plain, Size: 2934 bytes --]

On Wednesday 29 December 2010 09:26:57 Konstantinos Agouros wrote:
> In <20101227175826.1bbafaef@karnak.local> dwnoon@ntlworld.com (David W Noon) 
writes:
> >--Sig_/Hxy_r1egAtvobeT/s7/L0.O
> >Content-Type: text/plain; charset=US-ASCII
> >Content-Transfer-Encoding: quoted-printable
> >
> >On Mon, 27 Dec 2010 12:20:02 +0100, John wrote about [gentoo-user]
> >
> >xorg-server:
> >>I have just upgraded to xorg-server 1.9.2
> >>but unfortunately my keyboard is not recognising gb layout
> >
> >You have at least 2 courses of action:
> >
> >1) Add a udev rule in /etc/udev/rules.d/10-local.rules
> >
> ># A rule to define our keyboard layout.
> >KERNEL=3D=3D"event*", ENV{ID_INPUT_KEYBOARD}=3D=3D"?*",
> >ENV{xkblayout}=3D"g= b",
> >ENV{xkbmodel}=3D"pc105"
> >
> >2) Add a configuration file /etc/X11/xorg.conf.d/10-evdev.conf
> >
> ># Configuration for evdev-controlled input devices.
> >Section "InputClass"
> >
> >        Identifier      "keyboard"
> >        Driver          "evdev"
> >        Option          "XkbLayout" "gb"
> >        Option          "XkbModel" "pc105"
> >        Option          "XkbOptions" "terminate:ctrl_alt_bksp"
> 
> You got this working with xorg-server 1.9? This is the one piece that's
> not working for me.


Other than setting up udev rules I have tried everything that I could think 
of.  Based on the experiments I ran on two laptops I have come to the 
following conclusions (or should this be "confusions"?  ha, ha):

        Option "AllowEmptyInput" "off"

is necessary under Section "ServerLayout" to allow legacy kbd and mouse 
drivers to load.

Setting up a /etc/X11/xorg.conf.d/10-evdev.conf and then moving to 55-
evdev.conf so that the 50-synaptics.conf is read first does not work.  
Somehow evdev permeates everything, creates multiple devices and hijacks the 
touchpad, keyboard, etc.

Commenting out the /etc/X11/xorg.conf.d/10-evdev.conf lines for keyboard and 
touchpad also does not do the trick, because there is still the 
/usr/share/X11/xorg.conf.d/10-evdev.conf which seems to be parsed regardless 
of a /etc/X11/xorg.conf.d/10-evdev.conf file being available.

So, I removed /etc/X11/xorg.conf.d/10-evdev.conf, commented out the keyboard 
and touchpad entries in /usr/share/X11/xorg.conf.d/10-evdev.conf and can now 
use my touchpad with horizontal/vertical scroll functions, acceleration, etc. 
based on settings I added in /usr/share/X11/xorg.conf.d/50- as well as a 
multi-language keyboard.

Personally, I can't see why all these additional config files and locations 
are required, rather than a single /etc/X11/xorg.conf.  I have found all these 
back and forth changes to fdi's, xorg.conf.d and what have you, unnecessary 
and annoyingly time wasting.

Of course I might have missed something simple in all this kerfuffle, so 
please chime in if there is a better way around this.
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] xorg-server

[Dale]

Mick wrote:
> Other than setting up udev rules I have tried everything that I could think
> of.  Based on the experiments I ran on two laptops I have come to the
> following conclusions (or should this be "confusions"?  ha, ha):
>
>          Option "AllowEmptyInput" "off"
>
> is necessary under Section "ServerLayout" to allow legacy kbd and mouse
> drivers to load.
>
> Setting up a /etc/X11/xorg.conf.d/10-evdev.conf and then moving to 55-
> evdev.conf so that the 50-synaptics.conf is read first does not work.
> Somehow evdev permeates everything, creates multiple devices and hijacks the
> touchpad, keyboard, etc.
>
> Commenting out the /etc/X11/xorg.conf.d/10-evdev.conf lines for keyboard and
> touchpad also does not do the trick, because there is still the
> /usr/share/X11/xorg.conf.d/10-evdev.conf which seems to be parsed regardless
> of a /etc/X11/xorg.conf.d/10-evdev.conf file being available.
>
> So, I removed /etc/X11/xorg.conf.d/10-evdev.conf, commented out the keyboard
> and touchpad entries in /usr/share/X11/xorg.conf.d/10-evdev.conf and can now
> use my touchpad with horizontal/vertical scroll functions, acceleration, etc.
> based on settings I added in /usr/share/X11/xorg.conf.d/50- as well as a
> multi-language keyboard.
>
> Personally, I can't see why all these additional config files and locations
> are required, rather than a single /etc/X11/xorg.conf.  I have found all these
> back and forth changes to fdi's, xorg.conf.d and what have you, unnecessary
> and annoyingly time wasting.
>
> Of course I might have missed something simple in all this kerfuffle, so
> please chime in if there is a better way around this.
>    

I just did a fresh install on my new rig.  I also upgraded my old x86 to 
the new xorg as well.  Keep in mind that I have had hal disabled all 
this time.  I removed all the fdi files that hal needed a long time 
ago.  Everything works fine here on both rigs.  I say all that to say 
this, can you get the config files back to a point where it would be 
like hal never existed at all?   Maybe some config file is being read 
that shouldn't be read at all?

Also, I generated my xorg.conf file with nvidia-xconfig.  After I fixed 
a kernel issue, it has worked fine ever since.  I would be glad to send 
it off list if needed.  You may not want to use it but you may can 
compare it to yours.

Is it possible you have to much in the way of config files?

Dale

:-)  :-)

Re: [gentoo-user] xorg-server

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 565 bytes --]

On Wed, 29 Dec 2010 13:01:24 +0000, Mick wrote:

> Personally, I can't see why all these additional config files and
> locations are required, rather than a single /etc/X11/xorg.conf.  I
> have found all these back and forth changes to fdi's, xorg.conf.d and
> what have you, unnecessary and annoyingly time wasting.

They're not. All you have now is xorg.conf or xorg.conf.d, the same
settings but either in a single file or split for ease of maintenance -
it's your choice.


-- 
Neil Bothwick

Geordi, show these children the antimatter - Picard

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] xorg-server

[Mike Edenfield]

On Wed, 2010-12-29 at 13:01 +0000, Mick wrote:

> Personally, I can't see why all these additional config files and locations 
> are required, rather than a single /etc/X11/xorg.conf.  I have found all these 
> back and forth changes to fdi's, xorg.conf.d and what have you, unnecessary 
> and annoyingly time wasting.
> 
> Of course I might have missed something simple in all this kerfuffle, so 
> please chime in if there is a better way around this.

If all you are worried about is making your touchpad work in X, and
you're willing to pull it up in a text editor every time you need to
make a change, then no, you didn't really miss anything.

The purpose of xorg.conf.d is to allow packages/utilities/etc to drop in
changes to your X config seamlessly, as in, without the user being
required to take any specific action.  For example, the synaptics input
driver drops a 50-synaptics.conf file into your xorg.conf.d that
includes a simple "this is a touchpad" configuration, which would take
effect just by restarting X.  

The purpose of udev is to configure all of the hardware on your system,
not just for X.  It's how GNOME/KDE/whatever is able to automount your
USB key when it shows up, and knows that /dev/sr0 is a dvd-rom drive,
etc. Just as with HAL, using udev to configure X-specific options is
probably overkill. In theory, other GUI systems besides X could just as
easily read the x11 options from udev and use them. Since there isn't
really any such alternative, the practical benefits of udev over a
monolithic xorg.conf file mostly vanish.

--Mike

Re: [gentoo-user] xorg-server

[Mick]

[-- Attachment #1: Type: Text/Plain, Size: 2638 bytes --]

On Thursday 30 December 2010 17:40:18 Mike Edenfield wrote:
> On Wed, 2010-12-29 at 13:01 +0000, Mick wrote:
> > Personally, I can't see why all these additional config files and
> > locations are required, rather than a single /etc/X11/xorg.conf.  I have
> > found all these back and forth changes to fdi's, xorg.conf.d and what
> > have you, unnecessary and annoyingly time wasting.
> > 
> > Of course I might have missed something simple in all this kerfuffle, so
> > please chime in if there is a better way around this.
> 
> If all you are worried about is making your touchpad work in X, and
> you're willing to pull it up in a text editor every time you need to
> make a change, then no, you didn't really miss anything.

Well, it's the touch pad and keyboard on two laptops, both of which seem to 
not have liked evdev defaults, or modifying xorg.conf, or adding options to 
the evdev file itself, or adding options to the 50-synaptics.conf file, or a 
10-keyboard.conf file that I created.

On the other hand, with a desktop the transition to 1.9 two months or so ago 
just worked™.

> The purpose of xorg.conf.d is to allow packages/utilities/etc to drop in
> changes to your X config seamlessly, as in, without the user being
> required to take any specific action.  For example, the synaptics input
> driver drops a 50-synaptics.conf file into your xorg.conf.d that
> includes a simple "this is a touchpad" configuration, which would take
> effect just by restarting X.

Are you talking about the /usr/share/X11/xorg.conf.d/ directory or the 
/etc/X11/xorg.conf.d/ which I created on my own?  I was hoping that any 
additions in /etc/X11/xorg.conf.d/ would take precedence over settings in 
/usr/share/X11/xorg.conf.d/ and survive an update, but the two seem to clash 
and cause erratic behaviour.


> The purpose of udev is to configure all of the hardware on your system,
> not just for X.  It's how GNOME/KDE/whatever is able to automount your
> USB key when it shows up, and knows that /dev/sr0 is a dvd-rom drive,
> etc. Just as with HAL, using udev to configure X-specific options is
> probably overkill. In theory, other GUI systems besides X could just as
> easily read the x11 options from udev and use them. Since there isn't
> really any such alternative, the practical benefits of udev over a
> monolithic xorg.conf file mostly vanish.

Yes it does make sense, but I sort of objected to tweaking udev rules because 
I'm thinking the clash is not between devices, but between xf86 drivers.

Anyhow, I'm happy I got it working regardless.  :-)
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] xorg-server

[Mike Edenfield]

On Thu, 2010-12-30 at 19:02 +0000, Mick wrote:
> On Thursday 30 December 2010 17:40:18 Mike Edenfield wrote:
> > On Wed, 2010-12-29 at 13:01 +0000, Mick wrote:
> > > Personally, I can't see why all these additional config files and
> > > locations are required, rather than a single /etc/X11/xorg.conf.  I have
> > > found all these back and forth changes to fdi's, xorg.conf.d and what
> > > have you, unnecessary and annoyingly time wastin
> > > 
> > > Of course I might have missed something simple in all this kerfuffle, so
> > > please chime in if there is a better way around this.
> > 
> > If all you are worried about is making your touchpad work in X, and
> > you're willing to pull it up in a text editor every time you need to
> > make a change, then no, you didn't really miss anything.
> 
> Well, it's the touch pad and keyboard on two laptops, both of which seem to 
> not have liked evdev defaults, or modifying xorg.conf, or adding options to 
> the evdev file itself, or adding options to the 50-synaptics.conf file, or a 
> 10-keyboard.conf file that I created.
> 
> On the other hand, with a desktop the transition to 1.9 two months or so ago 
> just worked™.
> 
> > The purpose of xorg.conf.d is to allow packages/utilities/etc to drop in
> > changes to your X config seamlessly, as in, without the user being
> > required to take any specific action.  For example, the synaptics input
> > driver drops a 50-synaptics.conf file into your xorg.conf.d that
> > includes a simple "this is a touchpad" configuration, which would take
> > effect just by restarting X.
> 
> Are you talking about the /usr/share/X11/xorg.conf.d/ directory or the 
> /etc/X11/xorg.conf.d/ which I created on my own?  I was hoping that any 
> additions in /etc/X11/xorg.conf.d/ would take precedence over settings in 
> /usr/share/X11/xorg.conf.d/ and survive an update, but the two seem to clash 
> and cause erratic behaviour.

If you have a file of the same name in both directories, then the one
in /etc should override the one in /usr/share.  But the names need to
match exactly.

Re: [gentoo-user] xorg-server

[Mick]

[-- Attachment #1: Type: Text/Plain, Size: 337 bytes --]

On Thursday 30 December 2010 19:43:06 Mike Edenfield wrote:

> If you have a file of the same name in both directories, then the one
> in /etc should override the one in /usr/share.  But the names need to
> match exactly.

Yes, identical.  I know this, because I copied the one from /usr/share to 
/etc/X11.
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

[gentoo-user] xorg-server

[John]

	
Hi Gentoo Users

I have just upgraded to xorg-server 1.9.2
but unfortunately my keyboard is not recognising gb layout

I have copied across use-estonian-layout.fdi.bz2
to /etc/hal/fdi/policy/10-xinput-configuration.fdi
and altered to gb.

Rebooted etc but still keyboard is wrong.

Is this still the correct file to change or should I be using xorg.conf?

I have renamed to 10-keymap.fdi but does not make a difference.

Following gentoo documentation.


-- 
John D Maunder
john@articwolf.myzen.co.uk

Re: [gentoo-user] xorg-server

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 601 bytes --]

On Mon, 27 Dec 2010 11:14:53 +0000, John wrote:

> I have just upgraded to xorg-server 1.9.2
> but unfortunately my keyboard is not recognising gb layout
> 
> I have copied across use-estonian-layout.fdi.bz2
> to /etc/hal/fdi/policy/10-xinput-configuration.fdi
> and altered to gb.
> 
> Rebooted etc but still keyboard is wrong.
> 
> Is this still the correct file to change or should I be using xorg.conf?

xorg-server 1.9 no longer uses hal, xorg.conf is the easiest way to do
this.


-- 
Neil Bothwick

If man ruled the world:
Daisy Duke shorts would never go out of fashion.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] xorg-server

[Dale]

John wrote:
> 	
> Hi Gentoo Users
>
> I have just upgraded to xorg-server 1.9.2
> but unfortunately my keyboard is not recognising gb layout
>
> I have copied across use-estonian-layout.fdi.bz2
> to /etc/hal/fdi/policy/10-xinput-configuration.fdi
> and altered to gb.
>
> Rebooted etc but still keyboard is wrong.
>
> Is this still the correct file to change or should I be using xorg.conf?
>
> I have renamed to 10-keymap.fdi but does not make a difference.
>
> Following gentoo documentation.
>
>
>    

I don't think that version uses hal, but uses udev.  Is the udev USE 
flag enabled?

I think you may want to try using a xorg.conf file but I'm not certain 
it is required.  I gave up on hal a long time ago so I still have my 
file here.

Dale

:-)  :-)

[gentoo-user] xorg-server

[krgn]

Hi all,

I was playing with the thought of installing x11 7.0 (that's modular X?)
lately to try out a few Extensions and I wondered which driver to choose
for my Nvidia GeforceGo card. Can I still continue to use nvidia-kernel
and nvidia-glx?
How is it actually with Y-windows, most of the apps and window-managers
that work under X won't work under Y, correct?

thanks,

KArsten

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] xorg-server

[Richard Fish]

On 1/13/06, krgn <k.gebbert@gmail.com> wrote:
> How is it actually with Y-windows, most of the apps and window-managers
> that work under X won't work under Y, correct?

Y-windows is dead.  Based on the mailing list archives, nobody is
working on it.  It is also hard-masked pending removal from portage. 
The basic problem seems to be that when XFree forked to X.org, the
need for and interest in Y-windows evaporated.

The most interesting graphics work today is being done by
freedesktop.org, including x.org.

-Richard

-- 
gentoo-user@gentoo.org mailing list