arm November 2017

arm@lists.fedoraproject.org

7 participants
11 discussions

Summary of Fedora on Odroid XU4
by arm_ml＠rirasoft.de 08 Jan '18

08 Jan '18

Summary of Fedora on Odroid XU4 1. with Kernel 4.6.5-300.fc24 system boots without failure, but update to newer kernel fails due dracut didn't build suitable intramfs https://bugzilla.redhat.com/show_bug.cgi?id=1482825 2. newer kernel works only with "cpuidle.off=1" inserted into the "append" kernel line in the /boot/extlinux/extlinux.conf file, but all USB3 Hosts failed, no onboard ethernet 3. To boot the system from the eMMC card: A. The initramfs image file must be rebuilt. The simplest way is to: a. Boot up using the MicroSD card; b. Partition the eMMC card such that partition 1 begins on sector 3072 (Default starting sector from fdisk is 2048). There should be 4 partitions created; c. Mount the Fedora image desired to be installed on the eMMC card; d. Copy all partition data from the mounted fedora image partitions (there are 4 for Fedora 26 ARM images) to the appropriate eMMC partitions; e. Update the UUID values on what will be the /boot/extlinux/extlinux.conf file and /etc/fstab files of the eMMC card; f. Assuming the eMMC partitions are mounted as such -- mount /dev/mmcblk1p4 /mnt mount /dev/mmcblk1p2 /mnt/boot then perform the following mounts -- mount -o bind /proc /mnt/proc mount -o bind /dev /mnt/dev mount -o bind /sys /mnt/sys B. Rebuild the eMMC card's initramfs by executing the following command: chroot /mnt dracut --add-drivers='pwrseq_emmc mmc_block' /boot/initramfs-4.11.8-300.fc26.armv7hl.img 4.11.8-300.fc26.armv7hl C. Flash the boot information in the header of the eMMC card; C. Shutdown the system, then remove the MicroSD card; D. Boot up using the eMMC card. 4. If the system is to be updated using "dnf update", a new initramfs image must again be generated. This can be done using steps 1f - B. above using the new initramfs and kernel images provided by the "dnf update". ---------------------------------------------------------------- Note to the developers/maintainers of dracut: The kernel modules "pwrseq_emmc" and "mmc_block" should be included in dracut for the Odroid-XU3 and Odroid-XU4 such that the user need not have to execute this procedure each time and update to the system is performed. Is this correct and complete ? Andreas

9 38

activation of SPI on fedora26 with a raspberry3
by christophe pages 28 Dec '17

28 Dec '17

Hello, I try to activate the spi on my raspberry3 using a fedora 26. I tried these options: device_tree_param=spi=on dtoverlay=spi-bcm2708 I use this kernel: 4.12.5-300.fc26.armv7hl I see that the support in kernel seems already inside: CONFIG_SPI=y # CONFIG_SPI_DEBUG is not set CONFIG_SPI_MASTER=y But I never see the devices /dev/spi* appearing. I can't see any messages regarding spi in dmesg. I tested with a raspbian and I see them correctly. I think I miss somethiing. Could you help. Thanks.

3 5

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

26 Nov '17

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

1 0

Unable to see 'Initial setup wizard' on Raspberry PI 3 using aarch64 images
by Ashwin Rao 22 Nov '17

22 Nov '17

