[Bug 73291] New: Kernel 3.13.7 boots with hybrid Intel/ATI but to blank graphical screen

bugzilla-daemon at bugzilla.kernel.org bugzilla-daemon at bugzilla.kernel.org
Mon Mar 31 07:34:14 PDT 2014


https://bugzilla.kernel.org/show_bug.cgi?id=73291

            Bug ID: 73291
           Summary: Kernel 3.13.7 boots with hybrid Intel/ATI but to blank
                    graphical screen
           Product: Drivers
           Version: 2.5
    Kernel Version: 3.13.7
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: high
          Priority: P1
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri at kernel-bugs.osdl.org
          Reporter: mike.cloaked at gmail.com
        Regression: No

Created attachment 131071
  --> https://bugzilla.kernel.org/attachment.cgi?id=131071&action=edit
systemd journal for current boot with kernel 3.13.6

Running arch linux stock kernel. Previous Kernel 3.13.6 boots to graphical
screen giving a usable laptop but problems with radeon apparent from systemd
journal log. Updating the kernel to 3.13.7 boots the laptop, but the graphical
screen is blank apart from static cursor at top left of the screen. The kernel
is still running and able to ssh in to get at the log files (attached). No
graphics is usable.

Hybrid graphics in this Lenovo Thinkpad S540 is:

$ lspci | egrep '(Graphics|Display)'
00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated
Graphics Controller (rev 09)
06:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Sun XT
[Radeon HD 8670A]

i915 and radeon modules are built into the initial ramdisk.

xrandr only sees one provider:

$ xrandr --listproviders
Providers: number : 1
Provider 0: id: 0x48 cap: 0xb, Source Output, Sink Output, Sink Offload crtcs:
4 outputs: 5 associated providers: 0 name:Intel

I have tried adding intel.modeset=0, and separately  radeon.runpm=0 to the
kernel line but this does not remedy the situation.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.


More information about the dri-devel mailing list