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 👍, 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.

[kennethgomez01]

@skeptical have you find away for keyboard and mouse work in linux installation? It seems that the hardware is not enabled to be use in installtion of this os.

[leezu]

I'm attaching the kernel log printed at boot. The errors may clarify how to fix keyboard / mouse support.
I verified that USB Keyboard / Mouse is not working either (even though it works in the Bios and Grub).

[leezu]

The reason for lack of keyboard and mouse support in the 5.11 image is that SC7280 (Snapdragon 7c Gen 2) SMMU support - which handles IO - was not yet part of 5.11 but added later torvalds/linux@0b779f5.

Booting mainline Linux (5.18-rc3) which enables the SMMU and would provide keyboard / mouse support, the screen turns black and the system reboots after a few seconds. Booting with earlycon=efifb keep_bootcon to obtain kernel log (instead of black screen), the last lines before reboot are:

  arm-smmu arm-smmu.0.auto: probing hardware configuration...
  arm-smmu arm-smmu.0.auto: SMMUv2 with:
  arm-smmu arm-smmu.0.auto: ◦stage 1 translation
  arm-smmu arm-smmu.0.auto: ◦non-coherent table walk
  arm-smmu arm-smmu.0.auto: ◦(IDRO.CTTW overriden by FW configuration)
  arm-smmu arm-smmu.0.auto: ◦stream matching with 71 register groups
  arm-smmu arm-smmu.0.auto: ◦61 context banks (0 stage-2 only)
  arm-smmu arm-smmu.0.auto: ◦Supported page sizes: 0x61311000
  arm-smmu arm-smmu.0.auto: ◦Stage-1: 36-bit VA -> 36-bit IPA

Disabling the SMMU support at build time (CONFIG_ARM_SMMU=n, CONFIG_ARM_SMMU_V3=n, CONFIG_QCOM_IOMMU=n) restores the "no catastrophic fault but no keyboard/mouse support" behavior observed with the laptops-5.11 image.

[shawnguo2]

@leezu The installer has been tested only on Lenovo Yoga C630 (SDM850) and Flex 5G (SC8180X). And installer boots kernel with ACPI instead of DT. Although SC7280 is supported by kernel, I assume it's mostly about DT boot. With that being said, I'm not surprised by that the installer doesn't boot on SC7280.

[leezu]

@shawnguo2 it makes sense. Are you aware of any DT Boot enabled live-usb / installer / documentation to create one?

[shawnguo2]

It shouldn't be too hard to pack a DTB into debian-cdimage and instructs installer to do a DT boot. But do you have a DT for Samsung Galaxy Book Go?

[leezu]

I don't, but do you think it's possible to extract it while running the pre-installed Windows? If you have any pointers how I could try that, that would be very helpful.

[shawnguo2]

Windows only does ACPI, so there is no DT from Windows.

[leezu]

Adding a DTB into debian-cdimage is indeed trivial. One just needs to add a profiles/gnome.extra file before calling build-simple-cdd listing any .dtb files that should be copied. The devicetree can then be specified at boot by editing the grub entry and inserting devicetree /simple-cdd/NAME.dtb as a new line.

The crux is how to obtain the device tree for the Samsung Galaxy Book Go. Rob Clark pointed out that Snapdragon 7c Gen 2 corresponds to SC7180 not SC7280. But none of the SC7180 device trees from https://github.com/torvalds/linux/tree/master/arch/arm64/boot/dts/qcom that I tried worked. They would enable the device to boot to the installer page, but keyboard would remain dysfunctional.

[leezu]

Got a copy of the ACPI Table DSDT.aml via SSDTTime https://dortania.github.io/Getting-Started-With-ACPI/Manual/dump.html#from-windows and the decompiled DSDT.dsl via iasl.exe https://dortania.github.io/Getting-Started-With-ACPI/Manual/compile.html#windows

Results.zip

[steev]

For that results.zip - the https://github.com/aarch64-laptops/build repo has different directories, it might be better as a pull request there instead of a zip file attached to an issue here - in the misc directory, you can see how it's set up

[merckhung]

So I am able to boot to the shell and use USB and UFS storage on Galaxy Go.
The way I approach it is to reuse the ACPI support, instead of heading off crafting your own Device Tree.

So the first thing to handle is to make SMMU driver recognize the Galaxy Go laptop's ACPI.
(Otherwise the laptop will reboot once the SMMU driver is loaded)

Add this line into arm-smmu-qcom.c file

{ "QCOM ", "QCOMEDK2", 0x7180, ACPI_SIG_IORT, equal, "QCOM SMMU" },

And the next step is to enable USB (DWC3) driver to recognize the USB via ACPI.
So, add this line into dwc3/core.c file

{ "QCOM0826", 0 },

With these two changes, I am able to boot to the shell, and backup the windows 11 from the UFS storage (/dev/sda) via USB hub and drive.

For the keyboard and mouse, they are on i2c-hid, I have no luck here. But I am still trying to enable the keyboard.
And I am able to use USB keyboard and USB Wi-Fi for now.

[merckhung]

I am able to boot the Home Screen of Ubuntu. But still need to get the keyboard and mouse working.

so the ACPI was used. Wi-Fi and Bluetooth do not seem to be PCI devices. So for now, I have to use USB Wi-Fi and keyboard/mouse.