arm April 2024

arm@lists.fedoraproject.org

14 participants
18 discussions

Fedora on Rock 5B
by Andreas Reschke 11 Jun '24

11 Jun '24

Hi there, I've tried to install Fedora on my Rock 5 without success. Booting with https://github.com/edk2-porting/edk2-rk3588/releases/download/v0.7.1/rock-5… on SD-Card and source from https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Everythin…. Board boots up fine but later starting in loop with 350.456154] dracut-initqueue[1065]: Warning: ############# Anaconda installer errors end ############### [ 352.156835] dracut-initqueue[1065]: Warning: dracut-initqueue: timeout, still waiting for following initqueue hooks: [ 352.161387] dracut-initqueue[1065]: Warning: /lib/dracut/hooks/initqueue/finished/devexists-\x2fdev\x2froot.sh: "[ -e "/dev/root" ]" [ 352.164564] dracut-initqueue[1065]: Warning: /lib/dracut/hooks/initqueue/finished/wait_for_disks.sh: "[ "$main_loop" -ge "10" ]" [ 352.167716] dracut-initqueue[1065]: Warning: /lib/dracut/hooks/initqueue/finished/wait_for_settle.sh: "[ -f /tmp/settle.done ]" [ 352.171999] dracut-initqueue[1065]: Warning: dracut-initqueue: starting timeout scripts [ 352.172610] dracut-initqueue[1065]: Warning: ############# Anaconda installer errors begin ############# [ 352.172852] dracut-initqueue[1065]: Warning: # # [ 352.173097] dracut-initqueue[1065]: Warning: It seems that the boot has failed. Possible causes include [ 352.173296] dracut-initqueue[1065]: Warning: missing inst.stage2 or inst.repo boot parameters on the [ 352.173537] dracut-initqueue[1065]: Warning: kernel cmdline. Please verify that you have specified [ 352.173731] dracut-initqueue[1065]: Warning: inst.stage2 or inst.repo. [ 352.173918] dracut-initqueue[1065]: Warning: Please also note that the 'inst.' prefix is now mandatory. [ 352.174156] dracut-initqueue[1065]: Warning: # # [ 352.174354] dracut-initqueue[1065]: Warning: #### Installer errors encountered during boot: #### [ 352.174543] dracut-initqueue[1065]: Warning: # # [ 352.174775] dracut-initqueue[1065]: Warning: Reason unknown [ 352.174970] dracut-initqueue[1065]: Warning: # # Full log file: see rock.txt Has anybody more succcess ? Greetings Andreas

3 10

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

30 Apr '24

Dear all, You are kindly invited to the meeting: Fedora ARM & AArch64 status meeting on 2024-04-30 from 16:00:00 to 17: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/

3 2

Re: Issues with RPi4 and newer kernels
by Peter Robinson 29 Apr '24

29 Apr '24

