FedoraThis forum is for the discussion of the Fedora Project.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
It went to the REBOOT and started upgrade but after upgrade complete it would only boot into F17 and would go to the login , can't login as user or root, it comes back to the login each time after entering user name and password.
[MODERATION]Please see contents after merge below:[/MODERATION]
Running fedup from F17 to upgrade to F18, Is this the correct procedure ?
All I have is a live-dvd-KDE.iso, how can I find a iso that will let me upgrade my KDE desktop.
And I get the below Error message.
# fedup-cli --iso /home/jim/Downloads/Fedora-18-i686-Live-KDE.iso --debuglog=fedupdebug.log
setting up repos...
Error: can't get boot images.
The 'fedupiso' repo was rejected by yum as invalid.
This the only thing in /var/log/messages when fedup-cli is run;
Feb 18 18:50:47 localhost dbus[581]: [system] Activating service name='net.reactivated.Fprint' (using servicehelper)
Feb 18 18:50:47 localhost dbus-daemon[581]: Launching FprintObject
Feb 18 18:50:47 localhost dbus-daemon[581]: dbus[581]: [system] Successfully activated service 'net.reactivated.Fprint'
Feb 18 18:50:47 localhost dbus[581]: [system] Successfully activated service 'net.reactivated.Fprint'
Feb 18 18:50:47 localhost dbus-daemon[581]: ** Message: D-Bus service launched with name: net.reactivated.Fprint
Feb 18 18:50:47 ost dbus-daemon[581]: ** Message: No devices in use, exit
Last edited by unSpawn; 02-20-2013 at 04:48 PM.
Reason: //Post-merge clarification
The files downloaded successfully to /var/tmp/fedora-upgrade.
I rebooted and selected the Upgrade option. But, the upgrade failed at the scanning stage, dropping me into a shell. Options were continue with Ctrl-D, or log in as root for maintenance. Logging in as root, mounting partitions and then exiting the shell did not resume the upgrade. But, fortunately the boot process continued using the Fedora 17 kernel. I was able to login and achieve the desktop.
Determined to avoid starting over from scratch, I opened a terminal, logged in as root and used yum to get the downloaded Fedora 18 files installed and Fedora 17 files removed.
Tried the commands below that returned errors reporting version mis-matches.
Rebooted - got boot loop using the Fedora 18 kernel.
Rebooted, and for the heck of it chose the upgrade option.
Wala! The upgrade process completed successfully - but still had boot loop when rebooting.
'grub2-editenv list'
Revealed Fedora 17 kernel was still the default.
Searched internet for possible resolution and discovered additional steps to perform:
'grub2-set-default 'Fedora Linux, with Linux 3.9.4-200.fc18.x86_64''
'grub2-editenv list'
Now returned: saved_entry=Fedora Linux, with Linux 3.9.4-200.fc18.x86_64
Although I have not gone back and tried this, odds are good adding a step after the update files successfully download will lead to a successful, problem free update.
Once all files have successfully downloaded perform the following steps.
Before rebooting into the Upgrade I'd recommend the following:
Open a console/terminal.
Log in as root.
Change to the file system where the update files have downloaded to. This file system no longer exists on my laptop post upgrade, so you'll have to locate it yourself. I am guessing, but it may have been in /var/tmp/ .
then at the prompt:
'yum install ./<kernel-name> to make certain the Fedora 18 kernel is installed before rebooting. You may encounter error messages informing you of missing dependencies or conflicts. All I can say is try to resolve these issues before rebooting into the Upgrade option.
Check to see which kernel version is set to boot:
'grub2-editenv list'
If Fedora 17 kernel is still the default:
'grub2-set-default 'Fedora Linux, with Linux 3.9.4-200.fc18.x86_64'
'grub2-editenv list'
Desired output: saved_entry=Fedora Linux, with Linux 3.9.4-200.fc18.x86_64
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.