Fedora - InstallationThis forum is for the discussion of installation issues with Fedora.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Hi i was wondering if anyone can help. I have recently install Fedora Core 3 onto my server. The sever is a Compaq Proliant 6500, quad pent pro, 512 ram & 6 * 4.3Gb in raid 0 or 1.
When i boot the machine it reaches -
Initializing hardware.... storage network audio done [ OK ]
Then it hangs on me! When i installed Fedora i had to turn off the hardware probing because it also hanged on me.
I reinstalled fedora core 3 like 6 times till i figured it out...i even resorted to install FC2 and did a yum upgrade to FC3 LOL!!!
You'll probably need to re-install it like this:
Once you put in the first installation CD, it will ask you to press enter or type 'linux' to install...
type in 'linux acpi=off'
I hope this is the solution to your problem!
ps. if not, please don't hate me...
pps. The best way (in my oppinon) to setup your linux box is to have a few partitions...
that way if you need to reinstall, format all the partitions except /home that way, the system will always appear to be the same...even when you log in because all your personal settings are stored in your user directory.
Use the grub screen to halt the boot load (press space on start up), highlight the fedora command line, press 'e', highlight the line with the work kernal on it, press 'e' again, add the word 'single' right at the end of that line, press e to reboot.
It should now boot into mode 3, where you can edit the files to your hearts content as root.
(omit any ' ', i put them in to highlight what to type in)
I'm a Fedora man, but i love debian and even better Knoppix (which is also debian)!
If you're looking for bleeding edge you should install Knoppix! It has just about every thing you need, and if it doesn't all you have to do is 'apt-get install PackageName' and I guarantee you it will install it!
Updating that distro is dead simple too:
All you have to do is download Knoppix 3.7 (or higher) and then in a terminal type in 'knoppix-installer'
I just upgraded from FC2 to FC3 and the installation went fine, but when I try and boot, it hangs.
Mine gets slightly farther then bungle3 though. I see the initializing hardware line like he does, but then my screen flashes as it tires to load X. I'm not surprised X can't load, because I'm using the nvidia driver and haven't compiled it yet for FC3 (need to boot first =). Right after that I see a like about configuring the kernel and then it hangs.
My first thought was that my kernel didn't actually get upgraded and I was using a FC2 kernel. I went into linux rescue and deleted all my old kernels and did an upgrade install again. The FC3 kernel got installed... and the same thing happened.
I tried to hit 'I' to go into interactive boot, but it also didn't work since the boot process doesn't seem to get that far.
I'm running out of ideas... I'm down to the "this shouldn't make any difference, but I can't think of anything else" ideas... I'm going to boot into linux rescue and change X display drivers from nvidia to nv. I doubt that's causing any issues..
I've been kicking myself for being a putz when installing this machine. I did a default install for some reason and didn't follow my general rule to create a separate /home partition. If this wasn't the case, I'd have just copied any configuration files off and reinstalled fresh.... hell I probably would have done that to begin with.
I guess the worst case senario is to boot into linux rescue with the network loaded and copy my many gig /home partition to another machine, reinstall and then restore.
That'd suck... but on the bright side, I'd be able to fix my putziness of the past and create a /home partition this time =]
Linux rescue is a nice feature of the redhat based installation cds. You basically pop one in and at the boot prompt type "linux rescue"
You will be dumped into a shell with your file systems mounted in non-standard places. This lets you fix any issues you may have done which caused your system not to boot. If you need to you can always chroot into the your root filesystem if any commands need things to be in their standard locations. If you do that, you'll probably want to go into a subshell. If you do it in the main shell, you won't be able to get back to linux rescue's root w/o rebooting.
I ended up having to backup my home filesystem and do a fresh install on my system. It was nice because I was able to split off my home filesystem from the main one. This let me reinstall w/o blowing away my home directories. I'm up and running FC4 these days =]
I actually never needed the network in linux rescue. My recolection is that at least the FC3 rescue disk asked if you wanted to bring te network up. I don't know if it worked or not.
My guess would be to use ifconfig to bring up the network interface. Do a ifconfig -a to make sure the interface is there and then use ifconfig to load the ip address / network / broadcast / etc and then ifconfig eth0 up.
Either that or you can chroot into your filesystem and /etc/init.d/network start and that might work as well.