Slashdot Mirror

← Back to Stories (view on slashdot.org)

Antisocial Hardware?

Posted by Cliff on from the it-really-shouldn't-do-that dept.

87C751 asks: "Over the weekend, I happened upon a deal: 10/100 PCI NICs for $1.99. I bought two and installed one in my Linux box. The box came up to POST, and the new NIC started looking for a DHCP server (which I thought was cute, if useless). Once that timed out, boot sequence continued to the message "NTLDR not found"! In an attempt to do a PXE net boot, the new NIC had -rewritten my boot sector!- Granted, a few minutes with a GRUB boot floppy set things right again, but why in the world is J. Random piece of hardware arrogant enough to frob my disc? Has anyone else been bitten by antisocial hardware?"

3 of 94 comments (clear)

  1. The Dingo Ate Your Boot Sector by HotNeedleOfInquiry · · Score: 5, Insightful
    The NIC did not eat your boot sector. I'm very familiar with the design that appears on the web page you posted and there's no way that the NIC could have done it. It has NO way of storing executable code onboard unless there's a flash or EPROM chip installed.

    I don't know how your boot sector got trashed, but it wasn't the NIC hardware.

    --
    "Eve of Destruction", it's not just for old hippies anymore...
  2. Re:Beware the cheap NIC by HotNeedleOfInquiry · · Score: 5, Insightful
    "Yes, but there's no centralized MAC address authority"

    Of course there is. It's the IEEE. I know because I shelled out 1600 hard earned dollars for 2^24 MAC numbers. Need their URL?

    --
    "Eve of Destruction", it's not just for old hippies anymore...
  3. Jumping to Conclusions by penguinboy · · Score: 5, Insightful

    Once that timed out, boot sequence continued to the message "NTLDR not found"! In an attempt to do a PXE net boot, the new NIC had -rewritten my boot sector!-

    And you know this how, exactly? Did you try rebooting the machine with the card removed? I had a similar problem with an Intel NIC that wanted to netboot, but fixing the problem was a simple matter of telling the card not to netboot in its BIOS setup. Obviously it wouldn't be impossible for a NIC to rewrite your boot sector (since it's running unrestricted code when the system BIOS initializes it) but it's extremely unlikely.