Snapdragon X1 devices

[ArminiusTux]

At last, the reigning generation X1:

• Medion SPRCHRGD 14 S1 Elite

Computer Information
--------------------
BiosVendor: Medion
BiosVersion: 1.03
BiosMajorRelease: 1
BiosMinorRelease: 2
FirmwareMajorRelease: 01
FirmwareMinorRelease: 00
Manufacturer: MEDION
Family: SPRCHRGD
ProductName: 14 S1 Elite
ProductSku: ML-230007 40088830
EnclosureKind: a
BaseboardManufacturer: MEDION
BaseboardProduct: NM14QX4
Hardware IDs
------------
{e72ceeaf-45c6-50f5-9a8d-f3af93228f05}   <- Manufacturer + Family + ProductName + ProductSku + BiosVendor + BiosVersion + BiosMajorRelease + BiosMinorRelease
{0f49db05-25d9-5f1a-a633-40b358f6f6d2}   <- Manufacturer + Family + ProductName + BiosVendor + BiosVersion + BiosMajorRelease + BiosMinorRelease
{f6304115-77d2-52ef-b050-77b79c416b76}   <- Manufacturer + ProductName + BiosVendor + BiosVersion + BiosMajorRelease + BiosMinorRelease
{7cbb6d59-d341-5ef2-ba12-dd3bc4a41df6}   <- Manufacturer + Family + ProductName + ProductSku + BaseboardManufacturer + BaseboardProduct
{2fee1e80-b28f-51f2-8421-f0c39aa97516}   <- Manufacturer + Family + ProductName + ProductSku
{2904a882-918e-5f0b-9ac6-6a9737e685c9}   <- Manufacturer + Family + ProductName
{ba6260c3-a098-59ba-b999-2783726d1e44}   <- Manufacturer + ProductSku + BaseboardManufacturer + BaseboardProduct
{3713fa68-5f78-5538-b954-5e82e6c25646}   <- Manufacturer + ProductSku
{f3ceb2c3-66db-5519-98bc-d62cba323666}   <- Manufacturer + ProductName + BaseboardManufacturer + BaseboardProduct
{9eb99973-f4f7-53b2-8682-faafa5f8ad1f}   <- Manufacturer + ProductName
{ec048a86-f99a-5f29-a128-04d9254808ba}   <- Manufacturer + Family + BaseboardManufacturer + BaseboardProduct
{6c8c18e3-97bc-5d6a-8925-6b35df930a63}   <- Manufacturer + Family
{6827ad14-820d-5cd8-99d7-bbca641f70f9}   <- Manufacturer + EnclosureKind
{051d7406-b9df-588c-aba8-641ef322aaf2}   <- Manufacturer + BaseboardManufacturer + BaseboardProduct
{54c22697-274f-5508-ba48-07d5bd0c0894}   <- Manufacturer
Extra Hardware IDs
------------------
{6b54ec94-c2bb-5008-abe3-975b26e8a371}   <- Manufacturer + Family + ProductName + ProductSku + BiosVendor
{776dd828-0ea0-52b3-93d9-b4f97ac0e7e1}   <- Manufacturer + Family + ProductName + BiosVendor
{b5c59cf9-9f70-5709-99c3-9bc3ae44a9f0}   <- Manufacturer + BiosVendor

x1e78100-medion-sprchrgd-14s1-elite_arminiustux.txt

[ektor5]

Hi there, have you tested this device with Linux? There is no DTS in mainline at the moment.

[ArminiusTux]

Hello @ektor5,

no I haven't, the Medion is my main-dev platform for Windows on ARM.
I was rather planning to use my Lenovo X13s as a test candidate for Linux.

Though the best patients for a life-support boost, would be any Snapdragon device with 4GB of RAM.
It is a pain in the @rs€ to run Windows 11 on those and Linux could help a lot here if one's expectation is not higher than a mobile raspberry.

[chrisoctane]

HP Omnibook X 14 [fe0000] [ X1E-78-100]

