On Mon, Feb 8, 2010 at 8:10 AM, Ben Wong bugs.debian@wongs.net wrote:
Is that all with the same radeon dri driver (from libgl1-mesa-dri)?
WORKS
Ubuntu/karmic: DRI works perfectly
Linux-2.6.31.14.27
libgl1-mesa-dri-7.6.0-1ubuntu4
I just want to mention that, despite my results,
On Sat, Feb 6, 2010 at 00:02:14 -0500, Ben Wong wrote:
Debian/stable (2.6.26): DRI works perfectly.
Ubuntu/karmic (2.6.31): DRI works perfectly
Debian/testing (2.6.32): DRI destroys file system
Debian/testing using karmic's radeon driver: DRI destroys file system
Is that all with the same
Mesa 7.6 is not the problem. I tested with a LiveCD (Mint Helena)
that uses Mesa 7.6 and had no problems. I also installed it to hard
disk to make sure that that wasn't a factor. Again, no problems.
As a test, I've installed libgl1-mesa-dri and libgl1-mesa-glx from experimental
--
To
On Fri, Feb 5, 2010 at 12:05 PM, Ben Wong bugs.debian@wongs.net wrote:
Mesa 7.6 is not the problem. I tested with a LiveCD (Mint Helena)
that uses Mesa 7.6 and had no problems. I also installed it to hard
disk to make sure that that wasn't a factor. Again, no problems.
As a test, I've
I now believe radeon_cp.c is not the problem. In fact, the radeon DRM
driver appears to be completely innocent. I'd appreciate any help or
suggestions where to look next.
Less short: Using alternate versions of radeon_cp.c and the entire
radeon driver directory to compile the radeon.ko kernel
On Sat, Feb 6, 2010 at 12:02 AM, Ben Wong bugs.debian@wongs.net wrote:
Next I tried copying the entire driver/gpu/drm/radeon directory from
Ubuntu and compiled that kernel module under Debian. I was surprised
to find that the bug still manifested using that kernel module as
well.
Just
On Thu, Jan 14, 2010 at 5:47 AM, Ben Wong bugs.debian@wongs.net wrote:
On 1/13/10, Julien Cristau jcris...@debian.org wrote:
The reports seem to have started shortly after the upload of mesa 7.6 to
unstable, so it's possible this is a long-standing kernel bug being
triggered by a new bug
On 1/13/10, Julien Cristau jcris...@debian.org wrote:
On Wed, Jan 13, 2010 at 02:30:18 -0800, Ben Wong wrote:
FWIW, http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=550977 was
reported on r100, not r200.
Good to know. Thanks.
The reports seem to have started shortly after the upload of
firmware when it is separated from the kernel. (Could it be that the
binary blob didn't get copied correctly when it was split?)
I've compared them again - they're identical to the blobs previously
embedded in the driver (except for byteswapping).
That makes some sense, since DRI actually
On Wed, Jan 13, 2010 at 02:30:18 -0800, Ben Wong wrote:
When you say it 'only affect systems that use the radeon/R200_cp.bin
firmware' do you mean that you tested systems with other Radeon GPU
versions and they were not affected, or that this problem appeared after
the firmware was
On Wed, 2010-01-13 at 02:30 -0800, Ben Wong wrote:
When you say it 'only affect systems that use the radeon/R200_cp.bin
firmware' do you mean that you tested systems with other Radeon GPU
versions and they were not affected, or that this problem appeared after
the firmware was separated
I have organized this bug report so that the most important information
is at the top so that you can stop reading as soon as you get bored.
This bug, #550562, should be reclassified as a critical bug and possibly
merged with #560126.
This bug causes severe filesystem corruption and catastrophic
On Tue, 2010-01-12 at 04:30 -0800, Ben Wong wrote:
I have organized this bug report so that the most important information
is at the top so that you can stop reading as soon as you get bored.
This bug, #550562, should be reclassified as a critical bug and possibly
merged with #560126.
I
13 matches
Mail list logo
