Problems after update from 0.32 to 1.2.0
I have updated to the current 1.2.0 and i am unable to download or create a new image. I can register a host. when i try to do a quick image it does not accept the user names and passwords we have registered for mobile access. Any thoughts?
Are we working with this one?
What model of computer are you trying to network boot?
Are we still using 1.2.0 ?
Does it work at all? Can you get to the web UI ?
ericbarker last edited by
I am assisting Vickie… yes the secure boot is disabled… there is not a Launch CSM… we still are not able to get to the menu… it does com up with succeed to download NBP file…
but then it just jumps right to booting windows 7
A Former User last edited by
This post is deleted!
It has been all machines. I have been getting calls from all over the buildings where machine are hung on that screen i uploaded the lase image of. I have tried the undionly.kpxe.INTEL, undionly.kpxe, undionly.kkpxe and nothing seems to work today. I finally put the old pxelinux.0 back in because it would just let the machines load up. Now i have to figure out how to get things running again so we can image. Everything was working when I left yesterday. I’m not sure what has changed. I had the undionly.kpxe.INTEL working with all the older machines except 1 model. Now I’m back to square one.
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.
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 ?
Today all machines are getting hung at this screen
Check out this thread:
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.
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?
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]
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]
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?
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]
yes i put it back on the undionly.kpxe
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]
here is the screen
how do i know what the old kernel was?