Page MenuHomeSolus

Macook Pro 2011 (8,2) unable to boot Kernel 4.9.22-17+
Open, Needs More InfoPublic

Description

After downloading latest updates for 2017.04.18 my system will no longer boot. Tried using kernel 4.9.22-17 (+ additional updated versions push through sc), but no go. Have also installed further subsequent updates - still no go.

Tried to boot from live usb (usb created using dd in Solus) using latest Budgie iso (sha256 correct), same result -> initial loading messages and then solid cursor in top left corner, - cannot TTY, and have to hard power off, then select 4.9.20-12 to boot successfully (Thank goodness for CBM!)

Single boot Solus only
UEFI (Apple's take on it anyway)

System specs:
OS: Solus x86_64
Model: MacBookPro8,2 1.0
Kernel: 4.9.20-12.lts
Uptime: 18 mins
Packages: 977
Shell: bash 4.3.42
Resolution: 1440x900
DE: Budgie
Theme: OSX-Arc-White [GTK2/3]
Icons: La-capitaine-icon-theme [GTK2/
Terminal: gnome-terminal
CPU: Intel i7-2720QM (8) @ 3.3GHz
GPU: Intel Integrated Graphics
GPU: AMD Radeon HD 6630M/6650M/6750M/
Memory: 1912MiB / 15962MiB

First installed Solus (November 2016 - I think?) using Shannon 1.2.1 straight out of the box, no issues, and happily using all ok with all other updates since.

Can still use my system quite happily on 4.9.20-12, but would like to update when possible.

Event Timeline

I'm having the same problem when booting a live usb created from the 2017.04.18.0 image on my early 2013 Retina MBP (10,1), and on my mid-2010 MBP (6,1).

I confirmed that if I use the 2017.01.01.0 image, then it boots fine.

Sounds like your problem is very similar to mine: https://dev.solus-project.com/T3319

I have an Apple Mac Pro with an AMD GPU. I can boot, but not to Xorg / graphical login if I upgrade linux-lts beyond 4.9.20-12. I can get a TTY by using ctrl-alt-F1 when upgrading the kernel > 4.9.20-12 and can observe a segfault in Xorg log. If I downgrade the kernel back to 4.9.20-12, then Xorg resumes working.

Are you able to perform a similar test to see if it is the same error?

Yeah, this does seem very similar.
In my case I can't use ctrl-alt-F1 to get a TTY when the crash happens, but I was able to log in over SSH and see the error in dmesg.

Can you show me how to downgrade the kernel to see if that helps? (I'm a brand new Solus user)

No problem - I'm new too. The CLI tool that you use to install, upgrade, and downgrade packages is eopkg. The method I have been using is to see the history of updates using eopkg history. That will provide a list of transaction numbers and which packages were modified during each transaction. Look through the list of transactions to find when the linux-lts kernel was updated from 4.9.20-12 to a newer revision and note the transaction number (eg. 87). Revert your installed packages to that transaction number using the transaction number identified (87 in this example) with this command: eopkg history -t 87. Please note that this will roll back all the packages installed back to that transaction, so after rolling back, reboot your host into the Xorg GUI, run all updates except the linux-lts package. Reboot after the upgrade and verify that you still have graphical login.

There is probably a more direct method of simply downgrading just the linux-lts package, but I haven't looked for that yet / don't know how to do that.

Hopefully this helps :)

Thanks!
Unfortunately it seems that since I'm upgrading from 2017-01-01, the packages that I would be rolling back to are too old to still exist (i.e. the revert fails because "kernel" doesn't exist anymore).

That said, I took a clean 2017.04.18 image, booted to a console in the live environment (by adding 3 to the end of the bootloader config), added sshd (since when mine crashes I can't get to a TTY), and then switched to run level 5 (sudo init 5), and got the following xorg and lightdm logs:

The only error I see is at the end of the lightdm log:

[+1.60s] CRITICAL: session_get_login1_session_id: assertion 'session != NULL' failed

and nothing in dmesg (those errors i mentioned only appear once i install the nvidia drivers).

So perhaps this isn't the same problem that you are having?

JoshStrobl added a subscriber: JoshStrobl.

Does this issue still persist under a fully upgraded Solus 3?

Hi Josh,

I tested with a Solus 3 Live USB last week and issue was the same.

Additionally, I have since sold my MacBook, so I unfortunately I can no longer offer any other feedback.

Regards,
Keiran

Can anyone confirm if this is still an issue? Thanks.

I can confirm for Live USB and give you some insights for 8.3 (late 2011) - installed last month. MBP 8.2 is almost the same as 8.3.

Live USB from Solus website is not booting (freeze before starting X). I managed to install Solus using old version which I found somehow (2017.01.01). Then I did full upgrade, but there were plenty issues to solve. Unfortunately I lost/deleted file with instructions. The good news is that installed and fully upgraded Solus works like a charm.

I suspect something with kernel and AMD/Intel hybrid graphics only in USB Live Mode.

The same problem with Ubuntu, Fedora and Manjaro (I had to disable one of cards to start X).

DataDrake triaged this task as Needs More Info priority.Oct 8 2018, 11:26 AM

If anyone can confirm the status of this on the new ISO, I would appreciate it!

Can't boot new ISO. I have tried few methods, including Etcher but failed. Other distributions like Manjaro (including RC versions with new kernel) or Fedora (except Ubuntu with nomodeset param) are booting and freezing just like Solus 3 ISO. Some of them show something like "Couldn't get uefi db list". Now I use old Solus 1.2 usb to boot and install.