Results 1 to 6 of 6

Thread: OpenSuse 42.3 - Blank display on boot after update (no Radeon driver?)

  1. #1

    Default OpenSuse 42.3 - Blank display on boot after update (no Radeon driver?)

    Okay, weird one. I updated from 42.1 to 42.3 at the weekend. I had to perform the FGLRX removal instructions to use the Radeon driver instead. All was working well last night (was flying around in Flightgear happily). During that session, a security update was installed. On startup today, no display and no access to text console via CTRL+Fx. Reboot using Failsafe mode and X is failing.

    Following the 'Setup AMD display website', modprobe radeon returns 'modprobe: ERROR: could not insert 'radeon': Invalid argument

    lsmod | grep radeon returns nothing

    dracut -H --force returns lots of 'Possible missing firmware: "radeon/*" lines

    Has my radeon driver been removed by the update? The files are still in the /lib/firmware/radeon directory, however perhaps they are incompatible with a new kernel?

    lspci says my card is a Radeon HD 6800 Series, which is correct for the radeon driver and as I said, it was working until today.

  2. #2

    Default Re: OpenSuse 42.3 - Blank display on boot after update (no Radeon driver?)

    Followup....

    Essentially I am getting the same symptons as per this old Debian post:

    https://lists.debian.org/debian-kern.../msg00013.html

    At command line, modprobe radeon modeset=1 works. Startx then works.

    I created a new 50-radeon.conf file in /etc/modprobe.d with options radeon modeset=1 inside.

    Rebooted....same problem. So as per the Debian issue, unless I put modeset=0 into Grub, Suse boots with a blank screen.

  3. #3

    Default Re: OpenSuse 42.3 - Blank display on boot after update (no Radeon driver?)

    Quote Originally Posted by DorsetBlue View Post
    Followup....

    Essentially I am getting the same symptons as per this old Debian post:

    https://lists.debian.org/debian-kern.../msg00013.html

    At command line, modprobe radeon modeset=1 works. Startx then works.

    I created a new 50-radeon.conf file in /etc/modprobe.d with options radeon modeset=1 inside.

    Rebooted....same problem. So as per the Debian issue, unless I put modeset=0 into Grub, Suse boots with a blank screen.
    Did you run dracut after creating the 50-radeon.conf file?

  4. #4
    Join Date
    Feb 2010
    Location
    Germany
    Posts
    4,576

    Lightbulb Re: OpenSuse 42.3 - Blank display on boot after update (no Radeon driver?)

    @DorsetBlue:
    Please follow the steps detailed in the openSUSE SDB Radeon: <https://en.opensuse.org/SDB:Radeon>.

    It may be, that the fglrx installation had black-listed the radeon driver (by default part of the Kernel).

  5. #5

    Default Re: OpenSuse 42.3 - Blank display on boot after update (no Radeon driver?)

    Quote Originally Posted by dcurtisfra View Post
    @DorsetBlue:
    Please follow the steps detailed in the openSUSE SDB Radeon: <https://en.opensuse.org/SDB:Radeon>.

    It may be, that the fglrx installation had black-listed the radeon driver (by default part of the Kernel).
    Hi,

    Followed all of those instructions several times and also used Dracut. So I was happy to use my OpenSuse using the nomodeset in Grub until the next security updates.

    Next security updates came and were installed. Rebooted this morning and........cannot run my machine at all. I am writing this from within Rescatux!!!

    Even booting in Failsafe mode, it gets stuck at a point in the boot sequence where it is initialising the peripherals (from what I can tell) and then stops. CTRL+ALT+Fx is unavailable, so my computer is now not accessible at all!!!

  6. #6
    Join Date
    Feb 2010
    Location
    Germany
    Posts
    4,576

    Default Re: OpenSuse 42.3 - Blank display on boot after update (no Radeon driver?)

    Quote Originally Posted by DorsetBlue View Post
    Even booting in Failsafe mode, it gets stuck at a point in the boot sequence where it is initialising the peripherals (from what I can tell) and then stops. CTRL+ALT+Fx is unavailable, so my computer is now not accessible at all!!!
    You should be able to boot into Single User Mode (systemd Rescue mode): <https://doc.opensuse.org/documentati...ouble.login.no>.
    From there, you should be able to examine the Journal entries related to the failing boot.

    In addition, please take a look using the openSUSE Rescue System: <https://doc.opensuse.org/documentati...recover.rescue>.

    There's also information in the Support Database:
    SDB: Installation help: <https://en.opensuse.org/SDB:Installation_help>;
    SDB: Disaster Recovery: <https://en.opensuse.org/SDBisaster_Recovery> -- please ignore the emoticon in the URL -- it's a Forums bug …

    Some additional information related to AMD Radeon devices, please check the directories located in "/lib/modules/" -- for the current Leap 42.3 they should be:
    Code:
     > ls -l /lib/modules/
    total 16
    drwxr-xr-x 5 root root 4096 Mar 17 15:00 4.4.103-36-default
    drwxr-xr-x 5 root root 4096 Mar 17 15:00 4.4.104-39-default
    drwxr-xr-x 6 root root 4096 Mar 17 15:00 4.4.114-42-default
    drwxr-xr-x 3 root root 4096 Mar 17 15:00 4.4.79-4-default
     >
    If the '4.4.79-4-default' directory is missing, once you've got a system into a state where you can access the network, you'll need to reinstall (forcibly, with "zypper install --force") the package 'drm-kmp-default' -- the version on your copy of the Leap 42.3 DVD may be "drm-kmp-default-4.9.33_k4.4.76_1-3.2.x86_64.rpm" which is not the version 4.4.79 need by the "weak updates" directory tree of the current Leap 42.3 kernels:
    Code:
     > ls -l /lib/modules/4.4.114-42-default/weak-updates/updates/drivers/gpu/drm/
    total 96
    drwxr-xr-x 4 root root 4096 Mar 17 14:40 amd
    drwxr-xr-x 2 root root 4096 Mar 17 14:40 ast
    drwxr-xr-x 2 root root 4096 Mar 17 14:40 bochs
    drwxr-xr-x 2 root root 4096 Mar 17 14:40 cirrus
    lrwxrwxrwx 1 root root   60 Mar 17 14:40 drm.ko -> /lib/modules/4.4.79-4-default/updates/drivers/gpu/drm/drm.ko
    lrwxrwxrwx 1 root root   71 Mar 17 14:40 drm_kms_helper.ko -> /lib/modules/4.4.79-4-default/updates/drivers/gpu/drm/drm_kms_helper.ko
    drwxr-xr-x 2 root root 4096 Mar 17 14:40 gma500
    drwxr-xr-x 2 root root 4096 Mar 17 14:40 i2c
    drwxr-xr-x 2 root root 4096 Mar 17 14:40 i915
    drwxr-xr-x 2 root root 4096 Mar 17 14:40 mga
    drwxr-xr-x 2 root root 4096 Mar 17 14:40 mgag200
    drwxr-xr-x 2 root root 4096 Mar 17 14:40 nouveau
    drwxr-xr-x 2 root root 4096 Mar 17 14:40 qxl
    drwxr-xr-x 2 root root 4096 Mar 17 14:40 r128
    drwxr-xr-x 2 root root 4096 Mar 17 14:40 radeon
    drwxr-xr-x 2 root root 4096 Mar 17 14:40 savage
    drwxr-xr-x 2 root root 4096 Mar 17 14:40 sis
    drwxr-xr-x 2 root root 4096 Mar 17 14:40 tdfx
    drwxr-xr-x 2 root root 4096 Mar 17 14:40 ttm
    drwxr-xr-x 2 root root 4096 Mar 17 14:40 udl
    drwxr-xr-x 2 root root 4096 Mar 17 14:40 vgem
    drwxr-xr-x 2 root root 4096 Mar 17 14:40 via
    drwxr-xr-x 2 root root 4096 Mar 17 14:40 virtio
    drwxr-xr-x 2 root root 4096 Mar 17 14:40 vmwgfx
     >
    Once you've got that done, from a TTY CLI with the user "root", the command "modprobe radeon" should function correctly.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •