| 1 |
On Thu, Nov 20, 2008 at 9:03 PM, Iain Buchanan <iaindb@××××××××××××.au>wrote: |
| 2 |
|
| 3 |
> Nikos Chantziaras wrote:I have opened a bug for it, but it got closed |
| 4 |
> immediately because I have |
| 5 |
> |
| 6 |
>> no evidence to support it. lol :P |
| 7 |
>> |
| 8 |
>> http://bugs.gentoo.org/show_bug.cgi?id=247860 |
| 9 |
>> |
| 10 |
> |
| 11 |
> AFAIR Jer is only a wrangler (ok, "only" is not the right word, but you |
| 12 |
> know what I mean) so he's likely not going to get into too much detail about |
| 13 |
> the specifics of the bug wrt fglrx, ati, etc. You'd have better luck |
| 14 |
> talking to a dev who deals with fglrx or the kernel, and convincing them to |
| 15 |
> look at it. |
| 16 |
> |
| 17 |
> I know it can be frustrating to have bugs marked as INVALID, but saying |
| 18 |
> "your justification for marking this as INVALID is actually the invalid |
| 19 |
> thing here ... not my bug report" is probably going to get you ignored! |
| 20 |
> |
| 21 |
> I'm not disagreeing with you here, but I do think you will have a hard time |
| 22 |
> getting hard evidence it's specifically the fglrx driver, and not some |
| 23 |
> effect the fglrx driver is having on your hw... |
| 24 |
> |
| 25 |
|
| 26 |
I agree. Even if this is a bug, no open source developer could be qualified |
| 27 |
to fix it because fgrlx is closed source. If you can, report this to ATI, |
| 28 |
otherwise, you will have to live with the problem or use open source |
| 29 |
drivers. |
Archives