• [6.10.0-rc5] Boot to GUI not working


    casperse
    • Minor

    Hi All

     

    I had problems with a blinking cursor on the stable release of Unraid 6.9 but after upgrading to 6.10.rc4 it worked again!

    Now I have upgraded to Unraid 6.10rc5 and I get the dreaded cursor again 😞

    No Firefox UI

     

    I have tested this on a 1080P monitor with a HDMI cable

    And another 4K monitor and another cable and result is the same this is what I see on both screen:

     

    Hard to explain I made a video: (Sorry for the shaken picture)

     

    Diag log attached below

     

     

    UI-diagnostics-20220430-1151.zip




    User Feedback

    Recommended Comments

    Nice video. I’ve captured the moment it moves from a normal boot to the blank screen.CB9EEAFC-1C4F-437A-8C2B-121744BAAA6F.thumb.jpeg.03fe46175974658201820571fff29e04.jpeg

    Link to comment
    2 hours ago, danioj said:

    Nice video. I’ve captured the moment it moves from a normal boot to the blank screen.CB9EEAFC-1C4F-437A-8C2B-121744BAAA6F.thumb.jpeg.03fe46175974658201820571fff29e04.jpeg

    Great! Thanks - But can anyone tell me what does this mean? 😀

    I have no fancy boot settings just GUI as preferred boot
    image.thumb.png.9b535a20136e4fb3fcdd09858477b9a3.png

    Link to comment

    Those error would be from a plugin.  Presumably VM Backup (or something else VM related)

    Link to comment

    I have actually removed that before didn't do any difference?

    Also between it working and it stopped working no changes was made?

     

    Anyway to stop all script during boot - would safe boot do that? (Would be easy thing to check then?)

    Link to comment
    5 hours ago, casperse said:

    would safe boot do that

    Safe Boot stops any plugins from being installed.

    Link to comment
    On 5/2/2022 at 5:38 PM, itimpi said:

    Safe Boot stops any plugins from being installed.

    But I can se that no plugin in safe mode also stops the GUI?

     

    So how to boot with GUI and not load any plugin to verify if a plugin is causing this error?

    Link to comment
    Just now, casperse said:

    But I can se that no plugin in safe mode also stops the GUI?

     

    Why would you think that?  Safe mode only stops plugins from installing and has no effect on the GUI itself

    Link to comment
    1 minute ago, casperse said:

    But I can se that no plugin in safe mode also stops the GUI?

     

    So how to boot with GUI and not load any plugin to verify if a plugin is causing this error?


    Safe mode does not stop the GUI running unless your system NEEDS a particular plugin to get GUI mode to work.    
     

    You can also stop plugins running by renaming the .plg files on the flash drive to have a different file extension.   This can allow you to experiment with different combinations of plugins being loaded.

    Link to comment
    casperse

    Posted (edited)

    On 5/7/2022 at 7:09 PM, itimpi said:


    Safe mode does not stop the GUI running unless your system NEEDS a particular plugin to get GUI mode to work.    
     

    You can also stop plugins running by renaming the .plg files on the flash drive to have a different file extension.   This can allow you to experiment with different combinations of plugins being loaded.

     

    Ok so after updating to RC7 I did some more testing and I found that if I change the BIOS Display output

    From IGFX output to my P2000 Graphic card then after showing all the boot text (See video above) I actual get to the login screen of Unraid and it works!

     

    So IGFX always worked before? - I am not using it for anything like transcoding

    Any idea why IGFX doesn't work anymore?

     

    Update: Testing no plugins did NOT make any difference! 😞

     

    Edited by casperse
    Link to comment
    1 minute ago, casperse said:

    So IGFX always worked before? - I am not using it for anything like transcoding

    Any idea why IGFX doesn't work anymore?


    No idea I am afraid - maybe somebody else will have an idea.  

    • Like 1
    Link to comment
    42 minutes ago, casperse said:

     

    Ok so after updating to RC7 I did some more testing and I found that if I change the BIOS Display output

    From IGFX output to my P2000 Graphic card then after showing all the boot text (See video above) I actual get to the login screen of Unraid and it works!

     

    So IGFX always worked before? - I am not using it for anything like transcoding

    Any idea why IGFX doesn't work anymore?

     

    Update: Testing no plugins did NOT make any difference! 😞

     

    in 6.10rc2+ i915 driver is loaded by default.

     

    try blacklisting i915.

     

    root@computenode:~# cat /boot/config/modprobe.d/i915.conf 
    blacklist i915
    root@computenode:~# 

     

    • Like 1
    Link to comment
    casperse

    Posted (edited)

    53 minutes ago, SimonF said:

    in 6.10rc2+ i915 driver is loaded by default.

     

    try blacklisting i915.

     

    root@computenode:~# cat /boot/config/modprobe.d/i915.conf 
    blacklist i915
    root@computenode:~# 

     

    Thanks I will try that!

     

    UPDATE: I dont have any file in that dir?

    image.png.58c7596bdfef7fcc425f3303bb30336a.png


    Also I would really like to clean up any old configuration like stub's!
    Can I just delete them ? (I can see that the stubs are for some old netcard not the IGFX!)

    Guess I need to keep the append.....?
    image.thumb.png.75baf9f468ea98f3ea28637e6120f4fc.png

    Edited by casperse
    Link to comment
    SimonF

    Posted (edited)

    24 minutes ago, casperse said:

    UPDATE: I dont have any file in that dir?

    Just create it and add in blacklist i915

     

    append needs to stay and if you dont need them you can remove the stubs.

     

    You will need to reboot for the blacklist to take effect.

    Edited by SimonF
    Link to comment
    On 5/8/2022 at 9:53 PM, SimonF said:

    Just create it and add in blacklist i915

     

    append needs to stay and if you dont need them you can remove the stubs.

     

    You will need to reboot for the blacklist to take effect.

     

    I just checked my "GO file" and I found this very old setup for the GFX (Have not been a problem before, but all the updates might have broken this from the "old days") should I remove everything below the line #Setup**** ???
     

    root@PLEXZONE:/boot# cat /boot/config/go
    #!/bin/bash
    # Start the Management Utility
    /usr/local/sbin/emhttp &
    
    #Setup drivers for iGPU hardware transcoding
    modprobe i915
    chown -R nobody:users /dev/dri
    chmod -R 777 /dev/dri
    root@PLEXZONE:/boot# 


    Yes I have created a file named i915.conf 

    and in it I have the line:

    blacklist i915

     

    I will reboot it when possible 🙂

     

    Link to comment
    1 hour ago, casperse said:

     

    I just checked my "GO file" and I found this very old setup for the GFX (Have not been a problem before, but all the updates might have broken this from the "old days") should I remove everything below the line #Setup**** ???
     

    root@PLEXZONE:/boot# cat /boot/config/go
    #!/bin/bash
    # Start the Management Utility
    /usr/local/sbin/emhttp &
    
    #Setup drivers for iGPU hardware transcoding
    modprobe i915
    chown -R nobody:users /dev/dri
    chmod -R 777 /dev/dri
    root@PLEXZONE:/boot# 


    Yes I have created a file named i915.conf 

    and in it I have the line:

    blacklist i915

     

    I will reboot it when possible 🙂

     

    Do you use hardware trans-coding in plex? if you are blacklist will break this.

     

    These are from the older 6.9.x release notes.

     

    GPU Driver Integration
    Unraid OS now includes selected in-tree GPU drivers: ast (Aspeed), i915 (Intel), amdgpu and radeon (AMD).  For backward compatibility, these drivers are blacklisted by default via corresponding conf files in /etc/modprobe.d:
    
    /etc/modprobe.d/ast.conf
    /etc/modprobe.d/i915.conf
    /etc/modprobe.d/amdgpu.conf
    /etc/modprobe.d/radeon.conf
    Each of these files has a single line that blacklists the driver, preventing it from being loaded by the Linux kernel.
    
    It is possible to override the settings in these files by creating a custom conf file in the config/modprobe.d directory on your USB flash boot device.  For example, to un-blacklist the amdgpu driver create an empty file by typing this command in a Terminal session:
    
    touch /boot/config/modprobe.d/amdgpu.conf
    This only needs to be done once, it does not need to be added to your go script.
    
    
    In 6.9.1, if your go script contains a modprobe command for your GPU and/or a command to fix the permissions on /dev/dri, you should remove them:
    
    modprobe amdgpu
    chmod -R 777 /dev/dri

     

    Link to comment
    11 hours ago, SimonF said:

    Do you use hardware trans-coding in plex? if you are blacklist will break this.

     

    These are from the older 6.9.x release notes.

     

    GPU Driver Integration
    Unraid OS now includes selected in-tree GPU drivers: ast (Aspeed), i915 (Intel), amdgpu and radeon (AMD).  For backward compatibility, these drivers are blacklisted by default via corresponding conf files in /etc/modprobe.d:
    
    /etc/modprobe.d/ast.conf
    /etc/modprobe.d/i915.conf
    /etc/modprobe.d/amdgpu.conf
    /etc/modprobe.d/radeon.conf
    Each of these files has a single line that blacklists the driver, preventing it from being loaded by the Linux kernel.
    
    It is possible to override the settings in these files by creating a custom conf file in the config/modprobe.d directory on your USB flash boot device.  For example, to un-blacklist the amdgpu driver create an empty file by typing this command in a Terminal session:
    
    touch /boot/config/modprobe.d/amdgpu.conf
    This only needs to be done once, it does not need to be added to your go script.
    
    
    In 6.9.1, if your go script contains a modprobe command for your GPU and/or a command to fix the permissions on /dev/dri, you should remove them:
    
    modprobe amdgpu
    chmod -R 777 /dev/dri

     

    Sorry maybee stupid Q - I am a little confused 🙂

     

     

    I use my P2000 Nvidia graphic card for Plex transcoding works 100%

    My plan was to maybe use the IGFX on a Windows 10 VM for video editing?

     

    So I think I can remove the lines with the i915 from the GO file

    Not sure if blacklisting the i915 will prohibit me from using it in the VM, but it shouldn't stop the P2000 transcoding should it? 

    Link to comment
    On 5/10/2022 at 8:48 PM, SimonF said:

    Do you use hardware trans-coding in plex? if you are blacklist will break this.

     

    These are from the older 6.9.x release notes.

     

    GPU Driver Integration
    Unraid OS now includes selected in-tree GPU drivers: ast (Aspeed), i915 (Intel), amdgpu and radeon (AMD).  For backward compatibility, these drivers are blacklisted by default via corresponding conf files in /etc/modprobe.d:
    
    /etc/modprobe.d/ast.conf
    /etc/modprobe.d/i915.conf
    /etc/modprobe.d/amdgpu.conf
    /etc/modprobe.d/radeon.conf
    Each of these files has a single line that blacklists the driver, preventing it from being loaded by the Linux kernel.
    
    It is possible to override the settings in these files by creating a custom conf file in the config/modprobe.d directory on your USB flash boot device.  For example, to un-blacklist the amdgpu driver create an empty file by typing this command in a Terminal session:
    
    touch /boot/config/modprobe.d/amdgpu.conf
    This only needs to be done once, it does not need to be added to your go script.
    
    
    In 6.9.1, if your go script contains a modprobe command for your GPU and/or a command to fix the permissions on /dev/dri, you should remove them:
    
    modprobe amdgpu
    chmod -R 777 /dev/dri

     

     

    I created the file:

    image.png.66d02484e017b1b503ba6d7791f01b46.png

     

    Ant when I use the IGFX it stops just before the login promt with a blinking cursor on the screen like in the video?
    But if I add any graphic card to the server (Dont have a free PCI slot for this) then it works!

    Something breaks the internal GPU when launching the UI in firefox?

    All the loading is shown fine on the screen

     

    Link to comment
    On 5/13/2022 at 2:38 PM, casperse said:

    Ant when I use the IGFX it stops just before the login promt with a blinking cursor on the screen like in the video?

    Ok so looks like we need to remove the blacklist. Did you try safe boot?

    Link to comment
    On 5/8/2022 at 11:39 AM, SimonF said:

    in 6.10rc2+ i915 driver is loaded by default.

     

    try blacklisting i915.

     

    root@computenode:~# cat /boot/config/modprobe.d/i915.conf 
    blacklist i915
    root@computenode:~# 

     

    Thank you, @SimonF!  I recently upgraded from 6.9 to 6.10.2, and was not understanding why I couldn't get the GUI to show up locally.  I have an Intel HD 530 iGPU (which I totally forgot about) and an Nvidia GT730. 

     

    I have my monitor hooked up to the Nvidia card, so when booting up I saw everything loading fine.. then right after loading samba the screen blanks and I just see a blinking underline cursor.  Even in GUI w/safe mode.  So I missed this note about the i915 driver being loaded by default. 

     

    I am not using the i915 for anything (no transcoding, etc).  So I'm happy with this solution.  Thanks!

    • Like 1
    Link to comment


    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.


  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.


    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.