(X)(L)ubuntu (MATE) 16.10 Yakkety Yak

[zzd10h]

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

[xeno74]

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

Hi zzd10h,

Thanks a lot for testing the upgrade to ubuntu MATE 16.10. Could you please try out the VESA Framebuffer driver?

Section Device in the xorg.conf:

Code: Select all

# **********************************************************************
# 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

Thanks,

Christian

[zzd10h]

Hi,
same problem, I had 2 device sections, 1 for Radeon and 1 for fbdev.
I removed Radeon block and modified fbdev one to reflect yours and rebooted.

I forgot to say that screen is black but after a while, I see the xdm (?) logon screen but all in black except a white box to enter my user/pwd.
After to have entered my credentials, black screen again...

[Srtest]

You can also try the modesetting driver instead of fbdev or radeon. I actually did your little trick of renaming glamor and got radeon in xorg.conf to work again.

Another thing to notice is that various managers like sddm, lightdm, etc... respond differently to our broken driver situation. Sddm presents a certain delay and color problem yet loges on just fine. Lightdm at least here for me require logging on via console and then starting the lightdm service.

[zzd10h]

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

Thx

[Srtest]

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

Thx

The place in xorg.conf where you put either radeon, amdgpu or fbdev? try modesetting, although last time I tried it had the notorious color big endian issue (while it worked).

[xeno74]

Just for info.

I have figured out, that it is very important to set the BusID correctly. Without the BusID or with the incorrect BusID, Xorg doesn't start with my Radeon HD6870.

xorg.conf:

Code: Select all

BusID "PCI:1:0:0"

Sometimes I have to set

Code: Select all

Option "RenderAccel" "false"

additionally.

[kilaueabart]

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.

[xeno74]

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.

Hi Kilaueabart,

Thank you for your explanation. I also updated my ubuntu MATE 16.10 today and I have the same issues.

Code: Select all

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

It seems our kernels need SECCOMP support. I will compile the kernel 4.1 and 4.7 with SECCOMP support.

Cheers,

Christian

[xeno74]

Hi Kilaueabart,

I compiled the final kernel 4.7 with SECCOMP support today and it solved the systemd problem on ubuntu MATE 16.10. Please use the new kernel 4.7-2.

Download: vmlinux-4.7-2-AmigaONE_X1000.tar.gz



I will also compile the stable longterm kernel 4.1 with SECCOMP support. Many thanks for reporting.

Cheers,

Christian