> I’m in the process to create a new documentation for Fedora Server (cf
> https://docs.fedoraproject.org/en-US/fedora-server/) and want to add one or
> two articles about how to use ARM and Fedora Server. I’m new to the ARM
> architecture and had to learn that both boxes I have access to for
On Fri, May 7, 2021 at 2:17 PM Matthew Miller wrote:
>
> On Fri, May 07, 2021 at 07:01:52AM +0200, Michal Toman wrote:
> > - USB-C charging does not work. I tried 4 random chargers I have had
> > around - 2 of them seem to do absolutely nothing when plugged in, 2 of
> > them have the device
On Wed, May 5, 2021 at 2:21 PM Peter Robinson wrote:
>
> On Wed, May 5, 2021 at 2:11 PM Jonathan Rioux wrote:
> >
> > @PeterRobinson
> > By querying pacman, I get that package uboot-pinebookpro-bsp 1.5-8 is
> > installed on my new machine.
> > There seems to
On Wed, May 5, 2021 at 2:11 PM Jonathan Rioux wrote:
>
> @PeterRobinson
> By querying pacman, I get that package uboot-pinebookpro-bsp 1.5-8 is
> installed on my new machine.
> There seems to be a 2021.4-1 package available also.
>
> Ok, for nvme and deep sleep; it seems it needs bsp patches for
> I have a few questions :
> 1) Is it mandatory to upgrade U-boot, on newer pbp ?
Yes, if you want assistance, I have no idea what manjaro uses, I do
know it's on the EMMC.
> 2) Can I know what version it has without serial port ? Missing config file
> for fw_printenv.
The Fedora one? It's
Could you please trim your emails of unnecessary text!
> > U-Boot 2021.04 (Apr 28 2021 - 00:00:00)
> U-Boot TPL 2021.04 (Apr 21 2021 - 00:00:00)
> Channel 0: LPDDR4, 50MHz
> BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
> Channel 1: LPDDR4, 50MHz
> BW=32 Col=10 Bk=8 CS0
On Tue, May 4, 2021 at 3:45 PM Andreas Reschke wrote:
>
>
> Am 04.05.21 um 13:39 schrieb Peter Robinson:
> > For those that are interested here is the write up for getting
> > Pinebook Pro running Fedora:
> >
> > https://nullr0ute.com/2021/05/fedora-on-the-pineboo
For those that are interested here is the write up for getting
Pinebook Pro running Fedora:
https://nullr0ute.com/2021/05/fedora-on-the-pinebook-pro/
Feel free to reply on this thread for questions.
___
arm mailing list -- arm@lists.fedoraproject.org
On Sat, Apr 10, 2021 at 4:33 PM Massi aka Ergosum
wrote:
>
> Il giorno sab 10 apr 2021 alle ore 13:24 Peter Robinson
> ha scritto:
> >
> > I don't know what Purism is doing, they've made some choices around
> > their HW which is frankly quite strange,
On Sat, Apr 10, 2021 at 12:09 PM Massi aka Ergosum
wrote:
>
> Il giorno lun 5 apr 2021 alle ore 23:22 Peter Robinson
> ha scritto:
> >
> > On Thu, Mar 25, 2021 at 10:30 AM Massimiliano
> > wrote:
> > >
> > > I'm trying to understand if it's possibl
; ha scritto:
> >
> > Il giorno ven 19 mar 2021 alle ore 11:30 Peter Robinson
> > ha scritto:
> > >
> > > On Fri, Mar 19, 2021 at 10:24 AM Massimiliano
> > > wrote:
> > >
> > > No, I mean general andorid consumer phones aren't
>
On Sun, Mar 28, 2021 at 7:28 PM Gerhard Wiesinger wrote:
>
> Hello,
>
> I tried to move from Ubuntu to Fedora (33 and 34 Beta 1) but Linux
> doesn't boot:
>
> Installer commands for F33 oder F34Beta1::
>
> fedora-arm-image-installer --image=Fedora-Server-33-1.3.aarch64.raw.xz
> --target
On Sun, Mar 28, 2021 at 2:06 AM Zach Villers wrote:
>
> Apologies if I've been lazy at googling, but are there tests that can be run
> for F34 aarch 64?
They should be the standard server tests that are run on x86_64 and
other arches.
___
arm mailing
On Fri, Mar 19, 2021 at 10:24 AM Massimiliano wrote:
>
> Thanks Peter.
>
> > From the Arm PoV that statement is still mostly correct, but it's
> > nuanced as there's group that is focusing on some of those devices. I
> > think there will be a focus in that group on actively open phones, I
> >
Hi Massi,
> Hello folks!
> I just got my Librem 5, after a long time. I know that is not a
> priority (from [1]):
>
> "We don't directly support devices such as phones and tablets but it's
> not to say that without the required kernel/bootloader know how that
> they don't work, it's just not our
On Sun, Mar 7, 2021 at 5:53 PM Matthew Miller wrote:
>
> On Sun, Mar 07, 2021 at 05:28:24PM +, Peter Robinson wrote:
> > > On the other hand, I tried writing a Fedora image onto an SD card and
> > > booting an RPI 4 from it and it worked flawlessly. So maybe the docs
On Sun, Mar 7, 2021 at 4:24 PM Ondřej Budai wrote:
>
> Hello guys,
>
> is Raspberry Pi 4 officially supported by Fedora? Both docs[1] and wiki[2]
> don't mention Pi 4 as supported. The wiki even says that "We do not (as of
> 30th October 2019) support the Raspberry Pi 4 in any Fedora
On Fri, Mar 5, 2021 at 8:12 PM David W. Legg wrote:
>
> So, I installed Fedora-Minimal-33-1.3.aarch64.raw.xz on my RPI4, fully
> updated it (05/03/2021) turned on root logins using ssh and turned off
> selinux.
>
> It boots nicely and lets me login etc., until I try and boot without a
> monitor
Hi All,
Just a heads up for those that have a brcmfmac, the Cypress variants
of these WiFi modules (there's 3 vendors that make them: Broadcom,
Cypress/Infineon and now Synaptics) have got new firmwares, I'm giving
a heads up because in some cases the firmwares are being updated from
firmwares
On Wed, Jan 27, 2021 at 2:34 PM Jon Masters wrote:
>
> On Wed, Jan 27, 2021 at 6:38 AM Peter Robinson wrote:
>
>> Now Fedora Arm in a VM on an Apple M1 Mac is definitely something that
>> I'd love to support, and while my time to actively hack on it of late
>> has b
1] https://rosenzweig.io/blog/asahi-gpu-part-2.html
> Carvel
>
> On Jan 26, 2021, at 6:30 PM, Peter Robinson wrote:
>
> Welcome Carvel,
>
> Is there anything in particular that interests you or excites you that
> you'd like to see improvements where you feel you may be able to
&
Welcome Carvel,
Is there anything in particular that interests you or excites you that
you'd like to see improvements where you feel you may be able to
contribute with some guideance?
Peter
On Tue, Jan 26, 2021 at 1:35 PM Carvel Baus wrote:
>
> Hello,
>
> Just wanted to introduce myself as I
On Wed, Jan 20, 2021 at 6:53 PM Joel Savitz wrote:
>>
>> So it's going to take me a few days to reply, what I think I'll if
>> that's OK do a theme per reply. Do you have a list of hardware you
>> currently have available? HATs, sensors etc?
>
> We have a couple of senseHATs, some lights,
On Fri, Jan 22, 2021 at 7:51 PM Stefan Wahren wrote:
>
> Am 15.01.21 um 20:21 schrieb Peter Robinson:
> >
> > The RPi4 has changed this up some and the 3D render unit is now driven
> > by the v3d component and associated driver, and the display engine and
> > b
Hi Andreas,
> i want to try install 32 Bit software ( Moneyplex = Homebanking
> software) on my Fedora aarch64 system. This didn't work.
>
> [andreas@pinebook-pro moneyplex]$ ll
> total 22468
> -rwxr--r--. 1 andreas andreas 7543589 Jan 21 2020 Handbuch.pdf
> -rwxr-xr-x. 1 andreas andreas
Hey Adam,
Sorry for the delayed reply here. I wanted to reply properly, then it
got lost in my inbox.
> Hey folks! Just a heads up that I merged a branch I've had lying around
> for weeks that enables *some* of the openQA desktop tests on the
> aarch64 Workstation image.
Thanks for this, it's
On Mon, Jan 18, 2021 at 6:59 PM Joel Savitz wrote:
>>
>> Have you had any engagement with upstream (not Fedora) maintainer of
>> RPi.GPIO?
>
> As our project is a total rewrite of RPi.GPIO we have not yet interacted with
> the original upstream maintainer, but that's a good suggestion. I'll
> Sorry for not being clear. Yes, I mean the Tianocore firmware.
So I've added Jeremy to my reply as he's the maintainer of this
firmware but as it's EDK2 and ACPI, as opposed to device tree, I'm not
sure it's intended to work.
As the driver would need ACPI support and the firmware would need
On Fri, Jan 15, 2021 at 8:12 PM Eberhard Schruefer
wrote:
>
> Thanks for the explanations and the link. As I wrote it works out of the box
> when doing a *non* UEFI install. My question, however, is about an
> installation that uses the RPI UEFI firmware. I tried things like enabling
>
> Fedora 33 Workstation on the RPI4 with UEFI runs fine for me. However, I
> can't figure out how to get accelerated video working. Without UEFI, Fedora
> 33 with kernel 5.10.7 seems to enable accelerated video without any further
> configuration. There is a /boot/efi/config.txt in this case.
Hi Joel,
I've taken the group off as I'm not a member.
> A group of computer science undergraduates and I are interested in
> contributing to the usability of Fedora Linux on the Raspberry Pi 4.
>
> I was a part of this group as an undergrad and we developed a compatibility
> layer for
Hi Zach,
> I recently got Fedora 33 Server booting on my RPI 4 - 8G using the RPI4 UEFI
> firmware. The usb3 adapter I used worked fine with Raspbian, but with Fedora
> 33, there was an issue. I've worked around this issue and another involving
> F33 complaining about the lack of sd card.
This is cancelled this week.
On Sun, Dec 27, 2020 at 3:00 PM wrote:
>
> Dear all,
>
> You are kindly invited to the meeting:
>Fedora ARM & AArch64 status meeting on 2020-12-29 from 15:00:00 to
> 16:00:00 UTC
>At fedora-meetin...@irc.freenode.net
>
> The meeting will be about:
> Fedora
On Fri, Dec 11, 2020 at 2:13 PM Sam Varshavchik wrote:
>
> Derek Atkins writes:
>
> > Connect a USB keyabord and HDMI monitor and login via console.
>
> Thanks. I already had a monitor connected, but didn't have a USB keyboard
> plugged in. Figured I'd see how it boots first, before rooting
Hi Adrian,
> Hi! While theoretically should be possible, i would like to hear some
> confirmation that f33 can work on odroid N2 ...
I've not seen direct confirmation of Fedora 33 on this device but I
have had reports of prior releases working in the past so I don't
forsee any major issues.
>
On Sun, Dec 20, 2020 at 2:53 PM Antonio T. sagitter
wrote:
>
> Hi all.
>
> I can't compile IceCat on ARM-Rawhide branch (it's an issue related to
> GCC-11?) because of this error:
>
> 167:32.34
> /usr/lib/gcc/armv7hl-redhat-linux-gnueabi/11/include/arm_neon.h: In
> function ‘poly64x1_t
Hi Benson,
> Anyone with experience running Fedora on Olimex:
> https://www.olimex.com/Products/DIY-Laptop/
It hasn't come up before that I can remember, but we do enable all the
pieces so it may work. Upstream support looks reasonably complete, it
appears to have display support upstream,
On Mon, Dec 14, 2020 at 12:39 PM Daan Hoogland wrote:
>
>
> On 2020/12/10 09:51, berend wrote:
> >
> > On Thu, 10 Dec, 2020 at 08:19, Peter Robinson
> > wrote:
> >> To answer "when will it be supported" is currently an unanswerable
> >> qu
> I am fedora Mate-Compiz spin maintainer and i'd like to test the spin with
> fedora arm image on RockPro64 from https://www.pine64.org/rockpro64/
> There is an extra wifi/bt modul
> https://pine64.com/product/rockpro64-1x1-dual-band-wifi-802-11ac-bluetooth-5-0-module/?v=0446c16e2e66
> Do you
Hi,
>I have been testing F33 on Raspberry Pi 4 8GB and seems to be booting
> fine, but it is still very unstable. I have been reading the Fedora Meetbot
> meeting notes, and monitoring the Wiki for updates, but still no updates on
> the Wiki since Oct of this year. On which Fedora
On Wed, Nov 18, 2020 at 8:22 AM Michael Whapples
wrote:
>
> I have looked through the source of the arm-image-installer and now
> understand exactly what it is doing and yes I see how it really is not
> suited to setting the FS, the image determines that.
>
>
> BTRFS versions of the minimal
On Mon, Nov 16, 2020 at 7:27 PM ITwrx wrote:
>
> On 11/16/20 12:06 PM, Peter Robinson wrote:
> > We don't support it yet, the device tree isn't upstream in the kernel
> > and there's no upstream U-Boot as yet.
>
> did you see my post from 11/2/2020 about my orange pi r
> I've tried to boot / install Fedora-Server-netinst-aarch64-33-1.2.iso on
> my Helios64. Boot starts fine but after few seconds it stops with errors
> in dracut shell.
>
> fedora1.txt is complete bootlog
> rdsosreport.txt is the generated file from dracut.
>
> Does anybody has a tip to resolve
On Sat, Nov 14, 2020 at 9:43 PM Michael Whapples
wrote:
>
> Neal and Matthew thanks for clarifying that. Yes the various
> announcements do say desktop editions, the significance of that must
> have just passed me by.
>
>
> would be nice if the ARM image installer would allow selecting the FS
>
On Fri, Oct 30, 2020 at 11:31 PM Adam Williamson
wrote:
>
> Hi folks!
>
> A few of you have seen this already, but just wanted to send out a
> wider announcement: having been deservedly shamed by pbrobinson, I
> spent most of this week working on aarch64 testing in openQA, and am
> happy to
On Tue, Oct 27, 2020 at 6:04 PM Andreas Reschke wrote:
>
> Am 29.09.20 um 23:08 schrieb Peter Robinson:
>
> Hi there,
>
> I've a well good working Fedora 32 installation an my Pinebook Pro.
>
> Hi Andreas,
>
> I'm interested in replacing the pre-installed OS.
On Mon, Oct 26, 2020 at 7:47 PM Karl Li wrote:
>
> Sorry, yes, it is in fact the Pine64+ board; don't know why I brainfarted and
> called it Pine64 Pro (multiple times!)
>
> Good to know that this is a known issue; I'll sit tight and stay on 5.6.6-300
> until things clear up in a later kernel.
On Sat, Oct 24, 2020 at 9:38 PM Karl Li wrote:
>
> Hello all!
>
> I noticed that on a pine64-pro board running aarch64 Fedora 32, ethernet is
> broken with the latest set of patches installed through dfn update. To
> reproduce:
>
> 1. Download the latest Fedora-Minimal-32-1.6.aarch64.raw.xz
> System is Pine64+ with Allwinner A64 SoC.
> kernel 5.7.15-sunxi64
>
> Fedora 32 is booting and running on this sdcard based system. However it is
> using a very small part of the 64GB sd card. I am looking for suggestions on
> how to utilize the non-partitioned space. Manjaro seems to have a
Hey,
Sorry about the late reply on this.
> A while ago (around the freeze of FC29) grub2-efi on top of Uboot was
> proposed as the (potentially) default setup for armhfp too. Unfortunately
> (IMHO) it did not materialize and I'm searching for the game-breaker.
>
> On buggzilla found a few
On Sun, Oct 4, 2020 at 9:30 PM brm wrote:
>
> This is the original Pine64+ 2GB model. Is has SD Card only no emmc. As far
> as I know it uses the Arm Allwinner chip - V8.
The chip in the Pine64+ is the Allwinner A64 SoC, ARMv8 is the overall
designator for the generation of chip ISA that
> Has anyone booted a newer Fedora raw image on the Pine64 Allwinner V8? I
> cannot get anything working here. I have tried many Fedora aarch64 releases -
> Fedora 32 Fedora beta 33 etc.
What do you mean by Pine64 Allwinner V8? Which model? Which image, how
did you write out the image? Please
> > Hi there,
> >
> > I've a well good working Fedora 32 installation an my Pinebook Pro.
> >
>
> Hi Andreas,
>
> I'm interested in replacing the pre-installed OS. If that is what
> you've done, and you can point me to a step-by-step guild, I would
> appreciate a link.
I have Fedora 33 running on
> I'm trying to set up a Raspberry Pi 3B (or a 3B+) to run an Elgato Stream
> Deck (if you've never heard of that it's basically a fancy macro keyboard).
> I've had no problems using the Stream Deck on my x86_64 desktop (Fedora 32)
> and on a Raspberry Pi 3B or 3B+ running Raspbian (kernel
Hi,
> I've a well good working Fedora 32 installation an my Pinebook Pro. I
> want to replace the custom kernel with official fedora one. But it's not
> working.
>
> Failure: Bad Linux ARM64 Image magic!
We don't support extlinux.conf on aarch64, not sure how you set it up
but you'll need to
> libhybris systems don't have libGL.so at all. It is for "regular"
> Android devices transformed to glibc Linux through libhybris. So, when
> compiling anything that links to libGL, I get into trouble.
What is the hardware that you want to use via libhybris? Ultimately
libhybris is not something
> I intend to update this wiki page:
>
> https://fedoraproject.org/wiki/Architectures/ARM/Raspberry_Pi
>
> to clarify that the Raspberry Pi 4 does run Fedora 32 aarch64.
Yes, but three's a lot that doesn't work so please do not update it
(unless you want to do the support for all the queries).
>
On Wed, Aug 12, 2020 at 5:21 PM Peter Bowden wrote:
>
> Thanks Peter. I did figure that out yesterday. Symlink seemed to work. I also
> pulled in
> https://github.com/RPi-Distro/firmware-nonfree/blob/master/brcm/brcmfmac43455-sdio.txt
> as well.
>
> I did run into issues with wifi, but I'd
..@gmail.com
>
>
> On Wed, Aug 12, 2020 at 4:19 AM Peter Robinson wrote:
>>
>> > Taking a stab at fedora 32 on a R Pi 3A+. Looks like there's missing
>> > firmware. Based on the FAQ the wifi should work out of the box but it
>> > doesn't seem to be th
> Taking a stab at fedora 32 on a R Pi 3A+. Looks like there's missing
> firmware. Based on the FAQ the wifi should work out of the box but it doesn't
> seem to be the case:
>
> [ 43.501327] brcmfmac mmc1:0001:1: Direct firmware load for
>
> Thanks everyone for the lightning quick replies. I saw am335x_evm but assumed
> that was for a specific eval board. I'll give it a shot!
The am335x_evm firmware currently supports the following list of devices:
am335x-bone.dtb
am335x-boneblack.dtb
am335x-pocketbeagle.dtb
> > Hi All - What's the status of support for Fedora on Beaglebone Black? I
> > find references to a old version working on BBB, but nothing recently.
> > Anyone working on making it function?
>
> According to this issue
> https://pagure.io/arm-image-installer/issue/60
>
> BeagleBone Black is
> As stated here [1], in order to use HATs, and overlays in general on
> the Raspberry, you have to remove the /boot/dtb symlink.
> You know, I'm not an expert. What does this mean? Why do you need to do
> that? Why this symlink is here by default? And, there are some
> downsides by removing such
> > After successfully testing an OpenVPN link on a x86_64, I get the following
> > error on aarch64, as root:
> >
> > # nmcli connection import type ovpn file .ovpn
> > Error: failed to find VPN plugin for ovpn.
>
> So having tried that same command with a openvpn profile I use daily I
> had a
> After successfully testing an OpenVPN link on a x86_64, I get the following
> error on aarch64, as root:
>
> # nmcli connection import type ovpn file .ovpn
> Error: failed to find VPN plugin for ovpn.
So having tried that same command with a openvpn profile I use daily I
had a look at the
On Mon, Aug 3, 2020 at 11:24 PM Sam Varshavchik wrote:
>
> I'm running an F32 aarch64 guest qemu VM on an x86_64 F32 host, and, in that
> VM, I attempted to build something fairly simple via mock. This is my reward:
>
> configure:3590: gcc -O2 -g -pipe -Wall -Werror=format-security -Wp,-
>
e CMA/DMA issue.
> cma=256M@704M has no effect.
>
>
>
> On Mon, Aug 3, 2020 at 9:28 AM Peter Robinson wrote:
>>
>> On Sun, Aug 2, 2020 at 9:20 PM wrote:
>> >
>> > Further to those Fedora32 efforts described as below. I have been quite
>> > ha
7, 2020 at 4:03 PM
> Subject: [fedora-arm] Re: CMA on raspberry pi 4
> To: Peter Robinson
> Cc: Fedora List
>
> On Thu, May 7, 2020 at 11:23 AM Peter Robinson wrote:
>>
>> Hi Thomas,
>>
>> >> > I have looked into the CMA setting issue a bit. T
On Tue, Jul 28, 2020 at 10:51 AM brm wrote:
>
> Booted into the Armbian image today - 5.4.43-sunxi64. The wlan0 was able to
> be activated ok.
> Dmesg had some detail of the module being loaded. This is much the same as
> appears in Fedora.
>
> Jun 7 18:11:54 localhost kernel: [8.369702]
On Tue, Jul 28, 2020 at 12:01 AM Sam Varshavchik wrote:
>
> Paul Whalen writes:
>
> >
> >
> > - Original Message -
> > > > I'm trying to install an aarch64 guest VM on F32 x86-64 host.
> > > >
> > > > I created a suitably large disk image, then proceeded to:
> > >
> > >
> > >
> > > > I
> I'm trying to install an aarch64 guest VM on F32 x86-64 host.
>
> I created a suitably large disk image, then proceeded to:
> I surmize that arm-image-installer expected a real /dev to write to,
> instead of what is effectively a plain fie, so it failed to mount the disk
> image. I suppose
> I need to update the firmware of a fan for the RPi4 and given the below
> instructions in Raspbian. I also installed
>
> sudo dnf -y install i2c-tools
> sudo dnf -y install python3-i2c-tools
>
> but the firmware update fails. I guess, it is because of the serial port not
> being enabled. Any
> Where to look . . . lspci does not return a result. Should I see a device in
> dmesg ? Nothing so far.
It's attached via SDIO not PCI so you wouldn't expect it to be visible
via a tool like lspci.
Also there's a completely different r8723cs driver that is not
upstream, I think that the
On Wed, Jul 8, 2020 at 8:55 AM Andreas Reschke wrote:
>
> Am 02.06.20 um 16:36 schrieb Peter Robinson:
>
> On Tue, Jun 2, 2020 at 3:22 PM Andreas Reschke wrote:
>
>> Am 28.04.20 um 16:35 schrieb Peter Robinson:
>> >>>>> To summarise where we are for e
roving the situation they are very
welcome to come and engage and participate.
> On Mon, Jul 6, 2020 at 8:05 AM Peter Robinson wrote:
> >
> > > Hi all,
> > > Why Rock64 board has been removed from supported HW?
> > > The commit date is 2020-06-26,
>
> Hi all,
> Why Rock64 board has been removed from supported HW?
> The commit date is 2020-06-26,
> https://pagure.io/arm-image-installer/c/21c1c9a162332f0a841b0097e61f8959bc472965?branch=master
>
> No more way to install Fedora on Rock64?
It didn't work previously, it was purely an incorrect
> Perhaps it's too early to speculate, but with the recent release of
> information that Apple will be transitioning from Intel-based CPUs to their
> own, custom ARM chips, I wonder if anyone deeper in the know (pbrobinson,
> pwhalen, others?) could speak to the continuing of Fedora on the Mac
On Fri, Jun 26, 2020 at 2:57 PM Nicolas Chauvet wrote:
>
> HI,
>
> FYI, I've found an issue with the current kernel 5.6.x (maybe earlier)
> the as3722_regulator module isn't added by dracut in hostonly mode (it
> is added as all others regulators)
>
> I need to add this:
> cat
On Fri, Jun 26, 2020 at 5:42 AM Florian Fainelli wrote:
>
>
>
> On 6/25/2020 4:23 PM, Peter Robinson wrote:
> >> I'm having troubles with the Banana Pi-R1 router with newer kernels. No
> >> config changes, config works well since a lot of lernel updates ...
>
> I'm having troubles with the Banana Pi-R1 router with newer kernels. No
> config changes, config works well since a lot of lernel updates ...
> Banana Pi-R1 is configured via systemd-networkd and uses the DSA
> (Distributed Switch Architecture) with b53 switch. No visible difference
> in
On Tue, Jun 2, 2020 at 3:22 PM Andreas Reschke wrote:
> Am 28.04.20 um 16:35 schrieb Peter Robinson:
> >>>>> To summarise where we are for everyone, with other deadlines I ran
> out
> >>>>> of time to really polish this for F-32, it does actually boot
Firstly your jsg...@fedoraproject.org bounces, I think that's because
you've not agreed to the contributor agreement, so could you resolve
that one way or the other.
> I don't get a kernel panic, but rather a segv on a systemd-udevd thread
> related to eth0 that does not kill systemd-udevd nor
> > How difficult would it be to add armhfp to the CoreOS builds? If you're
> > interested in the use case, it's for the third and fourth generation
> > OLPC laptops, the XO-1.75 and XO-4, both of which are based on Marvell
> > MMP, and are 32-bit, with ~1GB RAM. As of Fedora 32, stock Fedora
Hi John,
> Fresh install of Fedora 32 on a Xilinux Zynq (Trenz Electronics TE0726-03M
> zynqberry).
> systemd 245.4-1 has a segmentation fault on boot.
It sounds similar to this bug [1] but I've not looked closely.
Peter
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1831239
> Downgrading
>> Am 12.05.20 um 08:56 schrieb Peter Robinson:
>> >> everytime I boot my Raspi I have to wait a few minutes till the kernel
>> >> start to boot.
>> >>
>> >> Last line is:
>> >>
> everytime I boot my Raspi I have to wait a few minutes till the kernel
> start to boot.
>
> Last line is:
>
> genet@7d58 Waiting for PHY auto negtiation to complete
>
> .
>
> there are more then 150
>> >> > I have looked into the CMA setting issue a bit. This is what I have
>> >> > found so far.
>> >> >
>> >> > The rpi4 needs CMA to be in ZONE_DMA (lower 1GB of memory) as this is
>> >> > the only area that the peripherals on the rpi4 can address.
>> >> >
>> >> > The DT sets the allowed
> "workaround" is a slight understatement. The RPi works and performs very well
> with it on Fedora 32!
Please keep the thread on topic. If you think it performs "very well"
you've either got very low expectations or will be thrilled when it's
got accelerated graphics. There's a LONG way to go!
Hi Thomas,
>> > I have looked into the CMA setting issue a bit. This is what I have found
>> > so far.
>> >
>> > The rpi4 needs CMA to be in ZONE_DMA (lower 1GB of memory) as this is the
>> > only area that the peripherals on the rpi4 can address.
>> >
>> > The DT sets the allowed range to
> >> I was looking for a fanless TV with modern software, but it looks hard
> >> to get an ARM based one :-(
> >>
> >> Looks like the fastest board that could be supported by Fedora is the
> >> rockpro64 (check?). But even then widevine is only available in 32 bits
> >> for chromium.
> >
> >
> I was looking for a fanless TV with modern software, but it looks hard
> to get an ARM based one :-(
>
> Looks like the fastest board that could be supported by Fedora is the
> rockpro64 (check?). But even then widevine is only available in 32 bits
> for chromium.
Unfortunately there's not much
Hi Rafael,
> I recently got an ODROID-N2 but forgot to first check if it was possible
> to run recent linux distros on it.
>
> I am happy with Fedora on my raspberry pi 4, so that would be my first
> choice. I now see that the N2 is not support and that booting it
> requires a few binary blobs:
>
> > >> To summarise where we are for everyone, with other deadlines I ran out
> > >> of time to really polish this for F-32, it does actually boot on
> > >> Fedora 32 but there's an issue with display output I've not got to the
> > >> bottom of as yet. I'm hoping to catch up and I'll do a remix
Hi Thomas,
> I have looked into the CMA setting issue a bit. This is what I have found so
> far.
>
> The rpi4 needs CMA to be in ZONE_DMA (lower 1GB of memory) as this is the
> only area that the peripherals on the rpi4 can address.
>
> The DT sets the allowed range to allocate the CMA from
>
Hi Ben,
> I've been trying without success to get the F32 Workstation RC1.6 (tomorrow's
> release) installed on my Pinebook Pro. If anyone here has done it, do you
> have instructions written up somewhere?
I have done it but it's all from serial console so it doesn't make it
an overly useful
> > Yep, I've seen the upstream discussion, I'll test the patches on my
> > revB1 when I get a moment, I've asked in the community if there's
> > someone with a revC to test. I suspect with the delays we might well
> > have another U-Boot build. Any chance you could do a bug report for me
> >
Hi Ben,
> I've been asked in a GitHub issue[1] if there is any work in progress
> (or if someone wants to take a look) for getting the GPIO libraries
> for Raspberry Pi working on Fedora. Someone subsequently posted a link
> to a BZ[2] where Peter said "the RPIO._GPIO module needs to be updated
>
graphical systems.
> On Fri, Apr 17, 2020 at 1:17 PM Peter Robinson wrote:
>>
>> On Fri, Apr 17, 2020 at 12:13 PM wrote:
>> >
>> > Thanks for that! In one of latest images it gets stuck at the point shown
>> > in the attached screenshot.
>>
>&
> All this talk about Wandboard Quad D1 is because I'm trying to upgrade an
> existing device currently running on a Wandboard Dual C1. It's a system
> that started as Fedora 25 and was upgraded to Fedora 31 (via dnf
> system-upgrade). It's been running fine on the Dual. I upgraded the
> U-boot
> >> He saved me hours and sent me files to test and they worked. So he's
> >> preparing a patch to send to the u-boot list. Hopefully that patch can
> >> get pulled into Fedora 32?
> >
> > We don't tend to build U-Boot once a release goes GA, primarily just
> > due to lack of resources. That
201 - 300 of 1647 matches
Mail list logo
