Fedora on Pinebook Pro
by Andreas Reschke
Hi there,
I've updated my Pinebook Pro today. With actual kernel NVME Discs are
working.
root@pinebook-pro ~]# uname -a
Linux pinebook-pro.reschke.lan 5.13.13-200.fc34.aarch64 #1 SMP Thu Aug
26 16:51:14 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux
[root@pinebook-pro ~]# nvme list
Node SN Model Namespace
Usage Format FW Rev
---------------- --------------------
---------------------------------------- ---------
-------------------------- ---------------- --------
/dev/nvme0n1 2018FV440610 WDC
WDS250G2B0C-00PXH0 1 250,06 GB / 250,06
GB 512 B + 0 B 211070WD
[root@pinebook-pro ~]# df -h
Dateisystem Größe Benutzt Verf. Verw%
Eingehängt auf
devtmpfs 1,9G 0 1,9G 0% /dev
tmpfs 1,9G 1,2M 1,9G 1% /dev/shm
tmpfs 767M 1,8M 766M 1% /run
/dev/mapper/fedora_pinebook--pro-root 56G 6,1G 47G 12% /
tmpfs 1,9G 3,1M 1,9G 1% /tmp
/dev/mapper/fedora_pinebook--pro-homelv 216G 8,8G 196G 5% /home
/dev/mmcblk2p2 976M 197M 713M 22% /boot
/dev/mmcblk2p1 599M 5,9M 593M 1% /boot/efi
tmpfs 384M 68K 384M 1%
/run/user/1000
[root@pinebook-pro ~]#
The last thing what I want to have is external Monitor over USB-C.
Thanks to all who managed these.
Andreas
1 year, 7 months
Fedora ARM & AArch64 Status Meeting Minutes 2021-09-28
by Paul Whalen
========================================================
#fedora-meeting-2: Fedora ARM and AArch64 Status Meeting
========================================================
Meeting started by pwhalen at 15:01:41 UTC. The full logs are available
athttps://meetbot.fedoraproject.org/fedora-meeting-2/2021-09-28/fedora_ar...
.
Meeting summary
---------------
* roll call (pwhalen, 15:01:42)
* 0) ==== Fedora 35 Beta Released today! ==== (pwhalen, 15:03:52)
* Fedora 35 Beta release announcement (pwhalen, 15:04:06)
* LINK: https://fedoramagazine.org/announcing-fedora-35-beta/
(pwhalen, 15:04:06)
* Fedora 35 Common Bugs (pwhalen, 15:04:15)
* LINK: https://fedoraproject.org/wiki/Common_F35_bugs (pwhalen,
15:04:15)
* Bug 2008537 - 5.14.x defaults to acpi on aarch64 (pwhalen,
15:04:48)
* Bug 2008557 - vc4-drm gpu: [drm] *ERROR* Timed out waiting for
commit (pwhalen, 15:05:45)
* 1) ==== Userspace Status ==== (pwhalen, 15:15:04)
* No new issues reported. (pwhalen, 15:16:57)
* 2) ==== Kernel Status ==== (pwhalen, 15:17:06)
* kernel-5.15.0-0.rc3.25.fc36 (pwhalen, 15:17:17)
* LINK: https://koji.fedoraproject.org/koji/buildinfo?buildID=1837487
(pwhalen, 15:17:17)
* kernel-5.14.8-300.fc35 (pwhalen, 15:18:24)
* LINK: https://koji.fedoraproject.org/koji/buildinfo?buildID=1837405
(pwhalen, 15:18:24)
* Please test and report any issues to the list or #fedora-arm.
(pwhalen, 15:21:17)
* 3) ==== Bootloader Status ==== (pwhalen, 15:21:27)
* Uboot-tools RC5 released upstream, not yet built for Fedora.
(pwhalen, 15:23:46)
* 4) ==== Fedora 35 GA ==== (pwhalen, 15:24:05)
* Fedora 35 Schedule -
https://fedorapeople.org/groups/schedule/f-35/f-35-key-tasks.html
(pwhalen, 15:24:48)
* 5) == Open Floor == (pwhalen, 15:28:57)
Meeting ended at 15:32:05 UTC.
Action Items
------------
Action Items, by person
-----------------------
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* pwhalen (40)
* zodbot (6)
* pbrobinson (5)
* jlinton (4)
* coremodule (2)
* nirik (2)
Generated by `MeetBot`_ 0.3
.. _`MeetBot`: https://fedoraproject.org/wiki/Zodbot#Meeting_Functions
1 year, 8 months
Re: Wiki claims RPi 4 is not supported
by Peter Robinson
On Tue, Sep 21, 2021 at 9:00 PM Donatom M <donatom.martino(a)gmail.com> wrote:
>
> How do I do that. I thought it would be automatic.
Reply All.
> On Tue, Sep 21, 2021 at 12:20 PM Peter Robinson <pbrobinson(a)gmail.com> wrote:
>>
>> Please leave the mailing list on replied.
>>
>> > I would agree that fedora 34 arm has some disadvantages when run on Raspberry Pi 4 with xorg server. I have fedora installed onto a SSD drive. As another member mentioned, I have found that audio does not work out of the box. I have not tried to get audio to work because audio was not important to me on this build. I would hope that Raspberry Pi support and fedora-arm would work on remedying the few problems that exist.
>> >
>> > I would like to note that I also have Archlinux-Arm with X server on an SD card (128 GiG) and everything works without any problem at all, so I would think that if Arch-ARM can build a system that is fully functional on Raspberry Pi 4, so can Fedora-ARM. All of my systems are running 64 bit with Raspberry Pi 4, by the way.
>>
>> Archlinux-Arm uses the downstream Raspberry Pi fork of the kernel.
>>
>> > On Tue, Sep 21, 2021 at 1:32 AM Peter Robinson <pbrobinson(a)gmail.com> wrote:
>> >>
>> >> > >> On this page it states that the RPi4 is not supported.
>> >>
>> >> That is correct, there's a very large cavernous gap between "may work
>> >> for a number of purposes including yours" and something that will work
>> >> for the vast majority of users.
>> >>
>> >> The core "supported" status will change when the standard GUI runs
>> >> fully accelerated and users have WiFi/sound and the things that are
>> >> associated with a reasonable desktop experience as that's the default
>> >> means a lot of new users expect. That's what I, as the RPi maintainer,
>> >> did when we introduced "supported" RPi3. Any less than that the
>> >> support queries are too high.
>> >>
>> >> > >> https://fedoraproject.org/wiki/Architectures/ARM/Raspberry_Pi#Raspberry_Pi_4
>> >> > >
>> >> > > yes the statement about hardware support isn't quite correct anymore.
>> >> > > But there is still a noticeable difference between the mainline kernel
>> >> > > (which Fedora uses) and the vendor kernel from the Raspberry Pi Foundation.
>> >> > >
>> >> > > Most notably are:
>> >> > > - audio support
>> >> > > - V3D support
>> >>
>> >> Those two are critical.
>> >>
>> >> > An update to say clearly that only server/headless worked then would better the. The blanket “it does not work”. I is only that I looked deeper that I found out that it
>> >> > might work.
>> >>
>> >> The Wiki page explicitly does not say "it does not work" it says it's
>> >> not supported. The words are chosen specifically. By saying it's
>> >> supported a user can rock up when something doesn't work and ask for
>> >> support or assistance, if something breaks we block the release etc.
>> >> By saying it's not supported a user may try it and if it works for
>> >> them great, but if it breaks while we'll attempt to fix it that may
>> >> take time and it may not get fixed.
>> >>
>> >> > Oh and would need a warning that the boot is very slow.
>> >> > I see a black screen for a couple of minutes before I see any output
>> >> > from the kernel or systemd.
>> >>
>> >> Oh look, a user asking for "support".... see my points above!
>> >>
>> >> > > A lot users doesn't accept this. Instead of blaming the vendor to focus
>> >> > > on its own kernel branch, they blame Fedora for using the mainline
>> >> > > kernel. So that's the reason to say it's not officially supported.
>> >>
>> >> It's one reason, but not the only ones.
>> >>
>> >> > >> There a lots of messages in this mailing archieve showing that people are
>> >> > >> getting Fedora to work on RPi4.
>> >>
>> >> Yes, and that's the idea, a more advanced user will be able to
>> >> ascertain it works, and it has for a *long* time and likely be able to
>> >> do most of what they want to do.
>> >>
>> >> > >> Is there still a reason to claim its not supported?
>> >> > >> If so what should I be watching out for/avoiding with the RPi4?
>> >> > > For a headless / server setup there shouldn't be no general issues.
>> >>
>> >> For a headless server it should be fine, but a general user comes via
>> >> Fedora Workstation and expect and accelerated desktop and sound and we
>> >> don't have them working ATM.
>> >>
>> >> Peter
>> >> - The Fedora Raspberry Pi "maintainer"
>> >> _______________________________________________
>> >> 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://docs.fedoraproject.org/en-US/project/code-of-conduct/
>> >> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>> >> List Archives: https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org
>> >> Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
1 year, 8 months
Re: Use kodi 19 from rpm fusion on fedora 34 with raspberry pi 2
by Felipe Diefenbach
I tried to use the kernel parameter on boot, but isn't work.
The problem seems to be the same as previous problem.
Maybe i have to try the desktop image instead the minimal image ? There would have some big difference between minimal and desktop image to justify use one or another, instead to use minimal X on minimal image ?
Or maybe would this be a problem with kodi and i need report this in another forum.
Or maybe is another mistake i made.
Please, if I would need to send you more details about setup or system, ask me and i will forward this, if i need to get help in other location, please redirect me to the proper location
thank you anyway.
---- Ativado Seg, 20 set 2021 16:38:31 -0300 Felipe Diefenbach <felipe(a)conexaoinfraestrutura.inf.br> escreveu ----
I used this:
Fedora-Minimal-34-1.2.armhfp.raw.xz
https://mirror1.cl.netactuate.com/fedora/releases/34/Spins/armhfp/images/...
before your instructions, i see this in dmesg:
dmesg | grep -i CMA
[ 0.000000] Reserved memory: created CMA memory pool at 0x29800000, size 64 MiB
[ 0.000000] OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool
[ 0.000000] Kernel command line: BOOT_IMAGE=(hd0,msdos2)/vmlinuz-5.13.16-200.fc34.armv7hl root=UUID=9ce87fe4-b0f9-4cb1-9ee9-0e3270f8cc42 ro CMA=256M
[ 0.000000] Memory: 668172K/786432K available (10489K kernel code, 2423K rwdata, 5576K rodata, 2048K init, 557K bss, 52724K reserved, 65536K cma-reserved, 0K highmem)
[ 6.757255] CMA=256M
[ 126.230817] [drm:vc4_bo_create [vc4]] *ERROR* Failed to allocate from CMA:
[ 126.277649] [drm:vc4_bo_create [vc4]] *ERROR* Failed to allocate from CMA:
[ 126.339697] [drm:vc4_bo_create [vc4]] *ERROR* Failed to allocate from CMA:
[ 126.406259] [drm:vc4_bo_create [vc4]] *ERROR* Failed to allocate from CMA:
[ 126.562712] [drm:vc4_bo_create [vc4]] *ERROR* Failed to allocate from CMA:
[ 126.615279] [drm:vc4_bo_create [vc4]] *ERROR* Failed to allocate from CMA:
[ 126.677529] [drm:vc4_bo_create [vc4]] *ERROR* Failed to allocate from CMA:
[ 129.748644] [drm:vc4_bo_create [vc4]] *ERROR* Failed to allocate from CMA:
[ 129.795836] [drm:vc4_bo_create [vc4]] *ERROR* Failed to allocate from CMA:
[ 129.848677] [drm:vc4_bo_create [vc4]] *ERROR* Failed to allocate from CMA:
[ 129.904766] [drm:vc4_bo_create [vc4]] *ERROR* Failed to allocate from CMA:
[ 129.951932] [drm:vc4_bo_create [vc4]] *ERROR* Failed to allocate from CMA:
And:
[ 129.951932] [drm:vc4_bo_create [vc4]] *ERROR* Failed to allocate from CMA:
[ 129.959162] vc4-drm soc:gpu: [drm] V3D: 35728kb BOs (14)
[ 129.967073] vc4-drm soc:gpu: [drm] V3D shader: 36kb BOs (9)
[ 129.974906] vc4-drm soc:gpu: [drm] dumb: 4116kb BOs (5)
[ 129.982702] vc4-drm soc:gpu: [drm] binner: 16384kb BOs (1)
[ 129.990523] vc4-drm soc:gpu: [drm] total purged BO: 288kb BOs (9)
[ 224.255219] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:74:crtc-3] flip_done timed out
[ 224.255242] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
[ 224.273316] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:74:crtc-3] commit wait timed out
[ 234.495100] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
[ 234.503091] vc4-drm soc:gpu: [drm] *ERROR* Timed out waiting for commit
I will go read the common bugs, but i remember breffly to read this page before.
this is my kodi unit for systemd.
cat /usr/lib/systemd/system/kodi.service
[Unit]
Description = kodi-standalone using xinit
After = remote-fs.target systemd-user-sessions.service
[Service]
User = root
Group = root
PAMName = login
Type = simple
ExecStart = /usr/bin/xinit /usr/bin/dbus-launch /usr/bin/kodi-standalone -- :0 -nolisten tcp
Restart = on-abort
[Install]
WantedBy = multi-user.target
I follow this guide to install kodi: https://kodi.wiki/view/Archive:Install_Kodi_on_Fedora_26_using_RPMFusion_...
---- Ativado Seg, 20 set 2021 15:56:36 -0300 Peter Robinson <mailto:pbrobinson@gmail.com> escreveu ----
> cat /etc/redhat-release
> Fedora release 34 (Thirty Four)
Did you download a specific desktop image?
> [ 0.000000] Memory: 668172K/786432K available (10489K kernel code, 2423K rwdata, 5576K rodata, 2048K init, 557K bss, 52724K reserved, 65536K cma-reserved, 0K highmem)
That tells me you're running with the default of 64Mb of CMA so
depending on your DE with kodi I'm not surprised.
> cat /boot/efi/config.txt | grep 256
> #cma_hwm=256
> gpu_mem=256
>
> I tryed with mixing of parameters but have no sucess
It will need to be a kernel command line:
grubby --update-kernel /boot/vmlinuz-$(uname -r) --args="CMA=256M"
There's details in the Fedora common bugs:
https://fedoraproject.org/wiki/Common_F34_bugs#Desktop_images_may_require...
>
> ---- Ativado Seg, 20 set 2021 14:06:10 -0300 Peter Robinson <mailto:pbrobinson@gmail.com> escreveu ----
>
> On Mon, Sep 20, 2021 at 4:40 PM Felipe Diefenbach
> <mailto:felipe@conexaoinfraestrutura.inf.br> wrote:
> >
> > I have recently migrate from OSMC (debian like SO) to fedora 34 in the rasberry pi 2 (armhf), but when I try to use kodi from rpm fusion a get this error.
>
> You don't mention which image you're using as your base.
>
> You probably need to increase the CMA allocation on the kernel command line.
>
> Running "dmesg | grep -i CMA" will likely give you the information you need.
>
> Also note the rpi media offload stuff isn't yet upstream so won't work
> to do HW accelerated video decode.
>
> Peter
>
> > [ 305.423847] [drm:vc4_bo_create [vc4]] *ERROR* Failed to allocate from CMA:
> > [ 305.431015] vc4-drm soc:gpu: [drm] V3D: 27556kb BOs (10)
> > [ 305.438839] vc4-drm soc:gpu: [drm] V3D shader: 24kb BOs (6)
> > [ 305.446602] vc4-drm soc:gpu: [drm] dumb: 4116kb BOs (5)
> > [ 305.454337] vc4-drm soc:gpu: [drm] binner: 16384kb BOs (1)
> > [ 305.462075] vc4-drm soc:gpu: [drm] total purged BO: 260kb BOs (2)
> > [ 305.494522] [drm:vc4_bo_create [vc4]] *ERROR* Failed to allocate from CMA:
> > [ 305.501868] vc4-drm soc:gpu: [drm] V3D: 27556kb BOs (10)
> > [ 305.509713] vc4-drm soc:gpu: [drm] V3D shader: 24kb BOs (6)
> > [ 305.517498] vc4-drm soc:gpu: [drm] dumb: 4116kb BOs (5)
> > [ 305.525284] vc4-drm soc:gpu: [drm] binner: 16384kb BOs (1)
> > [ 305.533149] vc4-drm soc:gpu: [drm] total purged BO: 260kb BOs (2)
> > [ 305.578081] [drm:vc4_bo_create [vc4]] *ERROR* Failed to allocate from CMA:
> > [ 305.585266] vc4-drm soc:gpu: [drm] V3D: 27568kb BOs (13)
> > [ 305.593099] vc4-drm soc:gpu: [drm] V3D shader: 24kb BOs (6)
> > [ 305.600850] vc4-drm soc:gpu: [drm] dumb: 4116kb BOs (5)
> > [ 305.608583] vc4-drm soc:gpu: [drm] binner: 16384kb BOs (1)
> > [ 305.616587] vc4-drm soc:gpu: [drm] total purged BO: 264kb BOs (3)
> > [ 305.646201] [drm:vc4_bo_create [vc4]] *ERROR* Failed to allocate from CMA:
> > [ 305.653393] vc4-drm soc:gpu: [drm] V3D: 27564kb BOs (12)
> > [ 305.661389] vc4-drm soc:gpu: [drm] V3D shader: 24kb BOs (6)
> > [ 305.669165] vc4-drm soc:gpu: [drm] dumb: 4116kb BOs (5)
> > [ 305.677026] vc4-drm soc:gpu: [drm] binner: 16384kb BOs (1)
> > [ 305.684835] vc4-drm soc:gpu: [drm] total purged BO: 264kb BOs (3)
> >
> >
> > I tryed getting some information on this issue from Google but stuck in nothing very usefull.
> > So, could someone help me ?
> >
> > Architecture: armv7l
> > Byte Order: Little Endian
> > CPU(s): 4
> > On-line CPU(s) list: 0-3
> > Thread(s) per core: 1
> > Core(s) per socket: 4
> > Socket(s): 1
> > Vendor ID: ARM
> > Model: 5
> > Model name: Cortex-A7
> > Stepping: r0p5
> > CPU max MHz: 900.0000
> > CPU min MHz: 600.0000
> > BogoMIPS: 38.40
> > Flags: half thumb fastmult vfp edsp thumbee neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm
> >
> > [root@krisiun ~]# cat /proc/meminfo
> > MemTotal: 751516 kB
> > MemFree: 169628 kB
> > MemAvailable: 624916 kB
> > Buffers: 19580 kB
> > Cached: 430532 kB
> > SwapCached: 32 kB
> > Active: 126604 kB
> > Inactive: 382212 kB
> > Active(anon): 860 kB
> > Inactive(anon): 58644 kB
> > Active(file): 125744 kB
> > Inactive(file): 323568 kB
> > Unevictable: 0 kB
> > Mlocked: 0 kB
> > HighTotal: 0 kB
> > HighFree: 0 kB
> > LowTotal: 751516 kB
> > LowFree: 169628 kB
> > SwapTotal: 750588 kB
> > SwapFree: 749820 kB
> > Dirty: 20 kB
> > Writeback: 0 kB
> > AnonPages: 58672 kB
> > Mapped: 96696 kB
> > Shmem: 800 kB
> > KReclaimable: 20184 kB
> > Slab: 46528 kB
> > SReclaimable: 20184 kB
> > SUnreclaim: 26344 kB
> > KernelStack: 1384 kB
> > PageTables: 3320 kB
> > NFS_Unstable: 0 kB
> > Bounce: 0 kB
> > WritebackTmp: 0 kB
> > CommitLimit: 1126344 kB
> > Committed_AS: 372256 kB
> > VmallocTotal: 245760 kB
> > VmallocUsed: 9908 kB
> > VmallocChunk: 0 kB
> > Percpu: 1040 kB
> > CmaTotal: 65536 kB
> > CmaFree: 57984 kB
> >
> >
> > _______________________________________________
> > arm mailing list -- mailto:arm@lists.fedoraproject.org
> > To unsubscribe send an email to mailto:arm-leave@lists.fedoraproject.org
> > Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> > List Archives: https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org
> > Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
>
>
>
1 year, 8 months
Re: Wiki claims RPi 4 is not supported
by Peter Robinson
Please leave the mailing list on replied.
> I would agree that fedora 34 arm has some disadvantages when run on Raspberry Pi 4 with xorg server. I have fedora installed onto a SSD drive. As another member mentioned, I have found that audio does not work out of the box. I have not tried to get audio to work because audio was not important to me on this build. I would hope that Raspberry Pi support and fedora-arm would work on remedying the few problems that exist.
>
> I would like to note that I also have Archlinux-Arm with X server on an SD card (128 GiG) and everything works without any problem at all, so I would think that if Arch-ARM can build a system that is fully functional on Raspberry Pi 4, so can Fedora-ARM. All of my systems are running 64 bit with Raspberry Pi 4, by the way.
Archlinux-Arm uses the downstream Raspberry Pi fork of the kernel.
> On Tue, Sep 21, 2021 at 1:32 AM Peter Robinson <pbrobinson(a)gmail.com> wrote:
>>
>> > >> On this page it states that the RPi4 is not supported.
>>
>> That is correct, there's a very large cavernous gap between "may work
>> for a number of purposes including yours" and something that will work
>> for the vast majority of users.
>>
>> The core "supported" status will change when the standard GUI runs
>> fully accelerated and users have WiFi/sound and the things that are
>> associated with a reasonable desktop experience as that's the default
>> means a lot of new users expect. That's what I, as the RPi maintainer,
>> did when we introduced "supported" RPi3. Any less than that the
>> support queries are too high.
>>
>> > >> https://fedoraproject.org/wiki/Architectures/ARM/Raspberry_Pi#Raspberry_Pi_4
>> > >
>> > > yes the statement about hardware support isn't quite correct anymore.
>> > > But there is still a noticeable difference between the mainline kernel
>> > > (which Fedora uses) and the vendor kernel from the Raspberry Pi Foundation.
>> > >
>> > > Most notably are:
>> > > - audio support
>> > > - V3D support
>>
>> Those two are critical.
>>
>> > An update to say clearly that only server/headless worked then would better the. The blanket “it does not work”. I is only that I looked deeper that I found out that it
>> > might work.
>>
>> The Wiki page explicitly does not say "it does not work" it says it's
>> not supported. The words are chosen specifically. By saying it's
>> supported a user can rock up when something doesn't work and ask for
>> support or assistance, if something breaks we block the release etc.
>> By saying it's not supported a user may try it and if it works for
>> them great, but if it breaks while we'll attempt to fix it that may
>> take time and it may not get fixed.
>>
>> > Oh and would need a warning that the boot is very slow.
>> > I see a black screen for a couple of minutes before I see any output
>> > from the kernel or systemd.
>>
>> Oh look, a user asking for "support".... see my points above!
>>
>> > > A lot users doesn't accept this. Instead of blaming the vendor to focus
>> > > on its own kernel branch, they blame Fedora for using the mainline
>> > > kernel. So that's the reason to say it's not officially supported.
>>
>> It's one reason, but not the only ones.
>>
>> > >> There a lots of messages in this mailing archieve showing that people are
>> > >> getting Fedora to work on RPi4.
>>
>> Yes, and that's the idea, a more advanced user will be able to
>> ascertain it works, and it has for a *long* time and likely be able to
>> do most of what they want to do.
>>
>> > >> Is there still a reason to claim its not supported?
>> > >> If so what should I be watching out for/avoiding with the RPi4?
>> > > For a headless / server setup there shouldn't be no general issues.
>>
>> For a headless server it should be fine, but a general user comes via
>> Fedora Workstation and expect and accelerated desktop and sound and we
>> don't have them working ATM.
>>
>> Peter
>> - The Fedora Raspberry Pi "maintainer"
>> _______________________________________________
>> 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://docs.fedoraproject.org/en-US/project/code-of-conduct/
>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>> List Archives: https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org
>> Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
1 year, 8 months
Fedora ARM and AArch64 Status Meeting Minutes 2021-09-21
by Paul Whalen
========================================================
#fedora-meeting-2: Fedora ARM and AArch64 Status Meeting
========================================================
Meeting started by pwhalen at 15:00:25 UTC. The full logs are available
athttps://meetbot.fedoraproject.org/fedora-meeting-2/2021-09-21/fedora_ar...
.
Meeting summary
---------------
* roll call (pwhalen, 15:00:25)
* 1) ==== Userspace Status ==== (pwhalen, 15:03:31)
* No new userspace issues reported. (pwhalen, 15:05:14)
* 2) ==== Kernel Status ==== (pwhalen, 15:05:55)
* kernel-5.15.0-0.rc2.18.fc36 (pwhalen, 15:06:13)
* LINK: https://koji.fedoraproject.org/koji/buildinfo?buildID=1835036
(pwhalen, 15:06:13)
* Workqueue: btrfs-delalloc btrfs_work_helper PC is at mmiocpy LR is
at ZSTD_compressStream (pwhalen, 15:06:49)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2006295
(pwhalen, 15:06:49)
* kernel-5.14.6-300.fc35 (pwhalen, 15:10:39)
* LINK: https://koji.fedoraproject.org/koji/buildinfo?buildID=1834235
(pwhalen, 15:10:39)
* Please test and report any issues to the list or #fedora-arm.
(pwhalen, 15:12:11)
* 3) ==== Bootloader Status ==== (pwhalen, 15:13:30)
* uboot-tools-2021.10-0.6.rc4.fc35 (pwhalen, 15:13:45)
* LINK: https://koji.fedoraproject.org/koji/buildinfo?buildID=1832543
(pwhalen, 15:13:45)
* grub2-2.06-5.fc35 (pwhalen, 15:16:53)
* LINK: https://koji.fedoraproject.org/koji/buildinfo?buildID=1830126
(pwhalen, 15:16:54)
* Fixes kernel alignment issue on AArch64 and the boot issue on 32-bit
arm (BZ#2000756). (pwhalen, 15:17:12)
* 4) ==== Fedora 35 Beta ==== (pwhalen, 15:18:45)
* Fedora 35 Beta Bugs (pwhalen, 15:18:56)
* LINK:
https://qa.fedoraproject.org/blockerbugs/milestone/35/beta/buglist
(pwhalen, 15:18:56)
* Attempting to join wifi network in initial-setup fails (pwhalen,
15:21:52)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2006314
(pwhalen, 15:22:05)
* [abrt] gnome-shell: cogl_texture_get_gl_texture(): gnome-shell
killed by SIGSEGV (pwhalen, 15:25:52)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1989726
(pwhalen, 15:25:53)
* Hardware testing -
https://fedoraproject.org/wiki/User:Pwhalen/QA/Fedora_Linux_35_Nightlies
(pwhalen, 15:28:19)
* 5) == Open Floor == (pwhalen, 15:38:15)
Meeting ended at 15:42:31 UTC.
Action Items
------------
Action Items, by person
-----------------------
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* pwhalen (56)
* jlinton (9)
* pbrobinson (8)
* zodbot (6)
* coremodule (6)
Generated by `MeetBot`_ 0.3
.. _`MeetBot`: https://fedoraproject.org/wiki/Zodbot#Meeting_Functions
1 year, 8 months
Use kodi 19 from rpm fusion on fedora 34 with raspberry pi 2 (
by Felipe Diefenbach
I have recently migrate from OSMC (debian like SO) to fedora 34 in the rasberry pi 2 (armhf), but when I try to use kodi from rpm fusion a get this error.
[ 305.423847] [drm:vc4_bo_create [vc4]] *ERROR* Failed to allocate from CMA:
[ 305.431015] vc4-drm soc:gpu: [drm] V3D: 27556kb BOs (10)
[ 305.438839] vc4-drm soc:gpu: [drm] V3D shader: 24kb BOs (6)
[ 305.446602] vc4-drm soc:gpu: [drm] dumb: 4116kb BOs (5)
[ 305.454337] vc4-drm soc:gpu: [drm] binner: 16384kb BOs (1)
[ 305.462075] vc4-drm soc:gpu: [drm] total purged BO: 260kb BOs (2)
[ 305.494522] [drm:vc4_bo_create [vc4]] *ERROR* Failed to allocate from CMA:
[ 305.501868] vc4-drm soc:gpu: [drm] V3D: 27556kb BOs (10)
[ 305.509713] vc4-drm soc:gpu: [drm] V3D shader: 24kb BOs (6)
[ 305.517498] vc4-drm soc:gpu: [drm] dumb: 4116kb BOs (5)
[ 305.525284] vc4-drm soc:gpu: [drm] binner: 16384kb BOs (1)
[ 305.533149] vc4-drm soc:gpu: [drm] total purged BO: 260kb BOs (2)
[ 305.578081] [drm:vc4_bo_create [vc4]] *ERROR* Failed to allocate from CMA:
[ 305.585266] vc4-drm soc:gpu: [drm] V3D: 27568kb BOs (13)
[ 305.593099] vc4-drm soc:gpu: [drm] V3D shader: 24kb BOs (6)
[ 305.600850] vc4-drm soc:gpu: [drm] dumb: 4116kb BOs (5)
[ 305.608583] vc4-drm soc:gpu: [drm] binner: 16384kb BOs (1)
[ 305.616587] vc4-drm soc:gpu: [drm] total purged BO: 264kb BOs (3)
[ 305.646201] [drm:vc4_bo_create [vc4]] *ERROR* Failed to allocate from CMA:
[ 305.653393] vc4-drm soc:gpu: [drm] V3D: 27564kb BOs (12)
[ 305.661389] vc4-drm soc:gpu: [drm] V3D shader: 24kb BOs (6)
[ 305.669165] vc4-drm soc:gpu: [drm] dumb: 4116kb BOs (5)
[ 305.677026] vc4-drm soc:gpu: [drm] binner: 16384kb BOs (1)
[ 305.684835] vc4-drm soc:gpu: [drm] total purged BO: 264kb BOs (3)
I tryed getting some information on this issue from Google but stuck in nothing very usefull.
So, could someone help me ?
Architecture: armv7l
Byte Order: Little Endian
CPU(s): 4
On-line CPU(s) list: 0-3
Thread(s) per core: 1
Core(s) per socket: 4
Socket(s): 1
Vendor ID: ARM
Model: 5
Model name: Cortex-A7
Stepping: r0p5
CPU max MHz: 900.0000
CPU min MHz: 600.0000
BogoMIPS: 38.40
Flags: half thumb fastmult vfp edsp thumbee neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm
[root@krisiun ~]# cat /proc/meminfo
MemTotal: 751516 kB
MemFree: 169628 kB
MemAvailable: 624916 kB
Buffers: 19580 kB
Cached: 430532 kB
SwapCached: 32 kB
Active: 126604 kB
Inactive: 382212 kB
Active(anon): 860 kB
Inactive(anon): 58644 kB
Active(file): 125744 kB
Inactive(file): 323568 kB
Unevictable: 0 kB
Mlocked: 0 kB
HighTotal: 0 kB
HighFree: 0 kB
LowTotal: 751516 kB
LowFree: 169628 kB
SwapTotal: 750588 kB
SwapFree: 749820 kB
Dirty: 20 kB
Writeback: 0 kB
AnonPages: 58672 kB
Mapped: 96696 kB
Shmem: 800 kB
KReclaimable: 20184 kB
Slab: 46528 kB
SReclaimable: 20184 kB
SUnreclaim: 26344 kB
KernelStack: 1384 kB
PageTables: 3320 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 1126344 kB
Committed_AS: 372256 kB
VmallocTotal: 245760 kB
VmallocUsed: 9908 kB
VmallocChunk: 0 kB
Percpu: 1040 kB
CmaTotal: 65536 kB
CmaFree: 57984 kB
1 year, 8 months
