oh no, it appears my assumption was wrong - Mageia appears to be using 'radeon' vendor 'Xorg Foundation'.
i presume that means its not proprietary ? !


i think later i will step through the Xorg log and look for differences - maybe thats something to try ??


thanks

same problem exists with 32 bit slack (forgot to say the above is all related to 64bit) on a different machine architecture

but flash is ok on mageia and suse machines (64 and 32) .... must check what version of flash is being used to ensure its not the latst plugin at fault............... then check FF versions.......... then check another browser??




:-| confused i am !!!

So is your user part of the audio group? I ask because flash won't play if it can't output audio, IIRC. To check, type:

as the user wanting to play flash into a terminal. If `audio' is not among those groups, become root and run:

.

Hope this helps, it at least helped me when I set up a new Slackware system and wanted to play flash and couldn't. Of course the problem could lie somewhere else. And if all else fails, there is still pipelight to try. (pipelight worked wonders on my Thinkpad T60, which suffered from choppy playback on some YouTube videos with Chrome's PepperFlash, pipelight played them fine.)

lems

Unless you upgrade your kernel to 3.11 or higher and add the kernel option radeon.dpm=1 to your bootloader configuration (the latter not necessary with kernel 3.13 and future versions) this videochip will only run in its lowest possible power-state and frequency, seriously impacting performance. If you don't want to make those changes it is highly recommended to use the proprietary drivers.
I use currently kernel 3.12 with that option on a HD3200 and a HD6870, without any problems.

Youtube indeed offers many (not all) videos in HTML5, but unless you use Google's Chrome/Chromium you have to manually activate that option: http://www.youtube.com/html5

You are indeed The Man, Tobi. Not only the information, but a link right to the page where one click and Bam! "Up yours, Adobe!"

thank you for that - i've never 'built' a kernel - i will have a read up. do you have any good , simple to follow references to recommend pls ?

also, where is the information that you refer to that details the chip not being supported to its fullest - im only asking because im not sure where to look?


@LEMS
"So is your user part of the audio group? I ask because flash won't play if it can't output audio, IIRC. To check, type:"


yes it is, via the 'users' group which features in the audio group by default it seems. (i put in in directly to try your idea, but nothing changed) i will have a further check.

thank you..... what a farce.......i feel quite sure it will be something obvious to some one :-)

http://alien.slackbook.org/dokuwiki/...kernelbuilding

I follow the development of the free radeon drivers closely, because I use them myself. Dynamic power management was for Radeon chips was introduced with kernel 3.11. I get my information from the Phoronix forum, that also follows development of various drivers and is frequented by some of the developers.

I have this when I don't have an /etc/asound.conf with my card in it.

ok :-) i have [re]built the kernel using the stable 3.12.8

whilst not full understanding what was going on, it seems to have gone without a hitch.

so a few questions please -

@TobySGD

where exactly do i put the radeon.dpm=1 ? and what can i use to prove everything is working/benefiting as it should graphics wise now i've done all this please ?


the flashplayer plugin is not resolved - there is a suggestion above (from Jack Hair) to create an asound.conf file .... what should I put in it and why is it not used on other distros I've tried please ?

thank you for your continuing support.

My asound.conf looks like this:

defaults.pcm.!card Generic
defaults.ctl.!card Generic
defaults.pcm.!device 3
defaults.ctl.!device 3


You can find out the device when you open a terminal and type: aplay -l it will tell you what card and device. Enter it like above into asound.conf and place it in /etc/

@JackHair

Thanks so much! the problem was not having the asound.conf ! I've created one (using the slackware docs help) and it works.
Top advice. What a job though for i to be that.


Now then, just waiting for how to get the best out of the Radeon from @Toby (and any others) if possible.


Many thanks.

Assuming that you use Lilo as bootloader. put it in your /etc/lilo.conf, in the line that begins with append=. It may be possible that you have already parameters there, just add the new parameter. For example, my append line looks like this:After you have changed that file you have to run lilo to apply the changes. Then reboot the system. After booting you can check if dynamic power-management is working with If it returns dpm then it is working correctly.