mjp,

Going to an older kernel doesn’t seem to help. I restored the ext3 partition containing a fresh FC1 installation, updated up2date to 4.1.21-3 (as per the initial up2date recommendation), downloaded/manually installed the .2140 kernel (i.e., rpm -i kernel-2.4.22-1.2140.nptl.athlon.rpm) and rebooted to kernel .2140. Then I updated everything except the kernel (.2174) and the kernel-pcmcia-cs update.

The system crashed during the shutdown, which considering the number of updates, wasn’t a big surprise. During the reboot, I allowed the filesystem checker to start (i.e., “press =Y to start filesystem checker within 3 seconds” or whatever it said). The system soon thereafter locked up and gave what was probably a fatal error death screen that looked a lot like a WinNt Blue Screen Of Death (listed lots info about the stack, call trace, etc. and ending with “code: 8b 40 0c bb ff ff ff ff 89 d9 83 c0 08 89 44 24 10 89 c7 31").

There are a few more permutations of updates that can be tried. Maybe it’s finally time to order the SuSE 9.0 disks, which I would have already tried if I could find a download (Added later: Never mind, I found a fast site to download an evaluation copy from).


Hey Lurkers,

It seems that there are more than the usual number of Fedora upgrade problems floating around in this forum right now and I bet that there are a lot of dead systems out there right now. If you are having similar problems with the recent Fedora upgrades, why not post a note here and give a few hardware details about your system (especially pentium vs athlon). It might be helpful. I would be really interested to know if the problems are exclusive to athlons or to some of the chipsets that are associated with athlon motherboards.

Speak now or forever hold your peace.

WhatsHisName,
What I'm probably going to do is after I repartition and reinstall, I will just download the updates I did the last time and stop with a "functioning" system and then just wait and see if I can find any info on this.
I downloaded the isos to Debian and will try and install on a spare partition as well. You mentioned Suse; I too would like to try it before buying it but the only evaluation copy I could find was to run it from the cd and I really didn't like doing it that much. However, it is a good way to see if you like the system. There may come a time when I will anti up the cash for their latest version and make a go of it.
Do you think that RedHat is using the Fedora updates like a beta testing system. Didn't they say that some of Fedora apps may be used on RHEL. I really don't know if this applies to the updates or not.
Hopfully others will give some feedback and maybe some sense can be made of this .

Unfortunately, I am having to post this from Windows because Fedora's up2date made my GNU/Linux partition unbootable. I can get a command prompt but the gui is horribly screwed. When I ran up2date, I noticed a number of XFree updates and almost every single update challenged the hashes of the packages.

Here's the error message I receive when I attempt to startx from the command line:

xauth:error while loading shared libraries: libXmuu.so.1: cannot open shared object file: No such file or directory.

Regrettably, I don't have time to pursue this problem any further right now but will try to provide more info when possible.

Pertinent System info:

P3 802 Mhz
512 MB SDRAM
Radeon 8500


--K.

Hey guys,

Just thought I'd let you know that I found this thread while having the same issues right after my latest updates. To fix the problem on getting back to using GNome, I basically ran from the command line: up2date XFree86. This updated my X configuration packages and I am able to get back on. However, in my experience, my GUI isn't acting the same. I am also trying to reinstall (or reupdate) my kernel to hopefully fix other bugs involved but 'up2date --force kernel' isn't working. Does anybody have any other ideas?

That almost got me fixed. After running up2date XFree86, I now get an eternal hourglass at boot-time. I should probably play around with interactive booting to see where the failure is.

Thanks for your suggestion. It's progress. Isn't it interesting that the process of learning is both humiliating and gratifying?

Hopefully, with the four-day weekend I'm facing, I'll have the opportunity to play around and discover what's plaguing my box.

Happy St. Patrick's Day!

--K.

hey all,

I am getting the same errors on a pos P3/450 pentium, with a rage128 graphics card.

somehow I think this has got very little to do with the graphics card.

interesting knowing I amn't the only one though - last time I blindly run up2date...

Hey,

I had the same problem a little while ago and was unable to get rid of it by searching and using the advice on this site. I have reinstalled and updated all but 52 of the packages so far. I left out hwdata and the initscripts (the latter I left out because the error messages I get involve init).

Anyway, I too have an Athlon processor. Anything else hardware-wise, I'm not too sure, but I think this is all that is relevant. I'll keep updating and leave a message if I narrow the malicious package(s) down. Thanks.