arm September 2019

arm@lists.fedoraproject.org

9 participants
13 discussions

How to help supporting a new Arm device
by Alexander Shopov 05 Apr '20

05 Apr '20

Hi all, I have the following device: DIY Laptop by Olimex https://www.olimex.com/Products/DIY-Laptop/ It is a 2GB A64 Cortex A53 Quad core 64-bit processor based. https://www.olimex.com/Products/DIY-Laptop/SPARE-PARTS/TERES-PCB1-A64/open-… There are several options for running Linux on it, but Fedora is not among them https://github.com/OLIMEX/DIY-LAPTOP/tree/master/SOFTWARE/A64-TERES I did not manage to run the latest stable Fedora on it. How can I help with getting Fedora on this laptop? Is there a how-to for getting this to run? Kind regards: al_shopov

3 4

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

29 Sep '19

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

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

22 Sep '19

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

Merging Centos-isms in to uboot-images
by Mark Verlinde 20 Sep '19

20 Sep '19

Hello list, After "complaining" on the centos-arm list about a Fedora specific patch in the el7 uboot-images they encouraged me to try to merge a fix upstream. Well here we are ;) It's about the specific location off the grub2 uefi boot stub @ efi/fedora/ for Fedrora vs efi/centos/ for centos. I wonder if a merge proposed in the compare link below is acceptable / discussable? https://github.com/markVnl/rpms-uboot-tools/compare/master...centosisms happy to hear from you

2 2

F31 raspberry pi support
by moiraine damodred 20 Sep '19

20 Sep '19

Is raspberry pi 4 support ready with Fedora 31? I see the dtd file (bcm2711-rpi-4-b.dtb) , the line "kernel=rpi4-u-boot.bin" is present in config.txt but the actural file (rpi4-u-boot.bin) missing in Fedora-Minimal-31_Beta-1.1.aarch64.raw.xz; rpi 4 will not boot and the led flashes 7 times, which may mean kernel missing? Thanks!

2 3

[Help Wanted] Fedora 31 Talking Points
by Alberto Rodriguez Sanchez 16 Sep '19

16 Sep '19

Hi team, I'm Alberto Rodríguez, and I'm here in the behalf of the Marketing team. As you should know, we prepare a lists of highlights about each release, called Talking Points: Talking points are key highlights of the new release. There are different types of talking points for different types of people: general desktop users/everyone, developers, and sysadmins. They are meant to provide a short, effective answer to the question "What cool stuff is in the latest release of Fedora?" They are compelling, not necessarily comprehensive This points help us, as Marketing team, as well to Ambassadors, to publicize each release with the news and cool stuff. For this matter and this release, we have this wiki page: https://fedoraproject.org/wiki/Fedora_31_talking_points and we will be happy to include the new things in Fedora 31 You can help us in both ways: 1. Editing the wiki directly with the points. 2. Throwing us the list, and we will put them in the wiki. Thanks in advance for your help and for your efforts. Best Regards

1 0

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

15 Sep '19

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

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

08 Sep '19

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

Camera module oopses
by Jan Kratochvil 06 Sep '19

06 Sep '19

