Hyperion Entertainment Message Boards

zzd10h wrote:upgraded my 16.04 partition without problem until step 12 "Reboot"

Black screen at X server opening

switching to console works. tested with kernel 4.5 and 4.6, same problem.
maybe related to my R7-250X. Nevertheless, it worked under 16.04.

I will not have the courage to reinstall 16.04 from scratch, therefore, bye

# **********************************************************************
# Graphics device section
# **********************************************************************

# Any number of graphics device sections may be present

Section "Device"
    Identifier  "VESA Framebuffer"
    Driver      "fbdev"
    #VideoRam    4096
    # Insert Clocks lines here if appropriate
EndSection

zzd10h wrote:@srtest
"You can also try the modesetting driver instead of fbdev"
Do you have more details, please ?

Thx

kilaueabart wrote:Every once in a while I have been launching Yakety Yak to see if there has been any improvement. Actually, it has seemed to work well, except for the inability to launch a proper Welcome. But I have felt safer using Xenial.

Yakety Yak's Software Updater has been telling me that I could do a partial update but I have passed on that option and rebooted to 16.04. But today I decided to give the partial update a go. At two points during the update I was given the option to keep an already configured file or replace it with a newer one. Figuring newer is better, I went with the replacement. Mistake, perhaps.

Lots of "Failed" messages during the long, long reboot afterwards, ending with a screen showing the UbuntuMATE logo bottom center and in screen center above it, the usual little login gadget. Along the whatchamacallit top border, "Amigaone" at far left, "Sat 06 Aug 16:00" in the center, and on the right a string of symbols, starting with the double circle with a ">" sticking in on the left, another circle with a stick figure (?) inside, "en_GB," and the usual power icon.

When I clicked the Login, the top line of stuff immediately vanished, and a long time later the UbuntuMATE logo moved up to the center of the screen. The mouse pointer changed to the busy dot, but I found that RMB would change it back to an arrow head as a little menu opened. I was able to use it to open my desktop, but attempts to open .png or .odt files didn't have any effect, at least in the amount of time I was willing to wait.

Going to the console I was soon given the chance to log in, and at least once "ls" worked, showing me the batch of files in my desktop and Home. But then it started spewing out in batches of about six, "Systemd [1]: Failed to start Login Service
"Systemd [4856] systemd-logind.service: Failed at step SECCOMP spawning /lib/systemd-logind: Invalid argument." (The 4--- number in the square brackets increased with each iteration.)

At one point it did inform me that there was nothing to update or upgrade, so I guess I'm not likely to get my working Yakety Yak back from the current state. I'm sort of thinking of starting from scratch again: empty the partition now holding a crippled Yakety Yak and copy my working xenial into it and follow the directions to upgrade it to Yakety Yak once more.

systemd[5544] : systemd-logind.service: Failed at step SECCOMP spawning /lib/systemd/systemd-logind: Invalid argument
systemd[1] : Failed to start Login Service
systemd[5544] : systemd-logind.service: Failed at step SECCOMP spawning /lib/systemd/systemd-logind: Invalid argument
systemd[1] : Failed to start Login Service
systemd[5544] : systemd-logind.service: Failed at step SECCOMP spawning /lib/systemd/systemd-logind: Invalid argument
systemd[1] : Failed to start Login Service
systemd[5544] : systemd-logind.service: Failed at step SECCOMP spawning /lib/systemd/systemd-logind: Invalid argument
systemd[1] : Failed to start Login Service