Description of problem: On my Fedora 17 system the NVidia blob is in use (YES, YES, shame on me!). Therefore kernels are booted with nouveau.modeset = 0, thus disabling KMS. When fedup-dracut runs - you only see the "plymouth text mode" with the colored bar and the text "Fedora 18" - after pressing ESC you don't see anything anymore (related to bug 883075 ?) - after pressing ESC again you get "plymouthd: could not start boot splash: No such file or directory" Version-Release number of selected component (if applicable): 0.7.2-1.fc17
I suspect that this isn't limited to nvidia blob drivers but to confirm, could you add the following to this bug if you have them: - full command line used for fedup-cli - fedup debug logs (as an attachment) It sounds like the preparation process finished and you were able to get the upgrade started. Did you let it finish or turn off your system before it completed?
Created attachment 672835 [details] /var/log/upgrade.log from final, succesful upgrade attempt I'm assuming that these last log lines indicate a successful update: Jan 04 15:32:29 stefanb-lnx.NVIDIA.COM upgrade[1048]: upgrade finished. Jan 04 15:32:29 stefanb-lnx.NVIDIA.COM systemd[1]: Started System Upgrade. Jan 04 15:32:29 stefanb-lnx.NVIDIA.COM systemd[1]: Starting System Upgrade (post)... Jan 04 15:32:29 stefanb-lnx.NVIDIA.COM upgrade-post[7471]: starting upgrade-post hook I got a little bit confused after the upgrade that I still had the "Fedora 17" text during boot, until I realized that F17 had a *newer* kernel than F18. Command line: fedup --network 18 --debuglog fedupdebug.log --instrepo http://dl.fedoraproject.org/pub/fedora/linux/development/18/x86_64/os Other data shared with bug 891943: attachment 672830 [details] fedup debug log from all attempts attachment 672829 [details] /var/log/upgrade.log from last failed attempt NOTE: I probably won't be able to reproduce this problem with this machine any more. After the successful upgrade I followed the advice to upgrade grub with grub2-install & grub2-mkconfig. That changed the settings for my system in such a way that dracut now uses graphical login *without* KMS. It looks like a low-resolution (640x480???) VESA framebuffer to me. Also the console font now looks different. So I assume that the latest Grub2 code is able to initialize some better VESA modes from the BIOS than plain ol' VGA 40x25 text console.
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.