Hey @pepete73, that is probably because the current version doesn’t handle non-bitlocker Windows installations properly. You could try the git version which I just updated with a patch I received from someone who faced the same problem.
1 Like
I’ve tried both with bit locker ( critical region not found error ) and without. Any tips for modifying the script?
Some ideas:
- Add
set -xat the start and see where it fails. - Look at lsblk to check how your windows is partitioned. The script currently assumes the first bitlocker partition on
nvme0n1is your windows, maybe that is not the case on your machine? - If it finds the correct partition but fails in dislocker maybe check out
man dislockerand play with command line options (does it work if you pass the password explicitly)
1 Like
Tested on XPS 9345 as well, success. As I’ve mentioned in the bugreport its lacking some features compared to linux-next kernel, but installation was very smooth.
I have Bitlocker on, script also did not work. Failure point:
$ sudo dislocker -vv --readonly "/dev/$part" -- "$tmpdir/dislocker"
+ sudo dislocker -vv --readonly /dev/nvme0n1p3 -- /dislocker
Sat Oct 19 23:44:29 2024 [ERROR] Error looking for the VIRTUALIZATION datum type 15 (VIRTUALIZATION INFO). Internal failure, abort.
Sat Oct 19 23:44:29 2024 [CRITICAL] Unable to compute regions. Abort.
Perhaps makes sense to add optional argument to pass decrypted partition directly? eg.
sudo qcom-firmware-extract --disk-c /dev/mapper/bitlk-0a5e85ff-b32b-438f-93b1-8583f5a48a35
1 Like
ok waiting for you …
I’ve tried the git version of qcom-firmware-extract on my Dell XPS 13 9345 and it works fine with my non-bitlocker partition. Thanks.
2 Likes
New image is uploaded now!
1 Like
Redownloaded new iso - updated version - surfs and runs - updates? Now to dive in!
Works great on my T14s, well done! Actually used it for work for 3 days (docker, pycharm, python etc…) and didn’t miss anything major.
It’s clear some parts need work (audio, bluetooth etc…) I wonder how I can help. Is this still part of missing parts in the DTB or do actual drivers for things still need to be written. Sorry if this is not the right place but very excited about this progress and can’t wait to make it my daily driver.
1 Like
Are you using it despite power management not functioning?
The battery indicator works once you have your firmware installed. Someone in Bug #2084191 " [X1E] Request: Add support for Lenovo Yoga Slim 7... : Bugs : ubuntu-concept found a way to work around the qcom-firmware-extract issue you are hitting, now we only need to find a way to add that to the script!
2 Likes
Yes, and the battery life is not that bad (of course not as good as it could be) but I still get about 5 hours out of it.
One interesting thing is (and I think Windows also has this problem) is that when I reboot when the power is connected it won’t be charging after the reboot. I need to physically plug it back in to take power again.
2 Likes
I was able to install the image from Oct 20th on a Dell XPS 13 9345, the process worked great! I did change the scaling in the live session to 100% to make the installer usable, but that was a known issue.
Following the instructions, installing the firmware as documented worked perfectly, great job there @tobhe
What works:
- Bluetooth
- Accelerated graphics
- WiFi
- Touchscreen
Doesn’t work:
- Sound via speakers
- Camera
- Some apps fail to launch with accelerated graphics, like mattermost-desktop
I’ll continue to test and work on this and post updates periodically.
Great work to all involved!
2 Likes
ok thank you ,
I will try it
Its sort of both. For some things dts definitions are missing, for some there are additional driver changes necessary. As for Bluetooth (and WLAN?) it may be board definition data that need to be in the atheros firmware. I guess the T14s has the WCN7850 WLAN SoC, don’t know if there are matching data yet. To find out you could try and use my multiboot image (v7 or newer), it has a patch that gives a dmesg when no matching board data can be found. Looks like this from the Snapdragon Dev Kit:
[ 11.076679] ath12k_pci 0004:01:00.0: failed to fetch board data for bus=pci,vendor=17cb,device=1107,subsystem-vendor=105b,subsystem-device=e0eb,qmi-chip-id=2,qmi-board-id=255 from ath12k/WCN7850/hw2.0/board-2.bin
[ 11.105392] ath12k_pci 0004:01:00.0: failed to fetch board.bin from WCN7850/hw2.0
Similar things can be done for Bluetooth, basically the firmware from Windows should be reachable in Linux. WCN7850 calculates the required fw name from the chip/board data.
Regarding DP operation via type-c and sound we likely need to wait until it is worked out in the driver / firmware space.
1 Like
Added a photo for screen, fit bars defaulted to black ignoring other chosen color. Apt store refuses to open, can still install from CL. Surfs cleanly, lacks customization of kde. Still you can do basics and should grow from there.
1 Like
Don’t want to go too offtopic here, I tried the image you referenced but I was not able to get it to boot on my t14s. Same error I got when using dtbloader and I discussed this also in #aarch64-laptops. The ubuntu concepts image does not seem to have this problem (didn’t look into the specifics on how the boot differs tho).
Additionally I’ve ran it with dyndbg kernel to see what firmware blobs were missing but it was able to load everything it was looking for (I did copy everything from the Windows partition using the mentioned qcom-firmware-extract tool).
WLAN does work fine but Bluetooth is not detected, at least on my t14s, I can try on my vivobook (but I prefer my thinkpad haha)
Hmm I keep forgetting that you need a dt definition for bluetooth since its using uart. Thank you for the hint. I guess one should be able to get there soon-ish. Loking at my(*) t14s definition, there is none 
But if I check out @anonymix007’s repo with branch wip/x1e80100-6.12-rc1, it is defined.
For wcn7850, it is not only hpnv*, could also be other names like hm*. To see what it did you could do sudo dmesg|grep Bluetooth.
Bluetooth firmware for wcn7850 could be found under Windows, but was also pushed upstream last week
1 Like
Thanks, I will pull those into our linux-firmware ppa package!