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.
I'm trying to upgrade my EeePC from Fedora 17 to 18. No matter which way (fedup, yum, fedora-upgrade) I choose, all of them fail due to a dependency problem with the xorg intel driver.
Error: package: xorg-x11-drv-intel-2.19.0-1.fc17.x86_64 (@fedora/17)
Requires: xserver-abi(videodrv-12) >=0
Removing: xorg-x11-server-Xorg-1.12.4-7.fc17.x86_64 (@fedora/17)
xserver-abi(videodrv-12) = 1
Updated By: xorg-x11-server-Xorg-1.13.3-3.fc18.x86_64 (updates)
Not found
Error: Package: xorg-x11-drv-intel-2.19.0-1.fc17.x86_64 (@fedora/17)
Requires: libudev.so.0()(64bit)
Removing: libudev-182-3.fc17.x86_64 (@updates/17)
libudev.so.0()(64bit)
Obsoleted By: systemd-libs-201-2.fc18.9.x86_4 (updates)
Not found
When upgrading with fedup, I end up with a running system that cannot start gdm. In F18 console, yum displays the intel driver from F17 and doesn't display any possible update. Xorg log shows that it cannot load the module intel because of the missing dependency library libudev.so.0.
I am entirely clueless and haven't found any solution to this specific problem.
Has anybody experienced this? Is there anything I can do to upgrade the F17?
Thanks.
Last edited by w359; 07-17-2014 at 02:46 PM.
Reason: quoted error message
It might have been possible in the past when both F17 and F18 were supported. Note I said "might".
Sometimes upgrades work, sometimes not - for all distros, but Fedora is a particularly active environment. Even if you were of a disposition to stay current, clean installs is usually a better bet.
Threatening to leave Fedora will influence no-one. Least of all the Fedora devs were they inclined to pass this way.
I apologize if it came across as a threat - it was just an illustration of how making a basic request impossible will drive away your user, customers, audience, etc.
It was also a fact, as I'm already in the process of evaluating a different Redhat-based distro that provides seamless upgrade (i.e. not a clean install) and a lightweight dektop environment suitable for a java developer.
it was just an illustration of how making a basic request impossible will drive away your user, customers, audience, etc.
Oh yeah, well known. In the past I've walked away from Redhat (before Fedora) and Fedora because they've pissed me off - and I'm also in the process of preparing to move again for my day-to-day (i.e. this) system.
No harm in trying something that may fit better.
I like fedora
fedora 4 to 11 were great for learning
after a few years i decided to get off the fedora roller coaster of NEW installs every 6 months
-- upgrades almost NEVER work well .
i now run OpenSUSE 13.1 and Scientific linux 6.5
fedora 19 and a few others on VM's
Fedora is well FEDORA !!!
except it for what it is
fedora IS fedora
it is not and NEVER!!!! will be RHEL or Debian stable
It could be that the mirror it's syncing to is missing packages that it's expecting. As others have said, 18 is EOL'd, so not everything might be in place.
I would try running this first:
Code:
yum-complete-transaction
That probably won't do anything, so you can use the package-cleanup command and try to remove any old packages.
Code:
package-cleanup --leaves --all
Be aware that --leaves isn't particularly intelligent and may recommend removing software that is needed.
One way that I've used to upgrade from F(n) to F(n+1) when both are out of date and something (usually a piece of Xorg or a kernel) doesn't quite work is to:
1. boot into a working distro
2. head over to koji and start grabbing early versions of the non-working package(s) for F(n+1)
3. if F(n+1) is bootable, I reboot at this point. Otherwise, I chroot into it.
4. manually install the upgrade packages
5. if necessary, reboot F(n+1)
Sometimes it works; sometimes it doesn't. YMMV
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.