Re: Problems with upgrade from Wheezy to Jessie

[David Christensen]

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

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

[Jörg-Volker Peetz]

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.

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

[Hans Kraus]

Hi,

Am 09.10.2016 um 23:46 schrieb Brian:

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?


Sorry, 'ps ax | grep xinit' didn't give any processes. The most similar
to X thing I found was:
=
 1350 tty7 Ssl+   4:14 /usr/bin/Xorg :0 -novtswitch -background 
none -noreset -verbose 3 -auth 
/var/run/gdm3/auth-for-Debian-gdm-ceY7sk/database -seat seat0 -nolisten 
tcp vt7

=
The whole output pf 'ps ax' is enclosed as ps.txt. Two parts of
screenshots with error regions in them are enclosed as err?.png.
I hope that's OK to include small graphics files, but to describe
display problems in text form is a bit awkward (at least to me).

I thought that my problems may be driver related because when I saw such
behaviour on Windows machines the culprit was always the graphics
driver.

Thanks & regards,
Hans

  PID TTY  STAT   TIME COMMAND
1 ?Ss 0:39 /sbin/init
2 ?S  0:00 [kthreadd]
3 ?S  0:24 [ksoftirqd/0]
5 ?S< 0:00 [kworker/0:0H]
7 ?S  4:38 [rcu_sched]
8 ?S  0:00 [rcu_bh]
9 ?S  0:00 [migration/0]
   10 ?S  0:01 [watchdog/0]
   11 ?S  0:01 [watchdog/1]
   12 ?S  0:00 [migration/1]
   13 ?S  0:21 [ksoftirqd/1]
   15 ?S< 0:00 [kworker/1:0H]
   16 ?S  0:01 [watchdog/2]
   17 ?S  0:00 [migration/2]
   18 ?S  0:20 [ksoftirqd/2]
   20 ?S< 0:00 [kworker/2:0H]
   21 ?S  0:01 [watchdog/3]
   22 ?S  0:00 [migration/3]
   23 ?S  0:20 [ksoftirqd/3]
   25 ?S< 0:00 [kworker/3:0H]
   26 ?S  0:01 [watchdog/4]
   27 ?S  0:00 [migration/4]
   28 ?S  0:24 [ksoftirqd/4]
   30 ?S< 0:00 [kworker/4:0H]
   31 ?S  0:01 [watchdog/5]
   32 ?S  0:00 [migration/5]
   33 ?S  0:21 [ksoftirqd/5]
   35 ?S< 0:00 [kworker/5:0H]
   36 ?S< 0:00 [khelper]
   37 ?S  0:00 [kdevtmpfs]
   38 ?S< 0:00 [netns]
   39 ?S  0:00 [khungtaskd]
   40 ?S< 0:00 [writeback]
   41 ?SN 0:00 [ksmd]
   42 ?SN 0:00 [khugepaged]
   43 ?S< 0:00 [crypto]
   44 ?S< 0:00 [kintegrityd]
   45 ?S< 0:00 [bioset]
   46 ?S< 0:00 [kblockd]
   50 ?S  0:00 [kswapd0]
   51 ?S< 0:00 [vmstat]
   52 ?S  0:03 [fsnotify_mark]
   58 ?S< 0:00 [kthrotld]
   60 ?S< 0:00 [ipv6_addrconf]
   62 ?S< 0:00 [deferwq]
  107 ?S  0:00 [scsi_eh_0]
  108 ?S< 0:00 [ata_sff]
  109 ?S  0:00 [khubd]
  110 ?S< 0:00 

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

[Brian]

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.

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

[Hans Kraus]

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

Re: Problems with upgrade from Wheezy to Jessie

[Brian]

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  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. 

Re: Problems with upgrade from Wheezy to Jessie

[Hans Kraus]

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

Re: Problems with upgrade from Wheezy to Jessie

[Felix Miata]

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=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/

Re: : Problems with upgrade from Wheezy to Jessie

