Hi,
Michel Dänzer wrote:
For Radeons, that's only true for older cards without ATOM BIOS,
basically anything older than Radeon X1xxx. So this shouldn't be a
problem for a Radeon HD 5450, but there might be other issues, e.g. the
drivers in the stable release might be too old to properly
On Fre, 2012-02-17 at 14:33 +0100, Stephane Louise wrote:
Michel Dänzer wrote:
For Radeons, that's only true for older cards without ATOM BIOS,
basically anything older than Radeon X1xxx. So this shouldn't be a
problem for a Radeon HD 5450, but there might be other issues, e.g. the
On Fre, 2012-02-17 at 15:50 +0100, Stephane Louise wrote:
Attached (note: this one is without monitor attached, because I am not
at home).
I don't see any obvious problems, would need to see the output with the
monitor connected. BTW, which connector(s) have you tried connecting it
to?
BTW, no
Attached (note: this one is without monitor attached, because I am not at home).
Stéphane
2012/2/17, Michel Dänzer daen...@debian.org:
On Fre, 2012-02-17 at 14:33 +0100, Stephane Louise wrote:
Michel Dänzer wrote:
For Radeons, that's only true for older cards without ATOM BIOS,
basically
I tried DVI and HDMI connectors. The only new dmesg that I have is:
[drm:radeon_dvi_detect] *ERROR* HDMI-A-1: probed a monitor but no|invalid EDID
That's the only time when you can actually see something wrong in
dmesg (it doesn't happen each time, but the result is the same).
Stéphane
Le 17
On Fri, Feb 17, 2012 at 09:12:33PM +0100, Stephane Louise wrote:
I tried DVI and HDMI connectors. The only new dmesg that I have is:
[drm:radeon_dvi_detect] *ERROR* HDMI-A-1: probed a monitor but no|invalid EDID
That's the only time when you can actually see something wrong in
dmesg (it
On Fre, 2012-02-17 at 15:52 -0500, Lennart Sorensen wrote:
On Fri, Feb 17, 2012 at 09:12:33PM +0100, Stephane Louise wrote:
I tried DVI and HDMI connectors. The only new dmesg that I have is:
[drm:radeon_dvi_detect] *ERROR* HDMI-A-1: probed a monitor but no|invalid
EDID
Same message when
Hello,
(Not subscribed to debian-powerpc@, please CC to me/the bug report as
appropriate).
Can somebody please help to check if this bug from SDL libraries is
still present on powerpc? I don't have access to any powerpc box, and the
submitter has not replied for a while.
The files are here
On Fri, Feb 17, 2012 at 10:23:48PM +, Manuel A. Fernandez Montecelo wrote:
(Not subscribed to debian-powerpc@, please CC to me/the bug report as
appropriate).
Can somebody please help to check if this bug from SDL libraries is
still present on powerpc? I don't have access to any powerpc
Hi Lennart,
2012/2/17 Lennart Sorensen lsore...@csclub.uwaterloo.ca:
I don't have video on any powerpc machine, but I ran with ssh -X
user@powerpc machine, and ran the testoverlay and testoverlay2 programs.
I got no errors from either and they appeared to do something interesting.
So if the
I'm writing this from an old Hoary LiveCD.
Are there any boot parameters I'll need to add to stop the problem?
--
To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
11 matches
Mail list logo