FedoraThis forum is for the discussion of the Fedora Project.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have the same error thanks to my 'efforts' last night!
Hansi, Woessey - Did the you add anything new like I did, or did it just happen on the first boot after the install?
My story.. I have been running FC3 for a few weeks (far from perfectly) and then yesterday decided to try to get it working better. Obviously, I made a mistake somewhere!
This is what I did -
1. Install the ATI Rage 200 driver (8.14.13) for X.Org 6.8, and run flxrconfig utility for said driver.
2. Install yum updates to the following packages (the ones I can remember)
- alsa-utils
- alsa-lib
- up2date
..that's all I can remember. There was also a couple of the more general libraries, but I'm at work now, not home and don't have notes here.
Interestingly, I can hit Ctrl-C when the systems appears to stop at "configuring kernel parameters" and it enters runlevel 5. From there, the boot continues (or tries to) but can't 'touch' a couple of files (kudzu and syslog from memory) because the file system has loaded read-only. After that it halts again whilst trying to start the system logging daemon.
I will try to bring the system up in single-user mode (that's runlevel 1, right?) when I get home tonight, and see what I can find out from there. Not really sure what I'm looking for, but my first stop will be demsg, then var/log/messages (after I check that the kernel is still configured to log there).
Any other hints would be appreciated!
Last edited by BadDoggie987; 07-29-2005 at 04:59 AM.
if you use grub as your bootloader, you should be able to edit the boot commands and add either a 1
Mine works when I have
kernel /bzImage-2.6.12-mm1-rc3 1 vga=0x317
Quote:
Quote from http://www.sensiblesoftware.com/arti...Runlevels.html
You can also change the runlevel at boot time. If your system uses
LILO as the boot manager, you can append the runlevel to the boot
command :
LILO: linux 3 or
LILO: linux 5
If your system uses GRUB, you can change the boot runlevel by
pressing the `e' key to edit the boot configuration. append the
runlevel to the end of the boot command as shown:
kernel /vmlinuz ro root=/dev/hda1 5
Last edited by musicman_ace; 07-30-2005 at 05:23 AM.
I still don't understand how to do this stuff. I am extremely new to Linux. I know absolutely nothing about any of the commands. If you are going to tell me what to do, you need to tell me exactly what to type and when to type it. I'm sorry that I am this dumb about everything. I'm just trying to learn everything I can.
Thanks for all of the help and trying to fix my problem. I still can't get it to work so I am going to install Redhat 7.2 or Redhat 9. We'll see how that works for me.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.