mersenneforum.org

mersenneforum.org (https://www.mersenneforum.org/index.php)
-   GPU Computing (https://www.mersenneforum.org/forumdisplay.php?f=92)
-   -   Ubuntu colonel update 3.2.0.38.46 to .39.47 issues (https://www.mersenneforum.org/showthread.php?t=17991)

Graff 2013-03-19 18:50

Ubuntu colonel update 3.2.0.38.46 to .39.47 issues
 
Both of my GPU-equipped Ubuntu 12.04-LTS boxes have just been
"upgraded" from kernel 3.2.0.38.46 to 3.2.0.39.47 by the Update Manager.
Following the required restart, the systems can be politely described
as extremely unstable. For the video display, I'm using the on-board
graphics device (an Intel 915, I believe). After a short time, the display
freezes and the pointer disappears. The only option is to reboot. The
display of text entered into terminal windows is corrupted or invisible.
As they stand, the two boxes are unusable at the moment.

Has anyone experienced grief like this with the latest patch installations?

Gareth

Dubslow 2013-03-19 18:53

If you take a look through `man apt-get` and remember which packages it updated (possibly in a log file), you ought to be able to tell apt-get to install an older version.

Graff 2013-03-19 18:56

[QUOTE=Dubslow;334022]If you take a look through `man apt-get` and remember which packages it updated (possibly in a log file), you ought to be able to tell apt-get to install an older version.[/QUOTE]

Got through one page of the man output and the system froze.

Gareth

Dubslow 2013-03-19 19:02

If you have other computers, even Windows ones available, you can find pretty much all GNU-Linux manuals online (by Googling `man apt-get`, as it were).

PS The folks over at ubuntuforums.org might be able to give you a more direct solution.

Xyzzy 2013-03-19 20:38

Use CTRL+ALT+F1 to get to a text terminal. All of the tools you need will be there. Logs for Aptitude will be in the /var/logs/apt directory.

WRT the graphics, are you using Unity? If so, perhaps try 2D. You can select this at the login screen. We sometimes have big problems with Compiz (?) and 3D.

If you have an old PCI video card you could chuck that in there just to troubleshoot. We keep an old 3DFX Voodoo card around for such times.

FWIW, regarding Ubuntu updates, we feel no pressing need to do updates immediately. Maybe set them to manual and do them occasionally? (We think there is an option somewhere to disallow kernel upgrades?)

In a worst case scenario, you can boot single-user text-mode by editing the GRUB screen at boot initiation. (You can also boot a Ubuntu CD/USB key in "live" mode and mount your drive and look at it.)

Graff 2013-03-19 21:10

[QUOTE=Xyzzy;334048]Use CTRL+ALT+F1 to get to a text terminal. All of the tools you need will be there. Logs for Aptitude will be in the /var/logs/apt directory.

WRT the graphics, are you using Unity? If so, perhaps try 2D. You can select this at the login screen. We sometimes have big problems with Compiz (?) and 3D.

If you have an old PCI video card you could chuck that in there just to troubleshoot. We keep an old 3DFX Voodoo card around for such times.

FWIW, regarding Ubuntu updates, we feel no pressing need to do updates immediately. Maybe set them to manual and do them occasionally? (We think there is an option somewhere to disallow kernel upgrades?)

In a worst case scenario, you can boot single-user text-mode by editing the GRUB screen at boot initiation. (You can also boot a Ubuntu CD/USB key in "live" mode and mount your drive and look at it.)[/QUOTE]

System is set to download updates, but installation is triggered manually.

As for Unity, I have no idea. It's one of your old machines :-)

A look in /var/log/apt/history.log shows mostly just the new kernel files.
I don't see a GRUB screen on boot, unlike my dual-OS laptop.
I'm looking to see if it possible to revert to kernel 3.2.0.38.46.

Gareth

Graff 2013-03-20 02:01

[QUOTE=Graff;334053]I'm looking to see if it possible to revert to kernel 3.2.0.38.46.
[/QUOTE]

I reverted both machines back to 3.2.0.38.46. One is sort of behaving now:
both GPUs are running. The other is still acting up. I log in and start
opening terminal windows. After a random interval, the screen goes black.
A reboot is the only way I found to get control back. By restricting the
number of terminal windows I have open and sticking to one workspace,
I have now got both GPUs working. I will see if both machines are
still working in the morning...

Gareth

Dubslow 2013-03-20 02:15

I guess it wasn't the kernel then (which it was never really likely to be).

What other packages did that update mess with?

Graff 2013-03-20 13:39

[QUOTE=Dubslow;334138]I guess it wasn't the kernel then (which it was never really likely to be).

What other packages did that update mess with?[/QUOTE]

From the /var/log/apt/history.log file (split one per line for easier
reading):

[CODE]Start-Date: 2013-03-19 18:36:43
Install:
linux-headers-3.2.0-39-generic:amd64 (3.2.0-39.62),
linux-headers-3.2.0-39:amd64 (3.2.0-39.62),
linux-image-3.2.0-39-generic:amd64 (3.2.0-39.62)
Upgrade:
libsmbclient:amd64 (3.6.3-2ubuntu2.3, 3.6.3-2ubuntu2.4),
smbclient:amd64 (3.6.3-2ubuntu2.3, 3.6.3-2ubuntu2.4),
libevince3-3:amd64 (3.4.0-0ubuntu1.5, 3.4.0-0ubuntu1.6),
linux-generic:amd64 (3.2.0.38.46, 3.2.0.39.47),
libwbclient0:amd64 (3.6.3-2ubuntu2.3, 3.6.3-2ubuntu2.4),
samba-common:amd64 (3.6.3-2ubuntu2.3, 3.6.3-2ubuntu2.4),
evince-common:amd64 (3.4.0-0ubuntu1.5, 3.4.0-0ubuntu1.6),
linux-headers-generic:amd64 (3.2.0.38.46, 3.2.0.39.47),
linux-image-generic:amd64 (3.2.0.38.46, 3.2.0.39.47),
evince:amd64 (3.4.0-0ubuntu1.5, 3.4.0-0ubuntu1.6),
linux-libc-dev:amd64 (3.2.0-38.61, 3.2.0-39.62),
samba-common-bin:amd64 (3.6.3-2ubuntu2.3, 3.6.3-2ubuntu2.4)
[/CODE]

Both machines were running this morning.

Gareth


All times are UTC. The time now is 22:44.

Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2021, Jelsoft Enterprises Ltd.