Imagaing issues with new Lenovo M93z

[adam boynton]

I am having an issue with a new Lenovo M93z, FOG has worked perfectly until this new model and now I get the following error when trying to image it.

Kernel Panic-not syncing: Attempted to kill init! exitcode=0x00000009

I have added Tom’s latest kernel image to my server which has allowed me to at least start the image but it will not go any further

[Tom Elliott]

which kernel, exactly did you try?

[url]https://mastacontrola.com/fogboot/kernel/bzImage[/url]

or

[url]https://mastacontrola.com/fogboot/kernel/bzImage32[/url]

[adam boynton]

the 32

[Tom Elliott]

And you’re not getting the panic anymore?

[adam boynton]

no, I still get the panic, I will try the bzImage and get back with you

[adam boynton]

it panics using either kernel

[Tom Elliott]

Alright,

Need some more details. What version of FOG Are you using? Have you ever been able to image these systems?

Can you capture a screenshot of the panic and post it here so I can troubleshoot a little better?

[adam boynton]

I am using FOG .32, we just got these machines and I havent been able to image them yet

I will capture a screen shot and post it shortly

[adam boynton]

[IMG]https://lh4.googleusercontent.com/-lwYulMP5gnQ/UyBlr3bY1II/AAAAAAAAAGc/BWdp4P9EMtc/w1589-h987-no/IMG_20140312_094634.jpg[/IMG]

[Tom Elliott]

And you’re sure it’s using the bzImage32 file instead of the default?

[adam boynton]

this error is from bzImage

[Tom Elliott]

What do you get with the bzImage32? The bzImage is now a 64 bit kernel, which will not work with the FOG 0.32 init.gz file.

[adam boynton]

here is the error with bzImage32[IMG]https://lh3.googleusercontent.com/GRXnoRwl5LuBYIgI-dCeog4uehO5dGRVtY9weluGOg=w1886-h1108-no[/IMG]

[Tom Elliott]

How are you copying the kernel?

[adam boynton]

scp to the server

[Tom Elliott]

So I’m assuming you’re doing:

[code]scp bzImage32 <ip.fog.server.1>:/tftpboot/fog/kernel/bzImage[/code]

[adam boynton]

I am using cyberduck, it is gui program on a mac, I can do it on the command prompt if needed

[Tom Elliott]

That’s not exactly helpful.

I need to know that the bzImage32 file isn’t just being stored on the server as: bzImage32. bzImage is the kernel file that needs to be loaded. If you where having issues with the old kernel, and just copied the bzImage32 as bzImage32 to the kernels directory, you’re still loading the old kernel. If you used bzImage from before, well the panic is due to the architecture differences.

Usually the error’s that you’re seeing reported is due to architecture differences.

[adam boynton]

it is being uploaded as bzImage, I rename it before I transfer it

[adam boynton]

any updates Tom?