Samsung Galaxy Book Go (Snapdragon 7c gen 2) no keyboard or mouse at install screen

[skeptical]

Hi, using installer v0.4 on a Samsung Galaxy Book Go (np340xla-ka1us)

• boots to grub fine with keyboard working
• selecting regular or graphic install opens either installer screen nicely, but keyboard/mouse are inactive and there is no way to proceed.
• I haven't tried any of the advanced automated install options in grub, being unsure of recovery if things go wrong.

I should say that even getting this far seems like a miracle on this device :+1:, linaro images crash immediately. Anyhow any pointers on what to try would be appreciated, and I'd also be glad to do any remote diagnostics if you want.

[TravMurav]

Some method of reliably loading OS is needed.

Can't say about samsung but aspire1 likes to sometimes ignore usb devices after adding a Boot00xx efivar for them. Manually booting shell.efi and deleting rogue variables for my usb stick (notably, the only thing that happens with is usb-sdcard adapter I often use as a usb stick), device boots from it again (until it adds a broken variable for it at some point)

I would like to try to build a PMOS image from @TravMurav's sc7180-6.6 pmaports branch.

All the changes here are upstream in mainline, with most recent being in 6.10-rc, a bit more stuff may be found in my kernel fork but probably nothing useful for book go for now.

Do we know if this model shares any other hardware with aspire1, like the embedded controller?

No. Hardware is very different.

Would the ACPI table dump shared by @leezu be useful as a reference for improving DT?

Usually yes, though reverse engineering it is not always trivial.

I'm not a kernel hacker, but I would like to learn about crafting DTs - general guides/references appreciated. edit: I found wiki.postmarketos.org/wiki/Mainlining_Guide#Device_Tree_Source. The PMOS wiki is great!

Yes this is a great source of resources indeed.

I'm going to start working on a device port in a branch off of the sc7180-6.6 one above.

No. Please use mainline (i.e. latest 6.10-rc from kernel.org git) when you are doing kernel development. Things change a lot across versions. (... though if you wish to use pmOS tooling, you can use envkernel.sh and related workflow to build yourself a kernel from a git checkout so you don't need to change the packaged kernel at first.)

I highly recommend you to join #aarch64-laptops on OFTC since there are others trying to work on this laptop, and it would be sad if you can't coordinate efforts and repeat done work.

[hexdump0815]

@edrex - that unreliable booting is the same for me - one thing i found out is that it gets to 100% reliable when i connected the usb device via a hub iirc ... :)

[Vogtinator]

FTR, what I did was write grub2.efi to the internal ESP with a config that allows me to select either windows or an OS on USB. That works 100% reliable so far, without any issues with the USB connection or the boot menu.