Okay, let's get X workingg on my new Stretch

classic Classic list List threaded Threaded
14 messages Options
Reply | Threaded
Open this post in threaded view
|

Okay, let's get X workingg on my new Stretch

Bob Bernstein
The mouse proves elusive:

# dmesg |grep -i mouse
[    2.645218] mousedev: PS/2 mouse device common for all mice
[    3.225344] psmouse serio1: logips2pp: Detected unknown
Logitech mouse model
90
[    3.722367] input: ImExPS/2 Logitech Explorer Mouse as
/devices/platform/i8042/serio1/input/input2

BUT:

Running $ X -configure yields:

"Xorg is not able to detect your mouse.
"Edit the file and correct the Device."

The file in question looks like this:

-snip-
Section "ServerLayout"
  Identifier     "X.org Configured"
  Screen      0  "Screen0" 0 0
  InputDevice    "Mouse0" "CorePointer"
  InputDevice    "Keyboard0" "CoreKeyboard"
EndSection

Section "Files"
  ModulePath   "/usr/lib/xorg/modules"
  FontPath     "/usr/share/fonts/X11/misc"
  FontPath     "/usr/share/fonts/X11/cyrillic"
  FontPath     "/usr/share/fonts/X11/100dpi/:unscaled"
  FontPath     "/usr/share/fonts/X11/75dpi/:unscaled"
  FontPath     "/usr/share/fonts/X11/Type1"
  FontPath     "/usr/share/fonts/X11/100dpi"
  FontPath     "/usr/share/fonts/X11/75dpi"
  FontPath     "built-ins"
EndSection

Section "Module"
  Load  "glx"
EndSection

Section "InputDevice"
  Identifier  "Keyboard0"
  Driver      "kbd"
EndSection

Section "InputDevice"
  Identifier  "Mouse0"
  Driver      "mouse"
  Option    "Protocol" "auto"
  Option    "Device" "/dev/input/mice"
  Option    "ZAxisMapping" "4 5 6 7"
EndSection

Section "Monitor"
  Identifier   "Monitor0"
  VendorName   "Monitor Vendor"
  ModelName    "Monitor Model"
EndSection

Section "Device"
         ### Available Driver options are:-
         ### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
         ### <string>: "String", <freq>: "<f> Hz/kHz/MHz",
         ### <percent>: "<f>%"
         ### [arg]: arg optional
         #Option     "Accel"               # [<bool>]
         #Option     "SWcursor"           # [<bool>]
         #Option     "EnablePageFlip"     # [<bool>]
         #Option     "ColorTiling"         # [<bool>]
         #Option     "ColorTiling2D"       # [<bool>]
         #Option     "RenderAccel"         # [<bool>]
         #Option     "SubPixelOrder"       # [<str>]
         #Option     "AccelMethod"         # <str>
         #Option     "ShadowPrimary"       # [<bool>]
         #Option     "EXAVSync"           # [<bool>]
         #Option     "EXAPixmaps"         # [<bool>]
         #Option     "ZaphodHeads"         # <str>
         #Option     "SwapbuffersWait"     # [<bool>]
         #Option     "DeleteUnusedDP12Displays" # [<bool>]
         #Option     "DRI3"               # [<bool>]
         #Option     "DRI"                 # <i>
         #Option     "TearFree"           # [<bool>]
  Identifier  "Card0"
  Driver      "radeon"
  BusID       "PCI:1:5:0"
EndSection

Section "Screen"
  Identifier "Screen0"
  Device     "Card0"
  Monitor    "Monitor0"
  SubSection "Display"
  Viewport   0 0
  Depth     1
  EndSubSection
  SubSection "Display"
  Viewport   0 0
  Depth     4
  EndSubSection
  SubSection "Display"
  Viewport   0 0
  Depth     8
  EndSubSection
  SubSection "Display"
  Viewport   0 0
  Depth     15
  EndSubSection
  SubSection "Display"
  Viewport   0 0
  Depth     16
  EndSubSection
  SubSection "Display"
  Viewport   0 0
  Depth     24
  EndSubSection
EndSection
-snip-