Hi, On Thu, 22 Aug 2019 12:15:31 +0200, Peter Robinson wrote: > On Thu, Aug 22, 2019 at 10:59 AM Stefan Wahren <stefan.wahren(a)i2se.com> wrote: > > On 22.08.19 11:31, Jan Kratochvil wrote: > > > (That NoIR Raspberry camera module locks up kernel but that is offtopic here.) > > > > This issue is new to me, please report to the list. > > News to me too, I have a standard camera module attached to a 3A > without issue. Lets start a different thread on this. It is a Camera V2.1, there was connected other camera on USB during boot, dmesg shows with the Raspberry Camera additionally just: bcm2835-v4l2: scene mode selected 0, was 0 bcm2835-v4l2: V4L2 device registered as video2 - stills mode > 1280x720 bcm2835-v4l2: Broadcom 2835 MMAL video capture ver 0.0.2 loaded. bcm2835-v4l2: Failed to enable capture port - error -1. Disabling camera port again More dumps below. Jan kernel-5.2.11-200.fc30.aarch64 fswebcam-20140113-11.fc30.aarch64 # v4l2-ctl --list-formats-ext -d /dev/video2 ioctl: VIDIOC_ENUM_FMT Type: Video Capture [0]: 'YU12' (Planar YUV 4:2:0) Size: Stepwise 32x32 - 3280x2464 with step 2/2 [1]: 'YUYV' (YUYV 4:2:2) Size: Stepwise 32x32 - 3280x2464 with step 2/2 [2]: 'RGB3' (24-bit RGB 8-8-8) Size: Stepwise 32x32 - 3280x2464 with step 2/2 [3]: 'JPEG' (JFIF JPEG, compressed) Size: Stepwise 32x32 - 3280x2464 with step 2/2 [4]: 'H264' (H.264, compressed) Size: Stepwise 32x32 - 3280x2464 with step 2/2 [5]: 'MJPG' (Motion-JPEG, compressed) Size: Stepwise 32x32 - 3280x2464 with step 2/2 [6]: 'YVYU' (YVYU 4:2:2) Size: Stepwise 32x32 - 3280x2464 with step 2/2 [7]: 'VYUY' (VYUY 4:2:2) Size: Stepwise 32x32 - 3280x2464 with step 2/2 [8]: 'UYVY' (UYVY 4:2:2) Size: Stepwise 32x32 - 3280x2464 with step 2/2 [9]: 'NV12' (Y/CbCr 4:2:0) Size: Stepwise 32x32 - 3280x2464 with step 2/2 [10]: 'BGR3' (24-bit BGR 8-8-8) Size: Stepwise 32x32 - 3280x2464 with step 2/2 [11]: 'YV12' (Planar YVU 4:2:0) Size: Stepwise 32x32 - 3280x2464 with step 2/2 [12]: 'NV21' (Y/CrCb 4:2:0) Size: Stepwise 32x32 - 3280x2464 with step 2/2 [13]: 'BGR4' (32-bit BGRA/X 8-8-8-8) Size: Stepwise 32x32 - 3280x2464 with step 2/2 # fswebcam -d /dev/video2 -r 3280x2464 --png 9 -F 1 /tmp/1.png --- Opening /dev/video2... Trying source module v4l2... /dev/video2 opened. No input was specified, using the first. Error starting stream. VIDIOC_STREAMON: Operation not permitted Unable to use mmap. Using read instead. --- Capturing frame... VIDIOC_DQBUF: Invalid argument No frames captured. At the moment one runs fswebcam it: ------------[ cut here ]------------ WARNING: CPU: 2 PID: 1319 at drivers/media/common/videobuf2/videobuf2-core.c:1486 vb2_start_streaming+0xf8/0x178 [videobuf2_common] Modules linked in: tun nf_conntrack_netbios_ns nf_conntrack_broadcast xt_CT ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 ipt_REJECT nf_reject_ipv4 xt_conntrack ebtable_nat ip6table_nat ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_nat iptable_mangle iptable_raw iptable_security nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c netconsole ip_set nfnetlink ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter bnep sunrpc vfat fat bcm2835_v4l2(C) snd_bcm2835(C) rc_cec cpufreq_dt v4l2_common vc4 snd_usb_audio snd_soc_core snd_usbmidi_lib snd_compress snd_hwdep ac97_bus uvcvideo snd_rawmidi snd_pcm_dmaengine snd_seq videobuf2_vmalloc videobuf2_memops snd_seq_device videobuf2_v4l2 snd_pcm videobuf2_common crct10dif_ce videodev btsdio snd_timer drm_kms_helper snd brcmfmac soundcore hci_uart media drm raspberrypi_hwmon brcmutil btqca raspberrypi_cpufreq btrtl cfg80211 btbcm btintel bluetooth fb_sys_fops syscopyarea sysfillrect sysimgblt ecdh_generic rfkill ecc bcm2835_thermal vchiq(C) bcm2835_wdt bcm2835_rng leds_gpio lz4 lz4_compress zram ip_tables microchip lan78xx mmc_block dwc2 sdhci_iproc sdhci_pltfm gpio_raspberrypi_exp udc_core sdhci pwm_bcm2835 bcm2835 bcm2835_dma i2c_bcm2835 phy_generic CPU: 2 PID: 1319 Comm: fswebcam Tainted: G C 5.2.11-200.fc30.aarch64 #1 Hardware name: raspberrypi rpi/rpi, BIOS 2018.09 09/11/2018 pstate: 40400005 (nZcv daif +PAN -UAO) pc : vb2_start_streaming+0xf8/0x178 [videobuf2_common] lr : vb2_start_streaming+0xf8/0x178 [videobuf2_common] sp : ffff00001252bac0 x29: ffff00001252bac0 x28: 0000000040045612 x27: 0000000000000000 x26: ffff000009263240 x25: 0000000000000000 x24: ffff00001252bcb0 x23: ffff8000321455c8 x22: ffff00001252bcb0 x21: ffff000008f7dd28 x20: ffff800032145878 x19: 00000000ffffffff x18: 0000000000000000 x17: 0000000000000000 x16: 0000000000000000 x15: 000000000000ad55 x14: 0000000000000010 x13: 00000000ffffffff x12: ffff000008cf7098 x11: 0000000000000001 x10: 0000000000000000 x9 : 0000000000000003 x8 : 0000000000000197 x7 : 00000000ad55ad55 x6 : 0000000000000001 x5 : 0000000000000000 x4 : ffff80003ad841d0 x3 : ffff80003ad91bc8 x2 : ffff80003ad841d0 x1 : 0000800029ad9000 x0 : 0000000000000024 Call trace: vb2_start_streaming+0xf8/0x178 [videobuf2_common] vb2_core_streamon+0x98/0x188 [videobuf2_common] vb2_streamon+0x30/0x78 [videobuf2_v4l2] vb2_ioctl_streamon+0x54/0x60 [videobuf2_v4l2] v4l_streamon+0x3c/0x50 [videodev] __video_do_ioctl+0x174/0x3b0 [videodev] video_usercopy+0x1bc/0x608 [videodev] video_ioctl2+0x3c/0x50 [videodev] v4l2_ioctl+0x64/0x90 [videodev] do_vfs_ioctl+0x468/0x5f0 ksys_ioctl+0x84/0xb8 __arm64_sys_ioctl+0x28/0x38 el0_svc_common.constprop.0+0x74/0x168 el0_svc_handler+0x34/0x90 el0_svc+0x8/0xc ---[ end trace 66558eb8d19a6247 ]---

2 2

"No GPUs found with udev" gnome-shell error on Raspberry Pi 3b+
by Brion Vibber 04 Sep '19

04 Sep '19

Hi all! I've got a Raspberry Pi 3b+ with Fedora 30 on SD cards running armv7 and aarch64. I recently installed updates with dnf on both after a few weeks, and after reboot I can no longer get into a graphical login. The shell fails to find a GPU which leads the session to fail: --------- Apr 26 02:49:52 lilbit gnome-shell[916]: Failed to create backend: No GPUs found with udev Apr 26 02:49:52 lilbit gnome-session[889]: gnome-session-binary[889]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 Apr 26 02:49:52 lilbit gnome-session-binary[889]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 Apr 26 02:49:52 lilbit gnome-session-binary[889]: Unrecoverable failure in required component org.gnome.Shell.desktop Apr 26 02:49:52 lilbit systemd-logind[725]: Failed to restore VT, ignoring: Input/output error --------- (Don't mind the wrong date, the system clock is wrong until networking comes up.) These SD cards were originally installed with Fedora 29 and upgraded via dnf-system-upgrade, so that might lead to something funky in the boot partitions perhaps; if that's an expected sort of failure I can just reinstall. :) Thanks for any advice! -- brion

4 14

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

arm September 2019