Computer Information
--------------------
BiosVendor: Insyde
BiosVersion: F.32
BiosMajorRelease: 15
BiosMinorRelease: 32
FirmwareMajorRelease: 11
FirmwareMinorRelease: 2c
Manufacturer: HP
Family: 103C_5335M8 HP OmniBook X
ProductName: HP OmniBook X Laptop 14-fe0xxx
ProductSku: A39FCEA#ABU
EnclosureKind: a
BaseboardManufacturer: HP
BaseboardProduct: 8CBE
Hardware IDs
------------
{f4203a4d-92d1-5514-ac81-5699c7aca347}   <- Manufacturer + Family + ProductName + ProductSku + BiosVendor + BiosVersion + BiosMajorRelease + BiosMinorRelease
{67752fd2-d6a4-5c11-aa85-6fb422b5941a}   <- Manufacturer + Family + ProductName + BiosVendor + BiosVersion + BiosMajorRelease + BiosMinorRelease
{7bcab202-94d5-5613-bb80-b8ac8ed7bc9e}   <- Manufacturer + ProductName + BiosVendor + BiosVersion + BiosMajorRelease + BiosMinorRelease
{de4289da-f812-52ed-b6bb-7430625186e5}   <- Manufacturer + Family + ProductName + ProductSku + BaseboardManufacturer + BaseboardProduct
{016779e6-6578-54ef-88a0-ba19e7b36a3c}   <- Manufacturer + Family + ProductName + ProductSku
{811126e6-4aee-5f9e-827d-d0f12f6a6f00}   <- Manufacturer + Family + ProductName
{d8dd7a7c-155f-540b-bdc7-0cf308b11231}   <- Manufacturer + ProductSku + BaseboardManufacturer + BaseboardProduct
{a061151b-acda-5cfa-aec2-d6f96123c510}   <- Manufacturer + ProductSku
{1a192aee-2cfd-5ab5-95f9-8093218a48ef}   <- Manufacturer + ProductName + BaseboardManufacturer + BaseboardProduct
{eaab52c6-ed22-5e1b-b788-fc5a0531291d}   <- Manufacturer + ProductName
{848aeb1d-302b-5b6b-9109-0f4632535915}   <- Manufacturer + Family + BaseboardManufacturer + BaseboardProduct
{5d43face-6ba8-5d41-8914-12f3410bbcf9}   <- Manufacturer + Family
{f999e8e2-2bed-5ee7-85be-a69096b9544d}   <- Manufacturer + EnclosureKind
{2ae478e9-ef65-5485-bb06-a233136e53c7}   <- Manufacturer + BaseboardManufacturer + BaseboardProduct
{93f84748-c854-5d6b-b78a-13c2361e0758}   <- Manufacturer
Extra Hardware IDs
------------------
{34469493-b7aa-54da-88b3-6f27159bb4c0}   <- Manufacturer + Family + ProductName + ProductSku + BiosVendor
{68d24be5-01b6-5d88-83fb-df2bcfa879aa}   <- Manufacturer + Family + ProductName + BiosVendor
{ad0b7f58-06f2-50b9-856b-343f54261425}   <- Manufacturer + BiosVendor

[jayaddison]

Medion SPRCHRGD 14 S1 Elite

I have one of these devices, and would be glad to contribute to testing it.

(I have built a DTB based on a recent LKML patchset and have used GRUB's devicetree directive to attempt to boot from that -- the kernel does appear to be boot, and the keyboard is responsive, but the display goes blank, and attempting to change Virtual Terminal does not help. I've attempted a few basic cmdline tweaks such as nomodeset to get a functional console, with no luck so far)

[ektor5]

Medion SPRCHRGD 14 S1 Elite

I have one of these devices, and would be glad to contribute to testing it.

(I have built a DTB based on a recent LKML patchset and have used GRUB's devicetree directive to attempt to boot from that -- the kernel does appear to be boot, and the keyboard is responsive, but the display goes blank, and attempting to change Virtual Terminal does not help. I've attempted a few basic cmdline tweaks such as nomodeset to get a functional console, with no luck so far)

Hi @jayaddison,
Probably you didn't add the proper firmware in /lib/firmware/qcom/x1e80100/MEDION folder. Please check.
You may need to copy the firmware from the Windows partition.

P.S: ask in #aarch64-laptops on oftc.net to get support for this.

[jayaddison]

Thank you, @ektor5 - that likely explains it. I'll try adding some of the vendor's firmware to that directory soon (it may take me a little while to rebuild the initrd where I think they should be placed). I'll join the IRC channel too.

