5 ms·
My display was not damaged. Switched back to an older kernel version and it was fine.
by makeworld 4y ago
My display was not damaged. Switched back to an older kernel version and it was fine.
- snapplebobapple 4y agoSame here, updated my framework laptop, rebooted to blinky screen, turned it off, did some research, loaded up a livecd to revert the kernel and then updated when 5.19.13 made it into arch. Thankfully just a pain in my butt not a dead lcd for me.
- dhruvmittal 4y agoI had the same experience. Updated the computer, rebooted into the blinky screen. Powered off the machine & went to the BTRFS snapshot created immediately before my update. No damage to the screen that I'm aware of.
- snapplebobapple 4y agooh, I didn't think to try the btrfs snapshot route, that's a good idea to keep in mind for me if this happens again.
- CameronNemo 4y agoYou have to load a livecd to use an older kernel? That is pretty sad. I keep as many kernels as I like. And I can easily run a command to purge all but the running and next kernels. As another commenter mentioned, fancy pants filesystems that support snapshots simplify this situation.
- snapplebobapple 4y agowell, It's my laptop and Iw as playing with endeavouros on it so it didn't have any fallback kernels. choosing grub options isn't really a brains operation for most of us, we stick with defaults.
- nemetroid 4y agoUsing a live image for the once-in-a-decade event that a kernel doesn't boot properly isn't a huge hassle.
- craftkiller 4y ago> fancy pants filesystems that support snapshots simplify this situation. This is what I used. zfsbootmenu is an EFI executable with support for doing zfs rollbacks (and any other arbitrary zfs command) so as long as my EFI partition is left untouched, I don't need a livecd or another partition or anything.
- bingo-bongo 4y ago> did some research Maybe just didn’t want to boot on faulty kernel at all, now that the risk of permanently damaging the display was known.