1. Please describe the problem: I'm trying to install Fedora IOT on Renesas RZ/G2L platform, but got stuck before kernel starts: EFI stub: Decompressing Linux Kernel... EFI stub: EFI_RNG_PROTOCOL unavailable EFI stub: Using DTB from configuration table EFI stub: Exiting boot services... This will require enabling the Renesas RZ SOM. Some of the configuration needs updated are: For SoC support and UART console: CONFIG_ARCH_RENESAS=y CONFIG_SERIAL_SH_SCI=y CONFIG_ARCH_R8A774A1=y For SD and eMMC support: CONFIG_GPIO_RCAR=m CONFIG_MMC_SDHI=m For USB2 support: CONFIG_PHY_RCAR_GEN3_USB2=m CONFIG_RESET_RZG2L_USBPHY_CTRL=m For Enabling devices CONFIG_ARCH_R9A07G044=y #RZG2L CONFIG_ARCH_R9A07G054=y #RZV2L CONFIG_ARCH_R9A07G043=y #RZV2UL 2. What is the Version-Release number of the kernel: Fedora-IoT-ostree-aarch64-39-20231103.1.iso 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: a. Prepare "Fedora-IoT-ostree-aarch64-39-20231103.1.iso" in a USB stick b. Connect Tera-term c. Boot Renesas RZ/G2L device ( https://www.renesas.com/us/en/products/microcontrollers-microprocessors/rz-mpus/rzg2l-general-purpose-microprocessors-dual-core-arm-cortex-a55-12-ghz-cpus-and-single-core-arm-cortex-m33) with Fedora IOT efi boot d. The installation got stuck at EFI stub: Decompressing Linux Kernel... EFI stub: EFI_RNG_PROTOCOL unavailable EFI stub: Using DTB from configuration table EFI stub: Exiting boot services... This shows that the Renesas RZG2L serial driver is not enabled and the device ARCH not enabled as given in the list above 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``: Not Applicable 6. Are you running any modules that not shipped with directly Fedora's kernel?: Possibly yes, The Renesas SOM not enabled on this OS 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. The kernel is not booting yet, hence the only log we get is before the kernel starting. Reproducible: Always
I went ahead and flipped these on for rawhide and Fedora 6.7 kernels. They should appear in rawhide builds starting tomorrow, and Fedora 6.7.1 and newer kernel builds. Next week is Fedora 6.7 test week, and this will end up on stable Fedora releases shortly after. As I do not have these platforms to test, please feel free to let me know if everything is correct or if further changes are needed. Flipping these configs exposed about 75 more which were gated behind CONFIG_ARCH_RENESAS. I set them to their defaults.
Thanks Justin, for this quick update. I'm looking at rawhide builds in the below link, the last update was on 15/Jan. https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Everything/aarch64/iso/ I'll wait for the new build, then test on the RZ platform and will update you. Best Regards John
Hi Justin I tested the rawhide iso images with Renesas RZ platform, the kernel boot still not working. I looked at the configuration generated, they still missing some of Renesas RZ platform driver configuration as below: CONFIG_MII=y CONFIG_NET_VENDOR_RENESAS=y CONFIG_SH_ETH=y CONFIG_RAVB=y CONFIG_RENESAS_ETHER_SWITCH=y CONFIG_MICREL_PHY=y CONFIG_PHYLIB=y CONFIG_PHYLINK=y CONFIG_RENESAS_GEN4_PTP=y CONFIG_CAN_RCAR_CANFD=m CONFIG_I2C_RIIC=y CONFIG_SPI_RSPI=m CONFIG_RZG2L_THERMAL=y CONFIG_RENESAS_RZG2LWDT=y CONFIG_SND_SOC_RZ=m CONFIG_USB_EHCI_HCD_PLATFORM=y CONFIG_RENESAS_DMA=y CONFIG_RZ_DMAC=y CONFIG_RENESAS_OSTM=y CONFIG_RZG2L_ADC=m CONFIG_RESET_RZG2L_USBPHY_CTRL=y CONFIG_PHY_RCAR_GEN3_USB2=y CONFIG_USB_STORAGE=y CONFIG_MMC_SDHCI_PLTFM=y Please can you help them to add them in the arm64 Fedora list. Best Regards John
Hi John, > I tested the rawhide iso images with Renesas RZ platform, the kernel boot > still not working. I'll look into this for you. > CONFIG_MII=y > CONFIG_NET_VENDOR_RENESAS=y > CONFIG_SH_ETH=y > CONFIG_RAVB=y > CONFIG_RENESAS_ETHER_SWITCH=y > CONFIG_MICREL_PHY=y > CONFIG_PHYLIB=y > CONFIG_PHYLINK=y Any reason why the above (other than NET_VENDOR_RENESAS) need to be =y and not =m? > CONFIG_RENESAS_GEN4_PTP=y > CONFIG_CAN_RCAR_CANFD=m > CONFIG_I2C_RIIC=y > CONFIG_SPI_RSPI=m > CONFIG_RZG2L_THERMAL=y > CONFIG_RENESAS_RZG2LWDT=y > CONFIG_SND_SOC_RZ=m > CONFIG_USB_EHCI_HCD_PLATFORM=y > CONFIG_RENESAS_DMA=y > CONFIG_RZ_DMAC=y > CONFIG_RENESAS_OSTM=y > CONFIG_RZG2L_ADC=m > CONFIG_RESET_RZG2L_USBPHY_CTRL=y > CONFIG_PHY_RCAR_GEN3_USB2=y > > CONFIG_USB_STORAGE=y > CONFIG_MMC_SDHCI_PLTFM=y > > Please can you help them to add them in the arm64 Fedora list. I'll review but most of them should be =m, for example we do have USB_STORAGE=m and MMC_SDHCI_PLTFM=m already for aarch64.
Hi Peter > Any reason why the above (other than NET_VENDOR_RENESAS) need to be =y and not =m? We are installing Fedora from the USB and hence the USB drivers to be made as "y" So, the following are RZ devices USB & HW related configurations needs as "y" ** USB related ** CONFIG_RESET_RZG2L_USBPHY_CTRL=y CONFIG_PHY_RCAR_GEN3_USB2=y CONFIG_USB_EHCI_HCD_PLATFORM=y CONFIG_USB_STORAGE=y ** HW * CONFIG_I2C_RIIC=y CONFIG_RENESAS_RZG2LWDT=y CONFIG_RZG2L_THERMAL=y CONFIG_RENESAS_RZG2LWDT=y CONFIG_RENESAS_DMA=y The following may be changed to "m" I think: CONFIG_MMC_SDHCI_PLTFM=m CONFIG_RENESAS_OSTM=m CONFIG_RZG2L_THERMAL=m CONFIG_RENESAS_GEN4_PTP=m Best Regards John
Hi Peter Are these changes added to the rawhide iso images? Please update once the changes updated, I'll test them on Renesas RZ platform. Best Regards John
> Are these changes added to the rawhide iso images? > > Please update once the changes updated, I'll test them on Renesas RZ > platform. No, I haven't got to them yet, I will so shortly, and yes will update this with details.
(In reply to john.vincent.xa from comment #5) > Hi Peter > > > Any reason why the above (other than NET_VENDOR_RENESAS) need to be =y and not =m? > > We are installing Fedora from the USB and hence the USB drivers to be made > as "y" We should automatically pull those into the initrd so they should not need to be Y I'll do an update and once things have landed we can retest.
So these are already enabled for all platforms and they work fine as they get pulled in where needed during initrd so they're available for the root device (no change): CONFIG_USB_EHCI_HCD_PLATFORM=m CONFIG_USB_STORAGE=m CONFIG_MMC_SDHCI_PLTFM=m CONFIG_MII=m CONFIG_MICREL_PHY=m CONFIG_PHYLIB=y CONFIG_PHYLINK=m I've enabled these as =m CONFIG_RZG2L_THERMAL CONFIG_I2C_RIIC CONFIG_SPI_RSPI CONFIG_CAN_RCAR_CANFD CONFIG_RENESAS_RZG2LWDT CONFIG_SND_SOC_RZ CONFIG_USB_RZV2M_USB3DRD CONFIG_RESET_RZG2L_USBPHY_CTRL CONFIG_PHY_RCAR_GEN3_USB2 CONFIG_USB_XHCI_RCAR These as =y CONFIG_RENESAS_OSTM CONFIG_USB_XHCI_RZV2M For networkworking I have done: CONFIG_NET_VENDOR_RENESAS=y CONFIG_RAVB=m CONFIG_RENESAS_GEN4_PTP=m I didn't enable these as they look to be for older < r9 platforms, please confirm as I'm finding it hard to map RZ platforms to the R9/8/7 numbering. CONFIG_SH_ETH CONFIG_RENESAS_ETHER_SWITCH I also enabled these two SoCs: CONFIG_ARCH_R9A08G045 CONFIG_ARCH_R9A09G011
Hi Peter Thanks for the updates. Looks ok to me. When will this changes available in rawhide iso images to test them on RZ platform? Best Regards John
I'll update here as things progress through.
The commit is part of this PR: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2926 In particular: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2926/diffs?commit_id=26874890f15a16b5f4af622b1df43575b9de01b9
Looking through some of the DT compats it looks like we might need/want CONFIG_SERIAL_8250_EM too? Seems it's in RZ/V2M? John can you confirm whether that's needed or not, CONFIG_SERIAL_SH_SCI is enabled which seems to be the widely used console.
Also do you want to enable any of the media/camera/ISP pieces? CONFIG_VIDEO_RENESAS_VSP1 CONFIG_VIDEO_RENESAS_FCP CONFIG_VIDEO_RZG2L_CRU CONFIG_VIDEO_RZG2L_CSI2
Hi Peter The RZ V2M platform uses CONFIG_SERIAL_8250_EM hence please enable them. Please enable media/camera/ISP pieces as well. Thanks Best Regards John
So the kernel MR config changes have been merged, this should be part of the 6.8-rc4 build later today, so should be in images tomorrow. I'll confirm all of that when I know it to be the case.
Hi Peter I tested the "Fedora-Everything-netinst-aarch64-Rawhide-20240212.n.0.iso" on RZ platform, the Linux boot is working now after the configuration updates. Thank you. But the installation still not successful. I'll attach the teraterm full log. The last error I get is: Failed to activate service 'org.fedoraproject.Anaconda.Modules.Storage': timed out The USB and MMC are detected ok and hence I'm thinking it is not related to device tree: USB logs: " usb 2-1: New USB device found, idVendor=0781, idProduct=5581, bcdDevice= 1.00 usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 usb 2-1: Product: SanDisk 3.2Gen1 usb 2-1: Manufacturer: USB " MMC " mmcblk0: mmc0:0001 G1M15M 59.3 GiB [ 60.710170] mmcblk0: p1 p2 p3 mmcblk0: p1 p2 p3 [ 60.824515] mmcblk0boot0: mmc0:0001 G1M15M 31.5 MiB mmcblk0boot0: mmc0:0001 G1M15M 31.5 MiB [ 60.977029] mmcblk0boot1: mmc0:0001 G1M15M 31.5 MiB mmcblk0boot1: mmc0:0001 G1M15M 31.5 MiB [ 61.117214] mmcblk0rpmb: mmc0:0001 G1M15M 4.00 MiB, chardev (510:0) mmcblk0rpmb: mmc0:0001 G1M15M 4.00 MiB, chardev (510:0) " Can you suggest any issues related to the installer causing this issue. Best Regards John
Created attachment 2016629 [details] Fedora installation log on Renesas RZ platform
Can you try this raw image dd:ed out to a mSD card. https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Spins/aarch64/images/Fedora-Minimal-Rawhide-20240212.n.0.aarch64.raw.xz
So this one should have all the configs above so should be good: https://dl.fedoraproject.org/pub/fedora/linux/development/40/Spins/aarch64/images/Fedora-Minimal-40-20240213.n.1.aarch64.raw.xz
Hi Peter The boot is working ok, but the initial setup screen is not appearing to setup user details, time-zone etc. Hence I'm not able to login to the Fedora Linux server after the installation complete. Is it possible the initial setup is disable by default in the above installer images. Best Regards John
Created attachment 2016734 [details] Fedora installation log into Linux login screen Hi Peter The Linux boot is working ok now with the "Fedora-Minimal-Rawhide-20240214.n.1.aarch64.raw.xz" but the initial setup screen not displayed. It directly enter into linux login screen without user details, time zone etc setup I added the boot log for reference. Best Regards John
So the initial-setup is coming up but it appears to be happening after the login prompt which is weird. We have just branched off rawhide for F-40 so I am wondering if there's a general problem there. We should probably have this in a different bug as it's not really kernel but let me check a few bits first.
Hi Peter Is there any update on the Linux boot issue please. Shall I take the new rawhide image and test them on RZ platform? Thank you. Best Regards John
Hi John, Looking at the output again you attached on comment 23 it's failing to boot for some reason but I can't see why and I don't have the same device to debug with. How did you write out that image? Did you just use dd? You can use arm-image-installer (on Fedora you can "sudo dnf install arm-image-installer" or upstream [1]) to setup the image with a blank password and to show all the kernel output which may help to get to the bottom of it. arm-image-installer --image=Fedora-Minimal-Rawhide-20240214.n.1.aarch64.raw.xz --norootpass --target=none --resizefs --showboot --media=/dev/XXX From there you should be able to login and debug what's going on in the kernel in the boot process. I suspect we're missing some dependency for the storage you're using. What media is it? Unfortunately while I can assist a little here without a device I'm going to have to depend on you a bit to get to the bottom of what we're missing here. [1] https://pagure.io/arm-image-installer/
Hi Peter The newer installer menu is working ok now. Thanks. 1. The installer used is: https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Spins/aarch64/images/Fedora-Minimal-Rawhide-20240220.n.0.aarch64.raw.xz This is able to boot directly by settings the following: ============================================= 1) [x] Language settings 2) [x] Time settings (English (United Kingdom)) (Europe/London timezone) 3) [x] Network configuration 4) [x] Root password (Unknown) (Root password is set) 5) [x] User creation (Administrator john will be created) ============================================= This version of Fedora installation works fine. Thank you. However, this installation does not install into the eMMC. 2. The following installer I tried, it fails because the "source installer" not able to set. https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Server/aarch64/iso/Fedora-Server-dvd-aarch64-Rawhide-20240220.n.0.iso https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Everything/aarch64/iso/Fedora-Everything-netinst-aarch64-Rawhide-20240220.n.0.iso https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Everything/aarch64/iso/Fedora-Everything-netinst-aarch64-Rawhide-20240220.n.0.iso The installation menu below Installation 1) [x] Language settings 2) [x] Time settings (English (United Kingdom)) (America/New_York timezone) 3) [!] Installation source 4) [!] Software selection (Error setting up repositories) (Installation source not set up) 5) [x] Installation Destination 6) [x] Network configuration (Automatic partitioning (Unknown) selected) 7) [x] Root password 8) [x] User creation (Root password is set) (Administrator john will be created) I'm not able to select 3) Installation source because it does not find the source iso file. I don't understand why it requires "Installation source" , I was expecting the installations source are present in the image itself. Do you know any installer works without selecting the "installation source" or how to pass this file? Thank you. Best Regards John
The network install images will require a NIC with appropriate IP/DHCP to be configured in order to find the install repo, and I can see from the menu there, that isn't the case. The server image, should include all the required packages to install so that is a bit of a mystery as you have gotten far enough into the install that presumably the USB mass storage/etc device you booted from is working. In that case there should be some data in the /tmp/anaconda.log and other files in /tmp telling you why it can't find the package repo. using 'lsblk' and friends should show the HW device with the ISO just to verify that the kernel modules/etc are loaded. Usually item 3 just says "Local ISO" or something to that effect when the ISO based repo is detected. Also, probably worth adding a section to https://fedoraproject.org/w/index.php?title=Architectures%2FARM&type=revision&diff=694655&oldid=635876#Supported_Hardware_and_Devices describing your SoC/Board.
> I don't understand why it requires "Installation source" , I was expecting > the installations source are present in the image itself. The everything netinst is a small installer designed to pull off the network, you need to have a working network for that one. I suppose the question is why the networking isn't coming up there. > Do you know any installer works without selecting the "installation source" > or how to pass this file? Thank you. The DVD iso will have everything for a standard minimal or Fedora Server install: https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Server/aarch64/iso/
Hi Peter I'm able to install Fedora OS in RZ platforms (iso image used https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Server/aarch64/iso/Fedora-Server-dvd-aarch64-Rawhide-20240229.n.0.iso).Thaks for your help. Following are few issues / workaround done: 1. The source selection fails saying no iso is present in the ISO disk. If I configuration destination first, source is automatically selected. 2. I connected the board to the network 3. An error occurred during "installing boot loader" to set new efi boot target. "The following error occurred while installing the boot loader. The system will not be bootable. Would you like to ignore this and continue with installation? Failed to set new efi boot target. This is most likely a kernel or firmware bug. Please respond 'yes' or 'no': yes " But the OS is still bootable from emmc after the installation completes. > Also, probably worth adding a section to https://fedoraproject.org/w/index.php?title=Architectures%2FARM&type=revision&diff=694655&oldid=635876#Supported_Hardware_and_Devices describing your SoC/Board. Are we able to edit this page for adding our SoC/Board? Best Regards John
> 1. The source selection fails saying no iso is present in the ISO disk. If I > configuration destination first, source is automatically selected. That sounds like an anaconda installer bug. > 2. I connected the board to the network > 3. An error occurred during "installing boot loader" to set new efi boot > target. > "The following error occurred while installing the boot loader. The system > will > not be bootable. Would you like to ignore this and continue with > installation? > Failed to set new efi boot target. This is most likely a kernel or firmware > bug. > Please respond 'yes' or 'no': yes > " > But the OS is still bootable from emmc after the installation completes. That's because the firmware doesn't support EFI set variable, the reason it boots is because it's using the UEFI fallback boot method. > > Also, probably worth adding a section to https://fedoraproject.org/w/index.php?title=Architectures%2FARM&type=revision&diff=694655&oldid=635876#Supported_Hardware_and_Devices describing your SoC/Board. > Are we able to edit this page for adding our SoC/Board? You need a Fedora FAS account, the CLA signed and I believe membership of one other group. I'm going to close this bug out as we now have the kernel support in place, we can deal with the rest of the details via email or chat or other bug reports. Thanks for your assistance here.