[jayaddison]

(done, albeit using a firmware path with lowercase medion instead of MEDION, to correspond to the DTS files in the patchset)

[jayaddison]

Probably you didn't add the proper firmware in /lib/firmware/qcom/x1e80100/MEDION folder. Please check.

I can confirm that that resolved the blank-display problem - thank you @ektor5.

[idnovic]

Hi @jayaddison, Probably you didn't add the proper firmware in /lib/firmware/qcom/x1e80100/MEDION folder. Please check. You may need to copy the firmware from the Windows partition.

P.S: ask in #aarch64-laptops on oftc.net to get support for this.

slightly offtopic:

Do you happen to know how likely it is that the firmware is integrated into a linux firmware package it the future?

This is going to be my first arm laptop. Medion stopped selling them. A firmware update seems unlikely. Can I copy the firmware from windows and delete the windows partition or should I keep it?

[ArminiusTux]

This is going to be my first arm laptop. Medion stopped selling them. A firmware update seems unlikely. Can I copy the firmware from windows and delete the windows partition or should I keep it?

Since the Medion uses regular NVMe modules (M.2 2280), it would be less effort and pain to physically access the SSD in order to back it up (externally) or replace it altogether, instead of modifying a Win11 ARM ISO to integrate the Qualcomm drivers for a potential Windows re-install.

add the proper firmware in /lib/firmware/qcom/x1e80100/MEDION folder

A shame the Linux kernel devs (@tuxedo-ggo, @konradybcio, @lumag, @krzk & @andersson) have not included firmware support for the little sister model (Medion SPRCHRGD 14 S1), as the internals should be identical apart from a weaker SoC (Snapdragon X Plus - X1P-42-100).

[lumag]

A shame the Linux kernel devs (@tuxedo-ggo, @konradybcio, @lumag, @krzk & @andersson) have not included firmware support for the little sister model (Medion SPRCHRGD 14 S1), as the internals should be identical apart from a weaker SoC (Snapdragon X Plus - X1P-42-100).

And a different GPU. I don't see the reason why you have tagged or tried to shame these people. Patches are welcome on linux-arm-msm ML.

[krzk]

A shame the Linux kernel devs (@tuxedo-ggo, @konradybcio, @lumag, @krzk & @andersson) have not included firmware support for the little sister model (Medion SPRCHRGD 14 S1), as the internals should be identical apart from a weaker SoC (Snapdragon X Plus - X1P-42-100).

Nothing stops you from working on this, instead of shaming other people's effort.

[ektor5]

Hi @jayaddison, Probably you didn't add the proper firmware in /lib/firmware/qcom/x1e80100/MEDION folder. Please check. You may need to copy the firmware from the Windows partition.
P.S: ask in #aarch64-laptops on oftc.net to get support for this.

slightly offtopic:

Do you happen to know how likely it is that the firmware is integrated into a linux firmware package it the future?

This is going to be my first arm laptop. Medion stopped selling them. A firmware update seems unlikely. Can I copy the firmware from windows and delete the windows partition or should I keep it?

@idnovic you can copy the firmware from the driver package from the official site https://www.medion.com/gb/service/product-detail/30038915

[lumag]

Hi @jayaddison, Probably you didn't add the proper firmware in /lib/firmware/qcom/x1e80100/MEDION folder. Please check. You may need to copy the firmware from the Windows partition.
P.S: ask in #aarch64-laptops on oftc.net to get support for this.

slightly offtopic:
Do you happen to know how likely it is that the firmware is integrated into a linux firmware package it the future?
This is going to be my first arm laptop. Medion stopped selling them. A firmware update seems unlikely. Can I copy the firmware from windows and delete the windows partition or should I keep it?

@idnovic you can copy the firmware from the driver package from the official site https://www.medion.com/gb/service/product-detail/30038915

Please try asking Medion / Emdoor to submit those files to linux-firmware. Point them to the Lenovo firmware already being a part of linux-firmware.

[jayaddison]

Quoting @lumag:

Please try asking Medion / Emdoor to submit those files to linux-firmware. Point them to the Lenovo firmware already being a part of linux-firmware.

I've asked Medion to consider doing that, by submitting a message using their customer contact support form. I forgot to mention Lenovo, unfortunately.