From: Maciej Rutecki <maciej.rutecki@gmail.com>
To: trentbuck@gmail.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: BUG: blank screen i915 (N10) LVDS in 2.6.37
Date: Wed, 12 Jan 2011 20:07:46 +0100 [thread overview]
Message-ID: <201101122007.46480.maciej.rutecki@gmail.com> (raw)
In-Reply-To: <20110107085931.GA1400@dali>
I created a Bugzilla entry at
https://bugzilla.kernel.org/show_bug.cgi?id=26602
for your bug report, please add your address to the CC list in there, thanks!
On piątek, 7 stycznia 2011 o 09:59:37 trentbuck@gmail.com wrote:
> When I boot 2.6.37, the onboard head remains blank.
> It works in 2.6.36. In both cases, the VGA head works fine.
>
> I had problems with 2.6.37rc*; I can't remember if they were related,
> but I know .36 works for me. The screen blanks immediately after
> extlinux loads the kernel; I have i915 compiled in.
>
> I am using Debian Sid with xserver-xorg-video-intel 2:2.13.0-5.
>
> video=LVDS1:e does not help, nor does video=LVDS-1:e. With .32 (and
> .36, I think), xrandr reports LVDS-1 with the hyphen, but in .37 it
> reports it without the hyphen. Likewise for VGA1 VGA-1. I have not
> tried nomodeset.
>
> My default environment is fbcon. I tried to start X on .37 by typing
> blind into fbcon, and nothing came up. From this, I presume that X
> also can't address the LVDS head properly. I didn't try it with a VGA
> head attached.
>
> The unit in question is an Asus Eee PC 1005P netbook.
>
> IIRC I also changed from eeepc_laptop on .36 to eeepc_wmi .37 (with
> the associated change to the boot parameter in .config); dunno if that
> matters.
--
Maciej Rutecki
http://www.maciek.unixy.pl
prev parent reply other threads:[~2011-01-12 19:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-07 8:59 BUG: blank screen i915 (N10) LVDS in 2.6.37 trentbuck
2011-01-07 17:19 ` Trent W. Buck
2011-01-12 19:07 ` Maciej Rutecki [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201101122007.46480.maciej.rutecki@gmail.com \
--to=maciej.rutecki@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=trentbuck@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox