FedoraThis forum is for the discussion of the Fedora Project.
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.
No, not old hardware. Dual processor intel 1600GHz 4GB RAM. Yes nvidia Geforce 9200. In older versions of Fed I had nouveau blacklisted. But the newer versions, eg this Fed 12 works fine without the nvidia driver.
I ran preupgrade. I can boot from its grub entry, but it never goes further than 'starting anaconda' I have to unplug, and reboot.
I just thought others may have the same problem. I have a 524MB boot partition.
As I said, the newer kernels will not work on this machine.
F14 is due in October. I'm running the LXDE spin (64-bit) compose of Aug 24 updated literally five minutes ago. On-board nvidia 9100 w/ nouveau driver and mesa-dri-drivers-experimental. Haven't tried running metacity, mutter, or compiz, but openbox+xcompmgr is somewhat buggy (openbox w/o xcompmgr is fine).
I haven't had any problems with F13. I would suggest trying to start in a text mode, either runlevel 1 or 3, just to see if the problem is graphics/video related or something do with services. Do you load any services after SMB, perhaps something in rc.local? Might also look there to see if you can disable anything that could be causing the halt. SMB starts pretty late in the scheme of things so there shouldn't be too much to look at services wise.
I've been running F14 Alpha a few days now. Fedora is now using systemd rather than upstart for init and it takes a little digging to figure out how things startup. After installing I had a problem with it booting in runlevel 3 instead of 5. Then after initial updates it began starting up in rescue mode (that was new). I found and fixed a bad link and it has been working fine since then.