What repos should be used for RPI3 B+?

[Jeffrey Walton]

Hi Everyone,

I need to sort out the dnf problems after a RPI3 B+ install using
Fedora-Minimal-armhfp-29-1.2-sda.raw.xz. Searching for DNF and repos
is returning hits for tradition Fedora desktops (like
https://fedoraproject.org/wiki/Repositories).

Would someone please provide the dnf tweaks needed or cat a working
conf file and post it here?

Thanks in advance.

[Matthew Miller]

On Fri, Mar 01, 2019 at 02:29:16PM -0500, Jeffrey Walton wrote:
>  I need to sort out the dnf problems after a RPI3 B+ install using
>  Fedora-Minimal-armhfp-29-1.2-sda.raw.xz. Searching for DNF and repos
>  is returning hits for tradition Fedora desktops (like
>  https://fedoraproject.org/wiki/Repositories). 
That's actually correct -- the Fedora images for Raspberry Pi are not
special and general (armhfp) Fedora repos should Just Work. So, something
else is wrong.



-- 
Matthew Miller
<mattdm(a)fedoraproject.org&gt;
Fedora Project Leader

[Jeffrey Walton]

On Fri, Mar 1, 2019 at 3:02 PM Matthew Miller <mattdm(a)fedoraproject.org&gt; wrote:
>  On Fri, Mar 01, 2019 at 02:29:16PM -0500, Jeffrey Walton wrote:
>  > I need to sort out the dnf problems after a RPI3 B+ install using
>  > Fedora-Minimal-armhfp-29-1.2-sda.raw.xz. Searching for DNF and repos
>  > is returning hits for tradition Fedora desktops (like
>  > https://fedoraproject.org/wiki/Repositories).
>
>  That's actually correct -- the Fedora images for Raspberry Pi are not
>  special and general (armhfp) Fedora repos should Just Work. So, something
>  else is wrong. 
Yeah, you're right. Networking is up.

It looks like image did not use the full SDcard. There was 13 GB
unused, and there was no swap file.

Once I GParted it things started working as expected.

Maybe dnf could be configured to provide an accurate error message
instead of swallowing exceptions and displaying 'Error: Failed to
synchronize cache for repo fedora'. Maybe something like 'Error: out
of disk space' or 'Error: out of memory'. That would be very useful.

Jeff

[Matthew Miller]

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 there was no swap file. 
I think it's supposed to expand on first boot -- that might be a bug? (I'm
not sure tbh)


>  Maybe dnf could be configured to provide an accurate error message
>  instead of swallowing exceptions and displaying 'Error: Failed to
>  synchronize cache for repo fedora'. Maybe something like 'Error: out
>  of disk space' or 'Error: out of memory'. That would be very useful. 
Yes, that seems... very reasonable.

-- 
Matthew Miller
<mattdm(a)fedoraproject.org&gt;
Fedora Project Leader

[Jeffrey Walton]

On Fri, Mar 1, 2019 at 3:26 PM Matthew Miller <mattdm(a)fedoraproject.org&gt; 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 there was no swap file.
>
>  I think it's supposed to expand on first boot -- that might be a bug? (I'm
>  not sure tbh)
>
>  > Maybe dnf could be configured to provide an accurate error message
>  > instead of swallowing exceptions and displaying 'Error: Failed to
>  > synchronize cache for repo fedora'. Maybe something like 'Error: out
>  > of disk space' or 'Error: out of memory'. That would be very useful.
>
>  Yes, that seems... very reasonable. 
Yeah, the guys who maintain dnf probably test on a desktop where there
are plenty of resources.

Good job on the image. I'm getting ready to try the Aarch64 image.

Jeff

[Troy Dawson]

On Fri, Mar 1, 2019 at 12:26 PM Matthew Miller <mattdm(a)fedoraproject.org&gt; 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 there was no swap file.
>
>  I think it's supposed to expand on first boot -- that might be a bug? (I'm
>  not sure tbh)
>
>
>  > Maybe dnf could be configured to provide an accurate error message
>  > instead of swallowing exceptions and displaying 'Error: Failed to
>  > synchronize cache for repo fedora'. Maybe something like 'Error: out
>  > of disk space' or 'Error: out of memory'. That would be very useful.
>
>  Yes, that seems... very reasonable.
>  
Just so you know, once you download the repo files (so that it knows
what's in the repo), if you run out of space while you are downloading
rpm's, it does give a reasonable error.
I run into this all the time with one of my machines.  It gives "Out
of disk space"
Also, if you manage to download all the rpm's, and it determines that
you don't have enough disk space to install them, it will tell you
that you don't have enough disk space then, as well. (experience with
the same machine)
So if you file a bugzilla bug, it should only be if there isn't enough
room to download the repo xml files ... whatever the proper term for
those files is.

