@sebastian-roth OK I can pxe boot these 7240s no problem. I set the bios back to factory, put laptop in bios (legacy mode), enabled pxe booting on built in network interface and then booted into FOG registration.
This is just for documentation purposes: this laptop has bios A21 with 4GB of ram and a 128GB SSD.
@tom I guess the first question I have is, Is the firmware updated on the 7240s?
When you say it suddenly stopped, can you determine an event that could have happened between when it did and when it didn’t work? (like upgrading fog??)
I have the 7240s on my campus so if needed I can go grab one and test. The only time I’ve personally seen this happen is when the system was a Lenovo and in uefi mode the system would download 69% of init.xy and then switch to the black screen and cursor.
Is this the only hardware that is doing this behavior or is it all?
BTW: The video is perfect since we can see how you got to the error. Bravo.
@andrewg78 There were some tweaks to the API between 1.4.2 and 1.4.4, but I can’t tell you off the top of my head. You would be better to move to 1.4.4 anyway outside of the API stuff. There were some issues with 1.4.2 that was address in 1.4.3 and finally in 1.4.4.
The developers are still on holiday, but let me see if I can ping one of them to kickstart the news server.
@sebastian-roth These files were successful in creating a platform with an expandable filesystem for FOS. I was able to install the Dell CCTK drivers but they failed to work. I’m still working on this project in the background, cause it would be an interesting option. From a FOS standpoint I can do what is needed so that is a success so great job!
@andrewg78 AFAIK no changes have been made to the API since 1.4.4 was released. The 1.5.0 branch has a few minor bug fixes, but was mainly focused on the new web gui.
@tywyn said in Computer does not see DHCP on PXE-Boot, but it does with Windows running:
Your hint to put a dump hub/switch between client and network dose did solve the problem as well.
FWIW: This is a quick test we can use to see if standard spanning tree is the issue. The dumb switch will keep the building switch from transitioning during the boot of FOS.
@enorum You get curl for windows, you can create your own PHP page that makes the call, or use powershell if you are so inclined with the Invoke-RestMethod function. There are a number of ways to DIY a solution around this.
lets start with some background information.
I assume that you see it download bzImage (linux OS) and init.zx (virtual hard drive) but then it doesn’t proceed from there.
Lets start there and see where we go with the new information.
@anthony-delarosa Yes I’m available. Make sure you have a good baseline of usage. Your vmware trending is good enough. If the process works correctly you should not see all of those httpd instances in top since it should spawn php-fpm instances.
Is your check in time still set to FOG defaults?
@george1421 I just found a compiled version of dnsmasq 2.76: ftp://ftp.pbone.net/mirror/rnd.rajven.net/centos/7.0.1406/os/x86_64/dnsmasq-2.76-1cnt7.x86_64.rpm
I can’t speak to the efficacy of the rpm, but it would jump you ahead of the compiling of the source. I’m going to still work on the compiler part, but only for my satisfaction
@george1421 I’m currently stuck on libidn. The compiler is not seeing it, but its installed. This may take me a bit more to understand why.
@msi I’m doing a test install on a centos machine right now. Let me see what needs to be altered for centos 7
@msi OK the instructions are for ubuntu, but for centos make sure the development tools are installed.
yum -y groupinstall "Development Tools"
@msi what version of linux are you using? You may need to install the developer tools to compile the code .
@mikec96 first step is the network connection tool. You need to make linux happy first then rerun the fog installer to get fog realigned with the new IP address.
@mikec96 you need to get a static IP address defined for your fog server. That is the first part of the issue. Your dhcp server settings appear correct, so that isn’t the problem.
How did the images get into the /images directory? And I assume when you say there are images in there, the the directory looks like [/images/<image_name1> /images/<image_name2> and so on]?
Please review your isc-dhcp server configuration file. I’m suspecting that its not set. Refer to this example for the proper settings: https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence#Example_1
@aksl said in Imposible to boot from hard drive:
UEFI 32 bit file name : ipxe32.efi
UEFI 64 bit file name : ipxe64.efi
What is this? These are not standard FOG boot file names. For x64 the boot file should be ipxe.efi. And for x86 the boot file should: i386-efi/ipxe.efi