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

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

Problems with upgrade from Wheezy to Jessie

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

Contents

  Problems with upgrade from Wheezy to Jessie Hans Kraus <hans@hanswkraus.com> - 2016-10-02 18:30 +0200
    Re: Problems with upgrade from Wheezy to Jessie brian <brian@meadows.pair.com> - 2016-10-02 19:00 +0200
      Re: Problems with upgrade from Wheezy to Jessie err404@free.fr - 2016-10-02 19:40 +0200
        Re: Problems with upgrade from Wheezy to Jessie brian <brian@meadows.pair.com> - 2016-10-02 20:30 +0200
          Re: Problems with upgrade from Wheezy to Jessie Felix Miata <mrmazda@earthlink.net> - 2016-10-03 07:00 +0200
            Re: Problems with upgrade from Wheezy to Jessie brian <brian@meadows.pair.com> - 2016-10-03 09:50 +0200
    Re: Problems with upgrade from Wheezy to Jessie Christian Seiler <christian@iwakd.de> - 2016-10-02 20:40 +0200
      Re: Problems with upgrade from Wheezy to Jessie Brian <ad44@cityscape.co.uk> - 2016-10-02 21:10 +0200
        Re: Problems with upgrade from Wheezy to Jessie Brian <ad44@cityscape.co.uk> - 2016-10-03 19:40 +0200
      Re: Problems with upgrade from Wheezy to Jessie Hans Kraus <hans@hanswkraus.com> - 2016-10-03 19:10 +0200
        Re: Problems with upgrade from Wheezy to Jessie Christian Seiler <christian@iwakd.de> - 2016-10-03 19:30 +0200
          Re: Problems with upgrade from Wheezy to Jessie Hans Kraus <hans@hanswkraus.com> - 2016-10-03 21:10 +0200
            Re: Problems with upgrade from Wheezy to Jessie Christian Seiler <christian@iwakd.de> - 2016-10-03 21:50 +0200
              Re: Problems with upgrade from Wheezy to Jessie Felix Miata <mrmazda@earthlink.net> - 2016-10-04 20:50 +0200
                Re: Problems with upgrade from Wheezy to Jessie Brian <ad44@cityscape.co.uk> - 2016-10-04 22:00 +0200
                  Re: Problems with upgrade from Wheezy to Jessie Brian <ad44@cityscape.co.uk> - 2016-10-05 12:00 +0200
                    Re: Problems with upgrade from Wheezy to Jessie Hans Kraus <hans@hanswkraus.com> - 2016-10-05 20:10 +0200
                      Re: Problems with upgrade from Wheezy to Jessie Brian <ad44@cityscape.co.uk> - 2016-10-05 21:00 +0200
                        Re: Problems with upgrade from Wheezy to Jessie Hans Kraus <hans@hanswkraus.com> - 2016-10-06 20:00 +0200
                          Re: Problems with upgrade from Wheezy to Jessie Brian <ad44@cityscape.co.uk> - 2016-10-06 20:50 +0200
                            Re: Problems with upgrade from Wheezy to Jessie Hans Kraus <hans@hanswkraus.com> - 2016-10-07 19:30 +0200
                              Re: Problems with upgrade from Wheezy to Jessie Brian <ad44@cityscape.co.uk> - 2016-10-07 22:30 +0200
                            Partial Success [was: Re: Problems with upgrade from Wheezy to  Jessie] Hans Kraus <hans@hanswkraus.com> - 2016-10-08 14:00 +0200
                              Re: Partial Success [was: Re: Problems with upgrade from Wheezy to  Jessie] Brian <ad44@cityscape.co.uk> - 2016-10-09 23:50 +0200
                                Re: Partial Success [was: Re: Problems with upgrade from Wheezy to  Jessie] Jörg-Volker Peetz <jvpeetz@web.de> - 2016-10-17 19:20 +0200
              Re: Problems with upgrade from Wheezy to Jessie Jörg-Volker Peetz <jvpeetz@web.de> - 2016-10-05 18:20 +0200
                Re: Problems with upgrade from Wheezy to Jessie Jörg-Volker Peetz <jvpeetz@web.de> - 2016-10-06 20:00 +0200
                  Re:: Problems with upgrade from Wheezy to Jessie Hans Kraus <hans@hanswkraus.com> - 2016-10-06 21:00 +0200
                    Re: : Problems with upgrade from Wheezy to Jessie Jörg-Volker Peetz <jvpeetz@web.de> - 2016-10-06 21:40 +0200
              Re: Problems with upgrade from Wheezy to Jessie Hans Kraus <hans@hanswkraus.com> - 2016-10-06 20:00 +0200
        Re: Problems with upgrade from Wheezy to Jessie Brian <ad44@cityscape.co.uk> - 2016-10-03 19:50 +0200
    Re: Problems with upgrade from Wheezy to Jessie Brian <ad44@cityscape.co.uk> - 2016-10-02 20:50 +0200
    Re: Problems with upgrade from Wheezy to Jessie Eike Lantzsch <zp6cge@gmx.net> - 2016-10-02 22:10 +0200
    Re: Problems with upgrade from Wheezy to Jessie David Christensen <dpchrist@holgerdanske.com> - 2016-10-02 23:50 +0200
      Re: Problems with upgrade from Wheezy to Jessie David Christensen <dpchrist@holgerdanske.com> - 2016-11-06 00:00 +0100
    Re: Problems with upgrade from Wheezy to Jessie Patrick Bartek <nemommxiv@gmail.com> - 2016-10-03 02:10 +0200
      Re: Problems with upgrade from Wheezy to Jessie songbird <songbird@anthive.com> - 2016-10-05 17:20 +0200
    Re: Problems with upgrade from Wheezy to Jessie Felix Miata <mrmazda@earthlink.net> - 2016-10-07 03:30 +0200

Page 2 of 2 — ← Prev page 1 [2]

#173276

Hi,

Am 06.10.2016 um 20:43 schrieb Brian:
> On Thu 06 Oct 2016 at 19:39:21 +0200, Hans Kraus wrote:
>
> [...]
>>> (What does the glxinfo command give?)
>>>
>> root@robbe:~# glxinfo
>> Error: unable to open display
>
> That is when you used a terminal. Boot into X with
>
>   xinit -- vt$XDG_VTNR
>
> It is not pretty but there is an xterm to type commands into. What is
> the output?
>
I'm not able to start the xterm. Nothing happens hen I type Ctrl-D in
the sad computer window.

When I start another shell and login into it I get for
'xinit -- vt$XDG_VTNR':
=====================================================================
(EE)
Fatal server error:
(EE) Server is already active for display 0
	If this server is no longer running, remove /tmp/.X0-lock
	and start again.
(EE)
(EE)
Please consult the The X.Org Foundation support
	 at http://wiki.x.org
  for help.
(EE)
XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
       after 7 requests (7 known processed) with 0 events remaining.
=====================================================================
After deleting /tmp/.X0-lock I get:
=====================================================================
_XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed
_XSERVTransMakeAllCOTSServerListeners: server already running
(EE)
Fatal server error:
(EE) Cannot establish any listening sockets - Make sure an X server 
isn't already running(EE)
(EE)
Please consult the The X.Org Foundation support
	 at http://wiki.x.org
  for help.
(EE) Please also check the log file at "/var/log/Xorg.0.log" for 
additional information.
(EE)
(EE) Server terminated with error (1). Closing log file.
X connection to :0 broken (explicit kill or server shutdown).
=====================================================================
  Thanks & regards,
Hans

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

#173292

On Fri 07 Oct 2016 at 19:05:23 +0200, Hans Kraus wrote:

