On 10/20/2017 06:53 PM, Ed Greshko wrote:
If I remember correctly, and that is a big if, the process that builds the new drivers is kicked
off between the "clean-up" and "verify" phase of the dnf process.
I think it generally doesn't work at that point even if it does try.
Question: How long should I have waited?
There is no set time since it is a variable depending on CPU and disk
performance.
After an upgrade I am often left with a blinking cursor. I just walk away and
come back later to find the login screen.
At the end of the upgrade process there are a lot of scripts and stuff
that run, sometimes for a long time depending on the speed of the computer.
When, if, you find yourself in the same situation you should just bring up a
console and check the log file to see what is happening.
I'm not clear if this happened at the end of the upgrade process or on
the first reboot. If it's at the end of the upgrade, then there are no
other consoles. On the reboot, if it's made it far enough, then there
will be.
Question: I did not run dnf after 2200. Who or what did? (not a complaint;
rather,
I'm curious)
But when did you reboot? akmod will check for a working nVidia driver on each
boot.
And akmods runs dnf to install the rpm it builds.
2017/10/19 14:36:16 akmods: Could not install newly built RPMs. You can find
them and the
logfile
The above indicated that the rpm was built, but could not be installed. Most
likely due to the dnf command still having the rpm database locked.
Right, so the next reboot will be able to do the install.
_______________________________________________
users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
