06-02-2016, 04:57 AM
(06-02-2016, 04:29 AM)Surge Wrote:Well then it's a hardware issue. Sometimes small damage to the card won't completely destroy all it's functionality, but it will cause the driver to report every chance it gets that a graphics extension that SHOULD be working isn't.(06-02-2016, 04:26 AM)SilverOtter Wrote: The driver had a bug, the PSU was either cheap or faulty, Windows, just Windows (why have failures be your fault, when we can do it for you!), and something set the BIOS to Netboot (which does work over Wi-Fi if the motherboard loads the drivers involved).
The drivers issue persisted for MONTHS across multiple versions and installs of the drivers until I outright replaced the hardware. Yes I am currently in the process of replacing that PSU right now because it has obviously burned itself out. FUCK Windows errors. That happened to me TWICE and I still don't understand how or why, just that it was annoying as hell to right and one time it actually managed to boot into an unauthorized version of Windows.
Also, that netboot problem sounds like you've got something configured on the network that is mistakenly being recognized as a windows netboot server.
Linux Crime Squad