Screen stuck on start The 2019 Stack Overflow Developer Survey Results Are In Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern) 2019 Community Moderator Election ResultsCan't control brightness on HP Pav dv6t running Fedora 16Stuck on Fedora splash screen after OpenBox3/tint2 installHow to enable OpenGL rendering on Fedora 18 with an Intel Corporation 82852/855GM?Installing NVIDIA graphics driver for Optimus configurationFedora 20 stuck in Emergency ModeGotomeeting on Fedora - crashes often when I start sharing the screenWhat's NUL-bombing my console during shutdown?Fedora 26 KDE Plasma Desktop will not boot with external monitorFedora 28 server install failurei915 Graphics, Fedora 28, Resolution and Display Issues

Did God make two great lights or did He make the great light two?

Am I ethically obligated to go into work on an off day if the reason is sudden?

How to stretch delimiters to envolve matrices inside of a kbordermatrix?

Why is superheterodyning better than direct conversion?

Can a novice safely splice in wire to lengthen 5V charging cable?

The following signatures were invalid: EXPKEYSIG 1397BC53640DB551

Take groceries in checked luggage

How to make `trap` know if the EXIT is after successful program finish or because of premature as an error or something

He got a vote 80% that of Emmanuel Macron’s

Road tyres vs "Street" tyres for charity ride on MTB Tandem

Working through the single responsibility principle (SRP) in Python when calls are expensive

"... to apply for a visa" or "... and applied for a visa"?

Single author papers against my advisor's will?

Why does the Event Horizon Telescope (EHT) not include telescopes from Africa, Asia or Australia?

How is simplicity better than precision and clarity in prose?

Hiding Certain Lines on Table

Make it rain characters

What LEGO pieces have "real-world" functionality?

Slither Like a Snake

Windows 10: How to Lock (not sleep) laptop on lid close?

How can I define good in a religion that claims no moral authority?

Would an alien lifeform be able to achieve space travel if lacking in vision?

Simulating Exploding Dice

Keeping a retro style to sci-fi spaceships?



Screen stuck on start



The 2019 Stack Overflow Developer Survey Results Are In
Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)
2019 Community Moderator Election ResultsCan't control brightness on HP Pav dv6t running Fedora 16Stuck on Fedora splash screen after OpenBox3/tint2 installHow to enable OpenGL rendering on Fedora 18 with an Intel Corporation 82852/855GM?Installing NVIDIA graphics driver for Optimus configurationFedora 20 stuck in Emergency ModeGotomeeting on Fedora - crashes often when I start sharing the screenWhat's NUL-bombing my console during shutdown?Fedora 26 KDE Plasma Desktop will not boot with external monitorFedora 28 server install failurei915 Graphics, Fedora 28, Resolution and Display Issues



.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;








0















Today I updated my computer to Fedora 28. Right after that every time I start my machine the start screen showing the Fedora icon remains.



Then I took to last option on (0-rescue-2d646b937ac4cd8bbdc1e26384CCC7c) 28 (Workstation edition) , now this says:



device descriptor read/64 error -110
SDB no catching mode found
assuming drive cache write through
etc/multipath.conf doesn't exist
you can run /sbin/mpathconf to create or modify /etc/multipath.conf


My graphics hardware / kernel driver:



[root@dhcppc2 mc]# lspci -k | grep -EA3 'VGA|3D|Display'
00:02.0 VGA compatible controller: Intel Corporation 82945G/GZ Integrated Graphics Controller (rev 02)
Subsystem: Elitegroup Computer Systems Device 2633
Kernel driver in use: i915
Kernel modules: i915









share|improve this question
























  • @sourcejedi first of all, in said link I couldn't find command. One command returned [mc@dhcppc2 ~]$ (lspci -nn | grep -i audio) 00:1b.0 Audio device [0403]: Intel Corporation NM10/ICH7 Family High Definition Audio Controller [8086:27d8] (rev 01)

    – Prabhjot Singh
    May 7 '18 at 12:57











  • unix.meta.stackexchange.com/questions/4853/… @sourcejedi I couldn't agree more.

    – Prabhjot Singh
    May 7 '18 at 19:31


















0















Today I updated my computer to Fedora 28. Right after that every time I start my machine the start screen showing the Fedora icon remains.



Then I took to last option on (0-rescue-2d646b937ac4cd8bbdc1e26384CCC7c) 28 (Workstation edition) , now this says:



