FOG 1.0.1 and older NICs
-
We have FOG 1.0.1 rolled out, but since have been having issues with imaging some of our older PCs with Intel NICs. The machines will get their IP, start to PXE, start to load, then gives the error “could not boot: no such file or directory ([url]http://ipxe.org/2d8c203b)”[/url]. Newer PCs image fine. HP dc6000 and d530s are two troubled devices.
FOG: 1.0.1 on Fedora 12.
-
This error is reporting specifically because of your BIOS, not because of your NIC.
Check and see if there’s an updated BIOS for your motherboard and if there is flash it, and try again.
If it’s still an error, you may need to comment the picture getting line on BootMenu.class.php.
I’ll give more information on what and where as we get more information from you.
Weird that you’re having issues with HP DC6000’s as I’ve got about 250 of them and they all, from what I’ve found, work fine with 1.x.x.
-
What BIOS version are you running on them?
-
System BIOS 786G2 v01.09
-
Updated the BIOS to 786G2 v2.02 on the dc6000 without a change.
-
[quote=“Scott B, post: 28719, member: 15315”]Updated the BIOS to 786G2 v2.02 on the dc6000 without a change.[/quote]
Error now says “Error 0x040ee119 ([url]http://ipxe.org/040ee119[/url])”
-
[quote=“Scott B, post: 28726, member: 15315”]Error now says “Error 0x040ee119 ([url]http://ipxe.org/040ee119[/url])”[/quote]
[url]http://fogproject.org/forum/threads/040ee119-error-on-boot.10493/page-2#post-28487[/url]
-
[quote=“Jaymes Driver, post: 28734, member: 3582”][url]http://fogproject.org/forum/threads/040ee119-error-on-boot.10493/page-2#post-28487[/url][/quote]
I tried the 5 files located in the f473-good directory and each one takes me back to “could not boot: no such file or directory ([URL=‘http://ipxe.org/2d8c203b)%E2%80%9D’]http://ipxe.org/2d8c203b)”[/URL].
-
need more information.
How did you try those 5 files?
What FOG Version are you using?
Did you rename the files as your /tftpboot/undionly.kpxe?
-
[quote=“Tom Elliott, post: 28743, member: 7271”]
How did you try those 5 files?[/quote]Downloaded each file then used ssh to transfer them to our fog server’s /tftpboot directory.
[quote=“Tom Elliott, post: 28743, member: 7271”]
What FOG Version are you using?[/quote]v1.0.1
[quote=“Tom Elliott, post: 28743, member: 7271”]
Did you rename the files as your /tftpboot/undionly.kpxe?[/quote]I didn’t rename the files other then the orginial undionly.kpxe to undionly.kpxe.bak. I then changed the file name for PXE in my DHCP server to match the file I wanted to try. ipxe.kkpxe, ipxe.kpxe, ect…
-
what type of DHCP server are you using?
can you retrieve the file with this command?
[FONT=Consolas]tftp -i <server IP> get default.ipxe[/FONT] -
[quote=“Junkhacker, post: 28753, member: 21583”]what type of DHCP server are you using?[/quote]
The host OS is SuSe Linux Enterprise Server and the DHCP server itself is part of Novell’s Open Enterprise Server.
-
[quote=“Scott B, post: 28754, member: 15315”]The host OS is SuSe Linux Enterprise Server and the DHCP server itself is part of Novell’s Open Enterprise Server.[/quote]
You’re going to have fun with Novell.
I ended up using dnsmasq. I also had to rename my unidonly.kpxe file to undionly.0 because Novell has a limit on the characters that can be entered for a name of a boot file. I believe the limit is 12. So that wouldn’t have affected the ipxe files.
But that was to solve my issues of not being able to find the file, I don’t think that is the case here, I am just letting you know I too have troubles using Novell dhcp.
I ended up using the f3d24_QUOTA_20-GOOD, my hardware is between 5-10 years old depending on parts of the building
-
a link to Jaymes’s wiki on dnsmasq [url]http://www.fogproject.org/wiki/index.php/Setting_up_ProxyDHCP[/url]
-
What version of Novell are you running?
Novel 6.5 prior to sp2 apparently has a file character limit to 12, so you may want to try relabeling the file as undionly.0 or something similar.
-
[quote=“Tom Elliott, post: 28758, member: 7271”]What version of Novell are you running?
Novel 6.5 prior to sp2 apparently has a file character limit to 12, so you may want to try relabeling the file as undionly.0 or something similar.[/quote]
We are past Novell NetWare and now on their Linux flavor of servers, the base is SuSe Linux, and the Novell “stuff” that was NetWare is now called Open Enterprise Server. So…
Novell Open Enterprise Server 11 (x86_64)
VERSION = 11.1
PATCHLEVEL = 1
SUSE Linux Enterprise Server 11 (x86_64)
VERSION = 11
PATCHLEVEL = 2 -
[quote=“Scott B, post: 28759, member: 15315”]We are past Novell NetWare and now on their Linux flavor of servers, the base is SuSe Linux, and the Novell “stuff” that was NetWare is now called Open Enterprise Server.[/quote]
I don’t have that luxury I am stuck on 6.5
We are looking to move to AD.
-
Yay AD
-
[quote=“Jaymes Driver, post: 28760, member: 3582”]I don’t have that luxury I am stuck on 6.5
We are looking to move to AD.[/quote]
Long live NetWare, still my fav server OS. You can still keep eDirectory and not deal with AD. Actually I think, even eDirecotry will now run on a Windows host OS.
-
[quote=“Scott B, post: 28762, member: 15315”]Long live NetWare, still my fav server OS. You can still keep eDirectory and not deal with AD. Actually I think, even eDirecotry will now run on a Windows host OS.[/quote]
Thanks for the heads up, My bosses only concern is keeping Groupwise at the moment -.-
You may want to check the read and write permissions on that boot file.
Try to grab the file from another machine on the network.
If it’s windows you need to enable the tftp client in the add/remove settings for the command to complete.
[code]
tftp x.x.x.x get undionly.kpxe[/code] where x.x.x.x is your fog server, you may want to change the undionly.kpxe part to your respective file at the moment.If you want to try it from linux use Junkhackers command above.
