Hi The setup, as in the subject, is supposed to boot a Winpe to install xp to a clean PC. I use the Ramdisk method (ie PXELinux pases the setup on to the M$ pxe loader and and boots WinPE) It works perfectly with evry other chipset, but Nvidias NForce 4. (tested 15 different) With NF4 it loads up well but the M$ PnP routine detects the Network management bus wrong (nvidia specific approach to first load a bus driver and after that the real NIC driver) I wouldn't mind too much, as the Nvidias chipset is known to be weird but... The same Ramdisk method WORKS all the way if booting the ramdisk from a CD. Like all the same files and everything.. but not over PXE -> TFTP but straight from CD. Now this indicates, that the PXE communication or the universal NIC driver has something to do with the problem. It could be, that the universal PXE NIC driver (or some part of it) stays loaded into the momory and blocks the M$ PnP from understanding the device HWID' right (it detects the device PCI/DEV../../ 0056 instead of 57 which is the correct bus id) and therefore failing to install the NIC on the bus. I understand, that this is probably M$'s PnP logic problem or even more the NVidias approach problem... but they don't care. Could any of You kind peaple help me out with a suggestion or some pointers? I'd be very thankfull:) Klaus
Hi The setup, as in the subject, is supposed to boot a Winpe to install xp to a clean PC. I use the Ramdisk method (ie PXELinux pases the setup on to the M$ pxe loader and and boots WinPE) It works perfectly with evry other chipset, but Nvidias NForce 4. (tested 15 different) With NF4 it loads up well but the M$ PnP routine detects the Network management bus wrong (nvidia specific approach to first load a bus driver and after that the real NIC driver) I wouldn't mind too much, as the Nvidias chipset is known to be weird but... The same Ramdisk method WORKS all the way if booting the ramdisk from a CD. Like all the same files and everything.. but not over PXE -> TFTP but straight from CD. Now this indicates, that the PXE communication or the universal NIC driver has something to do with the problem. It could be, that the universal PXE NIC driver (or some part of it) stays loaded into the momory and blocks the M$ PnP from understanding the device HWID' right (it detects the device PCI/DEV../../ 0056 instead of 57 which is the correct bus id) and therefore failing to install the NIC on the bus. I understand, that this is probably M$'s PnP logic problem or even more the NVidias approach problem... but they don't care. Could any of You kind peaple help me out with a suggestion or some pointers? I'd be very thankfull:) Klaus
I would seek help from the Motherboard manufacturer. I've got it working on MSI NF4 boards fine, So I would say it's a BIOS related issue or even the drivers you've included in the WinPE build. Note booting WinPE from a CD is quite different. It gives you the option to force the HAL type. Where as under the RAMdisk method it seems to be fixed as the HAL select menu (F7/F5) options don't work at boot up. Also make sure you're NOT specifying the "keeppxe" option in the pxelinux config. Other thing is that the PXE unloading mechanism is broken in the BIOS? Does RIS work okay? Rob -----Original Message----- Hi The setup, as in the subject, is supposed to boot a Winpe to install xp to a clean PC. I use the Ramdisk method (ie PXELinux pases the setup on to the M$ pxe loader and and boots WinPE) It works perfectly with evry other chipset, but Nvidias NForce 4. (tested 15 different) With NF4 it loads up well but the M$ PnP routine detects the Network management bus wrong (nvidia specific approach to first load a bus driver and after that the real NIC driver) I wouldn't mind too much, as the Nvidias chipset is known to be weird but... The same Ramdisk method WORKS all the way if booting the ramdisk from a CD. Like all the same files and everything.. but not over PXE -> TFTP but straight from CD. Now this indicates, that the PXE communication or the universal NIC driver has something to do with the problem. It could be, that the universal PXE NIC driver (or some part of it) stays loaded into the momory and blocks the M$ PnP from understanding the device HWID' right (it detects the device PCI/DEV../../ 0056 instead of 57 which is the correct bus id) and therefore failing to install the NIC on the bus. I understand, that this is probably M$'s PnP logic problem or even more the NVidias approach problem... but they don't care. Could any of You kind peaple help me out with a suggestion or some pointers? I'd be very thankfull:) Klaus
There are issues with a number of versions of the PXE BIOS used on the NIC hardware for NF4 and 2200 chipsets. Those I've run into mask the IRQ or some registers, and after booting the hardware can be seen but isn't controllable. Worse is the fact that in every instance I've seen this it's semi-random. Check your vendor/OEM for updated SBIOS that will include the updated PXE BIOS. Of course, your problem may not be related... /eli -----Original Message----- From: syslinux-bounces at zytor.com on behalf of Klaus J?gi Sent: Sun 3/26/2006 4:24 AM To: syslinux at zytor.com Subject: [syslinux] PXE -> tftp -> WinPE vs NForce 4 Hi The setup, as in the subject, is supposed to boot a Winpe to install xp to a clean PC. I use the Ramdisk method (ie PXELinux pases the setup on to the M$ pxe loader and and boots WinPE) It works perfectly with evry other chipset, but Nvidias NForce 4. (tested 15 different) With NF4 it loads up well but the M$ PnP routine detects the Network management bus wrong (nvidia specific approach to first load a bus driver and after that the real NIC driver) I wouldn't mind too much, as the Nvidias chipset is known to be weird but... The same Ramdisk method WORKS all the way if booting the ramdisk from a CD. Like all the same files and everything.. but not over PXE -> TFTP but straight from CD. Now this indicates, that the PXE communication or the universal NIC driver has something to do with the problem. It could be, that the universal PXE NIC driver (or some part of it) stays loaded into the momory and blocks the M$ PnP from understanding the device HWID' right (it detects the device PCI/DEV../../ 0056 instead of 57 which is the correct bus id) and therefore failing to install the NIC on the bus. I understand, that this is probably M$'s PnP logic problem or even more the NVidias approach problem... but they don't care. Could any of You kind peaple help me out with a suggestion or some pointers? I'd be very thankfull:) Klaus _______________________________________________ SYSLINUX mailing list Submissions to SYSLINUX at zytor.com Unsubscribe or set options at: http://www.zytor.com/mailman/listinfo/syslinux Please do not send private replies to mailing list traffic.