#fedora-meeting-2: Fedora ARM and AArch64 Status Meeting
Meeting started by pwhalen at 15:00:30 UTC. The full logs are available
On Fri, Jan 14, 2022 at 10:55 AM David W. Legg wrote:
> So, then I reverted to my working 5.14.10 kernel and did a:
>
> dnf update --exclude=kernel*
>
> which included an update up to:
>
> uboot-images-armv8-2021.10-2.fc35.noarch
>
uboot-images-armv8-2021.10-2.fc35 was our release version,
On Thu, Jan 13, 2022 at 11:12 AM David W. Legg wrote:
> So, here is my (temporary) solution, as reported in Bugzilla bug
> https://bugzilla.redhat.com/show_bug.cgi?id=2011423
>
> So my 4GB rpi4 refused to boot with the symptoms described about, i.e.
> mmc0 errors.
>
> I also found that
Apologies, I am unable to attend the meeting this morning. Proposing we
either cancel, or if someone else would like to run the meeting, please
reply to this email.
Paul
On Sun, Jan 9, 2022 at 10:00 AM wrote:
> Dear all,
>
> You are kindly invited to the meeting:
>Fedora ARM & AArch64
On Sun, Jan 2, 2022 at 4:58 PM RENARD Pierre-Francois
wrote:
> Hello guys,
>
>
> I have been working on a very strange issue when booting Fedora 35 on RPI4.
>
>
> I have the issue on 5 different RPI 4 boards, I have tried to swap
> power, network cable, network port, network switch, even use a
On Tue, Dec 14, 2021 at 1:51 PM Ben Beasley wrote:
> >> - Wayland
> >>
> >> Content of window ist missing, windows has to resize to show content,
> older X11 works fine.
> > What desktop or compositor? Need more details.
>
> I had similar Wayland problems after upgrading to F35 on PineBook Pro.
Proposing we cancel the meeting tomorrow. If you have something urgent to
discuss and would like to run the meeting, please reply to this email to
let everyone know.
Thanks,
Paul
___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an
With many contributors off this week for the Thanksgiving Holiday in the
US, proposing we cancel the meeting today.
Paul
On Sun, Nov 21, 2021 at 10:01 AM wrote:
> Dear all,
>
> You are kindly invited to the meeting:
>Fedora ARM & AArch64 status meeting on 2021-11-23 from 15:00:00 to
>
#fedora-meeting-2: Fedora ARM and AArch64 Status Meeting
Meeting started by pwhalen at 15:00:41 UTC. The full logs are available
#fedora-meeting-2: Fedora ARM and AArch64 Status Meeting
Meeting started by pwhalen at 15:01:41 UTC. The full logs are available
#fedora-meeting-2: Fedora ARM and AArch64 Status Meeting
Meeting started by pwhalen at 15:00:25 UTC. The full logs are available
To those testing Fedora 35 on armhfp,
The grub2 update in updates-testing (grub2-2.06-4.fc35) fixes a kernel
alignment issue on AArch64, but unfortunately breaks the boot on 32-bit
arm[1] and should be excluded when updating until a fixed build is
available.
Paul
[1] -
#fedora-meeting-2: Fedora ARM and AArch64 Status Meeting
Meeting started by pwhalen at 15:00:18 UTC. The full logs are available
I don't think we have anything pressing to discuss, proposing we take this
week off and cancel the meeting.
On Sun, Jun 6, 2021 at 11:01 AM wrote:
> Dear all,
>
> You are kindly invited to the meeting:
>Fedora ARM & AArch64 status meeting on 2021-06-08 from 15:00:00 to
> 16:00:00 UTC
>
#fedora-meeting-2: Fedora ARM and AArch64 Status Meeting
Meeting started by pwhalen at 15:01:12 UTC. The full logs are available
Hi Everyone,
Please help to test the Fedora 34 RC on your favourite ARM or AArch64
device, and add your results to the Fedora Wiki:
https://fedoraproject.org/wiki/Test_Results:Fedora_34_RC_1.1_Summary
All testing is greatly appreciated!
Thanks!
Paul
- Original Message -
> On Thu,
#fedora-meeting-2: Fedora ARM and AArch64 Status Meeting
Meeting started by pwhalen at 15:00:26 UTC. The full logs are available
at
#fedora-meeting-2: Fedora ARM and AArch64 Status Meeting
Meeting started by pwhalen at 15:00:54 UTC. The full logs are available
at
#fedora-meeting-2: Fedora ARM and AArch64 Status Meeting
Meeting started by pwhalen at 15:02:20 UTC. The full logs are available
at
#fedora-meeting-2: Fedora ARM and AArch64 Status Meeting
Meeting started by pwhalen at 15:00:14 UTC. The full logs are available
at
#fedora-meeting-2: Fedora ARM and AArch64 Status Meeting
Meeting started by pwhalen at 15:00:55 UTC. The full logs are available
at
Hi Alan,
- Original Message -
> I have a new Rasberry Pi 4b with 8gigs of ram. I installed the Fedora
> 33 1.3 image. Everything installs ok. Reboots fine. No problems.
>
> If I update using dnf, video no longer works. (I get a corrupted
> screen.)
>
> Is this a known issue?
Yes,
This meeting is cancelled.
Happy Holidays everyone! See you next year.
Paul
- Original Message -
> Dear all,
>
> You are kindly invited to the meeting:
>Fedora ARM & AArch64 status meeting on 2020-12-22 from 15:00:00 to
>16:00:00 UTC
>At fedora-meetin...@irc.freenode.net
#fedora-meeting-2: Fedora ARM and AArch64 Status Meeting
Meeting started by pwhalen at 15:00:37 UTC. The full logs are available
at
Hi Alex,
- Original Message -
> Hello,
> I have a Orange Pi PC PLUS and I’m trying to install Fedora but I have
> some problems.
> Generally I tested other distros (armbian etc) with no success and I
> don’t know what is wrong.
>
> On Fedora’s case, I downloaded the xfce version from
>
Proposing we cancel today's Fedora ARM meeting as I have a conflict and won't
be available.
If someone else would like to run the meeting, please respond to the list to
let others
know.
Thanks!
Paul
- Original Message -
> Dear all,
>
> You are kindly invited to the meeting:
>
#fedora-meeting-2: Fedora ARM and AArch64 Status Meeting
Meeting started by pwhalen at 15:00:18 UTC. The full logs are available
at
HI Pete,
- Original Message -
> 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?
Should be working OK, use the 'am335x_evm' target for uboot if using
- 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 surmize that arm-image-installer expected a real /dev to write to,
> > instead of what is effectively a plain fie, so it
Hi all,
I don't think we have anything urgent on the agenda this week, I propose
we cancel the ARM meeting.
If you have anything you would like to discuss please send it to the list
or visit #fedora-arm on Freenode.
Thanks,
Paul
___
arm mailing
#fedora-meeting-2: Fedora ARM and AArch64 Status Meeting
Meeting started by pwhalen at 15:02:37 UTC. The full logs are available
at
Hi Fred,
- Original Message -
> I tried Fedora-Minimal-32_Beta-1.2.aarch64.raw.xz but it did not work for me
What didnt work?
The minimal image should work OK (running it on two RPi4's). Desktop and server
images are currently broken as others have mentioned.
>
> On Thu, Apr 2,
#fedora-meeting-2: Fedora ARM and AArch64 Status Meeting
Meeting started by pwhalen at 15:00:12 UTC. The full logs are available
at
Hi Steve,
- Original Message -
> On 3/3/20 1:12 PM, Peter Robinson wrote:
> > On Tue, Mar 3, 2020 at 5:56 PM Steven A. Falco
> > wrote:
> >>
> >> On 3/3/20 9:38 AM, Paul Kennedy wrote:
> >>> I've just tried the latest F32 and Rawhide workstation images, but
> >>> neither successfully
- Original Message -
> On Wed, 2020-02-19 at 14:12 -0500, Paul Whalen wrote:
> >
> > - Original Message -
> > > On Wed, 2020-02-19 at 12:04 -0500, Michael H. Warfield wrote:
> > > > On Wed, 2020-02-19 at 11:25 -0500, Pau
- Original Message -
> On Wed, 2020-02-19 at 12:04 -0500, Michael H. Warfield wrote:
> > On Wed, 2020-02-19 at 11:25 -0500, Paul Whalen wrote:
> > > Hi Michael,
> > >
> > > Trying to reproduce this issue without success. How did you write
> >
- Original Message -
> On Wed, 2020-02-19 at 11:25 -0500, Paul Whalen wrote:
> > Hi Michael,
>
> > Trying to reproduce this issue without success. How did you write the
> > images and
> > what command was used? After booting, did you confirm the kargs wer
Hi Michael,
Trying to reproduce this issue without success. How did you write the images and
what command was used? After booting, did you confirm the kargs were as
expected?
Once booted, you just 'dnf update' and get the corrupted grub.cfg?
Thanks!
Paul
- Original Message -
> On
- Original Message -
> Hi Derek,
>
> - Original Message -
> > (sorry if you get this twice -- I wasn't subscribed with this address
> > so I think my message was held for moderation or just blocked)
> >
> > Hi,
> >
> > I've got an x86_64 F29 desktop and I'm trying to run
Hi Derek,
- Original Message -
> (sorry if you get this twice -- I wasn't subscribed with this address
> so I think my message was held for moderation or just blocked)
>
> Hi,
>
> I've got an x86_64 F29 desktop and I'm trying to run Fedora-Minimal-31
> ARM on QEMU. I was following the
- Original Message -
> On Tue, Feb 4, 2020 at 7:26 PM Ben Cotton < bcot...@redhat.com > wrote:
>
>
> On Mon, Feb 3, 2020 at 4:22 PM Paul Whalen < pwha...@redhat.com > wrote:
> >
> > Proposed changes to the Desktop release criteria for ARM and AArch
- Original Message -
> > > Proposed changes to the Desktop release criteria for ARM and AArch64 in
> > > Fedora 32:
> > > * drop Xfce on 32-bit ARM from release blocking desktops
> > > * add Workstation on AArch64 to release blocking desktops
> > >
> > Program Management is okay with
As discussed in the Fedora QA meeting today, below are the proposed changes to
release blocking desktops on ARM.
== Summary ==
Proposed changes to the Desktop release criteria for ARM and AArch64 in Fedora
32:
* drop Xfce on 32-bit ARM from release blocking desktops
* add Workstation on
#fedora-meeting-2: Fedora ARM and AArch64 Status Meeting
Meeting started by pwhalen at 15:00:50 UTC. The full logs are available
at
usage :)
Paul
>
> Regards,
> Hjalmarsson
>
> Den tis 7 jan. 2020 kl 23:00 skrev Paul Whalen :
> >
> > Hi Peter,
> >
> > - Original Message -
> > > Hi,
> > >
> > > The newly released arm-image-installer-2.15-1.fc31.noar
Hi Peter,
- Original Message -
> Hi,
>
> The newly released arm-image-installer-2.15-1.fc31.noarch has some problems I
> like to point out with regards to raspberry pi and the newly introduced
> support for rock64.
> Lets start with rock64:
Thanks, I merged the PR without looking at it
#fedora-meeting-2: Fedora ARM and AArch64 Status Meeting
Meeting started by pwhalen at 15:00:23 UTC. The full logs are available
at
Hi Peter,
- Original Message -
> Hi,
>
> That is true unless your board need a FDT.
> Then the following patch breaks that assumption that /boot is not
> needed before grub2 starts:
>
d be a
> > 100 different things.
> >
> > What are you "remixing", what changes are you adding, you also don't
> > mention whether you're build aarch64 or armv7 (armhfp) images. For
> > aarch64 appliance-tools isn't supported, you'll need to use
> > image-factor
Hi Christopher,
For armhfp we use appliance-tools, for aarch64 image-factory.
What happened when you tried to boot the image made using
appliance-tools?
Paul
- Original Message -
> Any updates on this? I found a bunch of Koji build configs, but I'm
> not exactly sure how to
Good morning folks,
Proposing we cancel the arm meeting tomorrow. Fedora 31 will be released
and I am not aware of any other pressing issues.
Please send any issues to the mailing list or #fedora-arm on Freenode.
Paul
- Original Message -
> Dear all,
>
> You are kindly invited to
#fedora-meeting-2: Fedora ARM and AArch64 Status Meeting
Meeting started by pwhalen at 15:00:11 UTC. The full logs are available
at
Good morning folks,
Cancelling the ARM meeting tomorrow as I will be unavailable.
Please send any issues to the mailing list or #fedora-arm on Freenode.
Paul
- Original Message -
> Dear all,
>
> You are kindly invited to the meeting:
>Fedora ARM & AArch64 status meeting on
#fedora-meeting-2: Fedora ARM and AArch64 Status Meeting
Meeting started by pwhalen at 15:00:29 UTC. The full logs are available
at
#fedora-meeting-2: Fedora ARM and AArch64 Status Meeting
Meeting started by pwhalen at 15:00:59 UTC. The full logs are available
at
Reminder, as discussed last week, this weeks status meeting is cancelled.
- Original Message -
> Dear all,
>
> You are kindly invited to the meeting:
>Fedora ARM & AArch64 status meeting on 2019-08-06 from 15:00:00 to
>16:00:00 UTC
>At fedora-meetin...@irc.freenode.net
>
#fedora-meeting-2: Fedora ARM and AArch64 Status Meeting
Meeting started by pwhalen at 15:00:31 UTC. The full logs are available
at
#fedora-meeting-2: Fedora ARM and AArch64 Status Meeting
Meeting started by pwhalen at 15:00:24 UTC. The full logs are available
at
I propose we cancel this week's meeting due to summer vacation and travel. If
anyone would like to go ahead with the meeting please respond to the list to
let everyone know.
Regards,
Paul
- Original Message -
> Dear all,
>
> You are kindly invited to the meeting:
>Fedora ARM &
We currently offer a large group of Desktop Spins for ARMv7 in Fedora.
Initially we enabled all the desktops that ship for x86_64 to bring ARMv7
to parity, but for AArch64 we took a more conservative approach and only
enabled a select few.
In preparation for Fedora 31 we would like to reduce
#fedora-meeting-2: Fedora ARM and AArch64 Status Meeting
Meeting started by pwhalen at 15:00:25 UTC. The full logs are available
at
#fedora-meeting-2: Fedora ARM and AArch64 Status Meeting
Meeting started by pwhalen at 15:00:31 UTC. The full logs are available
at
Hi Felix,
- Original Message -
>
> > A network installs need about 2G ram unfortunately. You can use NFS to
> > provide the initramfs using
> > 'inst.stage2=nfs://192.168.X.X:/path/to/install.img'.
> Thanks for the hint Paul.
> I tried with the file name appended as you suggested as
Hi Felix,
- Original Message -
> 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
With Fedora 30 out the door last week, I propose we cancel this weeks
status meeting. We'll resume next week.
Paul
- Original Message -
> Dear all,
>
> You are kindly invited to the meeting:
>Fedora ARM & AArch64 status meeting on 2019-05-07 from 15:00:00 to
>16:00:00 UTC
>
- Original Message -
> > Dear All, to upgrade a Raspberry 3 I executed this commands
> >
> > sudo dnf -y upgrade --refresh
> > sudo dnf -y install dnf-plugin-system-upgrade
> > sudo dnf -y system-upgrade download --releasever=30
> > sudo dnf -y system-upgrade reboot
> >
> >
- Original Message -
> Dear All, to upgrade a Raspberry 3 I executed this commands
>
> sudo dnf -y upgrade --refresh
> sudo dnf -y install dnf-plugin-system-upgrade
> sudo dnf -y system-upgrade download --releasever=30
> sudo dnf -y system-upgrade reboot
>
> after the reboot dnf fails.
- Original Message -
> Hello guys,
>
> is there any specific way to write an Atomic Host image on a sd card for
> raspberrypi (3 or 3+ in my case).
Would need uboot/firmware added or uboot/firmware on mmc and atomichost image
on usb disk
should work.
>
> I used this one :
>
#fedora-meeting-2: Fedora ARM and AArch64 Status Meeting
Meeting started by pwhalen at 15:00:20 UTC. The full logs are available
at
Hi Robert,
- Original Message -
> I just tested with Fedora-Minimal-armhfp-30-20190307.n.0-sda
>
> On a Cubieboard2:
>
> I installed the image on a 4GB uSD card and deleted all partitions.
> I installed the image on a 240GB SSD drive and enlarged the rootfs
> partition to about 6GB.
>
- Original Message -
> On Fri, Mar 1, 2019 at 3:26 PM Matthew Miller
> wrote:
> >
> > On Fri, Mar 01, 2019 at 03:23:23PM -0500, Jeffrey Walton wrote:
> > > Yeah, you're right. Networking is up.
> > > It looks like image did not use the full SDcard. There was 13 GB
> > > unused, and
#fedora-meeting-2: Fedora ARM and AArch64 Status Meeting
Meeting started by pwhalen at 15:00:19 UTC. The full logs are available
at
#fedora-meeting-2: Fedora ARM and AArch64 Status Meeting
Meeting started by pwhalen at 15:00:38 UTC. The full logs are available
at
#fedora-meeting-2: Fedora ARM and AArch64 Status Meeting
Meeting started by pwhalen at 15:00:46 UTC. The full logs are available
at
re.io/fedora-qa/fedfind
>
> Stewart
>
> On 1/23/19 6:31 AM, Paul Whalen wrote:
> > Hi Stewart,
> >
> > - Original Message -
> >> Hello All,
> >>
> >> Does anyone know if the Mate (not Mate-Compiz) release of Fedora has b
Hi Stewart,
- Original Message -
> Hello All,
>
> Does anyone know if the Mate (not Mate-Compiz) release of Fedora has been
> terminated? I don't seem to be able to find it for Fedora 29 in the normal
> places such as:
Unfortunately the Mate disk image failed for the RC that was
#fedora-meeting-2: Fedora ARM and AArch64 Status Meeting
Meeting started by pwhalen at 15:00:33 UTC. The full logs are available
at
- Original Message -
> I am looking for help getting serial communication to work via the UART on
> either a Raspberry PI 3 B or a 3 B + that is running Fedora 29. The kernel
> recognizes the UART as /dev/ttyS1 on these systems. Data flows, but it is
> corrupted at random intervals.
As discussed last week, next meeting will be on January 8th, 2019.
Happy Holidays!
Paul
- Original Message -
> Dear all,
>
> You are kindly invited to the meeting:
>Fedora ARM & AArch64 status meeting on 2018-12-18 from 15:00:00 to
>16:00:00 UTC
>At
#fedora-meeting-2: Fedora ARM and AArch64 Status Meeting
Meeting started by pwhalen at 15:00:12 UTC. The full logs are available
at
Hi Ken,
- Original Message -
> $ sudo arm-image-installer --image=Fedora-Xfce-armhfp-29-1.2-sda.raw.xz
> --target=orangepi_prime --media=/dev/sdc
>
> I got
>
> =
> = Selected Image:
> = Fedora-Xfce-armhfp-29-1.2-sda.raw.xz
> =
Hi Ken,
- Original Message -
> the cat list says it is supported but the target is not fornd
If you could give some more detail- which image, version of the installer and
command
you are using?
Thanks,
Paul
> ___
> arm mailing list --
- Original Message -
> Hello.
> I managed to set up the camera module (not the official one) on a
> Raspberry Pi 3 running Fedora 29.
> It is pretty simple and it works. [1]
>
> In the wiki [2] it is stated that the camera module doesn't work: can
> I update such paragraph?
Absolutely!
- Original Message -
>
>
> On 12/5/18 1:11 PM, Robert Moskowitz wrote:
> >
> >
> > On 12/5/18 1:05 PM, Robert Moskowitz wrote:
> >>
> >>
> >> On 12/5/18 1:01 PM, Robert Moskowitz wrote:
> >>>
> >>> =
> >>> = Selected Image:
> >>> =
:
> > >
> > >
> > > On 12/5/18 10:43 AM, Paul Whalen wrote:
> > >>
> > >> There is still an issue in rawhide with the minimal image, I need to
> > >> look
> > >> at further. The server image[1] looks ok- bot
- Original Message -
>
>
> On 12/5/18 11:25 AM, Robert Moskowitz wrote:
> >
> >
> > On 12/5/18 10:43 AM, Paul Whalen wrote:
> >>
> >> There is still an issue in rawhide with the minimal image, I need to
> >> look
> >> a
Hi Robert,
- Original Message -
>
>
> On 12/4/18 7:08 PM, Robert Moskowitz wrote:
> >
> >
> > On 12/4/18 7:01 PM, Peter Robinson wrote:
> >> Can you trim irrelevant bits from your mails, makes it easier to read.
> >
> > I was thinking of trimming but could not figure out the irrelevant
#fedora-meeting-2: Fedora ARM and AArch64 Status Meeting
Meeting started by pwhalen at 15:00:38 UTC. The full logs are available
at
Hi all,
Proposing we cancel tomorrow's status meeting. I don't think we have anything
pressing on the agenda.
If there is something you would like to discuss you can send it to the list
or visit #fedora-arm on Freenode.
Paul
- Original Message -
> Dear all,
>
> You are kindly
Hi All,
With most people focused on the remaining issues in F29, proposing we cancel
this weeks meeting.
If there is anything you would like to discuss you can send it to the list
or visit #fedora-arm on Freenode.
Paul
- Original Message -
> Dear all,
>
> You are kindly invited to
Hi Steve,
We've been looking at this for a while but have not been able to work out
the issue.
Thanks for filing the bug, I'll leave some additional info there.
Paul
- Original Message -
> Roughly a month ago I upgraded the kernel on my wandboard quad. The quad had
> been running
- Original Message -
> Robert,
>
> I'm not replying to all your emails as I suspect the problem is the
> same for all 3.
>
> Generally in Linux a remote user by default won't get access to local
> devices. I'm not sure in the case of VNC but in the vast majority of
> cases remote
#fedora-meeting-2: Fedora ARM and AArch64 Status Meeting
Meeting started by pwhalen at 15:00:03 UTC. The full logs are available
at
As discussed last week, this weeks meeting is cancelled.
If you have any issues to discuss please send them to the list or visit
#fedora-arm on Freenode.
Paul
- Original Message -
> Dear all,
>
> You are kindly invited to the meeting:
>Fedora ARM & AArch64 status meeting on
#fedora-meeting-2: Fedora ARM and AArch64 Status Meeting
Meeting started by pwhalen at 15:00:39 UTC. The full logs are available
at
#fedora-meeting-2: Fedora ARM and AArch64 Status Meeting
Meeting started by pwhalen at 15:00:56 UTC. The full logs are available
at
#fedora-meeting-2: Fedora ARM and AArch64 Status Meeting
Meeting started by pwhalen at 15:00:11 UTC. The full logs are available
at
#fedora-meeting-2: Fedora ARM and AArch64 Status Meeting
Meeting started by pwhalen at 15:00:10 UTC. The full logs are available
at
Hi Zamir,
- Original Message -
> Oh by the way, I am using
> Fedora-Minimal-armhfp-28-1.1-sda.raw.xz
>
> On 06/06/2018 12:13 AM, Zamir SUN wrote:
> > Hi,
> >
> > I have two questions about BeagleBone Black.
> >
> > 1. Is there anyway to make it boot when plug into power adapter? By
Hi Patrick,
- Original Message -
> Kernel 4.16.8-300 is the latest one which can get my RPI3B+ booting.
I'm currently running 4.16.13-300.fc28.armv7hl on the Rpi3B+ and don't see
those errors. Looks like the mSD might be corrupt.
[root@localhost ~]# uname -r
4.16.13-300.fc28.armv7hl
1 - 100 of 461 matches
Mail list logo