[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.

Regards,
jvp.

Re:: Problems with upgrade from Wheezy to Jessie

[Hans Kraus]

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 d000 (64-bit, prefetchable) [size=256M]
Memory at fe2e (64-bit, non-prefetchable) [size=128K]
I/O ports at 8000 [size=256]
Expansion ROM at fe2c [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.




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 root38 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 root96976 Feb 11  2015 libexa.so
-rw-r--r-- 1 root root18760 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 root10440 Feb 11  2015 libshadowfb.so
-rw-r--r-- 1 root root35080 Feb 11  2015 libshadow.so
-rw-r--r-- 1 root root22992 Feb 11  2015 libvbe.so
-rw-r--r-- 1 root root31872 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

Re: Problems with upgrade from Wheezy to Jessie

[Brian]

On Thu 06 Oct 2016 at 19:39:21 +0200, Hans Kraus wrote:

> Hi,
> 
> Am 05.10.2016 um 20:58 schrieb Brian:
> >On Wed 05 Oct 2016 at 19:50:50 +0200, Hans Kraus wrote:
> >
> >>thanks to all. Brian is right with his opinion that I'm not subscribed
> >>to the list. I sent a 'subscribe' to
> >> but didn't get an answer
> >>(or at least I didn't find it).
> >
> >The reply comes back to the address you subscribed from. Maybe that
> >wasn't h...@hanswkraus.com. But we will not dwell on that; you can sort
> >it out at another time.
> >
> >>How do I switch drivers under Debian, especiallay from the "AMD FGLRX driver
> >>for Radeon adapters" to the "free radeon driver, which is the default in
> >>jessie"?
> >
> >I did not mean to imply you are using the FGLRX driver. Your "lspci -v"
> >output shows
> >
> >  > Kernel driver in use: radeon
> >
> >which implies otherwise. But the journalctl output doesn't look happy.
> >
> >To answer your question:
> >
> >  dpkg -l | grep fglrx
> >
> >Lines with "ii" indicate installed packages. Purge and see what a reboot
> >does.
> 
> root@robbe:~# dpkg -l | grep fglrx
> ii  fglrx-atieventsd 1:15.9-4~deb8u2  amd64
> events daemon for the non-free ATI/AMD RadeonHD display driver
> ii  fglrx-driver 1:15.9-4~deb8u2  amd64non-free
> ATI/AMD RadeonHD display driver
> ii  fglrx-modules-dkms 1:15.9-4~deb8u2  amd64
> dkms module source for the non-free ATI/AMD RadeonHD display driver
> ii  glx-alternative-fglrx   0.5.1
> amd64allows the selection of FGLRX as GLX provider
> ii  libfglrx:amd64 1:15.9-4~deb8u2  amd64
> non-free ATI/AMD RadeonHD display driver (runtime libraries)
> ii  libfglrx-amdxvba1:amd64 1:15.9-4~deb8u2  amd64
> AMD XvBA (X-Video Bitstream Acceleration) backend for VA API
> ii  libgl1-fglrx-glx:amd64 1:15.9-4~deb8u2  amd64
> proprietary libGL for the non-free ATI/AMD RadeonHD display driver
> 
> Is it OK to purge all these?

I would say so. Whether it makes any difference or not is a different
matter. I've never used non-free video drivers. If you have an xorg.conf
in /etc/X11 I'd move it out of the way.

> >(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?

-- 
Brian.

  

Re: Problems with upgrade from Wheezy to Jessie

[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 d000 (64-bit, prefetchable) [size=256M]
>>> Memory at fe2e (64-bit, non-prefetchable) [size=128K]
>>> I/O ports at 8000 [size=256]
>>> Expansion ROM at fe2c [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.
>>>
>> 
>>
>> 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.

Re: Problems with upgrade from Wheezy to Jessie

[Hans Kraus]

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 d000 (64-bit, prefetchable) [size=256M]
Memory at fe2e (64-bit, non-prefetchable) [size=128K]
I/O ports at 8000 [size=256]
Expansion ROM at fe2c [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.




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

Re: Problems with upgrade from Wheezy to Jessie

[Hans Kraus]

Hi,

Am 05.10.2016 um 20:58 schrieb Brian:

On Wed 05 Oct 2016 at 19:50:50 +0200, Hans Kraus wrote:


thanks to all. Brian is right with his opinion that I'm not subscribed
to the list. I sent a 'subscribe' to
 but didn't get an answer
(or at least I didn't find it).


The reply comes back to the address you subscribed from. Maybe that
wasn't h...@hanswkraus.com. But we will not dwell on that; you can sort
it out at another time.


How do I switch drivers under Debian, especiallay from the "AMD FGLRX driver
for Radeon adapters" to the "free radeon driver, which is the default in
jessie"?


I did not mean to imply you are using the FGLRX driver. Your "lspci -v"
output shows

  > Kernel driver in use: radeon

which implies otherwise. But the journalctl output doesn't look happy.

To answer your question:

  dpkg -l | grep fglrx

Lines with "ii" indicate installed packages. Purge and see what a reboot
does.


root@robbe:~# dpkg -l | grep fglrx
ii  fglrx-atieventsd 
1:15.9-4~deb8u2  amd64events daemon for the 
non-free ATI/AMD RadeonHD display driver
ii  fglrx-driver 
1:15.9-4~deb8u2  amd64non-free ATI/AMD 
RadeonHD display driver
ii  fglrx-modules-dkms 
1:15.9-4~deb8u2  amd64dkms module source for 
the non-free ATI/AMD RadeonHD display driver
ii  glx-alternative-fglrx   0.5.1 
amd64allows the selection of FGLRX 
as GLX provider
ii  libfglrx:amd64 
1:15.9-4~deb8u2  amd64non-free ATI/AMD 
RadeonHD display driver (runtime libraries)
ii  libfglrx-amdxvba1:amd64 
1:15.9-4~deb8u2  amd64AMD XvBA (X-Video 
Bitstream Acceleration) backend for VA API
ii  libgl1-fglrx-glx:amd64 
1:15.9-4~deb8u2  amd64proprietary libGL for 
the non-free ATI/AMD RadeonHD display driver


Is it OK to purge all these?


(What does the glxinfo command give?)


root@robbe:~# glxinfo
Error: unable to open display

Thanks,
Hans

Re: Problems with upgrade from Wheezy to Jessie

[Brian]

On Wed 05 Oct 2016 at 19:50:50 +0200, Hans Kraus wrote:

> thanks to all. Brian is right with his opinion that I'm not subscribed
> to the list. I sent a 'subscribe' to
>  but didn't get an answer
> (or at least I didn't find it).

The reply comes back to the address you subscribed from. Maybe that
wasn't h...@hanswkraus.com. But we will not dwell on that; you can sort
it out at another time.

> How do I switch drivers under Debian, especiallay from the "AMD FGLRX driver
> for Radeon adapters" to the "free radeon driver, which is the default in
> jessie"?

I did not mean to imply you are using the FGLRX driver. Your "lspci -v"
output shows

  > Kernel driver in use: radeon

which implies otherwise. But the journalctl output doesn't look happy. 

To answer your question:

  dpkg -l | grep fglrx

Lines with "ii" indicate installed packages. Purge and see what a reboot
does.

(What does the glxinfo command give?)

-- 
Brian.

Re: Problems with upgrade from Wheezy to Jessie

[Hans Kraus]

Hi,

thanks to all. Brian is right with his opinion that I'm not subscribed
to the list. I sent a 'subscribe' to
 but didn't get an answer
(or at least I didn't find it).

How do I switch drivers under Debian, especiallay from the "AMD FGLRX 
driver for Radeon adapters" to the "free radeon driver, which is the 
default in jessie"?


Kind regards,
Hans

PS: Please send any mails regarding this with a 'CC' to me.

Re: Problems with upgrade from Wheezy to Jessie

[Jörg-Volker Peetz]

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 d000 (64-bit, prefetchable) [size=256M]
> Memory at fe2e (64-bit, non-prefetchable) [size=128K]
> I/O ports at 8000 [size=256]
> Expansion ROM at fe2c [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.
> 


What is the output of

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

which is loaded according to Xorg.0.log?

Regards,
jvp.

Re: Problems with upgrade from Wheezy to Jessie

[songbird]

Patrick Bartek wrote:
> Hans Kraus  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

Re: Problems with upgrade from Wheezy to Jessie

[Brian]

On Tue 04 Oct 2016 at 20:55:54 +0100, Brian wrote:

> Incidentally, we know X comes up for the OP (gnome-session runs. Without
> X it wouldn't). So this may not be the problem at all.
> 
>   glxinfo | grep render
> 
> is a good command for the OP to run. We would be interested in its output.

The Radeon HD 6670/7670 appeared in 2011. It would be highly unlikely
for the output of this command not to show

  direct-rendering: Yes

As Patrick Bartek cogently asked:

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

Probably not, so I did it for him.

   > Unlike other OpenGL drivers, the AMD FGLRX driver for
   > Radeon adapters does not support the EGL interface. As
   > such, several GNOME applications, including the core of
   > the GNOME desktop, will not start at all when this driver
   > is in use.

   > It is recommended to use the free radeon driver, which is
   > the default in jessie, instead.

(There is a strong chance that Hans Kraus is not subscribed to this list
and is not reading the list archives to monitor replies to his query,
This will be my first and only CC:)

-- 
Brian.

Re: Problems with upgrade from Wheezy to Jessie

[Brian]

On Tue 04 Oct 2016 at 14:41:11 -0400, Felix Miata wrote:

> Hans Kraus composed on 2016-10-04 20:01 (UTC+0200):
> 
> >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])
> ...
> >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.
> ...
> 
> Do you have xserver-xorg-video-ati, amd64-microcode and firmware-linu*
> installed? Xorg.0.log reports using the radeon driver, but your Turks may
> require the AMD driver from the ati package, and/or firmware not included in
> a default installation.
> 
> (EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not
> found) in Xorg.0.log would normally be a bad sign, but as you're using AMD
> video, the appearance of that message should be a logging error, not a real
> error.

You have highlighted

  > (EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not 
found)

This is an interesting line in the log.

Why should using a radeon card give such a message? What has radeon to
do with nvidia? It could be a logging error but why does it occur? xorg
has sorted out which card is present.

Incidentally, we know X comes up for the OP (gnome-session runs. Without
X it wouldn't). So this may not be the problem at all.

  glxinfo | grep render

is a good command for the OP to run. We would be interested in its output.

However, perhaps the OP could look at

  dpkg -l | grep nvidia

and purge any packages if anything nvidia related is in its output.

-- 
Brian.

Re: Problems with upgrade from Wheezy to Jessie

[Felix Miata]

Hans Kraus composed on 2016-10-04 20:01 (UTC+0200):


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])

...

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.

...

Do you have xserver-xorg-video-ati, amd64-microcode and firmware-linu* 
installed? Xorg.0.log reports using the radeon driver, but your Turks may 
require the AMD driver from the ati package, and/or firmware not included in 
a default installation.


(EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not 
found) in Xorg.0.log would normally be a bad sign, but as you're using AMD 
video, the appearance of that message should be a logging error, not a real 
error.

--
"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/

Re: Problems with upgrade from Wheezy to Jessie

[Hans Kraus]

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 d000 (64-bit, prefetchable) [size=256M]
Memory at fe2e (64-bit, non-prefetchable) [size=128K]
I/O ports at 8000 [size=256]
Expansion ROM at fe2c [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.

Many thanks & regards,
Hans


Am 03.10.2016 um 21:42 schrieb Christian Seiler:

[ kernel, dist-upgrade ]


All looks fine, you seem to have an up to date Jessie system and the
only thing that was installed was the security update DSA-3684-1 of
this morning.

On 10/03/2016 08:42 PM, Hans Kraus wrote:

Oct 02 17:24:37 robbe /etc/gdm3/Xsession[2351]: Xlib:  extension "GLX" missing on display 
":0".
Oct 02 17:24:37 robbe /etc/gdm3/Xsession[2351]: gnome-session-is-accelerated: 
No hardware 3D support.


There's your problem: as far as I know, GNOME under Jessie only works
if you have 3D OpenGL hardware acceleration support. And apparently
your GPU is either not supported (maybe not anymore) or you don't have
the right driver loaded.

Could you post the contents of /var/log/Xorg.0.log? (It may repeat
itself, every time the X server is started, only the last one of
these repeats is sufficient.) Also, what graphics card do you have?
(You can find out via "lspci -v" as root and looking for a device
with "VGA" in the device type.) Do you have any special drivers
installed? (For example, if you have an NVIDIA card, do you have the
proprietary nvidia drivers installed?)

Regards,
Christian

[18.722] 
X.Org X Server 1.16.4
Release Date: 2014-12-20
[18.722] X Protocol Version 11, Revision 0
[18.722] Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian
[18.722] Current Operating System: Linux robbe 3.16.0-4-amd64 #1 SMP Debian 
3.16.36-1+deb8u1 (2016-09-03) x86_64
[18.722] Kernel command line: BOOT_IMAGE=/vmlinuz-3.16.0-4-amd64 
root=/dev/mapper/vg_root-lv_root ro quiet
[18.722] Build Date: 11 February 2015  12:32:02AM
[18.722] xorg-server 2:1.16.4-1 (http://www.debian.org/support) 
[18.722] Current version of pixman: 0.32.6
[18.722]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[18.722] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[18.722] (==) Log file: "/var/log/Xorg.0.log", Time: Sun Oct  2 17:24:35 
2016
[18.724] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[18.726] (==) No Layout section.  Using the first Screen section.
[18.726] (==) No screen section available. Using defaults.
[18.726] (**) |-->Screen "Default Screen Section" (0)
[18.726] (**) |   |-->Monitor ""
[18.726] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[18.726] (==) Automatically adding devices
[18.726] (==) Automatically enabling devices
[18.726] (==) Automatically adding GPU devices
[18.730] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[18.730]Entry deleted from font path.
[18.733] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins
[18.733] (==) ModulePath set to "/usr/lib/xorg/modules"
[18.733] (II) The server relies on udev to provide the list of input 
devices.
If no devices become available, reconfigure udev or disable 
AutoAddDevices.
[18.733] (II) Loader magic: 0x7f58902fbd80
[18.733] (II) Module ABI versions:
[18.733]X.Org ANSI C Emulation: 0.4
[18.733]X.Org Video Driver: 18.0
[18.733]X.Org XInput driver : 21.0
[18.733]X.Org Server Extension : 8.0
[18.733] (II) xfree86: Adding drm device (/dev/dri/card0)
[18.735] (--) PCI:*(0:1:0:0) 1002:6758:1043:03e0 rev 0, Mem 

Re: Problems with upgrade from Wheezy to Jessie

[Christian Seiler]

> [ kernel, dist-upgrade ]

All looks fine, you seem to have an up to date Jessie system and the
only thing that was installed was the security update DSA-3684-1 of
this morning.

On 10/03/2016 08:42 PM, Hans Kraus wrote:
> Oct 02 17:24:37 robbe /etc/gdm3/Xsession[2351]: Xlib:  extension "GLX" 
> missing on display ":0".
> Oct 02 17:24:37 robbe /etc/gdm3/Xsession[2351]: gnome-session-is-accelerated: 
> No hardware 3D support.

There's your problem: as far as I know, GNOME under Jessie only works
if you have 3D OpenGL hardware acceleration support. And apparently
your GPU is either not supported (maybe not anymore) or you don't have
the right driver loaded.

Could you post the contents of /var/log/Xorg.0.log? (It may repeat
itself, every time the X server is started, only the last one of
these repeats is sufficient.) Also, what graphics card do you have?
(You can find out via "lspci -v" as root and looking for a device
with "VGA" in the device type.) Do you have any special drivers
installed? (For example, if you have an NVIDIA card, do you have the
proprietary nvidia drivers installed?)

Regards,
Christian

Re: Problems with upgrade from Wheezy to Jessie

[Hans Kraus]

Hi,

my results:
===
root@robbe:~# uname -a
Linux robbe 3.16.0-4-amd64 #1 SMP Debian 3.16.36-1+deb8u1 (2016-09-03) 
x86_64 GNU/Linux

===
root@robbe:~# apt-get update
Get:1 http://ftp.at.debian.org jessie-backports InRelease [166 kB]
Hit http://ftp.de.debian.org jessie-backports InRelease
Hit http://security.debian.org jessie/updates InRelease
Ign http://ftp.at.debian.org jessie InRelease
Get:2 http://ftp.at.debian.org jessie-updates InRelease [142 kB]
Ign http://linux.dropbox.com wheezy InRelease
Get:3 http://ftp.de.debian.org jessie-backports/main amd64 
Packages/DiffIndex [27.8 kB]

Hit http://linux.dropbox.com wheezy Release.gpg
Hit http://ftp.at.debian.org jessie Release.gpg
Get:4 http://ftp.at.debian.org jessie-backports/main amd64 
Packages/DiffIndex [27.8 kB]
Get:5 http://ftp.at.debian.org jessie-backports/contrib amd64 
Packages/DiffIndex [16.4 kB]
Get:6 http://ftp.at.debian.org jessie-backports/non-free amd64 
Packages/DiffIndex [12.0 kB]
Get:7 http://ftp.at.debian.org jessie-backports/main i386 
Packages/DiffIndex [27.8 kB]

Hit http://linux.dropbox.com wheezy Release
Get:8 http://ftp.at.debian.org jessie-backports/contrib i386 
Packages/DiffIndex [17.4 kB]

Hit http://security.debian.org jessie/updates/main Sources
Get:9 http://ftp.at.debian.org jessie-backports/non-free i386 
Packages/DiffIndex [11.9 kB]
Get:10 http://ftp.at.debian.org jessie-backports/contrib 
Translation-en/DiffIndex [5,500 B]
Get:11 http://ftp.de.debian.org jessie-backports/contrib amd64 
Packages/DiffIndex [16.4 kB]
Get:12 http://ftp.at.debian.org jessie-backports/main 
Translation-en/DiffIndex [27.8 kB]
Get:13 http://ftp.at.debian.org jessie-backports/non-free 
Translation-en/DiffIndex [8,806 B]

Hit http://ftp.at.debian.org jessie Release
Hit http://security.debian.org jessie/updates/contrib Sources
Hit http://security.debian.org jessie/updates/non-free Sources
Get:14 http://ftp.de.debian.org jessie-backports/non-free amd64 
Packages/DiffIndex [12.0 kB]
Get:15 http://ftp.at.debian.org jessie-backports/main i386 
2016-10-03-1508.04.pdiff [1,925 B]

Get:16 http://ftp.at.debian.org jessie-updates/main Sources [15.5 kB]
Get:17 http://ftp.at.debian.org jessie-updates/contrib Sources [32 B]
Hit http://security.debian.org jessie/updates/main amd64 Packages
Hit http://security.debian.org jessie/updates/contrib amd64 Packages
Hit http://security.debian.org jessie/updates/non-free amd64 Packages
Get:18 http://ftp.de.debian.org jessie-backports/main i386 
Packages/DiffIndex [27.8 kB]
Get:19 http://ftp.de.debian.org jessie-backports/contrib i386 
Packages/DiffIndex [17.4 kB]

Hit http://linux.dropbox.com wheezy/main amd64 Packages
Get:20 http://ftp.at.debian.org jessie-backports/main i386 
2016-10-03-1508.04.pdiff [1,925 B]

Get:21 http://ftp.at.debian.org jessie-updates/non-free Sources [920 B]
Get:22 http://ftp.at.debian.org jessie-updates/main amd64 
Packages/DiffIndex [5,440 B]

Get:23 http://ftp.at.debian.org jessie-updates/contrib amd64 Packages [32 B]
Get:24 http://ftp.at.debian.org jessie-updates/non-free amd64 
Packages/DiffIndex [736 B]
Get:25 http://ftp.at.debian.org jessie-updates/main i386 
Packages/DiffIndex [5,440 B]

Get:26 http://ftp.at.debian.org jessie-updates/contrib i386 Packages [32 B]
Hit http://security.debian.org jessie/updates/main i386 Packages
Hit http://security.debian.org jessie/updates/contrib i386 Packages
Hit http://security.debian.org jessie/updates/non-free i386 Packages
Hit http://security.debian.org jessie/updates/contrib Translation-en
Get:27 http://ftp.de.debian.org jessie-backports/non-free i386 
Packages/DiffIndex [11.9 kB]
Get:28 http://ftp.de.debian.org jessie-backports/contrib 
Translation-en/DiffIndex [5,500 B]
Get:29 http://ftp.at.debian.org jessie-updates/non-free i386 
Packages/DiffIndex [736 B]

Hit http://security.debian.org jessie/updates/main Translation-en
Get:30 http://ftp.de.debian.org jessie-backports/main 
Translation-en/DiffIndex [27.8 kB]

Get:31 http://ftp.at.debian.org jessie-updates/contrib Translation-en [14 B]
Get:32 http://ftp.at.debian.org jessie-updates/main 
Translation-en/DiffIndex [2,704 B]
Get:33 http://ftp.at.debian.org jessie-updates/non-free 
Translation-en/DiffIndex [736 B]

Hit http://ftp.at.debian.org jessie/main Sources
Hit http://security.debian.org jessie/updates/non-free Translation-en
Get:34 http://ftp.de.debian.org jessie-backports/non-free 
Translation-en/DiffIndex [8,806 B]

Hit http://ftp.at.debian.org jessie/contrib Sources
Hit http://ftp.at.debian.org jessie/non-free Sources
Hit http://ftp.at.debian.org jessie/main amd64 Packages
Hit http://ftp.at.debian.org jessie/contrib amd64 Packages
Hit http://linux.dropbox.com wheezy/main i386 Packages
Hit http://ftp.at.debian.org jessie/non-free amd64 Packages
Hit http://ftp.at.debian.org jessie/main i386 Packages
Hit http://ftp.at.debian.org jessie/contrib i386 Packages
Hit 

Re: Problems with upgrade from Wheezy to Jessie

[Brian]

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

Re: Problems with upgrade from Wheezy to Jessie

[Brian]

On Sun 02 Oct 2016 at 20:02:39 +0100, Brian wrote:

> On Sun 02 Oct 2016 at 20:31:50 +0200, Christian Seiler wrote:
> 
> > On 10/02/2016 05:59 PM, Hans Kraus wrote:
> > > I upgraded my Debian server about a week ago from Wheezy to Jessie.
> > > After that the GUI stopped,
> > 
> > This is a bit vague, so a better explanation would be good. What
> > exactly do you mean "gui stopped"? Did that happen during the
> > update? Or at boot? Does the login screen show up? Does this
> > message show up after login?
> > 
> > > 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.
> > 
> > Could you transcribe the precise error message?
> 
> He has.

Apologies; my remark was made too hastily. Firstly, it was not the
complete message (as we have seen). Secondly, there can be two
differently worded messages depending on whether gnome-session or
gnome-shell is involved.

-- 
Brian.

Re: Problems with upgrade from Wheezy to Jessie

[Christian Seiler]

On 10/03/2016 06:50 PM, Hans Kraus wrote:
> 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.

Ok, this appears to be a GNOME-specific error message.

Could you restart the computer, try to log in, wait until that
message pops up, don't close the message, switch to another console
(Ctrl+Alt+F2) and run the following command as root?

journalctl -b1 -n40 _UID=1000

(Replace 1000 with your user id, you can look it via running id in
the console as your normal user; 1000 is the default for the first
user created by the Debian installer.)

See if there's anything in that output that might be relevant here.

> The /etc/apt/sources.list:
> ===
> root@robbe:~# cat /etc/apt/sources.list
> # deb http://ftp.at.debian.org/debian/ wheezy main
> 
> # deb http://backports.debian.org/debian-backports wheezy-backports non-free
> deb http://ftp.at.debian.org/debian/ jessie-backports main contrib non-free
> 
> deb http://ftp.at.debian.org/debian/ jessie main contrib non-free
> deb-src http://ftp.at.debian.org/debian/ jessie main contrib non-free
> 
> deb http://security.debian.org/ jessie/updates main contrib non-free
> deb-src http://security.debian.org/ jessie/updates main contrib non-free
> 
> # wheezy-updates, previously known as 'volatile'
> deb http://ftp.at.debian.org/debian/ jessie-updates main contrib non-free
> deb-src http://ftp.at.debian.org/debian/ jessie-updates main contrib non-free
> 
> deb http://ftp.de.debian.org/debian/ jessie-backports main contrib non-free
> ===

Side note: you have jessie-backports in there twice (first and last
uncommented line), but that's completely harmless. Otherwise, looks
fine.

Could you run

apt-get update
apt-get dist-upgrade

and see if it still wants to upgrade additional software?

Also, what kernel version are you running? (Find that out via the
command "uname -a".)

Regards,
Christian

Re: Problems with upgrade from Wheezy to Jessie

[Hans Kraus]

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.

The /etc/apt/sources.list:
===
root@robbe:~# cat /etc/apt/sources.list
# deb http://ftp.at.debian.org/debian/ wheezy main

# deb http://backports.debian.org/debian-backports wheezy-backports non-free
deb http://ftp.at.debian.org/debian/ jessie-backports main contrib non-free

deb http://ftp.at.debian.org/debian/ jessie main contrib non-free
deb-src http://ftp.at.debian.org/debian/ jessie main contrib non-free

deb http://security.debian.org/ jessie/updates main contrib non-free
deb-src http://security.debian.org/ jessie/updates main contrib non-free

# wheezy-updates, previously known as 'volatile'
deb http://ftp.at.debian.org/debian/ jessie-updates main contrib non-free
deb-src http://ftp.at.debian.org/debian/ jessie-updates main contrib 
non-free


deb http://ftp.de.debian.org/debian/ jessie-backports main contrib non-free
===
The parts "main contrib non-free" are on the same line; Thundebird
insists on line breaks ...

Kind regards,
Hans

Am 02.10.2016 um 20:31 schrieb Christian Seiler:

On 10/02/2016 05:59 PM, Hans Kraus wrote:

I upgraded my Debian server about a week ago from Wheezy to Jessie.
After that the GUI stopped,


This is a bit vague, so a better explanation would be good. What
exactly do you mean "gui stopped"? Did that happen during the
update? Or at boot? Does the login screen show up? Does this
message show up after login?


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.


Could you transcribe the precise error message?


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.


That means your packages are in a state that dpkg assumes to be
consistent. However, since you upgraded recently, and apparently
still have access to your shell, could you tell us what the
contents of /etc/apt/sources.list is?

Regards,
Christian

Re: Problems with upgrade from Wheezy to Jessie

[brian]

On Mon, 3 Oct 2016 00:55:37 -0400, Felix Miata wrote:

>brian composed on 2016-10-02 14:23 (UTC-0400):
>
>> On Sun, 2 Oct 2016 19:29:12 +0200, err...@free.fr wrote:
>
>>>what is your hadware?
>>>graphic card?
>>>and did you have any drivers or firmware for this? like firmware free or 
>>>non-free, or drivers for nvidia, or amd etc.
>
>> It's an eMachines desktop which was originally supplied with Windows
>> 7. I wiped Windows and loaded on Wheezy from a live DVD. The CPU is an
>> Athlon II x2 220 @ 800 MHz. The graphics (on the motherboard) is a
>> GeForce 6150 SE nForce 430 rev a2.
>
>This has been a problematic gfxchip for more than one user over the years. 
>Try adding this to the kernel cmdline:
>
>   nouveau.config=NvMSI=0
>
>I have a machine with the same gfxchip on its motherboard,
>https://us.msi.com/Motherboard/K9N6PGM2V.html
>but currently it doesn't have any Debian installed on it to check which if 
>any releases are helped by it. It does have openSUSE 13.1 (kernel 3.12, 
>server 1.14.3), 13.2 (kernel 3.16, server 1.16.1), 42.1 (kernel 4.1, server 
>1.17.2) and Tumbleweed (kernel 4.7.4, server 1.18.4) installed. All four 
>suffer random brief video corruption running X. Tumbleweed seems to have 
>almost eliminated the corruption that is excessive and unacceptable in the 
>others. IIRC, last Debian tried on it was Wheezy with Gnome or Mate or 
>Cinnamon, and too much trouble or impossible at that time to actually use X.
>
>Something else to try is ensuring xserver-xorg-video-modesetting is 
>installed, then purging xserver-xorg-video-nouveau and all traces of NVidia's 
>proprietary driver bits. The modesetting driver has been getting quite some 
>attention from the devs:
>http://www.phoronix.com/scan.php?page=news_item=Ubuntu-Debian-Abandon-Intel-DDX
>
>The original owner of this motherboard suffered to the extent he installed a 
>PCI gfxcard as a workaround when the motherboard was rather young. I got the 
>motherboard free when when he bought a new one that I installed after its 
>original RAM went bad.
>

Thanks Felix, I'll give it a try as soon as I can persuade my wife to
stay off the PC for a while, and report back. It will be a week or so
though, as I've got a couple of chapters of a book to deliver with a
deadline of next weekend. 

Brian. 

Re: Problems with upgrade from Wheezy to Jessie

[Felix Miata]

brian composed on 2016-10-02 14:23 (UTC-0400):


On Sun, 2 Oct 2016 19:29:12 +0200, err...@free.fr wrote:



what is your hadware?
graphic card?
and did you have any drivers or firmware for this? like firmware free or 
non-free, or drivers for nvidia, or amd etc.



It's an eMachines desktop which was originally supplied with Windows
7. I wiped Windows and loaded on Wheezy from a live DVD. The CPU is an
Athlon II x2 220 @ 800 MHz. The graphics (on the motherboard) is a
GeForce 6150 SE nForce 430 rev a2.


This has been a problematic gfxchip for more than one user over the years. 
Try adding this to the kernel cmdline:


nouveau.config=NvMSI=0

I have a machine with the same gfxchip on its motherboard,
https://us.msi.com/Motherboard/K9N6PGM2V.html
but currently it doesn't have any Debian installed on it to check which if 
any releases are helped by it. It does have openSUSE 13.1 (kernel 3.12, 
server 1.14.3), 13.2 (kernel 3.16, server 1.16.1), 42.1 (kernel 4.1, server 
1.17.2) and Tumbleweed (kernel 4.7.4, server 1.18.4) installed. All four 
suffer random brief video corruption running X. Tumbleweed seems to have 
almost eliminated the corruption that is excessive and unacceptable in the 
others. IIRC, last Debian tried on it was Wheezy with Gnome or Mate or 
Cinnamon, and too much trouble or impossible at that time to actually use X.


Something else to try is ensuring xserver-xorg-video-modesetting is 
installed, then purging xserver-xorg-video-nouveau and all traces of NVidia's 
proprietary driver bits. The modesetting driver has been getting quite some 
attention from the devs:

http://www.phoronix.com/scan.php?page=news_item=Ubuntu-Debian-Abandon-Intel-DDX

The original owner of this motherboard suffered to the extent he installed a 
PCI gfxcard as a workaround when the motherboard was rather young. I got the 
motherboard free when when he bought a new one that I installed after its 
original RAM went bad.



Looking at the output from a
dpkg -l there's no mention of any of the packages you list above. When
I installed Wheezy for my wife, I basically just accepted defaults, so
anything which has been loaded was loaded by the installer.



I can send you the full output from dpkg -l if you wish, just ask.

--
"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/

Re: Problems with upgrade from Wheezy to Jessie

[Patrick Bartek]

On Sun, 2 Oct 2016 17:59:48 +0200 Hans Kraus 
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

Re: Problems with upgrade from Wheezy to Jessie

[David Christensen]

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

Re: Problems with upgrade from Wheezy to Jessie

[Eike Lantzsch]

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 ...

Re: Problems with upgrade from Wheezy to Jessie

[Brian]

On Sun 02 Oct 2016 at 20:31:50 +0200, Christian Seiler wrote:

> On 10/02/2016 05:59 PM, Hans Kraus wrote:
> > I upgraded my Debian server about a week ago from Wheezy to Jessie.
> > After that the GUI stopped,
> 
> This is a bit vague, so a better explanation would be good. What
> exactly do you mean "gui stopped"? Did that happen during the
> update? Or at boot? Does the login screen show up? Does this
> message show up after login?
> 
> > 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.
> 
> Could you transcribe the precise error message?

He has.

Re: Problems with upgrade from Wheezy to Jessie

[Brian]

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.

  

Re: Problems with upgrade from Wheezy to Jessie

[Christian Seiler]

On 10/02/2016 05:59 PM, Hans Kraus wrote:
> I upgraded my Debian server about a week ago from Wheezy to Jessie.
> After that the GUI stopped,

This is a bit vague, so a better explanation would be good. What
exactly do you mean "gui stopped"? Did that happen during the
update? Or at boot? Does the login screen show up? Does this
message show up after login?

> 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.

Could you transcribe the precise error message?

> 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.

That means your packages are in a state that dpkg assumes to be
consistent. However, since you upgraded recently, and apparently
still have access to your shell, could you tell us what the
contents of /etc/apt/sources.list is?

Regards,
Christian

Re: Problems with upgrade from Wheezy to Jessie

[brian]

On Sun, 2 Oct 2016 19:29:12 +0200, you wrote:

>what is your hadware?
>graphic card?
>and did you have any drivers or firmware for this? like firmware free or 
>non-free, or drivers for nvidia, or amd etc.

It's an eMachines desktop which was originally supplied with Windows
7. I wiped Windows and loaded on Wheezy from a live DVD. The CPU is an
Athlon II x2 220 @ 800 MHz. The graphics (on the motherboard) is a
GeForce 6150 SE nForce 430 rev a2. Looking at the output from a 
dpkg -l there's no mention of any of the packages you list above. When
I installed Wheezy for my wife, I basically just accepted defaults, so
anything which has been loaded was loaded by the installer. 

I can send you the full output from dpkg -l if you wish, just ask. 


Brian. 

Re: Problems with upgrade from Wheezy to Jessie

[err404]

what is your hadware?
graphic card?
and did you have any drivers or firmware for this? like firmware free or 
non-free, or drivers for nvidia, or amd etc.



signature.asc
Description: OpenPGP digital signature

Re: Problems with upgrade from Wheezy to Jessie

[brian]

On Sun, 2 Oct 2016 17:59:48 +0200, 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.
>

Sorry, Hans, not a solution, just a "Me too", My wife has an eMachines
PC bought from Wal-Mart, and each time I have tried to move her from
Wheezy to Jessie, the upgrade reports no errors, you can log in and
the GUI is there, but the moment you touch the mouse the screen breaks
up into a whole series of short horizontal lines, and there is no way
out of it but to reboot. This is totally reproducible, and I've seen
exactly the same effect with a recent Linux Mint (not LMDE, the
Ubuntu-based version) live disk. 

If anyone had this problem and managed to sort it, I'd be very
grateful for the solution, because at the moment my wife's PC is stuck
at Wheezy, and cannot be upgraded. 

Thanks, 

Brian. 

Problems with upgrade from Wheezy to Jessie

[Hans Kraus]

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

Re: gdm3 doesn't work any more after the upgrade from Wheezy to Jessie 8.5

[Jean-Paul Bouchet]

Hello,

It seems that libpam-systemd is correctly installed

dpkg --status libpam-systemd
Package: libpam-systemd
Status: install ok installed
Priority: optional
Section: admin
Installed-Size: 304
Maintainer: Debian systemd Maintainers 


Architecture: amd64
Multi-Arch: same
Source: systemd
Version: 215-17+deb8u4
...

system.logind is running but may be blocked:

4 S root   1644  1  0  80   0 -  4964 -  sept.09 ?  
00:00:00 /lib/systemd/systemd-logind


systemctl -l status systemd-logind.service
● systemd-logind.service - Login Service
   Loaded: loaded (/lib/systemd/system/systemd-logind.service; static)
   Active: active (running) since ven. 2016-09-09 13:47:14 CEST; 2 days ago
 Docs: man:systemd-logind.service(8)
   man:logind.conf(5)
   http://www.freedesktop.org/wiki/Software/systemd/logind
http://www.freedesktop.org/wiki/Software/systemd/multiseat
 Main PID: 1644 (systemd-logind)
   Status: "Processing requests..."
   CGroup: /system.slice/systemd-logind.service
   └─1644 /lib/systemd/systemd-logind

sept. 09 13:47:14 pac-sm-gafl01 systemd-logind[1644]: New seat seat0.
sept. 09 13:47:14 pac-sm-gafl01 systemd-logind[1644]: Watching system 
buttons on /dev/input/event0 (Power Button)


loginctl shows no session:
loginctl
   SESSIONUID USER SEAT

0 sessions listed.
May be there has been an attempt of creating a session for Debian-gdm to 
launch on the console the greetings screen?


The last update of most files in ~Debian-gdm correspond with the last 
reboot of the server.

ll -a ~Debian-gdm/
total 36
drwxr-xr-x  6 Debian-gdm Debian-gdm 4096 sept. 12 09:42 .
drwxr-xr-x 70 root   root   4096 sept.  9 13:30 ..
drwx--  4 Debian-gdm Debian-gdm 4096 sept.  9 13:47 .cache
drwx--  6 Debian-gdm Debian-gdm 4096 sept.  9 13:47 .config
drwx--  3 Debian-gdm Debian-gdm 4096 sept.  9 13:47 .dbus
-rw-r--r--  1 Debian-gdm Debian-gdm 5251 sept.  9 13:47 
greeter-dconf-defaults

-rw---  1 Debian-gdm Debian-gdm 2084 sept. 12 09:42 .ICEauthority
drwx--  3 Debian-gdm Debian-gdm 4096 sept.  9 13:47 .local

Best regards,

Jean-Paul Bouchet

On 10/09/2016 10:09, Laurent Bigonville wrote:

Jean-Paul Bouchet wrote:
> [...]
> Check that logind is properly installed and pam_systemd is getting 
used at login.

> [...]

Could you check if you have libpam-systemd package installed? And also 
please check if "loginctl" shows sessions.


Cheers,

Laurent Bigonville

Re: gdm3 doesn't work any more after the upgrade from Wheezy to Jessie 8.5

[Laurent Bigonville]

Jean-Paul Bouchet wrote:
> [...]
> Check that logind is properly installed and pam_systemd is getting 
used at login.

> [...]

Could you check if you have libpam-systemd package installed? And also 
please check if "loginctl" shows sessions.


Cheers,

Laurent Bigonville

gdm3 doesn't work any more after the upgrade from Wheezy to Jessie 8.5

[Jean-Paul Bouchet]

Hello,

We used during 2 years Gnome and gdm3 on a server with Debian Wheezy to 
let users work from their Windows PC via Cygwin and xlaunch (xdmcp). It 
worked well till the upgrade to Jessie, for these Windows PC, as for the 
system console, a very simple terminal.


The migration has been done a few days ago after a last upgrade of 
Wheezy and a verification that our server was OK, including connection 
features. The dist-upgrade has not been perfect: here are the last lines 
of the process:

...
update-initramfs: Generating /boot/initrd.img-3.16.0-4-amd64
W: Possible missing firmware /lib/firmware/tigon/tg3_tso5.bin for module tg3
W: Possible missing firmware /lib/firmware/tigon/tg3_tso.bin for module tg3
W: Possible missing firmware /lib/firmware/tigon/tg3.bin for module tg3
Traitement des actions différées (« triggers ») pour sgml-base 
(1.26+nmu4) ...

Traitement des actions différées (« triggers ») pour menu (2.1.47) ...
Des erreurs ont été rencontrées pendant l'exécution :
 tex-common
E: Sub-process /usr/bin/dpkg returned an error code (1)

dpkg --audit gives me a list of 149 packages with the half-configurated 
status. Among them: libpam-ldap:amd64, libpam-mount, xorg, xserver-xorg.
I have launched manually 'dpk -configure' for all of them and 
reinstalled tex-common.


Now dpkg --audit returns nothing. I have not yet done apt-get autoremove 
to eliminate the packages the have become useless.


During the upgrade I have installed the new version of 
/etc/gdm3/daemon.conf, /etc/init.d/gdm3 and got [ ok ] Scheduling reload 
of GNOME Display Manager configuration: gdm3.


After the migration it has been possible during the 3 first days to open 
sometimes a gnome session but with many problems, several minutes to get 
the users' list, and again a long time, up to 10 minutes, to get the 
gnome window. Once displayed, the desk was fully functional, but the 
whole process, from the launch of cygwin was much too long and uncertain 
(we could also never get the connexion window with the list of users). 
It has never been possible to lock or close properly a session and to 
get again the connection window.


I have reinstalled some packages, including gdm3, searched similar 
situations on the web, verified the configuration in /etc/gdm3 or 
/etc/pam.d, compared with the files we had with Wheezy, rebooted the 
server, as carefully and cautiously as I could, but without the least 
improvement. On the contrary, we are now unable to get the connexion 
window.


Now, what we get, for the system console, as for the windows PCs with 
Cygwin, is what I supposed to be the splash window, a blue background 
screen with the time, the date and at the left bottom 'Debian 8' and no 
button.


systemctl -l status gdm.service
● gdm.service - GNOME Display Manager
   Loaded: loaded (/lib/systemd/system/gdm.service; enabled)
   Active: active (running) since ven. 2016-09-09 13:47:15 CEST; 6h ago
  Process: 1729 ExecStartPre=/usr/share/gdm/generate-config 
(code=exited, status=0/SUCCESS)
  Process: 1721 ExecStartPre=/bin/sh -c [ "$(cat 
/etc/X11/default-display-manager 2>/dev/null)" = "/usr/sbin/gdm3" ] 
(code=exited, status=0/SUCCESS)

 Main PID: 1801 (gdm3)
   CGroup: /system.slice/gdm.service
   ├─1801 /usr/sbin/gdm3
   ├─1814 /usr/bin/Xorg :0 -novtswitch -background none 
-noreset -verbose 3 -auth 
/var/run/gdm3/auth-for-Debian-gdm-wEWSh7/database -seat seat0 vt7

   ├─2065 gdm-session-worker [pam/gdm-launch-environment]
   ├─2194 /usr/bin/gnome-session --autostart 
/usr/share/gdm/greeter/autostart
   ├─2204 /usr/bin/dbus-launch --exit-with-session 
/usr/bin/gnome-session --autostart /usr/share/gdm/greeter/autostart
   ├─2243 /usr/bin/dbus-daemon --fork --print-pid 5 
--print-address 7 --session

   ├─2252 /usr/lib/at-spi2-core/at-spi-bus-launcher
   ├─2256 /usr/bin/dbus-daemon 
--config-file=/etc/at-spi2/accessibility.conf --nofork --print-address 3
   ├─2259 /usr/lib/at-spi2-core/at-spi2-registryd 
--use-gnome-session

   ├─2289 /usr/lib/gnome-settings-daemon/gnome-settings-daemon
   ├─2376 gnome-shell --mode=gdm
   ├─2455 /usr/bin/pulseaudio --start --log-target=syslog
   ├─2629 /usr/lib/dconf/dconf-service
   ├─3096 gdm-session-worker [pam/gdm-launch-environment]
   ├─3101 /usr/bin/gnome-session --autostart 
/usr/share/gdm/greeter/autostart
   ├─3104 /usr/bin/dbus-launch --exit-with-session 
/usr/bin/gnome-session --autostart /usr/share/gdm/greeter/autostart
   ├─3105 /usr/bin/dbus-daemon --fork --print-pid 5 
--print-address 7 --session

   ├─3108 /usr/lib/at-spi2-core/at-spi-bus-launcher
   ├─3112 /usr/bin/dbus-daemon 
--config-file=/etc/at-spi2/accessibility.conf --nofork --print-address 3
   ├─3115 /usr/lib/at-spi2-core/at-spi2-registryd 
--use-gnome-session

   ├─3138 /usr/lib/gnome-settings-daemon/gnome-settings-daemon
   ├─3148 

Re: Hung version upgrade from wheezy to jessie

[Norbert Kiszka]

Dnia 2016-06-30, czw o godzinie 12:04 +0100, Lisi Reisz pisze:
> I am in the process of upgrading a desktop form Wheezy to Jessie.  So
> far it has gone fine, but it is hung here:
> 
> Restarting services possibly affected by the upgrade:
>   openbsd-inetd: restarting...done.
>   exim4: restarting...done.
>   cups: restarting...
> 
> What do I do now?
> Lisi
> 

1. Check syslog and messages.
2. Try to run apt-get upgrade with strace.

upgrade from wheezy to jessie

[Gerard ROBIN]

Hello,
usually when the distribution changes, I update my system rather than 
reinstall everything. But for the transition from wheezy to jessie, 
I would like to know:

-1- Is it possible to go from wheezy to jessie, keeping sysvinit.

-2- if not, from what I read on the internet, go from sysvinit to
systemd is not without risk. What about it exactly?

(I would say that I am not concerned whether sytemd is better or 
worse than sysvinit. I'm not proficient enough ...)

tia.

-- 
Gerard
___
***
*  Created with mutt 1.5.21-6.2+deb7u2  *
*  under Debian Linux WHEEZY version 7.7  *
*  Registered Linux User #388243  *
*  https://Linuxcounter.net   *
***


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/2015010648.GA5213@mauritiusGA

Re: upgrade from wheezy to jessie

[Brian]

On Tue 06 Jan 2015 at 12:11:48 +0100, Gerard ROBIN wrote:

 usually when the distribution changes, I update my system rather than 
 reinstall everything. But for the transition from wheezy to jessie, 
 I would like to know:
 
 -1- Is it possible to go from wheezy to jessie, keeping sysvinit.

https://www.debian.org/releases/testing/i386/release-notes/ch-information.en.html#systemd-upgrade-default-init-system

An alternative for you is to install sysvinit-core after updating but
before upgrading.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/06012015120943.e12976c26...@desktop.copernicus.demon.co.uk

Re: upgrade from wheezy to jessie

[Tony van der Hoff]

On 06/01/15 13:12, Brian wrote:
 On Tue 06 Jan 2015 at 12:11:48 +0100, Gerard ROBIN wrote:
 
 usually when the distribution changes, I update my system rather than 
 reinstall everything. But for the transition from wheezy to jessie, 
 I would like to know:

 -1- Is it possible to go from wheezy to jessie, keeping sysvinit.
 
 https://www.debian.org/releases/testing/i386/release-notes/ch-information.en.html#systemd-upgrade-default-init-system
 
 An alternative for you is to install sysvinit-core after updating but
 before upgrading.
 


There's an awful lot of FUD spread on the internet (and, sadly, even on
this list), mostly engendered by bigotry against the systemd author(s).

My advice would be to go with the minimum effort upgrade, as you would
have done in the past. I've been running Jessie in a KVM client for
several months now, with zero problems.


-- 
Tony van der Hoff  | mailto:t...@vanderhoff.org
Ariège, France |


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/54abd4b7.4010...@vanderhoff.org

Re: upgrade from wheezy to jessie

[Gerard ROBIN]

On Tue, Jan 06, 2015 at 01:27:35PM +0100, Tony van der Hoff wrote:
 Date: Tue, 06 Jan 2015 13:27:35 +0100
 From: Tony van der Hoff t...@vanderhoff.org
 To: debian-user@lists.debian.org
 Subject: Re: upgrade from wheezy to jessie
 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101
  Thunderbird/24.2.0
 
 On 06/01/15 13:12, Brian wrote:
  On Tue 06 Jan 2015 at 12:11:48 +0100, Gerard ROBIN wrote:
  
  usually when the distribution changes, I update my system rather than 
  reinstall everything. But for the transition from wheezy to jessie, 
  I would like to know:
 
  -1- Is it possible to go from wheezy to jessie, keeping sysvinit.
  
  https://www.debian.org/releases/testing/i386/release-notes/ch-information.en.html#systemd-upgrade-default-init-system
  
  An alternative for you is to install sysvinit-core after updating but
  before upgrading.
  
 
 
 There's an awful lot of FUD spread on the internet (and, sadly, even on
 this list), mostly engendered by bigotry against the systemd author(s).
 
 My advice would be to go with the minimum effort upgrade, as you would
 have done in the past. I've been running Jessie in a KVM client for
 several months now, with zero problems.

I agree with you regarding jessie, I installed it on a USB drive and 
it works fine with systend, but but what concerns me is the transition 
from sysvinit to systemd on wheezy. If I understand what I read on the
web (in English ...) it may be that my machine will not boot if I do 
not do the job well.

-- 
Gerard
___
***
*  Created with mutt 1.5.21-6.2+deb7u2  *
*  under Debian Linux WHEEZY version 7.7  *
*  Registered Linux User #388243  *
*  https://Linuxcounter.net   *
***


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150106124810.GA9947@mauritiusGA

Re: upgrade from wheezy to jessie

[Tony van der Hoff]

On 06/01/15 13:48, Gerard ROBIN wrote:
 On Tue, Jan 06, 2015 at 01:27:35PM +0100, Tony van der Hoff wrote:
 Date: Tue, 06 Jan 2015 13:27:35 +0100
 From: Tony van der Hoff t...@vanderhoff.org
 To: debian-user@lists.debian.org
 Subject: Re: upgrade from wheezy to jessie
 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101
  Thunderbird/24.2.0

 On 06/01/15 13:12, Brian wrote:
 On Tue 06 Jan 2015 at 12:11:48 +0100, Gerard ROBIN wrote:

 usually when the distribution changes, I update my system rather than 
 reinstall everything. But for the transition from wheezy to jessie, 
 I would like to know:

 -1- Is it possible to go from wheezy to jessie, keeping sysvinit.

 https://www.debian.org/releases/testing/i386/release-notes/ch-information.en.html#systemd-upgrade-default-init-system

 An alternative for you is to install sysvinit-core after updating but
 before upgrading.



 There's an awful lot of FUD spread on the internet (and, sadly, even on
 this list), mostly engendered by bigotry against the systemd author(s).

 My advice would be to go with the minimum effort upgrade, as you would
 have done in the past. I've been running Jessie in a KVM client for
 several months now, with zero problems.
 
 I agree with you regarding jessie, I installed it on a USB drive and 
 it works fine with systend, but but what concerns me is the transition 
 from sysvinit to systemd on wheezy. If I understand what I read on the
 web (in English ...) it may be that my machine will not boot if I do 
 not do the job well.
 
I've not heard that, except maybe in very old reports.
I think the installer has now reached a stage of maturity to avoid such
pit-falls, and will, presumably, mature more until the release. I'd then
be inclined to wait for a month or two before upgrading, to allow it to
gain even more maturity. I would expect all to go smoothly.

-- 
Tony van der Hoff  | mailto:t...@vanderhoff.org
Ariège, France |


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/54abe3d0.6080...@vanderhoff.org

Re: upgrade from wheezy to jessie

[Eduardo M KALINOWSKI]

On Ter, 06 Jan 2015, Joe wrote:

The main issue is that anything local mounted in /etc/fstab (even
removable drives) will be treated as essential, and if they are not
there, boot will fail. The answer is either to remove any such drives
from fstab, as the kernel automounting should be good enough now to do
the job consistently, or to mark them as not being required for boot.


This is already noted in the release notes.

--
Eduardo M KALINOWSKI
edua...@kalinowski.com.br



--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: 
https://lists.debian.org/20150106134243.horde.viaxbcqbhjp9llrc26vg...@mail.kalinowski.com.br

Re: upgrade from wheezy to jessie

[Joe]

On Tue, 06 Jan 2015 13:42:43 +
Eduardo M KALINOWSKI edua...@kalinowski.com.br wrote:

 On Ter, 06 Jan 2015, Joe wrote:
  The main issue is that anything local mounted in /etc/fstab (even
  removable drives) will be treated as essential, and if they are not
  there, boot will fail. The answer is either to remove any such
  drives from fstab, as the kernel automounting should be good enough
  now to do the job consistently, or to mark them as not being
  required for boot.
 
 This is already noted in the release notes.
 

Yes, but I believe it is likely to be the main reason for a possible
lack of booting, about which the OP was concerned. I was making the
point that is a very simple thing to avoid.

-- 
Joe


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150106135714.29372...@jresid.jretrading.com

Re: upgrade from wheezy to jessie

[Brian]

On Tue 06 Jan 2015 at 14:32:00 +0100, Tony van der Hoff wrote:

 On 06/01/15 13:48, Gerard ROBIN wrote:
  
  I agree with you regarding jessie, I installed it on a USB drive and 
  it works fine with systend, but but what concerns me is the transition 
  from sysvinit to systemd on wheezy. If I understand what I read on the
  web (in English ...) it may be that my machine will not boot if I do 
  not do the job well.
  
 I've not heard that, except maybe in very old reports.
 I think the installer has now reached a stage of maturity to avoid such
 pit-falls, and will, presumably, mature more until the release. I'd then
 be inclined to wait for a month or two before upgrading, to allow it to
 gain even more maturity. I would expect all to go smoothly.

New installations from d-i are, of course, different from upgrading from
Wheezy and testing of the betas and release candidates is very important.
Tommorrow should see a new version of the installer released. Reports of
success (or otherwise) made with the installation-report package are
more than welcome.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150106140100.gc3...@copernicus.demon.co.uk

Re: upgrade from wheezy to jessie

[Joe]

On Tue, 6 Jan 2015 13:48:10 +0100
Gerard ROBIN g.rob...@free.fr wrote:


 
 I agree with you regarding jessie, I installed it on a USB drive and 
 it works fine with systend, but but what concerns me is the
 transition from sysvinit to systemd on wheezy. If I understand what I
 read on the web (in English ...) it may be that my machine will not
 boot if I do not do the job well.
 
The main issue is that anything local mounted in /etc/fstab (even
removable drives) will be treated as essential, and if they are not
there, boot will fail. The answer is either to remove any such drives
from fstab, as the kernel automounting should be good enough now to do
the job consistently, or to mark them as not being required for boot.
The fstab syntax for systemd has been extended quite a bit.

But yes, I moved three sid systems from sysvinit to systemd, the two
simpler systems were fine, the much larger main workstation
installation had sufficient minor problems that I felt it better to
reinstall. Not something you want to do with a server.

-- 
Joe


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150106133548.42c37...@jresid.jretrading.com

Re: upgrade from wheezy to jessie

[Brian]

On Tue 06 Jan 2015 at 13:48:10 +0100, Gerard ROBIN wrote:

 On Tue, Jan 06, 2015 at 01:27:35PM +0100, Tony van der Hoff wrote:
  
  My advice would be to go with the minimum effort upgrade, as you would
  have done in the past. I've been running Jessie in a KVM client for
  several months now, with zero problems.
 
 I agree with you regarding jessie, I installed it on a USB drive and 
 it works fine with systend, but but what concerns me is the transition 
 from sysvinit to systemd on wheezy. If I understand what I read on the
 web (in English ...) it may be that my machine will not boot if I do 
 not do the job well.

The sysvinit package is on a Wheezy system. It will be upgraded to

  https://packages.debian.org/jessie/sysvinit

   This package depends on init, which is an essential package
   that pulls in the default init system. Starting with jessie,
   this will be systemd on Linux. It facilitates a smooth
   transition and provides a fallback SysV init binary which can be
   used to boot the system via the init=/lib/sysvinit/init kernel
   command line parameter in case the system fails to start after
   the switch to systemd.

The fallback SysV init binary has been thoughtfully provided to cater
for the situation you are concerned about.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150106133721.gb3...@copernicus.demon.co.uk

Re: upgrade from wheezy to jessie

[Jerry Stuckle]

On 1/6/2015 7:27 AM, Tony van der Hoff wrote:
 On 06/01/15 13:12, Brian wrote:
 On Tue 06 Jan 2015 at 12:11:48 +0100, Gerard ROBIN wrote:

 usually when the distribution changes, I update my system rather than 
 reinstall everything. But for the transition from wheezy to jessie, 
 I would like to know:

 -1- Is it possible to go from wheezy to jessie, keeping sysvinit.

 https://www.debian.org/releases/testing/i386/release-notes/ch-information.en.html#systemd-upgrade-default-init-system

 An alternative for you is to install sysvinit-core after updating but
 before upgrading.


 
 There's an awful lot of FUD spread on the internet (and, sadly, even on
 this list), mostly engendered by bigotry against the systemd author(s).
 
 My advice would be to go with the minimum effort upgrade, as you would
 have done in the past. I've been running Jessie in a KVM client for
 several months now, with zero problems.
 
 

There are also a lot of technical reasons why knowledgeable people  who
have no opinion about the systemd author(s) don't like systemd

There are also some people who discard any comments against systemd as
FUD, mostly engendered by bigotry against the systemd author(s).
Including on this list, sadly.

Jerry


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/54abf2bc.5070...@gmail.com

Re: upgrade from wheezy to jessie

[Thom Miller]

On 01/06/2015 06:57 AM, Joe wrote:
 On Tue, 06 Jan 2015 13:42:43 +
 Eduardo M KALINOWSKI edua...@kalinowski.com.br wrote:
 
 On Ter, 06 Jan 2015, Joe wrote:
 The main issue is that anything local mounted in /etc/fstab (even
 removable drives) will be treated as essential, and if they are not
 there, boot will fail. The answer is either to remove any such
 drives from fstab, as the kernel automounting should be good enough
 now to do the job consistently, or to mark them as not being
 required for boot.

 This is already noted in the release notes.

 
 Yes, but I believe it is likely to be the main reason for a possible
 lack of booting, about which the OP was concerned. I was making the
 point that is a very simple thing to avoid.
 

I very recently updated two systems from wheezy to jessie. Both are
running fine (I'm using one right now), but I had exactly the problem
above on one system.

I had an fstab entry that halted booting. Removed that line and it
booted fine.

The only other issue I've had since the upgrade is a wireless driver
(which I didn't want) was failing to load and my logs filled up 89G of
space telling me over and over in messages, syslog and kern.log until
the root partition was full.

-Thom


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/54ac0450.5070...@cagroups.com

Re: upgrade from wheezy to jessie

[Gerard ROBIN]

On Tue, Jan 06, 2015 at 01:35:48PM +, Joe wrote:
 Date: Tue, 6 Jan 2015 13:35:48 +
 From: Joe j...@jretrading.com
 To: debian-user@lists.debian.org
 Subject: Re: upgrade from wheezy to jessie
 X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.25; x86_64-pc-linux-gnu)
 
 On Tue, 6 Jan 2015 13:48:10 +0100
 Gerard ROBIN g.rob...@free.fr wrote:
 
 
  
  I agree with you regarding jessie, I installed it on a USB drive and 
  it works fine with systend, but but what concerns me is the
  transition from sysvinit to systemd on wheezy. If I understand what I
  read on the web (in English ...) it may be that my machine will not
  boot if I do not do the job well.
  
 The main issue is that anything local mounted in /etc/fstab (even
 removable drives) will be treated as essential, and if they are not
 there, boot will fail. The answer is either to remove any such drives
 from fstab, as the kernel automounting should be good enough now to do
 the job consistently, or to mark them as not being required for boot.
 The fstab syntax for systemd has been extended quite a bit.
 
 But yes, I moved three sid systems from sysvinit to systemd, the two
 simpler systems were fine, the much larger main workstation
 installation had sufficient minor problems that I felt it better to
 reinstall. Not something you want to do with a server.

Ok, I got my feet wet : 

~# apt-get install  systemd-sysv

--8--

You are about to do something potentially harmful.
To continue type in the phrase 'Yes, do as I say!'

~# Yes, do as I say!

~# apt-get install sysv-rc-conf

and after that wheezy has booted like a charm. Luke


Thanks to everyone who replied.

-- 
Gerard
___
***
*  Created with mutt 1.5.21-6.2+deb7u2  *
*  under Debian Linux WHEEZY version 7.7  *
*  Registered Linux User #388243  *
*  https://Linuxcounter.net   *
***


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150106164144.GA5237@mauritiusGA

Aw: Re: Re: GUI fails after upgrade from wheezy to jessie

[Hans Heider]

Hi Hans,



I purged whole X, kdm, gdm3, xfdestop4, lxde and finally also twm. After reinstalling lxde GUI login now works. However, auto-adjusting the resoltion with an external monitor does not work. Using lxrandr helps, therefore I consider this problem as fixed.



The only three FN+ XX keys working are the ones to decrease / increase screen brightness and to put the pc into sleep mode. By using xev I noticed that the other keys do not generate any event. The scripts which this keys should execute are in /usr/share/acpi-support/eeepc-acpi-scripts and at least vga-toogle.sh and volume.sh work perfectly fine when executed manually. Therefore, I assume that they are not executed when the keys are pressed.

Additionally, I found out that the eeepc-laptop kernel module (referenced here https://wiki.debian.org/DebianEeePC/HowTo/Configure#Power_management_.26_hotkeys) is not loaded and I cannot load it manually.

# modprobe eeepc-laptop gives: modprobe: ERROR: could not insert eeepc_laptop: No such device


# uname -a gives: Linux eeepc 3.14-2-686-pae #1 SMP Debian 3.14.15-2 (2014-08-09) i686 GNU/Linux



I checked that the module exists.



Is the module loaded on your system?



Yours,



Hans


Gesendet:Freitag, 05. September 2014 um 08:57 Uhr
Von:Hans hans.ullr...@loop.de
An:debian-user@lists.debian.org
Betreff:Re: Aw: Re: GUI fails after upgrade from wheezy to jessie

Am Freitag, 5. September 2014, 10:15:36 schrieb Hans Heider:
 Hi Hans,

 thank you for sharing your ideas.

 I used apt-get dist-upgrade for my upgrade from wheezy to jessie. Kernel
 command line in grub does not have any vga= options.
 I removed gdm3 and x11-session from /etc/init.rd/ but somehow Xorg still
 got started. Cannot image how/why?

Hmm, that should not be. Check, if there is any other loginmanager active in
init.d. Search at kdm, gdm and lightdm. Just remove all of them. Maybe you
might want to deinstall all of them. I suggest, to purge them, too. (either
aptitude purge packagename or apt-get --purge packagename)

Apropos purging: the comman aptitude purge ~c purges all configurations of all
deinstalled packages and libs. So these do not interfere.

Can you see the output, when you do startx as root from the prompt? There
should appear some messages.


 Regarding the first problem:
 - As lxde was already installed, I additionally installed xfce. However,
 this did not change the situation at all. - Afterwards, I installed kdm as
 a replacement for gdm3 (not uninstalled) - problem partly solved!

Yes, kdm is working also fine. But for testing purposes move it away from
/etc/init.d/, just like gdm.
 No more
 kernel faults and window manager now shows up soon after X is started.

 However, two less critical problems persist: * screen resolution is strange
 (not using whole screen) and I cannot select usage of different monitors
 via EeePC FN + XX keys any more.

Hmm, this should work. Did you install the package eeepc-acpi-scripts? If yes,
look at the configuration of it. Note: FN + Space, FN + F6 do not work after
reboot. They are working again, when you did a dpkg-reconfigure eeepc-acpi-
scripts - until next reboot. I sent a bugreport, but still no one cared.
 All this worked fine in wheezy. *
 nm-applet does not work properly, message like Policy Kit authorization
 failed: challenge needed for org.freedesktop.ModemManager1.Device.Control
 are diplayed. I will try to use information from
Network-manager is not woorking very well on an EEEPC. I suggest to change to
wicd. If you want to use a GSM-card, try umtsmon. It is an old qt4-package,
but working very very well. I am no coder, but I tried to change it to use
qt5, but still got no success. For this I am not experienced enough.

 https://wiki.archlinux.org/index.php/display_manager and
 https://bbs.archlinux.org/viewtopic.php?id=180025 to fix it as soon as I
 have time for it. To help others with similar problem I will report the
 result.
 Does the FN + XX-key combination work for you?

 Regarding second problem:
 - still exists, could not find a workaround

 Regarding third problem:
 - after running apt-get remove lilypond lilypond-doc lilypond-doc-html -
 problem solved!
 Yours,

Try also apt-get autoremove, and if you know, what you are doing, you can also
try orphaner. This will remove a lot of crap from your system. If after that
something is missing, just reinstall it.


 Hans


Good luck!

Hans


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/4357686.4IuIZ0RsLT@protheus7






-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/trinity-93dc0a4a-c8e0-40be-8b1e-a29e89cdb749-1410016691346@3capp-gmx-bs51

Re: Aw: Re: Re: GUI fails after upgrade from wheezy to jessie

[Hans]

Am Samstag, 6. September 2014, 17:18:11 schrieb Hans Heider:
 Hi Hans,
Hi Hans
  
 I purged whole X, kdm, gdm3, xfdestop4, lxde and finally also twm. After
 reinstalling lxde GUI login now works. However, auto-adjusting the
 resoltion with an external monitor does not work. Using lxrandr helps,
 therefore I consider this problem as fixed. 

That sounds good.

 The only three FN+ XX keys working are the ones to decrease / increase
 screen brightness and to put the pc into sleep mode. By using 'xev' I
 noticed that the other keys do not generate any event. The scripts which
 this keys should execute are in /usr/share/acpi-support/eeepc-acpi-scripts
 and at least vga-toogle.sh and volume.sh work perfectly fine when executed
 manually. Therefore, I assume that they are not executed when the keys are
 pressed. Additionally, I found out that the eeepc-laptop kernel module
 (referenced here

Yes, same here. Not all FN+* keys are working any more. I already sent a bug 
report, but as there are only very few people with this hardware, still no one 
cared about. And I am no coder, so I cannot fix it myself.

I hope, some day it will be fixed.
 
 https://wiki.debian.org/DebianEeePC/HowTo/Configure#Power_management_.26_ho
 tkeys) is not loaded and I cannot load it manually. # modprobe
 eeepc-laptop   gives: modprobe: ERROR: could not insert
 'eeepc_laptop': No such device # uname -a
 gives: Linux eeepc 3.14-2-686-pae #1 SMP Debian 3.14.15-2 (2014-08-09) i686
 GNU/Linux 
 I checked that the module exists.
  
 Is the module loaded on your system?

Yes, they are loaded here. Please pay attention, that the module acpi-wmi is 
not loaded. It depends on your hardare! Newer hardware uses acpi-wmi, the 
older ones use eeepc-laptop. 

To inhibit acpi-wmi to be loaded, add the command acpi_osi=Linux to your 
grub commandline. (I am using grub-legacy, which is mor easy to configure than 
grub2. I am using debian now for many years and so I am still at grub-legacy. 
Sorry for that.)

Then, after boot, check if the module is loaded with 

lsmod | grep eeepc

You can also check, which modules are loaded by lsmod | grep acpi


  
 Yours,
  
 Hans

Have a nice weekend.

Best 

Hans


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/3113856.fT0NBHfWjR@protheus7

Aw: Re: GUI fails after upgrade from wheezy to jessie

[Hans Heider]

Hi Hans,



thank you for sharing your ideas.



I used apt-get dist-upgrade for my upgrade from wheezy to jessie. Kernel command line in grub does not have any vga= options.



I removed gdm3 and x11-session from /etc/init.rd/ but somehow Xorg still got started. Cannot image how/why?



Regarding the first problem:

- As lxde was already installed, I additionally installed xfce. However, this did not change the situation at all.

- Afterwards, I installed kdm as a replacement for gdm3 (not uninstalled) - problem partly solved! No more kernel faults and window manager now shows up soon after X is started. However, two less critical problems persist:

* screen resolution is strange (not using whole screen) and I cannot select usage of different monitors via EeePC FN + XX keys any more. All this worked fine in wheezy.

* nm-applet does not work properly, message like Policy Kit authorization failed: challenge needed for org.freedesktop.ModemManager1.Device.Control are diplayed. I will try to use information from https://wiki.archlinux.org/index.php/display_manager and https://bbs.archlinux.org/viewtopic.php?id=180025 to fix it as soon as I have time for it. To help others with similar problem I will report the result.



Does the FN + XX-key combination work for you?



Regarding second problem:

- still exists, could not find a workaround



Regarding third problem:

- after running apt-get remove lilypond lilypond-doc lilypond-doc-html - problem solved!



Yours,



Hans





Gesendet:Donnerstag, 04. September 2014 um 12:48 Uhr


Von:Hans hans.ullr...@loop.de
An:debian-user@lists.debian.org
Betreff:Re: GUI fails after upgrade from wheezy to jessie

Am Donnerstag, 4. September 2014, 10:57:47 schrieb Hans Heider:
 Hi all,

 I just upgraded from Debian stable (wheezy) to testing (jessie).
 Unfortunately, I encountered three different problems which are (in
 decending severity): 1. The GUI became totally unusable. After booting X is
 started up but in 99% of all tries it just leaves me with a blank screen.
 Only once the gdm3 interface came up very slowly and I was able to log in,
 however the hole system froze after about one minute and I had to perform a
 hard reset. With removing the quiet from kernel command line I just see
 that X is started (displays OK) - no further errors reported. I managed
 to obtain the kernal fault trace attached to this email. This problem
 occurs every time and I have no clue how to fix it. Tried to add
 nomodeset to the kernel command line but no result. Additionally, the
 kernel fault seems to occur multiple times in a row. I can force the kernel
 fault to occure with # killall Xorg gdm3 gdm-session-manager which seems
 to restart the whole gui (however I do not know how restarts this
 services). After this command I am automatically taken to terminal 7 with a
 running GUI / blank screen. 2. During boot the system hangs for quite
 some time with displaying the message A start job is running for
 dev-disk-byx2duuid-29d73912x2d52cax2d4026x2d8a14x2d72c08e242b0b.device
 . I found this https://forum.manjaro.org/index.php?topic=5538.0 and the
 system continues to boot, but it is still something I would like to fix.
 Any ideas? 3. Do to Bug #758787
 (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758787) my apt became
 useless. Does anybody know of a workaround?
 My system is a laptop with Intel Atom processor and an onboard Intel
 Graphics chip. Kernel version is 3.14-2-686-pae.
 Dmesg also just gives me the report found in attachment. I could not find
 any helpful information in /var/log/Xorg.0.log or /var/log/Xorg.1.log
 neither in /var/log/syslog. Google gives no solution either...
 Any help is greatly appreciated.

 Yours,

 Hans


Hi Hans,

I am running Jessie on an netbook EEEPC 1005HAG, which is an atom processor
and an Intel 945 graphics chip. It is running very well.

So let me try to help.

First, check out, that during upgrade no needed packages were uninstalled.
This mostly when using aptitude. For upgrade I still prefer apt-get dist-
upgrade. Later you can finetune with aptitude.

Second, do not use any vga= option in grub. For this hardware, I got best
results in letting the kernel decide, which resolution to use. Otherwise you
might get in trouble with X.

Third, just for trying, install some other window manager, I suggest LXDE. It
is fast and stable.

Fourth, for testing purposes, remove /etc/init.d/gdm and /etc/init.d/kdm
somewhere else. Doing so, X is not started automatically. But you can start X
with the commad startx in the commandline as root. So you can see, if errors
appear, and what really happens. If everything is running fine later, you can
just rem,ove the files back.

Fifth, again, just for testing purposes, you can install grub-legacy. On this
older system I am quite happy with it. However, some people will now say, it
does not have any effects on X - and they may be right.

I hope, this will help a little, to find the reason for the problem.

Good

Re: Aw: Re: GUI fails after upgrade from wheezy to jessie

[Hans]

Am Freitag, 5. September 2014, 10:15:36 schrieb Hans Heider:
 Hi Hans,
  
 thank you for sharing your ideas.
  
 I used apt-get dist-upgrade for my upgrade from wheezy to jessie. Kernel
 command line in grub does not have any vga= options. 
 I removed gdm3 and x11-session from /etc/init.rd/ but somehow Xorg still
 got started. Cannot image how/why? 

Hmm, that should not be. Check, if there is any other loginmanager active in 
init.d. Search at kdm, gdm and lightdm. Just remove all of them. Maybe you 
might want to deinstall all of them. I suggest, to purge them, too. (either 
aptitude purge packagename or apt-get --purge packagename)

Apropos purging: the comman aptitude purge ~c purges all configurations of all 
deinstalled packages and libs. So these do not interfere.

Can you see the output, when you do startx as root from the prompt? There 
should appear some messages.


 Regarding the first problem:
 - As lxde was already installed, I additionally installed xfce. However,
 this did not change the situation at all. - Afterwards, I installed kdm as
 a replacement for gdm3 (not uninstalled) - problem partly solved! 

Yes, kdm is working also fine. But for testing purposes move it away from 
/etc/init.d/, just like gdm.
 No more
 kernel faults and window manager now shows up soon after X is started.

 However, two less critical problems persist: * screen resolution is strange
 (not using whole screen) and I cannot select usage of different monitors
 via EeePC FN + XX keys any more. 

Hmm, this should work. Did you install the package eeepc-acpi-scripts? If yes, 
look at the configuration of it. Note: FN + Space, FN + F6 do not work after 
reboot. They are working again, when you did a dpkg-reconfigure eeepc-acpi-
scripts - until next reboot. I sent a bugreport, but still no one cared. 
 All this worked fine in wheezy. *
 nm-applet does not work properly, message like Policy Kit authorization
 failed: challenge needed for org.freedesktop.ModemManager1.Device.Control
 are diplayed. I will try to use information from
Network-manager is not woorking very well on an EEEPC. I suggest to change to 
wicd. If you want to use a GSM-card, try umtsmon. It is an old qt4-package, 
but working very very well. I am no coder, but I tried to change it to use 
qt5, but still got no success. For this I am not experienced enough.

 https://wiki.archlinux.org/index.php/display_manager and
 https://bbs.archlinux.org/viewtopic.php?id=180025 to fix it as soon as I
 have time for it. To help others with similar problem I will report the
 result. 
 Does the FN + XX-key combination work for you?
  
 Regarding second problem:
 - still exists, could not find a workaround
  
 Regarding third problem:
 - after running apt-get remove lilypond lilypond-doc lilypond-doc-html -
 problem solved! 
 Yours,

Try also apt-get autoremove, and if you know, what you are doing, you can also 
try orphaner. This will remove a lot of crap from your system. If after that 
something is missing, just reinstall it.

  
 Hans
  

Good luck!

Hans


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/4357686.4IuIZ0RsLT@protheus7

GUI fails after upgrade from wheezy to jessie

[Hans Heider]

Hi all,



I just upgraded from Debian stable (wheezy) to testing (jessie). Unfortunately, I encountered three different problems which are (in decending severity):

1. The GUI became totally unusable. After booting X is started up but in 99% of all tries it just leaves me with a blank screen. Only once the gdm3 interface came up very slowly and I was able to log in, however the hole system froze after about one minute and I had to perform a hard reset. With removing the quiet from kernel command line I just see that X is started (displays OK) - no further errors reported. I managed to obtain the kernal fault trace attached to this email. This problem occurs every time and I have no clue how to fix it. Tried to add nomodeset to the kernel command line but no result. Additionally, the kernel fault seems to occur multiple times in a row.

I can force the kernel fault to occure with # killall Xorg gdm3 gdm-session-manager which seems to restart the whole gui (however I do not know how restarts this services). After this command I am automatically taken to terminal 7 with a running GUI / blank screen.

2. During boot the system hangs for quite some time with displaying the message A start job is running for dev-disk-byx2duuid-29d73912x2d52cax2d4026x2d8a14x2d72c08e242b0b.device. I found this https://forum.manjaro.org/index.php?topic=5538.0 and the system continues to boot, but it is still something I would like to fix. Any ideas?

3. Do to Bug #758787 (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758787) my apt became useless. Does anybody know of a workaround?



My system is a laptop with Intel Atom processor and an onboard Intel Graphics chip. Kernel version is 3.14-2-686-pae.



Dmesg also just gives me the report found in attachment. I could not find any helpful information in /var/log/Xorg.0.log or /var/log/Xorg.1.log neither in /var/log/syslog. Google gives no solution either...



Any help is greatly appreciated.



Yours,



Hans


Kernel failure message 1:
[ cut here ]
WARNING: CPU: 1 PID: 1094 at 
/build/linux-neEfbl/linux-3.14.15/drivers/gpu/drm/i915/intel_display.c:9541 
check_crtc_state+0x6a8/0xdb0 [i915]()
pipe state doesn't match!
Modules linked in: nls_utf8 isofs cpufreq_powersave cpufreq_conservative 
cpufreq_userspace cpufreq_stats binfmt_misc nfsd auth_rpcgss oid_registry 
nfs_acl nfs lockd fscache sunrpc iptable_filter xt_owner ip_tables x_tables 
hid_generic joydev option huawei_cdc_ncm cdc_wdm arc4 uvcvideo 
videobuf2_vmalloc ath9k usb_wwan ath9k_common ath9k_hw cdc_ncm videobuf2_memops 
videobuf2_core usbhid usbserial hid sr_mod usbnet cdrom mii ath videodev media 
mac80211 snd_hda_codec_realtek psmouse snd_hda_codec_generic cfg80211 iTCO_wdt 
eeepc_wmi iTCO_vendor_support asus_wmi coretemp evdev serio_raw snd_hda_intel 
snd_hda_codec snd_hwdep i915 lpc_ich snd_pcm_oss mfd_core snd_mixer_oss snd_pcm 
snd_timer snd drm_kms_helper soundcore rng_core sparse_keymap rfkill wmi drm 
i2c_algo_bit i2c_core shpchp video battery ac button acpi_cpufreq processor 
loop fuse ecryptfs parport_pc ppdev lp parport autofs4 ext4 crc16 mbcache jbd2 
usb_storage sg sd_mod crc_t10dif crct10dif_generic crct10dif_common ahci 
libahci uhci_hcd ehci_pci ehci_hcd libata scsi_mod thermal atl1c usbcore 
usb_common thermal_sys
CPU: 1 PID: 1094 Comm: Xorg Tainted: GW3.14-2-686-pae #1 Debian 
3.14.15-2
Hardware name: ASUSTeK Computer INC. 1005HA/1005HA, BIOS 160104/18/2011
 0009 c142f384 e39a1ab0 c10506ae f878b8e8 e39a1ac8 0446 f8782450
 2545 f87298d8 f87298d8 f3e5 f3e50648  f41f09cc c1050703
 0009 e39a1ab0 f878b8e8 e39a1ac8 f87298d8 f8782450 2545 f878b8e8
Call Trace:
 [c142f384] ? dump_stack+0x3e/0x4e
 [c10506ae] ? warn_slowpath_common+0x7e/0xa0
 [f87298d8] ? check_crtc_state+0x6a8/0xdb0 [i915]
 [f87298d8] ? check_crtc_state+0x6a8/0xdb0 [i915]
 [c1050703] ? warn_slowpath_fmt+0x33/0x40
 [f87298d8] ? check_crtc_state+0x6a8/0xdb0 [i915]
 [f8735fbc] ? intel_modeset_check_state+0x27c/0x760 [i915]
 [f873652a] ? intel_set_mode+0x2a/0x40 [i915]
 [f8736d46] ? intel_crtc_set_config+0x726/0x900 [i915]
 [f85233d3] ? drm_mode_set_config_internal+0x43/0xb0 [drm]
 [f8525cbe] ? drm_mode_setcrtc+0xde/0x590 [drm]
 [f8525be0] ? drm_mode_setplane+0x3e0/0x3e0 [drm]
 [f8519486] ? drm_ioctl+0x3a6/0x420 [drm]
 [f8525be0] ? drm_mode_setplane+0x3e0/0x3e0 [drm]
 [f85190e0] ? drm_free_buffer+0x30/0x30 [drm]
 [c115e5c7] ? do_vfs_ioctl+0x307/0x500
 [c1053743] ? do_setitimer+0x1b3/0x1f0
 [c1053893] ? SyS_setitimer+0xb3/0xf0
 [c115fb30] ? SyS_select+0xa0/0xc0
 [c115e818] ? SyS_ioctl+0x58/0x80
 [c143ab46] ? sysenter_do_call+0x12/0x12
---[ end trace 0fe34f1e9f06a4e7 ]---


Kernel failure message 2:
[ cut here ]
WARNING: CPU: 1 PID: 1094 at 
/build/linux-neEfbl/linux-3.14.15/drivers/gpu/drm/i915/intel_display.c:9541 
check_crtc_state+0x6a8/0xdb0 [i915]()
pipe state doesn't match!
Modules linked in: cpufreq_powersave cpufreq_conservative 

Re: GUI fails after upgrade from wheezy to jessie

[Hans]

Am Donnerstag, 4. September 2014, 10:57:47 schrieb Hans Heider:
 Hi all,
  
 I just upgraded from Debian stable (wheezy) to testing (jessie).
 Unfortunately, I encountered three different problems which are (in
 decending severity): 1. The GUI became totally unusable. After booting X is
 started up but in 99% of all tries it just leaves me with a blank screen.
 Only once the gdm3 interface came up very slowly and I was able to log in,
 however the hole system froze after about one minute and I had to perform a
 hard reset. With removing the quiet from kernel command line I just see
 that X is started (displays OK) - no further errors reported. I managed
 to obtain the kernal fault trace attached to this email. This problem
 occurs every time and I have no clue how to fix it. Tried to add
 nomodeset to the kernel command line but no result. Additionally, the
 kernel fault seems to occur multiple times in a row. I can force the kernel
 fault to occure with # killall Xorg gdm3 gdm-session-manager   which seems
 to restart the whole gui (however I do not know how restarts this
 services). After this command I am automatically taken to terminal 7 with a
 running GUI / blank screen. 2. During boot the system hangs for quite
 some time with displaying the message A start job is running for
 dev-disk-by\x2duuid-29d73912\x2d52ca\x2d4026\x2d8a14\x2d72c08e242b0b.device
 . I found this https://forum.manjaro.org/index.php?topic=5538.0 and the
 system continues to boot, but it is still something I would like to fix.
 Any ideas? 3. Do to Bug #758787
 (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758787) my apt became
 useless. Does anybody know of a workaround? 
 My system is a laptop with Intel Atom processor and an onboard Intel
 Graphics chip. Kernel version is 3.14-2-686-pae. 
 Dmesg also just gives me the report found in attachment. I could not find
 any helpful information in /var/log/Xorg.0.log or /var/log/Xorg.1.log
 neither in /var/log/syslog. Google gives no solution either... 
 Any help is greatly appreciated.
  
 Yours,
  
 Hans
  

Hi Hans,

I am running Jessie on an netbook EEEPC 1005HAG, which is an atom processor 
and an Intel 945 graphics chip. It is running very well.

So let me try to help.

First, check out, that during upgrade no needed packages were uninstalled. 
This mostly when using aptitude. For upgrade I still prefer apt-get dist-
upgrade. Later you can finetune with aptitude.

Second, do not use any vga= option in grub. For this hardware, I got best 
results in letting the kernel decide, which resolution to use. Otherwise you 
might get in trouble with X.

Third, just for trying, install some other window manager, I suggest LXDE. It 
is fast and stable. 

Fourth, for testing purposes, remove /etc/init.d/gdm and /etc/init.d/kdm 
somewhere else. Doing so, X is not started automatically. But you can start X 
with the commad startx in the commandline as root. So you can see, if errors 
appear, and what really happens. If everything is running fine later, you can 
just rem,ove the files back.

Fifth, again, just for testing purposes, you can install grub-legacy. On this 
older system I am quite happy with it. However, some people will now say, it 
does not have any effects on X - and they may be right.

I hope, this will help a little, to find the reason for the problem.

Good luck!

Hans


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/1502752.ekHtRjErud@protheus7

Re: Problem with upgrade from wheezy to jessie

[André Büsgen]

Am 31.10.2013 15:41, schrieb Jochen Spieker:
 André Büsgen:
 I've got an problem with upgrading my debian wheezy to jessie.
 While the upgrade was running the system got a problem with the graphics
 drivers.
 Since this upgrade I get an error by excecuting 'startx'.
 Even starting other applications (for example firefox) fails.
 Everytime i try to start firefox i get an error that there is no display
 specified.
 This is expected if X is not running. :)

 My graphics card is: ATI Radeon HD 4800 Series
 And heres what is in /var/log/Xorg.0.log:

 …
 [50.219] Loading extension GLX
 [50.219] (II) LoadModule: fglrx
 [50.219] (II) Loading /usr/lib/xorg/modules/drivers/fglrx_drv.so
 [50.231] (EE) Failed to load
 /usr/lib/xorg/modules/drivers/fglrx_drv.so:
 /usr/lib/xorg/modules/drivers/fglrx_drv.so: undefined symbol:
 noXFree86DRIExtension
 http://askubuntu.com/questions/203232/?

 BTW, your PGP signature is invalid.

 J.

Hello,
First  I want to thank you for your fast help but it didn't work for me.
After I had uninstalled the broken graphics driver I tried to install
the new driver but everytime I try to run the installation script it
responses that it can't find the file version.h and that I have to
install the Kernel headers.
Installing the latest Kernel header wasn't the problem but even after
installing them the installation script has the same error.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/5274f8f5.1030...@yahoo.de

Problem with upgrade from wheezy to jessie

[André Büsgen]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
 
Hello everyone,
I've got an problem with upgrading my debian wheezy to jessie.
While the upgrade was running the system got a problem with the graphics
drivers.
Since this upgrade I get an error by excecuting 'startx'.
Even starting other applications (for example firefox) fails.
Everytime i try to start firefox i get an error that there is no display
specified.
Even after trying to specify a display with DISPLAY=:0 fails.
My graphics card is: ATI Radeon HD 4800 Series
And heres what is in /var/log/Xorg.0.log:

X.Org X Server 1.14.3
Release Date: 2013-09-12
[50.210] X Protocol Version 11, Revision 0
[50.210] Build Operating System: Linux 3.10-2-amd64 x86_64 Debian
[50.210] Current Operating System: Linux Andre-PC 3.10-3-amd64
#1 SMP Debian 3.10.11-1 (2013-09-10) x86_64
[50.210] Kernel command line:
BOOT_IMAGE=/boot/vmlinuz-3.10-3-amd64
root=UUID=3f990915-2ba0-4a78-a51e-ac3555653c94 ro quiet
[50.210] Build Date: 05 October 2013  02:04:26PM
[50.211] xorg-server 2:1.14.3-4 (Julien Cristau
jcris...@debian.org)
[50.211] Current version of pixman: 0.30.2
[50.211] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[50.211] Markers: (--) probed, (**) from config file, (==)
default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[50.212] (==) Log file: /var/log/Xorg.0.log, Time: Thu Oct 31
14:38:01 2013
[50.212] (==) Using config file: /etc/X11/xorg.conf
[50.212] (==) Using system config directory
/usr/share/X11/xorg.conf.d
[50.213] (==) ServerLayout aticonfig Layout
[50.213] (**) |--Screen aticonfig-Screen[0]-0 (0)
[50.213] (**) |   |--Monitor default monitor
[50.213] (**) |   |--Device aticonfig-Device[0]-0
[50.214] (==) No monitor specified for screen
aticonfig-Screen[0]-0.
Using a default monitor configuration.
[50.214] (==) Automatically adding devices
[50.214] (==) Automatically enabling devices
[50.214] (==) Automatically adding GPU devices
[50.214] (WW) The directory /usr/share/fonts/X11/cyrillic does
not exist.
[50.214] Entry deleted from font path.
[50.214] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins
[50.214] (==) ModulePath set to /usr/lib/xorg/modules
[50.214] (II) The server relies on udev to provide the list of
input devices.
If no devices become available, reconfigure udev or disable
AutoAddDevices.
[50.214] (II) Loader magic: 0x7fa2ba97bd00
[50.214] (II) Module ABI versions:
[50.214] X.Org ANSI C Emulation: 0.4
[50.214] X.Org Video Driver: 14.1
[50.214] X.Org XInput driver : 19.1
[50.214] X.Org Server Extension : 7.0
[50.216] (--) PCI:*(0:1:0:0) 1002:9442:1787:2009 rev 0, Mem @
0xd000/268435456, 0xfdee/65536, I/O @ 0xee00/256, BIOS @
0x/131072
[50.216] (II) Open ACPI successful (/var/run/acpid.socket)
[50.216] Initializing built-in extension Generic Event Extension
[50.217] Initializing built-in extension SHAPE
[50.217] Initializing built-in extension MIT-SHM
[50.217] Initializing built-in extension XInputExtension
[50.217] Initializing built-in extension XTEST
[50.217] Initializing built-in extension BIG-REQUESTS
[50.217] Initializing built-in extension SYNC
[50.217] Initializing built-in extension XKEYBOARD
[50.217] Initializing built-in extension XC-MISC
[50.217] Initializing built-in extension SECURITY
[50.217] Initializing built-in extension XINERAMA
[50.217] Initializing built-in extension XFIXES
[50.217] Initializing built-in extension RENDER
[50.217] Initializing built-in extension RANDR
[50.217] Initializing built-in extension COMPOSITE
[50.217] Initializing built-in extension DAMAGE
[50.218] Initializing built-in extension MIT-SCREEN-SAVER
[50.218] Initializing built-in extension DOUBLE-BUFFER
[50.218] Initializing built-in extension RECORD
[50.218] Initializing built-in extension DPMS
[50.218] Initializing built-in extension X-Resource
[50.218] Initializing built-in extension XVideo
[50.218] Initializing built-in extension XVideo-MotionCompensation
[50.218] Initializing built-in extension SELinux
[50.218] Initializing built-in extension XFree86-VidModeExtension
[50.218] Initializing built-in extension XFree86-DGA
[50.218] 

Re: Problem with upgrade from wheezy to jessie

[Jochen Spieker]

André Büsgen:
 
 I've got an problem with upgrading my debian wheezy to jessie.
 While the upgrade was running the system got a problem with the graphics
 drivers.
 Since this upgrade I get an error by excecuting 'startx'.
 Even starting other applications (for example firefox) fails.
 Everytime i try to start firefox i get an error that there is no display
 specified.

This is expected if X is not running. :)

 My graphics card is: ATI Radeon HD 4800 Series
 And heres what is in /var/log/Xorg.0.log:
 
…
 [50.219] Loading extension GLX
 [50.219] (II) LoadModule: fglrx
 [50.219] (II) Loading /usr/lib/xorg/modules/drivers/fglrx_drv.so
 [50.231] (EE) Failed to load
 /usr/lib/xorg/modules/drivers/fglrx_drv.so:
 /usr/lib/xorg/modules/drivers/fglrx_drv.so: undefined symbol:
 noXFree86DRIExtension

http://askubuntu.com/questions/203232/?

BTW, your PGP signature is invalid.

J.
-- 
If I was a supermodel I would give all my cocaine to the socially
excluded.
[Agree]   [Disagree]
 http://www.slowlydownward.com/NODATA/data_enter2.html


signature.asc
Description: Digital signature