> Hi,
> 
> Am 06.10.2016 um 20:43 schrieb Brian:
> >On Thu 06 Oct 2016 at 19:39:21 +0200, Hans Kraus wrote:
> >
> >[...]
> >>>(What does the glxinfo command give?)
> >>>
> >>root@robbe:~# glxinfo
> >>Error: unable to open display
> >
> >That is when you used a terminal. Boot into X with
> >
> >  xinit -- vt$XDG_VTNR
> >
> >It is not pretty but there is an xterm to type commands into. What is
> >the output?
> >
> I'm not able to start the xterm. Nothing happens hen I type Ctrl-D in
> the sad computer window.
> 
> When I start another shell and login into it I get for
> 'xinit -- vt$XDG_VTNR':
> =====================================================================
> (EE)
> Fatal server error:
> (EE) Server is already active for display 0
> 	If this server is no longer running, remove /tmp/.X0-lock
> 	and start again.
> (EE)
> (EE)
> Please consult the The X.Org Foundation support
> 	 at http://wiki.x.org
>  for help.
> (EE)
> XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
>       after 7 requests (7 known processed) with 0 events remaining.
> =====================================================================
> After deleting /tmp/.X0-lock I get:
> =====================================================================
> _XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed
> _XSERVTransMakeAllCOTSServerListeners: server already running
> (EE)
> Fatal server error:
> (EE) Cannot establish any listening sockets - Make sure an X server isn't
> already running(EE)
> (EE)
> Please consult the The X.Org Foundation support
> 	 at http://wiki.x.org
>  for help.
> (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional
> information.
> (EE)
> (EE) Server terminated with error (1). Closing log file.
> X connection to :0 broken (explicit kill or server shutdown).
> =====================================================================
>  Thanks & regards,
> Hans

This is getting more complicated.                                                                                       
                                                                                                                        
  ps ax | grep init                                                                                                     
                                                                                                                        
Then kill <process_number> for anything with xinit in it. Maybe.                                                        
                                                                                                                        
There is probably a good reason but the consistent 24 hour lag between a                                                
message and a response from you is not exactly motivating.                                                              
                                                                                                                        
Also, there are other pertinent posts you have not replied to. 

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

#173315 — Partial Success [was: Re: Problems with upgrade from Wheezy to Jessie]

Hi,

after following the propositions of Brian:
>
>  dpkg -l | grep fglrx
>
> Lines with "ii" indicate installed packages. Purge and see what a reboot
> does.
and Jörg-Volker Peetz:
 > Hi,
 >
 > I also saw the other e-mail exchange with Brian where you concluded 
to purge all
 > "fglrx"-related packages. Similarily, there seem to be "nvidia" 
packages on your
 > system. Try
 >
 >  dpkg -l | grep -i nvidia
 >
 > Purge them also. Then have a look which xorg-video drivers are left:
 >
 >  dpkg -l | grep xorg-video
 >
 > Leave only xserver-xorg-video-radeon on the system.
 >
 > And have a look if there's still an "glx-alternative" package left, like
 > glx-alternative-mesa. This could also be purged.

I issued:
=======================================================================
root@robbe:/etc/X11# apt-get purge fglrx-atieventsd fglrx-driver 
fglrx-modules-dkms glx-alternative-fglrx libfglrx:amd64 
libfglrx-amdxvba1:amd64 libgl1-fglrx-glx:amd64

root@robbe:/etc/X11# apt-get purge glx-alternative-nvidia 
libegl1-nvidia:amd64 libgl1-nvidia-glx:amd64 libgl1-nvidia-glx:i386 
libgl1-nvidia-glx-i386 libgles1-nvidia:amd64 libgles2-nvidia:amd64 
libnvidia-eglcore:amd64 libnvidia-ml1:amd64 libnvidia-ml1:amd64 
libxvmcnvidia1:amd64 nvidia-alternative nvidia-driver nvidia-driver-bin 
nvidia-glx nvidia-installer-cleanup nvidia-kernel-common 
nvidia-kernel-dkms nvidia-modprobe nvidia-settings nvidia-support 
nvidia-vdpau-driver:amd64 xserver-xorg-video-nvidia

root@robbe:/etc/X11# apt-get install xserver-xorg-video-radeon
Reading package lists... Done
Building dependency tree
Reading state information... Done
xserver-xorg-video-radeon is already the newest version.
xserver-xorg-video-radeon set to manually installed.
The following package was automatically installed and is no longer required:
   libxnvctrl0
Use 'apt-get autoremove' to remove it.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@robbe:/etc/X11#
=======================================================================
Which partially solved my problems. The system is now booting into Gnome
again.

A problem remains: the contents of the screen (I controlled only text
based ones like Thunderbird) are sometimes overwritten. This happens for
lines where the text is partially overwritten with other text (normally
or skewed) and line backgrounds. The contents are restored if I move the
mouse pointer to the distorted parts.

This looks like a driver issue to me. Is there a better mailing list to
cope with these problems as 'debian-user'?

Many thanks to all which helped me,
Kind regards,
Hans

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

#173362 — Re: Partial Success [was: Re: Problems with upgrade from Wheezy to Jessie]

On Sat 08 Oct 2016 at 13:50:19 +0200, Hans Kraus wrote:

> after following the propositions of Brian:
> >
> > dpkg -l | grep fglrx
> >
> >Lines with "ii" indicate installed packages. Purge and see what a reboot
> >does.
> and Jörg-Volker Peetz:
> > Hi,
> >
> > I also saw the other e-mail exchange with Brian where you concluded to
> purge all
> > "fglrx"-related packages. Similarily, there seem to be "nvidia" packages
> on your
> > system. Try
> >
> >  dpkg -l | grep -i nvidia
> >
> > Purge them also. Then have a look which xorg-video drivers are left:
> >
> >  dpkg -l | grep xorg-video
> >
> > Leave only xserver-xorg-video-radeon on the system.
> >
> > And have a look if there's still an "glx-alternative" package left, like
> > glx-alternative-mesa. This could also be purged.
> 
> I issued:

[Account of package purging snipped]

> Which partially solved my problems. The system is now booting into Gnome
> again.

This is a fantastic step forwards. Before you had nothing, now you have
something. Why the original issue occured is a mystery. Why it was cured
is also a mystery.

> A problem remains: the contents of the screen (I controlled only text
> based ones like Thunderbird) are sometimes overwritten. This happens for
> lines where the text is partially overwritten with other text (normally
> or skewed) and line backgrounds. The contents are restored if I move the
> mouse pointer to the distorted parts.
> 
> This looks like a driver issue to me. Is there a better mailing list to
> cope with these problems as 'debian-user'?

But now the proposition is very different. We know you cannot have that
much of a driver problem because you can boot into GNOME. But you think
you have. Maybe its so. Let's eliminate GNOME.

Boot and do 'ps ax | grep xinit'. Kill xinit with 'kill process_number'.
Install fvwm and xterm (you can purge them later). Issue the command
'startx'. Check that nothing gnomish is running with 'ps ax | grep gnome.

Start an xterm (right or left click, I forget which). Any problems?
Start iceweasel (firefox) from an xterm. Any problems? Read a few man
pages. Any problems? Play with opening any program on your system. Any
problems? Which program? What are the symptoms?

-- 
Brian.

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

#173544 — Re: Partial Success [was: Re: Problems with upgrade from Wheezy to Jessie]

Hi Hans,

so the radeon driver seems to work but maybe needs some tweaking.

1) Let's have a look at Xorg.0.log.
     grep -i chipset /var/log/Xorg.0.log
     grep -i render /var/log/Xorg.0.log
   (Maybe, append the file to your message)
