![]() Owner: Igor Raits, Björn Esser, Neal Gompaĭisable rvice on first run if no dmraid sets are found.Additionally, %cmake_build, %cmake_install and %ctest macro will be created (and backported to the older supported Fedora releases) to perform various operations that are commonly used with CMake in a backend-agnostic (Makefiles, Ninja, etc.) way. 2.16 Automatic RPM dependencies on Python Extras.2.13 No more automagic Python bytecompilation (phase 3).repo files for modular repositories from a separate package 2.7 GHC 8.8 and Haskell Stackage LTS 16.2.5 DXVK as default wined3d backend on VK capable hardware.2.2 Default animated background for Fedora Workstation.2 Fedora 33 Accepted Self-Contained Changes.1.32 Changes/LTO by default for package builds.1.29 Use %make_build and %make_install macros.1.23 Removal of the glibc-headers package.1.22 Remove device-mapper-multipath from the Fedora workstation livecd.1.18 NetworkManager keyfile instead of ifcfg-rh.1.14 java-11-openjdk as system JDK in F33.1.9 Changes/MinGW environment and toolchain update.1.6 Disable rvice on first run if no dmraid sets are found.1.4 Cleanup GNOME Hidden Boot Menu Integration.1.3 Make btrfs the default file system for desktop variants.1.1 Aarch64 Pointer Authentication & Branch Target Enablement.1 Fedora 33 Accepted System-Wide Changes.I performed a `dnf upgrade uboot-tools` and then ran `update-uboot` to update my SD card. This can cause time to jump forward and worse go backwards which can mess up timeout and other code.Ĭode was added to both U-Boot and the Linux kernel to detect this and ignore these erroneous values.įor U-Boot you need 28 Unfortunately the "Intermittent Boot Errors for Pine 64" didn't show up in any of my Google searches.Īpparently the Allwinner A64 ARM chip has a timer issue where the last 11 bits of the timer value will erroneously be either all zero or one bits. The bug in U-Boot caused an erroneous `hd0` error to occur while GRUB was loading Fedora.Īfter trying several SD cards and doing research on how U-Boot and Grub work, I found that this was a KNOWN ISSUE with Fedora 28. The bad news was that there was a bug in the U-Boot used that caused Fedora to only occasionally complete the boot. I confirmed that the `ln` link to the DTB file was no longer needed. Sudo fedora-arm-image-installer -image=Fedora-Workstation-28-1.1. -target=pine64_plus -media=/dev/mmcblk0 # Install downloaded Fedora 28 Workstation image to SD card Sudo dnf install uboot-images-armv8 fedora-arm-installer # Install the fedora-arm-image-installer and Fedora uboot-images-armv8 package Determine the device name to which you'll be writing. Remember: This is pre-release software. Eventually you'll end up with a file named similar to this (the date will be different):įedora-Minimal-27-20171026.n.0. Make sure there's a green check mark by the item you intend to download, as that indicates that it was successfully built that day. I'd recommend one of either the Minimal or Server builds: *) Obtain one of the daily Fedora builds from Koji. ![]() *) Acquire a UART cable for using the serial console. Here are the steps as I best understand them. From there, once ethernet is established, you can SSH to the board. On first boot, you can create a user, set the timezone, etc. There's no graphical support yet, so you'll only be able to watch the OS boot on the serial console. ![]() Note, Fedora's philosophy eschews proprietary software as much as possible, so if upstream support isn't yet available, it won't be in Fedora. If you are interested in running a pre-release version of Fedora 27 on your Pine64, here's what you need to do at this point in its development. Note to admins here, it may be time to add a Fedora Sub Forum on this site. Official Fedora support is nearing the light of day from the good folks on the Fedora ARM team.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |