Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #194934 > unrolled thread

Re: X does not work in Debian 9.4

Back to article view | Back to linux.debian.user

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: X does not work in Debian 9.4 David Wright <deblis@lionunicorn.co.uk> - 2018-04-21 20:30 +0200
    Re: X does not work in Debian 9.4 Long Wind <longwind2@yahoo.com> - 2018-04-21 21:50 +0200
      Re: X does not work in Debian 9.4 Abdullah Ramazanoglu <ar018@yahoo.com> - 2018-04-21 22:20 +0200
      Re: X does not work in Debian 9.4 Felix Miata <mrmazda@earthlink.net> - 2018-04-21 22:20 +0200
        Re: X does not work in Debian 9.4 Felix Miata <mrmazda@earthlink.net> - 2018-04-22 01:10 +0200
          Re: X does not work in Debian 9.4 Long Wind <longwind2@yahoo.com> - 2018-04-22 02:40 +0200
            Re: X does not work in Debian 9.4 Felix Miata <mrmazda@earthlink.net> - 2018-04-22 03:10 +0200
              Re: X does not work in Debian 9.4 Long Wind <longwind2@yahoo.com> - 2018-04-22 11:50 +0200
                Re: X does not work in Debian 9.4 Abdullah Ramazanoglu <ar018@yahoo.com> - 2018-04-22 16:20 +0200
                Re: X does not work in Debian 9.4 Francisco M Neto <fmneto@gmail.com> - 2018-04-22 16:40 +0200
        Re: X does not work in Debian 9.4 David Wright <deblis@lionunicorn.co.uk> - 2018-04-22 05:30 +0200

#194934 — Re: X does not work in Debian 9.4

On Sat 21 Apr 2018 at 01:48:15 (+0000), Long Wind wrote:
> X works in 9.3, it doesn't in 9.4
> i attach log and conf files

My first reaction would be to hide the xorg.conf file and see what X
can do when left to its own devices (no pun intended).

BTW what's you xorg.conf designed to achieve?

Cheers,
David.

[toc] | [next] | [standalone]

#194938

[Multipart message — attachments visible in raw view] — view raw

Thanks! but i don't think deleting xorg.conf will help

the xorg.conf works in stretch 9.3
i created it to set resolution/freq of monitor
it's quite simple, do you see any option in xorg.conf that might cause trouble?

    On Sunday, April 22, 2018, 2:28:55 AM GMT+8, David Wright <deblis@lionunicorn.co.uk> wrote:  
 
 On Sat 21 Apr 2018 at 01:48:15 (+0000), Long Wind wrote:
> X works in 9.3, it doesn't in 9.4
> i attach log and conf files

My first reaction would be to hide the xorg.conf file and see what X
can do when left to its own devices (no pun intended).

BTW what's you xorg.conf designed to achieve?

Cheers,
David.

  

[toc] | [prev] | [next] | [standalone]

#194942

On Sat, 21 Apr 2018 19:42:05 +0000 (UTC) Long Wind said:

> Thanks! but i don't think deleting xorg.conf will help

But it is a step forward towards debugging. If it works with default/auto
settings, but fails with your manual settings, then you can narrow down (even
pinpoint) the offending culprit.

Even if it is related to a kernel upgrade, this is still a useful step, as it
might give you enough information to submit a bug report.

If you are so sure it is related to kernel that you see no reason for
debugging, then you can just try-and-err with different kernel versions. But
then why attach xorg.log in the first place?

Regards
-- 
Abdullah Ramazanoglu

[toc] | [prev] | [next] | [standalone]

#194943

Long Wind composed on 2018-04-21 19:42 (UTC):

> i don't think deleting xorg.conf will help

I think it could and probably would.

> the xorg.conf works in stretch 9.3
> i created it to set resolution/freq of monitor
> it's quite simple, do you see any option in xorg.conf that might cause trouble?

