You are not logged in.
I'd just gotten a new SSD and finished up moving my Arch installation across to it. After boot, I got the same error as another user, about "execlists". I didn't upgrade the kernel (although it was 4.2 before the move anyway) and rsynced the whole tree. Initially I thought the problem was the new SSD. But after headbanging for few hours, I narrowed it down to GRUB. If I `dd` the old SSD to the new one, everything works fine. But as soon as I reinstall GRUB, I'll need the fix mentioned in the other thread.
GRUB package hasn't changed for more than a year. I also diffed everything under /boot/grub/ and it's all the the same. I'm going to start diffing on block level. Does anyone have any other ideas?
EDIT: Turns out I'd played around with `i915` module options and had not built the initramfs afterwards. All good now.
Last edited by oxplot (2015-12-14 12:41:21)
Offline
Perhaps it's the UUID's of the disks differing. Or labels, or even perhaps which sdX it is. One of those would be the only difference if syncing the files doesn't work and dd'ing a copy does.
Offline
If I `dd` the old SSD to the new one, everything works fine. But as soon as I reinstall GRUB, I'll need the fix mentioned in the other thread.
This. As in, even on the original disk, reinstalling GRUB causes the issue. Forget the new disk (ie all UUIDs, labels, etc are the same).
Offline
Ok, I can't really comment further then. SysLinux for the win - dead simple unlike GRUB which is so complex it has apparently become self-aware in your case.
![]()
Offline