April 2018 - arm - Fedora Mailing-Lists

Re: Raspberry Pi 3

by Chris Hall

Hello Peter, Have you created the wifi RPM yet if so where can it be obtained

6 years

2
1
0 / 0

what do i have to do to enable spi on fedora 27 on a raspberry pi

by adpdyj+4aw13di0ccx1w＠sharklasers.com

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

6 years

2
2
0 / 0

Fedora ARM & AArch64 Status Meeting Minutes 2018-04-10

by Paul Whalen

======================================================== #fedora-meeting-2: Fedora ARM and AArch64 Status Meeting ======================================================== Meeting started by pwhalen at 15:00:24 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-2/2018-04-10/fedora_arm_... . Meeting summary --------------- * roll call (pwhalen, 15:00:25) * 1) ==== Userspace Status ==== (pwhalen, 15:07:00) * [abrt] firefox: raise(): firefox killed by SIGSEGV (pwhalen, 15:07:21) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1564204 (pwhalen, 15:07:21) * elfutils FTBFS due to test failure. If anyone can help investigate. https://koji.fedoraproject.org/koji/taskinfo?taskID=25394458 (pwhalen, 15:14:39) * 2) ==== Kernel Status ==== (pwhalen, 15:10:16) * kernel-4.16.1-300.fc28 (pwhalen, 15:10:29) * LINK: https://koji.fedoraproject.org/koji/buildinfo?buildID=1067657 (pwhalen, 15:10:29) * Please test and report any issues to the list or #fedora-arm. (pwhalen, 15:20:58) * 3) ==== Bootloader Status ==== (pwhalen, 15:21:17) * uboot-tools-2018.03-4.fc28 (pwhalen, 15:21:54) * LINK: https://koji.fedoraproject.org/koji/buildinfo?buildID=1066876 (pwhalen, 15:22:00) * Known issue on Raspberry Pi 2/3/3+. (pwhalen, 15:22:25) * Improvement to MMC speed on Allwinner Devices. (pwhalen, 15:23:18) * 4) == F28 Testing == (pwhalen, 15:25:56) * Latest nominated nightly - Fedora 28 20180407.n.0 (pwhalen, 15:26:41) * LINK: https://fedoraproject.org/wiki/Test_Results:Fedora_28_Branched_20180407.n... (pwhalen, 15:26:41) * OpenQA AArch64 Server Tests (pwhalen, 15:27:08) * LINK: https://openqa.stg.fedoraproject.org/tests/overview?distri=fedora&version... (pwhalen, 15:27:08) * 5) == Open Floor == (pwhalen, 15:33:44) Meeting ended at 15:45:34 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * pwhalen (36) * pbrobinson (27) * jlinton (24) * zodbot (4) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

6 years

1
0
0 / 0

[Feedback on aarch64 image]

by pfrenard

Hello I wanted to try aarch64 image, but I had a small issue. When I used arm-installer, it triggered an error and did not complete, I discovered that vg name is fedora, but this is also the same name for my laptop... Perhaps adding aarch64 on the name could reduce the risk of conflicts "fedora_aarch64", it could also be a release number such as F28 "fedora_F28" or both "fedora_F28_aarch64" :) By the way, probably a stupid question, what are the differences between armhfp and aarch64 builds ? Fox

6 years

3
2
0 / 0

[Fedora 28/aarch64] [nfs/autofs feedback]

by Pierre-Francois RENARD

Hello guys, I tried to use autofs and nfs. I have the same issue with autofs as other guys, with SELinux. I had to change SELinux mode to permissive to be able to make autofs usable ... But I also discovered that by default mount.nfs and autofs are using NFSv4 and cannot switch to NFSv3. I had to add an option to /etc/sysconfig/autofs << OPTIONS=" -O vers=3" >> so autofs use by default NFSv3... Is it a normal behaviour or did I miss something ? Thanks Fox

6 years

3
3
0 / 0

Nouveau acceleration on armv7/aarch64

by Nicolas Chauvet

Hi there, FYI I've backported the tegra/nouveau support that has landed in mesa master recently on top of mesa-18.0 Here is a koji scratch build: https://koji.fedoraproject.org/koji/taskinfo?taskID=26171305 I'm testing it only on a jetson-tk1 (armv7hl) for now, using a 4.16.0 kernel. But in this case, I have the following message (that freeze the system). [ 1140.014947] nouveau 57000000.gpu: fifo: SCHED_ERROR 20 [] Because of that, I need to boot with rd.driver.blacklist=nouveau modprobe.blacklist=nouveau from cmdline. I'm trying to have it reported upstream. Even with nouveau disabled, and using the mesa with tegra backport, I'm able to run a wayland session on tegra. (very slowly). this was not the case before the mesa tegra backport as it fallback on Xorg. I don't think there is any improvement on SOC older than tegra k1. I haven't tried yet. I hope you can enjoy. PS: I think this is a little too much for backport the whole tegra support to the normal fedora package. But if it's something to consider, I can submit a PR on mesa... -- - Nicolas (kwizart)

6 years

2
1
0 / 0

aarch64 - fedora28 - Fedora-Server-28-20180327.n.0.aarch64.raw.xz

