Bugzilla – Bug 1203558
openSUSE support for Renesas RZ/G2M
Last modified: 2023-07-31 22:24:45 UTC
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/drm/rcar-du
So this is not at all about the installation, but about the kernel. Reassigning.
Do you know what the upstream status of the GPU support ist. On a first quick glance it seems quite OK, maybe we are just missing some config options.
Since neither SUSE nor anyone in the openSUSE community at the time had any Renesas boards to test on, Dirk disabled virtually all Renesas platforms years ago when some driver failed to build (back for armv7hl). If you can provide us with a list of Kconfig options to enable, we can look into enabling them in Tumbleweed for you to test. Since Leap is reusing the SLE kernel, enabling new platforms in Leap 15.5 / 15.4 would be a business discussion to be had with SUSE (SLE feature requests).
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
Thank you. I have added that into the pending tumbleweed update as enablement for arm64.
Excuse me, Did you know when we have an OS distro for a test?
(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.
The feature was enabled on TW kernel, so let's close. Please reopen if the same problem persists even with the kernel including the fix. Thanks.
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...
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.
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.
Matthias, could you please help with troubleshooting?
If your board has a serial port it might be useful to use the serial console to get the kernel messages when the screen is not working.
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...
(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.
Here is Renensas dtb source: > https://github.com/renesas-rz/rz_linux-cip/tree/rzg2-cip74/arch/arm64/boot/dts/renesas
At first, we need to run board G2Mv3.0 so we have "r8a774a3-hihope-rzg2m-ex-idk-1110wr.dts" config for this board.
(In reply to Duy Hua from comment #17) > At first, we need to run board G2Mv3.0 so we have > "r8a774a3-hihope-rzg2m-ex-idk-1110wr.dts" config for this board. 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.
(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!
(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-Tumbleweed-DVD-aarch64-Current.iso
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.
(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?
(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.
(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?
Created attachment 862940 [details] create ISO test
Created attachment 862941 [details] log boot ISO test
(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?
(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.
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.
- 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
(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?
(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
(In reply to Duy Hua from comment #41) > (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 I'd say it's better to stay with openSUSE Tumbleweed. I suppose your own v5.10 kernel has a lot of downstream patches. The errors you mentioned in comment #29 look like there is a problem with the memory. My first bet would be that somehow the boot firmware didn't initialize the memory controller correctly. Can you check with the board/SoC vendor if there is a newer boot FW to install?
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.
Created attachment 863086 [details] log boot openSUSE Leap 15.4 at board RZ/G2Mv3
(In reply to Duy Hua from comment #44) > Created attachment 863086 [details] > log boot openSUSE Leap 15.4 at board RZ/G2Mv3 It seems that you are not using the openSUSE Leap kernel but your own kernel. We don't support that kind of setup. In any case it looks like with the new U-Boot the random memory errors are gone. So I'll close this issue as fixed. If you have any other issue, please open a new bug.
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