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.
--
Lab tests show that use of micro$oft causes cancer in lab animals
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.
--
Microsoft has beaten Volkswagen's world record. Volkswagen only created 22
million bugs.
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.
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 [email protected]
> 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)).
if none of these are what your hitting, then maybe(if you can) do a
bisect on this!
Justin P. Mattock
Justin P. Mattock 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 [email protected]
> >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).
Doesn't appear to be. I mentioned above that I have no errors. I forgot
about it saying something about the BIOS. It shows this
[drm:radeon_get_bios] *ERROR* Unable to locate a BIOS ROM
> 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)).
This one appears to be X related. In my case, this happens immediately at
radeon.ko load (with modeset=1).
Verification of this was booting with init=/bin/sh and modprobe radeon.
Instant black screen. The backlight stays on.
> if none of these are what your hitting, then maybe(if you can) do a
> bisect on this!
I tried 2.6.32.15. I noticed that KMS was in staging. This one didn't do a
black screen. I saw mostly white, green and a pinkish color. All were kind
of washed out and were in vertical lines. KMS on this laptop has not worked
with stock kernels.
I booted Ubuntu 10.04 live CD and it appears that KMS was working. I don't
know what patches they have in the kernel for this or what is different.
--
Microsoft has beaten Volkswagen's world record. Volkswagen only created 22
million bugs.
On Tue, Jul 6, 2010 at 2:18 AM, Justin P. Mattock
<[email protected]> 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 [email protected]
>> 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
>
> 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 [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
On 07/05/2010 07:34 PM, Xiaotian Feng wrote:
> On Tue, Jul 6, 2010 at 2:18 AM, Justin P. Mattock
> <[email protected]> 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 [email protected]
>>> 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 [email protected]
>> 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 <[email protected]>
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