https://bugs.freedesktop.org/show_bug.cgi?id=34462
Owen Riddy changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=34462
--- Comment #6 from Jonathan Nieder 2011-12-03 00:16:17
PST ---
Owen, can you bisect?
Just trying a few intermediate versions from http://snapshot.debian.org/ would
already be useful. For narrowing down the regression range beyond that, "git
https://bugs.freedesktop.org/show_bug.cgi?id=34462
--- Comment #6 from Jonathan Nieder jrnie...@gmail.com 2011-12-03 00:16:17
PST ---
Owen, can you bisect?
Just trying a few intermediate versions from http://snapshot.debian.org/ would
already be useful. For narrowing down the regression range
https://bugs.freedesktop.org/show_bug.cgi?id=34462
--- Comment #5 from Owen Riddy 2011-02-24 02:11:27
PST ---
> Does passing the parameter no_wb=1 to the radeon kernel module help?
It doesn't seem to help. `dmesg | grep WB` shows it as Disabled, but modprobe
still hangs on load at the RS780
https://bugs.freedesktop.org/show_bug.cgi?id=34462
--- Comment #5 from Owen Riddy owen.ri...@gmail.com 2011-02-24 02:11:27 PST
---
Does passing the parameter no_wb=1 to the radeon kernel module help?
It doesn't seem to help. `dmesg | grep WB` shows it as Disabled, but modprobe
still hangs on
https://bugs.freedesktop.org/show_bug.cgi?id=34462
--- Comment #4 from Michel D?nzer 2011-02-23 06:05:20
PST ---
(In reply to comment #4)
> [4.414321] radeon :01:05.0: WB enabled
Does passing the parameter no_wb=1 to the radeon kernel module help?
Alternatively, does disabling the
https://bugs.freedesktop.org/show_bug.cgi?id=34462
--- Comment #4 from Michel Dänzer mic...@daenzer.net 2011-02-23 06:05:20 PST
---
(In reply to comment #4)
[4.414321] radeon :01:05.0: WB enabled
Does passing the parameter no_wb=1 to the radeon kernel module help?
Alternatively, does
https://bugs.freedesktop.org/show_bug.cgi?id=34462
--- Comment #3 from Owen Riddy 2011-02-20 01:47:38
PST ---
:/ Sorry, my last paragraph was a little ambigous.
On my old debian 2.6.32 kernel, this worked swimmingly (module loaded nearly
instantly, screen resolution jumped up).
On the debian
https://bugs.freedesktop.org/show_bug.cgi?id=34462
--- Comment #2 from Owen Riddy 2011-02-18 21:23:16
PST ---
Comparing the initrd of 2.6.37 and 2.6.32 show they are both the same, and
neither of them have any firmware in them. They didn't actually have the radeon
module at all.
I compared
https://bugs.freedesktop.org/show_bug.cgi?id=34462
--- Comment #1 from Alex Deucher 2011-02-18 14:29:18 PST
---
Make sure you have the firmware in your initrd if you are using modules, or
built into the kernel if you built radeon into the kernel rather than as a
module. See the
https://bugs.freedesktop.org/show_bug.cgi?id=34462
Alex Deucher changed:
What|Removed |Added
Attachment #43540|application/octet-stream|text/plain
mime type|
https://bugs.freedesktop.org/show_bug.cgi?id=34462
Alex Deucher ag...@yahoo.com changed:
What|Removed |Added
Attachment #43540|application/octet-stream|text/plain
mime
https://bugs.freedesktop.org/show_bug.cgi?id=34462
--- Comment #1 from Alex Deucher ag...@yahoo.com 2011-02-18 14:29:18 PST ---
Make sure you have the firmware in your initrd if you are using modules, or
built into the kernel if you built radeon into the kernel rather than as a
module. See the
13 matches
Mail list logo
