To anyone trying to upgrade from Fedora 14 to Fedora 15, DON'T EVEN TRY!!! I've just tried and have had numerous problems, finally resulting in being unable to boot up any kernel version at all, using inittab mode 1,3, or 5. In view of this it appears I will have to reinstall Fedora 14.
cpp4ever
On 30/05/11 09:11, n2xssvv.g02gfr12930 wrote:
To anyone trying to upgrade from Fedora 14 to Fedora 15, DON'T EVEN TRY!!! I've just tried and have had numerous problems, finally resulting in being unable to boot up any kernel version at all, using inittab mode 1,3, or 5. In view of this it appears I will have to reinstall Fedora 14.
cpp4ever
No problems here.
On 05/30/2011 04:11 PM, n2xssvv.g02gfr12930 wrote:
To anyone trying to upgrade from Fedora 14 to Fedora 15, DON'T EVEN TRY!!! I've just tried and have had numerous problems, finally resulting in being unable to boot up any kernel version at all, using inittab mode 1,3, or 5. In view of this it appears I will have to reinstall Fedora 14.
You failed to mention what update/upgrade method you used....
On 30/05/11 09:28, Ed Greshko wrote:
On 05/30/2011 04:11 PM, n2xssvv.g02gfr12930 wrote:
To anyone trying to upgrade from Fedora 14 to Fedora 15, DON'T EVEN TRY!!! I've just tried and have had numerous problems, finally resulting in being unable to boot up any kernel version at all, using inittab mode 1,3, or 5. In view of this it appears I will have to reinstall Fedora 14.
You failed to mention what update/upgrade method you used....
the Subject: yum update
to recover try: 1: boot from dvd\bootcd.
rescue installed system when ready:
yum --releasever=15 distro-sync --skip-broken
On Mon, 30 May 2011 09:11:26 +0100, NG wrote:
To anyone trying to upgrade from Fedora 14 to Fedora 15, DON'T EVEN TRY!!! I've just tried and have had numerous problems, finally resulting in being unable to boot up any kernel version at all, using inittab mode 1,3, or 5. In view of this it appears I will have to reinstall Fedora 14.
What are you trying to achieve with such a general warning?
Distribution upgrades have never been entirely trouble-free, not even if doing it with the DVD image. Even if all old packages get replaced during the upgrade (and no package violated the upgrade-path), the new packages need to cope with all sorts of configuration/integration/customisation specialties at run-time.
Btw, a reinstall of Fedora 15 could be tried as well to test whether you would run into the same or similar issues. ;)
On 30/05/11 09:34, Frank Murphy wrote:
On 30/05/11 09:28, Ed Greshko wrote:
On 05/30/2011 04:11 PM, n2xssvv.g02gfr12930 wrote:
To anyone trying to upgrade from Fedora 14 to Fedora 15, DON'T EVEN TRY!!! I've just tried and have had numerous problems, finally resulting in being unable to boot up any kernel version at all, using inittab mode 1,3, or 5. In view of this it appears I will have to reinstall Fedora 14.
You failed to mention what update/upgrade method you used....
the Subject: yum update
to recover try: 1: boot from dvd\bootcd.
rescue installed system when ready:
yum --releasever=15 distro-sync --skip-broken
If only yum worked after booting from a rescue DVD.
I tried updating using yum in stages, (yumex actually using networkmanager). Unfortunately this eventually crippled networkmanager, and inittab 5 boot. The later I got round by creating a desktop file to and started gui from inittab 3, (to KDE).
I have updated using this method from Fedora 10 -> 14 successfully. As Fedora 8 -> 10 was KDE 3 -> 4 I did a fresh install.
Currently akmod builds fail on boot, and it eventually hangs. I've tried a variety of boot options to no avail.
On 30/05/11 09:11, n2xssvv.g02gfr12930 wrote:
To anyone trying to upgrade from Fedora 14 to Fedora 15, DON'T EVEN TRY!!! I've just tried and have had numerous problems, finally resulting in being unable to boot up any kernel version at all, using inittab mode 1,3, or 5. In view of this it appears I will have to reinstall Fedora 14.
cpp4ever
Any more suggestions would be appreciated,although having successfully upgraded Fedora 10 -> 14 incrementally before, I'm not hopeful.
In the meantime I'm looking to use a Fedora 14 rescue DVD to backup data to another partition, (not that there's much, I tend to do most of the important stuff on my laptop).
On 30/05/11 11:06, n2xssvv.g02gfr12930 wrote:
On 30/05/11 09:34, Frank Murphy wrote:
On 30/05/11 09:28, Ed Greshko wrote:
On 05/30/2011 04:11 PM, n2xssvv.g02gfr12930 wrote:
To anyone trying to upgrade from Fedora 14 to Fedora 15, DON'T EVEN TRY!!! I've just tried and have had numerous problems, finally resulting in being unable to boot up any kernel version at all, using inittab mode 1,3, or 5. In view of this it appears I will have to reinstall Fedora 14.
You failed to mention what update/upgrade method you used....
the Subject: yum update
to recover try: 1: boot from dvd\bootcd.
rescue installed system when ready:
yum --releasever=15 distro-sync --skip-broken
If only yum worked after booting from a rescue DVD.
I tried updating using yum in stages, (yumex actually using networkmanager). Unfortunately this eventually crippled networkmanager, and inittab 5 boot. The later I got round by creating a desktop file to and started gui from inittab 3, (to KDE).
I have updated using this method from Fedora 10 -> 14 successfully. As Fedora 8 -> 10 was KDE 3 -> 4 I did a fresh install.
Currently akmod builds fail on boot, and it eventually hangs. I've tried a variety of boot options to no avail.
It also appears the old LVM partition had become corrupted as when booting the rescue DVD I couldn't see my old home directory. Anyway I'm going to reinstall Fedora 14, update to latest releases, and then try again. Hopefully, with this being a standard Fedora 14 it'll succeed.
On 30/05/11 13:20, n2xssvv.g02gfr12930 wrote:
It also appears the old LVM partition had become corrupted as when booting the rescue DVD I couldn't see my old home directory. Anyway I'm going to reinstall Fedora 14, update to latest releases, and then try again. Hopefully, with this being a standard Fedora 14 it'll succeed.
Why not fresh install F15?
On 30/05/11 13:23, Frank Murphy wrote:
On 30/05/11 13:20, n2xssvv.g02gfr12930 wrote:
It also appears the old LVM partition had become corrupted as when booting the rescue DVD I couldn't see my old home directory. Anyway I'm going to reinstall Fedora 14, update to latest releases, and then try again. Hopefully, with this being a standard Fedora 14 it'll succeed.
Why not fresh install F15?
I only had a fedora 14 install DVD, and yes, I should have created a fedora 15 install DVD first. Basically I should know better!!!
Apart from which I'm looking to upgrade my laptop Fedora 14 -> 15. So determining if I can do this reliably first is the idea. Whatever, I need either my Desktop or Laptop working reliably. Currently for Fedora 15, updating appears to be a potentially disastrous operation based on my experience. There is also the possibility of other Fedora 15 quirks I'd like to sort out beforehand as well.
Regardless,your point was well made.
On Mon, 2011-05-30 at 09:11 +0100, n2xssvv.g02gfr12930 wrote:
To anyone trying to upgrade from Fedora 14 to Fedora 15, DON'T EVEN TRY!!! I've just tried and have had numerous problems, finally resulting in being unable to boot up any kernel version at all, using inittab mode 1,3, or 5. In view of this it appears I will have to reinstall Fedora 14.
Oh dear, I wish I known this before, then I wouldn't have updated to F15 from F14. I guess my working F15 system must be an illusion.
poc
On 30/05/11 15:00, Patrick O'Callaghan wrote:
On Mon, 2011-05-30 at 09:11 +0100, n2xssvv.g02gfr12930 wrote:
To anyone trying to upgrade from Fedora 14 to Fedora 15, DON'T EVEN TRY!!! I've just tried and have had numerous problems, finally resulting in being unable to boot up any kernel version at all, using inittab mode 1,3, or 5. In view of this it appears I will have to reinstall Fedora 14.
Oh dear, I wish I known this before, then I wouldn't have updated to F15 from F14. I guess my working F15 system must be an illusion.
poc
I've reinstalled Fedora 14 KDE minimal system, and I'm now trying to update to 15 from there. Hopefully, as there are no RPMFusion packages, or other none standard packages it should all be OK. Time will tell.
:-)
On 05/30/2011 06:06 AM, n2xssvv.g02gfr12930 wrote:
If only yum worked after booting from a rescue DVD.
I tried updating using yum in stages, (yumex actually using networkmanager). Unfortunately this eventually crippled networkmanager, and inittab 5 boot. The later I got round by creating a desktop file to and started gui from inittab 3, (to KDE).
I have updated using this method from Fedora 10 -> 14 successfully. As Fedora 8 -> 10 was KDE 3 -> 4 I did a fresh install.
Long experience by many is being shared with you ... updating - especially through multiple versions can lead to quirks ... a fresh install once in a while is a very healthy thing to do.
It is also likely to be difficult for others to help - since your system has aged differently (from F10 .. via upgrades) and hardware is different too .. so others may just say 'worked for me'.
Seriously, the best advice has been given - do a fresh install - and go from there - since your /home is a separate (backed up partition) right (?) - just restore it after the update ...
Also you may find it useful to run yum list installed > my-stuff as well as chkconfig --list > my-svcs before doing the install as a reference.
I only do fresh installs now (since about FC6) and it has certainly reduced the issues for me ... if you do insist and upgrade my advice would be alternate upgrades with fresh installs (i.e. F16 upgrade, F17 fresh install etc).
Good luck.
On 05/30/2011 01:41 PM, n2xssvv.g02gfr12930 wrote:
To anyone trying to upgrade from Fedora 14 to Fedora 15, DON'T EVEN TRY!!! I've just tried and have had numerous problems, finally resulting in being unable to boot up any kernel version at all, using inittab mode 1,3, or 5. In view of this it appears I will have to reinstall Fedora 14.
Worked fine here
Rahul
On Mon, 2011-05-30 at 09:34 +0100, Frank Murphy wrote:
the Subject: yum update
to recover try: 1: boot from dvd\bootcd.
rescue installed system when ready:
yum --releasever=15 distro-sync --skip-broken
Frank,
Will this work on an old 32-bit Thinkpad that's maxed out with 512MB of RAM? Installing from DVD fails.
--Doc Savage Fairview Heights, IL
On 30/05/11 17:14, Robert G. (Doc) Savage wrote:
On Mon, 2011-05-30 at 09:34 +0100, Frank Murphy wrote:
the Subject: yum update
to recover try: 1: boot from dvd\bootcd.
rescue installed system when ready:
yum --releasever=15 distro-sync --skip-broken
Frank,
Will this work on an old 32-bit Thinkpad that's maxed out with 512MB of RAM? Installing from DVD fails.
--Doc Savage Fairview Heights, IL
I don't think so, the min spec is a little over 700mb ram, 1gb recommended. for a GUI install.
On 05/30/2011 04:00 PM, Patrick O'Callaghan wrote:
On Mon, 2011-05-30 at 09:11 +0100, n2xssvv.g02gfr12930 wrote:
To anyone trying to upgrade from Fedora 14 to Fedora 15, DON'T EVEN TRY!!! I've just tried and have had numerous problems, finally resulting in being unable to boot up any kernel version at all, using inittab mode 1,3, or 5. In view of this it appears I will have to reinstall Fedora 14.
Oh dear, I wish I known this before, then I wouldn't have updated to F15 from F14. I guess my working F15 system must be an illusion.
Well, YMMV or you might not have looked into details yet ;)
None of the 2 test systems I have given Fedora 15 a try on so far, is working in a state which deserves to be called "smooth" and "calm".
Ralf
On 30/05/11 17:27, Ralf Corsepius wrote: <snip>. In view of this it appears I will have to reinstall Fedora 14.
Oh dear, I wish I known this before, then I wouldn't have updated to F15 from F14. I guess my working F15 system must be an illusion.
Well, YMMV or you might not have looked into details yet ;)
None of the 2 test systems I have given Fedora 15 a try on so far, is working in a state which deserves to be called "smooth" and "calm".
Ralf
I'm paraphrasing, but it was the sweeping statement, Patrick had issue with.
On 30/05/11 17:14, Robert G. (Doc) Savage wrote: <snip>
Frank,
Will this work on an old 32-bit Thinkpad that's maxed out with 512MB of RAM? Installing from DVD fails.
--Doc Savage Fairview Heights, IL
What Desktop are you using? Gnome\KDE? It might work for one of the lighter Desktops Xfce\Lxde. Check the specs on the resepective pages. Havn't got them to hand.
On Mon, 2011-05-30 at 22:13 +0530, Rahul Sundaram wrote:
On 05/30/2011 09:44 PM, Robert G. (Doc) Savage wrote:
Frank,
Will this work on an old 32-bit Thinkpad that's maxed out with 512MB of RAM? Installing from DVD fails.
You can try upgrading piecemeal. Some major set of packages, python, then gtk and so on
Rahul,
That's what I was thinking. The roadblock I run into with a conventional DVD install/upgrade is:
[ 7.076671] Trying to unpack rootfs image as initramfs...
I don't think a yum upgrade tries to do that, but I'm not certain.
--Doc Savage Fairview Heights, IL
On 05/30/2011 08:28 AM, Genes MailLists wrote:
I only do fresh installs now (since about FC6) and it has certainly reduced the issues for me ... if you do insist and upgrade my advice would be alternate upgrades with fresh installs (i.e. F16 upgrade, F17 fresh install etc).
When it was time for me to move from F9 to F11, I installed and used preupgrade. (There were so many problems with F10 that I just skipped it.) Worked just fine, and I've used it ever since. Right now, I'm waiting for F15 to settle down before using it again. YMMD of course, but I've had good experience with upgrading instead of fresh installs.
On 30/05/11 09:11, n2xssvv.g02gfr12930 wrote:
To anyone trying to upgrade from Fedora 14 to Fedora 15, DON'T EVEN TRY!!! I've just tried and have had numerous problems, finally resulting in being unable to boot up any kernel version at all, using inittab mode 1,3, or 5. In view of this it appears I will have to reinstall Fedora 14.
cpp4ever
OK, folks I have just reinstalled Fedora 14, (KDE minimal and working), updated, (working) , then upgraded to Fedora 15 and it still fails completely. Based on this experience I'm loathe to recommend Fedora 15, and I suspect that even a Fedora 15 DVD install will give the same result. Even worse my Fedora 14 rescue DVD has been of no use either.
On Mon, 30 May 2011 18:44:01 +0100 "n2xssvv.g02gfr12930" n2xssvv.g02gfr12930@ntlworld.com wrote:
On 30/05/11 09:11, n2xssvv.g02gfr12930 wrote:
To anyone trying to upgrade from Fedora 14 to Fedora 15, DON'T EVEN TRY!!! I've just tried and have had numerous problems, finally resulting in being unable to boot up any kernel version at all, using inittab mode 1,3, or 5. In view of this it appears I will have to reinstall Fedora 14.
cpp4ever
OK, folks I have just reinstalled Fedora 14, (KDE minimal and working), updated, (working) , then upgraded to Fedora 15 and it still fails completely. Based on this experience I'm loathe to recommend Fedora 15, and I suspect that even a Fedora 15 DVD install will give the same result. Even worse my Fedora 14 rescue DVD has been of no use either.
Can you please expand on 'fails completely' ?
I just did 2 updates yesterday with no problems at all.
kevin
On 30/05/11 18:44, n2xssvv.g02gfr12930 wrote:
OK, folks I have just reinstalled Fedora 14, (KDE minimal and working), updated, (working) , then upgraded to Fedora 15 and it still fails completely.
What happens?
Based on this experience I'm loathe to recommend Fedora 15,
and I suspect that even a Fedora 15 DVD install will give the same result. Even worse my Fedora 14 rescue DVD has been of no use either.
What does F14 resuce give you?
On 30/05/11 18:47, Kevin Fenzi wrote:
On Mon, 30 May 2011 18:44:01 +0100 "n2xssvv.g02gfr12930" n2xssvv.g02gfr12930@ntlworld.com wrote:
On 30/05/11 09:11, n2xssvv.g02gfr12930 wrote:
To anyone trying to upgrade from Fedora 14 to Fedora 15, DON'T EVEN TRY!!! I've just tried and have had numerous problems, finally resulting in being unable to boot up any kernel version at all, using inittab mode 1,3, or 5. In view of this it appears I will have to reinstall Fedora 14.
cpp4ever
OK, folks I have just reinstalled Fedora 14, (KDE minimal and working), updated, (working) , then upgraded to Fedora 15 and it still fails completely. Based on this experience I'm loathe to recommend Fedora 15, and I suspect that even a Fedora 15 DVD install will give the same result. Even worse my Fedora 14 rescue DVD has been of no use either.
Can you please expand on 'fails completely' ?
I just did 2 updates yesterday with no problems at all.
kevin
Failed completely means I cannot even boot to a console, (inittab 3). Currently I'm trying to boot the last Fedora 14 kernel and it's having to do some SELinux filesystem update. So the next thing to try is to install from a Fedora 15 install DVD. Just for the record the yum Fedora 14 -> 15 upgrade for the minimal install ran faultlessly, no conflicts or package removals.
The only other thing that maybe affecting things is there are other partitions and drives. But that should not be a problem, although I may try again with just the one drive.
Having upgraded using yum Fedora 10 -> 14 incrementally without this problem, I'm somewhat concerned. Bottom line, trying to upgrade to Fedora 15 via yum is inherently risky and I cannot recommend people try it, based on my experience. So for now my laptop is going to stay with Fedora 14 install until I can gain some confidence installing Fedora 15 on my Desktop.
cpp4ever
On Mon, 30 May 2011 19:20:55 +0100 "n2xssvv.g02gfr12930" n2xssvv.g02gfr12930@ntlworld.com wrote:
Failed completely means I cannot even boot to a console, (inittab 3).
ok. What are the messages on the screen when this fails? Screenshot?
Currently I'm trying to boot the last Fedora 14 kernel and it's having to do some SELinux filesystem update. So the next thing to try is to install from a Fedora 15 install DVD. Just for the record the yum Fedora 14 -> 15 upgrade for the minimal install ran faultlessly, no conflicts or package removals.
The only other thing that maybe affecting things is there are other partitions and drives. But that should not be a problem, although I may try again with just the one drive.
Having upgraded using yum Fedora 10 -> 14 incrementally without this problem, I'm somewhat concerned. Bottom line, trying to upgrade to Fedora 15 via yum is inherently risky and I cannot recommend people try it, based on my experience. So for now my laptop is going to stay with Fedora 14 install until I can gain some confidence installing Fedora 15 on my Desktop.
Sure, your choice. There's clearly some bug or issue here and we want to get to the bottom of it, but just as clearly it doesn't affect everyone.
kevin
On 05/30/2011 10:44 AM, n2xssvv.g02gfr12930 wrote:
Based on this experience I'm loathe to recommend Fedora 15, and I suspect that even a Fedora 15 DVD install will give the same result.
Going from a specific example to a general rule is called "inductive reasoning," and it's generally a Good Thing. Coming to the conclusion that Fedora 15 Just Doesn't Work from a sample of one computer, especially as there are tens of thousands (at least) of counter examples, simply isn't justified. I'm sure that there are a large number of people on this list ready and willing to help you (and more at fedoraforum.org) but you're going to have to cut back on the hysteria and give us some details. HTH, HAND.
On 30/05/11 18:50, Frank Murphy wrote:
On 30/05/11 18:44, n2xssvv.g02gfr12930 wrote:
OK, folks I have just reinstalled Fedora 14, (KDE minimal and working), updated, (working) , then upgraded to Fedora 15 and it still fails completely.
What happens?
Based on this experience I'm loathe to recommend Fedora 15,
and I suspect that even a Fedora 15 DVD install will give the same result. Even worse my Fedora 14 rescue DVD has been of no use either.
What does F14 resuce give you?
The yum upgrade from the minimal Fedora 14 KDE ran smoothly, (no conflicts or removals). Unfortunately on rebooting I cannot boot at all, (inittab 3 or 5), and when I just tried the Fedora 14 rescue DVD, that failed as well!! Currently I can only suspect that the SELinux permissions update are not being completed properly on reboot. So perhaps a Fedora 15 DVD install and update will work.
As I've said elsewhere I will be avoiding Fedora 15 until I can find a reliable method of installing/upgrading that works. Hence my laptop, (in use now), will continue to run Fedora 14. Also I have successfully upgraded via yum Fedora 10 -> 11 -> 12 -> 13 -> 14, (and never had this big a problem).
Based on my experience, even with a minimal Fedora 14 installation, I cannot recommend trying to upgrade Fedora 14 -> 15 via yum.
On 30/05/11 19:26, Kevin Fenzi wrote:
On Mon, 30 May 2011 19:20:55 +0100 "n2xssvv.g02gfr12930"n2xssvv.g02gfr12930@ntlworld.com wrote:
<snip>
Sure, your choice. There's clearly some bug or issue here and we want to get to the bottom of it, but just as clearly it doesn't affect everyone.
kevin
I would also recommend dowloading an F15 netinstall.iso see if you can boot from that if yes, then "rescue installed system"
if you let ue, we can guide you through this.
On 30/05/11 19:35, n2xssvv.g02gfr12930 wrote: <snip>
Based on my experience, even with a minimal Fedora 14 installation, I cannot recommend trying to upgrade Fedora 14 -> 15 via yum.
what size boot partition do you have on the laptop?
On 30/05/11 19:31, Joe Zeff wrote:
On 05/30/2011 10:44 AM, n2xssvv.g02gfr12930 wrote:
Based on this experience I'm loathe to recommend Fedora 15, and I suspect that even a Fedora 15 DVD install will give the same result.
Going from a specific example to a general rule is called "inductive reasoning," and it's generally a Good Thing. Coming to the conclusion that Fedora 15 Just Doesn't Work from a sample of one computer, especially as there are tens of thousands (at least) of counter examples, simply isn't justified. I'm sure that there are a large number of people on this list ready and willing to help you (and more at fedoraforum.org) but you're going to have to cut back on the hysteria and give us some details. HTH, HAND.
And I wish anybody luck trying to upgrade. But having successfully upgraded Fedora 10 -> 11 -> 12 -> 13 -> 14 without this big a problem I think others should be warned. In fact since I started using Fedora core 2, most problems I've been able handle, (except at least one I created due to stupidity). That's over 8 years, and congratulations to the Fedora teams that have made that possible, but this time something appears to have failed in my case. If you consider my response as hysteria, so be it.
cpp4ever
On 05/30/2011 04:11 PM, n2xssvv.g02gfr12930 wrote:
To anyone trying to upgrade from Fedora 14 to Fedora 15, DON'T EVEN TRY!!! I've just tried and have had numerous problems, finally resulting in being unable to boot up any kernel version at all, using inittab mode 1,3, or 5. In view of this it appears I will have to reinstall Fedora 14.
Just took a F14 system to F15 using "preupgrade". ZERO problems.
Maybe you should think twice before spreading FUD?
On 05/30/2011 01:20 PM, n2xssvv.g02gfr12930 wrote:
Failed completely means I cannot even boot to a console, (inittab 3). Currently I'm trying to boot the last Fedora 14 kernel and it's having to do some SELinux filesystem update. So the next thing to try is to install from a Fedora 15 install DVD. Just for the record the yum Fedora 14 -> 15 upgrade for the minimal install ran faultlessly, no conflicts or package removals.
The only other thing that maybe affecting things is there are other partitions and drives. But that should not be a problem, although I may try again with just the one drive.
Having upgraded using yum Fedora 10 -> 14 incrementally without this problem, I'm somewhat concerned. Bottom line, trying to upgrade to Fedora 15 via yum is inherently risky and I cannot recommend people try it, based on my experience. So for now my laptop is going to stay with Fedora 14 install until I can gain some confidence installing Fedora 15 on my Desktop.
cpp4ever
Having more then one drive can be a problem, depending on if the drive mapping is the same when you boot from a CD/DVD as when you boot from a hard drive. It can also be a problem with a yum upgrade if the Grub drive map does not match your system.
I have seen the first stage boot loader get installed to the wrong drive, and I have seen the first stage look for the next stage on the wrong drive.
It would help to know if you get the Grub menu screen and then it gets stuck, or if you can not even get to the Grub menu screen.
Mikkel
On 05/31/2011 12:20 AM, Ed Greshko wrote:
On 05/30/2011 04:11 PM, n2xssvv.g02gfr12930 wrote:
To anyone trying to upgrade from Fedora 14 to Fedora 15, DON'T EVEN TRY!!! I've just tried and have had numerous problems, finally resulting in being unable to boot up any kernel version at all, using inittab mode 1,3, or 5. In view of this it appears I will have to reinstall Fedora 14.
Just took a F14 system to F15 using "preupgrade". ZERO problems.
Maybe you should think twice before spreading FUD?
Come on. Let's assume good will. His warning might not be helpful with more details but he is certainly just trying to warn users.
Rahul
On 05/31/2011 02:53 AM, Rahul Sundaram wrote:
Come on. Let's assume good will. His warning might not be helpful with more details but he is certainly just trying to warn users.
Over reaction to a personal experience is *never* a good thing not matter how well intended.
FUD is FUD.
On 30/05/11 19:37, Frank Murphy wrote:
On 30/05/11 19:35, n2xssvv.g02gfr12930 wrote:
<snip>
Based on my experience, even with a minimal Fedora 14 installation, I cannot recommend trying to upgrade Fedora 14 -> 15 via yum.
what size boot partition do you have on the laptop?
The same 200Mb,(1Tb drive on desktop, 500Gb on laptop ), as I had for Fedora 14, which worked fine. Please note my current theory is that SELinux permissions are changed, and the reboot to the Fedora 15 kernel does not properly update them.
Please see my other posts, I have to congratulate the Fedora team for 8+ years of mostly relatively problem free Linux!
HTH
cpp4ever
On 05/31/2011 12:28 AM, Ed Greshko wrote:
On 05/31/2011 02:53 AM, Rahul Sundaram wrote:
Come on. Let's assume good will. His warning might not be helpful with more details but he is certainly just trying to warn users.
Over reaction to a personal experience is *never* a good thing not matter how well intended.
FUD is FUD.
I think you are doing the same thing that you are accusing the other person of doing IMO. You can just point out what is wrong.
Rahul
On 05/30/2011 08:35 PM, n2xssvv.g02gfr12930 wrote:
As I've said elsewhere I will[snip]
Based on my experience,[snip]
Your continued repeating of your anti-F15 "recommendations" and the lack of actual technical information and/or screenshots other than it did not work makes you look like a troll. A quick google for your email address shows you had similar "recommendations" when your upgrade to Fedora 12 failed. Seems you are the only person in the universe that just can not make those upgrades work again and again and then recommends that others not upgrade because your upgrade failed for unknown reasons.
How about you stop with your imo baseless "recommendations" and start providing detailed technical information and screenshots to those who asked for them so they can help you find the issue and possibly fix it?
Or are you just a troll spreading FUD?
Patrick
Ed Greshko wrote:
On 05/30/2011 04:11 PM, n2xssvv.g02gfr12930 wrote:
To anyone trying to upgrade from Fedora 14 to Fedora 15, DON'T EVEN TRY!!! I've just tried and have had numerous problems, finally resulting in being unable to boot up any kernel version at all, using inittab mode 1,3, or 5. In view of this it appears I will have to reinstall Fedora 14.
Just took a F14 system to F15 using "preupgrade". ZERO problems.
Maybe you should think twice before spreading FUD?
No, upgrading F15 is a pain. Beware, expect danger!
System 1: I tried to upgrade one system using the install DVD. Upon rebooting, I got a blank screen with a flashing cursor. Not even grub! A fresh install (overwriting everything) fixed that, but still...
System 2: I tried it on a second system, using both the Live CD and the install DVD. I got further, but gdm crashed when trying to log users in (https://bugzilla.redhat.com/show_bug.cgi?id=707985, https://bugzilla.gnome.org/show_bug.cgi?id=651180). I found a workaround for that, but the system was super-unstable and prone to long freezes. Swapping in different video cards and ethernet cards didn't fix it, so I had to revert to F14 on that system.
System 3: I used preupgrade-cli with vnc, but it wouldn't boot into anaconda - another black screen with a flashing cursor. Going to the second grub choice landed me safely back in F14.
I'm kind of sad, because I actually really like gnome-shell now! It has quirks, but they'll get ironed out soon enough...
This will be a slow roll-out here, based on results so far :-(
- Mike
On 30/05/11 19:50, Ed Greshko wrote:
On 05/30/2011 04:11 PM, n2xssvv.g02gfr12930 wrote:
To anyone trying to upgrade from Fedora 14 to Fedora 15, DON'T EVEN TRY!!! I've just tried and have had numerous problems, finally resulting in being unable to boot up any kernel version at all, using inittab mode 1,3, or 5. In view of this it appears I will have to reinstall Fedora 14.
Just took a F14 system to F15 using "preupgrade". ZERO problems.
Maybe you should think twice before spreading FUD?
I wish I could say the same, it's failed twice for me now, even from a minimal Fedora 14 KDE reinstall/update. Might be FUD in your world,but I hope for your sake you never come across a similar problem. Rest assured if our places are ever reversed you will have my sympathy,and not FUD. Oh, by the way I am jealous!
On 30/05/11 19:35, n2xssvv.g02gfr12930 wrote: <snip>
Based on my experience, even with a minimal Fedora 14 installation, I cannot recommend trying to upgrade Fedora 14 -> 15 via yum.
Know that there will be people here to give a hand when your ready.
On 30/05/11 20:08, Patrick Lists wrote:
On 05/30/2011 08:35 PM, n2xssvv.g02gfr12930 wrote:
As I've said elsewhere I will[snip]
Based on my experience,[snip]
Your continued repeating of your anti-F15 "recommendations" and the lack of actual technical information and/or screenshots other than it did not work makes you look like a troll. A quick google for your email address shows you had similar "recommendations" when your upgrade to Fedora 12 failed. Seems you are the only person in the universe that just can not make those upgrades work again and again and then recommends that others not upgrade because your upgrade failed for unknown reasons.
How about you stop with your imo baseless "recommendations" and start providing detailed technical information and screenshots to those who asked for them so they can help you find the issue and possibly fix it?
Or are you just a troll spreading FUD?
Patrick
How to collect technical information when Fedora 15 fails to boot? I have since tried again with a similar result, (see other posts). If the positions are ever reversed I will be sympathetic to Patrick and not a FUD spreading Troll.
On 05/30/2011 11:49 AM, n2xssvv.g02gfr12930 wrote:
If you consider my response as hysteria, so be it.
Coming out of nowhere and saying that because the upgrade didn't work for you on one machine it wouldn't work for anybody was, at the least, a tad over-the-top, don't you think?
On 30/05/11 19:52, Mikkel L. Ellertson wrote:
On 05/30/2011 01:20 PM, n2xssvv.g02gfr12930 wrote:
Failed completely means I cannot even boot to a console, (inittab 3). Currently I'm trying to boot the last Fedora 14 kernel and it's having to do some SELinux filesystem update. So the next thing to try is to install from a Fedora 15 install DVD. Just for the record the yum Fedora 14 -> 15 upgrade for the minimal install ran faultlessly, no conflicts or package removals.
The only other thing that maybe affecting things is there are other partitions and drives. But that should not be a problem, although I may try again with just the one drive.
Having upgraded using yum Fedora 10 -> 14 incrementally without this problem, I'm somewhat concerned. Bottom line, trying to upgrade to Fedora 15 via yum is inherently risky and I cannot recommend people try it, based on my experience. So for now my laptop is going to stay with Fedora 14 install until I can gain some confidence installing Fedora 15 on my Desktop.
cpp4ever
Having more then one drive can be a problem, depending on if the drive mapping is the same when you boot from a CD/DVD as when you boot from a hard drive. It can also be a problem with a yum upgrade if the Grub drive map does not match your system.
I have seen the first stage boot loader get installed to the wrong drive, and I have seen the first stage look for the next stage on the wrong drive.
It would help to know if you get the Grub menu screen and then it gets stuck, or if you can not even get to the Grub menu screen.
Mikkel
Grub works fine thanks Mikkel. Apparently I'm gaining the reputation of being a FUD spreading Troll, so your response is appreciated. Unfortunately, as I've tried to make clear in other posts, recovering much technical information is not as simple as I'd like, and I've tried.
cpp4ever
On 30/05/11 20:16, Joe Zeff wrote:
On 05/30/2011 11:49 AM, n2xssvv.g02gfr12930 wrote:
If you consider my response as hysteria, so be it.
Coming out of nowhere and saying that because the upgrade didn't work for you on one machine it wouldn't work for anybody was, at the least, a tad over-the-top, don't you think?
Easy for you to say when you don't have the problem, and I wish you never have a similar problem. Then I'd be interested to see your response. In the meant time please see my other posts.
On 05/30/2011 12:28 PM, n2xssvv.g02gfr12930 wrote:
Easy for you to say when you don't have the problem, and I wish you never have a similar problem. Then I'd be interested to see your response. In the meant time please see my other posts.
I've had problems with upgrades, installations and updates a few times. Each time I did, I started out with the presumption that the trouble was at my end, and not a system-wide failure of the distro in question. Not once was I forced to change that assumption. And, because I didn't start out by channeling Chicken Little, I was able to get all the help I needed in a prompt and timely manor. HTH, HAND.
On Monday, May 30, 2011 04:11:26 n2xssvv.g02gfr12930 wrote:
To anyone trying to upgrade from Fedora 14 to Fedora 15, DON'T EVEN TRY!!! I've just tried and have had numerous problems, finally resulting in being unable to boot up any kernel version at all, using inittab mode 1,3, or 5. In view of this it appears I will have to reinstall Fedora 14.
While, in one instance, I had problems, I wouldn't recommend not even trying. F15 is a stable good release for me on two machines.
Here's my experience on two systems:
At work, I did the preupgrade thing and it was a big yawn. All went well and everything Just Works(tm).
At home, I used the DVD to upgrade. I had several problems, but I was able to recover from all of them:
1. I was not asked to include the updates repository during the update process. Now I will have to do an update after first boot.
2. This is apparently a general problem not really related to the specific upgrade. I noticed that the upgrade process was slow. The disk just churned forever. After booting for the first time, I ran yum erase on my debuginfos so that the subsequent yum update would not pull those in. This erase command took way too long.
I think the rpm database gets into a state that needs attention. This fixed it:
sudo rm -f /var/lib/rpm/__db.001 /var/lib/rpm/__db.002 \ /var/lib/rpm/__db.003 /var/lib/rpm/__db.004 sudo rpm --rebuilddb
After that, yum operations sped up an order of magnitude.
3. The first boot ended at multiuser.target instead of graphical.target. (That's init level 3 instead of level 5 in oldspeak.) I have never touched the inittab on either machine. They were both set to boot into the graphical login.
When I entered the command
sudo systemctl isolate graphical.target
kdm came up and allowed a normal desktop login.
Hmmm. I compared my machine at work to the home machine and it had the correct graphical.target file linked in /etc/systemd/system . So I had to do this to correct the problem:
sudo rm /etc/systemd/system/default.target sudo ln -s /lib/systemd/system/runlevel5.target \ /etc/systemd/system/default.target
I don't know why this happened with the DVD upgrade and not with the preupgrade upgrade.
4. I then did a yum update and waited a few hours while over 500 packages were downloaded and updated/installed. This was almost 1GB of downloads. Most packages did not have delta rpms.
5. I run KDE and after logging in and starting Kmail, it refused to start, complaining about akonadi not being available:
Test 5: ERROR ... InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. <repeated many times>
Test 10: ERROR ... Akonadi control process not registered at D-Bus.
Test 15: ERROR ... No resource agents found.
(Wow, this is a fragile piece in kdepim.)
The fix for this ended up being:
sudo yum --enablerepo=kde-testing update
Only Kmail users will experience this one and once the fixed packages are in updates, it won't happen at all.
6. There was no system log after the upgrade. That one was fixed with this:
sudo systemctl enable rsyslog.service
Now the home system is operating as expected and all looks good. Based on my reading over the past several weeks, I think others have already encountered most of this stuff.
Summary -------
Serious system problems were 3 and 6 above. These were surprises. Both were trivial to recover from. The rest was irritating only.
Thank you for another excellent Fedora release.
On 05/30/2011 12:50 PM, Garry T. Williams wrote:
- The first boot ended at multiuser.target instead of
graphical.target. (That's init level 3 instead of level 5 in oldspeak.) I have never touched the inittab on either machine. They were both set to boot into the graphical login.
I presume the names were changed to make it easier to know what they mean? If so, it's a good idea, especially if there's a comment somewhere that tells you how they correspond so that all of us oldpharts can adjust.
On 05/31/2011 01:34 AM, Joe Zeff wrote:
I presume the names were changed to make it easier to know what they mean? If so, it's a good idea, especially if there's a comment somewhere that tells you how they correspond so that all of us oldpharts can adjust.
multi-user.target and graphical.target are symlinked to runlevel3.target and runlevel5.target For instance,
ll /etc/systemd/system/runlevel5.target
lrwxrwxrwx. 1 root root 36 Aug 24 2010 /etc/systemd/system/runlevel5.target -> /lib/systemd/system/graphical.target
Rahul
On 30/05/11 21:04, Joe Zeff wrote:
I presume the names were changed to make it easier to know what they mean? If so, it's a good idea, especially if there's a comment somewhere that tells you how they correspond so that all of us oldpharts can adjust.
http://fedoraproject.org/wiki/SysVinit_to_Systemd_Cheatsheet
On Mon, 30 May 2011 18:44:01 +0100, NG wrote:
OK, folks I have just reinstalled Fedora 14, (KDE minimal and working), updated, (working) , then upgraded to Fedora 15 and it still fails completely.
Updating the F14 prior to upgrading it to F15 may be a mistake already, given that F14 updates may be newer than F15 release. Do you enable the "updates" network repo during F15 upgrade?
On Mon, 30 May 2011 19:20:55 +0100, NG wrote:
Failed completely means I cannot even boot to a console, (inittab 3).
F15 doesn't use inittab anymore, so what do you mean? In case you refer to the kernel boot args, you would need to read up on systemd run-level args.
On Mon, 30 May 2011 20:16:09 +0100, NG wrote:
How to collect technical information when Fedora 15 fails to boot?
To check whether your theory of SELinux problems could be true, try booting with the enforcing=0 kernel arg.
Descriptions such as "cannot boot at all" are useless, because certainly you could mention a few details about what parts of the boot process work, what is displayed on screen (possibly by leaving the graphical booter with ESC), and where it stops unexpectedly.
On Mon, May 30, 2011 at 11:26 AM, Kevin Fenzi kevin@scrye.com wrote:
On Mon, 30 May 2011 19:20:55 +0100 "n2xssvv.g02gfr12930" n2xssvv.g02gfr12930@ntlworld.com wrote:
Failed completely means I cannot even boot to a console, (inittab 3).
ok. What are the messages on the screen when this fails? Screenshot?
Maybe the OP is missing the fact that F15 uses systemd and not the old SysVinit infrastructure?
This should help:
https://fedoraproject.org/wiki/Systemd#Boot_Kernel_Command_Line
On 30/05/11 20:46, Joe Zeff wrote:
On 05/30/2011 12:28 PM, n2xssvv.g02gfr12930 wrote:
Easy for you to say when you don't have the problem, and I wish you never have a similar problem. Then I'd be interested to see your response. In the meant time please see my other posts.
I've had problems with upgrades, installations and updates a few times. Each time I did, I started out with the presumption that the trouble was at my end, and not a system-wide failure of the distro in question. Not once was I forced to change that assumption. And, because I didn't start out by channeling Chicken Little, I was able to get all the help I needed in a prompt and timely manor. HTH, HAND.
Well, I could say the same, but this problem is an order of magnitude more complicated than anything I have experienced using Fedora in 8+ years, is that chicken little?. Although some of the other responses have made clear that some important underlying changes have been made Fedora 14 -> 15, and any one of these could be the cause of my problem. Therefore I cautiously recommend a fresh install of Fedora 15, rather than trying a yum update, (which was my original warning), and this makes updating my laptop a much more time consuming process. Your name calling, whether it be Chicken Little, Hysteria, or whatever, certainly doesn't help, or inspire confidence. Especially as you may well find yourself with a similar order of magnitude type problem, and face similar responses.
cpp4ever
On 05/30/2011 02:30 PM, n2xssvv.g02gfr12930 wrote:
Well, I could say the same, but this problem is an order of magnitude more complicated than anything I have experienced using Fedora in 8+ years, is that chicken little?.
Yes, it is. Starting out with the assumption that F15 is at fault -- not F15 Alpha, not F15 Beta or a Release Candidate, but the fully-tested "ready for prime time" version of F15 -- instead of something at your end is completely unrealistic. If there were something so badly wrong with F15 that it wasn't ready to be installed on anybody's computer without major risks, it would never have been released. And, considering how many early adopters there are, this mailing list and the support forum at fedoraforum.org would be jammed with reports of this happening. They aren't. I'm not saying that this was caused by anything you did wrong, because at present there's no evidence to suggest that; in fact, there's an almost complete lack of evidence as to just what happened, even though you've not only been asked for it, you've been told how to collect it. Now, the only question is, do you want help or do you just want to complain?
On 05/31/2011 03:09 AM, n2xssvv.g02gfr12930 wrote:
I wish I could say the same, it's failed twice for me now, even from a minimal Fedora 14 KDE reinstall/update. Might be FUD in your world,but I hope for your sake you never come across a similar problem. Rest assured if our places are ever reversed you will have my sympathy,and not FUD. Oh, by the way I am jealous!
Make no mistake, you have my sympathies. As you may find out, if you read another response here, I recently ended up with a system that wouldn't boot to level 5 after doing what should have been a routine "yum install".
While it is only my opinion, posting as you did in CAPS telling everyone not to attempt an upgrade is to be avoided.
On 05/31/2011 03:03 AM, Rahul Sundaram wrote:
I think you are doing the same thing that you are accusing the other person of doing IMO. You can just point out what is wrong.
The OP specifically told people "DON'T EVEN TRY!!!" to upgrade from F14 to F15. No details, no suggestion as to what could have gone wrong in one isolated instance. A flat out statement in capital shouting out from the highest hill proclamation that disaster is looming for any fool attempting to such folly. That, IMO, is spreading FUD.
FUD is not normally spread with evil intentions. FUD is often spread by people who seemingly know what they are doing.
There is currently a food additive crisis going on in Taiwan. Some unscrupulous manufacturers have been selling "clouding agents" containing toxic plasticizers DEHP and DINP to processed food companies. While there certainly is a problem, some media outlets have taken to reporting on this with breathless abandon. There are a certain number of people who take this and then overreact. I personally know one person who now refuses to buy any processed food from any source. Also, the mother of one of my friends had gone even further and throw out all processed food in their home. They succumbed to bad reporting...an extreme case of FUD.
The other day I was considering installing the nVidia drivers from rpmfusion. I had a question and you helpfully supplied a method where I would be able to learn the answer for myself. I thanked you for that.
I then when ahead with the install. Apparently I hit an end case (or whatever you want to call it) situation with yum the rpmfusion repo. I ended up with a system that would not boot into level 5.
I could have hit the panic button. I could have raced off to this list and warned everyone of the consequences of attempting what I just did. I could have told people "DON'T EVEN TRY TO INSTALL NVIDIA FROM RPMFUSION".
I figured out what went wrong, asked a few questions, and learned about the limitations (flaws?) in the yum update/install process. And, yes, it is true that I now wouldn't trust the process around my nuclear reactor. :-) :-)
People, who later seemingly know what they are doing, should know better and be responsible for their reporting. In this case, the OP later seems to know what he is doing, making the first FUD based posting even more believable by individuals susceptible to FUD.
FUD is FUD no matter how well intended.
On 30 May 2011 22:30, n2xssvv.g02gfr12930 n2xssvv.g02gfr12930@ntlworld.com wrote:
On 30/05/11 20:46, Joe Zeff wrote:
On 05/30/2011 12:28 PM, n2xssvv.g02gfr12930 wrote:
Easy for you to say when you don't have the problem, and I wish you never have a similar problem. Then I'd be interested to see your response. In the meant time please see my other posts.
I've had problems with upgrades, installations and updates a few times. Each time I did, I started out with the presumption that the trouble was at my end, and not a system-wide failure of the distro in question. Not once was I forced to change that assumption. And, because I didn't start out by channeling Chicken Little, I was able to get all the help I needed in a prompt and timely manor. HTH, HAND.
Well, I could say the same, but this problem is an order of magnitude more complicated than anything I have experienced using Fedora in 8+ years, is that chicken little?. Although some of the other responses have made clear that some important underlying changes have been made Fedora 14 -> 15, and any one of these could be the cause of my problem. Therefore I cautiously recommend a fresh install of Fedora 15, rather than trying a yum update, (which was my original warning), and this makes updating my laptop a much more time consuming process. Your name calling, whether it be Chicken Little, Hysteria, or whatever, certainly doesn't help, or inspire confidence. Especially as you may well find yourself with a similar order of magnitude type problem, and face similar responses.
I still don't see you outlining your problem, other than it doesn't boot. What doesn't boot, what have you treid to remedy this, what troubleshooting steps have you followed, what appears on the screen. These simple bits of information might help us to help you. What you've said so far lacks technical details and contains a surfeit of hyperbole. Hence the reception you are getting.
The world isn't ending, youe computer just isn't working and you don't know how to fix it yourself. Help us to help you...
People, who later seemingly know what they are doing, should know better and be responsible for their reporting. In this case, the OP later seems to know what he is doing, making the first FUD based posting even more believable by individuals susceptible to FUD.
FUD is FUD no matter how well intended.
Call it FUD or not the underlying situation is that FC15 messed up on some systems on upgrade. But so did F14, F13, F12, F11, ....
Anything that complex is going to break on some configuration, especially given the way Fedora is tested which is going to find bugs in common configurations well, and unusual ones badly.
Unless they've changed the instructions for just about any OS upgrade (Windows, Linux, whatever) and the advice around it has always started
"First make a backup"
Midn you the other semi-serious rule of course is never install a .0 release, and FC15 is kind of a .0 release for the init code (which is absolutely critical) and Gnome 3 8)
And if the crap completely hits the fan you can specify a program to run off the root fs with init=/bin/sh or similar. That is done by the kernel so its very very hard for an upgrade to screw that one up.
Alan
On 30/05/11 09:11, n2xssvv.g02gfr12930 wrote:
To anyone trying to upgrade from Fedora 14 to Fedora 15, DON'T EVEN TRY!!! I've just tried and have had numerous problems, finally resulting in being unable to boot up any kernel version at all, using inittab mode 1,3, or 5. In view of this it appears I will have to reinstall Fedora 14.
cpp4ever
I will be going down the path of doing a fresh install of Fedora 15, after doing a backup. This will take longer, so be it. It appears to me that you are all passionate about Linux/Fedora, but comments like, Troll, FUD, Hysteria, etc, in response to others problems does not IMO encourage others to try Linux/Fedora. Certainly, I'll be more reluctant to post problems here if that's the type of response I can expect. Let alone try to encourage others to try Fedora/Linux. An end to this problem and the IMO somewhat disappointing response folks can expect here.
Regards, and Amen to this
cpp4ever
Am Montag, den 30.05.2011, 09:11 +0100 schrieb n2xssvv.g02gfr12930:
To anyone trying to upgrade from Fedora 14 to Fedora 15, DON'T EVEN TRY!!!
After reading this thread I still don't know what exactly you did to upgrade your system. Can you please give us more details ? What commands did you run and what repos were enabled?
This is what I did yesterday:
# rpm -Uvh \ http://download.fedora.redhat.com/pub/fedora/linux/releases/15/Fedora/x86_64... \ http://download.fedora.redhat.com/pub/fedora/linux/releases/15/Fedora/x86_64... # yum clean all # yum update yum # yum --releasever=15 distro-sync # reboot
Worked like a charm. Next time, please follow the instructions from the wiki, namely http://fedoraproject.org/wiki/YumUpgradeFaq and http://fedoraproject.org/wiki/YumUpgradeFaq#Fedora_14_-.3E_Fedora_15
Regards, Christoph
The original post was obviously a mistake and I'm an hysterical, fud spreading troll who deserves no sympathy. Sorry for wasting all of your time.
Regards
cpp4ever
On 05/30/2011 04:05 PM, n2xssvv.g02gfr12930 wrote:
On 30/05/11 09:11, n2xssvv.g02gfr12930 wrote:
To anyone trying to upgrade from Fedora 14 to Fedora 15, DON'T EVEN TRY!!! I've just tried and have had numerous problems, finally resulting in being unable to boot up any kernel version at all, using inittab mode 1,3, or 5. In view of this it appears I will have to reinstall Fedora 14.
cpp4ever
I will be going down the path of doing a fresh install of Fedora 15, after doing a backup. This will take longer, so be it. It appears to me that you are all passionate about Linux/Fedora, but comments like, Troll, FUD, Hysteria, etc, in response to others problems does not IMO encourage others to try Linux/Fedora. Certainly, I'll be more reluctant to post problems here if that's the type of response I can expect. Let alone try to encourage others to try Fedora/Linux. An end to this problem and the IMO somewhat disappointing response folks can expect here.
Regards, and Amen to this
cpp4ever
Just to add my (worthless) 2 cents, my F14 to F15 "upgrade" left me with broken ATI video (black screen), using the open source driver. Doing a fresh install, from the live cd fixed the problem.
Regards,
John
On 05/30/2011 04:34 PM, n2xssvv.g02gfr12930 wrote:
The original post was obviously a mistake and I'm an hysterical, fud spreading troll who deserves no sympathy. Sorry for wasting all of your time.
Oh, what you wanted was sympathy? Why didn't you say so? And here we were all thinking you wanted help. Silly us!
On 05/30/2011 04:34 PM, n2xssvv.g02gfr12930 wrote:
The original post was obviously a mistake and I'm an hysterical, fud spreading troll who deserves no sympathy. Sorry for wasting all of your time.
Regards
cpp4ever
Actually, you seems to have provided entertainment for lots of users, based on the size and number of the followup threads. You have my sympathy, because I felt the same way after my failed upgrade attempts.
Don't let the bastards wear you down.
John
Oh, what you wanted was sympathy? Why didn't you say so? And here we were all thinking you wanted help. Silly us!
I hope when you need help and ask in the wrong way you are treated the same way you treat others. At that point maybe you'll learn some useful lessons.
Alan
n2xssvv.g02gfr12930 wrote:
The yum upgrade from the minimal Fedora 14 KDE ran smoothly, (no conflicts or removals). Unfortunately on rebooting I cannot boot at all, (inittab 3 or 5), and when I just tried the Fedora 14 rescue DVD, that failed as well!!
I'm probably being a bit slow, but what exactly do you mean by "yum upgrade"? What commands do you give? I find it quite difficult to work out exactly what you are doing.
Michael Schwendt wrote:
Updating the F14 prior to upgrading it to F15 may be a mistake already, given that F14 updates may be newer than F15 release. Do you enable the "updates" network repo during F15 upgrade?
Is that true? I thought I'd read somewhere that one should update the old system before upgrading?
On 05/30/2011 08:40 PM, Timothy Murphy wrote:
Michael Schwendt wrote:
Updating the F14 prior to upgrading it to F15 may be a mistake already, given that F14 updates may be newer than F15 release. Do you enable the "updates" network repo during F15 upgrade?
Is that true? I thought I'd read somewhere that one should update the old system before upgrading?
yes, he (Michael) is correct - imagine an important update is available but F15 has gone gold and is frozen - no prob it goes into F15 updates - and its important so it goes into F14 as well ... now your F14 is ahead of the released F15 ... until you run an update on F15 or include the updates repo during the install/upgrade process.
At least that is my understanding.
The more time passes since the release the worse this problem may get because there is no official re-spin of F15.
What I do - is use mock/pungi to build a fully updated DVD (personal re-spin) and install from there ...
So to confirm, what is the preferred method to upgrade? I usually update daily, so in F14 most likely I'd have the latest and greatest updates when I decided to move to F15. Do I just need to bite the bullet and do a clean install? On a clean install is it safe to keep your /home partition and only update the / partition?
On May 30, 2011, at 8:00 PM, Genes MailLists lists@sapience.com wrote:
On 05/30/2011 08:40 PM, Timothy Murphy wrote:
Michael Schwendt wrote:
Updating the F14 prior to upgrading it to F15 may be a mistake already, given that F14 updates may be newer than F15 release. Do you enable the "updates" network repo during F15 upgrade?
Is that true? I thought I'd read somewhere that one should update the old system before upgrading?
yes, he (Michael) is correct - imagine an important update is available but F15 has gone gold and is frozen - no prob it goes into F15 updates - and its important so it goes into F14 as well ... now your F14 is ahead of the released F15 ... until you run an update on F15 or include the updates repo during the install/upgrade process.
At least that is my understanding.
The more time passes since the release the worse this problem may get because there is no official re-spin of F15.
What I do - is use mock/pungi to build a fully updated DVD (personal re-spin) and install from there ...
-- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
On 05/30/2011 06:56 PM, Alex wrote:
So to confirm, what is the preferred method to upgrade? I usually update daily, so in F14 most likely I'd have the latest and greatest updates when I decided to move to F15.
Same here. I've been using preupgrade since (I think) F11 with good results.
On Tue, 31 May 2011 01:18:47 +0200, Christoph Wickert wrote:
Am Montag, den 30.05.2011, 09:11 +0100 schrieb n2xssvv.g02gfr12930:
To anyone trying to upgrade from Fedora 14 to Fedora 15, DON'T EVEN TRY!!!
After reading this thread I still don't know what exactly you did to upgrade your system. Can you please give us more details ? What commands did you run and what repos were enabled?
This is what I did yesterday:
# rpm -Uvh \ http://download.fedora.redhat.com/pub/fedora/linux/releases/15/Fedora/
x86_64/os/Packages/fedora-release-15-1.noarch.rpm
\ http://download.fedora.redhat.com/pub/fedora/linux/releases/15/Fedora/
x86_64/os/Packages/fedora-release-rawhide-15-1.noarch.rpm
# yum clean all # yum update yum # yum --releasever=15 distro-sync # reboot
See, that's my problem in all of this. I still have no clear idea how the original poster attempted to update from Fedora 14 to Fedora 15.
There seem to be at least two paths to do this (without a complete reinstall). The first is to use the preupgrade path. A link to this can be found here:
http://fedoraproject.org/wiki/PreUpgrade
The second is the one outlined in the message above. Both have been reported to work well for various users.
What I would have liked to see from the original poster is the following:
Following the steps outlined in the PreUpgrade link, I did the following:
1. (command) Expected results Actual results
2. (command) Expected results Actual results
n. (command) Expected results Actual results (failure description)
Then, it would be nice to have seen the same sort of format followed for problem diagnosis and fix attempts.
The above (plus hardware particulars) would have given everyone a good chance to evaluate whether or not an upgrade or a fresh install is appropriate.
I've personally done some rather crazy things with preupgrade, including skipping versions. Outside of some pulse audio and font rendering issues, I've not been bit. The pulse audio problem was a bit difficult to fix, but now I have a working configuration (and the configuration files in version control). After playing around with a personal .fonts.conf, I've managed to get everything looking nice except for 12 point Courier in Emacs. 14 point Courier looks fine, so I'll live with that for now.
My real problem in moving from Fedora 14 to Fedora 15 stems from running the binary NVidia driver for an old 7600 GS card. According to numerous reports on the NVidia forums, this could result in lockups due to issues with xorg 1.10. Also, without patched Cairo libraries, themes that use gradients perform unusably slowly with the later NVidia drivers.
So I guess in order for me to upgrade, I have to answer the following questions:
1. Has Fedora patched the Xorg server to not do a recursive call to the underlying video drivers?
If not, then I will have to wait until NVidia fixes their drivers (again). An alternate solution is to downgrade to the last version of Xorg 1.9.5 (if possible). I'm sorry that I cannot be more explicit here, but the details are scarce on the NVidia forums.
2. Has the gradient patch been removed from Cairo 1.10-3?
I know that the original plan was to do this for Fedora 15, but I could find no mention of it after glancing at the change logs. If so, then I'll have to either re-apply the patch for the gradients or wait until NVidia fixes their drivers (again).
These are the challenges I face in upgrading. If the original poster had been this explicit, I could have determined which of the following do to.
1. Back up and do a fresh install of Fedora 15 2. Use preupgrade to go from Fedora 14 to Fedora 15 3. Wait until my issues are answered, then move to Fedora 15 4. Skip Fedora 15 and wait until Fedora 16
However, the all-caps WARNING! just provides anecdotal information concerning one person's challenges. While I'm sympathetic to this person's frustrations, I have no idea whether these challenges are germane to my environment or not.
. . . . just my two cents.
/mde/
On 05/30/2011 07:49 PM, Mark Eggers wrote:
If not, then I will have to wait until NVidia fixes their drivers (again).
Or, you can uninstall the binary blob, and follow the instructions here to install akmond-nvidia and be done with it once and for all: http://forums.fedoraforum.org/showthread.php?t=204752
On Mon, 30 May 2011 19:56:02 -0700, Joe Zeff wrote:
On 05/30/2011 07:49 PM, Mark Eggers wrote:
If not, then I will have to wait until NVidia fixes their drivers (again).
Or, you can uninstall the binary blob, and follow the instructions here to install akmond-nvidia and be done with it once and for all: http://forums.fedoraforum.org/showthread.php?t=204752
My understanding of this is as follows:
1. It's a repackaging of the NVidia binary blobs that does the following:
a) Adds this to the yum/rpm database b) Avoids certain libraries getting replaced by other rpm packages
2. The driver may be a few revisions behind NVidia's current driver
3. Occasionally the driver release lags kernel releases by a few days
So unless the maintainers hack the proprietary code to address the bugs I've previously mentioned, the only advantages are:
1. I don't have to rebuild the kernel module by hand 2. I don't have to reinstall when an update overwrites some libraries 3. It's in the rpm / yum database
None of those seem to address the two (most likely NVidia) bugs. It also makes testing beta and legacy drivers more difficult when trying to work around these and other bugs.
I have no problems rebuilding kernel modules.
If the rpms have specific solutions for Fedora compatibility beyond ease of packaging / installation, then that would be welcome news indeed. All of my reading so far indicates that this is not the case.
I would be happy to be shown incorrect.
. . . . just my two cents.
/mde/
On 05/30/2011 09:17 PM, Mark Eggers wrote:
I would be happy to be shown incorrect.
Your understanding is, on the whole, correct. However, you can always use akmod-nvidia instead. If there's not a kmod for the current kernel, akmod builds it on the fly at boot. It's not a panacea by any means, but for most of us, it's much better than having to remember to re-install the binary blob every time there's a kernel update.
On 31/05/11 03:10, Joe Zeff wrote:
On 05/30/2011 06:56 PM, Alex wrote:
So to confirm, what is the preferred method to upgrade?
Preupgrade is the officially supported method, as it includes the updates repo during its calcualtions.
http://fedoraproject.org/wiki/Upgrading "Preupgrade"
Thanks! I'm glad there is some form of an upgrade method. I've usually just reformatted for other distros, but it's nice to have another option.
On Tue, 2011-05-31 at 08:23 +0100, Frank Murphy wrote:
On 31/05/11 03:10, Joe Zeff wrote:
On 05/30/2011 06:56 PM, Alex wrote:
So to confirm, what is the preferred method to upgrade?
Preupgrade is the officially supported method, as it includes the updates repo during its calcualtions.
http://fedoraproject.org/wiki/Upgrading "Preupgrade"
-- Regards,
Frank Murphy UTF_8 Encoded Friend of Fedora
Alex wrote:
So to confirm, what is the preferred method to upgrade? I usually update daily, so in F14 most likely I'd have the latest and greatest updates when I decided to move to F15. Do I just need to bite the bullet and do a clean install? On a clean install is it safe to keep your /home partition and only update the / partition?
I always keep separate /home and /boot partitions. This has occasionally caused minor problems in the past, but Fedora-14 to Fedora-15 was the simplest upgrade I remember. I did both fresh install and upgrade, and both worked without a single problem on very different computers.
I always keep Fedora up-to-date, and have never had any problem from this. I'm sure the suggestion that you shouldn't update if you are going to upgrade is misguided. How long before an upgrade are you supposed to stop updating?
Nowadays I always keep a spare partition for a new installation if I have enough space. The installation always creates a new grub.conf but it saves the old and I just add this to the new one (deleting duplicate material).
Incidentally, isn't it time the Fedora developers gave up this passion for DVDs? Does anyone burn DVDs to install Fedora today? Half the new machines I see don't have DVD drives anyway. Surely everyone has a big enough USB stick? Why not be honest, and take that as the default?
On Mon, 2011-05-30 at 22:04 -0700, Joe Zeff wrote:
On 05/30/2011 09:17 PM, Mark Eggers wrote:
I would be happy to be shown incorrect.
Your understanding is, on the whole, correct. However, you can always use akmod-nvidia instead. If there's not a kmod for the current kernel, akmod builds it on the fly at boot. It's not a panacea by any means, but for most of us, it's much better than having to remember to re-install the binary blob every time there's a kernel update.
The real question is, is the nvidia blob still necessary? In F15, the nouveau driver has 3D acceleration enabled by default. Performance might not be all the way to the nvidia drivers, but GNOME Shell runs in standard mode with the default nouveau driver. That should at least tide you over until the nvidia packages catch up.
On 05/31/2011 05:58 AM, Timothy Murphy wrote:
I'm sure the suggestion that you shouldn't update if you are going to upgrade is misguided. How long before an upgrade are you supposed to stop updating?
To clarify, I believe the suggestion (by Michael) was to ensure that the update repo is included as part of an upgrade to new version (preupgrade does this) - not that one should not update your current distro.
On Tue, 2011-05-31 at 02:26 -0500, Alex wrote:
Thanks! I'm glad there is some form of an upgrade method. I've usually just reformatted for other distros, but it's nice to have another option.
Be warned, however, that preupgrade requires more than 512MB RAM (I think 768MB is enough). After the reboot, the system hangs if there's not enough memory. Rebooting again brings up the un-upgraded system. The yum upgrade should work without booting to an installer, so should work in limited memory.
On Tue, 2011-05-31 at 08:23 +0100, Frank Murphy wrote:
On 31/05/11 03:10, Joe Zeff wrote:
On 05/30/2011 06:56 PM, Alex wrote:
So to confirm, what is the preferred method to upgrade?
Preupgrade is the officially supported method, as it includes the updates repo during its calcualtions.
http://fedoraproject.org/wiki/Upgrading "Preupgrade"
-- Regards,
Frank Murphy UTF_8 Encoded Friend of Fedora
Matthew Saltzman writes:
On Mon, 2011-05-30 at 22:04 -0700, Joe Zeff wrote:
On 05/30/2011 09:17 PM, Mark Eggers wrote:
I would be happy to be shown incorrect.
Your understanding is, on the whole, correct. However, you can always use akmod-nvidia instead. If there's not a kmod for the current kernel, akmod builds it on the fly at boot. It's not a panacea by any means, but for most of us, it's much better than having to remember to re-install the binary blob every time there's a kernel update.
The real question is, is the nvidia blob still necessary? In F15, the nouveau driver has 3D acceleration enabled by default. Performance might not be all the way to the nvidia drivers, but GNOME Shell runs in standard mode with the default nouveau driver. That should at least tide you over until the nvidia packages catch up.
I don't use nvidia's blob, but nouveau's stability is still not consistent. Maybe about 10% of the time X locks up when I open gthumb. If I ssh in and kill X, Gnome will whine and go into fallback mode. I must reboot to regain hardware acceleration.
It's not a big deal to me, especially as compared to the rest of the issues with gnome 3, but I can see how some might prefer to stick with nvidia.
On Tue, May 31, 2011 at 10:15:57AM -0400, Sam Varshavchik wrote:
Your understanding is, on the whole, correct. However, you can always use akmod-nvidia instead. If there's not a kmod for the current kernel, akmod builds it on the fly at boot. It's not a panacea by any means, but for most of us, it's much better than having to remember to re-install the binary blob every time there's a kernel update.
The real question is, is the nvidia blob still necessary? In F15, the nouveau driver has 3D acceleration enabled by default. Performance might not be all the way to the nvidia drivers, but GNOME Shell runs in standard mode with the default nouveau driver. That should at least tide you over until the nvidia packages catch up.
I don't use nvidia's blob, but nouveau's stability is still not consistent. Maybe about 10% of the time X locks up when I open gthumb. If I ssh in and kill X, Gnome will whine and go into fallback mode. I must reboot to regain hardware acceleration. It's not a big deal to me, especially as compared to the rest of the issues with gnome 3, but I can see how some might prefer to stick with nvidia.
It might not be a big deal but the lock ups, though not very frequent, sometimes occur at very inopportune moments. Also irritating is the snails pace at which graphical actions happen.
But I am not complaining since the situation, in my case at least, is even more irritating with regard to nvidia. I have tried with both kmod-nvidia and akmod-nvidia and done everything according to the book but I really wonder if the installation scripts from rpmfusion are 100% adapted to fed 15. The installation just can't get rid of the nouveau modules so you just boot up to the 'desktop' but mouse and keyboard can't activate anything.
I even tried some contortions with respect to initram, etc. but to no avail.
A couple of years ago I had no problems with rpmfusion kmod-nvidia's
Alexander
On 05/31/2011 02:58 AM, Timothy Murphy wrote:
Incidentally, isn't it time the Fedora developers gave up this passion for DVDs? Does anyone burn DVDs to install Fedora today? Half the new machines I see don't have DVD drives anyway. Surely everyone has a big enough USB stick? Why not be honest, and take that as the default?
Not everybody has a brand-new machine. Not everybody even has one that can boot off of USB. I can remember when Fedora stopped providing a CD version and I didn't have a DVD drive. (Nor, I might add, the money to buy one because they were still quite expensive.) I had to find a third-party website that had broken the DVD up into CDs. Just because you don't like DVDs doesn't mean that they (and CDs) aren't still important to a large fraction of Fedora users.
On 31 May 2011 18:33, Joe Zeff joe@zeff.us wrote:
On 05/31/2011 02:58 AM, Timothy Murphy wrote:
Incidentally, isn't it time the Fedora developers gave up this passion for DVDs? Does anyone burn DVDs to install Fedora today? Half the new machines I see don't have DVD drives anyway. Surely everyone has a big enough USB stick? Why not be honest, and take that as the default?
Not everybody has a brand-new machine. Not everybody even has one that can boot off of USB. I can remember when Fedora stopped providing a CD version and I didn't have a DVD drive. (Nor, I might add, the money to buy one because they were still quite expensive.) I had to find a third-party website that had broken the DVD up into CDs. Just because you don't like DVDs doesn't mean that they (and CDs) aren't still important to a large fraction of Fedora users.
I think you'll find Timothy said "take that as the default", not "stop releasing the DVD version". I for one would like more prominence to the USB image and methods of creating it on the Fedora install pages, just because a tleast two of the machines I generally install it on don't have a CD/DVD drive (all of our Office machines lack them).
On Tue, 31 May 2011 18:19:07 +0200, Alexander Volovics wrote:
On Tue, May 31, 2011 at 10:15:57AM -0400, Sam Varshavchik wrote:
Your understanding is, on the whole, correct. However, you can always use akmod-nvidia instead. If there's not a kmod for the current kernel, akmod builds it on the fly at boot. It's not a panacea by any means, but for most of us, it's much better than having to remember to re-install the binary blob every time there's a kernel update.
It's actually a little worse than that, although no longer strictly necessary. I reinstall every time there's a new X server, screen saver update, or new GL libraries. Yes, it's somewhat of a pain, but see below.
The real question is, is the nvidia blob still necessary? In F15, the nouveau driver has 3D acceleration enabled by default. Performance might not be all the way to the nvidia drivers, but GNOME Shell runs in standard mode with the default nouveau driver. That should at least tide you over until the nvidia packages catch up.
My first impression of Gnome 3 was pretty unpleasant. I'll try it for a week in Fedora 15, but right now it doesn't seem to fit my use cases or work flow (see below).
I don't use nvidia's blob, but nouveau's stability is still not consistent. Maybe about 10% of the time X locks up when I open gthumb. If I ssh in and kill X, Gnome will whine and go into fallback mode. I must reboot to regain hardware acceleration. It's not a big deal to me, especially as compared to the rest of the issues with gnome 3, but I can see how some might prefer to stick with nvidia.
It might not be a big deal but the lock ups, though not very frequent, sometimes occur at very inopportune moments. Also irritating is the snails pace at which graphical actions happen.
But I am not complaining since the situation, in my case at least, is even more irritating with regard to nvidia. I have tried with both kmod-nvidia and akmod-nvidia and done everything according to the book but I really wonder if the installation scripts from rpmfusion are 100% adapted to fed 15. The installation just can't get rid of the nouveau modules so you just boot up to the 'desktop' but mouse and keyboard can't activate anything.
I even tried some contortions with respect to initram, etc. but to no avail.
A couple of years ago I had no problems with rpmfusion kmod-nvidia's
Alexander
I've tried Gnome 3 a couple of times from within Fedora 14. To be fair, it's hard to give Gnome 3 a fair chance in Fedora 14, so I will use it exclusively for a week once I upgrade to Fedora 15.
However, I'm a software pack rat. I use lots of different applications, and I experiment with more. Finding software in a pile of icons seemed difficult, and taking my hand off the mouse to type slows down the interaction. Maybe there are ways to organize favorites that I can live with. I don't know, so I'll have to experiment.
For the record, I had a similar issue with KDE 4 and it's menu organization by description first, then application name. I find applications by category / name, but I guess many people find applications by description.
Given the above, I've been working more comfortably in KDE 4 for casual work, and WindowMaker for heads-down work. Given the recent improvement in KDE's performance, I've been spending more and more time in KDE and I'm beginning to enjoy its eye candy.
And there's the rub. The KDE / desktop effects / NVidia combination has a history of challenges. I've spent a reasonable amount of time reading the NVidia forums to find the configuration necessary for stability and performance. I have options enabled on driver loading and in xorg.conf that improve performance and stability. I also overclock the 7600GS, since it and my 2.6 GHz P4 need all the help they can get.
Right now the nouveau driver doesn't offer me the flexibility I need in order to get the performance I would like from KDE. I would like to contribute, but I'm already contributing (mostly answering questions and writing documentation) on other projects. There are unfortunately so many hours in a day. Besides the 7600 is an old card, and I can't imagine that there is a lot of interest in improving the driver for it.
As for kmod and akmod, I've not really tried them. Other than packaging / convenience, I've not seen a compelling reason to use them. Also, as Alexander mentioned above, there seem to be edge cases where kmod or akmod installations are problematic. I've seen postings on various forums indicating this as well. While less convenient, I've never had a problem installing the binary blob from NVidia (aside from a few SELinux issues which I have a script for).
LXDE plus compiz seem to be another possible choice. I'll investigate that as well when I move to Fedora 15.
. . . . just my two cents.
/mde/
On 05/31/2011 06:16 AM, Matthew Saltzman wrote:
but GNOME Shell runs in standard mode with the default nouveau driver.
That's good to know, if I ever go back to Gnome. XFCE works just fine, TYVM, with Compiz and the kmod-nvidia driver. (I do have the akmod installed for those rare times when kmod's slow in updating.)
On 05/31/2011 09:19 AM, Alexander Volovics wrote:
A couple of years ago I had no problems with rpmfusion kmod-nvidia's
Have you checked the F15 setup guide at fedoraforums? There might be a step you're not aware of that would fix things for you. And, if not, there's lots of people there who know this stuff and are more than willing to help.
On 05/31/2011 11:09 AM, Sam Sharpe wrote:
I for one would like more prominence to the USB image and methods of creating it on the Fedora install pages
Possibly the best option would be for them simply to add a USB image to the list of downloads.
other than a problem with CUPS, no problem here
On Mon, May 30, 2011 at 3:11 AM, n2xssvv.g02gfr12930 < n2xssvv.g02gfr12930@ntlworld.com> wrote:
To anyone trying to upgrade from Fedora 14 to Fedora 15, DON'T EVEN TRY!!! I've just tried and have had numerous problems, finally resulting in being unable to boot up any kernel version at all, using inittab mode 1,3, or 5. In view of this it appears I will have to reinstall Fedora 14.
cpp4ever
-- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
On 06/03/2011 05:23 PM, Javier Perez wrote:
other than a problem with CUPS, no problem here
On Mon, May 30, 2011 at 3:11 AM, n2xssvv.g02gfr12930 <n2xssvv.g02gfr12930@ntlworld.com mailto:n2xssvv.g02gfr12930@ntlworld.com> wrote:
To anyone trying to upgrade from Fedora 14 to Fedora 15, DON'T EVEN TRY!!! I've just tried and have had numerous problems, finally resulting in being unable to boot up any kernel version at all, using inittab mode 1,3, or 5. In view of this it appears I will have to reinstall Fedora 14. cpp4ever -- users mailing list users@lists.fedoraproject.org <mailto:users@lists.fedoraproject.org> To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines--
/_/\ |O O| pepebuho@gmail.com mailto:pepebuho@gmail.com
~~~~ While the night runs ~~~~ toward the day... m m Pepebuho watches from his high perch.
I'm sure somebody will be able to help you with the cups problem. Although from my experience I've noticed how Fedora 15 install is configured differently from Fedora 14.
Congratulations by the way, and I hope it settles down to a good stable version for you.
Actually, that would be selinux=0, instead of enforcing=0
On Mon, May 30, 2011 at 3:26 PM, Michael Schwendt mschwendt@gmail.comwrote:
On Mon, 30 May 2011 20:16:09 +0100, NG wrote:
How to collect technical information when Fedora 15 fails to boot?
To check whether your theory of SELinux problems could be true, try booting with the enforcing=0 kernel arg.
Descriptions such as "cannot boot at all" are useless, because certainly you could mention a few details about what parts of the boot process work, what is displayed on screen (possibly by leaving the graphical booter with ESC), and where it stops unexpectedly. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
El 30/05/11 18:52, Robert G. (Doc) Savage escribió:
On Mon, 2011-05-30 at 22:13 +0530, Rahul Sundaram wrote:
On 05/30/2011 09:44 PM, Robert G. (Doc) Savage wrote:
Frank,
Will this work on an old 32-bit Thinkpad that's maxed out with 512MB of RAM? Installing from DVD fails.
You can try upgrading piecemeal. Some major set of packages, python, then gtk and so on
Rahul,
That's what I was thinking. The roadblock I run into with a conventional DVD install/upgrade is:
[ 7.076671] Trying to unpack rootfs image as initramfs...
Hey there!
I had the same problem, could not install or upgrade with DVD, netinstall or preupgrade one Thinkpad R51 with 512 MB RAM.
I did succeed with distro-sync and is working wonderfully (we use XFCE).
First I removed a lot of games, multimedia programs and others (it's my 4 year old's computer) so that I would have as much free space as possible and then, due to lack of space (still), I installed the fedora-release package and upgraded a few packages that did not pull many dependecies, and then distro-synced into Fedora 15 the rest.
Greetings! Ester
On Sat, 4 Jun 2011 14:30:53 -0500, JP wrote:
Actually, that would be selinux=0, instead of enforcing=0
No, turning off SELinux is more brute-force than permissive mode.
On Mon, May 30, 2011 at 3:26 PM, Michael Schwendt wrote:
On Mon, 30 May 2011 20:16:09 +0100, NG wrote:
How to collect technical information when Fedora 15 fails to boot?
To check whether your theory of SELinux problems could be true, try booting with the enforcing=0 kernel arg.
Descriptions such as "cannot boot at all" are useless, because certainly you could mention a few details about what parts of the boot process work, what is displayed on screen (possibly by leaving the graphical booter with ESC), and where it stops unexpectedly.
-
Alan Cox -
Alex -
Alexander Volovics -
Christoph Wickert -
Dr. Michael J. Chudobiak -
Ed Greshko -
Ester Muñoz Aparicio -
Frank Murphy -
Garry Williams -
Genes MailLists -
Javier Perez -
Joe Zeff -
John Wendel -
Kevin Fenzi -
Mark Eggers -
Matthew Saltzman -
Michael Schwendt -
Mikkel L. Ellertson -
n2xssvv.g02gfr12930 -
Patrick Lists -
Patrick O'Callaghan -
Rahul Sundaram -
Ralf Corsepius -
Robert G. (Doc) Savage -
Sam Sharpe -
Sam Varshavchik -
Suvayu Ali -
Timothy Murphy