Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
hardwareissues [2009/08/28 14:55] tal.aloni a detailed workaround for nforce NIC |
hardwareissues [2010/11/13 14:14] (current) tal.aloni fixed typo |
||
|---|---|---|---|
| Line 15: | Line 15: | ||
| ==== How to Fix ==== | ==== How to Fix ==== | ||
| - | 3com deliver a firmware upgrade and can be downloaded [[ftp://ftp.3com.com/pub/nic/3c90x/util430.exe|here]]. | + | 3com deliver a firmware upgrade which used to live [[ftp://ftp.3com.com/pub/nic/3c90x/util430.exe|here]]; however the upgrade is apparently no longer available direct from 3Com but copies can still be found on [[http://www.filewatcher.com/m/util430.exe.1945735.0.0.html|other sites]]. This file has to be decompressed and run in a real dos mode. |
| - | This file have to be decompressed and run in a real dos mode. | + | |
| Then run //mbaflash.exe// | Then run //mbaflash.exe// | ||
| Line 34: | Line 33: | ||
| The MBA version is now upgraded to v4.30, gpxe can now be loaded. | The MBA version is now upgraded to v4.30, gpxe can now be loaded. | ||
| + | === Alternate strategy booting MEMDISK from GRUB === | ||
| + | |||
| + | Additional notes from a user: | ||
| + | In this instance, I could not use a 3com 3c90 to pxe boot, at all, it would just hang, even though I flashed from 4.00 to 4.30 using memdisk, I still could not pxe boot, so somehow I found myself a newer mbaflash.exe | ||
| + | This was all done on Debian. | ||
| + | |||
| + | Download a newer mba for the 3com cards (4.31) | ||
| + | curl -O ftp://ftp.hp.com/pub/softlib/software1/ob656/ob656en/3cmba431.exe | ||
| + | |||
| + | Extract with 7zip: | ||
| + | 7z x 3cmba431.exe | ||
| + | The first 32 bytes of firmware.img is just the COPYDISK header, so skip it | ||
| + | dd if=firmware.img bs=32 skip=1 of=dos.img | ||
| + | If you can boot from a disk on the machine that has the card you're trying to flash, that would be good, since you can't PXE boot in theory. | ||
| + | Hopefully you're using some Linux and you have syslinux and grub2 installed. | ||
| + | |||
| + | Add memdisk: | ||
| + | sudo cp /usr/share/syslinux/memdisk /boot/ | ||
| + | |||
| + | Add the dos diskimage you're going to be flashing from: | ||
| + | sudo mkdir /boot/images | ||
| + | sudo cp dos.img /boot/images | ||
| + | |||
| + | Update grub: | ||
| + | sudo grub-update | ||
| + | |||
| + | Now you can theoretically reboot using memdisk to boot into DOS to flash the 3c90 rom that you couldn't pxeboot from before | ||
| ===== Nvidia nForce ===== | ===== Nvidia nForce ===== | ||
| Line 43: | Line 69: | ||
| After installing Microsoft iSCSI Boot initiator and executing sanbootconf (and thus making sure the NVENETFD service is started at boot) booting the image over iSCSI will result in BSOD (0x0000007b). This happens even though the NVENETFD service is loaded during boot. | After installing Microsoft iSCSI Boot initiator and executing sanbootconf (and thus making sure the NVENETFD service is started at boot) booting the image over iSCSI will result in BSOD (0x0000007b). This happens even though the NVENETFD service is loaded during boot. | ||
| - | This is tested on Windows XP x64. | + | This was tested on Windows XP x64. |
| ==== Symptoms (AOE) ==== | ==== Symptoms (AOE) ==== | ||
| Line 51: | Line 77: | ||
| ==== How to Fix ==== | ==== How to Fix ==== | ||
| - | the nvnetbus service has to be activated, and loaded before NVENETFD: | + | the nvnetbus service has to be started before NVENETFD: |
| in order to do this, the user has to be familiar with CurrentControlSet\Services Subkey Entries (http://support.microsoft.com/kb/103000) | in order to do this, the user has to be familiar with CurrentControlSet\Services Subkey Entries (http://support.microsoft.com/kb/103000) | ||
| and with CurrentControlSet\Control\GroupOrderList Entries (http://technet.microsoft.com/en-us/library/cc976063.aspx). | and with CurrentControlSet\Control\GroupOrderList Entries (http://technet.microsoft.com/en-us/library/cc976063.aspx). | ||
| - | overview of the steps required to make nvnetbus being loaded before NVENETFD: | + | overview of the steps required to make nvnetbus being started before NVENETFD: |
| + | <code> | ||
| 1. navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NVENETFD: | 1. navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NVENETFD: | ||
| a. remember the value of Tag (priority) and increment it by 1 | a. remember the value of Tag (priority) and increment it by 1 | ||
| Line 64: | Line 92: | ||
| 3. navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GroupOrderList\NDIS: | 3. navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GroupOrderList\NDIS: | ||
| a. increment the number of Tags (first four bytes), and add the new tag we just added for NVENETFD at the end of the list (you're adding four more bytes at the end). | a. increment the number of Tags (first four bytes), and add the new tag we just added for NVENETFD at the end of the list (you're adding four more bytes at the end). | ||
| + | </code> | ||
| * Another option is to use the RIS driver for the nForce card (not verified). The simplest fix is to simply use another network adapter. | * Another option is to use the RIS driver for the nForce card (not verified). The simplest fix is to simply use another network adapter. | ||
| Line 78: | Line 106: | ||
| iSCSI support, for example, is a good candidate for disabling, as it uses a lot of space. | iSCSI support, for example, is a good candidate for disabling, as it uses a lot of space. | ||
| + | ===== Realtek RTL8111D ===== | ||
| + | |||
| + | ==== Symptoms ==== | ||
| + | gpxe undionly driver v1.0.1 hangs when "initialising devices..." (although the chipset declares Intel UNDI v2.1 capability upon boot). | ||
| + | |||
| + | ==== How to Fix ===== | ||
| + | * Buy another NIC. Really. I tried two and both did never work reliably (link problems -- either no link detected or DHCP answers missed -- could be a firmware issue, but how do I fix the firmware when I need to boot with that NIC??). | ||
| + | * The undionly solution seems to be broken with that chipset. Use r8169 driver instead. | ||
| + | |||
| + | ===== Broadcom NetXtreme II BCM 57711 (10 Gbit) ===== | ||
| + | |||
| + | Network card in HP Proliant BL460c G6. | ||
| + | |||
| + | ==== Symptoms ==== | ||
| + | |||
| + | gPXE with undionly.**kk**pxe driver fails to access network. | ||
| + | |||
| + | ==== How to Fix ===== | ||
| + | |||
| + | Use undionly.**k**pxe instead. Please note that undionly.kpxe does not support cached DHCP settings, i e "set use-cached 1" will not work. | ||
