Discussion in 'Videocards - AMD Radeon Drivers Section' started by theoneofgod, Mar 1, 2016.
You can code?
Yes but there are problems with me. It has to be a one man project, others can hardly follow my code lines (no comments, no order), if someone say it doesn't work but fail to say how or what's the problem I will assume it's a troll and even if he/she is right because he/she failed to provide some sort of evidences I won't bother to check.
I also need some sort of motivation (you can't really motivate me with money (for me money = new form of slavery) or fame (fame usually generates stupid hate)), something that I totaly lack atm.
Humans tend to pick the easiest solution and don't even bother to look for other solutions. Why shouldn't I do the same? (Being not like the rest makes the majority reject you.)
Starting a one man project based on amd and ms documentation to make some alternative drivers looks impossible to me. By the time I will have something working the gpus it was designed for will be legacy (just look at how long it took the development of gallium-nine and it's still far from being done and that's not a one man project (mesa devs are totaly unfriendly, that's the main reason I don't even bother to send them reports about the 101 bugs with gallium-nine & hd 4xxx))...
For example I do not trust the gpu usage reported by the gpu itself. Due to this I can not use it for clocks/voltages changes. If I want to make some sort of power save I would use 2 clocks (lowest and highest) and add some exceptions for when the lowest will be used, in the rest of the time highest would be use. Yes the gpu will use a lot of power, but from my point of view power efficiency is a problem that must be solved during chip design.
Well let's hope we'll like what he sees too
black screen no signal only when i watch videos
on amd 16.1 or 16.2 and 16.2.1 all my games run fine..... its a random thing but only happens when i am watching youtube or when i am streaming a movie or a tv show etc... and it only happens when i click like half way thur the movie or a 1/4 of the way.... all of sudden my screen will go black.... then 5 secs later no signal comes accross the screen.. all i can do is reset pc... like i said this doesnt happen when i game... only when i am watching a stream of some type.... its really bad on 16.2.1 every 5 to 8 mins i get no signal, so i downloaded the clockblocker it doesnt work for me on 16.2.1... i have read maybe its a power limit thing... well i turnt up the power on my r9 380 and it still does the same thing..... does anyone know if theres a fix.. or some thing i am missin......
For anyone having issue with the clocks jumping around, just force an overclock profile via msi afterburner. Been doing that since the first crimson driver arrived.
That one too, dumb ecogreenpowerplaysuckinfeature...
Other is that I had random black screens. Like unplugged cable, signal cable, and so was information on screen. While gaming, browsing, etc. Random, not every hour or 2 but...like 30 mins of play, blackscreen, then turn off/on monitor, sometimes helped instant, sometimes 2 times, then again was like 3hrs later or none...2-5times a day(I included using pc by my son, CS:GO, had it too, and my wife email checks...)
I have a somewhat similar problem as well. Monitor will lose signal for a sec and come back up again. Happens randomly. If i switch to the Intel HD, no such issues. All driver versions since 15.x have this issue. (AMD)Matt helped me troubleshoot, but still no go. Guess will save up for Polaris etc.
This is a misconception.
By design the kernel is isolated from the user mode applications and it has codepaths to keep crashes happening in user code from destabilizing the system. When the kernel panics, it panics because of a flaw within the kernel itself, by definition:
let's assume there is a kernel bug and the computer crashes => it means there is a kernel bug
let's assume there is nothing wrong with the kernel and the computer crashes due to an user-space application crashing => it means there is a kernel bug because the kernel somehow failed to prevent a mundane program from taking down the whole machine
If xbmc causes a BSOD, it means that someone in the drivers team was going way overboard while trying to reach the Ballmer peak, instead of paying attention while reading the DDK sections on MSDN.