device descriptor read/64 error -110
SDB no catching mode found
assuming drive cache write through
etc/multipath.conf doesn't exist
you can run /sbin/mpathconf to create or modify /etc/multipath.conf


My graphics hardware / kernel driver:



[root@dhcppc2 mc]# lspci -k | grep -EA3 'VGA|3D|Display'
00:02.0 VGA compatible controller: Intel Corporation 82945G/GZ Integrated Graphics Controller (rev 02)
Subsystem: Elitegroup Computer Systems Device 2633
Kernel driver in use: i915
Kernel modules: i915









share|improve this question
























  • @sourcejedi first of all, in said link I couldn't find command. One command returned [mc@dhcppc2 ~]$ (lspci -nn | grep -i audio) 00:1b.0 Audio device [0403]: Intel Corporation NM10/ICH7 Family High Definition Audio Controller [8086:27d8] (rev 01)

    – Prabhjot Singh
    May 7 '18 at 12:57











  • unix.meta.stackexchange.com/questions/4853/… @sourcejedi I couldn't agree more.

    – Prabhjot Singh
    May 7 '18 at 19:31














0












0








0


1






Today I updated my computer to Fedora 28. Right after that every time I start my machine the start screen showing the Fedora icon remains.



Then I took to last option on (0-rescue-2d646b937ac4cd8bbdc1e26384CCC7c) 28 (Workstation edition) , now this says:



device descriptor read/64 error -110
SDB no catching mode found
assuming drive cache write through
etc/multipath.conf doesn't exist
you can run /sbin/mpathconf to create or modify /etc/multipath.conf


My graphics hardware / kernel driver:



[root@dhcppc2 mc]# lspci -k | grep -EA3 'VGA|3D|Display'
00:02.0 VGA compatible controller: Intel Corporation 82945G/GZ Integrated Graphics Controller (rev 02)
Subsystem: Elitegroup Computer Systems Device 2633
Kernel driver in use: i915
Kernel modules: i915









share|improve this question
















Today I updated my computer to Fedora 28. Right after that every time I start my machine the start screen showing the Fedora icon remains.



Then I took to last option on (0-rescue-2d646b937ac4cd8bbdc1e26384CCC7c) 28 (Workstation edition) , now this says:



device descriptor read/64 error -110
SDB no catching mode found
assuming drive cache write through
etc/multipath.conf doesn't exist
you can run /sbin/mpathconf to create or modify /etc/multipath.conf


My graphics hardware / kernel driver:



[root@dhcppc2 mc]# lspci -k | grep -EA3 'VGA|3D|Display'
00:02.0 VGA compatible controller: Intel Corporation 82945G/GZ Integrated Graphics Controller (rev 02)
Subsystem: Elitegroup Computer Systems Device 2633
Kernel driver in use: i915
Kernel modules: i915






fedora






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Apr 10 at 8:19









sourcejedi

26k445114




26k445114










asked May 6 '18 at 15:19









Prabhjot SinghPrabhjot Singh

159213




159213












  • @sourcejedi first of all, in said link I couldn't find command. One command returned [mc@dhcppc2 ~]$ (lspci -nn | grep -i audio) 00:1b.0 Audio device [0403]: Intel Corporation NM10/ICH7 Family High Definition Audio Controller [8086:27d8] (rev 01)

    – Prabhjot Singh
    May 7 '18 at 12:57











  • unix.meta.stackexchange.com/questions/4853/… @sourcejedi I couldn't agree more.

    – Prabhjot Singh
    May 7 '18 at 19:31


















  • @sourcejedi first of all, in said link I couldn't find command. One command returned [mc@dhcppc2 ~]$ (lspci -nn | grep -i audio) 00:1b.0 Audio device [0403]: Intel Corporation NM10/ICH7 Family High Definition Audio Controller [8086:27d8] (rev 01)

    – Prabhjot Singh
    May 7 '18 at 12:57











  • unix.meta.stackexchange.com/questions/4853/… @sourcejedi I couldn't agree more.

    – Prabhjot Singh
    May 7 '18 at 19:31

















@sourcejedi first of all, in said link I couldn't find command. One command returned [mc@dhcppc2 ~]$ (lspci -nn | grep -i audio) 00:1b.0 Audio device [0403]: Intel Corporation NM10/ICH7 Family High Definition Audio Controller [8086:27d8] (rev 01)

