2012-08-23, 09:49
Good evening all. Onto another round of questions.
Started looking at utilising wireless boot this evening, but hit a bit of a snag. Using latest compiled git as at about 2 hours ago. ipxe.usb version with embedded script.
Script was essentially:
It successfully connects to the wireless, downloads the ipxe menu over http without a problem, but none of the further options in the menu successfully load, it just displays the requested filename, and hangs. I haven't done any extensive testing yet, but two laptops (1x Sony, 1x Toshiba), both exhibited identical symptoms. The menu options are all http based, and range from sanboot ISO's to memdisk ISO & Images. Using one of the sanboot options it appears to register the SAN device, displayed the ISOLINUX message, 'then' hung. All of these menu options work fine if I revert to standard network boot via ethernet with undionly.
Any thoughts? I've already gone home for the night, but will do some more troubleshooting when I have time. Likewise I'll need to recheck if the two test units may have shared the same wireless chipset or not.
Started looking at utilising wireless boot this evening, but hit a bit of a snag. Using latest compiled git as at about 2 hours ago. ipxe.usb version with embedded script.
Script was essentially:
Code:
#!ipxe
set net0/ssid WIFISSID
set net0/key WIFIKEY
autoboot
It successfully connects to the wireless, downloads the ipxe menu over http without a problem, but none of the further options in the menu successfully load, it just displays the requested filename, and hangs. I haven't done any extensive testing yet, but two laptops (1x Sony, 1x Toshiba), both exhibited identical symptoms. The menu options are all http based, and range from sanboot ISO's to memdisk ISO & Images. Using one of the sanboot options it appears to register the SAN device, displayed the ISOLINUX message, 'then' hung. All of these menu options work fine if I revert to standard network boot via ethernet with undionly.
Any thoughts? I've already gone home for the night, but will do some more troubleshooting when I have time. Likewise I'll need to recheck if the two test units may have shared the same wireless chipset or not.