arm February 2018

arm@lists.fedoraproject.org

16 participants
18 discussions

what do i have to do to enable spi on fedora 27 on a raspberry pi
by adpdyj+4aw13di0ccx1w＠sharklasers.com 10 Apr '18

10 Apr '18

to quote the fedoraproject wiki on the raspberry pi: Are Device Tree Overlays supported? There's basic support for overlays in u-boot and the linux kernel but an overlay manager isn't yet upstream. There's (sic) Is GPIO supported? GPIO isn't supported well as they need to be mapped with Device Tree overlays. This will be improved in the F-27 cycle, and in Fedora 28. Is SPI supported? Yes, basic SPI is supported. Is I2C supported? Yes, basic I2C is supported. by default, i know that i2c is functional since i added an rtc and added a simple udev rule to make it work, however, spi isn't that simple i have an enc28j60 wired to the gpio in hopes of having a secondary ethernet interface, i know it's wired correctly since i downloaded raspbian and added the appropriate overlay magic to config.txt and it automatically registers as eth1 on fedora, a simple modprobe spidev or modprobe spi-bcm2835{,aux} doesn't seem to populate /dev/ with any spidev* i even grafted all of the fedora kernel patches (https://src.fedoraproject.org/rpms/kernel.git) onto the raspberry pi kernel (https://github.com/raspberrypi/linux.git, rpi-4.15.y), built it (make olddefconfig), installed it, did all that funny mkimage crap, booted off it (raspberries instead of penguins (everything else still worked)), and still no functional spi i think this implies that between raspbian and fedora there's a specific CONFIG_ option in the kernel i need to add, but i don't know what one (ones?) it would be any help would be appreciated ---- Sent using Sharklasers.com Block or report abuse: https://www.sharklasers.com//abuse/?a=QFN5JQEJUKAGxgix9HENcwTVQsCV0cMeyLZF

2 2

Re: The 4.15 kernel rebase on stable releases
by Stewart Samuels 21 Mar '18

21 Mar '18

I just got a chance to test the 4.16.0-0.rc2 kernel using the 20180220 Xfce Rawhide Spin. It fails to boot due to a kernel paging request. Here are the snippets: U-Boot 2018.03-rc2 (Feb 16 2018 - 14:14:52 +0000) for ODROID-XU3/XU4/HC1 CPU: Exynos5422 @ 800 MHz Model: Odroid XU3 based on EXYNOS5422 Board: Odroid XU3 based on EXYNOS5422 Type: xu4 DRAM: 2 GiB MMC: EXYNOS DWMMC: 0, EXYNOS DWMMC: 1 Loading Environment from MMC... *** Warning - bad CRC, using default environment Failed (-5) In: serial Out: serial Err: serial Net: No ethernet found. Hit any key to stop autoboot: 0 mmc_init: -5, time 6 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:2... Found /extlinux/extlinux.conf Retrieving file: /extlinux/extlinux.conf 591 bytes read in 14 ms (41 KiB/s) Ignoring unknown command: ui Ignoring malformed menu command: autoboot Ignoring malformed menu command: hidden Ignoring unknown command: totaltimeout Fedora-Xfce-armhfp-Rawhide-20180220.n.0 Boot Options. 1: Fedora-Xfce-armhfp-Rawhide-20180220.n.0 (4.16.0-0.rc2.git0.1.fc28.armv7hl) Enter choice: 1: Fedora-Xfce-armhfp-Rawhide-20180220.n.0 (4.16.0-0.rc2.git0.1.fc28.armv7hl) Retrieving file: /initramfs-4.16.0-0.rc2.git0.1.fc28.armv7hl.img 54271696 bytes read in 4082 ms (12.7 MiB/s) Retrieving file: /vmlinuz-4.16.0-0.rc2.git0.1.fc28.armv7hl 6660608 bytes read in 519 ms (12.2 MiB/s) append: ro root=UUID=7d9c6236-7437-49c9-9e30-cf5ba8d147d5 cma=192MB Retrieving file: /dtb-4.16.0-0.rc2.git0.1.fc28.armv7hl/exynos5422-odroidxu4.dtb 56970 bytes read in 508 ms (109.4 KiB/s) Kernel image @ 0x42000000 [ 0x000000 - 0x65a200 ] ## Flattened Device Tree blob at 43000000 Booting using the fdt blob at 0x43000000 Loading Ramdisk to 4cc3e000, end 4ffffed0 ... OK Loading Device Tree to 4cc2d000, end 4cc3de89 ... OK Starting kernel ... [ 0.000000] Booting Linux on physical CPU 0x100 [ 0.000000] Linux version 4.16.0-0.rc2.git0.1.fc28.armv7hl (mockbuild(a)buildvm-armv7-07.arm.fedoraproject.org) (gcc version 8.0.1 20180218 8 [ 0.000000] CPU: ARMv7 Processor [410fc073] revision 3 (ARMv7), cr=10c5387d . . . [ 6.366866] 12c30000.serial: ttySAC3 at MMIO 0x12c30000 (irq = 61, base_baud = 0) is a S3C6400/10 [ 6.377630] msm_serial: driver initialized [ 6.380655] STMicroelectronics ASC driver initialized [ 6.390013] libphy: Fixed MDIO Bus: probed [ 6.393299] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 6.399194] ehci-pci: EHCI PCI platform driver [ 6.403631] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [ 6.409762] ohci-pci: OHCI PCI platform driver [ 6.414203] uhci_hcd: USB Universal Host Controller Interface driver [ 6.420729] usbcore: registered new interface driver usbserial_generic [ 6.427020] usbserial: USB Serial support registered for generic [ 6.433186] mousedev: PS/2 mouse device common for all mice [ 6.445564] device-mapper: uevent: version 1.0.3 [ 6.449213] device-mapper: ioctl: 4.37.0-ioctl (2017-09-20) initialised: dm-devel(a)redhat.com [ 6.461297] ledtrig-cpu: registered to indicate activity on CPUs [ 6.466198] hidraw: raw HID events driver (C) Jiri Kosina [ 6.471445] usbcore: registered new interface driver usbhid [ 6.476783] usbhid: USB HID core driver [ 6.483709] drop_monitor: Initializing network drop monitor service [ 6.489025] Initializing XFRM netlink socket [ 6.493716] NET: Registered protocol family 10 [ 8.028149] Unable to handle kernel paging request at virtual address fffffffc Stewart On 02/22/2018 12:01 PM, Peter Robinson wrote: > On Thu, Feb 22, 2018 at 7:52 PM, Stewart Samuels <searider74(a)gmail.com> wrote: >> >> On 02/22/2018 11:39 AM, Peter Robinson wrote: >>> On Thu, Feb 22, 2018 at 7:24 PM, Stewart Samuels <searider74(a)gmail.com> >>> wrote: >>>> Hi Peter, >>>> >>>> I just got a chance to update my Odroid Xu4 with the latest updates for >>>> F27. >>>> All was working fine with the exceptions for the Exynos 5 USB-3 issues >>>> prior >>>> to this upgrade. After the upgrade and a reboot, my system no longer >>>> boots >>>> into graphics mode. It seems to be failing somewhere along the line with >>>> udev, but I am not certain of this. The system will eventually boot into >>>> non-graphics mode, which can be seen when connecting the serial port and >>>> watching the boot messages. >>>> >>>> As I mentioned in previous posts, the Rawhide Spins all seem to have this >>>> issue too. In fact, they have had the problem for a long time now. On >>>> the >>>> positive side, both this release of F27 updates and the Rawhide spins do >>>> seem to have the USB-3 issues fixed. >>> Can you try the 4.16rc2 kernel [1] and see if that has the same >>> issues. The 4.16 kernel might help as there was a bunch of stuff that >>> changed in the exynos drm driver. >>> >>> https://koji.fedoraproject.org/koji/buildinfo?buildID=1046448 >> Looking at the builds in this URL I see "rawhide" listed as one of the >> "Tasks". Doe this mean the current rawhide build are already including the >> kernel-4.16.0-0.rc2 kernel? > Yes, and the just branched F-28 will as well. So you can do an upgrade > to F-28 and get it there too > >>>> Attached, is a MS Word formatted file of my boot log. Hope this helps. >>> Please don't do that, word processing docs are really not the way to >>> handle this in open source just fpaste it or something. If it's booted >>> just do "dmesg | fpaste" and provide the URL. >>> >>>> Regards, >>>> Stewart >>>> >>>> >>>> On 02/12/2018 09:56 AM, Peter Robinson wrote: >>>>> Hi All, >>>>> >>>>> Just a heads up that the 4.15 kernel is headed to stable releases. >>>>> >>>>> I did a bunch of testing over the weekend and fixed up a bunch of >>>>> issues, added some minor enhancements across a number of platforms. >>>>> There is a kernel-4.15.2-301.fc27 build [1] which had all those fixes >>>>> for people to test, I expect a 4.15.3 kernel going to updates-testing >>>>> later today or tomorrow. >>>>> >>>>> A few notes for the fixes I added: >>>>> * fixed cpufreq/thermal on i.MX6 (thanks kwizart for upstream fix) >>>>> * Crypto/rng engine on some AllWinner devices now loads/works >>>>> (A10/A143/A20 at least, I suspect more will come with later kernels) >>>>> * Exynos 5 USB-3 issue should now be fixed once and for all (I hope) >>>>> * A bunch of improvements for monitor detection on the Raspberry Pi >>>>> * Ethernet driver more stable on AllWInner A64/H5 platforms (like >>>>> Pine64) >>>>> * Numerous other upstream fixes improvements that headed upstream >>>>> * 4.15.3 (not in the build above) will include aarch64 fixes for >>>>> Spectre/Meltdown. >>>>> >>>>> So please test and feel free to reply to this thread with any new >>>>> issues you see with the 4.15 series, or any positive results. >>>>> >>>>> [1] https://koji.fedoraproject.org/koji/taskinfo?taskID=24966088 >>>>> _______________________________________________ >>>>> arm mailing list -- arm(a)lists.fedoraproject.org >>>>> To unsubscribe send an email to arm-leave(a)lists.fedoraproject.org >>>>

