This is an old revision of the document!
====== Michael Decker: Driver Development ====== ==== Week 8 ==== ---- === July 16 === This morning I created a new Windows disk image to test AoE with. The last image I made was on a different machine, so that wouldn't work. The AoE driver seemed most sensitive to the change of hardware. I connected a spare hard disk & cd drive to the test machine. I booted off a Windows XP x64 cd, created a 3GB partition, and installed there (it barely fit!). I then downloaded the AoE driver on my development machine, copied via a pen drive, and installed it. Then, I rebooted the test machine with an Ubuntu Live cd, mounted an SMB folder from the vblade server, then dd'd the 3GB partition into a file in the SMB folder. I then reconfigured vblade to use the new image, removed the disc from the test machine, and rebooted it. I watched in amazement as it booted up Windows without a hitch. 8-o I then recompiled my eepro100 driver and copied to the tftp path, and rebooted the test machine. Again, it booted up Windows using my latest driver. I ran [[http://homepage.virgin.net/roy.longbottom/index.htm|a disk benchmark]] and defragged the drive without a hitch. My two eepro100 cards successfully tested: * 82559-based PCI card - Vendor ID: 8086 Device ID: 1229 * 82558-based PCI card - Vendor ID: 8086 Device ID: 1229 They operate flawlessly when installed alone. If I install them both, then it will work correctly //if// the first NIC booted by gPXE is connected. If the first NIC times out waiting for link-up, the second NIC times out AoE booting. I'm not convinced this is a problem with my driver.