> I agree with that, until it de-escalets into finger pointing (your fault, my fault) nonsense.. very little to be gained there! Doesn't matter who F'd up . Get several eyes on it and fix it . ... I'm sorry, I'm not sure what you mean by finger pointing, I wasn't pointing any fingers, people are busy, I was was just asking you if you could detail issues in bug reports so we could improve things for all users and have improvements for all. > On Mon, Apr 29, 2024, 16:01 Peter Robinson <pbrobinson(a)gmail.com> wrote: >> >> Adding arm(a)lists.fedoraproject.org back as it was dropped at some point. >> >> > I've never filed bug report. This is free, open source software. WiFi failing to stay connected, failing to route to anything that's not in its own subnet Bind losing it's mind about what subnet it's on GUI Begins coming up, only to black and leave you with virtual terminals. >> >> We use a primarily upstream linus kernel, we've never had reports from >> users of key things like this, and I've never seen it in my own >> testing, so I would be interested in your usecase/configuration. >> >> > There's so much I could say. Rather than gripe about it, i'd much rather just roll up my sleeves and find a way to help as best as I can. Been writing C/C++ on UNIX/Linux for almost 25 years now. I think that's a more productive approach.. . >> >> To some degree report bugs is helping because it means we can fix it >> for all Fedora users, even if your coding ends up fixing it, because >> it means we can ensure the fixes are in place for all users, not just >> a single user, I feel that's a productive approach hence the request >> for bug reports :-) >> >> Peter >> >> > >> > On Mon, Apr 29, 2024, 15:39 Peter Robinson <pbrobinson(a)gmail.com> wrote: >> >> >> >> > I'm curious now. I use ethernet on mine and almost always build custom kernels. In the absence of anything more useful, I feel motivated to play with this and see what I can see. Had plenty of other issues with RPi (4b) and Fedora tho'. Contemplating migration to Manjaro...... >> >> >> >> What sort of issues? Can you provide some details or links to some bug >> >> reports please? >> >> >> >> > On Mon, Apr 29, 2024 at 12:33 PM Peter Robinson <pbrobinson(a)gmail.com> wrote: >> >> >> >> >> >> Hi, >> >> >> >> >> >> > I have a couple of Raspberry Pi 4 systems running Fedora 39 (as headless >> >> >> > servers), but I'm now hitting kernel update issues with both of them. >> >> >> > I've opened RHBZs on both but haven't gotten any response (they're niche >> >> >> > issues on a somewhat niche platform, so probably not much attention). I >> >> >> > was wondering if anybody here might have any suggestions for working on >> >> >> > getting these fixed. >> >> >> > >> >> >> > One issue started with kernel 6.7 on one Pi - about 30-60 seconds after >> >> >> > boot, it crashes back to a uboot screen (had to hook up a monitor to see >> >> >> > it). I have netconsole set up but it doesn't show anything. This Pi >> >> >> > has a GPS HAT set up with PPS for a time source... I suspect it may be >> >> >> > related to that? The boot-to-crash delay is probably around the time >> >> >> > that it takes for the GPS/PPS to start up after boot. Kernel 6.6.13 >> >> >> > still works fine. >> >> >> > >> >> >> > https://bugzilla.redhat.com/show_bug.cgi?id=2264560 >> >> >> > >> >> >> > The other issue started with kernel 6.8 on another Pi - this one loses >> >> >> > the ability to connect to a WPA3-PSK wifi network. It can still connect >> >> >> > to a WPA2-PSK network, and kernel 6.7 can connect to WPA3-PSK. I have >> >> >> > other (x86_64) Fedora systems that can connect to the WPA3-PSK network >> >> >> > with kernel 6.8. >> >> >> > >> >> >> > https://bugzilla.redhat.com/show_bug.cgi?id=2275835 >> >> >> >> >> >> I replied on both of those bugs. While I maintain various pieces of >> >> >> arm kernel I don't follow all kernel bugs as I don't have the >> >> >> bandwidth so it's useful to ping here as you've done for awareness to >> >> >> problems. >> >> >> >> >> >> P >> >> >> -- >> >> >> _______________________________________________ >> >> >> 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, report it: https://pagure.io/fedora-infrastructure/new_issue >> >> > >> >> > >> >> > >> >> > -- >> >> > Randall DuCharme (Radio AD5GB) >> >> > Powered by Open Source software. >> >> >

1 0

Re: Issues with RPi4 and newer kernels
by Peter Robinson 29 Apr '24

29 Apr '24

Adding arm(a)lists.fedoraproject.org back as it was dropped at some point. > I've never filed bug report. This is free, open source software. WiFi failing to stay connected, failing to route to anything that's not in its own subnet Bind losing it's mind about what subnet it's on GUI Begins coming up, only to black and leave you with virtual terminals. We use a primarily upstream linus kernel, we've never had reports from users of key things like this, and I've never seen it in my own testing, so I would be interested in your usecase/configuration. > There's so much I could say. Rather than gripe about it, i'd much rather just roll up my sleeves and find a way to help as best as I can. Been writing C/C++ on UNIX/Linux for almost 25 years now. I think that's a more productive approach.. . To some degree report bugs is helping because it means we can fix it for all Fedora users, even if your coding ends up fixing it, because it means we can ensure the fixes are in place for all users, not just a single user, I feel that's a productive approach hence the request for bug reports :-) Peter > > On Mon, Apr 29, 2024, 15:39 Peter Robinson <pbrobinson(a)gmail.com> wrote: >> >> > I'm curious now. I use ethernet on mine and almost always build custom kernels. In the absence of anything more useful, I feel motivated to play with this and see what I can see. Had plenty of other issues with RPi (4b) and Fedora tho'. Contemplating migration to Manjaro...... >> >> What sort of issues? Can you provide some details or links to some bug >> reports please? >> >> > On Mon, Apr 29, 2024 at 12:33 PM Peter Robinson <pbrobinson(a)gmail.com> wrote: >> >> >> >> Hi, >> >> >> >> > I have a couple of Raspberry Pi 4 systems running Fedora 39 (as headless >> >> > servers), but I'm now hitting kernel update issues with both of them. >> >> > I've opened RHBZs on both but haven't gotten any response (they're niche >> >> > issues on a somewhat niche platform, so probably not much attention). I >> >> > was wondering if anybody here might have any suggestions for working on >> >> > getting these fixed. >> >> > >> >> > One issue started with kernel 6.7 on one Pi - about 30-60 seconds after >> >> > boot, it crashes back to a uboot screen (had to hook up a monitor to see >> >> > it). I have netconsole set up but it doesn't show anything. This Pi >> >> > has a GPS HAT set up with PPS for a time source... I suspect it may be >> >> > related to that? The boot-to-crash delay is probably around the time >> >> > that it takes for the GPS/PPS to start up after boot. Kernel 6.6.13 >> >> > still works fine. >> >> > >> >> > https://bugzilla.redhat.com/show_bug.cgi?id=2264560 >> >> > >> >> > The other issue started with kernel 6.8 on another Pi - this one loses >> >> > the ability to connect to a WPA3-PSK wifi network. It can still connect >> >> > to a WPA2-PSK network, and kernel 6.7 can connect to WPA3-PSK. I have >> >> > other (x86_64) Fedora systems that can connect to the WPA3-PSK network >> >> > with kernel 6.8. >> >> > >> >> > https://bugzilla.redhat.com/show_bug.cgi?id=2275835 >> >> >> >> I replied on both of those bugs. While I maintain various pieces of >> >> arm kernel I don't follow all kernel bugs as I don't have the >> >> bandwidth so it's useful to ping here as you've done for awareness to >> >> problems. >> >> >> >> P >> >> -- >> >> _______________________________________________ >> >> 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, report it: https://pagure.io/fedora-infrastructure/new_issue >> > >> > >> > >> > -- >> > Randall DuCharme (Radio AD5GB) >> > Powered by Open Source software. >> >

