Depends a little on who you trust. I do fairly new builds, and sometimes I put them on google drive here. It’s basically ubuntu config reduced to qcom-only platform support. The same kernel runs here on X13s, Windows Dev Kit 2023, HP Omnibook X14, and since recently on Snapdragon Dev Kit. The .debs can simply be installed via sudo dpkg -i *.deb when you’re in the directory with the packages. If flash-kernel knows your machine, install should run smoothly with grub. Uninstall is sudo apt-get purge linux*<versionstring>*. Normal business for tests here.
FWIW, this is the Ubuntu unstable repo:
https://code.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/unstable
Do you use the firmware from Linux-Firmware? For X13s (and the chip rev usually used) there is a better one to be found on the Windows partition - hpnv21.b8c
Okt 17 08:33:20 x13s-jg kernel: Bluetooth: hci0: setting up wcn6855
Okt 17 08:33:20 x13s-jg bootmac[1741]: Bluetooth MAC address configured successfully
Okt 17 08:33:20 x13s-jg kernel: Bluetooth: hci0: QCA Product ID :0x00000013
Okt 17 08:33:20 x13s-jg kernel: Bluetooth: hci0: QCA SOC Version :0x400c0210
Okt 17 08:33:20 x13s-jg kernel: Bluetooth: hci0: QCA ROM Version :0x00000201
Okt 17 08:33:20 x13s-jg kernel: Bluetooth: hci0: QCA Patch Version:0x000038e6
Okt 17 08:33:20 x13s-jg kernel: Bluetooth: hci0: QCA controller version 0x02100201
Okt 17 08:33:20 x13s-jg kernel: Bluetooth: hci0: QCA Downloading qca/hpbtfw21.tlv
Okt 17 08:33:21 x13s-jg kernel: Bluetooth: hci0: QCA Downloading qca/hpnv21.b8c
Okt 17 08:33:21 x13s-jg kernel: Bluetooth: hci0: QCA setup on UART is completed
For the unpatched btqca driver to load it instead of hpnv21.bin you can put it in /lib/firmware/updates/qca/ and symlink it to the .bin name. This should give better range and quality, maybe the option bug is also solved.
Do I want the el2-x1e or the x1e version?
el2 is for the adventurous if you want to run Linux on EL2, enabling KVM support. Since this also comes with drawbacks (which are neglibe for a Windows Dev Kit) I would not recommend to do this on Laptops, where you usually want the adsp to work.
Sorry, I need a little bit more help as I have never done this before.
Which .debs do I want to install?
These three?
linux-image-unsigned-6.12.0-061200rc3-x1e-generic_6.12.0-061200rc3-x1e.20241013143332_arm64.deb
linux-modules-6.12.0-061200rc3-x1e-generic_6.12.0-061200rc3-x1e.20241013143332_arm64.deb
linux-headers-6.12.0-061200rc3-x1e-generic_6.12.0-061200rc3-x1e.20241013143332_arm64.deb
Those three should suffice, but generally I just install all of them and don’t bother. The packages are a set, only for arm64-generic flavour, with all what was built with the ubuntu-mainline config. The config is stripped of the arm-64k flavour already. Therefore the instruction: Download whole folder, extract cd into it, sudo dpkg -i *.deb
I’m running Linux 6.12.0-061200rc3-x1e-generic now. Thanks!
For anyone following along, upgrading to @glathe’s kernel makes it so the qualcom camss and ov5675 drivers stop showing up and thus the camera stops working.
Is there a way to change the installation ISO so that the default user which is created is automatically in the “video” group?
I had to run ‘usermod -aG video myusername’ to get my camera to work.
Or maybe add that to the install directions at the top of this page?
I also added this hack, which may or may not have been required: X13s · jhovold/linux Wiki · GitHub
To get the camera to work in firefox I went to “about:config”, accepted the risks, and then searched for pipewire.
After that I set “media.webrtc.camera.allow-pipewire” to true and restarted Firefox.
1 Like
Well gotcha. No I haven’t tested with the camera yet, and I actually still have my own derivative X13s dtb. I guess I will fall back to “standard” X13s dtb to remove this issue.
Thanks for the time you take to build and publish newer kernel releases! I am happy to test out any new ones you put up to see if the camera is working!
I can’t seem to get it to work on my X13s with Ubuntu 24.10. I suspect it may be because I’m on the stock kernel:
Linux drack 6.11.0-9-generic
It works with the stock kernel here.
Did you install libcamera-tools and libcamera-ipa from apt?
I probably should have added that as a needed step in my post.
I can see it now though software but I have issues with permissions now.
1 Like
Did you run ‘sudo usermod -aG video yourusername’ in the terminal?
This is what I have so far:
What is the best way to upgrade to the 6.12 kernel from here? dist upgrade to plucky? or is there a better path?
I am using @glathe’s custom build of 6.12 for now, which can be obtained from the link above. Seems to be working well.
1 Like
Hello. I upgraded to 24.10 (from 24.04) a few days ago and with the 6.11.0-9 kernel it only boots once every 10 times approximately. Thus I too tried @glathe 's custom 6.12 kernel. Both kernels makes the camera being recognized by various apps. However qcam is the only app that gives any video output (e.g. cheese and mpv do not). So not that usable yet. I applied all the tips I could find above in this thread before updating to 24.10 and 6.11.0-9 so I don’t know if I needed those tips to get the camera recognized. A problem with the custom 6.12 kernel is that bluetooth is highly unstable, and not really usable. Thus, I mostly boot into an older kernel (6.11.0-06…) that works really well except no camera at all.
@glathe , any debug output you want me to run?
(EDIT: missed a 0 in the old kernel version)