Ubuntu Concept ♥️ Snapdragon X Elite

Jglathe’s ISO can do it like this, for me just set timeout=0 and use Microsoft Denali Oled DTB, and I have tried boot in Ubuntu text mode(by editing grub.cfg), it also show nothing, the screen is black, but didn’t restart the computer.

1 Like

I put a break in grub and finally able to get some usable information:

I do not understand what any of this is so I am posting it here for more knowledgeable people.

This seems to be the point where the system hangs

2 Likes

The hwids I posted are for the oled version 12cores

1 Like

Something we had seen previously was that the machine booted with display brightness set to 0. Maybe try if you can increase the brightness after a while or see something if you look closely with an external light source?

I will give it a shot tonight. I know the x elite oled has been and issue. I’ll try to provide as much useful information as I can.

[Slim 7x, 6.19.0-9-qcom-x1e]

I have ubuntu-x1e-settings installed

Restarting pipewire and wpctl status still doesn’t show a camera.

Does anything stick out in your dmesg log? Any firmware loading errors or sth like that? The device tree bits look the same as on the T14s and that works.

ov02c10 1-0036: failed to find sensor: -110
ovo2c10 1-0036: Error reading reg 0x300a: -110

and

adreno 3d00000.gpu: supply vddcx not found, using dummy regulator
adreno 3d00000.gpu: supply vdd not found, using dummy regulator

msm_dpu ae01000/display-controller: [drm:adreno_request_fw [msm]] *ERROR* failed to load gen70500_sqe.fw

msm_dpu ae01000.display-controller: Direct firmware load for qcom/gen70500_sqe_.fw failed with error -2

followed later by

msm_dpu ae01000.display-controller: [drm:adreno_request_fw [msm]] loaded qcom/gen70500_gmu_bin from new location

msm_dpu ae01000.display-controller: [drm:adreno_request_fw [msm]] loaded qcom/gen70500_sqe.fw from new location

The firmware ones are probably irrelevant, the failure is in the initrd and later it works with the real root file system but that is GPU firmware.

The ov02c10 one is the actual bug we are looking for I think

1 Like

I have to say thank you. My Dell XPS 9345 is like a different machine, far more stable and useable as a daily driver. Still no sound via speakers, but thats not a big issue for me.

Excellent work and you have my thanks.

2 Likes

maybe these extra camera patches are not included?

https://gitlab.com/Linaro/arm64-laptops/linux/-/work_items/26

2 Likes

I published another kernel update with some minor dtb changes. Our camera patches should be in sync with https://gitlab.com/Linaro/arm64-laptops/linux/-/tree/qcom-laptops-v6.19-rc8-camss

3 Likes

Slim 7x camera still not functional with new kernel. Same failed to find sensor message.

Thanks for testing, I’ll investigate further. I’ll have to build yet another new kernel anyway because we are affected by Bug #2141298 “AppArmor blocks write(2) to network sockets with L...” : Bugs : snapd

1 Like

First, thank you very much for all the great work. Also testing camera on a Slim 7x with 6.19.0-10-qcom-x1e and getting:
[ 3.157387] ov02c10 2-0036: Error reading reg 0x300a: -110
[ 3.157390] ov02c10 2-0036: failed to find sensor: -110
[ 3.159473] ov02c10 2-0036: probe with driver ov02c10 failed with error -110

Not sure if it helps, but found these patches

Best regards.

1 Like

With 6.19.0-10-qcom-x1eI get :

% wpctl status
[…]