2) Is there a file /etc/X11/xorg.conf?
3) Take a look at the man-page of "radeon" (man radeon)

Regards,
jvp.

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

#173209

Hans Kraus wrote on 10/04/16 20:01:
> Hi,
> 
> The VGA output:
> ========================================================================
> 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Turks
> XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller])
>     Subsystem: ASUSTeK Computer Inc. Device 03e0
>     Flags: bus master, fast devsel, latency 0, IRQ 53
>     Memory at d0000000 (64-bit, prefetchable) [size=256M]
>     Memory at fe2e0000 (64-bit, non-prefetchable) [size=128K]
>     I/O ports at 8000 [size=256]
>     Expansion ROM at fe2c0000 [disabled] [size=128K]
>     Capabilities: [50] Power Management version 3
>     Capabilities: [58] Express Legacy Endpoint, MSI 00
>     Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
>     Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?>
>     Capabilities: [150] Advanced Error Reporting
>     Kernel driver in use: radeon
> ========================================================================
> I appended the '/var/log/Xorg.0.log' as text file. I hope that's OK.
> 
> As far as I know I didn't install a special video driver. At least not
> for Jessie, and, to the best of my knowledge, not for Wheezy too.
> 
<snip>

What is the output of

   dpkg -S /usr/lib/xorg/modules/linux/libglx.so

which is loaded according to Xorg.0.log?

Regards,
jvp.

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

#173245

Hans Kraus wrote on 10/06/16 19:40:
>
>
> Am 05.10.2016 um 22:16 schrieb Jörg-Volker Peetz:
>> [already sent to the list; sent it again to you since you asked for CC]
>>
>> Hans Kraus wrote on 10/04/16 20:01:
>>> Hi,
>>>
>>> The VGA output:
>>> ========================================================================
>>> 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Turks
>>> XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller])
>>>     Subsystem: ASUSTeK Computer Inc. Device 03e0
>>>     Flags: bus master, fast devsel, latency 0, IRQ 53
>>>     Memory at d0000000 (64-bit, prefetchable) [size=256M]
>>>     Memory at fe2e0000 (64-bit, non-prefetchable) [size=128K]
>>>     I/O ports at 8000 [size=256]
>>>     Expansion ROM at fe2c0000 [disabled] [size=128K]
>>>     Capabilities: [50] Power Management version 3
>>>     Capabilities: [58] Express Legacy Endpoint, MSI 00
>>>     Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
>>>     Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?>
>>>     Capabilities: [150] Advanced Error Reporting
>>>     Kernel driver in use: radeon
>>> ========================================================================
>>> I appended the '/var/log/Xorg.0.log' as text file. I hope that's OK.
>>>
>>> As far as I know I didn't install a special video driver. At least not
>>> for Jessie, and, to the best of my knowledge, not for Wheezy too.
>>>
>> <snip>
>>
>> What is the output of
>>
>>    dpkg -S /usr/lib/xorg/modules/linux/libglx.so
>>
>> which is loaded according to Xorg.0.log?
>>
>> Regards,
>> jvp.
>
> root@robbe:~# dpkg -S /usr/lib/xorg/modules/linux/libglx.so
> dpkg-query: no path found matching pattern /usr/lib/xorg/modules/linux/libglx.so
>
> Regards,
> Hans
>

