Skip to content

Conversation

@jglathe
Copy link

@jglathe jglathe commented Nov 2, 2025

Originally submitted by @lakatdev, got processed on my "make stubble boot all x1 stuff I have/have data for" quest. Couldn't verify it boots.

Signed-off-by: Jens Glathe <jens.glathe@oldschoolsolutions.biz>
@seqre
Copy link

seqre commented Nov 3, 2025

I also have Acer Swift Go 14 AI and I wanted to check if I get the same data, so I run sudo fwupdtool hwids and got something slightly different. I see that my BIOS is newer and the first three hardware IDs that depend on it differ. I'm not sure if those could be useful, but I'm sharing those just in case.

Computer Information
--------------------
BiosVendor: Insyde Corp.
BiosVersion: V1.24
BiosMajorRelease: 0
BiosMinorRelease: 0
FirmwareMajorRelease: 01
FirmwareMinorRelease: 15
Manufacturer: Acer
Family: Swift Go 14 AI
ProductName: Swift SFG14-01
ProductSku: 
EnclosureKind: a
BaseboardManufacturer: SX1
BaseboardProduct: Bluetang_SX1
Hardware IDs
------------
{9b9eea2b-c3ea-56e7-98de-6e76c9a9fddb}   <- Manufacturer + Family + ProductName + ProductSku + BiosVendor + BiosVersion + BiosMajorRelease + BiosMinorRelease
{6b76eeb8-f641-55e0-a7a6-8e9bf87480b8}   <- Manufacturer + Family + ProductName + BiosVendor + BiosVersion + BiosMajorRelease + BiosMinorRelease
{b28920f2-7d66-52cb-a8cb-3e012918c84f}   <- Manufacturer + ProductName + BiosVendor + BiosVersion + BiosMajorRelease + BiosMinorRelease
{79dd27da-6d6b-57da-8fba-b97b489be61d}   <- Manufacturer + Family + ProductName + ProductSku + BaseboardManufacturer + BaseboardProduct
{3bd63b6b-dfa3-5314-9846-76363ae49445}   <- Manufacturer + Family + ProductName + ProductSku
{03f8cc3c-5d61-5ea0-aeb1-b3142528bce2}   <- Manufacturer + Family + ProductName
{3f49141c-d8fb-5a6f-8b4a-074a2397874d}   <- Manufacturer + ProductSku + BaseboardManufacturer + BaseboardProduct
{7c107a7f-2d77-51aa-aef8-8d777e26ffbc}   <- Manufacturer + ProductSku
{2e71fd01-d5f5-5c67-9abc-c47c10f08626}   <- Manufacturer + ProductName + BaseboardManufacturer + BaseboardProduct
{6abb9980-4909-5d87-95a4-871129047302}   <- Manufacturer + ProductName
{a07b1705-c904-5a73-b97a-f46bc2dd8400}   <- Manufacturer + Family + BaseboardManufacturer + BaseboardProduct
{94782273-eb4e-57d4-b9c1-bfc88588e6c0}   <- Manufacturer + Family
{92dcc94d-48f7-5ee8-b9ec-a6393fb7a484}   <- Manufacturer + EnclosureKind
{32f83b0f-1fad-5be2-88be-5ab020e7a70e}   <- Manufacturer + BaseboardManufacturer + BaseboardProduct
{1e301734-5d49-5df4-9ed2-aa1c0a9dddda}   <- Manufacturer
Extra Hardware IDs
------------------
{e66990c4-b390-59c3-a580-149c73cfe585}   <- Manufacturer + Family + ProductName + ProductSku + BiosVendor
{69670c5e-509d-5193-9f0a-882a00180b1a}   <- Manufacturer + Family + ProductName + BiosVendor
{86654360-65f0-5935-bc87-81102c6a022b}   <- Manufacturer + BiosVendor

Also, I'm happy to test this PR on my device, but as I'm fairly ignorant about such low-level work, I'd appreciate some pointers with taht.

@jglathe
Copy link
Author

jglathe commented Nov 3, 2025

I guess it would be okay to combine the differing lines into the json If I understood this right. Re testing, you can either ukify the kernel yourself, or you use the pre-built .debs on my google drive for 6-17.0-jg-1. This kernel has all the hwids and dtbs linked to its kernel and boot on all of these newly pr'ed devices (Plus Dell 5455, working on a dedicated dtb).

@seqre
Copy link

seqre commented Nov 4, 2025

@jglathe I installed all the .debs and there is for sure an improvement! For instance, power management went from not working at all (always showing battery completely discharged) to slightly working (recognizing that the battery has some charge and whether a charger is connected).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants