15:00:42 #startmeeting Fedora IoT Working Group Meeting 15:00:42 Meeting started Wed Feb 17 15:00:42 2021 UTC. 15:00:42 This meeting is logged and archived in a public location. 15:00:42 The chair is pwhalen. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:42 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:00:42 The meeting name has been set to 'fedora_iot_working_group_meeting' 15:00:42 #chair pwhalen pbrobinson bcotton tdawson puiterwijk coremodule 15:00:42 #topic roll call 15:00:42 Current chairs: bcotton coremodule pbrobinson puiterwijk pwhalen tdawson 15:00:51 Good morning folks, who's here today? 15:00:54 Good morning, /me is here! 15:00:59 .hello2 15:01:00 bcotton: bcotton 'Ben Cotton' 15:01:00 howdy coremodule 15:01:12 hey pwhalen, bcotton 15:01:14 * pbrobinson o/ 15:01:14 good $daypart, everyone 15:01:28 * tdawson is here. 15:01:32 heh, and a good $daypart to you as well :) 15:01:49 hopefully everyone has finished digging out today 15:02:34 it's not cold enough here to nee to dig anywhere 15:03:54 we got enough to go around if you want some 15:04:01 ok, lets get started 15:04:09 #topic 1) ==== Working Group process and admin ==== 15:04:09 #link https://docs.fedoraproject.org/en-US/iot/ 15:04:16 Anything for admin this week? 15:05:10 nothing I can think of 15:05:21 anything on test days or do that in f34? 15:05:39 pbrobinson, yes, can we wait for the open floor or come back, im multi-meeting wrangling 15:05:59 #info No changes. 15:06:06 #topic 2) ==== Fedora 33 status ==== 15:06:15 #info Latest - Fedora-IoT-33-20210214.0 15:06:15 #link https://openqa.fedoraproject.org/tests/overview?distri=fedora&version=33&build=Fedora-IoT-33-20210214.0&groupid=1&groupid=5 15:06:58 looking ok here. Anyone hit any issues? 15:08:12 #info No new issues reported. 15:08:43 #topic 3) ==== Fedora 34 status ==== 15:08:51 #info Latest compose Fedora-IoT-34-20210215 15:08:52 #link https://openqa.fedoraproject.org/tests/overview?distri=fedora&version=34&build=Fedora-IoT-34-20210215.0&groupid=1&groupid=5 15:10:02 Looking better, we still have parsec failing in f34, but the systemd-oomd was fixed 15:10:52 We should also have armhfp images again next compose. Those were failing due to a kernel issue pbrobinson fixed yesterday 15:11:10 * jsmith is here, but having connectivity issues, apparently 15:11:14 yes, I fixed a bunch of the parsec but I'm waiting for a new parsec daemon to fix the last bits 15:11:52 so overall I think F-34 is branched properly, I need to spin up a couple of images to verify 15:12:08 #info Parsec fixes in progress, waiting for a new parsec daemon to fix the last bits. 15:12:13 I fixed the ARMv7 kernel issue last night and got a build done this morning 15:12:13 okay I'm back, had a 1x1 bluejeans call that went over in time 15:12:22 so that should unblock too as of tomorrow 15:12:33 awesome 15:12:38 pbrobinson++ 15:12:38 pwhalen: Karma for pbrobinson changed to 7 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 15:13:11 I've started to look at an updated u-boot to fully support Jetson Nano for IoT and I got a local build completing earlier today 15:13:26 I have yet to actually see if it works 15:13:36 that's great 15:13:42 but I'm hoping I can push a new build by EOW 15:13:43 pbrobinson, willing to help test that if you need it 15:13:48 pbrobinson++ 15:13:48 jsmith: Karma for pbrobinson changed to 8 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 15:13:53 I can help test on the Nano as well 15:14:14 coremodule: yep, once I have a new uboot build it will be the same process as before and feedback will be gladly welcome 15:14:31 thumbs up 15:14:42 one thing to note here is to stick witl L4T release .4 as the last .5 is a little broken 15:15:00 Oh? 15:15:08 Broken in what ways, may I ask? 15:15:13 as in L4T R32.4.4 15:15:55 broken if you're not flashing the full L4T distro with the firmware, AKA flashing only the firmware to SPI 15:16:05 ACK 15:16:13 I've not actually tried, just got a heads up from NV about the problem 15:17:07 OK 15:17:08 tdawson: while you're here and I remember we should also now have OOTB working wifi on the Rock960 15:17:46 and I'm working on finalising the rockchips support as part of the UEFI on ARMv7 feature 15:18:50 that will be nice 15:18:59 Anything else for F34? 15:19:43 #topic 4) ==== Fedora 35 (Rawhide) status ==== 15:19:46 oh and rpi4 support has improved a lot, I'm expecting a new firmware soon that should fix the last of the USB problems 15:20:05 I've not actually tested it at all on IoT as yet though so testing there is welcome 15:20:19 pbrobinson: Ya!! (Sorry, stepped out for a minute) 15:20:29 \0/ saves me from pestering you about that one (usb) 15:20:30 thanks 15:21:47 yea, the rpif may have worked out how to actually set a pci bar properly and consistently 15:21:57 iot rawhide looks like it may need some new needles, will need to look some mroe 15:22:05 #link https://openqa.fedoraproject.org/tests/overview?distri=fedora&version=35&build=Fedora-IoT-35-20210217.0&groupid=1&groupid=5 15:22:59 Anything else for rawhide? 15:23:11 not from me 15:23:31 #topic 5) ==== Open Floor ==== 15:23:40 test days? 15:23:47 yep 15:24:28 would like to propose either wednesday the 11th of march, thursday the 12th of march, or friday the 13th of march for the beta testday 15:25:07 this is a few days before beta launch, beta launch being 3-16 if we don't slip at all 15:25:34 personally I'd prefer not Fri, but I can likely make most of them work 15:25:42 to some degree at least 15:26:10 I like Wednesdays, we can remind people durign the meeting 15:26:21 how about Thursday the 12th? the thought being we will have had this meeting the day before to ensure anything we wanted can be implemented 15:26:37 pwhalen, I'm good with Wednesday too, we can do the same on Wednesday 15:26:58 Wednesday the 11th then? 15:27:11 heh, yea Thursday is a little meeting heavy for me so I wont be around as much 15:27:14 wfm 15:27:38 perfect, wednesday it is. I will wait on scheduling the final test day until later on in the schedule 15:27:45 as far as test cases go 15:27:52 great, thanks for setting it up 15:27:56 I should either be available for any of those days, or none. But right now, it looks like any of them are good for me. 15:28:22 last week pwhalen you had mentioned some better coverage in PARSEC and zezere. is there a good time I can get with you and/or pbrobinson to write some stronger test cases for use in the test day? 15:28:24 tdawson: awesome, thanks 15:28:46 preferably in the next week or two 15:29:07 coremodule: tests need to be written for those 15:29:34 sure, I just don't know exactly how to set them up, so will need some guidance on your part if I can 15:29:35 The existing http zezere install I never got working. I'll try to fix that 15:30:09 coremodule: right, thats the part we need to work out 15:30:34 is there a day/time that works for you to get together and hammer some of this out? 15:30:37 coremodule: with pwhalen likely the best 15:31:13 coremodule: sure, we can discuss after the meeting 15:31:18 sounds good. 15:31:21 I have two more things 15:32:36 pbrobinson, last week you mentioned lack of testing on previous test days. Wondering what your thoughts on having a "test day" competition where the top (new) contributor is sent an ARM board to use for testing in the future? some kind of incentive to get people to test. also, if you like the idea, if you have the budget to do so :) 15:33:45 I have no budget what so ever, that would be one for mattdm/marie 15:33:59 gotcha. 15:34:31 sounds good to me! okay, /me passes the torch back to pwhalen and stumbles off the stage 15:34:49 ..wait, that was one 15:34:55 come back! :) 15:35:04 oh right 15:35:05 whoops 15:35:08 heh 15:36:13 pbrobinson, pwhalen, QA team was wondering if you guys knew anything about ARM/IoT devices that were shipped for people to use. do you know if they have all been shipped? 15:36:42 I believe they were all shipped out last year 15:36:57 pbrobinson, do you know if any pinebook pro's were shipped? 15:36:58 Same, some of what we wanted wasnt available 15:37:07 no, they werent available 15:37:28 coremodule: no pinebook pros, not available, and also not associated with IoT 15:38:06 got it! That's what they wanted to know. Thank you. /me covers his face and hurriedly walks off stage in shame for not knowing how to count to two 15:38:39 the PBP is due back in stock in mid march 15:39:05 and I should have one of the early quartz64 devices soon 15:39:25 that will be a bit of a longer road due to the upstream status of rk356x 15:39:25 looking forward to hearing about that one 15:40:48 thank you all 15:40:48 #endmeeting