Re: Problems with upgrade from Wheezy to Jessie
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]
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]
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]
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]
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
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
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
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
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
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
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
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
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
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
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
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
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
Patrick Bartek wrote: > Hans Krauswrote: > >> 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
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
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
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
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
> [ 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
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
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
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
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
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
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
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
On Sun, 2 Oct 2016 17:59:48 +0200 Hans Krauswrote: > 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
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
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
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
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
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
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
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
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.