You are not logged in.
I tend to run the latest kernel on my machines, even if they're still in staging or testing.
I've run kernels 4.13.1-4.13.3 on my laptop without any issues. However, on my desktop machine, every version of 4.13 hangs at boot.
After selecting Arch in grub, the screen displays a garbled green pattern and that's it. The only solution each time has been to restore a Clonezilla backup, since I'm unable to boot from the failsafe option in grub either.
The desktop machine is an Intel i5 with a Gigabyte GA-Z77x-UD3H (it's 6+ years old).
I figure kernel 4.13 will hit stable soon, so I'd better work out a solution. Any ideas?
Offline
What GPU? Also, can you SSH into the machine?
aur S & M :: forum rules :: Community Ethos
Resources for Women, POC, LGBT*, and allies
Offline
Just shared Intel graphics.
I haven't tried SSHing in. In order to test, I'll have to upgrade the kernel again and risk not being able to boot. ![]()
Offline
Install the lts kernel in addition?
Offline
So the LTS kernel won't replace the existing kernel like kernels from staging and testing do? I might do that if it'll add it to grub in addition to the existing kernel. It might be good insurance. ![]()
EDIT: I installed the LTS kernel, but there's no addition entries in grub. ![]()
Last edited by Pumpino (2017-09-24 08:03:03)
Offline
you'll need to run
#grub-mkconfig -o /boot/grub/grub.cfgOffline
Thanks.
I can confirm that SSH connections fail, so it's not just a display issue. I frequently SSH in from my phone, so it's something that usually works.
Interestingly, kernel 4.13 boots fine in Fedora, so it's Arch specific.
Offline
https://wiki.archlinux.org/index.php/Ge … bug_output
Also try "nomodeset"
Offline
If the issue still occurs with nomodeset try intel_iommu=off
Edit
intel_iommu instead of intel_iommo
Last edited by loqs (2017-09-24 09:17:37)
Offline
I tried nomodeset, i915.modeset=0 and intel_iommo=off by hitting "e" to edit when the grub entry was displayed and then adding them one at a time at the end of the "rw quiet" line. Is that the correct way to do it? None of them worked.
Last edited by Pumpino (2017-09-24 09:15:23)
Offline
"intel_iommu"?
I btw. rather hoped for some useful debug output ;-)
edit: and certainly get rid of the "quiet" - also use the "debug" and other parameters on the formerly linked troubleshooting section.
Last edited by seth (2017-09-24 09:16:34)
Offline
@seth my mistake I requested intel_iommo=off instead of intel_iommu=off
Offline
yes, me and pumpipno simply crossposted. post #11 started as answer to you ![]()
Offline
Ahhh, so one of them had a typo. Indeed, we have lift-off with intel_iommu=off. Yay.
So, what exactly does that do and what's the best way to permanently solve the issue? Do I just manually add it to /boot/grub/grub.cfg and check each time there's a kernel update?
Offline
https://bugs.archlinux.org/task/55629 - likely.
Offline
Thanks. I guess I can add intel_iommu=off or intel_iommu=igfx_off to /etc/default/grub for a permanent fix.
Offline
If intel_iommu=igfx_off cures the issue it is definitely the iGPU otherwise you would need to blacklist modules/module combinations to find out of it is attributable to a particular module.
Offline