15:00:07 <pwhalen> #startmeeting Fedora ARM and AArch64 Status Meeting
15:00:07 <zodbot> Meeting started Tue Feb 13 15:00:07 2018 UTC.  The chair is pwhalen. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:07 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:00:07 <zodbot> The meeting name has been set to 'fedora_arm_and_aarch64_status_meeting'
15:00:07 <pwhalen> #chair pwhalen pbrobinson
15:00:07 <zodbot> Current chairs: pbrobinson pwhalen
15:00:07 <pwhalen> #topic roll call
15:00:18 <pwhalen> morning folks, whos here today?
15:01:17 * pbrobinson o/
15:01:45 <optimist> David Todd (Optimist)
15:01:58 <optimist> Just sitting in to see if I can learn something
15:02:57 <pbrobinson> optimist: welcome!
15:02:57 <pwhalen> welcome optimist!
15:04:34 * jsmith \o
15:04:37 <pwhalen> ok, lets start
15:04:45 <optimist> No problem ... Peter sent a note yesterday and I'm good.
15:04:45 <pwhalen> howdy jsmith
15:05:07 <pwhalen> #topic 1) ==== Userspace Status  ====
15:05:16 <pbrobinson> So the mass rebuild is done
15:05:27 <pwhalen> #info Mass rebuild is complete.
15:05:28 <pbrobinson> it's being signed and tagged atm (might even have finished)
15:05:41 <pbrobinson> so shortly we get to see the fallout
15:05:42 <jsmith> Whee!
15:06:02 <pwhalen> #info List of failures - https://kojipkgs.fedoraproject.org/mass-rebuild/f28-failures.html
15:06:27 <pwhalen> #info List of packages needing rebuild - https://kojipkgs.fedoraproject.org/mass-rebuild/f28-need-rebuild.html
15:07:32 <pwhalen> is anyone aware of any userspace issues?
15:07:54 <pbrobinson> I'm not aware of any specific issues, there's a few possible ones
15:09:02 * jsmith is happy to not find his name somewhere on that list
15:09:11 <pbrobinson> mine is....
15:09:24 <pbrobinson> most of mine aren't a surprise to me though :-D
15:10:36 <pbrobinson> there's an issue with golang that the maintainer is investigating on aarch64
15:10:51 <pbrobinson> but that'll be resolved shortly, not a major issue
15:11:15 <pwhalen> reminder I need to get that host for him. thanks.
15:11:24 <pwhalen> #topic 2) ==== Kernel Status ====
15:11:36 <pwhalen> #info Latest - kernel-4.16.0-0.rc1.git0.1.fc28
15:11:36 <pwhalen> #link https://koji.fedoraproject.org/koji/buildinfo?buildID=1043729
15:11:57 <pbrobinson> so 4.16rc1 is built, will be in the next rawhide compose
15:12:37 <pwhalen> looks ok so far in the limited testing I've done, anyone seeing any issues?
15:12:42 <pbrobinson> 4.15.x is on it's way to stable, there should be a 4.15.3 release some time today, that will have spectre/meltdown fixes for ARM, plus a bunch of other fixes for issues I've seen
15:12:55 <pwhalen> #info F27 - kernel-4.15.2-301.fc27
15:12:55 <pwhalen> #link https://koji.fedoraproject.org/koji/buildinfo?buildID=1043716
15:13:16 <pwhalen> #info Please test and report any issues to the list or #fedora-arm.
15:13:26 <pbrobinson> that build doesn't have spectre/meltdown and won't be submitted as an update but it's good for people to test with
15:13:50 <optimist> Installed 4.15.2 this morning, but not enough time to exercise it yet.
15:14:01 <optimist> No problem coming up and basics.
15:14:11 <pbrobinson> optimist: which device/platform?
15:14:12 <pwhalen> optimist, excellent, which hardware?
15:14:21 <pwhalen> heh
15:14:30 <optimist> Raspberry Pi3B; from microSD in this case
15:14:48 <optimist> Haven't tried it from USB yet.  Will try thought
15:14:51 <optimist> Though
15:15:01 <pwhalen> nice, thanks for testing
15:15:03 <pbrobinson> optimist: ARMv7 or aarch64? There'll be some further fixes in the next build for RPi that I added
15:15:09 <optimist> aarch64
15:15:59 <optimist> Killed X in the update from 4.13 to 4.14 and I haven't fixed that yet, so no gui in 4.15.  I seem to always have problems with X
15:17:06 <optimist> So I haven't tried to set up WiFi from CLI, can't verify that it works yet.  Just using EN for now
15:17:13 <pbrobinson> optimist: yes, there's a few fixes that should help monitor detection in the patches I pushed, it's working "OK" for me, but it's not problem free, I have a bunch of bits to follow up with upstream
15:17:39 <pbrobinson> optimist: cli options covered here https://nullr0ute.com/2016/09/connect-to-a-wireless-network-using-command-line-nmcli/
15:18:30 <optimist> COOL!  I'll look forward to that.  are the monitor detection fixes in today's push or should be in 4.15.2?
15:19:23 <optimist> And thanks for the pointer to the wireless cli business.  I'll give it a shot, too.
15:19:47 <pbrobinson> optimist: they;re in the build pwhalen referenced, will be part of 4.15.3 that will be pushed as an update
15:20:12 <optimist> Great.  I'll install it as soon as it's available.
15:20:12 <pwhalen> #topic 3) ==== Bootloader Status ====
15:20:26 <pbrobinson> new 2018.03-rc2 build today
15:20:28 <pwhalen> #info uboot-tools-2018.03-0.3.rc2.fc28
15:20:28 <pwhalen> #link https://koji.fedoraproject.org/koji/buildinfo?buildID=1043960
15:20:54 <pwhalen> I've not tested that at all, pbrobinson have you had a chance?
15:21:01 <jlinton> Hi, so I didn't find a defect with anaconda/etc failing to create gpt partitions.
15:21:03 <pbrobinson> the 2018.03 release will be what we'll be shipping for F-28 so wide testing is appreciated (you can test on older releases too)
15:21:15 <pbrobinson> nope, I've not had time yet either
15:21:35 * jsmith hasn't either
15:21:36 <jlinton> but the 2018 rawhide I tried installing from the other day, failed to create the uefi system partition correctly
15:21:59 <jlinton> or rather mark it correctly because it was there, but the partition type was mbr/fat16
15:22:07 <jlinton> which meant my firmware couldn't find it.
15:23:07 <pwhalen> jlinton, yea, seeing the same issues, not reproducable on x86. will file the bz today
15:23:39 <jlinton> I'm guessing whatever it does to detect BIOS vs UEFI is failing on arm
15:25:09 <pwhalen> jlinton, there is also another bug on efivar - https://bugzilla.redhat.com/show_bug.cgi?id=1542141
15:25:12 <pbrobinson> jlinton: you mean F-28?
15:25:43 <pbrobinson> jlinton: it checks for something in sys or proc from memory
15:26:32 <jlinton> Oh nice, I was actually running the reinstaller to check that my uefi variable changes were working correctly (they seem to be)
15:26:59 <jlinton> Although now i'm questioning that...
15:27:35 <jsmith> pwhalen: Mind copying me (or sending me the link) when you've done that, so I can follow along?
15:27:55 <pwhalen> jsmith, will add you to the cc on it
15:28:31 <pwhalen> #topic 4)  == F28 Testing ==
15:28:33 <jsmith> pwhalen: Thanks!
15:30:09 <pwhalen> with the mass rebuild complete, branching is scheduled for next Tuesday (Jan 20th)
15:30:16 <pbrobinson> so the 4.16 kernel and the 2018.03 u-boot is easily tested (even on F-27), the full F-28/rawhide compose should happen shortly once any of the fallout from the mass rebuild happens
15:31:05 <pwhalen> its been a while since we had a successful rawhide compose
15:31:56 <pwhalen> has anyone hit anything while testing f28 not mentioned today?
15:33:02 <pbrobinson> I'll probably start to upgrade late this week
15:34:29 <pwhalen> great, thanks..
15:34:30 <pwhalen> #topic 5) == Open Floor ==
15:35:12 <jlinton> Well, the DW sd driver (or the dependent clock driver) missing from the initrd is a problem on the hikey
15:35:27 <jlinton> keeps the machine from booting after the gpt/uefi system partition problem is corrected
15:35:54 <jlinton> I need to spend a bit of time tracking down exactly what is wrong as pbrobinson says there is a dracut change in place to pick up the driver.
15:37:11 <pbrobinson> jlinton: I'll also check rawhide dracut when I get a sec to make sure it's all still there as I expected
15:39:43 <pwhalen> ok, if nothing else.. closing in a moment
15:41:18 <pwhalen> #endmeeting