I figured it out by removing everything from the RPI4b, laying the bare board on the table top, and booting it up. It’s the fan shim, the dang Pimoroni Fan Shim (1)! It’s using GPIO serial pins (14,15). Cannot remember what that was and do not have a spare sd card to test with right now. I do seem to remember that something about the writing to the sd may have had an error in transferring one file over that had to be done manually. # For this functionality follow the following guide: # To use this on Fedora you need to use firmware provided device tree, not kernel # Each dtoverlay line is an individual HAT/overlay, multiple lines allowed # Stop the RPi turning on HDMI monitors on reboot # Automatically load overlays for detected DSI displays # Automatically load overlays for detected cameras # You need to set this to at least 80 for using the camera # but this isn't used by mainline VC4 driver so reduce to lowest supported value # We need this to be 32Mb to support VCHI services and drivers which use them # Early boot delay in the hope monitors are initialised enough to provide EDID # Terrible hack to work around U-Boot issues on most devices # u-boot will auto detect serial and pass corrent options to kernel if enabled # Serial console is ttyS0 on RPi3 and ttyAMA0 on all other variants # Only enable UART if you're going to use it as it has speed implications # Default Fedora configs for all Raspberry Pi Revisions # 4K display support - RPi4 only, only one port possible (This is at the root of what would be the efi partition if the Pi were to boot using efi) # Options you can adjust for all Raspberry Pi Revisions Mine, The file at /boot/efi/config.txt reads I do not recall that I changed anything in this, but will post the content just in case. The config file was also something I seem to remember may have been involved. On the other thread I linked it seemed that the only significant difference between my Pi and his was the Pi firmware version. What else can I try? Is there a way to make the u-boot process more verbose, or write the output to a log file? I’m trying that right now with a fresh write of Fedora-KDE-37-1.7. to an SDcard using: sudo arm-image-installer -target=rpi4 -image=Fedora-KDE-37-1.7. -media=/dev/sdc -showboot -resizefsĪnd… after letting it run for 15 minutes and a reboot I’m unhappy to say I see the exactly the same thing, a u-boot prompt with a flood of “eth0:” I have left it run like that for as long as 15 minutes once, but I’ll have to say I don’t believe I tried cycling the power to reboot it. They all gave the same result shown in the screen shot above. I thought I had also tried Fedora-Workstation-37.1., but I guess not. Jeff, thanks for your reply! I’ve tried these Fedora images:įedora-KDE-Rawhide-20230118.n.0.įedora-Workstation-Rawhide-20230118.n.0. This thread is about the last time I tried it. I do use a logitech mouse (MX Ergo trackball) and keyboard (K350) with the unifying receiver and do not have a touchpad. After the setup was complete it boots though it still remains with the black screen until gdm starts up and the login screen appears. It then gave me a black screen for an extended period but finally came up with the normal first boot config screen and I was able to do the setup. (don’t remember exactly what I saw)Īfter waiting about 10 minutes I powered the pi off then back on. Sudo arm-image-installer -image=Fedora-Workstation-37-1.7. -media=/dev/sdf -resizefs -target=rpi4 The command line to write it to the card was I used the one from fedora Fedora-Workstation-37-1.7. and placed it on the sd card with the arm-image-installer. What exact file name did you download and place on the sd card? Altium will never give your email address to any third party.I have used fedora 37 on an RPi4B 8GB with no problems. You also acknowledge that by signing up to use CircuitMaker, you agree that Altium can send you occasional emails with news about CircuitMaker and our partner service, components, and reference designs. Please refer to the exact terms of the GPL and LGPL at (Free Software Foundation) or (Open Source Initiative) regarding your rights under said licenses. By checking the “I agree” line below, you acknowledge that any project you post, including any design files and source code, will be public information and may be subject to one or more open source software or hardware licenses. The projects created using CircuitMaker may include certain open source software or hardware designs originated from third parties that is subject to the GNU General Public License (GPL), GNU Library/Lesser General Public License (LGPL) and different and/or additional copyright licenses, disclaimers, and notices.
0 Comments
Leave a Reply. |