@LostInSpacetime: your bug might be in fglrx, or it might be in Skype... Try using Skype without fglrx (use the FOSS ati/radeon/radeonhd driver) to see if you can reproduce the bug.
You can also try disabling composite in fglrx (it doesn't deal well with it).
@mirv: there is one major difference between your Nforce3 chipset and mine: Nforce3 uses AGP (which is now old enough to have all quirks known and worked around), while Nforce430 (mine) and more recent (baskin) use PCI-express. I suspect the problem is to be found in fglrx's internal, proprietary, graphics bus controller: PCI-E being still evolving, I betcha there's a little regression in it somewhere!
One path worth investigating: how does fglrx deal with PCI-E 2.0 cards plugged in PCI-E 1.0 motherboards? Did it change in any way for Catalyst 9.9?
You can also try disabling composite in fglrx (it doesn't deal well with it).
@mirv: there is one major difference between your Nforce3 chipset and mine: Nforce3 uses AGP (which is now old enough to have all quirks known and worked around), while Nforce430 (mine) and more recent (baskin) use PCI-express. I suspect the problem is to be found in fglrx's internal, proprietary, graphics bus controller: PCI-E being still evolving, I betcha there's a little regression in it somewhere!
One path worth investigating: how does fglrx deal with PCI-E 2.0 cards plugged in PCI-E 1.0 motherboards? Did it change in any way for Catalyst 9.9?
Comment