Imagaing issues with new Lenovo M93z
-
no, I still get the panic, I will try the bzImage and get back with you
-
it panics using either kernel
-
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?
-
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
-
-
And you’re sure it’s using the bzImage32 file instead of the default?
-
this error is from bzImage
-
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.
-
here is the error with bzImage32[IMG]https://lh3.googleusercontent.com/GRXnoRwl5LuBYIgI-dCeog4uehO5dGRVtY9weluGOg=w1886-h1108-no[/IMG]
-
How are you copying the kernel?
-
scp to the server
-
So I’m assuming you’re doing:
[code]scp bzImage32 <ip.fog.server.1>:/tftpboot/fog/kernel/bzImage[/code]
-
I am using cyberduck, it is gui program on a mac, I can do it on the command prompt if needed
-
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.
-
it is being uploaded as bzImage, I rename it before I transfer it
-
any updates Tom?
-
Try this kernel for your lenovo’s apparently my kernel’s haven’t been able to work on them quite yet.
[url]https://onedrive.live.com/?cid=971575ddb836155f&id=971575DDB836155F!175&ithint=file,&authkey=!AFmNg5OiH-ViV00[/url] -
It works! Thanks so much for your help!!!