Yes I do think yours might. I think you should read about HorizSync &
VertRefresh in the xorg.conf man page again. While you are there, read about
PreferredMode. If you insist on using an xorg.conf file, then express  HorizSync
and VertRefresh as ranges instead of values. e.g. instead of

	HorizSync	47.71
	VertRefresh	59.79

use

	HorizSync	45-49
	VertRefresh	58-62

or

	HorizSync	30-72
	VertRefresh	56-80

I have ATI Radeon 7500, which is about a year older than your Radeon XPRESS 200,
at least a full generation older. It works just fine @1680x1050 on Debian
Stretch 9.4 without any xorg.conf file:

$ xrandr
Screen 0: minimum 320 x 200, current 1680 x 1050, maximum 4096 x 4096
VGA-0 connected primary 1680x1050+0+0 (normal left inverted right x axis y axis)
474mm x 296mm
   1680x1050     59.97*+  74.89
   1600x1000     60.01
   1280x1024     75.02    72.05    60.02
   1440x900      74.98    59.89
   1152x864      75.00
   1024x768      75.03    70.07    60.00
   800x600       72.19    75.00    60.32
   640x480       75.00    72.81    66.67    59.94
   720x400       70.08
S-video disconnected (normal left inverted right x axis y axis)
$ cat /etc/X11/xorg.conf
cat: /etc/X11/xorg.conf: No such file or directory
$ cat /etc/debian_version
9.4
-- 
"Wisdom is supreme; therefore get wisdom. Whatever else you
get, get wisdom." Proverbs 4:7 (New Living Translation)

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

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

[toc] | [prev] | [next] | [standalone]

#194956

Felix Miata composed on 2018-04-21 16:10 (UTC-0400):

> ...If you insist on using an xorg.conf file, then express  HorizSync
> and VertRefresh as ranges instead of values. e.g. instead of

> 	HorizSync	47.71
> 	VertRefresh	59.79

> use

> 	HorizSync	45-49
> 	VertRefresh	58-62

> or

> 	HorizSync	30-72
> 	VertRefresh	56-80

Did you try either of the above xorg.conf changes?

Is xserver-xorg-legacy installed? If not, see if installing it helps.
-- 
"Wisdom is supreme; therefore get wisdom. Whatever else you
get, get wisdom." Proverbs 4:7 (New Living Translation)

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

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

[toc] | [prev] | [next] | [standalone]

#194959

[Multipart message — attachments visible in raw view] — view raw

 i think my monitor comply with those standards and can support default setting used by X
and your freq range have little chance of solving my problem

and i'm in poor health and not energetic enough to test your solution

i have a look at legacy package you mention, i'm afraid it won't help

Thanks anyway!


    On Sunday, April 22, 2018, 7:03:40 AM GMT+8, Felix Miata <mrmazda@earthlink.net> wrote:  
 
 Felix Miata composed on 2018-04-21 16:10 (UTC-0400):

> ...If you insist on using an xorg.conf file, then express  HorizSync
> and VertRefresh as ranges instead of values. e.g. instead of

>     HorizSync    47.71
>     VertRefresh    59.79

> use

>     HorizSync    45-49
>     VertRefresh    58-62

> or

>     HorizSync    30-72
>     VertRefresh    56-80

Did you try either of the above xorg.conf changes?

Is xserver-xorg-legacy installed? If not, see if installing it helps.
-- 
"Wisdom is supreme; therefore get wisdom. Whatever else you
get, get wisdom." Proverbs 4:7 (New Living Translation)

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

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

  

[toc] | [prev] | [next] | [standalone]

#194960

Long Wind composed on 2018-04-22 00:32 (UTC):

>  i think my monitor comply with those standards and can support default setting used by X
> and your freq range have little chance of solving my problem

You don't know that if you didn't try. Something in the driver could have
changed to cause a rounding difference that differs in 9.4 from 9.3 that puts
your narrow specification out of range. You didn't provide much detail about
what the problem is, that is, what you do or did beside replacing 9.3 with 9.4
that causes it:

1-Is 9.4 an upgrade from 9.3, or a fresh installation?

2-Is it a standard systemd installation, or one that's using sysvinit?

3-Is there a displaymanager installed and running? If so, which one?

4-Are you running startx as root, or as normal user?

5-Are you including any command line options to startx? If so, which one(s)?

6-Do you get the same failure on all vttys?

7-Do you get the same failure booted to the previous kernel?

> and i'm in poor health and not energetic enough to test your solution

Anyone who has enough energy to write an email has enough energy to edit
xorg.conf and restart a PC or startx. I'm not in good health or energetic
either, but that doesn't stop me from typing an email or editing config files.

> i have a look at legacy package you mention, i'm afraid it won't help

What does that mean? Did you try? Comments near the end of
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801605 suggest it very well
might. (permissions on /usr/bin/Xorg or content of /etc/X11/Xwrapper.config
needs needs_root_rights=yes)
-- 
"Wisdom is supreme; therefore get wisdom. Whatever else you
get, get wisdom." Proverbs 4:7 (New Living Translation)

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

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

[toc] | [prev] | [next] | [standalone]

#194971

[Multipart message — attachments visible in raw view] — view raw

 i just return home and check email
by asking so many questions, you surely have more energy than i

url you give seems helpful
#801605 - xserver-xorg: X fails to start as normal user - Debian Bug report logs

i run X as root, and succeed, Thanks!
it seems i'm helping testing/debugging, i'm not interested in such effort

actually i have other option, i can put up with 9.3, which i'm using now to write this mail 

 

    On Sunday, April 22, 2018, 9:09:29 AM GMT+8, Felix Miata <mrmazda@earthlink.net> wrote:  
 
 Long Wind composed on 2018-04-22 00:32 (UTC):

>  i think my monitor comply with those standards and can support default setting used by X
> and your freq range have little chance of solving my problem

You don't know that if you didn't try. Something in the driver could have
changed to cause a rounding difference that differs in 9.4 from 9.3 that puts
your narrow specification out of range. You didn't provide much detail about
what the problem is, that is, what you do or did beside replacing 9.3 with 9.4
that causes it:

1-Is 9.4 an upgrade from 9.3, or a fresh installation?

2-Is it a standard systemd installation, or one that's using sysvinit?

3-Is there a displaymanager installed and running? If so, which one?

4-Are you running startx as root, or as normal user?

5-Are you including any command line options to startx? If so, which one(s)?

6-Do you get the same failure on all vttys?

7-Do you get the same failure booted to the previous kernel?

> and i'm in poor health and not energetic enough to test your solution

Anyone who has enough energy to write an email has enough energy to edit
xorg.conf and restart a PC or startx. I'm not in good health or energetic
either, but that doesn't stop me from typing an email or editing config files.

> i have a look at legacy package you mention, i'm afraid it won't help

What does that mean? Did you try? Comments near the end of
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801605 suggest it very well
might. (permissions on /usr/bin/Xorg or content of /etc/X11/Xwrapper.config
needs needs_root_rights=yes)
-- 
"Wisdom is supreme; therefore get wisdom. Whatever else you
get, get wisdom." Proverbs 4:7 (New Living Translation)

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

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

  

[toc] | [prev] | [next] | [standalone]

#194981

On Sun, 22 Apr 2018 09:44:25 +0000 (UTC) Long Wind said:

> it seems i'm helping testing/debugging, i'm not interested in such effort

So you are not interested in helping with community software problems, but the
community should be interested in helping with your usage problems.

Cool regards
-- 
Abdullah Ramazanoglu

[toc] | [prev] | [next] | [standalone]

#194982

Maybe you should call customer support for the company that sold you
that software.

Oh, wait.

On Sun, 2018-04-22 at 09:44 +0000, Long Wind wrote:
> i just return home and check email
> by asking so many questions, you surely have more energy than i
> 
> url you give seems helpful
> #801605 - xserver-xorg: X fails to start as normal user - Debian Bug
> report logs
> 
> i run X as root, and succeed, Thanks!
> it seems i'm helping testing/debugging, i'm not interested in such
> effort
> 
> actually i have other option, i can put up with 9.3, which i'm using
> now to write this mail 
> 
> 
> 
> On Sunday, April 22, 2018, 9:09:29 AM GMT+8, Felix Miata <mrmazda@eart
> hlink.net> wrote:
> 
> 
> Long Wind composed on 2018-04-22 00:32 (UTC):
> 
> >  i think my monitor comply with those standards and can support
> default setting used by X
> > and your freq range have little chance of solving my problem
> 
> You don't know that if you didn't try. Something in the driver could
> have
> changed to cause a rounding difference that differs in 9.4 from 9.3
> that puts
> your narrow specification out of range. You didn't provide much detail
> about
> what the problem is, that is, what you do or did beside replacing 9.3
> with 9.4
> that causes it:
> 
> 1-Is 9.4 an upgrade from 9.3, or a fresh installation?
> 
> 2-Is it a standard systemd installation, or one that's using sysvinit?
> 
> 3-Is there a displaymanager installed and running? If so, which one?
> 
> 4-Are you running startx as root, or as normal user?
> 
> 5-Are you including any command line options to startx? If so, which
> one(s)?
> 
> 6-Do you get the same failure on all vttys?
> 
> 7-Do you get the same failure booted to the previous kernel?
> 
> > and i'm in poor health and not energetic enough to test your
> solution
> 
> Anyone who has enough energy to write an email has enough energy to
> edit
> xorg.conf and restart a PC or startx. I'm not in good health or
> energetic
> either, but that doesn't stop me from typing an email or editing
> config files.
> 
> > i have a look at legacy package you mention, i'm afraid it won't
> help
> 
> What does that mean? Did you try? Comments near the end of
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801605 suggest it
> very well
> might. (permissions on /usr/bin/Xorg or content of
> /etc/X11/Xwrapper.config
> needs needs_root_rights=yes)
> 
> -- 
> "Wisdom is supreme; therefore get wisdom. Whatever else you
> get, get wisdom." Proverbs 4:7 (New Living Translation)
> 
> Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
> 
> Felix Miata  ***  http://fm.no-ip.com/
> 
-- 
--
[]'s,

Francisco M Neto
Institut für Anorganische Chemie
Universität Duisburg-Essen

[toc] | [prev] | [next] | [standalone]

#194964

On Sat 21 Apr 2018 at 22:01:23 (+0000), Long Wind wrote:
>  i copy those freq from monitor's manual
> and they work in 9.3 and early distro
> 
> i remove xorg.conf, error seems same
> see attachment

I don't understand the (EE) line below: do you normally see this with 9.3?
And incidentally do you normally run X on VC2?

--✄--------

[   110.450] (II) Module ABI versions:
[   110.450]    X.Org ANSI C Emulation: 0.4
[   110.450]    X.Org Video Driver: 23.0
[   110.450]    X.Org XInput driver : 24.1
[   110.450]    X.Org Server Extension : 10.0
[   110.450] (EE) dbus-core: error connecting to system bus:
             org.freedesktop.DBus.Error.FileNotFound
             (Failed to connect to socket
             /var/run/dbus/system_bus_socket:
             No such file or directory)
[   110.450] (++) using VT number 2

[   110.451] (II) xfree86: Adding drm device (/dev/dri/card0)

--✄--------

Here's what I get at the same point:

--✄--------

(II) Module ABI versions:
        X.Org ANSI C Emulation: 0.4
        X.Org Video Driver: 23.0
        X.Org XInput driver : 24.1
        X.Org Server Extension : 10.0
(++) using VT number 1

(II) systemd-logind: took control of session /org/freedesktop/login1/session/_31
(II) xfree86: Adding drm device (/dev/dri/card0)
(II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 11 paused 0

--✄--------

Cheers,
David.

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web