Installing Qubes 3.1 : boot process freezes after Qubes logo blinks












0















After burning Qubes iso on a USB stick using dd I boot it in UEFI mode and I got a problem with the following symptom :



If I select Verify source and install Qubes the process freezes after the test passes.
If I select Install Qubes I got this :



Ignoring BGRT : invalid status 0 (expected 1)
mce : unable to init device /dev/mcelog (rc:-16)
/etc/vconsole.cong line 1: 1=: command not found
/etc/vconsole.cong line 1: 1=: command not found
sd 4:0:0:0:[sdb] no caching mode page found
sd 4:0:0:0:[sdb] assuming drive cache : write through
mount: /dev/sdb is write protected, mounting read-only


And then the booting process freezes completely and I can only reboot with ctrl+alt+del. I have to add that the Qubes graphical logo blinks very briefly before it comes back to the command line and freezes.



Any idea on what is happening ? Is there a way to activate a verbose mode so there is more detail on the failure reason ?










share|improve this question














bumped to the homepage by Community 18 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
















  • It may be totally unrelated, but that file /etc/vconsole.conf, it looks like there might be some variables in there being set, but with the variable name prepended by a $ (e.g. $FONT=).

    – Kusalananda
    Jan 1 '17 at 18:46
















0















After burning Qubes iso on a USB stick using dd I boot it in UEFI mode and I got a problem with the following symptom :



If I select Verify source and install Qubes the process freezes after the test passes.
If I select Install Qubes I got this :



Ignoring BGRT : invalid status 0 (expected 1)
mce : unable to init device /dev/mcelog (rc:-16)
/etc/vconsole.cong line 1: 1=: command not found
/etc/vconsole.cong line 1: 1=: command not found
sd 4:0:0:0:[sdb] no caching mode page found
sd 4:0:0:0:[sdb] assuming drive cache : write through
mount: /dev/sdb is write protected, mounting read-only


And then the booting process freezes completely and I can only reboot with ctrl+alt+del. I have to add that the Qubes graphical logo blinks very briefly before it comes back to the command line and freezes.



Any idea on what is happening ? Is there a way to activate a verbose mode so there is more detail on the failure reason ?










share|improve this question














bumped to the homepage by Community 18 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
















  • It may be totally unrelated, but that file /etc/vconsole.conf, it looks like there might be some variables in there being set, but with the variable name prepended by a $ (e.g. $FONT=).

    – Kusalananda
    Jan 1 '17 at 18:46














0












0








0








After burning Qubes iso on a USB stick using dd I boot it in UEFI mode and I got a problem with the following symptom :



If I select Verify source and install Qubes the process freezes after the test passes.
If I select Install Qubes I got this :



Ignoring BGRT : invalid status 0 (expected 1)
mce : unable to init device /dev/mcelog (rc:-16)
/etc/vconsole.cong line 1: 1=: command not found
/etc/vconsole.cong line 1: 1=: command not found
sd 4:0:0:0:[sdb] no caching mode page found
sd 4:0:0:0:[sdb] assuming drive cache : write through
mount: /dev/sdb is write protected, mounting read-only


And then the booting process freezes completely and I can only reboot with ctrl+alt+del. I have to add that the Qubes graphical logo blinks very briefly before it comes back to the command line and freezes.



Any idea on what is happening ? Is there a way to activate a verbose mode so there is more detail on the failure reason ?










share|improve this question














After burning Qubes iso on a USB stick using dd I boot it in UEFI mode and I got a problem with the following symptom :



If I select Verify source and install Qubes the process freezes after the test passes.
If I select Install Qubes I got this :



Ignoring BGRT : invalid status 0 (expected 1)
mce : unable to init device /dev/mcelog (rc:-16)
/etc/vconsole.cong line 1: 1=: command not found
/etc/vconsole.cong line 1: 1=: command not found
sd 4:0:0:0:[sdb] no caching mode page found
sd 4:0:0:0:[sdb] assuming drive cache : write through
mount: /dev/sdb is write protected, mounting read-only


And then the booting process freezes completely and I can only reboot with ctrl+alt+del. I have to add that the Qubes graphical logo blinks very briefly before it comes back to the command line and freezes.



Any idea on what is happening ? Is there a way to activate a verbose mode so there is more detail on the failure reason ?







system-installation qubes






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Jan 8 '16 at 2:10









ChiseledAbsChiseledAbs

84731432




84731432





bumped to the homepage by Community 18 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







bumped to the homepage by Community 18 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.















  • It may be totally unrelated, but that file /etc/vconsole.conf, it looks like there might be some variables in there being set, but with the variable name prepended by a $ (e.g. $FONT=).

    – Kusalananda
    Jan 1 '17 at 18:46



















  • It may be totally unrelated, but that file /etc/vconsole.conf, it looks like there might be some variables in there being set, but with the variable name prepended by a $ (e.g. $FONT=).

    – Kusalananda
    Jan 1 '17 at 18:46

















It may be totally unrelated, but that file /etc/vconsole.conf, it looks like there might be some variables in there being set, but with the variable name prepended by a $ (e.g. $FONT=).

– Kusalananda
Jan 1 '17 at 18:46





It may be totally unrelated, but that file /etc/vconsole.conf, it looks like there might be some variables in there being set, but with the variable name prepended by a $ (e.g. $FONT=).

– Kusalananda
Jan 1 '17 at 18:46










1 Answer
1






active

oldest

votes


















0














As there is some common bug in UEFI implementation, you may find workaround in this article.



Press Ctrl+Alt+F2 for shell, F3 for log or F4 for storage log. I assume it may be a kernel-related issue, too. Consider making a newer Qubes 3.2 install using dd or try rufus. You can still look on hardware compatibility list.






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%2f253997%2finstalling-qubes-3-1-boot-process-freezes-after-qubes-logo-blinks%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









    0














    As there is some common bug in UEFI implementation, you may find workaround in this article.



    Press Ctrl+Alt+F2 for shell, F3 for log or F4 for storage log. I assume it may be a kernel-related issue, too. Consider making a newer Qubes 3.2 install using dd or try rufus. You can still look on hardware compatibility list.






    share|improve this answer






























      0














      As there is some common bug in UEFI implementation, you may find workaround in this article.



      Press Ctrl+Alt+F2 for shell, F3 for log or F4 for storage log. I assume it may be a kernel-related issue, too. Consider making a newer Qubes 3.2 install using dd or try rufus. You can still look on hardware compatibility list.






      share|improve this answer




























        0












        0








        0







        As there is some common bug in UEFI implementation, you may find workaround in this article.



        Press Ctrl+Alt+F2 for shell, F3 for log or F4 for storage log. I assume it may be a kernel-related issue, too. Consider making a newer Qubes 3.2 install using dd or try rufus. You can still look on hardware compatibility list.






        share|improve this answer















        As there is some common bug in UEFI implementation, you may find workaround in this article.



        Press Ctrl+Alt+F2 for shell, F3 for log or F4 for storage log. I assume it may be a kernel-related issue, too. Consider making a newer Qubes 3.2 install using dd or try rufus. You can still look on hardware compatibility list.







        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited Jan 1 '17 at 18:37

























        answered Jan 1 '17 at 18:07









        Tomáš PánikTomáš Pánik

        36918




        36918






























            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%2f253997%2finstalling-qubes-3-1-boot-process-freezes-after-qubes-logo-blinks%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

            Accessing regular linux commands in Huawei's Dopra Linux

            Can't connect RFCOMM socket: Host is down

            Kernel panic - not syncing: Fatal Exception in Interrupt