1 0

Issues with RPi4 and newer kernels
by Chris Adams 29 Apr '24

29 Apr '24

I have a couple of Raspberry Pi 4 systems running Fedora 39 (as headless servers), but I'm now hitting kernel update issues with both of them. I've opened RHBZs on both but haven't gotten any response (they're niche issues on a somewhat niche platform, so probably not much attention). I was wondering if anybody here might have any suggestions for working on getting these fixed. One issue started with kernel 6.7 on one Pi - about 30-60 seconds after boot, it crashes back to a uboot screen (had to hook up a monitor to see it). I have netconsole set up but it doesn't show anything. This Pi has a GPS HAT set up with PPS for a time source... I suspect it may be related to that? The boot-to-crash delay is probably around the time that it takes for the GPS/PPS to start up after boot. Kernel 6.6.13 still works fine. https://bugzilla.redhat.com/show_bug.cgi?id=2264560 The other issue started with kernel 6.8 on another Pi - this one loses the ability to connect to a WPA3-PSK wifi network. It can still connect to a WPA2-PSK network, and kernel 6.7 can connect to WPA3-PSK. I have other (x86_64) Fedora systems that can connect to the WPA3-PSK network with kernel 6.8. https://bugzilla.redhat.com/show_bug.cgi?id=2275835 -- Chris Adams <linux(a)cmadams.net>

2 3

Lenovo X13s Firmware Load Issues on Kernel 6.8.7-300
by Andrew Spooner 24 Apr '24

24 Apr '24

Hi all, I have been using Fedora 40 Beta on my Lenovo X13s (followed instructions on https://fedoraproject.org/wiki/Thinkpad_X13s, thanks for those, very helpful). However, last couple of kernel updates have brought regressions which I think are due to failing to load firmware. dmesg has lines like : - [ 2.596550] remoteproc remoteproc0: Direct firmware load for qcom/sc8280xp/LENOVO/21BX/qcadsp8280.mbn failed with error -2 [ 2.606506] remoteproc remoteproc1: Direct firmware load for qcom/sc8280xp/LENOVO/21BX/qccdsp8280.mbn failed with error -2 This has the impact that the power monitor doesn't seem to be able to pull battery status (pd-mapper is installed and running) Rebooting and selecting kernel 6.8.4-300.fc40.aarch64 and this issue disappears. Is this happening to any other X13s owner? Any help a debugging the issue/resolving it without downgrading kernel would be appreciated. Thanks Andrew Spooner

3 3

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

22 Apr '24

Dear all, You are kindly invited to the meeting: Fedora ARM & AArch64 status meeting on 2024-04-23 from 16:00:00 to 17: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

Error with arm-image-installer F39 Rpi4 IoT image on F38 Host
by Derek Atkins 17 Apr '24

17 Apr '24

I just tried to use arm-image-installer to build an Rpi4 IoT image using the Fedora-39 IoT release image: Fedora-IoT-39.20231103.1-20231103.1.aarch64.raw.xz I asked the installer to resize the partition. At the end of the run, I get: The partition table has been altered. Calling ioctl() to re-read partition table. Syncing disks. e2fsck 1.46.5 (30-Dec-2021) /dev/sdb3 has unsupported feature(s): FEATURE_C12 e2fsck: Get a newer version of e2fsck! root: ********** WARNING: Filesystem still has errors ********** resize2fs 1.46.5 (30-Dec-2021) Please run 'e2fsck -f /dev/sdb3' first. I'm guessing the file system was created with a newer version of e2fsprogs than that supported in F38 (and there is no update on F38) and it created a new default feature in the filesystem, which isn't supported in the older version. According to google, this might be the orphan_file feature, but I have not verified that. -derek -- Derek Atkins 617-623-3745 derek(a)ihtfp.com www.ihtfp.com Computer and Internet Security Consultant

2 1

Unsuscribe
by vbrugel＠laposte.net 16 Apr '24

16 Apr '24

‌Hello. Is it possible to unsuscribe to your list? Thanks for your answer. Regards, Vincent BRUGEL

1 0

Mapping GPIO Pins from Wandboard to Fedora/libpiod
by Derek Atkins 15 Apr '24

15 Apr '24

Hi Arm Team, I have a Wandboard (yeah, I know, OLD Hardware) currently running a project, and I'm trying to add some GPIO inputs to it. In previous GPIO handling (on a different platform) I used the /sys/class/gpio interfaces to set up the GPIO, but I've discovered this is now deprecated and removed from Fedora. So I installed libgpiod and am trying to use it. I'm using https://download.technexion.com/development_resources/wandboard/wbquad-revb… as a reference for the board layout. Specifically, on page 27, it shows me that the JP4 header connects to GPIO3_12, GPIO3_27, GPIO6_31, CPIO1_24, GPIO7_8, GPIO3_26, GPIO_18, and GPIO_19. I figure that GPIO_18 is going to be gpiochip0 line 18, and GPIO3_12 will be gpiochip3 line 12.. Except that gpiodetect only tells me I have gpiochip0 through gpiochip6, so I'm not sure where GPIO7_8 would get mapped. That's the first issue I have. The second issue is that the kernel does not have any named mappings, so running gpioinfo just displays generic data, like: gpiochip6 - 32 lines: line 0: unnamed unused input active-high line 1: unnamed unused input active-high Except, of course, looking at gpiochip3 line 12 shows me: gpiochip3 - 32 lines: ... line 12: unnamed "scl" output active-high [used open-drain] Which seems to imply that that GPIO3_12 is actually used for something else -- or my mapping strategy is off. I'd appreciate any guidance anyone might have on this subject. Thanks, -derek -- Derek Atkins 617-623-3745 derek(a)ihtfp.com www.ihtfp.com Computer and Internet Security Consultant

2 10

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

15 Apr '24

Dear all, You are kindly invited to the meeting: Fedora ARM & AArch64 status meeting on 2024-04-16 from 16:00:00 to 17: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-04-15 @ 16:00 UTC - Fedora 40 Blocker Review Meeting
by Adam Williamson 14 Apr '24

14 Apr '24

# F40 Blocker Review meeting # Date: 2024-04-15 # Time: 16:00 UTC # Location: https://matrix.to/#/#blocker-review:fedoraproject.org?web-instance[element.… Hi folks! It's time for another blocker review meeting. We have 1 proposed blocker (kinda...) and 4 proposed freeze exceptions 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+40+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

no /dev/mtd* devices in Fedora 40 beta on Rock 5B
by Pim Zandbergen 09 Apr '24

09 Apr '24

I have my Rock 5B booting Fedora 40 Beta on NVMe, using EDK2 on an SD card. I would like to flash the EDK2 image to SPI, but this requires access to /dev/mtdblock* devices. There appear to be none. Could this be related to the ACPI vs DTB setting in the EDK2? Fedora 40 Beta will not boot in DTB mode, and possibly this is required for automatically creating /dev/mtdblock* devices.

3 2

Fedora on ROCK 5 Model B
by Andreas Reschke 08 Apr '24

08 Apr '24

Hello, I've installed Fedora 40 Rawhide on my Rock 5 Short howto: What you need: 1) https://github.com/edk2-porting/edk2-rk3588/releases/download/v0.9.1/rock-5… dd this Image on a SD-Card 2) https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Everythin… dd this Image on a USB stick Put both in your Rock 5B and boot. I've done the Net-install installation with KDE Wayland. The SD-Card with UEFI is needed for booting. Questions: 1. GPU: root@rockpi5:~# inxi -Gx Graphics: Message:No PCI device data found. Display:server:X.Org v:23.2.2 with:Xwayland v:23.2.2 driver:X: loaded:modesetting dri:swrast gpu:N/A resolution:1920x1080~60Hz API:EGL v:1.5 drivers:kms_swrast,swrast platforms: active:gbm,x11,surfaceless,device inactive:wayland API:OpenGL v:4.5 vendor:mesa v:23.3.0 glx-v:1.4 direct-render:yes renderer:llvmpipe (LLVM 17.0.4 128 bits) API:Vulkan v:1.3.268 drivers:llvmpipe surfaces:xcb,xlib devices:1 root@rockpi5:~# How can I improve GPU Performance ? Mali / Panfrost Driver are available but not loaded /used root@rockpi5:~# rpm -ql mesa-dri-drivers-23.3.0-1.fc40.aarch64 | grep -i pan /usr/lib64/dri/panfrost_dri.so root@rockpi5:~# rpm -ql mesa-dri-drivers-23.3.0-1.fc40.aarch64 | grep -i mali /usr/lib64/dri/mali-dp_dri.so root@rockpi5:~# Creating a custom xorg.conf doesn't make sense while using Wayland ? 2. Boot Is there any way to boot Fedora direct from NVME instead using rock-5b_UEFI_Release_v0.9.1.img on SD-Card ? Thanks Andreas

4 7

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

08 Apr '24

Dear all, You are kindly invited to the meeting: Fedora ARM & AArch64 status meeting on 2024-04-09 from 16:00:00 to 17: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-04-08 @ 16:00 UTC - Fedora 40 Blocker Review Meeting
by Adam Williamson 06 Apr '24

06 Apr '24

# F40 Blocker Review meeting # Date: 2024-04-08 # Time: 16:00 UTC # Location: https://matrix.to/#/#blocker-review:fedoraproject.org?web-instance[element.… Hi folks! It's time for another blocker review meeting. We have 4 proposed blockers and 5 proposed freeze exceptions 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+40+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 this weekend, 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 weekend 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 01 Apr '24

01 Apr '24

Dear all, You are kindly invited to the meeting: Fedora ARM & AArch64 status meeting on 2024-04-02 from 16:00:00 to 17: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-04-01 @ 16:00 UTC - Fedora 40 Blocker Review Meeting
by Adam Williamson 31 Mar '24

31 Mar '24

# F40 Blocker Review meeting # Date: 2024-04-01 # Time: 16:00 UTC # Location: https://matrix.to/#/#blocker-review:fedoraproject.org?web-instance[element.… Hi folks! It's time for another blocker review meeting. We have 3 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+40+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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

arm April 2024