Is this file really present on your system? What does

  ls -lF /usr/lib/xorg/modules/linux/libglx.so

show? Is there a link somewhere in this path?

  ls -lF /usr/lib/xorg/modules/linux
  ls -lF /usr/lib/xorg/modules

According to Xorg.0.log it should belong to some NVIDIA package.

What does

  dpkg -S /usr/lib/xorg/modules/linux

print out?

Regards,
jvp.

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

#173252 — Re:: Problems with upgrade from Wheezy to Jessie

Hi,

the requested outputs:

Am 06.10.2016 um 19:56 schrieb Jörg-Volker Peetz:
> Hans Kraus wrote on 10/06/16 19:40:
>>
>>
>> Am 05.10.2016 um 22:16 schrieb Jörg-Volker Peetz:
>>> [already sent to the list; sent it again to you since you asked for CC]
>>>
>>> Hans Kraus wrote on 10/04/16 20:01:
>>>> Hi,
>>>>
>>>> The VGA output:
>>>> ========================================================================
>>>> 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Turks
>>>> XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller])
>>>>     Subsystem: ASUSTeK Computer Inc. Device 03e0
>>>>     Flags: bus master, fast devsel, latency 0, IRQ 53
>>>>     Memory at d0000000 (64-bit, prefetchable) [size=256M]
>>>>     Memory at fe2e0000 (64-bit, non-prefetchable) [size=128K]
>>>>     I/O ports at 8000 [size=256]
>>>>     Expansion ROM at fe2c0000 [disabled] [size=128K]
>>>>     Capabilities: [50] Power Management version 3
>>>>     Capabilities: [58] Express Legacy Endpoint, MSI 00
>>>>     Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
>>>>     Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?>
>>>>     Capabilities: [150] Advanced Error Reporting
>>>>     Kernel driver in use: radeon
>>>> ========================================================================
>>>> I appended the '/var/log/Xorg.0.log' as text file. I hope that's OK.
>>>>
>>>> As far as I know I didn't install a special video driver. At least not
>>>> for Jessie, and, to the best of my knowledge, not for Wheezy too.
>>>>
>>> <snip>
>>>
>>> What is the output of
>>>
>>>    dpkg -S /usr/lib/xorg/modules/linux/libglx.so
>>>
>>> which is loaded according to Xorg.0.log?
>>>
>>> Regards,
>>> jvp.
>>
>> root@robbe:~# dpkg -S /usr/lib/xorg/modules/linux/libglx.so
>> dpkg-query: no path found matching pattern /usr/lib/xorg/modules/linux/libglx.so
>>
>> Regards,
>> Hans
>>
>
> Is this file really present on your system? What does
>
>   ls -lF /usr/lib/xorg/modules/linux/libglx.so
>
> show? Is there a link somewhere in this path?

root@robbe:~# ls -lF /usr/lib/xorg/modules/linux/libglx.so
lrwxrwxrwx 1 root root 38 Sep 25 12:44 
/usr/lib/xorg/modules/linux/libglx.so -> 
/etc/alternatives/glx--linux-libglx.so

>   ls -lF /usr/lib/xorg/modules/linux
>   ls -lF /usr/lib/xorg/modules

root@robbe:~# ls -lF /usr/lib/xorg/modules/linux
total 64
-rw-r--r-- 1 root root 64432 Mar 25  2016 libfglrxdrm.so
lrwxrwxrwx 1 root root    38 Sep 25 12:44 libglx.so -> 
/etc/alternatives/glx--linux-libglx.so
root@robbe:~#
root@robbe:~# ls -lF /usr/lib/xorg/modules
total 15852
-rw-r--r-- 1 root root   205784 Mar 25  2016 amdxmm.so
drwxr-xr-x 2 root root     4096 Sep 25 13:04 drivers/
drwxr-xr-x 2 root root     4096 Sep 25 12:44 extensions/
-rw-r--r-- 1 root root 14984744 Mar 25  2016 glesx.so
drwxr-xr-x 2 root root     4096 Sep 25 12:45 input/
-rw-r--r-- 1 root root    96976 Feb 11  2015 libexa.so
-rw-r--r-- 1 root root    18760 Feb 11  2015 libfbdevhw.so
-rw-r--r-- 1 root root   154768 Feb 11  2015 libfb.so
-rw-r--r-- 1 root root   286992 Feb 11  2015 libglamoregl.so
-rw-r--r-- 1 root root   146248 Feb 11  2015 libint10.so
-rw-r--r-- 1 root root    10440 Feb 11  2015 libshadowfb.so
-rw-r--r-- 1 root root    35080 Feb 11  2015 libshadow.so
-rw-r--r-- 1 root root    22992 Feb 11  2015 libvbe.so
-rw-r--r-- 1 root root    31872 Feb 11  2015 libvgahw.so
-rw-r--r-- 1 root root   195728 Feb 11  2015 libwfb.so
drwxr-xr-x 2 root root     4096 Sep 25 12:44 linux/
drwxr-xr-x 2 root root     4096 Sep 25 12:45 multimedia/

