arm June 2019

arm@lists.fedoraproject.org

11 participants
18 discussions

Fedora ARM & AArch64 Status Meeting Minutes 2019-06-18
by Paul Whalen 18 Jun '19

18 Jun '19

======================================================== #fedora-meeting-2: Fedora ARM and AArch64 Status Meeting ======================================================== Meeting started by pwhalen at 15:00:25 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-2/2019-06-18/fedora_arm_an… . Meeting summary --------------- * roll call (pwhalen, 15:00:25) * 1) ==== Userspace Status ==== (pwhalen, 15:05:08) * No new issues reported. (pwhalen, 15:05:40) * 2) ==== Kernel Status ==== (pwhalen, 15:06:30) * F30: kernel-5.1.11-300.fc30 (pwhalen, 15:06:40) * LINK: https://koji.fedoraproject.org/koji/buildinfo?buildID=1289142 (pwhalen, 15:06:40) * F31: kernel-5.2.0-0.rc5.git0.1.fc31 (pwhalen, 15:08:50) * LINK: https://koji.fedoraproject.org/koji/buildinfo?buildID=1288824 (pwhalen, 15:08:50) * Please test and report any issues to the list or #fedora-arm. (pwhalen, 15:09:55) * 3) ==== Bootloader Status ==== (pwhalen, 15:11:23) * uboot-tools-2019.07-0.1.rc4 (pwhalen, 15:11:31) * LINK: https://koji.fedoraproject.org/koji/taskinfo?taskID=35612902 (pwhalen, 15:11:31) * Please test and report any issues to the list or #fedora-arm. (pwhalen, 15:14:29) * 4) ==== Fedora 31 ==== (pwhalen, 15:15:59) * F31 composes currently failing, last nominated compose was Fedora-Rawhide-20190601.n.0 (pwhalen, 15:17:04) * 5) == Open Floor == (pwhalen, 15:28:16) Meeting ended at 15:42:01 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * pwhalen (46) * pbrobinson (20) * nirik (14) * zodbot (6) * tdawson (1) * jlinton (0) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`:

1 0

[Fedocal] Reminder meeting : Fedora ARM & AArch64 status meeting
by pwhalen＠redhat.com 16 Jun '19

16 Jun '19

Dear all, You are kindly invited to the meeting: Fedora ARM & AArch64 status meeting on 2019-06-18 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/9431/

1 0

Fedora ARM & AArch64 Status Meeting Minutes 2019-06-11
by Paul Whalen 11 Jun '19

11 Jun '19

======================================================== #fedora-meeting-2: Fedora ARM and AArch64 Status Meeting ======================================================== Meeting started by pwhalen at 15:00:31 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-2/2019-06-11/fedora_arm_an… . Meeting summary --------------- * roll call (pwhalen, 15:00:45) * 1) ==== Userspace Status ==== (pwhalen, 15:07:58) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1705676 (pbrobinson, 15:09:38) * edk2 doesn't always enabled the graphical display on arm/aarch64 (pwhalen, 15:10:09) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1705676 (pwhalen, 15:10:18) * 2) ==== Kernel Status ==== (pwhalen, 15:20:05) * F31: kernel-5.2.0-0.rc4.git0.1.fc31 (pwhalen, 15:20:16) * LINK: https://koji.fedoraproject.org/koji/buildinfo?buildID=1285015 (pwhalen, 15:20:16) * F30: kernel-5.1.8-300.fc30 (pwhalen, 15:22:25) * LINK: https://koji.fedoraproject.org/koji/buildinfo?buildID=1283779 (pwhalen, 15:22:25) * Please test and report any issues to the list or #fedora-arm. (pwhalen, 15:22:53) * 3) ==== Bootloader Status ==== (pwhalen, 15:24:17) * New grub2 available for testing - grub2-2.02-87.fc31 (pwhalen, 15:24:41) * LINK: https://koji.fedoraproject.org/koji/buildinfo?buildID=1285376 (pwhalen, 15:24:42) * 4) ==== Fedora 31 ==== (pwhalen, 15:27:21) * SoaS initramfs fix added to fedora-kickstarts (not yet merged) (pwhalen, 15:27:34) * LINK: https://pagure.io/fedora-kickstarts/pull-request/531 (pwhalen, 15:27:35) * Last successful compose - Fedora-Rawhide-20190609.n.1 (pwhalen, 15:30:11) * LINK: https://kojipkgs.fedoraproject.org/compose//rawhide/Fedora-Rawhide-20190609… (pwhalen, 15:30:20) * 5) == Open Floor == (pwhalen, 15:42:13) Meeting ended at 15:47:37 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * pwhalen (38) * pbrobinson (23) * jlinton (20) * satellit (9) * zodbot (6) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

[Fedocal] Reminder meeting : Fedora ARM & AArch64 status meeting
by pwhalen＠redhat.com 09 Jun '19

09 Jun '19

Dear all, You are kindly invited to the meeting: Fedora ARM & AArch64 status meeting on 2019-06-11 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/9431/

1 0

Error during Fedora 30 kickstart on Raspberry Pi 3 B+
by Felix Geschwindner 03 Jun '19

03 Jun '19

Hey Guys, I've been using Fedora on Raspberry Pis for a while now and I love it. The only problem I consistently face is the process of reinstalling (due to broken SD, sudo SNAFU etc.): 1. Put SD card in secondary machine 2. DD the Fedora aarch64 image onto SD card 3. Grow partition 4. Put SD card back 5. Boot 6. Go through initial setup 7. Update all packages 8. Continue with regular config and host management Since I've used PXE in x86_64 environments for years, I started looking into doing the same for the RPI. The idea is to condense the process into a single step: 1. Either insert (new) empty SD card or destroy the partition table on the active SD card and reboot In theory this should work because by default the RPI 3 B+ boots from SD card first and on failure moves on to PXE which then loads the PXE components from TFTP and starts the kickstart process. That should give (with the proper kickstart instructions) a completely headless and unattended installation environment for RPI. This has been done for preseeding raspbian here: https://github.com/debian-pi/raspbian-ua-netinst and I'd love to do this for Fedora as well. I brought up my PXE environment and the RPI is reliably pulling everything from initial bootcode.bin all the way to U-Boot and I end up with a U-Boot shell prompt. Then loading grubaa64.efi through TFTP brings me to the GRUB shell which pulls the vmlinuz and initrd.img devices and starts the kernel. This is where I'm stuck. When the system is loading the stage2 install.img it looks like it's running out of space on the tmpfs and I'm getting a "No space left on device" error and kernel panic (not sure yet if they are related). I'm not very skilled in dissecting initrd images so I'd appreciate any pointers. Is there a kernel or anaconda parameter to increase the tmpfs size? Maybe the 1G of memory is just not big enough to hold the ~470MB install.img AND have enough left to finish the kickstart. Would it be feasible to reduce install.img? [ 47.515164] usbcore: registered new interface driver lan78xx [ 49.874865] ------------[ cut here ]------------ [ 49.892272] irq 79 handler irq_default_primary_handler+0x0/0x20 enabled interrupts [ 49.912598] WARNING: CPU: 0 PID: 0 at kernel/irq/handle.c:152 __handle_irq_event_percpu+0x1fc/0x228 [ 49.934342] Modules linked in: microchip lan78xx hid_ite snd_pcm snd_timer snd soundcore drm_kms_helper mmc_block syscopyarea sysfillrect sysimgblt fb_sys_fops drm dwc2 sdhci_iproc sdhci_pltfm crct10dif_ce udc_core sdhci gpio_raspberrypi_exp pwm_bcm2835 i2c_bcm2835 bcm2835 bcm2835_dma phy_generic sunrpc lrw dm_crypt dm_round_robin dm_multipath linear raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 squashfs zstd_decompress cramfs be2iscsi bnx2i cnic uio cxgb4i cxgb4 cxgb3i cxgb3 mdio libcxgbi libcxgb qla4xxx iscsi_boot_sysfs iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi [ 50.057520] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.0.9-301.fc30.aarch64 #1 [ 50.078134] Hardware name: raspberrypi rpi/rpi, BIOS 2019.04 04/18/2019 [ 50.098047] pstate: 60400005 (nZCv daif +PAN -UAO) [ 50.116053] pc : __handle_irq_event_percpu+0x1fc/0x228 [ 50.134467] lr : __handle_irq_event_percpu+0x1fc/0x228 [ 50.152808] sp : ffff000010003ce0 [ 50.168935] x29: ffff000010003ce0 x28: ffff80002aa46a00 [ 50.186785] x27: ffff000011184018 x26: ffff000011184018 [ 50.204289] x25: ffff00001157ef60 x24: ffff000010003d6c [ 50.221399] x23: 0000000000000000 x22: 000000000000004f [ 50.238168] x21: ffff80002aa46a28 x20: 0000000000000002 [ 50.254596] x19: ffff80002370d700 x18: 0000000000000000 [ 50.270753] x17: 0000000000000000 x16: 0000000000000000 [ 50.286512] x15: 0000000000000010 x14: 0000000000000001 [ 50.301835] x13: 0000000000001280 x12: ffff000010bf0db8 [ 50.316804] x11: 0000000000000000 x10: ffff800037ada0b0 [ 50.331455] x9 : 00000000ffffffff x8 : 0000000000000152 [ 50.346058] x7 : ffff0000176d1820 x6 : 0000000000000001 [ 50.360583] x5 : 0000000000000000 x4 : 0000000000000001 [ 50.374766] x3 : 0000000000000000 x2 : 0000000000000040 [ 50.388589] x1 : 0000000000000004 x0 : 0000000000000046 [ 50.402281] Call trace: [ 50.412701] __handle_irq_event_percpu+0x1fc/0x228 [ 50.425284] handle_irq_event_percpu+0x28/0x70 [ 50.437447] handle_irq_event+0x50/0xa8 [ 50.448636] handle_simple_irq+0xac/0xf8 [ 50.459564] generic_handle_irq+0x34/0x50 [ 50.470387] intr_complete+0x8c/0x178 [lan78xx] [ 50.481577] __usb_hcd_giveback_urb+0x74/0x140 [ 50.492398] usb_giveback_urb_bh+0xd0/0x150 [ 50.502669] tasklet_action_common.isra.0+0x88/0xf0 [ 50.513687] tasklet_hi_action+0x2c/0x38 [ 50.523602] __do_softirq+0x128/0x31c [ 50.533054] irq_exit+0xc0/0xe0 [ 50.541612] __handle_domain_irq+0x70/0xc0 [ 50.550842] bcm2836_arm_irqchip_handle_irq+0x74/0xd8 [ 50.560783] el1_irq+0xe8/0x1c0 [ 50.568434] arch_cpu_idle+0x34/0x1b8 [ 50.576319] do_idle+0x1fc/0x248 [ 50.583591] cpu_startup_entry+0x2c/0x30 [ 50.591483] rest_init+0xc0/0xcc [ 50.598557] arch_call_rest_init+0x14/0x1c [ 50.606494] start_kernel+0x46c/0x480 [ 50.614059] ---[ end trace b9c80dddae7c6c2b ]--- [ 50.628673] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 54.412911] dracut-initqueue[880]: Warning: can't find installer main image path in .treeinfo [ 54.483584] dracut-initqueue[880]: % Total % Received % Xferd Average Speed Time Time Time Current [ 54.484525] dracut-initqueue[880]: Dload Upload Total Spent Left Speed 38 482M 38 187M 0 0 38.1M 0 0:00:12 0:00:04 0:00:08 38.2M [ 59.408000] dracut-initqueue[880]: curl: (23) Failed writing body (2946 != 5792) [ 60.172589] loop: module loaded [ 60.334211] dracut-initqueue[880]: mount: /run/initramfs/squashfs: wrong fs t[ 60.342641] dracut: FATAL: Failed to find a root filesystem in /tmp/curl_fetch_url1/install.img. ype, bad option, bad superblock on /dev/loop0, missing codepage or helpe[ 60.342703] dracut: Refusing to continue r program, or other error. [ 60.337120] dracut-initqueue[880]: /lib/dracut-lib.sh: line 465: echo: write error: No space left on device [ 60.367607] dracut-initqueue[880]: /lib/dracut-lib.sh: line 466: echo: write error: No space left on device [ 60.425966] dracut-initqueue[880]: /lib/anaconda-lib.sh: line 151: printf: write error: No space left on device

2 5

Connect to hidden wifi networks at boot.
by Mostafa Faridi 02 Jun '19

02 Jun '19

I installed Fedora Server on PI 3 and everything works. I want to connect to hidden wifi networks. I want when my Fedora boot, it connect to Hidden networks and I can control it by SSH over wifi. I can not find good solutions. The router of the wifi network uses DHCP to give IP to connected devices.

5 17

Can I use cron job to run nmcli
by Mostafa Faridi 02 Jun '19

02 Jun '19

can I use cron job to run nmcli on Fedora Server on PI 3?

2 1

[Fedocal] Reminder meeting : Fedora ARM & AArch64 status meeting
by pwhalen＠redhat.com 02 Jun '19

02 Jun '19

Dear all, You are kindly invited to the meeting: Fedora ARM & AArch64 status meeting on 2019-06-04 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/9431/

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

arm June 2019