Kernel Updates
-
As a caveat to the above, I’m going to make post here that gives all the selected options so others may see what they need added and/or removed for their setup’s.
-
Excellent work and the option list is useful to know!
-
It’ll be a little bit until I get a full list going but I assure you all I will post it.
-
Wow!, I must say they’ve been pretty active in updating. Woohoo 3.11, dang i’m a slight step behind. Don’t worry building the kernel and it will be up in about an hour. Same link as above. I haven’t had much time…yet… to go thru all the selected options. Don’t worry, I’ll also do a build with all the Network Drivers as well, once the main kernel is up and running.
-
Hello,
I am glad someone is working on and keeping an updated kernel!!
I know what to do with the bzimage, but am not entirely sure what to do with your .config file. Does it need to be put into the bzImage file?
-
No,
The config file is if you’re trying to build your own kernel. You’d simply copy the file in the linux-<version> folder as (note the period in front) .config then run:
make ARCH=i386 menuconfig
Exit the menu,
then run:
make ARCH=i386 bzImage -
I’ve remodified my configuration last night as a test. I am running VMWare ESXi 5.1 where I work and even with the SCSI Low Level Drivers enabled, it doesn’t recognize any of the LSI SAS SCSI drives or anything. So I went through, I think, systematically and enabled and disabled things I found were pertinent to be contained within the kernel. It still has, as far as I can tell, all the possible networking drivers and no mode setting, but it now recognizes, natively I might add, the LSI SAS which I was having issues with. I’ll test some more before updating my configuration file within the current revision of FOG, but if others want to test please download the kernel at:
[url]https://mastacontrola.com/fogboot/kernel/bzImage[/url]
It’s much smaller now. Originally it was small at 8.1MB, but now it’s a whopping 6.2MB. I hope others will like it as well.
-
Adding to my kernel the config. This way I can pull the data in the future. Previous versions I didn’t add this as I wasn’t aware of what the option does.
-
Kernel 3.13.7 is available on my website.
32 bit kernel can be downloaded from: [url]https://mastacontrola.com/fogboot/kernel/bzImage32[/url]
64 bit kernel can be downloaded from: [url]https://mastacontrola.com/fogboot/kernel/bzImage[/url]Also, you can use the FOG Web GUI if on 0.33b with a revision that I had this installed. I forget which one. It displays just like the normal fog kernel update page, but also has the Architecture displayed.
-
Hi Tom
Great that you are keeping the kernel up to date Have one question and I hope you can help me on this when I download the file it is a DOS/Windows executable (application/x-ms-dos-executable) what do I do with this file not sure how to install it Any help on this would be great
Thanks
Gary -
I hate to sound like a “d**k” but have you tried searching for similar issues:
The quick and dirty.
If you’re running 0.32
[code]sudo su -
cd /tftpboot/fog/kernel/
mv bzImage bzImage.orig.2014MAR25
wget --no-check-certificate https://mastacontrola.com/fogboot/kernel/bzImage32 -O bzImage
[/code]If you’re running 0.33b and you want the 64 bit kernel
[code]sudo su -
cd /var/www/{fog,html/fog}/service/ipxe
mv bzImage bzImage.orig.2014MAR25
wget --no-check-certificate https://mastacontrola.com/fogboot/kernel/bzImage
[/code]
If you’re running 0.33b and you wan the 32 bit kernel
[code]sudo su -
cd /var/www/{fog,html/fog}/service/ipxe
mv bzImage32 bzImage32.orig2014MAR25
wget --no-check-certificate https://mastacontrola.com/fogboot/kernel/bzImage32
[/code]
If you’re running 0.33b, you can also use the kernel update mechanism from the GUI to get my kernels. Just select the dropdown unofficial kernels.When it comes time to name them, if you chose the arch (x86) you will need to add the 32 to the name so it gets stored as bzImage32 or you can name it anything you want, just you’ll have to remember it’s a 32 bit kernel.
-
Possibly a bit of a noob question, why would I use an x64 kernel over an x86?
I know the reasons why I’d use a 64bit OS over 32bit, but don’t really understand why a 64bit kernel would be needed with FOG, are some of the drivers 64bit only? -
Hi Tom
Yes I have searched the forums for this and have tried the exact commands that you have listed above but for some reason it did not work.Did use yours and now it is working fine.Thanks for the fast response and your help on this matter. -
This does not seem to change the kernel that is loaded. When changing the filename in the WebGUI (0.33b) nothing seems to change, and I cannot boot iPXE because I cannot set an HTTP proxy for iPXE.
Thanks in advance for any advice.
-
[quote=“moss, post: 24656, member: 553”]Possibly a bit of a noob question, why would I use an x64 kernel over an x86?
I know the reasons why I’d use a 64bit OS over 32bit, but don’t really understand why a 64bit kernel would be needed with FOG, are some of the drivers 64bit only?[/quote]We moved to 64 bit so we have access to UEFI when we can finally network boot UEFI through iPXE.
[quote=“Jackobyte, post: 24708, member: 23235”]This does not seem to change the kernel that is loaded. When changing the filename in the WebGUI (0.33b) nothing seems to change, and I cannot boot iPXE because I cannot set an HTTP proxy for iPXE.
Thanks in advance for any advice.[/quote]
It does change the filename, unless your kernel directory is still set to /tftpboot/fog/kernel. If it is you’ll need to update the kernel directory to /var/www/fog/service/ipxe (or whatever the fog web folder is located). Then the kernels in use will “change” with the selected downloaded kernel unless you’re giving custom names.
I don’t know how to get it to work through a proxy, but the default.ipxe file which is loaded on initial boot time would be a place to look.
It use’s IP’s to chain the boot process. Why you’d need to proxy to get to your FOG server is beyond me.
-
Because the server sits in a VM in a datacentre and for some reason this requires to be proxied. This seems to be what I’m looking for but is a bit technical for me. [url]https://tinyurl.com/bog55gq[/url]
-
I’ve managed to get iPXE to boot now getting “Could not start download: Operation not supported” message.
I take it this means that it is not finding my bzImage32 for some reason however i have checked and changed the setting for kernel directory to the one specified above and changed PXE boot image to init_32.xz
[IMG]http://www.anonimg.com/img/a6826d980ef9f5e255c7d96732b62205.png[/IMG]
-
Do you have a firewall that may be blocking port 80?
The configuration you’ve got looks to be fine.
One way to verify is to, from a browser that’s behind the same network settings as the client that’s unable to download, go to the link:
[url]http://150.1.52.94/fog/service/ipxe/bzImage32[/url]
[url]http://150.1.52.94/fog/service/ipxe/init_32.xz[/url]If you can download the file, all should be good.
If it doesn’t download try these links:
[url]http://150.1.52.94/service/ipxe/bzImage32[/url]
[url]http://150.1.52.94/service/ipxe/init_32.xz[/url]If that doesn’t work check the firewall on the system or between the client and the system. Verify traffic can pass properly.
Also, verify the files are in the proper locations. My guess, for whatever reasoning, the init_32.xz and bzImage32 may be missing from the server location. -
Kernel’s have been updated to 3.14.0 as of last night. Upgrading my systems at the moment so they’re all on the same level. VB Released an update as well which is currently my holdup.
-
Kernel’s have been updated to 3.14.1 as of 10 minutes ago. I’m currently working on compiling a kernel based on the config provided by CentOS directly which, theoretically, would have more drivers enabled by default. Word of caution, while I will be providing this kernel on my site, it’s probably going to be quite large. Maybe it can help out. For right now, it’s only going to be 64 bit on the CentOS config. (I’ll probably call it the CentOSBase).
