[Bug 1203558] New: openSUSE support for Renesas RZ/G2M
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1203558 Bug ID: 1203558 Summary: openSUSE support for Renesas RZ/G2M Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers@suse.de Reporter: duy.hua-duc@banvien.com.vn QA Contact: jsrain@suse.com Found By: --- Blocker: --- I need to install openSUSE to our chip but I realize that the openSUSE-Leap-15.4-DVD-aarch64-Build243.2-Media.iso does not support our GPU driver so I can't install it. + Document about our chip: https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=&cad=rja&uact=8&ved=2ahUKEwjetPb6iKD6AhVrqFYBHcmdAUkQFnoECA4QAQ&url=https%3A%2F%2Fwww.renesas.com%2Fus%2Fen%2Fproducts%2Fmicrocontrollers-microprocessors%2Frz-mpus%2Frzg2m-ultra-high-performance-microprocessors-arm-cortex-a57-and-arm-cortex-a53-cpus-3d-graphics-and-4k&usg=AOvVaw3Ymgg6zOhVGXdomup7g4Ef + This is our GPU driver: https://github.com/renesas-rz/rz_linux-cip/tree/rz-5.10-cip1-rt1/drivers/gpu... -- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1203558 http://bugzilla.opensuse.org/show_bug.cgi?id=1203558#c4 --- Comment #4 from Duy Hua <duy.hua-duc@banvien.com.vn> --- As Senior Engineer of Renesas, you need to enable Rcar-du as a module and the required module will be inserted after initrd loaded. CONFIG_DRM_RCAR_DU=m CONFIG_DRM_RCAR_DW_HDMI=m CONFIG_DRM_RCAR_MIPI_DSI=m -- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1203558 http://bugzilla.opensuse.org/show_bug.cgi?id=1203558#c5 Dirk Mueller <dmueller@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(duy.hua-duc@banvi | |en.com.vn) | --- Comment #5 from Dirk Mueller <dmueller@suse.com> --- Thank you. I have added that into the pending tumbleweed update as enablement for arm64. -- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1203558 Dirk Mueller <dmueller@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |IN_PROGRESS -- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1203558 http://bugzilla.opensuse.org/show_bug.cgi?id=1203558#c6 --- Comment #6 from Duy Hua <duy.hua-duc@banvien.com.vn> --- Excuse me, Did you know when we have an OS distro for a test? -- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1203558 http://bugzilla.opensuse.org/show_bug.cgi?id=1203558#c7 --- Comment #7 from Dirk Mueller <dmueller@suse.com> --- (In reply to Duy Hua from comment #6)
Excuse me, Did you know when we have an OS distro for a test?
my changes for tumbleweed are still under review. its a matter of days, hopefully. -- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1203558 http://bugzilla.opensuse.org/show_bug.cgi?id=1203558#c9 Duy Hua <duy.hua-duc@banvien.com.vn> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED |--- --- Comment #9 from Duy Hua <duy.hua-duc@banvien.com.vn> --- I already download "openSUSE-Tumbleweed-DVD-aarch64-Snapshot20221001-Media.iso" and burn it to my USB. After that, I boot the image with this command in u-boot. => usb start;fatload usb 0:1 50000000 EFI/BOOT/BOOTAA64.EFI;bootefi 50000000 And serial terminal logs out: Loading kernel ... Loading initial ramdisk ... EFI stub: Booting Linux Kernel... EFI stub: EFI_RNG_PROTOCOL unavailable EFI stub: Using DTB from configuration table EFI stub: Exiting boot services... -- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1203558 http://bugzilla.opensuse.org/show_bug.cgi?id=1203558#c10 Guillaume GARDET <guillaume.gardet@arm.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |guillaume.gardet@arm.com --- Comment #10 from Guillaume GARDET <guillaume.gardet@arm.com> --- This will be part of the update to kernel 6.0 - https://build.opensuse.org/request/show/1007640 So, you still need to wait a bit. -- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1203558 http://bugzilla.opensuse.org/show_bug.cgi?id=1203558#c11 --- Comment #11 from Duy Hua <duy.hua-duc@banvien.com.vn> --- I saw that request was approved but openSUSE-Tumbleweed-DVD-aarch64-Snapshot20221015-Media.iso still does not work with our chip. Please support me check and respond for me. Thank you. -- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1203558 http://bugzilla.opensuse.org/show_bug.cgi?id=1203558#c14 --- Comment #14 from Duy Hua <duy.hua-duc@banvien.com.vn> --- It logs like the previous iso Loading kernel ... Loading initial ramdisk ... EFI stub: Booting Linux Kernel... EFI stub: EFI_RNG_PROTOCOL unavailable EFI stub: Using DTB from configuration table EFI stub: Exiting boot services... -- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1203558 http://bugzilla.opensuse.org/show_bug.cgi?id=1203558#c15 --- Comment #15 from Matthias Brugger <mbrugger@suse.com> --- (In reply to Duy Hua from comment #14)
It logs like the previous iso
Loading kernel ... Loading initial ramdisk ... EFI stub: Booting Linux Kernel... EFI stub: EFI_RNG_PROTOCOL unavailable EFI stub: Using DTB from configuration table EFI stub: Exiting boot services...
Can you try to pass 'earlycon' as boot parameter to the kernel. If that does not help, then please provide the devicetree used for booting the device. -- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1203558 http://bugzilla.opensuse.org/show_bug.cgi?id=1203558#c16 --- Comment #16 from Duy Hua <duy.hua-duc@banvien.com.vn> --- Here is Renensas dtb source:
https://github.com/renesas-rz/rz_linux-cip/tree/rzg2-cip74/arch/arm64/boot/d...
-- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1203558 http://bugzilla.opensuse.org/show_bug.cgi?id=1203558#c17 --- Comment #17 from Duy Hua <duy.hua-duc@banvien.com.vn> --- At first, we need to run board G2Mv3.0 so we have "r8a774a3-hihope-rzg2m-ex-idk-1110wr.dts" config for this board. -- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1203558 http://bugzilla.opensuse.org/show_bug.cgi?id=1203558#c27 --- Comment #27 from Duy Hua <duy.hua-duc@banvien.com.vn> --- (In reply to Matthias Brugger from comment #26)
I realized that we are missing config options for the serial console driver. I queued the changes for tumbleweed. This should allow you to use earlycon to see what happens on the board. As always it will take some time to be published though. If you want I can provide you with a test kernel that you can use to test in advance.
yes, please! -- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1203558 http://bugzilla.opensuse.org/show_bug.cgi?id=1203558#c28 --- Comment #28 from Matthias Brugger <mbrugger@suse.com> --- (In reply to Duy Hua from comment #27)
(In reply to Matthias Brugger from comment #26)
I realized that we are missing config options for the serial console driver. I queued the changes for tumbleweed. This should allow you to use earlycon to see what happens on the board. As always it will take some time to be published though. If you want I can provide you with a test kernel that you can use to test in advance.
yes, please!
You can download kernel-default-6.*.rpm package from the kernel of the day (KOT) repository: https://download.opensuse.org/repositories/Kernel:/stable/ARM/aarch64/ If you want to update the kernel in your ISO image [1] you can update that with the following command: sudo mksusecd --create test.iso --kernel=path/to/your/kernel-default*.rpm -- path/to/your/openSUSE-Tumbleweed-DVD-aarch64-Current.iso Hope that helps. [1] https://download.opensuse.org/ports/aarch64/tumbleweed/iso/openSUSE-Tumblewe... -- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1203558 http://bugzilla.opensuse.org/show_bug.cgi?id=1203558#c29 --- Comment #29 from Duy Hua <duy.hua-duc@banvien.com.vn> --- Created attachment 862849 --> http://bugzilla.opensuse.org/attachment.cgi?id=862849&action=edit log boot openSUSE tumbleweed at board RZ/G2Mv3 In "openSUSE-Tumbleweed-DVD-aarch64-Snapshot20221108-Media.iso" our board can boot and install but still has problems while installing. You can see the log file for more detail. -- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1203558 http://bugzilla.opensuse.org/show_bug.cgi?id=1203558#c30 Matthias Brugger <mbrugger@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(duy.hua-duc@banvi | |en.com.vn) --- Comment #30 from Matthias Brugger <mbrugger@suse.com> --- (In reply to Duy Hua from comment #29)
Created attachment 862849 [details] log boot openSUSE tumbleweed at board RZ/G2Mv3
In "openSUSE-Tumbleweed-DVD-aarch64-Snapshot20221108-Media.iso" our board can boot and install but still has problems while installing. You can see the log file for more detail.
At the first glance this looks like a memory issue which most probably is provoked by the boot firmware and not the kernel. Are you able to boot a plain upstream kernel? -- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1203558 http://bugzilla.opensuse.org/show_bug.cgi?id=1203558#c31 --- Comment #31 from Duy Hua <duy.hua-duc@banvien.com.vn> --- (In reply to Matthias Brugger from comment #30)
At the first glance this looks like a memory issue which most probably is provoked by the boot firmware and not the kernel. Are you able to boot a plain upstream kernel?
We will try to test with kernel 5.10 same as current our kernel. -- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1203558 http://bugzilla.opensuse.org/show_bug.cgi?id=1203558#c32 --- Comment #32 from Matthias Brugger <mbrugger@suse.com> --- (In reply to Duy Hua from comment #31)
(In reply to Matthias Brugger from comment #30)
At the first glance this looks like a memory issue which most probably is provoked by the boot firmware and not the kernel. Are you able to boot a plain upstream kernel?
We will try to test with kernel 5.10 same as current our kernel.
So your downstream 5.10 kernel boots without any memory issues? -- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1203558 http://bugzilla.opensuse.org/show_bug.cgi?id=1203558#c33 --- Comment #33 from Duy Hua <duy.hua-duc@banvien.com.vn> --- Created attachment 862940 --> http://bugzilla.opensuse.org/attachment.cgi?id=862940&action=edit create ISO test -- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1203558 http://bugzilla.opensuse.org/show_bug.cgi?id=1203558#c34 Duy Hua <duy.hua-duc@banvien.com.vn> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #862940|0 |1 is obsolete| | --- Comment #34 from Duy Hua <duy.hua-duc@banvien.com.vn> --- Created attachment 862941 --> http://bugzilla.opensuse.org/attachment.cgi?id=862941&action=edit log boot ISO test -- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1203558 http://bugzilla.opensuse.org/show_bug.cgi?id=1203558#c35 --- Comment #35 from Duy Hua <duy.hua-duc@banvien.com.vn> --- (In reply to Duy Hua from comment #34)
Created attachment 862941 [details] log boot ISO test
- I build follow this link: https://tutorialforlinux.com/2021/01/05/step-by-step-build-kernel-opensuse-e... - The ISO kernel panic happens, this I miss something? -- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1203558 http://bugzilla.opensuse.org/show_bug.cgi?id=1203558#c36 Matthias Brugger <mbrugger@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(duy.hua-duc@banvi | |en.com.vn) | --- Comment #36 from Matthias Brugger <mbrugger@suse.com> --- (In reply to Duy Hua from comment #35)
(In reply to Duy Hua from comment #34)
Created attachment 862941 [details] log boot ISO test
- I build follow this link: https://tutorialforlinux.com/2021/01/05/step-by-step-build-kernel-opensuse- easy-guide/ - The ISO kernel panic happens, this I miss something?
Yes it didn't found the init program to start userspace. See the last line: No working init found. Try passing init= option to kernel. See Linux Documentation/admin-guide/init.rst for guidance. -- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1203558 http://bugzilla.opensuse.org/show_bug.cgi?id=1203558#c37 --- Comment #37 from Duy Hua <duy.hua-duc@banvien.com.vn> --- I had tried this bootargs below:
setenv bootargs 'console=ttySC0,115200n8,earlyprintk=ttySC0,rootwait,init=/initrd' setenv bootargs 'console=ttySC0,115200n8,earlyprintk=ttySC0,rootwait,init=/sbin/init' setenv bootargs 'console=ttySC0,115200n8,earlyprintk=ttySC0,rootwait,init=/bin/init'
And all of this meets kernel panic. -- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1203558 http://bugzilla.opensuse.org/show_bug.cgi?id=1203558#c38 --- Comment #38 from Duy Hua <duy.hua-duc@banvien.com.vn> --- - This we have any package kernel-default.rpm Tumbleweed for aarch64. I can't find out any package kernel 5, and kernel-default of Leap does not support our chip. - I seek on http://rpmfind.net/linux/rpm2html/search.php?query=kernel-default&submit=Search+...&system=&arch=aarch64 -- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1203558 http://bugzilla.opensuse.org/show_bug.cgi?id=1203558#c40 --- Comment #40 from Matthias Brugger <mbrugger@suse.com> --- (In reply to Duy Hua from comment #37)
I had tried this bootargs below:
setenv bootargs 'console=ttySC0,115200n8,earlyprintk=ttySC0,rootwait,init=/initrd' setenv bootargs 'console=ttySC0,115200n8,earlyprintk=ttySC0,rootwait,init=/sbin/init' setenv bootargs 'console=ttySC0,115200n8,earlyprintk=ttySC0,rootwait,init=/bin/init'
And all of this meets kernel panic.
What is the init binary on your initrd? It seems you use some modified initrd, correct? -- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1203558 http://bugzilla.opensuse.org/show_bug.cgi?id=1203558#c41 --- Comment #41 from Duy Hua <duy.hua-duc@banvien.com.vn> --- (In reply to Matthias Brugger from comment #40)
What is the init binary on your initrd? It seems you use some modified initrd, correct?
Yes, I already rebuild initrd too, here is my command:
sudo mksusecd --rebuild-initrd --create test.iso --kernel /usr/src/packages/RPMS/aarch64/kernel-5.10.154-1.aarch64.rpm -- openSUSE-Tumbleweed-DVD-aarch64-Snapshot20221112-Media.iso
-- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1203558 http://bugzilla.opensuse.org/show_bug.cgi?id=1203558#c43 --- Comment #43 from Duy Hua <duy.hua-duc@banvien.com.vn> --- Yes, I will check and update the latest source build u-boot. By the way, you can help me update distro Leap for support RZ/G2M. I saw that kernel of Leap 15.4 is 5.14.21 maybe it can run well with our chip. I already try to modify the kernel of Leap 15.4 and it can boot but the prosses is stuck in udev. -- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1203558 http://bugzilla.opensuse.org/show_bug.cgi?id=1203558#c44 --- Comment #44 from Duy Hua <duy.hua-duc@banvien.com.vn> --- Created attachment 863086 --> http://bugzilla.opensuse.org/attachment.cgi?id=863086&action=edit log boot openSUSE Leap 15.4 at board RZ/G2Mv3 -- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1203558 http://bugzilla.opensuse.org/show_bug.cgi?id=1203558#c46 Huynh Thanh Hung <huynhthanhhung13@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |huynhthanhhung13@gmail.com --- Comment #46 from Huynh Thanh Hung <huynhthanhhung13@gmail.com> --- Hello, I'm from Renesas Electronics. The memory issue is gone without modification, I don't know why. About latest result of Duy Hua. He used the ext4 partition and copy the live image content into that, then the initrd can not run the "loop" module with the right "root". So actually, the installer process did not reach to "memory issue" section. It failed before that. Anyway, thank you so much for helping us enable support for Renesas platform. Best Regards, Hung Huynh -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@suse.com