juanejot
commented
2 years ago Screenshot of message about the PARTUUID:
~It occurs to me as possible that the evolving OpenLinuxBoot.efi and ext4_64.efi drivers for OpenCore Legacy Patcher may be somehow involved (see my comment on issue #222). The versions that come/work with the OpenCore 0.7.3 base of OpenCore Legacy Patcher 0.3.1 are different than the latest that come/work with OpenCore 0.7.5. But this may have nothing to do with it, as the whole bootloader setup worked fine with Pop!_OS 21.04 & 21.10 through kernel 5.13.0-7620-generic.~ UPDATE 11/20: While this bootloader configuration remains on my system, it seems more likely given the success listed way below with kernel 5.15.3, as opposed to 5.15.0 through 5.15.2, is unrelated to which bootloader I use.
timatinsipid
timjordanatteck
jacobgkau
mdpetters
How did you upgrade to 21.10? (Fresh install / Upgrade)
Upgraded from 21.04
Related Application and/or Package Version (run
apt policy $PACKAGE NAME):Unexpected upgrade to kernel 5.15.0-76051500, then BusyBox 1.30.1 & initramfs (what works with 5.13 is 0.140ubuntu6, dunno if 5.15 uses same)
Issue/Bug Description: Upon a regular cycle of
sudo apt update && sudo apt full-upgrade, the 5.15 kernel was unexpectedly installed. Upon attempt to boot, it dropped me to BusyBox (uh oh, initramfs updates went wrong). Sure enough, the PARTUUID it was trying to use as root was notone that was on my system, once successfully booted to 5.13 &EDIT: It did match the PARTUUID called up byls -al /dev/disk/by-uuidchecked.cat /proc/cmdlinewhile booted to 5.13-7620-generic, so that's likely a red herring; ie. root is not being found, but not exactly for that reason?Steps to reproduce (if you know): As above
Expected behavior: Boot to 5.15, or at least that result when I type in
uname -rOther Notes: I am running Pop!_OS 21.10 Beta on a MacBookPro5,3 using version 0.3.1 of the OpenCore Legacy Patcher (based off of OpenCore 0.7.3). See update for notes on this. [UPDATE 11/20: This is likely unrelated, as comments closer to the bottom will point out the likely cause & potential solution.]
Meanwhile, everything works as expected* (so far) under 5.15 kernel, on separate 9700K/RX580 desktop machine with OpenCore 0.7.5 & Pop!_OS 21.10 beta installed on its own drive, separate from other OSes.
~(except, of course, for awaiting the update to Application Picker as in issue #243; the old-style one still eventually loads, but only after waiting to invoke it for at least 10 or so minutes. On the IC2Duo T9900/9400M/9600M GT system in this* issue, the Application Picker has always continued to work, as long as I can get through boot.)~