From: "Justin P. Mattock" <justinmattock@gmail.com>
To: Xiaotian Feng <xtfeng@gmail.com>
Cc: Marvin <marvin24@gmx.de>,
linux-kernel@vger.kernel.org, xorg-driver-ati@lists.x.org
Subject: Re: Radeon KMS doesn't work.
Date: Mon, 05 Jul 2010 20:28:31 -0700 [thread overview]
Message-ID: <4C32A2DF.4010500@gmail.com> (raw)
In-Reply-To: <AANLkTil2pHW4C-g-DPKUy-yvDfB3fedQC270RfqL3Gnt@mail.gmail.com>
On 07/05/2010 07:34 PM, Xiaotian Feng wrote:
> On Tue, Jul 6, 2010 at 2:18 AM, Justin P. Mattock
> <justinmattock@gmail.com> wrote:
>> On 07/05/2010 10:27 AM, Marvin wrote:
>>>
>>> Hi Wakko,
>>>
>>> as nobody seems to have answered yet, I think it's better that you file a
>>> bug
>>> against the radeon driver (bugs.freedesktop.org, one bug for each defect).
>>> There may be similar bugs already, so please check this also.
>>>
>>> Thanks
>>>
>>> Marvin
>>>
>>> Am Montag 05 Juli 2010, 01:19:26 schrieb Wakko Warner:
>>>>
>>>> Wakko Warner wrote:
>>>>>
>>>>> I have a Dell Inspiron 5100 with an ATI Radeon Mobility M7 (7500 R100
>>>>> PCI ID 1002:4c57 sub 1028:0149).
>>>>>
>>>>> Immediately when radeon.ko is loaded, the screen goes blank (The
>>>>> backlight stays on). I have fbcon compiled into the kernel (I also
>>>>> tried as module). I am unable to get the screen to work again until I
>>>>> reboot. The logs did not appear to have any errors after the module
>>>>> loaded. The system was still responsive on the network.
>>>>>
>>>>> I tried kernels 2.6.33 and 2.6.34.
>>>>>
>>>>> I can provide kernel output if needed.
>>>>
>>>> I need to add that if I use modeset=0, the screen does not blank.
>>>>
>>>> Also 2.6.34 (with modeset=0) doesn't do 3D very well on this system.
>>>> Some
>>>> objects look ok, some are garbled, some do not appear at all. The gears
>>>> from xscreensaver does not show up at all.
>>>
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>> Please read the FAQ at http://www.tux.org/lkml/
>>>
>>
>>
>> I've hit a couple of things with radeon as well.. the first was this:
>> http://lkml.org/lkml/2010/6/6/172
>> (if your hitting this issue, then the patch should work and/or it should
>> already be in the main tree).
>>
>> then a few days ago hit another:
>> https://bugzilla.kernel.org/show_bug.cgi?id=16335
>> (keep in mind still uncertain on a fix for this, reverting the commit gets
>> me up and running(I created a patch, but an umsure if it's a right
>> solution)).
>
> I think this is the same cases with (http://lkml.org/lkml/2010/7/5/44)
> And the fix for this bug is in -tip tree, commit 2463eb8
>
> Could you please try following patch?
> http://git.kernel.org/tip/2463eb8b3093995e09a0d41b3d78ee0cf5fb4249
>
applied.. o.k. system started without hitting the crash I was
experiencing!! Thanks for this.. I'll run this and let you know if I
experience anything out of the ordinary..
>>
>> if none of these are what your hitting, then maybe(if you can) do a bisect
>> on this!
>>
>> Justin P. Mattock
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>> Please read the FAQ at http://www.tux.org/lkml/
>>
>
Tested-By: Justin P. Mattock <justinmattock@gmail.com>
I'll send this info over to the bug report so they know..and if things
go good get this thing closed..
Justin P. Mattock
prev parent reply other threads:[~2010-07-06 3:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-03 22:10 Radeon KMS doesn't work Wakko Warner
2010-07-04 23:19 ` Wakko Warner
2010-07-05 17:27 ` Marvin
2010-07-05 18:18 ` Justin P. Mattock
2010-07-06 1:52 ` Wakko Warner
2010-07-06 2:34 ` Xiaotian Feng
2010-07-06 3:28 ` Justin P. Mattock [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=4C32A2DF.4010500@gmail.com \
--to=justinmattock@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marvin24@gmx.de \
--cc=xorg-driver-ati@lists.x.org \
--cc=xtfeng@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;
as well as URLs for NNTP newsgroup(s).