Troy

Post-install (was: What repos should be used for RPI3 B+)

[Jeffrey Walton]

On Fri, Mar 1, 2019 at 3:26 PM Matthew Miller <mattdm(a)fedoraproject.org&gt; 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 there was no swap file.
>
>  I think it's supposed to expand on first boot -- that might be a bug? (I'm
>  not sure tbh) 
I needed to tweak the filesystem after dd'ing for both the armhf and
aarch64 images.

Both filesystems needed a swap file, and both needed to be extended to
use the full SDcard.

Jeff

Post-install (was: What repos should be used for RPI3 B+)

[Paul Whalen]

----- Original Message -----
>  On Fri, Mar 1, 2019 at 3:26 PM Matthew Miller
> <mattdm(a)fedoraproject.org&gt;
>  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 there was no swap file.
>  >
>  > I think it's supposed to expand on first boot -- that might be a bug? (I'm
>  > not sure tbh)
>  
>  I needed to tweak the filesystem after dd'ing for both the armhf and
>  aarch64 images.
>  
>  Both filesystems needed a swap file, and both needed to be extended to
>  use the full SDcard. 
We provide a script called 'arm-image-installer' which is used to write
the image as well as resize. You can install it using dnf. 

In Fedora 29 we introduced zram[1] for swap on the disk images. You can
find some more info on Peter's blog[2].

Paul

[1] - https://fedoraproject.org/wiki/Changes/ZRAMforARMimages
[2] - https://nullr0ute.com/2018/10/using-zram-as-swap-on-fedora/

> 
> Jeff
> _______________________________________________
> arm mailing list -- arm(a)lists.fedoraproject.org
> To unsubscribe send an email to arm-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/[e-mail]
>

Post-install (was: What repos should be used for RPI3 B+)

[Jeffrey Walton]

On Fri, Mar 1, 2019 at 5:02 PM Paul Whalen <pwhalen(a)redhat.com&gt; wrote:
>  ----- Original Message -----
>  > On Fri, Mar 1, 2019 at 3:26 PM Matthew Miller <mattdm(a)fedoraproject.org&gt;
>  > 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 there was no swap file.
>  > >
>  > > I think it's supposed to expand on first boot -- that might be a bug?
> (I'm
>  > > not sure tbh)
>  >
>  > I needed to tweak the filesystem after dd'ing for both the armhf and
>  > aarch64 images.
>  >
>  > Both filesystems needed a swap file, and both needed to be extended to
>  > use the full SDcard.
>
>  We provide a script called 'arm-image-installer' which is used to write
>  the image as well as resize. You can install it using dnf. 
Thanks. I saw arm-image-installer but did not see a download for it.

I'm working on Debian for the downloads and dd's. I have two machines
with monitors, and they are Debian and Windows. Everything else is
headless and I work over SSH.

Jeff

[Peter Robinson]

>  > On Fri, Mar 01, 2019 at 02:29:16PM -0500, Jeffrey Walton wrote:
>  > > I need to sort out the dnf problems after a RPI3 B+ install using
>  > > Fedora-Minimal-armhfp-29-1.2-sda.raw.xz. Searching for DNF and repos
>  > > is returning hits for tradition Fedora desktops (like
>  > > https://fedoraproject.org/wiki/Repositories).
>  >
>  > That's actually correct -- the Fedora images for Raspberry Pi are not
>  > special and general (armhfp) Fedora repos should Just Work. So, something
>  > else is wrong.
>
>  Yeah, you're right. Networking is up.
>
>  It looks like image did not use the full SDcard. There was 13 GB
>  unused, and there was no swap file. 
If you use arm-image-installer there's a --resize option which expands
out the disk. We generally don't expand the disk by default because
some people like to do manual adjustment, separate /home etc.

In the case if no swap, that's intentional, we use zram/zswap [1] as
of F-29 as it's much kinder on SD card wear levels and is generally
faster.

>  Once I GParted it things started working as expected. 
Excellent news.

Peter

[1] https://fedoraproject.org/wiki/Changes/ZRAMforARMimages