---------- Forwarded message ----------

From: Fritz Hudnut To: factory@lists.opensuse.org Cc: Bcc: Date: Fri, 7 Oct 2022 09:34:05 -0700 Subject: Re: TW heads up - kernel firmware fails to install I was breezing thru the posts here because the other comments were about "LENOVO" and I am running various TW iterations on a Mac. Running zypper dup -l in a Gecko Rolling addition I hit this error in a list of "firmware" updates . . . . I tried "retry" and that failed, then I tried "ignore" and it went through w/o error. Haven't rebooted yet to see if any effects will hit.

[CODE]( 92/160) Installing: kernel-firmware-qlogic-20220930-1.1.noarch .........[done] error: unpacking of archive failed on file /usr/lib/firmware/qcom/LENOVO/21BX;634045b4: cpio: File from package already exists as a directory in system error: kernel-firmware-qcom-20220930-1.1.noarch: install failed error: kernel-firmware-qcom-20220902-1.1.noarch: erase skipped ( 93/160) Installing: kernel-firmware-qcom-20220930-1.1.noarch ..........[error] Installation of kernel-firmware-qcom-20220930-1.1.noarch failed: Error: Subprocess failed. Error: RPM failed: Command exited with status 1. Abort, retry, ignore? [a/r/i] (a): [/CODE]

---------- Forwarded message ---------- From: Felix Miata To: factory@lists.opensuse.org Cc: Bcc: Date: Fri, 7 Oct 2022 12:44:08 -0400 Subject: Re: TW heads up - kernel firmware fails to install Fritz Hudnut composed on 2022-10-07 09:34 (UTC-0700):

https://forums.opensuse.org/showthread.php/576367-zypper-dup-failed explains the workaround is remove the installed package, then finish the dup. If you have no hardware depending on qcom firmware, it won't matter what you do or not, as it won't affect booting. Does anything resembling qcom show up in your lspci output? --

Felix Miata

---------- Forwarded message ---------- From: Larry Len Rainey To: Fritz Hudnut , Factory < factory@lists.opensuse.org> Cc: Bcc: Date: Fri, 7 Oct 2022 11:47:05 -0500 Subject: Re: TW heads up - kernel firmware fails to install

The fix for me was to zypper rm kernel-firmware-qcom then zypper in kernel-firmware-qcom

Don't know why that works but it does.

Felix M && Larry R:

So I checked the lspci data and indeed nothing there seemed to indicate "qcom" and clearly since the zypper went through with "i" it wasn't a "dependency" . . . . So, just for humor I ran Larry's suggested commands and that brought in a bunch of dracut lines, essentially saying, "we aren't removing the package, because . . . we can't find it." And then when I installed it, another thousand dracut lines, followed by something like, "we didn't do that, because it didn't make sense to us"??? And then, back to the cursor . . . . So all appears well, for now. Thanks for the replies on it. F