16:00:04 #startmeeting Fedora ARM Working Group Meeting 16:00:04 Meeting started Tue Jan 9 16:00:04 2024 UTC. 16:00:04 This meeting is logged and archived in a public location. 16:00:04 The chair is coremodule. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 16:00:04 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:00:04 The meeting name has been set to 'fedora_arm_working_group_meeting' 16:00:04 #chair pwhalen pbrobinson jlinton jforbes coremodule 16:00:04 Current chairs: coremodule jforbes jlinton pbrobinson pwhalen 16:00:04 #topic roll call 16:01:28 * jlinton waves 16:01:56 * pwhalen is here 16:01:59 .hi 16:01:59 morning 16:02:00 pboy: pboy 'Peter Boy' 16:02:44 hi all 16:02:50 thanks for being here. 16:02:58 #topic 1) ==== Stable Releases ==== 16:02:58 #info Fedora-Cloud-39-20240109.0 16:02:58 #link https://openqa.fedoraproject.org/tests/overview?distri=fedora&version=39&build=Fedora-Cloud-39-20240109.0&groupid=5 16:03:07 anything to discuss on the topic of f39? 16:03:51 #info No new info to report on F39. 16:03:59 #topic 2) ==== Kernel Status ==== 16:03:59 #info F38 kernel-6.6.10-100.fc38 16:03:59 #info https://koji.fedoraproject.org/koji/buildinfo?buildID=2339430 16:03:59 #info F39 kernel-6.6.10-200.fc39 16:04:00 #link https://koji.fedoraproject.org/koji/buildinfo?buildID=2341539 16:04:01 #info Rawhide kernel-6.7.0-68.fc40 16:04:02 #link https://koji.fedoraproject.org/koji/buildinfo?buildID=2342369 16:04:04 kernel status! 16:04:22 I saw a rawhide kernel was currently building, but didn't link it to the meeting since it wasn't complete. 16:04:31 The 6.7.0 kernel is starting the stabilization process, I expect the test week will be in 2 weeks 16:04:54 perfect. jforbes have you been in touch with Sumantro in the new year? 16:05:06 Hello, I'm new at this meeting 16:05:11 I have not yet, I planned to this afternoon 16:05:21 no worries, I was just curious if he was on PTO or not 16:05:32 hello linuxfriend01, glad to have you here 16:05:36 not sure, I was last week, so only back a day so far 16:06:04 #info 6.7.0 is starting the stabilization process, there should be a test week in ~two weeks. 16:06:55 anything else for kernel? 16:07:40 thanks for the update jforbes 16:07:42 #topic 3) ==== Bootloader Status ==== 16:07:42 #info uboot-tools-2024.01-1.fc40 16:07:42 #link https://koji.fedoraproject.org/koji/buildinfo?buildID=2342531 16:07:49 nothing else at the moment, 6.8 merge window just opened, so too early to tell 16:08:06 gotcha 16:08:19 looks like a new uboot dropped yesterday, testing here would be helpful 16:09:14 #topic 4) ==== Fedora Rawhide status === 16:09:14 #info OpenQA Testing Fedora-Rawhide-20240108.n.0 16:09:14 #info https://openqa.fedoraproject.org/tests/overview?distri=fedora&version=Rawhide&build=Fedora-Rawhide-20240108.n.0&groupid=5 16:09:17 Right before I left I noticed a problem with shim and machines with EFI_MEMORY_ATTRIBUTES, i'm told it is a known bug/fix but doesn't look like the fedora shim has it. (I need to dig into this some more) 16:09:32 #undo 16:09:32 Removing item from minutes: INFO by coremodule at 16:09:14 : https://openqa.fedoraproject.org/tests/overview?distri=fedora&version=Rawhide&build=Fedora-Rawhide-20240108.n.0&groupid=5 16:09:33 #undo 16:09:33 Removing item from minutes: INFO by coremodule at 16:09:14 : OpenQA Testing Fedora-Rawhide-20240108.n.0 16:09:35 #undo 16:09:35 Removing item from minutes: 16:10:18 thanks jlinton, was that before the winter break? 16:10:37 Yes, so I need to dig into it today. 16:11:32 EFI_MEMORY_ATTRIBUTES protocol support to be clear 16:12:00 thanks for looking into it, if you file a bugzilla report, will you paste it into the fedora-arm channel? 16:12:12 Yes, once I find the patch/test it. 16:12:36 thanks 16:12:41 #topic 4) ==== Fedora Rawhide status === 16:12:41 #info OpenQA Testing Fedora-Rawhide-20240108.n.0 16:12:41 #info https://openqa.fedoraproject.org/tests/overview?distri=fedora&version=Rawhide&build=Fedora-Rawhide-20240108.n.0&groupid=5 16:12:57 I am interested in the status of the server installation. I was offline for some time. 16:13:04 I think it is a LVM bug that affects not only ARM, but also standard LVM administration 16:13:22 But I'm notg sure 16:13:23 at a quick glance, rawhide is failing all over the place, i will look into this after the meeting 16:14:10 I haven't tested server since the break, only workstation, so I'm not sure here 16:14:50 OK, I'll test the rawhide status and report in the channel 16:15:10 thanks pboy, I'll be around 16:16:32 #topic 5) ==== Open Floor ==== 16:16:38 open floor! anyone have anything? 16:17:14 I'm running Workstation with LVM on my Rock5 with Rawhide without LVM errors. 16:17:27 I poked on the x86 optimized binaries conversation that its worthwhile to assure that it works on arm64 as well. 16:17:45 but I think there may be a baseline definition problem. 16:19:14 linuxfriend01, yeah, we had/have an issue with ARM server and seemingly LVM, but it only manifests on server... if you wanted to test server on your HW and report in-channel, that would be very helpful! 16:19:58 Okay, I can do this. 16:20:15 Yes, but the LVM bug also affects workstations with LVM; 16:20:28 thanks for the help linuxfriend01 16:20:54 The integration of new LVM VGs is lacking. 16:21:08 pboy, it appears to only be affecting our server images 16:21:31 and I'm not sure if anything has been fixed over the break (probably not) but I haven't tested yet 16:21:51 coremodule The installation issue is manifest on server only. 16:22:14 But try to ad a new VG on an existing system. It doesn't work 16:22:30 hmm, okay. I will test this. 16:22:53 That LVM but is the cause that ARM installer fails - at least according to my tentative tests so far. 16:23:01 gut -> bug 16:23:39 but -> bug - sorry 16:24:11 pboy: gut bugs can be really nasty :P 16:24:30 :-) 16:25:13 alright everyone, thanks for attending today, unless there is an objection, I'm going to close the meeting in 5... 16:25:20 4... 16:25:24 3... 16:25:29 Just for information: We are planning a special server edition for home lab and ARM SBC, possibly for F41. 16:25:29 2... 16:25:38 Would be good if we could get some support for it / some feedback on our texts and lanning here. 16:25:49 for clarification: who is "we"? 16:25:50 whats the difference from the normal server images? 16:26:03 we = server Working Group 16:26:15 got it 16:27:15 jlinton not final yet, but preinstalled and preconfigured applications, may be basendon OS-tree 16:29:20 pboy, when you have an image, let us know, I 16:29:50 We can organize an official time to test it as well as potentially add it to the weekly agenda 16:30:37 We are in an early stage. 16:31:02 keep us posted! 16:31:07 But I'm writing a planing text. Would be fine to get feedback on that. 16:31:24 sure, when it's ready, we can discuss it here 16:31:39 Thanks 16:31:53 anything else this week? 16:32:25 #endmeeting