arm August 2024

arm@lists.fedoraproject.org

8 participants
11 discussions

U-Boot 2024.10 testing
by Peter Robinson 04 Sep '24

04 Sep '24

Hi Folks, I've started building the 2024.10 RCs in F-41+ so it would be great to get some testing. I found that at least the Allwinner a64 devices looked like they regressed in F-40 and I've tested the Pine64+ with the rc2 build and I think they should be OK now. It would be great if people could test and provide some feedback on these builds as we go towards F-41 beta freeze. https://koji.fedoraproject.org/koji/buildinfo?buildID=2530785 Peter

3 13

Intel Xe
by Pim Zandbergen 02 Sep '24

02 Sep '24

Upstream has support for Intel Xe graphics in all of kernel, libdrm and mesa, yet all of these packages are built with Intel support disabled on aarch64. Intel Xe drivers, unlike i915 are architecture independent. On x86_64, they conflict with i915 drivers, so an elaborate scheme is used to allow both drivers to coexist. On aarch64, Intel Xe has no legacy counterpart, so no conflict either. All the more reason to enable Intel Xe on aarch64, just like on x86_64. Intel Xe support may not be perfect on aarch64, but this is just as true on x86_64.

2 6

Problem with Bluetooth
by Andreas Reschke 29 Aug '24

29 Aug '24

Hi there, I've running Fedora release 42 (Rawhide) on my Rock 5B. Integrated Bluetooth is now working but i want work with one of my Bluetooth speaker. When I want to connect the speaker I get error : Aug 28 16:21:38 rockpi5.reschke.lan bluetoothd[14638]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 04:21:44:0D:86:91: Permission denied (13) Another speaker is working fine without any issue. Any help with this topic ? PS: Deleting this device and reconnect didn't work, same failure. Greetings Andreas

2 5

[Fedocal] Reminder meeting : Fedora ARM & AArch64 status meeting
by coremodule＠fedoraproject.org 27 Aug '24

27 Aug '24

