15:00:14 <coremodule> #startmeeting Fedora ARM Working Group Meeting
15:00:14 <zodbot> Meeting started Tue Oct 31 15:00:14 2023 UTC.
15:00:14 <zodbot> This meeting is logged and archived in a public location.
15:00:14 <zodbot> The chair is coremodule. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions.
15:00:14 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:00:14 <zodbot> The meeting name has been set to 'fedora_arm_working_group_meeting'
15:00:14 <coremodule> #chair pwhalen pbrobinson jlinton jforbes coremodule
15:00:14 <zodbot> Current chairs: coremodule jforbes jlinton pbrobinson pwhalen
15:00:14 <coremodule> #topic roll call
15:00:28 <jforbes> morning
15:01:05 <coremodule> morning jforbes
15:01:50 * pwhalen is here
15:02:10 <coremodule> hi pwhalen
15:03:22 <coremodule> lets get started with the stable release
15:03:24 <coremodule> #topic 1) ==== Stable Releases ====
15:03:24 <coremodule> #info Fedora-Cloud-38-20231031.0
15:03:24 <coremodule> #link https://openqa.fedoraproject.org/tests/overview?distri=fedora&version=38&build=Fedora-Cloud-38-20231031.0&groupid=5
15:03:27 <coremodule> Anything here?
15:03:32 <coremodule> I don't have anything...
15:04:50 <jforbes> I don't either
15:05:16 <coremodule> Okay, let's move to kernel
15:05:17 <coremodule> #topic 2) ==== Kernel Status ====
15:05:18 <coremodule> #info F38 kernel-6.5.9-200.fc38
15:05:18 <coremodule> #info https://koji.fedoraproject.org/koji/buildinfo?buildID=2311763
15:05:18 <coremodule> #info F39 kernel-6.5.9-300.fc39
15:05:18 <coremodule> #link https://koji.fedoraproject.org/koji/buildinfo?buildID=2311765
15:05:19 <coremodule> #info Rawhide kernel-6.6.0-61.fc40
15:05:21 <coremodule> #link https://koji.fedoraproject.org/koji/buildinfo?buildID=2313875
15:05:23 <coremodule> #info Please test and report any issues to #fedora-arm or the mailing list.
15:05:40 <coremodule> jforbes, could you give an update?
15:06:29 <jforbes> I haven't seen a whole lot regarding 6.6 on aarch64 yet. We should have the Fedora stable branch created this week, and test week will be 2 weeks from now.
15:07:22 <jforbes> The lack of response on it is not really surprising, it seems we have fewer people testing aarch64 on rawhide. It happens like this most releases
15:08:17 <coremodule> sure, that makes sense. I don't really have a chance to look at rawhide until after we ship our milestone.
15:08:19 <jforbes> I am guessing a lot of that is due to the nature of the hardware.   Anyway, I expect the 6.7 cycle will be a bit more interesting as I think there are some Pi 5 bits staged
15:09:31 <coremodule> Thanks for the update jforbes
15:09:51 <coremodule> #topic 3) ==== Bootloader Status ====
15:09:51 <coremodule> #info uboot-tools-2023.10-0.9.fc40
15:09:51 <coremodule> #link https://koji.fedoraproject.org/koji/buildinfo?buildID=2314249
15:09:51 <coremodule> #info uboot-tools-2023.07-3.fc39
15:09:52 <coremodule> #link https://koji.fedoraproject.org/koji/buildinfo?buildID=2311866
15:10:08 <jforbes> NP.  We should maybe look at backporting the Pi 5 graphics changes to 6.6 at some point if it makes sense
15:10:30 <coremodule> jforbes, Cool! Have you been hands-on with a RPi5 yet?
15:10:39 <jforbes> I have not yet
15:10:53 <coremodule> Same here
15:12:18 <coremodule> pwhalen, Do you have any info regarding uboot?
15:13:00 <pwhalen> I don't think so.
15:13:19 <coremodule> Cool, no worries.
15:13:19 <pwhalen> I think the latest build addresses most of the blockers.
15:14:03 <pwhalen> Display on server needs nomodeset, for IoT we blacklist vc4 so we're ok
15:15:01 <coremodule> Okay, thanks for the update. I didn't think the nomodeset fix was in the new arm-image-installer, but when I still had to add it after using 3.9.2 yesterday, I wasn't sure if I was doing it correctly. I'll add my karma after the meeting.
15:15:27 <coremodule> I thought maybe it was supposed to detect it was a server image and add the kernel arg.
15:15:30 <pwhalen> you have to add it as a kernel arg, its not automatic
15:15:59 <coremodule> Sure, okay. Anyway, I'll add some karma here shortly.
15:16:19 <coremodule> #topic 4) ==== Fedora 39 status ===
15:16:20 <coremodule> #info OpenQA Testing Fedora-39-20231031.0
15:16:20 <coremodule> #info https://openqa.fedoraproject.org/tests/overview?distri=fedora&version=39&build=Fedora-39-20231031.0&groupid=5
15:16:20 <coremodule> #info Fedora 39 Candidate RC-1.4 Available Now!
15:16:20 <coremodule> #link https://fedoraproject.org/wiki/Test_Results:Fedora_39_RC_1.4_Summary
15:16:21 <coremodule> #info Accepted Blockers & Freeze Exceptions
15:16:23 <coremodule> #link https://qa.fedoraproject.org/blockerbugs/milestone/39/final/buglist
15:16:25 <coremodule> #info Fedora 39 Schedule
15:16:27 <coremodule> #link https://fedorapeople.org/groups/schedule/f-39/f-39-key-tasks.html
15:17:06 <jlinton> The rpi is the only arm specific problems at the moment, right?
15:17:15 <coremodule> Big thing here, RC 1.4 is out, any testing you can do is super appreciated at this stage. If you do test, please report in the test matrix so we can log that it's been tested.
15:18:34 <coremodule> Yeah, or at least as far as we know. I tested server and IoT on an NanoPi NEO2 that I found yesterday, it's horribly slow, but it did work. I just mention that because all of my testing this release has been on RPi or virt, so it was a nice change to see it work on an Allwinner chip yesterday.
15:20:21 <coremodule> Anything else for F39?
15:20:43 <coremodule> #topic 5) ==== Open Floor ====
15:21:08 <jlinton> Are there SoC's that need the msm driver in the initrd? Or can we remove it?
15:24:02 <jlinton> I guess i'm questioning if its needed for graphics anywhere, or we have uefi framebuffers from uboot/etc. Because at least on the x13s its better if it doesn't try to start while running out of the initrd (where it fails and blanks the screen) vs waiting until the rootfs is mounted, where it can satisfy all the clk/regulator/etcs it needs on that machine.
15:25:55 <jforbes> I don't kmow of a case where it is necessary, but I could be missing something
15:39:24 <coremodule> pwhalen, jlinton, jforbes, QA team is wondering: is RPi the ideal ARM hardware for testing Fedora ARM moving forward? Or is there a better alternative that is more representative of what we want for testing?
15:40:15 <pwhalen> coremodule: I think QA should have a variety of devices. Not just the Pi.
15:40:44 <pwhalen> I believe the project bought a bump of things for people. Pinebook .. etc
15:40:49 <jlinton> Not, really something like the honeycomb might be, a better choice
15:40:55 <pwhalen> er, bunch
15:41:00 <jlinton> I really think they should pick something that is systemready ES+ certified.
15:41:14 <coremodule> pwhalen, Sure, that makes sense. Can you recommend anything? I think they're specifically focused on something that is easy to use.
15:41:26 <coremodule> Unlike the Pinebook, Jetson Nano, etc
15:41:48 <coremodule> Some ARM board that is easy to use on an everyday basis for daily nightly testing
15:41:49 <pwhalen> We should be making sure things work.. things people will use, not just a single device.
15:41:51 <coremodule> daily nightly, lol
15:42:38 <coremodule> jlinton, thanks for that recommendation, I'll look into systemready ES+ stuff
15:44:16 <coremodule> pwhalen, Yes, agreed. But is there better hardware available than the Pinebook and Jetson Nano? We have a Pinebook in Brno, but it's hated because it's slow and not easy to use, same with Jetson Nano. QA team has budget to procure new boards, but wanted me to ask here for suggestions on what else to get.
15:44:49 <jlinton> One of the jetsons is certified isn't it?
15:44:54 <jlinton> I might have to check the list.
15:45:35 <coremodule> jlinton, I can't find the list, do you have a link?
15:45:58 <jlinton> I'm actually not sure there is a public list, let me poke around a bit.
15:47:53 <coremodule> thanks jlinton
15:49:10 <jlinton> These rk3588 device are popular lately, and have gotten a fair bit up upstream work done.
15:50:21 <jlinton> HW wise its a nice SoC, but i'm not sure if any of them have been even SystemReady IR certified, so...
15:51:54 <coremodule> jlinton, thanks. Looking at RockPi 5B
15:52:54 <coremodule> thanks all for the meeting
15:52:56 <coremodule> #endmeeting