> According to Xorg.0.log it should belong to some NVIDIA package.
>
> What does
>
>   dpkg -S /usr/lib/xorg/modules/linux
>
> print out?

root@robbe:~# dpkg -S /usr/lib/xorg/modules/linux
glx-alternative-nvidia, glx-alternative-fglrx, fglrx-driver: 
/usr/lib/xorg/modules/linux

> Regards,
> jvp.
>
Thanks & regards,
Hans

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

#173257 — Re: : Problems with upgrade from Wheezy to Jessie

Hi,

I also saw the other e-mail exchange with Brian where you concluded to purge all
"fglrx"-related packages. Similarily, there seem to be "nvidia" packages on your
system. Try

 dpkg -l | grep -i nvidia

Purge them also. Then have a look which xorg-video drivers are left:

 dpkg -l | grep xorg-video

Leave only xserver-xorg-video-radeon on the system.

And have a look if there's still an "glx-alternative" package left, like
glx-alternative-mesa. This could also be purged.

Regards,
jvp.

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

#173243

Am 05.10.2016 um 22:16 schrieb Jörg-Volker Peetz:
> [already sent to the list; sent it again to you since you asked for CC]
>
> Hans Kraus wrote on 10/04/16 20:01:
>> Hi,
>>
>> The VGA output:
>> ========================================================================
>> 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Turks
>> XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller])
>>     Subsystem: ASUSTeK Computer Inc. Device 03e0
>>     Flags: bus master, fast devsel, latency 0, IRQ 53
>>     Memory at d0000000 (64-bit, prefetchable) [size=256M]
>>     Memory at fe2e0000 (64-bit, non-prefetchable) [size=128K]
>>     I/O ports at 8000 [size=256]
>>     Expansion ROM at fe2c0000 [disabled] [size=128K]
>>     Capabilities: [50] Power Management version 3
>>     Capabilities: [58] Express Legacy Endpoint, MSI 00
>>     Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
>>     Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?>
>>     Capabilities: [150] Advanced Error Reporting
>>     Kernel driver in use: radeon
>> ========================================================================
>> I appended the '/var/log/Xorg.0.log' as text file. I hope that's OK.
>>
>> As far as I know I didn't install a special video driver. At least not
>> for Jessie, and, to the best of my knowledge, not for Wheezy too.
>>
> <snip>
>
> What is the output of
>
>    dpkg -S /usr/lib/xorg/modules/linux/libglx.so
>
> which is loaded according to Xorg.0.log?
>
> Regards,
> jvp.

root@robbe:~# dpkg -S /usr/lib/xorg/modules/linux/libglx.so
dpkg-query: no path found matching pattern 
/usr/lib/xorg/modules/linux/libglx.so

Regards,
Hans

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

#173158

On Mon 03 Oct 2016 at 18:50:59 +0200, Hans Kraus wrote:

> Hi, thank's for your sppedy reaction.
> 
> With "gui stopped" I mean the following:
> After the boot process, instead of the graphical login screen where
> one can select the user, enter the password and do some selections,
> the following screen appears:
> 
> A pic of a sad computer with the text (the first line is in bold):
> ===================================================================
>        Oh no! Something has gone wrong.
> A problem occurred and the system can't recover.
>         Please log out and try again.
>                -----------
>                | Log Out |
>                -----------
> ===================================================================
> I get the same screen when I choose another shell (via Ctrl-Alt-F2),
> log in as root and enter: startx.

Stop gdm3:

  systemctl stop gdm.service

What happens with these two commands?

  xinit -- vt$XDG_VTNR
(Click in the xterm and type ctrl-D to exit).

and

  xinit /usr/bin/gnome-session -- vt$XDG_VTNR

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

#173132

On Sun 02 Oct 2016 at 17:59:48 +0200, Hans Kraus wrote:

> I upgraded my Debian server about a week ago from Wheezy to Jessie.
> After that the GUI stopped, I see only  the grey screen with the sad
> computer telling me " Oh no, Something is Wrong" and the only option is
> to log out.
> 
> I'm using Gnome as my desktop. I installed the package again with:
> apt-get install task-gnome-desktop
> I did not get any error message, but that didn't cure my problem.
> 
> Afterwards I tried: "dpkg --configure -a". Again, I didn't get any
> error message but  that didn't cure my problem.
> 
> I rebooted the system several times but with no avail.
> 
> Which info should I provide and/or where should I check my system for
> errors? The text based login via ssh (I use Putty from Win 8.1)
> functions without problems.

Difficult this. It doesn't look hardware related because X comes up and
you get what is known as the "fail whale" (and a most informative and
helpful message :) ).

Also difficult because what you had personally configured on Wheezy is
unknown. So we'll try a thing or two. No guarantees.

Disable logging in with gdm3 with

  systemctl set-default multi-user.target

You can reverse this with

  systemctl set-default graphical.target

Make sure you have xinit installed ('dpkg -l xinit') and reboot. Log in
and run 'startx'. Over to you.

-- 
Brian.

  

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

#173135

On Sonntag, 2. Oktober 2016 17:59:48 PYST Hans Kraus wrote:
> Hi,
> 
> I upgraded my Debian server about a week ago from Wheezy to Jessie.
> After that the GUI stopped, I see only  the grey screen with the sad
> computer telling me " Oh no, Something is Wrong" and the only option is
> to log out.
> 
> I'm using Gnome as my desktop. I installed the package again with:
> apt-get install task-gnome-desktop
> I did not get any error message, but that didn't cure my problem.
> 
> Afterwards I tried: "dpkg --configure -a". Again, I didn't get any
> error message but  that didn't cure my problem.
> 
> I rebooted the system several times but with no avail.
> 
> Which info should I provide and/or where should I check my system for
> errors? The text based login via ssh (I use Putty from Win 8.1)
> functions without problems.
> 
> Kind regards, Hans

Never had this problem but
searching for "Oh no, Something is Wrong" with a hint of "Debian" or "Jessie" 
or "X Window" brings up the following:

https://bbs.archlinux.org/viewtopic.php?id=161310

https://ask.fedoraproject.org/en/question/69051/why-do-i-get-the-oh-no-something-has-gone-wrong-screen-when-using-the-fedora-22-live-dvd/

https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/
1041790

Just my 2 cents ...

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

#173138

On 10/02/2016 08:59 AM, Hans Kraus wrote:
> I upgraded my Debian server about a week ago from Wheezy to Jessie.
> After that the GUI stopped, I see only  the grey screen with the sad
> computer telling me " Oh no, Something is Wrong" and the only option is
> to log out.
> 
> I'm using Gnome as my desktop. I installed the package again with:
> apt-get install task-gnome-desktop
> I did not get any error message, but that didn't cure my problem.
> 
> Afterwards I tried: "dpkg --configure -a". Again, I didn't get any
> error message but  that didn't cure my problem.
> 
> I rebooted the system several times but with no avail.
> 
> Which info should I provide and/or where should I check my system for
> errors? The text based login via ssh (I use Putty from Win 8.1)
> functions without problems.

Some people have computers upon which they have successfully performed
operating system in-place major version upgrades; some boast of several
such upgrades over many years.  I didn't have much success with this
early on, so I pursued the KISS approach instead.  I have invested in
learning and resources that allow me to do image, backup, archive, wipe,
install, configure, restore, migrate, test, commissioning, and cut-over
processes.


I find it helpful to:

1.  Have a dedicated hardware firewall/ router appliance.

2.  Have more than one computer, each dedicate to one purpose:

    a.  File server.

    b.  Backup, archive, and imaging.

    c.  Workstation or laptop (one user each).

    d.  Other, as needed.

3.  Use HDD/SSD mobile racks.

4.  Maintain a supply of spare parts, including a spare computer that
can substitute for any of #2.


It sounds like you have put yourself into a disaster recovery situation.
 I'd advise restoring the Wheezy server, building a fresh Jessie server,
migrating the services and data, testing thoroughly, and making a decision.


David

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

#174218

