Bugzilla – Bug 1213148
Atomisp results in tumbleweed being unable to boot on some atom computers since kernel 6.2
Last modified: 2024-05-02 06:40:59 UTC
Since kernel 6.2, my Tumbleweed refuses to boot because of intel isp. Ubuntu had this problem but they fixed it by disabling atomisp. I have a request to the openSUSE kernel maintainers: Can you please disable atomisp in your kernel, especially since this will affect Leap later on next year?
Sorry, by intel isp i meant atomisp instead😀
Yes, that's a known problem (bsc#1210639). At best, we should address the regression, but the complete disablement is a secondary option, of course. On a system with the blacklist, could you try to load the module manually, and get the crash messages? Then I can take a bit deeper look.
No. I do not know how to blacklist it properly. I know i have to press e in the grub menu and pass blacklist=atomisp, but where?
(In reply to Basil Cat from comment #3) > No. I do not know how to blacklist it properly. I know i have to press e in > the grub menu and pass blacklist=atomisp, but where? So you're already blacklisting it :) Just try to load atomisp manually after the boot again, and get the crash messages. If you get the kernel Oops or such, please attach to Bugzilla. If you'd like to blacklist the module persistently, create a file such as /etc/modprobe.d/90-atomisp-blacklist.conf, containing a line: blacklist atomisp
I tried blacklisting it by the end of the grub, but it didn't work 🤦🏽
(In reply to Basil Cat from comment #5) > I tried blacklisting it by the end of the grub, but it didn't work 🤦🏽 What exactly did you do? At best create a modprobe.d config file to blacklist persistently.
(In reply to Takashi Iwai from comment #6) > (In reply to Basil Cat from comment #5) > > I tried blacklisting it by the end of the grub, but it didn't work 🤦🏽 > > What exactly did you do? > > At best create a modprobe.d config file to blacklist persistently. Oh, i sorted it out😀 I did modprobe.blacklist=atomisp and it now boots. I also managed to block the module persistently by adding it to the modprobe.blacklist conf.
OK, now on the system with blacklist, try to load the module manually again. This should trigger the crash, but since the system is already up, we have a better chance to get a crash log.
No follow up, closing