2 4

Fedora 27 on Banana Pi M64
by Jan Pazdziora 28 Feb '18

28 Feb '18

Hello, I've got Banana Pi M64 on which I am able to run 2017-08-14-ubuntu-16.04-mate-desktop-beta-aarch64-bpi-m64-sd-emmc.img from http://www.banana-pi.org/m64-download.html reasonably well, except for failing WiFi connections to hidden SSID networks and for kodi being unbearably slow, even the UI and mouse movements. So seeing Ubuntu MATE not failing completely, I thought I'd give Fedora a try. I've used Fedora-Minimal-27-1.6.aarch64.raw.xz Upon boot I see U-Boot (?) output and EFI lines and then row of Tuxes and initial boot messages but then my TV goes blank. At no point during the boot (like grub interface) do I have USB (mouse, keyboard) working. When I add the dtb symlink to workaround https://bugzilla.redhat.com/show_bug.cgi?id=1528575 I see wired networking and DHCP working. Upgrading kernel seems to break the wired networking https://bugzilla.redhat.com/show_bug.cgi?id=1528593 but with all the other packages from updates upgraded, the board still works including wired networking and DHCP. The initial-setup.service seems to be looping during the boot and it seems to also affect dnf operations so I've disabled it. Is there any opinion about how well can Banana Pi M64 be supported by Fedora at this point, given that the board seems fine under Ubuntu MATE but that might include some non-OSS bits that we might not want in Fedora. Specifically missing at this point seems to be USB support, console after boot, and WiFi networking. Is there anything which might be useful to try? -- Jan Pazdziora Senior Principal Software Engineer, OpenShift Security Team, Red Hat

