AMD Adrenalin driver software not accessible when installing official latest graphics drivers drivers

Hi guys,

unluckily using the official drivers from the Lenovo Legion Go driver page I don't get access to the driver settings, like it happened with an older beta driver already. At that time you could run a file hidden in some folder from the driver package and then everything was fine again... Now I couldn't even find such file...

I tried reinstalling it cleanly after deinstalling the graphics and the chipset drivers and cleaning up the rest a few times with the AMD driver removal tool, and one time even with DDU, but nothing of this helped...

As I installed the latest driver posted in this forum I still had the possibility to access to the AMD Adrenalin driver settings... 

With the one downloaded from the driver page there is no chance though...

-> As I would have preferred not to manually have to make the registry change for activating integer scaling using the one posted in this forum, but to use the meant implementation in the drivers, does anyone have tips on how to fix this?

I even had the newest AMD Ryzen 7840U drivers installed temporarily, even including a HYPR-FX Eco mode, but as only the 1600p resolution was selectable as one of the Legion Go's proper 16:10 resolutions and all the others were distorted it doesn't make sense for me to use it...

Parents
  • I will bring this up with our RD team and see if we can modify future VGA driver updates to include Adrenalin install.

  •   

    Thank you very much for that!

    What   wrote is true, but the really bad thing is, there seems to be no way back once you sideloaded a 780m driver onto your device at all, like I did (please read my other comment about this)...

    -> You could say it is my fault beeing unpatient for the new drivers to be released onto the GO and installing those "sideloaded" ones at all, but new drivers still take a really long time to be fully adapted and to be made available "officially" for the GO...

Reply
  •   

    Thank you very much for that!

    What   wrote is true, but the really bad thing is, there seems to be no way back once you sideloaded a 780m driver onto your device at all, like I did (please read my other comment about this)...

    -> You could say it is my fault beeing unpatient for the new drivers to be released onto the GO and installing those "sideloaded" ones at all, but new drivers still take a really long time to be fully adapted and to be made available "officially" for the GO...

Children
No Data