Video
 ├─ Devices:
 │      58. Iris Decoder                        [v4l2]
 │      59. Iris Encoder                        [v4l2]
 │      60. Qualcomm Camera Subsystem           [v4l2]
 │      61. Qualcomm Camera Subsystem           [v4l2]
 │      62. Qualcomm Camera Subsystem           [v4l2]
 │      63. Qualcomm Camera Subsystem           [v4l2]
 │      64. Qualcomm Camera Subsystem           [v4l2]
 │      65. Qualcomm Camera Subsystem           [v4l2]
 │      66. Qualcomm Camera Subsystem           [v4l2]
 │      67. Qualcomm Camera Subsystem           [v4l2]
 │      68. Qualcomm Camera Subsystem           [v4l2]
 │      69. Qualcomm Camera Subsystem           [v4l2]
 │      70. Qualcomm Camera Subsystem           [v4l2]
 │      71. Qualcomm Camera Subsystem           [v4l2]
 │      72. Qualcomm Camera Subsystem           [v4l2]
 │      73. Qualcomm Camera Subsystem           [v4l2]
 │      74. Qualcomm Camera Subsystem           [v4l2]
 │      75. Qualcomm Camera Subsystem           [v4l2]
 │      77. ov02c10                             [libcamera]
 │  
 ├─ Sinks:
 │  
 ├─ Sources:
 │  *   86. Interne vordere Kamera             
 │  
 ├─ Filters:
 │  
 └─ Streams:

But neither Firefox nor Chromium detect a camera.

guess you have the Thinkpad

might need media.webrtc.camera.allow-pipewire in Firefox flags.

also libcamera 0.7 or git version should fix auto white balance / colours (Ubuntu is still on 0.5)

I think that’s right. Alex also reported it on the mailing list at https://lore.kernel.org/linux-arm-msm/11783570-cd00-4bec-9f45-65ff4e8eae19@linaro.org/
I’ll include the fix in my next build

1 Like

OK, I have got the information from the Arch Linux(run hwids.py), my device is SP11 X1E80100 OLED:

Computer Information
--------------------
Manufacturer: Microsoft Corporation
Family: Surface
ProductName: Microsoft Surface Pro, 11th Edition
ProductSku: Surface_Pro_11th_Edition_2076
BaseboardManufacturer: Microsoft Corporation
BaseboardProduct: Microsoft Surface Pro, 11th Edition
EDID: SDC4195

Hardware IDs
------------
{aca467c0-5fc2-59ad-8ed5-1b7a0988d11c}	<- #3   Manufacturer + Family + ProductName + ProductSku + BaseboardManufacturer + BaseboardProduct
{95971fb3-d478-591f-9ea3-eb0af0d1dfb5}	<- #4   Manufacturer + Family + ProductName + ProductSku
{c9c14db9-2b61-597a-a4ba-84397fe75f63}	<- #5   Manufacturer + Family + ProductName
{7cef06f5-e7e6-56d7-b123-a6d640a5d302}	<- #6   Manufacturer + ProductSku + BaseboardManufacturer + BaseboardProduct
{48b86a5e-1955-5799-9577-150f9e1a69e4}	<- #7   Manufacturer + ProductSku
{06128fee-87dc-50f6-8a3f-97cd9a6d8bf6}	<- #8   Manufacturer + ProductName + BaseboardManufacturer + BaseboardProduct
{84b2e1d1-e695-5f41-8c41-cf1f059c616a}	<- #9   Manufacturer + ProductName
{16a47337-1f8b-5bd3-b3bd-8e50b31cb1c9}	<- #10  Manufacturer + Family + BaseboardManufacturer + BaseboardProduct
{ca2e5189-1d32-509f-88a0-d4ebcc721899}	<- #11  Manufacturer + Family
{aca387a9-183e-5da9-8f9d-f460c3f50f54}	<- #11  Manufacturer + EnclosureKind
{fdef4ae0-6bfb-5706-8aae-a565639505f5}	<- #13  Manufacturer + BaseboardManufacturer + BaseboardProduct
{cc0aea32-ad2c-5013-8bed-cede6be8c9f4}	<- #14  Manufacturer
{d752a22b-1fd8-53c3-89ef-8ca95618134a}	<- #15  Manufacturer + Family + ProductName + EDID
{ca2ff828-b404-5253-9e0e-579c93bfb059}	<- #16  Manufacturer + Family + EDID
{65bc7507-3ca6-5afa-9ea1-9fd1c099a3e7}	<- #17  Manufacturer + ProductSku + EDID

Ah, yes, this makes it available, but the colours are funky indeed :mirror_ball:

Could we get this into the x1e-repo? It seems like even Ubuntu 26.04 will ship with 0.5