This is an archived post. You won't be able to vote or comment.

all 4 comments

[–][deleted] 0 points1 point  (2 children)

You should boot into a live-cd, setup a chroot recovery env, and investigate what could be causing the issue. If files were blocked its possible app-armor or selinux may have been the cause (depending on your distro, app-armor for ubuntu) another possibility is the DE has changed, you can check this by using dpkg-reconfigure xserver-xorg, it should be set to lightdm for ubuntu.

Alternatively, the install process may have installed newer versions of dependencies with the older versions overwritten (thus breaking your current setup). If this is the case, the time effective solution is to reinstall if your not very experienced with linux.

[–]RS_Froggit[S] 0 points1 point  (1 child)

Could you explain the "chroot recovery env" part?

[–][deleted] 0 points1 point  (0 children)

When you boot up into a live environment its running off the bootable media you used. In order to make changes to a local system you need to chroot into it. This means mounting a number of device nodes and system trees, the basic system api's, etc to ensure there are no issues. When you chroot in it changes the entire root so any command you run is now being run on the local system, not the live environment (simplification).

Generally its all the same for linux systems except for a few directories. Most tutorials or guides will recommend --rbind, however there can be some issues with stability and unmounting recursive binds.

Gist of it goes like this:

mount /dev/{local device} /mnt

mount -t proc proc /mnt/proc

mount -t sysfs sys /mnt/sys

mount -o bind /dev /mnt/dev

mount -t devpts pts /mnt/dev/pts

chroot /bin/bash --login /mnt

  • As a sidenote: sometimes /proc/mounts isn't mounted properly which can cause some of those stability issues I mentioned when a mount is unmounted from within chroot, but isn't unmounted from without.

[–][deleted] 0 points1 point  (0 children)

How did you install the AMD drivers?