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.
Got a question. I upgraded to Fedora Core 1 and would like to get the Graphical boot working. I did manage to instal the rhgb***.rpm file. Then I see the following in the release notes.
and add the rhgb boot-time parameter to your bootloader configuration.
Would really appreciate some help in doing this. Not sure exactly what to add to what file. Since I am a relative newbie, please make it clear for me. Thanks.
Edit your /boot/grub/grub.conf file, and add "rhgb" to the end of the line starting with "kernel /vmlinuz...". Then, you'll need to look in your /etc/inittab and make sure the default runlevel is set to 5. There will be a section telling what runlevel is what, and the line "id:5:initdefault:". It make sure it has a five, and not another number. Should be good to go, after that.
Thanks for the response. I did put rhgb at the end of the vmlinuz line so that it looks like this,
[root@localhost grub]# more grub.conf
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You do not have a /boot partition. This means that
# all kernel and initrd paths are relative to /, eg.
# root (hd1,0)
# kernel /boot/vmlinuz-version ro root=/dev/hdd1
# initrd /boot/initrd-version.img
#boot=/dev/hda
default=0
timeout=10
splashimage=(hd1,0)/boot/grub/splash.xpm.gz
title Fedora Core (2.4.22-1.2115.nptl)
root (hd1,0)
kernel /boot/vmlinuz-2.4.22-1.2115.nptl ro root=LABEL=/ hdc=ide-scsi rhgb
initrd /boot/initrd-2.4.22-1.2115.nptl.img
title Windows ME
rootnoverify (hd0,0)
chainloader +1
Well, it did it part of the way. Once I got to the interactive part, it went into the graphical boot. Is it susposed to work that way? Thanks again.
The graphical boot starts after the kernel loads, so you still see the text of the kernel loading. Then the graphical boot takes over when fedora starts loading it's services.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.