On Fri, Mar 15, 2013 at 12:29 AM, Jani Nikula
wrote:
> I've never used the acpi_osi= kernel parameter, but it looks like you
> could workaround this with acpi_osi="!Windows 2012". Please check that
> running the "bad" kernel.
I find out that I just can't set the acpi_osi="!Windows 2012" properly
On Fri, Mar 15, 2013 at 12:29 AM, Jani Nikula
wrote:
> Fun. The BIOS seems to ask for zero backlight. Maybe it means something
> else for Windows 8. White is the new black or something.
I did some experiment, I go to intel_backlight directory.
It show brightness is 4648, but actual_brightness is
On Fri, Mar 15, 2013 at 12:29 AM, Jani Nikula
wrote:
> I've never used the acpi_osi= kernel parameter, but it looks like you
> could workaround this with acpi_osi="!Windows 2012". Please check that
> running the "bad" kernel.
That did not work for me. Still have black screen on the tip of git.
I
On Mon, Mar 11, 2013 at 6:16 AM, Jani Nikula
wrote:
> Interesting snippets from your dmesgs:
>
> 1) good
>
> [0.00] Linux version 3.6.0-rc6+ (chr...@ideapad.lan) (gcc version
> 4.7.2 20121109 (Red Hat 4.7.2-8) (GCC) ) #25 SMP Wed Feb 20 12:55:06 PST 2013
> ...
> [5.341431] [drm:intel_
On Mon, Mar 4, 2013 at 3:16 PM, Chris Li wrote:
>>> Two things to test:
>>> - Can you please check whether any of the backlight drivers in
>>> /sys/class/backlight does anything? You need to frob the brightness
>>> file. Please also list all the drivers you hav
Thanks Daniel
I am recompiling the kernel.
I will also open a bug in bugzilla when I collect all the relative information.
Chris
On Mon, Mar 4, 2013 at 9:50 AM, Daniel Vetter wrote:
>> Two things to test:
>> - Can you please check whether any of the backlight drivers in
>> /sys/class/backlight
%
reproducible.
Any suggestion how to further debug this i9515 black screen problem?
I really want to get it fixed.
Thanks
Chris
On Fri, Feb 22, 2013 at 2:42 PM, Chris Li wrote:
> Ping. Any update for this black screen problem?
>
> Chris
>
> On Wed, Feb 20, 2013 at 1:04 PM, Chris Li wr
Ping. Any update for this black screen problem?
Chris
On Wed, Feb 20, 2013 at 1:04 PM, Chris Li wrote:
> Here is the dmesg with "drm.debug=0xe" at
> 80187431762989ebade986468d3c548287a12689
>
> That is the 3.6 kernel, exactly one commit before the ACPI commit
> wh
On Wed, Feb 20, 2013 at 12:19 PM, Daniel Vetter wrote:
> The debug option did not stick for some reason. Also you're hitting a
> bunch of WARNs in our driver self-checks. Iirc those should be fixed
> in the latest code. Can you please test with the latest
> drm-intel-nightly branch from
>
> http:/
On Wed, Feb 20, 2013 at 11:45 AM, Chris Li wrote:
> Here is the dmesg with "drm.debug=0xe". It is from the tip of git
> kernel. The computer has the black screen.
> Let me know what else do you need.
More probing. When I use type "reboot" via ssh. The machine will
On Wed, Feb 20, 2013 at 11:29 AM, Chris Li wrote:
>
> Here it is the dmesg from the FC18 live CD kernel. No black screen.
Sorry please ignore my previous dmesg. It was boot with i915.modeset=0.
I am doing another one without that line.
Chris
--
To unsubscribe from this list: send th
CC Linus for suggestion of debugging.
Linus, it seems very hard to extract information from the dead kernel.
Black screen prevents seeing the kernel OOPS, if there is one.
The laptop has no serial port. Ethernet driver is not working on that
laptop. Only wifi works.
Any suggestion?
On Tue, Feb 1
My Lenovo Y580 laptop with FC18 start to get black screen after the kernel
upgrade to 3.7.xxx
The black screen happens about the time kernel switch to using VT console.
At the point of black screen, no response of cap locks key led no network
connection. The machine seems dead.
The CPU is i7 and
Err,
Sparse does not support the local label syntax yet. It just treats the
second label "x:" as the same as the first one. Then the linearize
code gets serious confused when it saw one label get define in two
places.
The fix seems not trivial from the first look.
Chris
On 10/16/07, Alexey Dobr
14 matches
Mail list logo