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 some problem with the graphics driver (nvidia from livna), which seems to be starting "too late". When The startup screen is supposed to show up the screen complains of wrong frequencies. Then the computer then either freezes or continues to the login screen when the nvidia logo shows up and everything works fine. So my question is, how do I disable the grapics during the startup period? Offcourse it would be preferable if I instead can make it work.
So the startup screen when Fedora is booting up prior to login screen? You can comment that out in /etc/rc.sysinit on line 346. Should look like this
# Start the graphical boot, if necessary; /usr may not be mounted yet, so we
# may have to do this again after mounting
346:RHGB_STARTED=0
347:mount -n /dev/pts >/dev/null 2>&1
348:[ -n "$SELINUX_STATE" ] && restorecon /dev/pts >/dev/null 2>&1
349:if strstr "$cmdline" rhgb && ! strstr "$cmdline" early-login && [ "$BOOTUP" = "color" -a "$GRAPHICAL" = "yes" -a -x /usr/bin/rhgb ]; then
350: ( . /etc/sysconfig/i18n 2>/dev/null ; /usr/bin/rhgb )
351: RHGB_STARTED=1
352:fi
So just taking a guess you could comment out line 350 & 351 and put in it's place this -> echo "Disabled graphical boot".
I've added the line numbers on the left just to make it easier on you, you won't see these when you open the file of course.
If you're using "vi" to open the file, once open type :350 and hit enter and it will take you to line 350 So like this
# Start the graphical boot, if necessary; /usr may not be mounted yet, so we
# may have to do this again after mounting
346:RHGB_STARTED=0
347:mount -n /dev/pts >/dev/null 2>&1
348:[ -n "$SELINUX_STATE" ] && restorecon /dev/pts >/dev/null 2>&1
349:if strstr "$cmdline" rhgb && ! strstr "$cmdline" early-login && [ "$BOOTUP" = "color" -a "$GRAPHICAL" = "yes" -a -x /usr/bin/rhgb ]; then
350: echo "Disabled graphical boot"
351: #( . /etc/sysconfig/i18n 2>/dev/null ; /usr/bin/rhgb )
352: #RHGB_STARTED=1
353:fi
Thanks for the reply. I will try this at once. Do you (or anyone else) have any idear how to get the graphical bootup to work? It would be so much nicer
The "fix" you describe sadly doesn't work. The message shows up like seven or 8 green "OKs" before the screen frequency goes haywire. Is there anywhere later in the file you would suggest to write something similar? Are you sure it won't screw up the bootup totally?
Try removing the rhgb parameter from the kernel line in your grub.conf file. That will prevent the blue splashscreen background for GRUB menu and the blue progress bar screen. But the log in screen will still be the graphical log in. Maybe that will help.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.