Running X -config xorg.conf.new produces a nice blank black
screen but no sign of a mouse.

Thank you


--
Poobah

Reply | Threaded
Open this post in threaded view
|

Re: Okay, let's get X workingg on my new Stretch

Bob Bernstein-3
More data:

-snip-
$ startx

X.Org X Server 1.19.2
Release Date: 2017-03-02
X Protocol Version 11, Revision 0
Build Operating System: Linux 4.9.0-8-amd64 x86_64 Debian
Current Operating System: Linux debian.localdomain 4.9.0-9-amd64
#1 SMP Debian 4.9.168-1+deb9u3 (2019-06-16) x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.9.0-9-amd64
root=UUID=b67d82e0-9444-4663-b3d4-1a4d20d2a0ef ro quiet
Build Date: 03 November 2018  03:09:11AM
xorg-server 2:1.19.2-1+deb9u5 (https://www.debian.org/support)
Current version of pixman: 0.34.0
         Before reporting problems, check http://wiki.x.org
         to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default
setting,
         (++) from command line, (!!) notice, (II) informational,
         (WW) warning, (EE) error, (NI) not implemented, (??)
unknown.
(==) Log file: "/home/bob/.local/share/xorg/Xorg.0.log", Time:
Tue Jun 18 14:33:10 2019
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
on.(EE) (EE) Server terminated with error (1). Closing log
file.tional informatixinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error
-snip-

Here is the log associated with the above events

-snip-
Current Operating System: Linux debian.localdomain 4.9.0-9-amd64
#1 SMP Debian 4.9.168-1+deb9u3 (2019-06-16) x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.9.0-9-amd64
root=UUID=b67d82e0-9444-4663-b3d4-1a4d20d2a0ef ro quiet
Build Date: 03 November 2018  03:09:11AM
xorg-server 2:1.19.2-1+deb9u5 (https://www.debian.org/support)
Current version of pixman: 0.34.0
         Before reporting problems, check http://wiki.x.org
         to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default
setting,
         (++) from command line, (!!) notice, (II) informational,
         (WW) warning, (EE) error, (NI) not implemented, (??)
unknown.
(==) Log file: "/home/bob/.local/share/xorg/Xorg.0.log", Time:
Tue Jun 18 14:33:10 2019
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
on.(EE) (EE) Server terminated with error (1). Closing log
file.tional informatixinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error
$ tail -f .local/share/xorg/Xorg.0.log
Fatal server error:
[ 12588.925] (EE) AddScreen/ScreenInit failed for driver 0
[ 12588.925] (EE)
[ 12588.925] (EE)
Please consult the The X.Org Foundation support
          at http://wiki.x.org
  for help.
[ 12588.925] (EE) Please also check the log file at
"/home/bob/.local/share/xorg/Xorg.0.log" for additional
information.
[ 12588.925] (EE)
[ 12588.942] (EE) Server terminated with error (1). Closing log
file.
-snip-

In:

"AddScreen/ScreenInit failed for driver 0"

I don't know to what "driver 0" refers.


Thank you

--
These are not the droids you are looking for.

Reply | Threaded
Open this post in threaded view
|

Re: Okay, let's get X workingg on my new Stretch

bw-2
In reply to this post by Bob Bernstein
In-Reply-To: <[hidden email]>

Bob Bernstein <[hidden email]> says:
[snip]
>    Driver      "radeon"
...
>Running X -config xorg.conf.new produces a nice blank black screen but no
>sign of a mouse.

You usually would not need an xorg.conf do you have firmware-amd-graphics
installed for the radeon board?

Reply | Threaded
Open this post in threaded view
|

Re: Okay, let's get X workingg on my new Stretch

Bob Bernstein
On Tue, Jun 18, 2019 at 04:21:31PM -0400, bw wrote:

> You usually would not need an xorg.conf do you have
> firmware-amd-graphics installed for the radeon board?

Here's what I show:

# dpkg -l |grep firm

ii firmware-amd-graphics 20161130-5
   all          Binary firmware for AMD/ATI graphics chips
   
ii firmware-linux-free 3.4
      all          Binary firmware for various drivers in
      the Linux kernel

ii  firmware-linux-nonfree                      
      20161130-5
         all Binary firmware for various drivers in the
         Linux kernel (meta-package)
         
ii firmware-misc-nonfree
         20161130-5 all Binary firmware for various
            drivers in the Linux kernel

Are there others I should have?
           
Thank you

--
"In our age there is no such thing as ‘keeping out of
politics’. All issues are political issues, and politics
itself is a mass of lies, evasions, folly, hatred, and
schizophrenia."

 George Orwell "Politics and the English Language" (1946)

Reply | Threaded
Open this post in threaded view
|

Re: Okay, let's get X workingg on my new Stretch

Bob Bernstein
In reply to this post by Bob Bernstein
I don't know if this made it to the list.


---------- Forwarded message ----------
From: Bob Bernstein <[hidden email]>
To: Debian User List <[hidden email]>
Subject: Re: Okay, let's get X workingg on my new Stretch
Date: Tue, 18 Jun 2019 14:45:01
User-Agent: Alpine 2.21 (DEB 202 2017-01-01)

More data:

-snip-
$ startx

X.Org X Server 1.19.2
Release Date: 2017-03-02
X Protocol Version 11, Revision 0
Build Operating System: Linux 4.9.0-8-amd64 x86_64 Debian
Current Operating System: Linux debian.localdomain 4.9.0-9-amd64 #1 SMP Debian
4.9.168-1+deb9u3 (2019-06-16) x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.9.0-9-amd64
root=UUID=b67d82e0-9444-4663-b3d4-1a4d20d2a0ef ro quiet
Build Date: 03 November 2018  03:09:11AM
xorg-server 2:1.19.2-1+deb9u5 (https://www.debian.org/support)
Current version of pixman: 0.34.0
         Before reporting problems, check http://wiki.x.org
         to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
         (++) from command line, (!!) notice, (II) informational,
         (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/home/bob/.local/share/xorg/Xorg.0.log", Time: Tue Jun 18
14:33:10 2019
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
on.(EE) (EE) Server terminated with error (1). Closing log file.tional
informatixinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error
-snip-

Here is the log associated with the above events

-snip-
Current Operating System: Linux debian.localdomain 4.9.0-9-amd64 #1 SMP Debian
4.9.168-1+deb9u3 (2019-06-16) x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.9.0-9-amd64
root=UUID=b67d82e0-9444-4663-b3d4-1a4d20d2a0ef ro quiet
Build Date: 03 November 2018  03:09:11AM
xorg-server 2:1.19.2-1+deb9u5 (https://www.debian.org/support)
Current version of pixman: 0.34.0
         Before reporting problems, check http://wiki.x.org
         to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
         (++) from command line, (!!) notice, (II) informational,
         (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/home/bob/.local/share/xorg/Xorg.0.log", Time: Tue Jun 18
14:33:10 2019
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
on.(EE) (EE) Server terminated with error (1). Closing log file.tional
informatixinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error
$ tail -f .local/share/xorg/Xorg.0.log
Fatal server error:
[ 12588.925] (EE) AddScreen/ScreenInit failed for driver 0
[ 12588.925] (EE)
[ 12588.925] (EE)
Please consult the The X.Org Foundation support
          at http://wiki.x.org
  for help.
[ 12588.925] (EE) Please also check the log file at
"/home/bob/.local/share/xorg/Xorg.0.log" for additional information.
[ 12588.925] (EE)
[ 12588.942] (EE) Server terminated with error (1). Closing log file.
-snip-

In:

"AddScreen/ScreenInit failed for driver 0"

I don't know to what "driver 0" refers.


Thank you

--
These are not the droids you are looking for.

Reply | Threaded
Open this post in threaded view
|

Re: Okay, let's get X workingg on my new Stretch

Felix Miata-3
In reply to this post by Bob Bernstein
Bob Bernstein composed on 2019-06-18 13:45 (UTC-0400):

> The mouse proves elusive:

> # dmesg |grep -i mouse
> [    2.645218] mousedev: PS/2 mouse device common for all mice
> [    3.225344] psmouse serio1: logips2pp: Detected unknown
> Logitech mouse model
> 90
> [    3.722367] input: ImExPS/2 Logitech Explorer Mouse as
> /devices/platform/i8042/serio1/input/input2

> BUT:

> Running $ X -configure yields:

in most cases, a useless waste of time. For nearly every system, Xorg automagic
does a satisfactory job.

What happens when you start X with no /etc/X11/xorg.conf at all? What is the
output from:

        ls -l /etc/X11/xorg.conf.d/ ?

> Running X -config xorg.conf.new produces a nice blank black
> screen but no sign of a mouse.

Does this match errant behavior that triggered you starting this thread? Given the
trouble you had with networking, something seems to have gone amiss with your
dist-upgrade in spite of your ounce of prevention. Was Jessie an upgrade from
Wheezy? From Squeeze to Wheezy to Jessie? Farther back?

Logitech pointing devices always just work for me.
--
Evolution as taught in public schools is religion, not science.

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

Felix Miata  ***  http://fm.no-ip.com/

Reply | Threaded
Open this post in threaded view
|

Re: Okay, let's get X workingg on my new Stretch

Bob Bernstein
In reply to this post by Bob Bernstein
I put this into google: "systemd X windows Debian" and was
brought here:

https://www.debian.org/doc/manuals/debian-reference/ch07.en.html

I executed the suggested command:

# dpkg-reconfigure --priority=low x11-common

...and then decided to throw all caution to the winds:

# startx

Saints Be Praised! I had a colorful image in front of me, and my
icewm had been neatly launched. No mouse problem. OMG!

But it only works for root.

:(

We're almost there kids. Please bear with me, as I know I have
been testing the patience of some of you.

Thank you

--
Poobah

Reply | Threaded
Open this post in threaded view
|

Re: Okay, let's get X workingg on my new Stretch

Nicholas Geovanis-2
So I think your next/last step will be to open X security to that display for the non-root user you tried. The command is xhost, but it's possible you may need to install it.

On Tue, Jun 18, 2019, 5:49 PM Bob Bernstein <[hidden email]> wrote:
I put this into google: "systemd X windows Debian" and was
brought here:

https://www.debian.org/doc/manuals/debian-reference/ch07.en.html

I executed the suggested command:

# dpkg-reconfigure --priority=low x11-common

...and then decided to throw all caution to the winds:

# startx

Saints Be Praised! I had a colorful image in front of me, and my
icewm had been neatly launched. No mouse problem. OMG!

But it only works for root.

:(

We're almost there kids. Please bear with me, as I know I have
been testing the patience of some of you.

Thank you

--
Poobah

Reply | Threaded
Open this post in threaded view
|

Re: Okay, let's get X workingg on my new Stretch

Felix Miata-3
In reply to this post by Bob Bernstein
Bob Bernstein composed on 2019-06-18 18:48 (UTC-0400):

> # startx

> Saints Be Praised! I had a colorful image in front of me, and my
> icewm had been neatly launched. No mouse problem. OMG!

> But it only works for root.

The gods of security have decreed that instead of startx you must use a display
manager to login and start your X session.

Don't let anyone know I suggested how to have startx work for other than root. ;-)
The security gods have determined it is unreasonably dangerous (and it might not
help):

        sudo chmod 4711 /usr/bin/Xorg
        startx

IMO it's OK to use to test that X works at all before choosing and installing a
display manager. Future updates will undo the chmod (for your safety).
--
Evolution as taught in public schools is religion, not science.

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

Felix Miata  ***  http://fm.no-ip.com/

Reply | Threaded
Open this post in threaded view
|

Re: Okay, let's get X workingg on my new Stretch

Nicholas Geovanis-2

On Tue, Jun 18, 2019 at 6:21 PM Felix Miata <[hidden email]> wrote:

IMO it's OK to use to test that X works at all before choosing and installing a
display manager. Future updates will undo the chmod (for your safety).

The conveniences you have demanded are now mandatory.
-- Jello Biafra
 


Felix Miata  ***  http://fm.no-ip.com/

Reply | Threaded
Open this post in threaded view
|

Re: Okay, let's get X workingg on my new Stretch

Bob Bernstein-3
In reply to this post by Felix Miata-3
On Tue, 18 Jun 2019, Felix Miata wrote:

> The gods of security have decreed that instead of startx you
> must use a display manager to login and start your X session.

This statement had such a clear veridical ring to it I realized
it would be foolish to submit myself, all of you, and the cat,
to any further nonsense, so "apt-get install xdm" and bingo here
we are.

I have no idea what they've done to xhost but they've clearly
taken that also out of our work-tarnished prole hands.

Thanks all!

--
These are not the droids you are looking for.

Reply | Threaded
Open this post in threaded view
|

Re: Okay, let's get X workingg on my new Stretch

Greg Wooledge
In reply to this post by Felix Miata-3
On Tue, Jun 18, 2019 at 07:21:35PM -0400, Felix Miata wrote:
> The gods of security have decreed that instead of startx you must use a display
> manager to login and start your X session.

Utter nonsense.  startx works in every release of Debian.  Every single
one.  I use it myself.

Be aware that under *current* Debian releases (stretch and buster), an
attempt is made to run the X server as your own user instead of setuid
to root.  In order for that to work, your user must be able to login
successfully with a full systemd login session.  If your user account is
defined locally in /etc/passwd, and if you haven't done anything unusual
to your init system or kernel boot parameters, and if you have all of
the required firmware, it should just work.

This also means your X log file may be in ~/.local/share/xorg/ instead
of in /var/log/.

See <https://wiki.debian.org/NewInStretch>.

(Under buster, if your users are defined in a network service like NIS
or possibly LDAP, you may have to take special steps to allow systemd
to retrieve your account credentials.  See bug #878625.  We can worry
about that if it becomes relevant.)

Reply | Threaded
Open this post in threaded view
|

Re: Okay, let's get X workingg on my new Stretch

David Wright-3
In reply to this post by Bob Bernstein
On Tue 18 Jun 2019 at 18:48:52 (-0400), Bob Bernstein wrote:
> I put this into google: "systemd X windows Debian" and was brought
> here:
>
> https://www.debian.org/doc/manuals/debian-reference/ch07.en.html

… which includes the statement "The entire X architecture is
considered insecure if run as root. You must always use the lowest
privilege level possible, like a regular user account."

> I executed the suggested command:
>
> # dpkg-reconfigure --priority=low x11-common
>
> ...and then decided to throw all caution to the winds:
>
> # startx
>
> Saints Be Praised! I had a colorful image in front of me, and my icewm
> had been neatly launched. No mouse problem. OMG!
>
> But it only works for root.
>
> :(

Posting that something works, when the command is delinquent (how
Americans love that word :) ), is not much help in diagnosis. So
it might be worth posting the mode of failure using the command
under the correct circumstances, ie as a user. It might avoid the
scattergun fixes being suggested by some.

I've never run startx as root, and have no idea what's supposed to
be the result. (Because of the frequency with which one starts an
X server, I use a function to call startx, so that my fingers don't
get used to typing it.)

As Greg said, startx has always worked; since 1996 for me. On jessie,
-rwsr-sr-x 1 root   root        9468 Apr  1  2014 X*
but on stretch:
lrwxrwxrwx 1 root   root           4 Oct 31  2018 X -> Xorg*
-rwxr-xr-x 1 root   root         274 Oct 31  2018 Xorg*
hence the move by the logs.

> We're almost there kids. Please bear with me, as I know I have been
> testing the patience of some of you.

Cheers,
David.

Reply | Threaded
Open this post in threaded view
|

Re: Okay, let's get X workingg on my new Stretch

Greg Wooledge
On Wed, Jun 19, 2019 at 12:57:26PM -0500, David Wright wrote:
> I've never run startx as root, and have no idea what's supposed to
> be the result.

I have, for testing purposes.  When trying to get firmware/drivers
working, it's nice to just log in as root and do all the steps that
way.

If you don't have a Desktop Environment installed (or configured via
the alternatives system), it'll just run whatever your x-window-manager
alternative points to.  Or whatever you supply on the startx line.

Once you confirm that X runs, you'll want to log out of the root session
fairly quickly.