The nodes will not PXE boot. I see the standard install loads the Realtek r8169 driver. Based on past experience, my hardware requires the r8168 driver.
Can the NIC driver be changed in qlustar?
Do I execute the following commands at the root@cl-head~# prompt. Or from a different location?
apt-get install r8168 -dkms rmmod r8169 lspci -s 3:00.0 -vv (verifies the r8168 driver is loaded) reboot
thanks
"B" == Bob Johnson xyzemail19@gmail.com writes:
B> The nodes will not PXE boot.
Up to what stage do the nodes get in the boot process?
B> I see the standard install loads the Realtek r8169 driver. Based B> on past experience, my hardware requires the r8168 driver.
B> Can the NIC driver be changed in qlustar?
The correct driver is automatically selected by udev according to the uevent message generated for the device. There is no need to change it, since the correct one should be loaded if it is present.
B> Do I execute the following commands at the root@cl-head~# B> prompt. Or from a different location?
B> apt-get install r8168 -dkms rmmod r8169 lspci -s 3:00.0 -vv B> (verifies the r8168 driver is loaded) reboot
This won't help.
"B" == Bob Johnson xyzemail19@gmail.com writes:
B> The nodes will not PXE boot.
Up to what stage do the nodes get in the boot process?
B> I see the standard install loads the Realtek r8169 driver. Based B> on past experience, my hardware requires the r8168 driver.
B> Can the NIC driver be changed in qlustar?
The correct driver is automatically selected by udev according to the uevent message generated for the device. There is no need to change it, since the correct one should be loaded if it is present.
B> Do I execute the following commands at the root@cl-head~# B> prompt. Or from a different location?
B> apt-get install r8168 -dkms rmmod r8169 lspci -s 3:00.0 -vv B> (verifies the r8168 driver is loaded) reboot
This won't help.
"B" == Bob Johnson xyzemail19@gmail.com writes:
B> The nodes will not PXE boot.
Up to what stage do the nodes get in the boot process?
B> I see the standard install loads the Realtek r8169 driver. Based B> on past experience, my hardware requires the r8168 driver.
B> Can the NIC driver be changed in qlustar?
The correct driver is automatically selected by udev according to the uevent message generated for the device. There is no need to change it, since the correct one should be loaded if it is present.
B> Do I execute the following commands at the root@cl-head~# B> prompt. Or from a different location?
B> apt-get install r8168 -dkms rmmod r8169 lspci -s 3:00.0 -vv B> (verifies the r8168 driver is loaded) reboot
This won't help.
R> Up to what stage do the nodes get in the boot process?
Remotely login to cl-head from my workstation and start qluman. i.e. qluman-qt &
Enter password and proceed to manage host - new hosts
None of the nodes are seen in the Unknown Mac area.
Enter a hostname and mac address for each of the MoBo nic's into the Unknown MAC window
Open Enclosure View and set each node to standard node
Boot each node and each node reports a PXE-E51 error
Tried pinging each IP address and no response.
"B" == Bob writes:
R> Up to what stage do the nodes get in the boot process?
B> Remotely login to cl-head from my workstation and start qluman. B> i.e. qluman-qt &
B> Enter password and proceed to manage host - new hosts
B> None of the nodes are seen in the Unknown Mac area.
B> Enter a hostname and mac address for each of the MoBo nic's into B> the Unknown MAC window
B> Open Enclosure View and set each node to standard node
B> Boot each node and each node reports a PXE-E51 error
That means, your nodes don't even get as far as booting the linux kernel, so can't be a driver issue. Most likely causes:
a) The DHCP server on the head-node doesn't run. b) The nodes are physically not connected to the cluster BOOT network on which the head-node's DHCP server listens to requests (maybe you have multiple networks wrongly attached).
B> Tried pinging each IP address and no response.
-
Bob Johnson -
Roland Fehrenbacher -
xyzemail19＠gmail.com