15:01:00 #startmeeting Fedora ARM and AArch64 Status Meeting 15:01:00 Meeting started Tue Jan 12 15:01:00 2021 UTC. 15:01:00 This meeting is logged and archived in a public location. 15:01:00 The chair is pwhalen. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:01:00 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:01:00 The meeting name has been set to 'fedora_arm_and_aarch64_status_meeting' 15:01:00 #chair pwhalen pbrobinson jlinton coremodule 15:01:00 #topic roll call 15:01:00 Current chairs: coremodule jlinton pbrobinson pwhalen 15:01:12 good morning folks, who's here today? 15:01:12 good morning pwhalen! 15:01:16 * coremodule is here 15:01:20 * jlinton waves 15:01:30 howdy coremodule, jlinton 15:01:50 * pwhalen gives it a couple of minutes for others 15:03:21 * defolos is lurking in the shadows 15:03:52 step into the light defolos! :) 15:03:58 ok, lets get started. 15:04:08 #topic 1) ==== Userspace Status ==== 15:04:19 Is anyone aware of any new user space issues? 15:04:25 * defolos has nothing to add unfortunately 15:04:40 nothing new her 15:04:57 #info No new issues reported. 15:05:11 #topic 2) ==== Kernel Status ==== 15:05:38 so, the good news first.. we have 5.11 kernels building 15:05:46 #info kernel-5.11.0-0.rc3.122.fc34 15:05:47 #link https://koji.fedoraproject.org/koji/buildinfo?buildID=1667670 15:06:13 There were issues previously with gcc11 and aarch64 15:06:47 testing 5.11 rc2 on armhfp I was either getting a kernel panic or no output on the console 15:07:35 talked with pbrobinson about it yesterday, we were hoping 5.11 rc3, seems not so far 15:09:25 I'll try to get some output today to file a bug 15:10:13 aarch64 seems ok, tested on a few SBC's and enterprise hw, no issues so far. 15:10:42 Anything else for kernel news? 15:11:10 #info armhfp kernel panic on boot. Needs further investigation. 15:11:19 #info Please test and report any issues to the list or #fedora-arm. 15:11:41 #topic 3) ==== Bootloader Status ==== 15:11:57 pwhalen, I'll spend some time today playing with 5.11 rc2 on armhfp 15:13:25 cooll 15:14:09 so we have a new uboot build, but its DOA from what I understand. Use the f33 uboot to test the kernel/user space 15:15:02 #topic 4) ==== Fedora 34 ==== 15:15:13 #info Latest nominated compose (today) 15:15:13 #link https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test 15:15:47 not yet started to test this, first issue I see is initial setup didnt run in openqa. Will take a look and file that one shortly 15:16:04 #link https://openqa.fedoraproject.org/tests/overview?distri=fedora&version=Rawhide&build=Fedora-Rawhide-20210112.n.0&groupid=5 15:17:18 looks likea few issues to look at in the openqa results. 15:17:47 * pbrobinson waves and apologises for being late 15:18:03 howdy pbrobinson, no worries.. just discussing f34 15:18:21 so I've got a few things I'm trying to get to this week for f34 15:18:34 the aforementioned armv7 kernel issue 15:19:18 thx, trying to get some output from it now 15:19:20 and a new u-boot build with a fix for the boot issue, there was a stable 2021.01 release yesterday, the plan is I won't push that until a fix is in place 15:19:38 ok sounds good, can test that as soon as we have a build 15:20:16 #info Fedora 34 Changeset 15:20:16 #link https://fedoraproject.org/wiki/Releases/34/ChangeSet 15:20:42 in the F34 changes, this one looks concerning - "Scale ZRAM to Full Memory Size" 15:20:54 #info Fedora 34 Change: Scale ZRAM to Full Memory Size (Self-Contained Change proposal) 15:20:54 #link https://fedoraproject.org/wiki/Changes/Scale_ZRAM_to_full_memory_size 15:21:08 and of course the armv7 edk2 build for epel8 15:21:24 ah right 15:21:57 so I need to double check but I think that's the ratio we were running the old zram stuff at before for the f33 change so I'm not overly concerned there TBH 15:22:30 I also need to write up the self contained change for armv7 uefi 15:22:52 then definitely less concerning. 15:24:08 That's all I ahd for f34. 15:24:45 Anything else we want to talk about? 15:25:03 I also may have a fix for the rpi4-8gb usb issue I need to test 15:25:20 I need to put together a patch and a scratch kernel build 15:25:46 great, let me know 15:25:55 #topic 5) == Open Floor == 15:26:00 pbrobinson, if you need additional testing, happy to help 15:26:01 👍️ 15:26:12 coremodule: do you have the 8G? 15:26:25 I have a 8gb pi 4 too, but had some trouble getting anything to boot on that 15:26:25 coremodule: yea, let me actually get a patch and a kernel that builds first ;-) 15:26:26 pwhalen, yeah, new acquisition 15:26:32 :) sounds good! 15:26:33 nice! 15:26:50 defolos: it was booting just fine, there's some improvements coming for all of rpi4 15:26:53 coremodule: did you get other hw? 15:27:15 * pwhalen just trying to keep track of what you have too 15:27:20 pbrobinson: awesome, great to hear! Any idea when? 15:27:33 pwhalen, yes, I got a jetson nano as well... i think that's it 15:27:39 * defolos has a jetson nano as well courtesy of @mattdm 15:27:40 I fixed a bunch of stuff over the shut down but there's another bug, mentioned above, I'm chasing in general u-boot, I think f34 should look much better RSN 15:27:44 The newer BCM soc's aren't yet supported on the uefi port either due to the vc firmware modifying the pcie dma ranges 15:27:49 defolos: when I get the time to get to it ;-) 15:27:53 coremodule: awesome-sauce 15:27:57 i think someone else on the fedora qa team was sent a pinebook bro 15:28:01 *pro 15:28:10 I got that too… 15:28:14 I have a hardware problem 15:28:26 defolos: heh, I think we can relate 15:28:32 unlikely given they've not been in stock for some time due to a lack of screen availability for production runs 15:29:44 hmmm, I'll have to check and see what hardware he got. I know someone else on the fedora qa got *something* not sure what exactly 15:31:17 Thanks for joining all! 15:31:21 #endmeeting