Hi, When running the aarch64 Workstation, Server, and Minimal images I am not able to see the initial setup wizard. I can see the messages shown during boot but after some time the screen either starts to flicker or just blanks out. I tried this on 3 different raspberry Pis with different cards and the result is always the same. The steps I followed are 1. I downloaded the aarch64 images from [ https://fedoraproject.org/wiki/Architectures/ARM/Raspberry_Pi#Raspberry_Pi_… ] and followed the instructions mentioned on the same web page to prepare the images using xzcat. 2. I connect the HDMI cable of my monitor, and connect the keyboard and mouse. I am not connecting an Ethernet cable. 3. I can see the boot screen, and the messages showing that the device is booting. 4. After some time the screen either blanks out or starts to flicker. I have tried it with different monitors and different power supplies as well but the result is the same. I noticed that the red LED of the Raspberry Pi also starts to blink abruptly. I am able to use Raspbian and OpenSuse using the same Raspberry Pis so I doubt there is an issue with the card, the power supply, or with the Pis. It would be nice if someone suggests the things I need to do, or if someone was able to troubleshoot similar issues. Regards, Ashwin

3 5

Fedora ARM & AArch64 Status Meeting Minutes 2017-11-21
by Paul Whalen 21 Nov '17

21 Nov '17

======================================================== #fedora-meeting-2: Fedora ARM and AArch64 Status Meeting ======================================================== Meeting started by pwhalen at 15:00:45 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-2/2017-11-21/fedora_arm_an… . Meeting summary --------------- * 1) ==== Userspace Status ==== (pwhalen, 15:04:43) * No issues reported. (pwhalen, 15:06:45) * 2) ==== Kernel Status ==== (pwhalen, 15:10:05) * Latest - kernel-4.14.0-1.fc28 (pwhalen, 15:10:17) * LINK: https://koji.fedoraproject.org/koji/buildinfo?buildID=998399 (pwhalen, 15:10:17) * Latest 4.15 - kernel-4.15.0-0.rc0.git6.1.fc28 (pwhalen, 15:11:51) * LINK: https://koji.fedoraproject.org/koji/buildinfo?buildID=1002516 (pwhalen, 15:12:19) * Latest F27 - kernel-4.13.14-300.fc27 (pwhalen, 15:16:46) * LINK: https://koji.fedoraproject.org/koji/buildinfo?buildID=1002396 (pwhalen, 15:16:46) * Please test and report any issues to the list or #fedora-arm. (pwhalen, 15:16:47) * 3) ==== Bootloader Status ==== (pwhalen, 15:16:56) * uboot-tools-2017.11-1.fc28 (pwhalen, 15:17:04) * LINK: https://koji.fedoraproject.org/koji/buildinfo?buildID=999266 (pwhalen, 15:17:04) * 4) == F27 Final Retrospective == (pwhalen, 15:20:12) * LINK: https://fedoraproject.org/wiki/Architectures/ARM/F27-Retrospective (pwhalen, 15:21:09) * 5) == F27 Modular Server == (pwhalen, 15:23:41) * 2018-01-09 Fedora Modular Server 27 Final Release (GA) (pwhalen, 15:23:48) * F27 Modular Server Beta Test Results - https://fedoraproject.org/wiki/Test_Results:Fedora_Modular_27_Beta_1.5_Summ… (pwhalen, 15:26:19) * Link to the latest compose : https://fedoraproject.org/wiki/Test_Results:Current_Modular_Summary (pwhalen, 15:27:49) * 6) == Open Floor == (pwhalen, 15:28:56) Meeting ended at 15:34:45 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * pwhalen (50) * pbrobinson (10) * jlinton_ (10) * zodbot (5) 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 19 Nov '17

19 Nov '17

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

1 0

[Fedocal] Reminder meeting : Fedora ARM & AArch64 status meeting
by pwhalen＠redhat.com 12 Nov '17

12 Nov '17

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

1 0

RPI3 and kind of issue with 8812 Realtek USB dongle
by Tomasz Kłoczko 07 Nov '17

07 Nov '17

Hi, I've received today ordered https://www.aliexpress.com/item/Wireless-USB-Adapter-1200mbps-Dual-Band-5Gh… I'v ordered this dongle not to have higher bandwidth over wifi but to be able to use 802.11ac channels. Generally dongle is working however when I'm trying to use it with RPi3 using lsusb I see it as: Bus 001 Device 009: ID 0bda:8176 Realtek Semiconductor Corp. RTL8188CUS 802.11n WLAN Adapter However when I'm trying to use it with x86 laptop I see it as: Bus 003 Device 099: ID 0bda:8812 Realtek Semiconductor Corp. RTL8812AU 802.11a/b/g/n/ac 2T2R DB WLAN Adapter Of course when I'm trying to use it with RPi3 I'm not able to even scan 802.11ac channels. Any comments or hints why under the same kernel version (in both cases I'm using up-to-date rawhide) on RPi3 this dongle is not detected as 8812 Realtek device? kloczek -- Tomasz Kłoczko | LinkedIn: http://lnkd.in/FXPWxH

2 3

Re: RPi 3 and kernel 4.14.0-0.rc3.git3.1.fc28.armv7hl
by Peter Robinson 07 Nov '17

07 Nov '17

re-added the list, looks like my mobile client dropped it On Tue, Nov 7, 2017 at 12:04 PM, Tomasz Kłoczko <kloczko.tomasz(a)gmail.com> wrote: > On 7 November 2017 at 11:55, Peter Robinson <pbrobinson(a)gmail.com> wrote: > [..] >> >> Update to rc8 and all the issues with vc4 should go away. >> >> _PLEASE_ if your using rawhide make sure your damn well running the >> latest version before wasting other people's time > > As I wrote loos like to keep everything up to date it is not enough to > only execute "dnf upgrade" and few (not obvious) steps needs to be > taken manually. So rc8 will be on it's way out to the mirrors likely today (or tomorrow) but I would tend to just pull them from koji if you want the latest. > No I know what needs to be done on RPi3 but I think that similar issue > may be affecting other armv7l/aarch64 installations. Again which issue? The DMA one, the firmware..... you've covered a number of possible issues in this thread. > Is it any existing tool/script which is addressing such issues? Address which such issues, please be explicit.

2 3

RPi 3 and kernel 4.14.0-0.rc3.git3.1.fc28.armv7hl
by Tomasz Kłoczko 07 Nov '17

07 Nov '17

Just resurected my old RPi 3 and as long as latest f27 image was OK I've pushed it to rawhide and seems current rawhide kernel has some issues on RPi 3. Just quick question: are below issues are already known or should I open ticket(s)? (ful dmesg in attachment) 1) [ 95.367454] Hardware name: Generic DT based system [ 95.367810] Workqueue: hci0 hci_cmd_work [bluetooth] [ 95.367848] [<c03131b4>] (unwind_backtrace) from [<c030d98c>] (show_stack+0x18/0x1c) [ 95.367868] [<c030d98c>] (show_stack) from [<c0b7e310>] (dump_stack+0xa0/0xd8) [ 95.367887] [<c0b7e310>] (dump_stack) from [<c03b2dd4>] (register_lock_class+0x298/0x514) [ 95.367905] [<c03b2dd4>] (register_lock_class) from [<c03b716c>] (__lock_acquire+0xe4/0x11f8) [ 95.367921] [<c03b716c>] (__lock_acquire) from [<c03b8e4c>] (lock_acquire+0x280/0x2dc) [ 95.367940] [<c03b8e4c>] (lock_acquire) from [<c0b99634>] (_raw_read_lock+0x4c/0x5c) [ 95.368057] [<c0b99634>] (_raw_read_lock) from [<bf58603c>] (hci_uart_tx_wakeup+0x1c/0x98 [hci_uart]) [ 95.368243] [<bf58603c>] (hci_uart_tx_wakeup [hci_uart]) from [<bf5870f0>] (hci_uart_send_frame+0x54/0x6c [hci_uart]) [ 95.368669] [<bf5870f0>] (hci_uart_send_frame [hci_uart]) from [<bf2ff26c>] (hci_send_frame+0xcc/0xf8 [bluetooth]) [ 95.369271] [<bf2ff26c>] (hci_send_frame [bluetooth]) from [<bf2ff340>] (hci_cmd_work+0xa8/0x124 [bluetooth]) [ 95.369581] [<bf2ff340>] (hci_cmd_work [bluetooth]) from [<c03735a4>] (process_one_work+0x444/0x840) [ 95.369598] [<c03735a4>] (process_one_work) from [<c0374d80>] (worker_thread+0x290/0x40c) [ 95.369615] [<c0374d80>] (worker_thread) from [<c037aac0>] (kthread+0x174/0x1a0) [ 95.369633] [<c037aac0>] (kthread) from [<c03087c8>] (ret_from_fork+0x14/0x2c) [ 95.507788] Bluetooth: hci0: BCM: chip id 94 2) [ 107.079610] ------------[ cut here ]------------ [ 107.079645] WARNING: CPU: 1 PID: 1 at lib/dma-debug.c:614 debug_dma_assert_idle+0x148/0x1e0 [ 107.079655] vc4-drm soc:gpu: DMA-API: cpu touching an active dma mapped cacheline [cln=0x00c8acc0] [ 107.079659] Modules linked in: ebtable_filter ebtables ip6table_filter ip6_tables rc_cec vc4 snd_soc_core ac97_bus snd_pcm_dmaengine cec rc_core snd_pcm snd_timer snd soundcore brcmfmac drm_kms_helper brcmutil drm fb_sys_fops hci_uart cfg80211 syscopyarea sysfillrect btbcm sysimgblt btqca btintel bluetooth bcm2835_wdt ecdh_generic rfkill bcm2835_thermal bcm2835_rng leds_gpio xfs libcrc32c smsc95xx usbnet mii mmc_block sdhci_iproc dwc2 sdhci_pltfm crc32_arm_ce udc_core sdhci pwm_bcm2835 i2c_bcm2835 bcm2835 bcm2835_dma phy_generic [ 107.079932] CPU: 1 PID: 1 Comm: systemd Not tainted 4.14.0-0.rc3.git3.1.fc28.armv7hl #1 [ 107.079937] Hardware name: Generic DT based system [ 107.079973] [<c03131b4>] (unwind_backtrace) from [<c030d98c>] (show_stack+0x18/0x1c) [ 107.079995] [<c030d98c>] (show_stack) from [<c0b7e310>] (dump_stack+0xa0/0xd8) [ 107.080012] [<c0b7e310>] (dump_stack) from [<c0354024>] (__warn+0xe4/0x104) [ 107.080028] [<c0354024>] (__warn) from [<c0354080>] (warn_slowpath_fmt+0x3c/0x4c) [ 107.080045] [<c0354080>] (warn_slowpath_fmt) from [<c0711634>] (debug_dma_assert_idle+0x148/0x1e0) [ 107.080069] [<c0711634>] (debug_dma_assert_idle) from [<c04e59e8>] (wp_page_copy+0xfc/0x640) [ 107.080087] [<c04e59e8>] (wp_page_copy) from [<c04e74b8>] (do_wp_page+0x3a4/0x5ac) [ 107.080101] [<c04e74b8>] (do_wp_page) from [<c04ea810>] (handle_mm_fault+0xd28/0xde0) [ 107.080118] [<c04ea810>] (handle_mm_fault) from [<c0b9a980>] (do_page_fault+0x244/0x3b8) [ 107.080136] [<c0b9a980>] (do_page_fault) from [<c0301360>] (do_DataAbort+0x40/0xc0) [ 107.080151] [<c0301360>] (do_DataAbort) from [<c0b9a260>] (__dabt_usr+0x40/0x60) [ 107.080159] Exception stack(0xef113fb0 to 0xef113ff8) [ 107.080170] 3fa0: 02565dd0 02601bb8 02565df0 00000002 [ 107.080184] 3fc0: 02565df0 0260c920 02601bb8 befdd848 befdd850 b6f7aa48 02565dd0 02559508 [ 107.080196] 3fe0: b6dd38f4 befdd7c8 b6cd1e38 b6cc8f3c 20060010 ffffffff [ 107.080249] ---[ end trace 66ededa5d1568f0b ]--- [ 107.080253] Mapped at: [ 107.080345] vc4_bo_create+0xe4/0x198 [vc4] [ 107.080420] vc4_allocate_bin_bo+0x38/0x150 [vc4] [ 107.080494] vc4_v3d_bind+0x12c/0x20c [vc4] [ 107.080507] component_bind_all+0x138/0x220 [ 107.080581] vc4_drm_bind+0x88/0x130 [vc4] [ 108.193398] nf_conntrack version 0.5.0 (16384 buckets, 65536 max) 3) some issue with missing symbol due systemd run [ 57.304786] systemd-journald[193]: Received SIGTERM from PID 1 (systemd). [ 59.997395] systemd: 15 output lines suppressed due to ratelimiting [ 61.986368] systemd[1]: RTC configured in localtime, applying delta of -240 minutes to system time. [ 75.141028] unwind: Unknown symbol address bf067284 [ 75.141036] unwind: Index not found bf067284 [ 78.120054] systemd-journald[457]: Received request to flush runtime journal from PID 1 [ 78.255026] unwind: Unknown symbol address bf067284 [ 78.269971] unwind: Index not found bf067284 [ 78.284717] unwind: Unknown symbol address bf067284 [ 78.299588] unwind: Index not found bf067284 [ 78.314816] unwind: Unknown symbol address bf067284 These messages about "Unknown symbol address bf067284" are repeated after this several times. 4) [ 107.079610] ------------[ cut here ]------------ [ 107.079645] WARNING: CPU: 1 PID: 1 at lib/dma-debug.c:614 debug_dma_assert_idle+0x148/0x1e0 [ 107.079655] vc4-drm soc:gpu: DMA-API: cpu touching an active dma mapped cacheline [cln=0x00c8acc0] [ 107.079659] Modules linked in: ebtable_filter ebtables ip6table_filter ip6_tables rc_cec vc4 snd_soc_core ac97_bus snd_pcm_dmaengine cec rc_core snd_pcm snd_timer snd soundcore brcmfmac drm_kms_helper brcmutil drm fb_sys_fops hci_uart cfg80211 syscopyarea sysfillrect btbcm sysimgblt btqca btintel bluetooth bcm2835_wdt ecdh_generic rfkill bcm2835_thermal bcm2835_rng leds_gpio xfs libcrc32c smsc95xx usbnet mii mmc_block sdhci_iproc dwc2 sdhci_pltfm crc32_arm_ce udc_core sdhci pwm_bcm2835 i2c_bcm2835 bcm2835 bcm2835_dma phy_generic [ 107.079932] CPU: 1 PID: 1 Comm: systemd Not tainted 4.14.0-0.rc3.git3.1.fc28.armv7hl #1 [ 107.079937] Hardware name: Generic DT based system [ 107.079973] [<c03131b4>] (unwind_backtrace) from [<c030d98c>] (show_stack+0x18/0x1c) [ 107.079995] [<c030d98c>] (show_stack) from [<c0b7e310>] (dump_stack+0xa0/0xd8) [ 107.080012] [<c0b7e310>] (dump_stack) from [<c0354024>] (__warn+0xe4/0x104) [ 107.080028] [<c0354024>] (__warn) from [<c0354080>] (warn_slowpath_fmt+0x3c/0x4c) [ 107.080045] [<c0354080>] (warn_slowpath_fmt) from [<c0711634>] (debug_dma_assert_idle+0x148/0x1e0) [ 107.080069] [<c0711634>] (debug_dma_assert_idle) from [<c04e59e8>] (wp_page_copy+0xfc/0x640) [ 107.080087] [<c04e59e8>] (wp_page_copy) from [<c04e74b8>] (do_wp_page+0x3a4/0x5ac) [ 107.080101] [<c04e74b8>] (do_wp_page) from [<c04ea810>] (handle_mm_fault+0xd28/0xde0) [ 107.080118] [<c04ea810>] (handle_mm_fault) from [<c0b9a980>] (do_page_fault+0x244/0x3b8) [ 107.080136] [<c0b9a980>] (do_page_fault) from [<c0301360>] (do_DataAbort+0x40/0xc0) [ 107.080151] [<c0301360>] (do_DataAbort) from [<c0b9a260>] (__dabt_usr+0x40/0x60) [ 107.080159] Exception stack(0xef113fb0 to 0xef113ff8) [ 107.080170] 3fa0: 02565dd0 02601bb8 02565df0 00000002 [ 107.080184] 3fc0: 02565df0 0260c920 02601bb8 befdd848 befdd850 b6f7aa48 02565dd0 02559508 [ 107.080196] 3fe0: b6dd38f4 befdd7c8 b6cd1e38 b6cc8f3c 20060010 ffffffff [ 107.080249] ---[ end trace 66ededa5d1568f0b ]--- [ 107.080253] Mapped at: [ 107.080345] vc4_bo_create+0xe4/0x198 [vc4] [ 107.080420] vc4_allocate_bin_bo+0x38/0x150 [vc4] [ 107.080494] vc4_v3d_bind+0x12c/0x20c [vc4] [ 107.080507] component_bind_all+0x138/0x220 [ 107.080581] vc4_drm_bind+0x88/0x130 [vc4] [ 108.193398] nf_conntrack version 0.5.0 (16384 buckets, 65536 max) kloczek -- Tomasz Kłoczko | LinkedIn: http://lnkd.in/FXPWxH

2 14

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

arm November 2017