Problems after update from 0.32 to 1.2.0
-
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]
-
These new machines that i have gotten (ASUS X200M) are supposed to be legacy compatible but it hasn’t worked. I have been on the phone with ASUS and they don’t have an answer to why its not functioning. I have thought about setting up a separate server on a closed network just to image these machines. Do you think that might work?
-
It’s possible… but… that’s so tedious… and you’d be dedicating resources JUST for this problem… it’s not efficient nor clean.
I’d recommend… if you don’t want to change your DHCP configuration, making a USB bootable FOG stick, and have it configured to use the files that these machines need.
This would not require you to devote so much equipment to the problem (just a flash drive), and would allow you to use your existing FOG server. There’s a thread around here somewhere about it that is recent… I’ll find it and post.
-
Check out this thread:
[url]http://fogproject.org/forum/threads/help-usb-boot-fog.12778/[/url]
-
Today all machines are getting hung at this screen
[url=“/_imported_xf_attachments/1/1938_20150429_095128_resized.jpg?:”]20150429_095128_resized.jpg[/url]
-
Are you sure it’s ALL computers?? They won’t boot at all? Or just won’t image?
Is your boot file still undionly.kpxe ?
-
Optionally, you could try undionly.kkpxe
That boot file will work with anything that undionly.kpxe will work with. It’s recommended for buggy bios. I use it in my building because of some dumb Lenovos we have.
