Unable to upload first image
-
I have managed to get a screengrab of the kernal panic error. Sorry for the size
[url=“/_imported_xf_attachments/1/1164_Kernal Panic.png?:”]Kernal Panic.png[/url]
-
Please, has anyone seen this before?
I need to figure out why this Kernel Panic keeps happening or this project will be scrapped by my manager
I have tried building images on both VM and physical machines but each time I get this kernel panic. I managed to upload an image once but when I tried to deploy it I got the same ‘failed to sync’ error. This happened on both virtual and physical machines.
-
My guess is your pxelinux.0 method isn’t chaining properly to ipxe. That and the file is properly really old. A sneaky method you could try is to link the undionly.kpxe file to pxelinux.0:
[code]sudo mv /tftpboot/pxelinux.0 /tftpboot/pxelinux.0.WORKS
sudo ln -s /tftpboot/undionly.kpxe /tftpboot/pxelinux.0[/code]Then try booting.
It sounds to me like it’s trying to boot the init_32.xz with the bzImage which won’t work. That or it’s vice-versa trying to boot the init.xz with the bzImage32.
-
Have you tried to reinstalling Ubuntu? I have not seen a Kernel Panic using FOG before, but I have had a bad install of Ubuntu for no reason.
-
Yeah I have tried reinstalling 3 times now since Friday.
The command line you gave didn’t work as it says I have no PXElinux.0 file. Only a pxelinux.0.old file. Im just so frustrated with this but we desperately need it in my work
-
Did you try the information I gave?
[url]http://fogproject.org/forum/threads/unable-to-upload-first-image.11130/#post-33033[/url] -
Yes, the line:
sudo mv /tftpboot/pxelinux.0 /tftpboot/pxelinux.0.WORKS
fails as it says pxelinux.0 does not exist
-
That’s okay,
Follow the second line then.
-
OK tried that. Same issue. It now says:
tsc: Fast TSC calibration failed then doesn’t do anything before displaying the kernel panic again
-
Just a quick update but I got the system to work.
I reinstalled from scratch this morning, Ubuntu and Fog and avoided using virtual machines. I made an image on a physical PC, it uploaded fine and it deployed to an old client PC we had spare.
it must have been the virtual PC’s that had the issue.
Thanks for the help though
-
Did you not try doing a “Bridged” adapter?
