Page MenuHomeSolus

Boot fails with black screen and flashing cursor, every boot
Closed, ResolvedPublic

Description

My laptop with an AMD APU A10-5750M which is based on the Richland-architecture boots with a flashing cursors in the left corner. It boots fine with the nomodeset parameter. This is because that in the kernel parameters this is forced: radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 amdgpu.cik_support=1 This makes the OS try to use the AMDGPU drivers which is not supported for Richland. This has come in a new kernel update because it worked fine before. If i remove that line it boots fine but with a sudo clr-boot-manager they get back there. I have checked in /etc/kernel/cmdline.d and they are not there so i have not forced this myself.

Event Timeline

stigarn created this task.Nov 10 2017, 7:22 AM

I had this case too. In my case boot fails with black screen and flashing cursor only one time. Then when I forcefully shutdown my laptop and again start it then it works. I am on AMD Raedoen R5 Graphics Card.

JoshStrobl reopened this task as Open.Nov 10 2017, 10:54 AM
JoshStrobl removed a project: Lacks Project.
JoshStrobl added a subscriber: JoshStrobl.

@maverick1 Do not triage issues. You're not part of the triage team.

This problem still exists after update to kernel 4.13.12-32

I didn't but now i did so now I know how to fix this. However, should that really be there when it makes some computer won't boot with Solus? If it will remain there I think this should be added to the help center how to fix this if you have a computer that won't boot with that line.

baimafeima added a comment.EditedJan 6 2018, 5:02 AM

It's not related to AMD in my case as I use an Intel® Core™ i5-2540M CPU @ 2.60GHz × 4. It happened for the first time as I was aborting an update in the software center (linux firmware and linux kernels) as it was too slow (around 50kb/s). I aborted the downloads during downloading stage, not updating stage though. I had to cold reboot and was able to get into Solus again.

I've installed 4.18 from unstable now on my laptop which has this problem and it still exists.

So I've tried to modify this line radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 amdgpu.cik_support=1 to radeon.si_support=1 radeon.cik_support=1 amdgpu.si_support=1 amdgpu.cik_support=1 and now my laptop boots with the radeon driver and my desktop with a radeon 290 boots with the amdgpu driver so that solves the issue.

DataDrake added a subscriber: DataDrake.

I wonder if it's time to enable si and cik for radeon-only GPUs

I wonder if it's time to enable si and cik for radeon-only GPUs

Just ping me if you decide to try anything so I can try on my laptop.

DataDrake triaged this task as Normal priority.Oct 16 2018, 5:20 PM

I'll test this out after friday sync.

Didn't happen for a long time (1-2 months I would say).

Going to force radeon.si=1 and radeon.cik=1 in today's kernel update. @stigarn testing welcome.

@DataDrake Tested now and it works! :)

DataDrake closed this task as Resolved.Nov 11 2018, 7:30 PM