From: "Alexander E. Patrakov" <patrakov@gmail.com>
To: intel-gfx@lists.freedesktop.org
Subject: Re: blank screen FUJITSU LIFEBOOK S760
Date: Sun, 6 May 2012 05:32:24 +0000 (UTC) [thread overview]
Message-ID: <jo52d8$j45$1@dough.gmane.org> (raw)
In-Reply-To: 20120505124033.GA11736@phenom.ffwll.local
Daniel Vetter wrote:
> On Sat, May 05, 2012 at 07:20:16AM -0400, Babar Haq wrote:
>> Hi all,
>>
>> I hope this is the right place to raise this issue. I have waited
>> patiently for almost a year but it remains unfixed. I filed the burt
>> here and any information/workaround related to it would be highly
>> appreciated.
>
> Well, if you want to report this bug with upstream here, we pretty much
> expect you to test latest git kernel first. If that doesn't help, please
> file the bug on bugs.freedesktop.org, see
>
> http://intellinuxgraphics.org/how_to_report_bug.html
>
> We're working on quite a few bugfixes and issues leading to black
> screens,
> but without further details there's not much we can do.
> -Daniel
I also have a Fujitsu Lifebook S760 laptop, and video Just Works in
Gentoo. And it worked from day one, i.e. since February 2011. Thus the
request to test the latest kernel from git looks rather bogus to me.
2.6.39 should be sufficient, and my gut feeling is that some other
package is at fault here.
One obvious difference is that Ubuntu and Fedora (who has a duplicate
bug) use Plymouth, while Gentoo doesn't. To test the theory, could you
please remove the "splash vt.handoff=7" parameters from the kernel
command line?
--
Alexander E. Patrakov
next prev parent reply other threads:[~2012-05-06 5:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-05 11:20 blank screen FUJITSU LIFEBOOK S760 Babar Haq
2012-05-05 12:40 ` Daniel Vetter
2012-05-06 5:32 ` Alexander E. Patrakov [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-05-07 13:31 Babar Haq
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='jo52d8$j45$1@dough.gmane.org' \
--to=patrakov@gmail.com \
--cc=intel-gfx@lists.freedesktop.org \
/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