– Prabhjot Singh
May 7 '18 at 12:57





@sourcejedi first of all, in said link I couldn't find command. One command returned [mc@dhcppc2 ~]$ (lspci -nn | grep -i audio) 00:1b.0 Audio device [0403]: Intel Corporation NM10/ICH7 Family High Definition Audio Controller [8086:27d8] (rev 01)

– Prabhjot Singh
May 7 '18 at 12:57













unix.meta.stackexchange.com/questions/4853/… @sourcejedi I couldn't agree more.

– Prabhjot Singh
May 7 '18 at 19:31






unix.meta.stackexchange.com/questions/4853/… @sourcejedi I couldn't agree more.

– Prabhjot Singh
May 7 '18 at 19:31











1 Answer
1






active

oldest

votes


















4














Interestingly, the Fedora install guide claims that this "usually means a problem with the graphical boot sequence; to solve this issue, you must disable graphical boot.". It is only talking about the graphical boot progress and icon - you can disable this and still use a graphical desktop like Gnome.




https://docs.fedoraproject.org/f28/install-guide/install/Troubleshooting.html#sect-trouble-after-graphical-boot



After you finish the installation and reboot your system for the first time, it is possible that the system stops responding during the graphical boot sequence, requiring a reset. In this case, the boot loader is displayed successfully, but selecting any entry and attempting to boot the system results in a halt. This usually means a problem with the graphical boot sequence; to solve this issue, you must disable graphical boot. To do this, temporarily alter the setting at boot time before changing it permanently.




In Fedora, you can do this by removing the rhgb boot option. The install manual includes a comprehensive explanation of how to test this temporarily, and then change it permanently.



(The linked version involves using su -. If you have not set a root password, use sudo su - instead).



For SO policy reasons I have paste-dumped it here, but the linked version has better formatting.




Trouble With the Graphical Boot Sequence



After you finish the installation and reboot your system for the first time, it is possible that the system stops responding during the graphical boot sequence, requiring a reset. In this case, the boot loader is displayed successfully, but selecting any entry and attempting to boot the system results in a halt. This usually means a problem with the graphical boot sequence; to solve this issue, you must disable graphical boot. To do this, temporarily alter the setting at boot time before changing it permanently.



Disabling Graphical Boot Temporarily



  1. Start your computer and wait until the boot loader menu appears. If you set your boot loader timeout period to 0, hold down the Esc key to access it.


  2. When the boot loader menu appears, use your cursor keys to highlight the entry you want to boot and press the e key to edit this entry’s options.


  3. In the list of options, find the kernel line - that is, the line beginning with the keyword linux (or, in some cases, linux16 or linuxefi). On this line, locate the rhgb option and delete it. The option may not be immediately visible; use the cursor keys to scroll up and down.


  4. Press F10 or Ctrl+X to boot your system with the edited options.


  5. If the system started successfully, you can log in normally. Then you will need to disable the graphical boot permanently - otherwise you will have to perform the previous procedure every time the system boots. To permanently change boot options, do the following.


Disabling Graphical Boot Permanently




  1. Log in to the root account using the su - command:



    $ su -


  2. Open the /etc/default/grub configuration file using a plain text editor such as vim.



  3. Within the grub file, locate the line beginning with GRUB_CMDLINE_LINUX. The line should look similar to the following:



    GRUB_CMDLINE_LINUX="rd.lvm.lv=rhel/root rd.md=0 rd.dm=0 vconsole.keymap=us $([ -x /usr/sbin/rhcrashkernel-param ] && /usr/sbin/rhcrashkernel-param || :) rd.luks=0 vconsole.font=latarcyrheb-sun16 rd.lvm.lv=vg_rhel/swap rhgb quiet"


    On this line, delete the rhgb option.



  4. Save the edited configuration file.



  5. Refresh the boot loader configuration by executing the following command:



    # grub2-mkconfig --output=/boot/grub2/grub.cfg


After you finish this procedure, you can reboot your computer. Fedora will not use the graphical boot sequence any more. If you wish to enable graphical boot, follow the same procedure, add the rhgb option to the GRUB_CMDLINE_LINUX line in the /etc/default/grub file and refresh the boot loader configuration again using the grub2-mkconfig command.



See the Fedora System Administrator’s Guide, available at http://docs.fedoraproject.org/, for more information about working with the GRUB2 boot loader.






share|improve this answer























    Your Answer








    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "106"
    ;
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function()
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled)
    StackExchange.using("snippets", function()
    createEditor();
    );

    else
    createEditor();

    );

    function createEditor()
    StackExchange.prepareEditor(
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: false,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    imageUploader:
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    ,
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    );



    );













    draft saved

    draft discarded


















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f442136%2fscreen-stuck-on-start%23new-answer', 'question_page');

    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    4














    Interestingly, the Fedora install guide claims that this "usually means a problem with the graphical boot sequence; to solve this issue, you must disable graphical boot.". It is only talking about the graphical boot progress and icon - you can disable this and still use a graphical desktop like Gnome.




    https://docs.fedoraproject.org/f28/install-guide/install/Troubleshooting.html#sect-trouble-after-graphical-boot



    After you finish the installation and reboot your system for the first time, it is possible that the system stops responding during the graphical boot sequence, requiring a reset. In this case, the boot loader is displayed successfully, but selecting any entry and attempting to boot the system results in a halt. This usually means a problem with the graphical boot sequence; to solve this issue, you must disable graphical boot. To do this, temporarily alter the setting at boot time before changing it permanently.




    In Fedora, you can do this by removing the rhgb boot option. The install manual includes a comprehensive explanation of how to test this temporarily, and then change it permanently.



    (The linked version involves using su -. If you have not set a root password, use sudo su - instead).



    For SO policy reasons I have paste-dumped it here, but the linked version has better formatting.




    Trouble With the Graphical Boot Sequence



    After you finish the installation and reboot your system for the first time, it is possible that the system stops responding during the graphical boot sequence, requiring a reset. In this case, the boot loader is displayed successfully, but selecting any entry and attempting to boot the system results in a halt. This usually means a problem with the graphical boot sequence; to solve this issue, you must disable graphical boot. To do this, temporarily alter the setting at boot time before changing it permanently.



    Disabling Graphical Boot Temporarily



    1. Start your computer and wait until the boot loader menu appears. If you set your boot loader timeout period to 0, hold down the Esc key to access it.


    2. When the boot loader menu appears, use your cursor keys to highlight the entry you want to boot and press the e key to edit this entry’s options.


    3. In the list of options, find the kernel line - that is, the line beginning with the keyword linux (or, in some cases, linux16 or linuxefi). On this line, locate the rhgb option and delete it. The option may not be immediately visible; use the cursor keys to scroll up and down.


    4. Press F10 or Ctrl+X to boot your system with the edited options.


    5. If the system started successfully, you can log in normally. Then you will need to disable the graphical boot permanently - otherwise you will have to perform the previous procedure every time the system boots. To permanently change boot options, do the following.


    Disabling Graphical Boot Permanently




    1. Log in to the root account using the su - command:



      $ su -


    2. Open the /etc/default/grub configuration file using a plain text editor such as vim.



    3. Within the grub file, locate the line beginning with GRUB_CMDLINE_LINUX. The line should look similar to the following:



      GRUB_CMDLINE_LINUX="rd.lvm.lv=rhel/root rd.md=0 rd.dm=0 vconsole.keymap=us $([ -x /usr/sbin/rhcrashkernel-param ] && /usr/sbin/rhcrashkernel-param || :) rd.luks=0 vconsole.font=latarcyrheb-sun16 rd.lvm.lv=vg_rhel/swap rhgb quiet"


      On this line, delete the rhgb option.



    4. Save the edited configuration file.



    5. Refresh the boot loader configuration by executing the following command:



      # grub2-mkconfig --output=/boot/grub2/grub.cfg


    After you finish this procedure, you can reboot your computer. Fedora will not use the graphical boot sequence any more. If you wish to enable graphical boot, follow the same procedure, add the rhgb option to the GRUB_CMDLINE_LINUX line in the /etc/default/grub file and refresh the boot loader configuration again using the grub2-mkconfig command.



    See the Fedora System Administrator’s Guide, available at http://docs.fedoraproject.org/, for more information about working with the GRUB2 boot loader.






    share|improve this answer



























      4














      Interestingly, the Fedora install guide claims that this "usually means a problem with the graphical boot sequence; to solve this issue, you must disable graphical boot.". It is only talking about the graphical boot progress and icon - you can disable this and still use a graphical desktop like Gnome.




      https://docs.fedoraproject.org/f28/install-guide/install/Troubleshooting.html#sect-trouble-after-graphical-boot



      After you finish the installation and reboot your system for the first time, it is possible that the system stops responding during the graphical boot sequence, requiring a reset. In this case, the boot loader is displayed successfully, but selecting any entry and attempting to boot the system results in a halt. This usually means a problem with the graphical boot sequence; to solve this issue, you must disable graphical boot. To do this, temporarily alter the setting at boot time before changing it permanently.




      In Fedora, you can do this by removing the rhgb boot option. The install manual includes a comprehensive explanation of how to test this temporarily, and then change it permanently.



      (The linked version involves using su -. If you have not set a root password, use sudo su - instead).



      For SO policy reasons I have paste-dumped it here, but the linked version has better formatting.




      Trouble With the Graphical Boot Sequence



      After you finish the installation and reboot your system for the first time, it is possible that the system stops responding during the graphical boot sequence, requiring a reset. In this case, the boot loader is displayed successfully, but selecting any entry and attempting to boot the system results in a halt. This usually means a problem with the graphical boot sequence; to solve this issue, you must disable graphical boot. To do this, temporarily alter the setting at boot time before changing it permanently.



      Disabling Graphical Boot Temporarily



      1. Start your computer and wait until the boot loader menu appears. If you set your boot loader timeout period to 0, hold down the Esc key to access it.


      2. When the boot loader menu appears, use your cursor keys to highlight the entry you want to boot and press the e key to edit this entry’s options.


      3. In the list of options, find the kernel line - that is, the line beginning with the keyword linux (or, in some cases, linux16 or linuxefi). On this line, locate the rhgb option and delete it. The option may not be immediately visible; use the cursor keys to scroll up and down.


      4. Press F10 or Ctrl+X to boot your system with the edited options.


      5. If the system started successfully, you can log in normally. Then you will need to disable the graphical boot permanently - otherwise you will have to perform the previous procedure every time the system boots. To permanently change boot options, do the following.


      Disabling Graphical Boot Permanently




      1. Log in to the root account using the su - command:



        $ su -


      2. Open the /etc/default/grub configuration file using a plain text editor such as vim.



      3. Within the grub file, locate the line beginning with GRUB_CMDLINE_LINUX. The line should look similar to the following:



        GRUB_CMDLINE_LINUX="rd.lvm.lv=rhel/root rd.md=0 rd.dm=0 vconsole.keymap=us $([ -x /usr/sbin/rhcrashkernel-param ] && /usr/sbin/rhcrashkernel-param || :) rd.luks=0 vconsole.font=latarcyrheb-sun16 rd.lvm.lv=vg_rhel/swap rhgb quiet"


        On this line, delete the rhgb option.



      4. Save the edited configuration file.



      5. Refresh the boot loader configuration by executing the following command:



        # grub2-mkconfig --output=/boot/grub2/grub.cfg


      After you finish this procedure, you can reboot your computer. Fedora will not use the graphical boot sequence any more. If you wish to enable graphical boot, follow the same procedure, add the rhgb option to the GRUB_CMDLINE_LINUX line in the /etc/default/grub file and refresh the boot loader configuration again using the grub2-mkconfig command.



      See the Fedora System Administrator’s Guide, available at http://docs.fedoraproject.org/, for more information about working with the GRUB2 boot loader.






      share|improve this answer

























        4












        4








        4







        Interestingly, the Fedora install guide claims that this "usually means a problem with the graphical boot sequence; to solve this issue, you must disable graphical boot.". It is only talking about the graphical boot progress and icon - you can disable this and still use a graphical desktop like Gnome.




        https://docs.fedoraproject.org/f28/install-guide/install/Troubleshooting.html#sect-trouble-after-graphical-boot



        After you finish the installation and reboot your system for the first time, it is possible that the system stops responding during the graphical boot sequence, requiring a reset. In this case, the boot loader is displayed successfully, but selecting any entry and attempting to boot the system results in a halt. This usually means a problem with the graphical boot sequence; to solve this issue, you must disable graphical boot. To do this, temporarily alter the setting at boot time before changing it permanently.




        In Fedora, you can do this by removing the rhgb boot option. The install manual includes a comprehensive explanation of how to test this temporarily, and then change it permanently.



        (The linked version involves using su -. If you have not set a root password, use sudo su - instead).



        For SO policy reasons I have paste-dumped it here, but the linked version has better formatting.




        Trouble With the Graphical Boot Sequence



        After you finish the installation and reboot your system for the first time, it is possible that the system stops responding during the graphical boot sequence, requiring a reset. In this case, the boot loader is displayed successfully, but selecting any entry and attempting to boot the system results in a halt. This usually means a problem with the graphical boot sequence; to solve this issue, you must disable graphical boot. To do this, temporarily alter the setting at boot time before changing it permanently.



        Disabling Graphical Boot Temporarily



        1. Start your computer and wait until the boot loader menu appears. If you set your boot loader timeout period to 0, hold down the Esc key to access it.


        2. When the boot loader menu appears, use your cursor keys to highlight the entry you want to boot and press the e key to edit this entry’s options.


        3. In the list of options, find the kernel line - that is, the line beginning with the keyword linux (or, in some cases, linux16 or linuxefi). On this line, locate the rhgb option and delete it. The option may not be immediately visible; use the cursor keys to scroll up and down.


        4. Press F10 or Ctrl+X to boot your system with the edited options.


        5. If the system started successfully, you can log in normally. Then you will need to disable the graphical boot permanently - otherwise you will have to perform the previous procedure every time the system boots. To permanently change boot options, do the following.


        Disabling Graphical Boot Permanently




        1. Log in to the root account using the su - command:



          $ su -


        2. Open the /etc/default/grub configuration file using a plain text editor such as vim.



        3. Within the grub file, locate the line beginning with GRUB_CMDLINE_LINUX. The line should look similar to the following:



          GRUB_CMDLINE_LINUX="rd.lvm.lv=rhel/root rd.md=0 rd.dm=0 vconsole.keymap=us $([ -x /usr/sbin/rhcrashkernel-param ] && /usr/sbin/rhcrashkernel-param || :) rd.luks=0 vconsole.font=latarcyrheb-sun16 rd.lvm.lv=vg_rhel/swap rhgb quiet"


          On this line, delete the rhgb option.



        4. Save the edited configuration file.



        5. Refresh the boot loader configuration by executing the following command:



          # grub2-mkconfig --output=/boot/grub2/grub.cfg


        After you finish this procedure, you can reboot your computer. Fedora will not use the graphical boot sequence any more. If you wish to enable graphical boot, follow the same procedure, add the rhgb option to the GRUB_CMDLINE_LINUX line in the /etc/default/grub file and refresh the boot loader configuration again using the grub2-mkconfig command.



        See the Fedora System Administrator’s Guide, available at http://docs.fedoraproject.org/, for more information about working with the GRUB2 boot loader.






        share|improve this answer













        Interestingly, the Fedora install guide claims that this "usually means a problem with the graphical boot sequence; to solve this issue, you must disable graphical boot.". It is only talking about the graphical boot progress and icon - you can disable this and still use a graphical desktop like Gnome.




        https://docs.fedoraproject.org/f28/install-guide/install/Troubleshooting.html#sect-trouble-after-graphical-boot



        After you finish the installation and reboot your system for the first time, it is possible that the system stops responding during the graphical boot sequence, requiring a reset. In this case, the boot loader is displayed successfully, but selecting any entry and attempting to boot the system results in a halt. This usually means a problem with the graphical boot sequence; to solve this issue, you must disable graphical boot. To do this, temporarily alter the setting at boot time before changing it permanently.




        In Fedora, you can do this by removing the rhgb boot option. The install manual includes a comprehensive explanation of how to test this temporarily, and then change it permanently.



        (The linked version involves using su -. If you have not set a root password, use sudo su - instead).



        For SO policy reasons I have paste-dumped it here, but the linked version has better formatting.




        Trouble With the Graphical Boot Sequence



        After you finish the installation and reboot your system for the first time, it is possible that the system stops responding during the graphical boot sequence, requiring a reset. In this case, the boot loader is displayed successfully, but selecting any entry and attempting to boot the system results in a halt. This usually means a problem with the graphical boot sequence; to solve this issue, you must disable graphical boot. To do this, temporarily alter the setting at boot time before changing it permanently.



        Disabling Graphical Boot Temporarily



        1. Start your computer and wait until the boot loader menu appears. If you set your boot loader timeout period to 0, hold down the Esc key to access it.


        2. When the boot loader menu appears, use your cursor keys to highlight the entry you want to boot and press the e key to edit this entry’s options.


        3. In the list of options, find the kernel line - that is, the line beginning with the keyword linux (or, in some cases, linux16 or linuxefi). On this line, locate the rhgb option and delete it. The option may not be immediately visible; use the cursor keys to scroll up and down.


        4. Press F10 or Ctrl+X to boot your system with the edited options.


        5. If the system started successfully, you can log in normally. Then you will need to disable the graphical boot permanently - otherwise you will have to perform the previous procedure every time the system boots. To permanently change boot options, do the following.


        Disabling Graphical Boot Permanently




        1. Log in to the root account using the su - command:



          $ su -


        2. Open the /etc/default/grub configuration file using a plain text editor such as vim.



        3. Within the grub file, locate the line beginning with GRUB_CMDLINE_LINUX. The line should look similar to the following:



          GRUB_CMDLINE_LINUX="rd.lvm.lv=rhel/root rd.md=0 rd.dm=0 vconsole.keymap=us $([ -x /usr/sbin/rhcrashkernel-param ] && /usr/sbin/rhcrashkernel-param || :) rd.luks=0 vconsole.font=latarcyrheb-sun16 rd.lvm.lv=vg_rhel/swap rhgb quiet"


          On this line, delete the rhgb option.



        4. Save the edited configuration file.



        5. Refresh the boot loader configuration by executing the following command:



          # grub2-mkconfig --output=/boot/grub2/grub.cfg


        After you finish this procedure, you can reboot your computer. Fedora will not use the graphical boot sequence any more. If you wish to enable graphical boot, follow the same procedure, add the rhgb option to the GRUB_CMDLINE_LINUX line in the /etc/default/grub file and refresh the boot loader configuration again using the grub2-mkconfig command.



        See the Fedora System Administrator’s Guide, available at http://docs.fedoraproject.org/, for more information about working with the GRUB2 boot loader.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered May 7 '18 at 12:58









        sourcejedisourcejedi

        26k445114




        26k445114



























            draft saved

            draft discarded
















































            Thanks for contributing an answer to Unix & Linux Stack Exchange!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid


            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.

            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f442136%2fscreen-stuck-on-start%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            getting Checkpoint VPN SSL Network Extender working in the command lineHow to connect to CheckPoint VPN on Ubuntu 18.04LTS?Will the Linux ( red-hat ) Open VPNC Client connect to checkpoint or nortel VPN gateways?VPN client for linux machine + support checkpoint gatewayVPN SSL Network Extender in FirefoxLinux Checkpoint SNX tool configuration issuesCheck Point - Connect under Linux - snx + OTPSNX VPN Ububuntu 18.XXUsing Checkpoint VPN SSL Network Extender CLI with certificateVPN with network manager (nm-applet) is not workingWill the Linux ( red-hat ) Open VPNC Client connect to checkpoint or nortel VPN gateways?VPN client for linux machine + support checkpoint gatewayImport VPN config files to NetworkManager from command lineTrouble connecting to VPN using network-manager, while command line worksStart a VPN connection with PPTP protocol on command linestarting a docker service daemon breaks the vpn networkCan't connect to vpn with Network-managerVPN SSL Network Extender in FirefoxUsing Checkpoint VPN SSL Network Extender CLI with certificate

            Cannot Extend partition with GParted The 2019 Stack Overflow Developer Survey Results Are In Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern) 2019 Community Moderator Election ResultsCan't increase partition size with GParted?GParted doesn't recognize the unallocated space after my current partitionWhat is the best way to add unallocated space located before to Ubuntu 12.04 partition with GParted live?I can't figure out how to extend my Arch home partition into free spaceGparted Linux Mint 18.1 issueTrying to extend but swap partition is showing as Unknown in Gparted, shows proper from fdiskRearrange partitions in gparted to extend a partitionUnable to extend partition even though unallocated space is next to it using GPartedAllocate free space to root partitiongparted: how to merge unallocated space with a partition

            NetworkManager fails with “Could not find source connection”Trouble connecting to VPN using network-manager, while command line worksHow can I be notified about state changes to a VPN adapterBacktrack 5 R3 - Refuses to connect to VPNFeed all traffic through OpenVPN for a specific network namespace onlyRun daemon on startup in Debian once openvpn connection establishedpfsense tcp connection between openvpn and lan is brokenInternet connection problem with web browsers onlyWhy does NetworkManager explicitly support tun/tap devices?Browser issues with VPNTwo IP addresses assigned to the same network card - OpenVPN issues?Cannot connect to WiFi with nmcli, although secrets are provided