qcom-firmware-extract now fails for me on Dell XPS 13 with error code 1 for dpkg.
I updated to latest 6.12.0-30 qcom-x1e kernel
Mounting Windows partition nvme0n1p3...
Extracting firmware from /tmp/fwfetch.GPsaTbXd/mnt/Windows/System32/DriverStore/FileRepository
adsp_dtbs.elf
adspr.jsn
adsps.jsn
adspua.jsn
battmgr.jsn
cdsp_dtbs.elf
cdspr.jsn
qcadsp8380.mbn
qccdsp8380.mbn
qcdxkmsuc8380.mbn
Building package qcom-x1e-firmware-extracted-dell-xps139345_20250207_arm64...
Installing qcom-x1e-firmware-extracted-dell-xps139345_20250207_arm64...
E: Sub-process /usr/bin/dpkg returned an error code (1)
Hmm, reboot caused GPU driver to fail to load firmware, resulting in a 5s cycle of starting gdm and failing, and I also can’t get recovery boot working, display won’t turn on after short blackening. I can fortunately ssh into the machine.
I did a reinstall of linux-firmware, but qcom-firmware-extract still fails. /var/log/dpkg doesn’t really give an insights. And beside removing qcom-firmware-extract there are no qcom-x1e-firmware* packages installed, so I can’t remove those.
sorry for the fallout, I’ll try to fix this as soon as we know what’s wrong. How does your /lib/firmware look like? any manually added files? Does /lib/firmware/updates exist?
EDIT: if you remove the > /dev/null from the apt command at the end of qcom-fimware-extract it should tell you what’s wrong
I did have manually added files to /lib/firmware/qcom/vpu, but cleared those and reinstalled linux-firmware.
Yes, /lib/firmware/updates exists, with a qcom folder in it
Installing qcom-x1e-firmware-extracted-dell-xps139345_20250207_arm64...
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Note, selecting 'qcom-x1e-firmware-extracted-dell-xps139345' instead of './qcom-x1e-firmware-extracted-dell-xps139345_20250207_arm64.deb'
The following NEW packages will be installed:
qcom-x1e-firmware-extracted-dell-xps139345
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/10.1 MB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 /tmp/fwfetch.TnjiloDe/qcom-x1e-firmware-extracted-dell-xps139345_20250207_arm64.deb qcom-x1e-firmware-extracted-dell-xps139345 arm64 20250207 [10.1 MB]
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LANG = "EN"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
(Reading database ... 461379 files and directories currently installed.)
Preparing to unpack .../qcom-x1e-firmware-extracted-dell-xps139345_20250207_arm64.deb ...
Unpacking qcom-x1e-firmware-extracted-dell-xps139345 (20250207) ...
dpkg: error processing archive /tmp/fwfetch.TnjiloDe/qcom-x1e-firmware-extracted-dell-xps139345_20250207_arm64.deb (--unpack):
trying to overwrite '/lib/firmware/updates/qcom/x1e80100/dell/xps13-9345/adsp_dtbs.elf', which is the diverted version of '/lib/firmware/qcom/x1e80100/dell/xps13-9345/adsp_dtbs.elf' (package: linux-firmware)
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Errors were encountered while processing:
/tmp/fwfetch.TnjiloDe/qcom-x1e-firmware-extracted-dell-xps139345_20250207_arm64.deb
N: Download is performed unsandboxed as root as file '/tmp/fwfetch.TnjiloDe/qcom-x1e-firmware-extracted-dell-xps139345_20250207_arm64.deb' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied)
E: Sub-process /usr/bin/dpkg returned an error code (1)
So seems to be conflict between linux-firmware and the package.
EDIT: I think I understand half of the problem. Fix for the bigger one is underway, one package didn’t migrate correctly so the new location isn’t picked up by update-initramfs properly.
Which one? I removed the updates/qcom folder but still fails with same error.
Also removed /lib/firmware/updates/qcom/x1e80100/dell/xps13-9345/* but still same dpkg error.
I was thinking /lib/firmware/updates as a whole. I think your previous error log is enough for me to try to reproduce it locally on my machine, let me try that.
Removing /lib/firmware/updates doesn’t do anything for the dpkg error.
Unpacking qcom-x1e-firmware-extracted-dell-xps139345 (20250207) ...
dpkg: error processing archive /tmp/fwfetch.xIdbWmCJ/qcom-x1e-firmware-extracted-dell-xps139345_20250207_arm64.deb (--unpack):
trying to overwrite '/lib/firmware/updates/qcom/x1e80100/dell/xps13-9345/adsp_dtbs.elf', which is the diverted version of '/lib/firmware/qcom/x1e80100/dell/xps13-9345/adsp_dtbs.elf' (package: linux-firmware)
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Kinda weird, cause the folder doesn’t exist. Not sure what is happening here.
Nothing, empty list. I also can’t get autocomplete for apt-get remove qcom-x1e, so it seems it’s not there.
Did a apt-get remove --purge linux-firmware. That left some qcom folders I also deleted. But reinstalling that and then still fails with dpkg error 1 in qcom-firmware-extract.
/lib/firmware (after purge)
peter@XPS13-9345:/lib/firmware$ ls
6.11.0-37-qcom-x1e 6.11.0-51-qcom-x1e 6.12.0-30-qcom-x1e regulatory.db.p7s
6.11.0-38-qcom-x1e 6.12.0-28-qcom-x1e regulatory.db skl_hda_dsp_generic-tplg.bin
Building package qcom-x1e-firmware-extracted-lenovo-21n1_20250207_arm64...
Installing qcom-x1e-firmware-extracted-lenovo-21n1_20250207_arm64...
E: Sub-process /usr/bin/dpkg returned an error code (1)
Looks like I managed to reproduce your setup Working on a fix now
EDIT: Fixes uploaded, will take a bit to show up with apt update. Should be one ubuntu-x1e-settings and one qcom-firmware-extract update. After that it should work again.
Are there any security bios-settings other than secure boot that has something to do if other os than windows boots ?
I have reinstalled windows and installed all the windows-updates.
I can boot the Ubuntu install iso from usb-c and install, but I can never boot Ubuntu after install - it just reboots and since “ubuntu” is prechosen I end up in a loop.
I have tried both old and new versions of this iso and different Ubuntu installs (dual-boot with windows, Ubuntu only, encrypted Ubuntu etc)
If I boot Ubuntu in recovery mode I can see this:
EFI stub: Booting Linux Kernel...
EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path
EFI stub: Measured initrd data into PCR 9
EFI stub: Generating empty DTB
EFI stub: Exiting boot services...
And then it reboots.
Right now I have dualboot with windows and unencrypted Ubuntu from the latest iso (20250207) and windows starts OK.
This is a Lenovo Yoga Slim 7 14Q8X9
BIOS: NHCN53WW
Bitlocker: off
Edit:
I have also reset BIOS settings (and therefor enabled secureboot again) and tried to boot - windows boots but not Ubuntu as expected. Turned off secure boot again, but the same thing happens.
I can boot the Ubuntu install iso from usb-c and install, but I can never boot Ubuntu after install - it just reboots and since “ubuntu” is prechosen I end up in a loop.
I have tried both old and new versions of this iso and different Ubuntu installs (dual-boot with windows, Ubuntu only, encrypted Ubuntu etc)
This sounds weird. Security/Bios setting etc are unlikely because that would affect the installer too. I was going to say depending on when you did this you might have hit a bug earlier yesterday where flash-kernel was broken for a while. Since the installer pulls the latest packages if you are connected to the network that might have affected new and old ISOs.
Can you get into the grub boot selection menu and press ‘e’ while the cursor is over the default entry. That should show you the default boot entry. It should say something like:
That might be it, i am at a new clean windows install right now and I am going to redownload the iso from yesterday and install Ubuntu. If I get the same problem I will look into grub and get back here, thanks.
Edit:
Yupp! Writing this from Ubuntu on X1E again - feels nice!
No problem at all
Unfortunately it did not fix my original problem with the black screen instead of a Ubuntu password splash when you have an LVM encrypted install. But I am gonna work on your hints with lsmod and see if I find a solution - I will let you know.
Hi,
I have problems booting ubuntu from usb on my Hp Omnibook x.
The usb boots intu the grub menu on other laptops fine, but my Omnibook does not identify an bootable usb in the boot manger.
I have tried changing the boot order to prioritise usb boot, Does not work
(I have disabled secure boot, even cleared the secure boot keys)
Have any other had this problem while installing Ubuntu on the Hp Omnibook X?
Working on a fix now