IceScreamer This, with the lower battery life compared to competing Intel solutions, is the main reason I recommend against buying Ryzen laptops to my friends/family.

And that bullshit excuse is fishy, offering the generic drivers on site at least seems like a simple solution and my guess the OEMs are somehow stopping them. I mean they (AMD) do have some dumb choices but this is absurd.

Valantar Let's address the latter point first: no, it wouldn't. The vast majority of vendor-distributed drivers are straight-up unmodified, and the vast majority of most modified drivers is again straight from the OEM, with only very minor modifications implemented. Leaving a blank space for [Insert vendor modification here] in the driver really shouldn't cause meaningful bloat unless they for some reason decide to replicate a large amount of the original driver's functionality - which would be a terribly dumb thing to do, unless the OEM driver is bad enough to be discarded wholesale (which is an entirely different discussion from this). Also, isn't it rather obvious that the current method of doing this is far too time- and resource intensive, given that we're not seeing updates at all?



As for your former paragraph, we should really be well past this in 2018. Sure, there are variations in how hardware is implemented, but modifying a driver for this should be dead simple - how hard can it be commenting out a section of the driver code, or just deleting it? Also, where's the harm in a driver exposing a SATA or USB controller that doesn't have any ports, or PCIe lanes that don't ever leave the substrate? Sure, it might pull a teeny-tiny amount of additional power, but likely not enough to ever matter. The only relevant issue here would be things people interact with - HID, audio and displays. If the driver switches your display output to a nonexistent Displayport output, that would be bad, but given how GPUs automatically detect connected displays, that really shouldn't be an issue. A more relevant problem would be adding a GPU-integrated audio device that the PC doesn't make use of, but given how easy it is to switch audio devices in W10 (and that any HDMI-equipped PC needs to have this option), again, this isn't a problem. PCs are inherently modular. Treating drivers as monolithic blocks is diametrically opposed to this, and really should be avoided as much as possible. Heck, the AMD GPU driver package lets you select/deselect a bunch of features. How hard would it be to implement a check against a database of devices for unsupported features?

Cheeseball I've got the Acer Nitro 5 with the Ryzen 2700U so I know how it feels. This mobile driver issue is pretty bad.

SetsunaFZero hmmm not sure if Intel is paying OEMs to stop development of AMD OEM drivers :rolleyes:

Not to toot my own horn, but I'm sure that my post was the one AMD was responding to when they made this statement, because they also commented it in my post about this issue.It really feels like they aren't listening because I myself have said many times that the chips in every Ryzen Mobile system - including the PRO chips - are exactly the same and the OEMs don't do anything to the drivers or chip besides limiting the TDP in some cases to keep the system from overheating (which isn't even the case for TDP limited devices). These limits are usually controlled by the BIOS anyways and that's why installing "unsupported" drivers yields in so much success without the device "exploding" or becoming bricked.The drivers that Acer, Dell, Asus and Co. release on their website are clearly just copy-pastes from what AMD sends them which shows that either AMD is the problem here by not coding drivers, or what I believe is the more realistic case, OEMs have deals with AMD (and maybe other brands) that stop AMD from posting those "reference" drivers to their website and for their own reasons they aren't uploading the drivers they're probably getting from AMD. The OEMs probably aren't updating the drivers on their websites because as you said, it's in their interest if your device doesn't work and you go out, running to buy a new one.The thing is that in the end, most of us are more pissed off about the driver situation because the devices are so unstable. From random freezing to BSODs, everything can happen which in my case often resulted in data loss - during a class/exam - and is my main reason for trying to get HP to let me switch out my device for a new one. I wouldn't mind some performance issues if at least my device were stable - but that isn't the case and it's the reason so many people aren't recommending AMD laptops and are even going as far as to creating posts to stop people from making the mistake they made.Please AMD, if you're reading, we love you as a company, Ryzen and Vega are great products, but situation with Ryzen Mobile currently is uncomprehensible and the company's response isn't any better. We'll only start buying your Mobile products again - and recommending them - when you fix this and formally apologize to the community for making them wait this long and triggering an internet-wide shitstorm that really shouldn't be necessary. Come on, you make intel and nVidia look pro-consumer, yuck.That's the only plausible reasoning there currently is to this situation: generic drivers are being "blocked" by OEMs through a close that was possibly created in cooperation with intel/nVidia to give AMD the bad name they're getting.The thing is that even if OEMs did a lot of changing with the drivers, things like config files exist so if the OEMs were worried about generic AMD drivers being installed, they would have to implement a config file like that with AMD in the software that possibly users could even configure and everyone would be happy.I feel you dude, if I'm not mistaken I have the most expensive Ryzen Mobile device on the market - the top-end HP EliteBook 755 G5 - and it hurts, so much that I'm currently working with HP to get the EliteBook 840/850 G5.I can imagine this being the case as intel has pulled this kind of bs before, nVidia has never done anything as illegal as this though...