Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Sep 22 17:54

    dwrobel on master

    Sync firmware-nonfree to commit… (compare)

  • Sep 22 17:54

    dwrobel on master

    Sync to latest git commit: f9bc… (compare)

  • Jul 29 16:49

    dwrobel on master

    Sync firmware-nonfree to commit… (compare)

  • Jul 29 16:48

    dwrobel on master

    Sync to latest git commit: e83f… (compare)

  • Jun 24 21:56

    dwrobel on master

    Sync to latest git commit: 5cea… (compare)

  • Apr 27 17:56

    dwrobel on master

    Sync to latest git commit: 616d… (compare)

  • Mar 12 19:23

    dwrobel on master

    Update to the latest available … (compare)

  • Mar 12 19:23

    dwrobel on master

    Sync to latest git commit: 0591… (compare)

  • Jan 05 11:35
    vd-rd commented #48
  • Jan 05 11:34
    vd-rd commented #48
  • Dec 24 2020 10:12
    dwrobel commented #48
  • Dec 23 2020 20:44

    dwrobel on master

    Update to the latest available … (compare)

  • Dec 23 2020 20:42

    dwrobel on master

    Sync to latest git commit: 0fb9… (compare)

  • Dec 17 2020 15:08
    vd-rd opened #48
  • Dec 16 2020 17:17
    AnimeKato opened #1
  • Sep 30 2020 14:40

    agrez on 5.4.y

    Ensure Fedora/CentOS patches ar… Disable EFI_BOOTLOADER_CONTROL Sync RPi patch to git revision:… and 1 more (compare)

  • Sep 30 2020 12:54
    agrez labeled #39
  • Sep 30 2020 12:54
    agrez assigned #39
  • Sep 30 2020 12:54
    agrez opened #39
  • Sep 30 2020 12:09

    agrez on 5.4.y

    Disable building kernel-tools a… Merge pull request #38 from dwr… (compare)

Michael Katzmann
@Heterodyne
I upgraded to F28 but had/have a conflict between linux-firmare package and bcm434xx-firmware.
Which package should I use/not use or how can I install both (if both are needed)
The conflicting/duplicate file is bcrmfmac43455-stdio.bin
Vaughan Agrez
@agrez
@Heterodyne Thanks for the report..... Hmmmm..... I see Fedora has updated the linux-firmware rpm but we have excludes for this in our yum repo files, so I'm not quite sure why this is happening when upgrading.
You need our bcm434xx-firmware + linux-firmware packages together, otherwise our bcm434xx-firmware rpm will surely conflict with Fedora's release.
I will update our linux-firmware which will fix the issue for now and then try to figure out why dnf is ignoring the linux-firmware exclude we have in place.
Vaughan Agrez
@agrez
Just out of interest, what's the output of cat /etc/yum.repos.d/fedora.repo |grep -m1 linux-firmware and cat /etc/yum.repos.d/fedora-updates.repo |grep -m1 linux-firmware?
Michael Katzmann
@Heterodyne
No output to either...
Michael Katzmann
@Heterodyne
I think the conflict was between the Fedberry linux-firmware package and the Fedberry bcm434xx-firmware rpm (not the Fedora linux-firmware rpm).
Vaughan Agrez
@agrez
Hmmm, you should get output for both of those commands..... which means your install is either not fully updated or you might have fedora.repo.rpmnew & fedora-updates.repo.rpmnew files in /etc/yum.repos.d/
what release of 'fedberry-repos' do you have installed? rpm -q fedberry-repo
Michael Katzmann
@Heterodyne
Yes, the rpmnew files were there. I copied them over. fedberry-repo-28-8.fc28.noarch
Vaughan Agrez
@agrez
Its likely that was the issue then (ie the fedora.repo fedora-updates.repo files weren't updated therefore the linux-firmware exclude wasn't present). I don't usually like updating repo files after release due to this very issue but sometimes certain issues force my hand.
Juan Carlos
@JuanKman94
Hello, everyone
I'm trying to compile minidlna for the fedberry (currently compiling ffmpeg, since it isn't in the repos)
I was thinking about making an RPM for the builds to avoid the hassle for the next guy, so far I've built:
Do you guys have your own repos for armv7?
Juan Carlos
@JuanKman94
Okay, I just saw the rpm specs on the repo hehe :sweat_smile:
Vaughan Agrez
@agrez
Hi @JuanKman94. I have only built ffmpeg for Fedberry 28 at this point. Packages are in the 'testing' repo.
Vaughan Agrez
@agrez
I might trigger a build for Fedberry 27 but I don't know when I'll get a chance to test it...
itisthec
@itisthec
Hi, looking to see if there is a reason for raspberrypi-vc-libs-20180801-1.f74ea7f.fc27.armv7hl to creating "/opt/vc" and "/opt/vc/lib" in the packages, as they seem to be removed as well (dnf repoquery --list raspberrypi-vc-libs-20180801-1.f74ea7f.fc27.armv7hl) shows these files, but they are not there after update. I just happen to be running autofs on /opt and thus cannot run dnf update without stopping/disabling autofs, rebooting without it and then updating, and re-enabling. If these don't need to exists, why are they in the package? thanks for any help/insights - not sure if this is the right place for this
Vaughan Agrez
@agrez
hi @itisthec. The /opt/vc dir is the 'official' RPi location for the libs and since we have the libs located elsewhere (/usr/lib/vc), I recently added some soft links in /opt to help maintain compatibility. Basically, everything else out there in the Raspberry Pi universe expects the libs to be in /opt/vc/lib and I was tired of working around this issue in various packages.
Vaughan Agrez
@agrez
My guess for /opt/vc and /opt/vc/lib not existing after updating is that autofs is still somehow messing with whole update process. Can you assign a different dir for autofs to use? Maybe something a little more standard like /media or if not, a subdir in /opt (/opt/media) ?
itisthec
@itisthec
i can see what i can do - but this isn't auto-mounting media, this is nfs auto-mounting application software to local network machines (single central configured software mounted out to all the machines with separate local logging), auto-mounted media does go into /media
but this is new with this release? so it wouldn't have been an issue before (just trying to understand cause/effect)
oh, and thanks for the quick reply and background, very much appreciated. Really love the fedberry releases, thanks for that too!
Vaughan Agrez
@agrez
@itisthec yes, these are new changes I made when working on Fedberry 28 packages and its all been pushed to Fedberry 27 as well, so no it wouldn't have been as issue before.
David Demelier
@markand
hello all
is there a guide to create custom version (as image disk) of fedberry using kickstart?
for example, to add/remove some packages from the default barebone kickstart file
Vaughan Agrez
@agrez
Hi @markand. You can pretty much follow the standard Fedora procedure here: https://fedoraproject.org/wiki/Architectures/ARM/Creating_Remixes
Of course however, use our kickstarts instead.
Go here to grab the latest kickstarts: https://github.com/fedberry/fedberry-kickstarts (master branch is for Fedberry 28)
David Demelier
@markand
okay thanks I'll do :)
fedberry running on my raspberry pi 3 !
is chronyd really required since we can have systemd-timesyncd instead?
Vaughan Agrez
@agrez
Fedora still defaults to chronyd at this point, so we follow suit. Not sure if/when they plan to switch.
I must admit, chronyd was/is significantly impacting on boot times with fedberry-barebone (28) last time I checked (as compared to previous Fedberry barebone releases). I like to keep boot times to around 5 sec for barebone and chronyd is currently spoiling the party!
Peter Oliver
@mavit
Hello, I notice that upstream Fedora 27 is scheduled to become end of life in just six weeks time. Are there any plans for Fedberry 28 or 29 release?
Vaughan Agrez
@agrez
Hi @mavit. Yes, I have seen the Fedora 27 EOL date looming. I never did 'official' Fedberry 28 release images as I was never happy with 'downstream' RPi kernel builds from branches newer than rpi-4.14.x (BTW, I did push up some 'unofficial' Fedberry 28 snapshot images but never announced anything). Recently, kernel builds from the rpi-4.18.x branch are looking pretty good, so I am starting to work towards a Fedberry 29 release based on these. It happens to coincide quite nicely with the Fedora 29 release time frame.
orbitaLinx
@orbitaLinx
Hello.
Vaughan Agrez
@agrez
Welcome @orbitaLinx :smiley:
MarlonPindter
@MarlonPindter
hi everyone! i have a problem when update a fedberry i had this error
image.png
i need help :c
Vaughan Agrez
@agrez
Hi @MarlonPindter. Do you happen to have either /etc/yum.repos.d/fedora.repo.rpmnew or /etc/yum.repos.d/fedora-updates.repo.rpmnew files hanging around?
If so, then if you rename them to fedora-updates.repo & fedora.repo it should hopefully fix the problem.
Vaughan Agrez
@agrez
For those who may be interested, I have pushed up some Fedberry 29 development snapshot images (barebone, minimal & xfce). Barebone and minimal releases are pretty solid while the xfce image has a few minor niggles here and there which may or may not get ironed out by the time we do an official 29.1 release.