From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 90534] integrated LVDS displays stays dark (firmware-linux-nonfree-0.43) Date: Mon, 01 Jun 2015 14:29:03 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1626384824==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id C2CCC6E644 for ; Mon, 1 Jun 2015 07:29:02 -0700 (PDT) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1626384824== Content-Type: multipart/alternative; boundary="1433168942.cc0a0.4486"; charset="UTF-8" --1433168942.cc0a0.4486 Date: Mon, 1 Jun 2015 14:29:02 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" https://bugs.freedesktop.org/show_bug.cgi?id=90534 --- Comment #19 from Alex Deucher --- It's always been the same firmware. firmware is firmware. Different distros have changed their packaging polices with respect to firmware. That might be the case for you (e.g., distro used to just include the firmware with the kernel and now ships it as a separate package). As to narrowing it down, I'd suggest trying interim kernels between the last know good one and most recent one you've tried to see of you can narrow down when it broke. E.g., if kernel 3.14 worked and 3.15 is bad you know the regression happened in the 3.15 kernel cycle. -- You are receiving this mail because: You are the assignee for the bug. --1433168942.cc0a0.4486 Date: Mon, 1 Jun 2015 14:29:02 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8"

Comment # 19 on bug 90534 from 
It's always been the same firmware.  firmware is firmware.  Different distros
have changed their packaging polices with respect to firmware.  That might be
the case for you (e.g., distro used to just include the firmware with the
kernel and now ships it as a separate package).  As to narrowing it down, I'd
suggest trying interim kernels between the last know good one and most recent
one you've tried to see of you can narrow down when it broke.  E.g., if kernel
3.14 worked and 3.15 is bad you know the regression happened in the 3.15 kernel
cycle.

You are receiving this mail because:
  • You are the assignee for the bug.
--1433168942.cc0a0.4486-- --===============1626384824== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHA6Ly9saXN0 cy5mcmVlZGVza3RvcC5vcmcvbWFpbG1hbi9saXN0aW5mby9kcmktZGV2ZWwK --===============1626384824==--