On 11/05/2016 08:11 AM, someone wrote wrote:
> On Sun, Oct 02, 2016 at 02:39:50PM -0700, David Christensen wrote:
>> early on, so I pursued the KISS approach ....
>>
>> I find it helpful to:
>>
>> 1.  Have a dedicated hardware firewall/ router appliance.
>>
>> 2.  Have more than one computer, each dedicate to one purpose:
>>
>>     a.  File server.
>>
>>     b.  Backup, archive, and imaging.
>>
>>     c.  Workstation or laptop (one user each).
>>
>>     d.  Other, as needed.
>>
>> 3.  Use HDD/SSD mobile racks.
>>
>> 4.  Maintain a supply of spare parts, including a spare computer that
>> can substitute for any of #2.
> 
> Really? Short and Simple approach? 
> 
> It looks more like a 'quite long' and 'not so simple' approach.
> 

KISS = keep it simple, stupid


It's a question of value -- how valuable are the data and services on
the OP's computer?  I assumed they were valuable and responded accordingly.


If the data and services are of no value, then KISS would be running the
computer until it breaks, wiping the HDD, doing a fresh install, and
starting over.  The other stuff is not required.


David

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

#173141

On Sun, 2 Oct 2016 17:59:48 +0200 Hans Kraus <hans@hanswkraus.com>
wrote:

> Hi,
> 
> I upgraded my Debian server about a week ago from Wheezy to Jessie.

What exactly did you do to "upgrade?"  Did you read the Jessie Release
Notes regarding distribution upgrading?

B

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

#173207

Patrick Bartek wrote:
> Hans Kraus <hans@hanswkraus.com> wrote:
>
>> Hi,
>> 
>> I upgraded my Debian server about a week ago from Wheezy to Jessie.
>
> What exactly did you do to "upgrade?"  Did you read the Jessie Release
> Notes regarding distribution upgrading?

  and as a side note, if it is indeed hardware issue
you can run MATE on it as i have an e-machine and
it is working fine for me with MATE.  i also replaced
gdm3 with lightdm.  Gnome has rarely worked well other
than the now obsolete fallback mode or whatever they
called it.

  i've been running testing/sid though too which
is up to version 1.16 of MATE.  i think 1.14 or
1.12 is more stable.  looks like from recent 
discussion they are trying to get 1.18 into the 
next stable release, but i'm not sure they'll be
able to make it under the freeze deadlines.


  songbird

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

#173262

Hans Kraus composed on 2016-10-02 17:59 (UTC+0200):

> I upgraded my Debian server about a week ago from Wheezy to Jessie.
> After that the GUI stopped, I see only  the grey screen with the sad
> computer telling me " Oh no, Something is Wrong" and the only option is
> to log out.

> I'm using Gnome as my desktop. I installed the package again with:
> apt-get install task-gnome-desktop
> I did not get any error message, but that didn't cure my problem.

> Afterwards I tried: "dpkg --configure -a". Again, I didn't get any
> error message but  that didn't cure my problem.

> I rebooted the system several times but with no avail.

> Which info should I provide and/or where should I check my system for
> errors? The text based login via ssh (I use Putty from Win 8.1)
> functions without problems.

	From https://wiki.debian.org/NvidiaGraphicsDrivers#Installation

"If you are doing a distribution upgrade, you should at the very least remove 
all the nvidia packages from wheezy, get your desktop working with nouveau, 
then reinstall the nvidia packages if there is a pressing reason."

So, clearly, distribution upgrading provides booby traps for the unwary 
upgrader. There's no similar mention on the corresponding AMD page for 
upgrading from Wheezy to Jessie. However, there was this warning from
https://wiki.debian.org/ATIProprietary :

"Debian 8 "Jessie"

AMD Catalyst 14.9

For support of Radeon R9 200, Radeon R7 200, Radeon HD 8000, Radeon HD 7000, 
Radeon HD 6000 and Radeon HD 5000 series GPUs (supported devices).

<!> This driver is incompatible with the GNOME desktop, as it does not 
support the EGL interface. It is recommended to use the free radeon driver 
instead. "

So clearly, if you wish to continue with Gnome, you need to purge all traces 
of fglrx from your system before you can expect any FOSS AMD driver to 
function with Gnome. Once that is done, an AMD driver should work 
automatically with your Turks XT 7670 gfxchip. If it doesn't, then you might 
consider to purge xserver-xorg-video-ati and xserver-xorg-video-radeon, and 
install xserver-xorg-video-modesetting (if it isn't already), which should 
result in modesetting driver use automatically. It's built directly into the 
server in Testing and Unstable. This suggests why to use modesetting:
http://www.phoronix.com/scan.php?page=news_item&px=Ubuntu-Debian-Abandon-Intel-DDX
-- 
"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/

[toc] | [prev] | [standalone]

Page 2 of 2 — ← Prev page 1 [2]

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

csiph-web