Ok so all working now, I used the latest kernel download and named the kernel via FTP bzimage and then copied that file and renamed bzimage to bzimage32, so the same kernel for both 64 32 bit which seems to work fine now. So that seems to be the issue sorted out so thanks to everyone who added a reply on this.

Regards

Hi wayne

yes I can confirm all the files are named correctly and in the correct area.

Anyone else have any idea’s on this one?

yep I haven’t changed anything in there, it seems that on the 32 bit stations its not passing the init32 file i only ever see the straight init.xz file.

[ATTACH=full]1985[/ATTACH]
this is my tftp area

[url=“/_imported_xf_attachments/1/1985_tftp.PNG?:”]tftp.PNG[/url]

I have included a screen grab, the laptop I have taken this pic from is a Dell Vostro A860 [ATTACH=full]1984[/ATTACH]

[url=“/_imported_xf_attachments/1/1984_WP_20150508_11_27_13_Pro.jpg?:”]WP_20150508_11_27_13_Pro.jpg[/url]

Good day

I have been dancing around the same issue for a little while with 32 bit images not loading at all, I have upgraded the kernel to 3.19.3 32 64 bit and from the ipxe menu it will pass the bzimage32 but the init.xz is always the default one it doesn’t change to the init32.xz file, then we get the same modprobe error which will then just stay stuck on the same screen. I have snap shooted and moved up to the latest SVN which then boots great for 32/64Bit systems but then I cant push/upload any images or I cant move my pxe menu items from my backed up fog.prev folder as FTP keeps telling me perms are a problem, I try and set recursively perms 777 but it just fails so ultimately I just revert back to the previous snapshot and same 32 bit issues.

It is probably something stupid on my end but quite frustrating because these systems worked on 0.32 absolutely fine.

I forgot to add if it helps that I upgraded fog 1.2.0 to 3318 via the Ubuntu terminal command, so this had an existing fog install working all be it the kernel problem I was having

I have actually seen on another bit of hardware a different error now, still same end result no image pushed out, it completes all the preliminaries then just reports the task as complete then reboots, this is on a HP small form factor 5100.

it is a deploy to station, I have tried doing it from for Webgui as a task and also using the Quick image option.

Ok I have a video of exactly what is happening but just wondering what is the protocol for attaching videos? just link it through Youtube or is there a simpler way.