Bug 2077513

Summary:	Fedora 36 Beta ARM aarch64 installer crashes on boot on Samsung Galaxy Book Go
Product:	[Fedora] Fedora	Reporter:	Leonard Lausen <leonard>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	36	CC:	acaringi, adscvr, airlied, alciregi, bskeggs, hdegoede, hpa, jarodwilson, jforbes, jglisse, jonathan, josef, kernel-maint, lgoncalv, linville, masami256, mchehab, pbrobinson, ptalbert, steved
Target Milestone:	---
Target Release:	---
Hardware:	aarch64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-09-15 14:00:30 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	245418

Description Leonard Lausen 2022-04-21 13:36:01 UTC

1. Please describe the problem:
Fedora 36 Beta ARM aarch64 installer crashes on boot on Samsung Galaxy Book Go.
Booting up the laptop with the USB stick and brings up GRUB. GRUB loads, appears to function (navigating the menu works, pressing ‘c’ drops to a command prompt, etc), I can select the "Test this media & start Fedora-Workstation-Live 36" option, press Enter, the screen clears and shows a cursor, and a few seconds later the laptop reboots. It never really gets much past GRUB. The fact that GRUB loads and runs says that the ARM-based CPU is executing instructions.

The same issue applies with Fedora 35.

In contrast to the experience with Fedora, booting from Linaro's aarch64-laptops/debian-cdimage works fine (https://github.com/aarch64-laptops/debian-cdimage/releases/tag/v0.4)

This issue has previously been reported at https://ask.fedoraproject.org/t/how-to-install-fedora-on-a-samsung-galaxy-book-go/19390

2. What is the Version-Release number of the kernel:
Version included in both Fedora 35 Installer and Fedora 36 Installer.

3. Did it work previously in Fedora? If so, what kernel version did the issue
*first* appear? Old kernels are available for download at
https://koji.fedoraproject.org/koji/packageinfo?packageID=8 :
No

4. Can you reproduce this issue? If so, please provide the steps to reproduce
the issue below:

- Obtain Samsung Galaxy Book Go Laptop ($299 at https://smile.amazon.com/dp/B09DDCDKZZ/)
- On another machine, copy the image to an USB drive: sudo dd if=Fedora-Workstation-Live-aarch64-36_Beta-1.4.iso of=/dev/sdX status=progress
- Boot the Samsung Galaxy Book Go Laptop, pressing F10 and enter the BIOS Setup. Disable Secure Boot and save the settings.
- Boot the Samsung Galaxy Book Go Laptop, pressing F10 and boot from USB
Select "Start Fedora-Workstation-Live 36"
- The laptop reboots after a few seconds

5. Does this problem occur with the latest Rawhide kernel? To install the
Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
``sudo dnf update --enablerepo=rawhide kernel``:
N/A

6. Are you running any modules that not shipped with directly Fedora's kernel?:
No

7. Please attach the kernel logs. You can get the complete kernel log
for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
issue occurred on a previous boot, use the journalctl ``-b`` flag.

Unavailable

Comment 1 Justin M. Forbes 2022-04-21 14:33:33 UTC

The beta installer is rather behind on kernel, can you give a more recent compose a try?

Comment 2 Leonard Lausen 2022-04-21 15:15:54 UTC

Thank you Justin. I verified the issue persists with Fedora-Everything-netinst-aarch64-36-20220421.n.0.iso and Fedora-Everything-netinst-aarch64-Rawhide-20220421.n.0.iso. Are those the images you wanted me to try?

Comment 3 Justin M. Forbes 2022-04-21 15:28:53 UTC

Those would be the ones, I appreciate it.

Comment 4 Peter Robinson 2022-09-13 12:25:41 UTC

I'd be surprised if this worked, what sort of firmware does the Samsung chromebook use?

Comment 5 Leonard Lausen 2022-09-15 13:14:27 UTC

You're right. The problem is that there are no device tree files for this Galaxy Book Go. Note that it's not a Chromebook but a Windows ARM Laptop. Windows relies on ACPI not device trees, but Linux ACPI support for ARM is essentially non-existent. Thus someone would need to reverse engineer a device tree file for the Galaxy Book Go. ARM Chromebooks in contrast have device tree files upstream, for example https://github.com/torvalds/linux/blob/master/arch/arm64/boot/dts/qcom/sc7180-trogdor.dtsi In fact the Galaxy Book Go is very similar to the Trogdor Chromebook, so one could start out with the linked dtsi. Nevertheless, it's probably a better choice to buy a Chromebook and install Fedora on there. Some prebuilt images are available at https://github.com/hexdump0815/imagebuilder/blob/main/systems/chromebook_trogdor/readme.md I recommend to close this issue and instead consider adding support for ARM Chromebooks to the Fedora installer.

Comment 6 Peter Robinson 2022-09-15 14:00:30 UTC

> Windows relies on ACPI not device trees, but Linux ACPI support for ARM is
> essentially non-existent. Thus someone would need to reverse engineer a

The Linux ACPI support for aarch64 is 100% complete, it's required for ServerReady systems, the ACPI support for QCom based devices is a different matter entirely, they're not the same thing.