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.
I can certainly help, I have just got back from setting up a court video link so I will try and get a video for all, its very strange I must say it picks up the hard drive gets to the MBR/GPT part then just bombs out and thinks that everything is done and reboots.
Hi tom
Thanks for your reply, the error pops up then the machine just reboots, so it doesn’t even attempt to push the image to the station.
cheers
Good day to one and all
I have had some down time in work so upgraded fog 1.2.0 to the latest version 3318 and everything went really smooth and looks good, the kernel thing seems to be really good as well it works for 32 bit and 64 bit systems I have but now I cant actually deploy any images, it keeps throwing a dev/sda1 sda 2 under the erasing mbr/gpt part!!! any one any clues on how to get around this one?
I have tried playing with the image types to see if its the way the image was uploaded but this is an issue across the board for me all hardware are unable to deploy images.
cheers all
I have had to accept defeat for the time being and I have gone back to Fog 0.32 to get me around the Kernel issues. It has caused a back log of stations needing to be imaged.
Can I ask if anyone has any tutorials or links I can read up on to see about compiling fog kernels for 1.2.0, im a complete Ubuntu numb nuts and struggle with getting my head around the commands etc.
Thanks all
I have just tried a Dell Inspiron 15r and I am getting the same problem with Kernal panic, I have downloaded from the Fog management page a new kernel but still know avail. I apologies if I’m being a donkey but I cant seem to get my head around the new kernel scenario. Is there a mass network driver kernel I can download? part of the message says
“esas2r: driver will not be loaded because no ATTO esas2r devices were found”
any help would be ideal but these are laptops that I have had no issues with on 0.32 version.
Hi tom
im using version 1.2.0
I will check the log files and report accordingly. I have gone on the forums etc and i also tried your wegpage kernel but still no fix, but it could be that im just being stupid and not understanding how to create the kernel.
Good morning all
I have recently been having issues with kernel panic messages appearing when I look to do a bypass host registration image from the pxe boot menu. I have downloaded several different kernals and updated the pxe config to point to the different downloaded config and still just getting the Kernal panic message, I have left it a good 5-10 minutes and it just stays on that error. The machine in question is Dell inspiron 6440.
Indecently the whole kernel side of play on the new Fog server is slightly different i started to get my head around it in the previous version and know its a bit of trial and error.
Hope i have supplied enough info but would be keen to hear from anybody on this is issues
I have not been on the forums for a little while but I just wanted to pop my head in and say a big thank you to all the developers and testers who spend there spare time working on this great product, I have just this week fired up fog 1.2.0 and started adding custom pxe menus isos and lots of other great stuff that without these informative forums and wiki threads id be well and truly screwed.
so from somebody who’s day to day working life would not survive without fog thank you all very much.
P.s interested to see what other people are doing to pimp up there new fog system, my next thought is add several av malware iso’s to allow a sheep dip scenario.
Hi Saxx I would be interested in the testing the Fog virtual box sounds like a cracking idea mate
Guys just want to say how extremly excited i am (i no im sad) to test the new version of Fog a big well done from someone who could not do his work without fog. Can i ask how we download the latest release of fog so i can load up into my test network please?