|
Bugzilla – Full Text Bug Listing |
| Summary: | Boot error while requesting firmware | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Tumbleweed | Reporter: | Vojtech Zeisek <Vojtech.Zeisek> |
| Component: | Kernel | Assignee: | openSUSE Kernel Bugs <kernel-bugs> |
| Status: | RESOLVED DUPLICATE | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | tiwai |
| Version: | Current | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | openSUSE Tumbleweed | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Vojtech Zeisek
2024-02-06 13:44:44 UTC
Likely a dup of bsc#1210639. Better to blacklist the driver. Could you boot with module_blacklist=atomisp boot parameter? Thank You. I added the parameter via editing GRUB entry and I don't see the error, but boot hangs after "Starting File System Check on /dev/disk/by...". Also, I have encrypted LVM with root and SWAP (only /boot/efi is out of it) and with this parameter I had to enter the LUKS passphrase for second time. You can add blacklist to /etc/modprobe.d/* for the permanent setup. Create a file in /etc/modprobe.d, e.g. /etc/modprobe.d/90-atomisp.conf, containing the line: blacklist atomisp (In reply to Takashi Iwai from comment #3) > You can add blacklist to /etc/modprobe.d/* for the permanent setup. > Create a file in /etc/modprobe.d, e.g. /etc/modprobe.d/90-atomisp.conf, > containing the line: > blacklist atomisp This works, so we can mark is at duplicate of https://bugzilla.suse.com/show_bug.cgi?id=1210639 Thank You. dup. *** This bug has been marked as a duplicate of bug 1210639 *** |