Problems after update from 0.32 to 1.2.0
-
Are there directions for changing these? Where do i get them?
Thank you for your help!
-
You already have them. They downloaded to the /tftpboot directory when you reinstalled. There’s normally no need to change anything in there.
If you’re handing out your bootfile and next-server information via Windows DHCP, you’d simply go into that, go into scope options, and set option 067 to one of those files and then test it.
If you’re using dnsmasq, you’d need to edit the ltsp.conf file and change the boot-file name, and then restart dnsmasq.
Look through this: [url]http://fogproject.org/wiki/index.php/Modifying_existing_DHCP_server_to_work_with_FOG[/url]
Let us know if you have issues. -
I feel like i am sooooo close!!
I used snponly.efi and now i can get to the boot menu. but any option i choose just loops back to the menu.
-
[quote=“Vickie Osbornr, post: 46271, member: 29486”]I feel like i am sooooo close!!
I used snponly.efi and now i can get to the boot menu. but any option i choose just loops back to the menu.[/quote]
What is the model of this UEFI target-host?
-
Asus X200M
-
Are you using the on-board NIC or an add-in NIC?
I read in the specs for this device that the on-board is only 100Mbps so this is why I ask.
-
we are using the onboard nic
-
Is “protected boot” or “secure boot” or “secure boot state” or “secure boot control” enabled in the firmware ? If they are enabled, disable them and try again.
Is there a setting for “Launch CSM” ? Can you enable that and try again?
-
secure boot is disabled and Launch CSM is enabled.
init.xz … flashes on screen and goes back to boot menu -
Can you try to grab a newer kernel via the FOG Settings page? try one for x86_x64 first and see if that works. If not, then try just x86, then just x64.
-
ok… i have done that and now we are getting stuck on a trace screen. and that’s all my computers are getting stuck there when booting up.
-
then revert back to the older kernel.
-
how do i know what the old kernel was?
-
here is the screen
[url=“/_imported_xf_attachments/1/1930_20150427_142141_resized_1.jpg?:”]20150427_142141_resized_1.jpg[/url]
-
FOG 1.2.0 used kernel [SIZE=13px][FONT=arial][COLOR=#262626]3.14.2[/COLOR][/FONT][/SIZE]
[SIZE=13px][FONT=arial][COLOR=#262626]However, before you do that, did you change the boot-file back to the previous one?[/COLOR][/FONT][/SIZE]
[SIZE=13px][FONT=arial][COLOR=#262626]The EFI boot files are not compatible with BIOS type firmware. [/COLOR][/FONT][/SIZE]
-
yes i put it back on the undionly.kpxe
-
The kernel that you’re using is 64 bit? The four FOG logos at the top tell me you’re not using a 3.14.2 kernel.
That said, there are newer kernels.
On your FOG Server can you run:
[code]wget -O /var/www/html/fog/service/ipxe/bzImage http://downloads.sourceforge.net/project/freeghost/KernelList/bzImage
wget -O /var/www/html/fog/service/ipxe/bzImage32 http://downloads.sourceforge.net/project/freeghost/KernelList/bzImage32[/code] -
I updated the files with the links that Tom put up and every thing is running for my older machines again.
So what are the options if I have inventory with computers of both older machines and machines that boot from EFI? is there a way to use fog so it can do both? -
It is possible but you need to run SVN and DHCP user classes as described in this thread. [url]http://fogproject.org/forum/threads/fog-ver-1-2-0-uefi-legacy-boot.11566/[/url]
-
There is.
The method you need to use depends on your setup.
I’ve been working on documentation for this, but I haven’t had luck with UEFI yet on my machines. Luckily, legacy mode works on them… I was just trying to get ahead of the game and be ready for the next shipment of computers that will be UEFI only. I suppose I’ll have to wait until they are here.
Look at this thread, I’ve been researching pretty heavily and filling it up with junk that is relevant: [url]http://fogproject.org/forum/threads/undionly-kpxe-and-ipxe-efi.12607/[/url]
