06-02-2016, 05:03 AM
(06-02-2016, 05:00 AM)Surge Wrote:Possible explanation: If you have no other devices in the network, it was likely trying to boot off of ITSELF.(06-02-2016, 04:57 AM)SilverOtter 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.I still fail to see how netboot was convincing the BIOS to boot via the receiver for my wireless keyboard.
Also, that netboot problem sounds like you've got something configured on the network that is mistakenly being recognized as a windows netboot server.
Netboot is just a mode of booting up the OS, only across a network. If the BIOS is set up in some way, attempting a Netboot will come first before scanning the hard drives for a local OS.
Linux Crime Squad