2 9

High load with kernel 4.15 on OdroidH1
by arm_ml＠rirasoft.de 27 Feb '18

27 Feb '18

Hi there, I've done a fresh installation of Fedora 27 (Fedora-Server-armhfp-27-1.6-sda.raw.xz) on my Odroid H1. With Kernel 4.13.9-300.fc27.armv7hl from this Image the load after boot is nearly 0 without any service running. After Update to actual kernel 4.15.4-300.fc27.armv7hl the load reach up to 4,12. Is the behavour normal? No services are running, no other modifications, boot from SD-Card.

1 1

[Fedocal] Reminder meeting : Fedora ARM & AArch64 status meeting
by pwhalen＠redhat.com 26 Feb '18

26 Feb '18

Dear all, You are kindly invited to the meeting: Fedora ARM & AArch64 status meeting on 2018-02-27 from 15:00:00 to 16:00:00 UTC At fedora-meeting-2(a)irc.freenode.net The meeting will be about: Fedora ARM & AArch64 weekly status meeting. More information available at: [https://fedoraproject.org/wiki/Architectures/ARM](https://fedoraproject.org… Source: https://apps.fedoraproject.org/calendar/meeting/8698/

2 1

Request for a review of F28 Release blocking deliverables
by Jan Kurik 26 Feb '18

26 Feb '18

I would like to ask for a review of Release blocking deliverables [1][2][3] for F28 release delivered by Spins SIGs. Please let me know in case of missing images, or in case the "blocking" status has changed since the last release. [1] https://fedoraproject.org/wiki/Releases/28/ReleaseBlocking#Labs [2] https://fedoraproject.org/wiki/Releases/28/ReleaseBlocking#Spins [3] https://fedoraproject.org/wiki/Releases/28/ReleaseBlocking#Everything Thanks, Jan -- Jan Kuřík Platform & Fedora Program Manager Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic

1 0

aarch64 kernel 4.15.3-300 & 4.15.4-300 SError Interrupt - panic on bootup - macchiatobin (Armada8040)
by Gabor Samu 26 Feb '18

26 Feb '18

Hello, I have a macchiatobin Armada 8040 based system with an old AMD Firestream 9250 video card booting via UEFI EDKII. The system has worked quite well up until recently. With kernels 4.15.3-300 and 4.15.4-300 the systempanics on bootup starting with error: [ 4.134847] SError Interrupt on CPU1, code 0xbf000000 -- SError [ 4.134851] CPU: 1 PID: 334 Comm: systemd-udevd Not tainted 4.15.4-300.fc27.aarch64 #1 [ 4.134852] Hardware name: Marvell Armada 8040 MacchiatoBin/Armada 8040 MacchiatoBin, BIOS EDK II Oct 10 2017 [ 4.134854] pstate: 80400005 (Nzcv daif +PAN -UAO) [ 4.134996] pc : r100_io_wreg+0x68/0x80 [radeon] [ 4.135123] lr : cail_ioreg_write+0x38/0x48 [radeon] [ 4.135123] sp : ffff00001247b4f0 [ 4.135125] x29: ffff00001247b4f0 x28: 000000000000b112 [ 4.135127] x27: 000000000000b111 x26: 0000000000000020 [ 4.135129] x25: 00000000ffffffff x24: ffffb19668d53900 [ 4.135131] x23: 0000000000000002 x22: 0000000000008001 [ 4.135132] x21: 0000000000008001 x20: 0000000000000034 [ 4.135134] x19: ffffb196671ec000 x18: 0000000000000018 [ 4.135135] x17: 0000000000000000 x16: 0000000000000000 [ 4.135137] x15: ffffffffffffffff x14: ffffffffffff0000 [ 4.135138] x13: ffffffffffffffff x12: ffff1b4a9ce35000 [ 4.135140] x11: 0000000000000000 x10: ffff1b4a9cfe3000 [ 4.135141] x9 : 0000000000000000 x8 : ffffb19667263e80 [ 4.135143] x7 : ffff01f28ed85618 x6 : ffff01f28ed85150 [ 4.135144] x5 : 000000000000b5bf x4 : 0000000000000002 [ 4.135146] x3 : ffff01f28ec847d0 x2 : 0000000000000100 [ 4.135147] x1 : 0000000000000034 x0 : ffff7dfffee01034 [ 4.135150] Kernel panic - not syncing: Asynchronous SError Interrupt Full boot log is at: EFI stub: Booting Linux Kernel... EFI stub: Using DTB from configuration table - Pastebin.com | | | | | | | | | | | EFI stub: Booting Linux Kernel... EFI stub: Using DTB from configuratio... | | |

1 0

Fedora 27 does not boot
by Alexander Chernov 23 Feb '18

23 Feb '18

Hi, I've been trying to install Fedora 27 to Raspberry Pi2, Raspberry Pi3, and Orange Pi Plus 2 without any success. Generally, the kernel boots then service initialization starts, but does not complete. For example, the latest attempt at booting Fedora 27 Server on Orange Pi Plus 2 stopped at the following: [ OK ] Reached target Basic System. Starting Initial Setup configuration program... [ OK ] Started Hardware RNG Entropy Gatherer Daemon. Starting OpenSSH rsa Server Key Generation... Starting ABRT Automated Bug Reporting Tool... Starting GSSAPI Proxy Daemon... Starting Authorization Manager... Starting OpenSSH ecdsa Server Key Generation... Starting System Security Services Daemon... Starting NTP client/server... Starting OpenSSH ed25519 Server Key Generation... Starting System Logging Service... [ OK ] Started Self Monitoring and Reporting Technology (SMART) Daemon. [ OK ] Started D-Bus System Message Bus. [ OK ] Started irqbalance daemon. [ OK ] Started System Logging Service. ... and nothing more on serial console. Any help would be appreciated. Regards, Alexander

3 3

Re: The 4.15 kernel rebase on stable releases
by Stewart Samuels 22 Feb '18

22 Feb '18

Sorry about not transmitting to the list previously. I hadn't noticed till you just pointed it out. My bad!!! Okay. My follow-up. I tried to install Fedora-Xfce-armhfp-Rawhide-20180220.n.0-sda.raw.xz. Here is a snippet from dracut during the installation process which I believe to be relevant: [ 4719.209090] dracut[1462] Executing: /usr/bin/dracut -f /boot/initramfs-4.16.0-0.rc2.git0.1.fc28.armv7hl.img 4.16.0-0.rc2.git0.1.fc28.armv7hl [ 4721.152402] dracut[1462] dracut module 'busybox' will not be installed, because command 'busybox' could not be found! [ 4724.107476] dracut[1462] dracut module 'biosdevname' will not be installed, because command 'biosdevname' could not be found! [ 4725.185474] dracut[1462] dracut module 'busybox' will not be installed, because command 'busybox' could not be found! [ 4727.693909] dracut[1462] *** Including module: bash *** [ 4727.799897] dracut[1462] *** Including module: systemd *** [ 4730.596548] dracut[1462] *** Including module: systemd-initrd *** [ 4730.859397] dracut[1462] *** Including module: nss-softokn *** [ 4731.005977] dracut[1462] *** Including module: i18n *** [ 4733.099767] dracut[1462] *** Including module: network *** [ 4734.115142] dracut[1462] *** Including module: ifcfg *** [ 4734.205946] dracut[1462] *** Including module: drm *** [ 4734.634405] dracut[1462] *** Including module: plymouth *** [ 4736.175415] dracut[1462] *** Including module: kernel-modules *** [ 4743.067874] dracut[1462] *** Including module: kernel-network-modules *** [ 4743.551749] dracut[1462] *** Including module: rootfs-block *** [ 4743.692609] dracut[1462] *** Including module: terminfo *** [ 4743.857149] dracut[1462] *** Including module: udev-rules *** [ 4744.004466] dracut[1462] Skipping udev rule: 40-redhat.rules [ 4744.025481] dracut[1462] Skipping udev rule: 50-firmware.rules [ 4744.046519] dracut[1462] Skipping udev rule: 50-udev.rules [ 4745.995457] dracut[1462] Skipping udev rule: 91-permissions.rules [ 4746.018661] dracut[1462] Skipping udev rule: 80-drivers-modprobe.rules [ 4746.256854] dracut[1462] *** Including module: dracut-systemd *** [ 4747.002206] dracut[1462] *** Including module: usrmount *** [ 4747.064120] dracut[1462] *** Including module: base *** [ 4747.670184] dracut[1462] *** Including module: fs-lib *** [ 4747.892757] dracut[1462] *** Including module: shutdown *** [ 4748.488677] dracut[1462] *** Including modules done *** [ 4748.514363] dracut[1462] *** Installing kernel module dependencies *** [ 4749.681429] dracut[1462] *** Installing kernel module dependencies done *** [ 4749.826826] dracut[1462] *** Resolving executable dependencies *** [ 4757.901864] dracut[1462] *** Resolving executable dependencies done*** [ 4758.173199] dracut[1462] *** Hardlinking files *** [ 4758.361998] dracut[1462] *** Hardlinking files done *** [ 4758.396299] dracut[1462] *** Stripping files *** [ 4758.693423] dracut[1462] *** Stripping files done *** [ 4758.720413] dracut[1462] *** Generating early-microcode cpio image *** [ 4758.812895] dracut[1462] *** Constructing AuthenticAMD.bin **** [ 4758.980397] dracut[1462] *** Store current command line parameters *** [ 4759.014533] dracut[1462] *** Creating image file '/boot/initramfs-4.16.0-0.rc2.git0.1.fc28.armv7hl.img' *** [ 4774.636604] dracut[1462] Image: /var/tmp/dracut.Y9Up20/initramfs.img: 18M So, although the boot messages are different now, the result is the same. The system boots but not into graphical mode. Also, note the orange highlighted lines from dracut. I will try to get the dmesg | fpaste output once I get the system on the network. Is there a particular URL you would like me to specify? Also, one other question. Is there anything from partition 1 (which seems to be strictly for Raspberry PIs) necessary to build and boot the system for other systems like the Odroid? More specifically, should I be able to build and boot the system using ONLY partitions 2,3,and 4? Thanks again. Stewart On 02/22/2018 12:01 PM, Peter Robinson wrote: > On Thu, Feb 22, 2018 at 7:52 PM, Stewart Samuels <searider74(a)gmail.com> wrote: >> >> On 02/22/2018 11:39 AM, Peter Robinson wrote: >>> On Thu, Feb 22, 2018 at 7:24 PM, Stewart Samuels <searider74(a)gmail.com> >>> wrote: >>>> Hi Peter, >>>> >>>> I just got a chance to update my Odroid Xu4 with the latest updates for >>>> F27. >>>> All was working fine with the exceptions for the Exynos 5 USB-3 issues >>>> prior >>>> to this upgrade. After the upgrade and a reboot, my system no longer >>>> boots >>>> into graphics mode. It seems to be failing somewhere along the line with >>>> udev, but I am not certain of this. The system will eventually boot into >>>> non-graphics mode, which can be seen when connecting the serial port and >>>> watching the boot messages. >>>> >>>> As I mentioned in previous posts, the Rawhide Spins all seem to have this >>>> issue too. In fact, they have had the problem for a long time now. On >>>> the >>>> positive side, both this release of F27 updates and the Rawhide spins do >>>> seem to have the USB-3 issues fixed. >>> Can you try the 4.16rc2 kernel [1] and see if that has the same >>> issues. The 4.16 kernel might help as there was a bunch of stuff that >>> changed in the exynos drm driver. >>> >>> https://koji.fedoraproject.org/koji/buildinfo?buildID=1046448 >> Looking at the builds in this URL I see "rawhide" listed as one of the >> "Tasks". Doe this mean the current rawhide build are already including the >> kernel-4.16.0-0.rc2 kernel? > Yes, and the just branched F-28 will as well. So you can do an upgrade > to F-28 and get it there too > >>>> Attached, is a MS Word formatted file of my boot log. Hope this helps. >>> Please don't do that, word processing docs are really not the way to >>> handle this in open source just fpaste it or something. If it's booted >>> just do "dmesg | fpaste" and provide the URL. >>> >>>> Regards, >>>> Stewart >>>> >>>> >>>> On 02/12/2018 09:56 AM, Peter Robinson wrote: >>>>> Hi All, >>>>> >>>>> Just a heads up that the 4.15 kernel is headed to stable releases. >>>>> >>>>> I did a bunch of testing over the weekend and fixed up a bunch of >>>>> issues, added some minor enhancements across a number of platforms. >>>>> There is a kernel-4.15.2-301.fc27 build [1] which had all those fixes >>>>> for people to test, I expect a 4.15.3 kernel going to updates-testing >>>>> later today or tomorrow. >>>>> >>>>> A few notes for the fixes I added: >>>>> * fixed cpufreq/thermal on i.MX6 (thanks kwizart for upstream fix) >>>>> * Crypto/rng engine on some AllWinner devices now loads/works >>>>> (A10/A143/A20 at least, I suspect more will come with later kernels) >>>>> * Exynos 5 USB-3 issue should now be fixed once and for all (I hope) >>>>> * A bunch of improvements for monitor detection on the Raspberry Pi >>>>> * Ethernet driver more stable on AllWInner A64/H5 platforms (like >>>>> Pine64) >>>>> * Numerous other upstream fixes improvements that headed upstream >>>>> * 4.15.3 (not in the build above) will include aarch64 fixes for >>>>> Spectre/Meltdown. >>>>> >>>>> So please test and feel free to reply to this thread with any new >>>>> issues you see with the 4.15 series, or any positive results. >>>>> >>>>> [1] https://koji.fedoraproject.org/koji/taskinfo?taskID=24966088 >>>>> _______________________________________________ >>>>> arm mailing list -- arm(a)lists.fedoraproject.org >>>>> To unsubscribe send an email to arm-leave(a)lists.fedoraproject.org >>>>

2 2

F27 grubaa64.efi pxe boot with Mustang drops to grub> prompt
by Chris Tatman 22 Feb '18

22 Feb '18

Hey All, Sorry if I have missed this someplace obvious. But I am trying to test a pxe install on a Mustang (xgene-1) board with F27 using the grubaa64.efi acquired from here: http://dl.fedoraproject.org/pub/fedora-secondary/releases/27/Server/aarch64… After being handed off this file from my dhcp server, the system drops down into a 'grub>' shell awaiting my input. But if I then replace the F27 grubaa64.efi file with the known good grubaa64.efi from RHEL-alt-7.4, the system boots as normal and loads my grub.cfg menu and I am allowed to choose an install option: ------------------------ Install Red Hat Enterprise Linux for ARM 7.4 GA Install Fedora 27 Use the and keys to change the selection. Press 'e' to edit the selected item, or 'c' for a command prompt. The selected entry will be started automatically in 2s. --------------------------- However, as you can imagine, this does not work if I select the Fedora 27 install. It halts and tells me I need to load the correct kernel: -------------- error: invalid magic number. error: you need to load the kernel first. ----------- This I assume is b/c I am using the incorrect grubaa64.efi to hand off to the F27 install kernel. So, is this a bug in the F27 grubaa64.efi? I have a pxe server that has been working for me with UEFI systems for a couple years now. All I normally do to test a a new OS is swap out the grubaa64.efi as I have done here. But, I admit that my experience is with different versions of RHEL and cetos. This is my first time doing this with Fedora. Thanks in advance for any tips!

2 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

arm February 2018