Dear all, You are kindly invited to the meeting: Fedora ARM & AArch64 status meeting on 2024-08-27 from 15:00:00 to 16:00:00 UTC The meeting will be about: Fedora ARM & AArch64 weekly status meeting. Join us on Matrix at [https://matrix.to/#/#meeting-2:fedoraproject.org](https://matrix.to/#/#meet… through [chat.fedoraproject.org](through chat.fedoraproject.org) More information available at: [https://fedoraproject.org/wiki/Architectures/ARM](https://fedoraproject.org… Source: https://calendar.fedoraproject.org//meeting/10455/

1 0

Fedora on Rock 5B
by Andreas Reschke 27 Aug '24

27 Aug '24

Hello together, with Kernel: 6.11.0-0.rc3.20240814git6b0f8db921ab.32.fc42.aarch64 the integrated Bluetooth is now working. root@rockpi5:~# inxi -E Bluetooth: Device-1: Realtek Bluetooth Radio driver: btusb type: USB Report: btmgmt ID: hci0 state: up address: 2C:05:47:79:7C:2D bt-v: 5.2 root@rockpi5:~# Missing is still accelerated GPU and Headphone Jack. root@rockpi5:~# inxi -G Graphics: Message: No PCI device data found. Display: unspecified server: X.Org v: 24.1.2 with: Xwayland v: 24.1.2 driver: X: loaded: modesetting gpu: N/A resolution: 1920x1080~60Hz API: EGL v: 1.5 drivers: swrast platforms: x11,surfaceless,device API: OpenGL v: 4.5 vendor: mesa v: 24.2.0 note: incomplete (EGL sourced) renderer: llvmpipe (LLVM 18.1.8 128 bits) API: Vulkan v: 1.3.290 drivers: N/A surfaces: xcb,xlib root@rockpi5:~# inxi -A Audio: Message: No device data found. API: ALSA v: k6.11.0-0.rc3.20240814git6b0f8db921ab.32.fc42.aarch64 status: kernel-api Server-1: PipeWire v: 1.2.1 status: active root@rockpi5:~# Thanks a lot. Greetings Andreas

1 0

2024-08-26 @ 16:00 UTC - Fedora 41 Blocker Review Meeting
by Adam Williamson 26 Aug '24

26 Aug '24

# F10 Blocker Review meeting # Date: 2024-08-26 # Time: 16:00 UTC # Location: https://matrix.to/#/#blocker-review:fedoraproject.org?web-instance[element.… Hi folks! It's time for a Fedora 41 blocker review meeting! We have 1 proposed blocker and 1 proposed freeze exception for Beta, and 2 proposed blockers for Final. Here is a handy link which should show you the meeting time in your local time: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Fedora+41+Blocker… The meeting will be on Matrix. Click the link above to join in a web client - you can authenticate with your FAS account - or use a dedicated client of your choosing. If you have time today, you can take a look at the proposed or accepted blockers before the meeting - the full lists can be found here: https://qa.fedoraproject.org/blockerbugs/ . Remember, you can also now vote on bugs outside of review meetings! If you look at the bug list in the blockerbugs app, you'll see links labeled "Vote!" next to all proposed blockers and freeze exceptions. Those links take you to tickets where you can vote. https://pagure.io/fedora-qa/blocker-review has instructions on how exactly you do it. We usually go through the tickets shortly before the meeting and apply any clear votes, so the meeting will just cover bugs where there wasn't a clear outcome in the ticket voting yet. **THIS MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!** We'll be evaluating these bugs to see if they violate any of the Release Criteria and warrant the blocking of a release if they're not fixed. Information on the release criteria for F40 can be found on the wiki [0]. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process And for those of you who are curious how a Blocker Review Meeting works - or how it's supposed to go and you want to run one - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting Have a good day and see you tomorrow! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@fosstodon.org https://www.happyassassin.net

1 0

[Fedocal] Reminder meeting : Fedora ARM & AArch64 status meeting
by coremodule＠fedoraproject.org 20 Aug '24

20 Aug '24

Dear all, You are kindly invited to the meeting: Fedora ARM & AArch64 status meeting on 2024-08-20 from 15:00:00 to 16:00:00 UTC The meeting will be about: Fedora ARM & AArch64 weekly status meeting. Join us on Matrix at [https://matrix.to/#/#meeting-2:fedoraproject.org](https://matrix.to/#/#meet… through [chat.fedoraproject.org](through chat.fedoraproject.org) More information available at: [https://fedoraproject.org/wiki/Architectures/ARM](https://fedoraproject.org… Source: https://calendar.fedoraproject.org//meeting/10455/

1 0

2024-08-19 @ 16:00 UTC - Fedora 41 Blocker Review Meeting
by Adam Williamson 19 Aug '24

19 Aug '24

# F10 Blocker Review meeting # Date: 2024-08-19 # Time: 16:00 UTC # Location: https://matrix.to/#/#blocker-review:fedoraproject.org?web-instance[element.… Hi folks! It's time for a Fedora 41 blocker review meeting! We have 1 proposed blocker and 1 proposed freeze exception for Beta, and 6 proposed blockers for Final. Here is a handy link which should show you the meeting time in your local time: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Fedora+41+Blocker… The meeting will be on Matrix. Click the link above to join in a web client - you can authenticate with your FAS account - or use a dedicated client of your choosing. If you have time today, you can take a look at the proposed or accepted blockers before the meeting - the full lists can be found here: https://qa.fedoraproject.org/blockerbugs/ . Remember, you can also now vote on bugs outside of review meetings! If you look at the bug list in the blockerbugs app, you'll see links labeled "Vote!" next to all proposed blockers and freeze exceptions. Those links take you to tickets where you can vote. https://pagure.io/fedora-qa/blocker-review has instructions on how exactly you do it. We usually go through the tickets shortly before the meeting and apply any clear votes, so the meeting will just cover bugs where there wasn't a clear outcome in the ticket voting yet. **THIS MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!** We'll be evaluating these bugs to see if they violate any of the Release Criteria and warrant the blocking of a release if they're not fixed. Information on the release criteria for F40 can be found on the wiki [0]. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process And for those of you who are curious how a Blocker Review Meeting works - or how it's supposed to go and you want to run one - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting Have a good day and see you tomorrow! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@fosstodon.org https://www.happyassassin.net

1 0

[Fedocal] Reminder meeting : Fedora ARM & AArch64 status meeting
by coremodule＠fedoraproject.org 13 Aug '24

13 Aug '24

Dear all, You are kindly invited to the meeting: Fedora ARM & AArch64 status meeting on 2024-08-13 from 15:00:00 to 16:00:00 UTC The meeting will be about: Fedora ARM & AArch64 weekly status meeting. Join us on Matrix at [https://matrix.to/#/#meeting-2:fedoraproject.org](https://matrix.to/#/#meet… through [chat.fedoraproject.org](through chat.fedoraproject.org) More information available at: [https://fedoraproject.org/wiki/Architectures/ARM](https://fedoraproject.org… Source: https://calendar.fedoraproject.org//meeting/10455/

1 0

Bluetooth on Pinebook Pro
by Andreas Reschke 10 Aug '24

10 Aug '24

Hello, first: don't know if Bluetooth has worked before. If updated today the laptop and noticed Bluetooth isn't working. dmesg | grep -i bluetooth missed 'brcm/BCM4345C5.hcd After searching Internet I've found https://copr.fedorainfracloud.org/coprs/jwillikers/pinebook-pro and installed ap6256-firmware-2020.02-10.fc39.aarch64.rpm No failure on root@pinebook-pro:/home/andreas# dmesg | grep -i bluetooth [ 54.157295] Bluetooth: Core ver 2.22 [ 54.168145] NET: Registered PF_BLUETOOTHprotocol family [ 54.168154] Bluetooth: HCI device and connection manager initialized [ 54.168167] Bluetooth: HCI socket layer initialized [ 54.168173] Bluetooth: L2CAP socket layer initialized [ 54.168215] Bluetooth: SCO socket layer initialized [ 54.375968] Bluetooth: HCI UART driver ver 2.3 [ 54.381603] Bluetooth: HCI UART protocol H4 registered [ 54.387230] Bluetooth: HCI UART protocol BCSP registered [ 54.418449] Bluetooth: HCI UART protocol LL registered [ 54.420446] Bluetooth: HCI UART protocol ATH3K registered [ 54.438694] Bluetooth: HCI UART protocol Three-wire (H5) registered [ 54.438939] Bluetooth: HCI UART protocol Intel registered [ 54.450367] Bluetooth: HCI UART protocol Broadcom registered [ 54.450978] Bluetooth: HCI UART protocol QCA registered [ 54.466370] Bluetooth: HCI UART protocol AG6XX registered [ 54.481649] Bluetooth: HCI UART protocol Marvell registered [ 54.871946] Bluetooth: hci0: BCM: chip id 130 [ 54.878835] Bluetooth: hci0: BCM: features 0x0f [ 54.881103] Bluetooth: hci0: BCM4345C5 [ 54.881119] Bluetooth: hci0: BCM4345C5 (003.006.006) build 0000 [ 54.915175] Bluetooth: hci0: BCM4345C5 'brcm/BCM4345C5.hcd' Patch [ 55.863677] Bluetooth: hci0: BCM: features 0x0f [ 55.889055] Bluetooth: hci0: BCM4345C5 Ampak_CL1.5 UART 37.4 MHz BT 5.0 [Version: Version: 0033.0080] [ 55.889093] Bluetooth: hci0: BCM4345C5 (003.006.006) build 0080 [ 55.890379] Bluetooth: hci0: BCM: Using default device address (43:45:c5:00:1f:ac) [ 57.583111] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 57.587702] Bluetooth: BNEP filters: protocol multicast [ 57.592713] Bluetooth: BNEP socket layer initialized root@pinebook-pro:~# rfkill | grep blue 1 bluetooth hci0 unblocked unblocked root@pinebook-pro:~# Bluetooth doesn't find any controller. Greetings Andreas

4 5

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

arm August 2024