Oooh, look! A shiny thing!

Hmm.

Today I was supposed to be finalizing the test cases for Thursday’s switchable graphics Test Day.

Instead, thanks to this:

(jeff) adamw: Hey, I’ve been approached by 2 different people telling me dnf system-upgrade was failing. In both cases they had to import the F24 key manually. And in both cases they were going F21->F24. Do you know if that’s a documented limitation somewhere?

I somehow wound up spending the day using yum and dnf to upgrade a virtual machine from Fedora 13 to 15, to 16, to 17, to 23, to 24. And making a bunch of improvements to:

Easily distracted?

Moi?

Oh, sorry, I saw something shiny over there…(wanders off)

5 Responses

  1. liam
    liam November 2, 2016 at 2:04 pm | | Reply

    Speaking of persistent….
    any thoughts about whether MacBooks with hardware muxers fit under testing day purview?
    The feature page didn’t specify (other than saying that nvidia users shouldn’t expect their card to ever an low power state when switched to the igpu…but even that was unclear as to whether it was referring to the nvidia card or the nvidia blob—my guess was that it assumed use of nouveau and nouveau’s power state super is highly variable) so, it’s quite unclear if this is the kind of data that you’re interested in for this particular test day.
    BTW, we’re already install f25 based on the 30 Oct compose in koji, and it’s mostly working well*.

    *We encountered 3 problems (one of which we’ve already submitted a bug report): 1) install always failed at the stage where blue loader was being written (submitted), 2) when running from the live USB the screen backlight keys actually worked but once it was installed they no longer did anything (only way to change backlight from maximum was to use send BRIDGE_CONTROL=1 to the PCI address of the gpu and then set brightness through sysfs, 3) wasn’t able to get past that boot loader error until I deleted the osx partitions (this is complicated, and related to the first bug, which I reported on bugzilla as being fixed by removing the efivar that had Fedora as the default boot but I now think it may have been caused by my, accidental, erasure of the osx partitions).

    Sorry for the wall of text:)

  2. marius
    marius November 3, 2016 at 8:36 am | | Reply

    i hope you thougth of a way not to interfere with i.e. nvidia builds from rpmfusion, because they just work flawlessly on one gpu systems.

Leave a Reply to liam Cancel reply

Your email address will not be published. Required fields are marked *