by Richard Ryniker

I can manually configure my Raspberry Pi model 3B-plus on-board wired Ethernet port to operate. It is indeed only DHCP configuration that fails, but only with the on-board device; DHCP configuration of a USB wired Ethernet port works fine. Curious.

6 years

3
4
0 / 0

RPi 3, Rawhide-20180330: hangs on "fb: switching to vc4drnfb from EFI VGA"

by Tomasz Kłoczko

Hi, Like it is in subject boot process stops on display "fb: switching to vc4drnfb from EFI VGA" Any suggestions/advices? kloczek -- Tomasz Kłoczko | LinkedIn: http://lnkd.in/FXPWxH

6 years

2
8
0 / 0

Fwd: Re: Raspberry Pi 3+

by Geoffrey Marr

Just for those following this email, I installed the Fedora Beta LXDE image on a RPI-3+, copied/modified the .dtb file, and booted with no issues on boot. Used a USB-to-Ethernet adapter to run "dnf update", which caused the onboard ethernet to start working. No trouble found so far. Will keep updated as I continue to mess with this... Geoff Marr IRC: coremodule ---------- Forwarded message ---------- From: Geoffrey Marr <gmarr(a)redhat.com> Date: Thu, Apr 5, 2018 at 10:26 AM Subject: Re: [fedora-arm] Re: Raspberry Pi 3+ To: Eric Sandeen <sandeen(a)redhat.com> Just for those following this email, I installed the Fedora Beta LXDE image on a RPI-3+, copied/modified the .dtb file, and booted with no issues on boot. Used a USB-to-Ethernet adapter to run "dnf update", which caused the onboard ethernet to start working. No trouble found so far. Will keep updated as I continue to mess with this... Geoff Marr IRC: coremodule On Mon, Apr 2, 2018 at 7:28 PM, Eric Sandeen <sandeen(a)redhat.com> wrote: > On 4/2/18 7:05 PM, Peter Robinson wrote: > > On Mon, Apr 2, 2018 at 7:42 PM, Tomáš Frolík <tomas.frolik2(a)gmail.com> > wrote: > >> Peter, I would like to as You, whether the onboard-wired-ethernet > problem on RPi3+ was solved in current F28 test release (31.3.2018). If > not, can You provide any indication when it could be? > > > > I don't know what you mean by "I would like to as You", please note > > that I provide the support for RPi in my own time as and when I have > > spare time. > > > > That said I did pull in some patches that should improve a bunch of > > things on the 3+but they're not in an official build just yet, you can > > get a scratch kernel [1] and report back whether they improved your > > situation. There's a couple of patches that might improve the wired > > lan but I've not currently got access to ethernet to test as I'm > > currently traveling. > > > > [1] https://koji.fedoraproject.org/koji/taskinfo?taskID=26121358 > > That kernel did fix the "mac address changes every reboot" for me. > And yes, the ethernet port does still work. ;) > Thanks! > > And the ethernet port LEDS ... I seem to have a flashing amber > activity LED, and the green LED is off. > > -Eric > _______________________________________________ > arm mailing list -- arm(a)lists.fedoraproject.org > To unsubscribe send an email to arm-leave(a)lists.fedoraproject.org >

6 years

1
0
0 / 0

Fwd: Re: Raspberry Pi 3+

by Geoffrey Marr

Just for those following this email, I installed the Fedora Beta LXDE image on a RPI-3+, copied/modified the .dtb file, and booted with no issues on boot. Used a USB-to-Ethernet adapter to run "dnf update", which caused the onboard ethernet to start working. No trouble found so far. Will keep updated as I continue to mess with this... Geoff Marr IRC: coremodule On Mon, Apr 2, 2018 at 7:28 PM, Eric Sandeen <sandeen(a)redhat.com> wrote: > On 4/2/18 7:05 PM, Peter Robinson wrote: > > On Mon, Apr 2, 2018 at 7:42 PM, Tomáš Frolík <tomas.frolik2(a)gmail.com> > wrote: > >> Peter, I would like to as You, whether the onboard-wired-ethernet > problem on RPi3+ was solved in current F28 test release (31.3.2018). If > not, can You provide any indication when it could be? > > > > I don't know what you mean by "I would like to as You", please note > > that I provide the support for RPi in my own time as and when I have > > spare time. > > > > That said I did pull in some patches that should improve a bunch of > > things on the 3+but they're not in an official build just yet, you can > > get a scratch kernel [1] and report back whether they improved your > > situation. There's a couple of patches that might improve the wired > > lan but I've not currently got access to ethernet to test as I'm > > currently traveling. > > > > [1] https://koji.fedoraproject.org/koji/taskinfo?taskID=26121358 > > That kernel did fix the "mac address changes every reboot" for me. > And yes, the ethernet port does still work. ;) > Thanks! > > And the ethernet port LEDS ... I seem to have a flashing amber > activity LED, and the green LED is off. > > -Eric > _______________________________________________ > arm mailing list -- arm(a)lists.fedoraproject.org > To unsubscribe send an email to arm-leave(a)lists.fedoraproject.org >

6 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

arm April 2018