Kernel Updates


  • Senior Developer

    All,

    I just wanted everybody to know I’ve been trying to keep up with the kernel updates as they come out.

    I thought it would be nice/good for everybody to know that they’re generally available at my website:

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

    I’m also going to post my configuration file as it seems, to me, to work the best as it doesn’t try to operate around the video card. It’s based on Peter Sykes config file with a few inclusions for the proc system.

    I’ll call this kernel (for lack of an original name) TomElliott.config

    It can be download at:
    [url]https://mastacontrola.com/fogboot/kernel/TomElliott.config[/url]
    or from this forum.

    If you download from the forum, change the file name from TomElliott.txt to TomElliott.config

    Or change the file directly in the kernel source directory to .config

    Use it and please tell me how you feel about it. You can use the working copy by downloading or using the config to build your own.

    I would like to know other’s mileage with it.

    Thank you,

    [url="/_imported_xf_attachments/0/391_TomElliott.txt?:"]TomElliott.txt[/url]


  • Senior Developer

    If you’re running FOG 0.32,

    The kernel likely “panicked” which would explain the “kernel error” you were seeing. Since 1.0.0 I’ve been building a 64 bit AND a 32 bit kernel. When you downloaded your new kernel, which architecture did you download? My guess is you downloaded the 64 bit kernel and this is where things went south for you.

    Also, you state the file “could not be found & the kernel error” This sounds exactly like the information I just told you. The 64bit kernel cannot find a 64 bit init.gz file. It’s because of this you see the “could not be found” AND the reason why you have the kernel error.

    If you download the bzImage32 file as your bzImage, things should work more properly for you.



  • The reason I brought that up is when PXE booting it gives a kernel error. I updated to your kernel and the error changed and said the file could not be found & the kernel error, sort of a combo, that was where it was dealing with the kernel updates.

    Thank you for your help


  • Senior Developer

    [quote=“Stars75238, post: 37032, member: 23572”]I am currently running 12.04.5 with fog .32

    I had to reinstall because of a MySQL unrecoverable error. I wanted to try 1.2 but is requiring the undionly.kpxe file that I do not know how to create or cannot find on the server. Any help?[/quote]

    What, exactly, does this have to do with Kernel Updates?

    All that said, What do you mean it’s requiring the undionly.kpxe file and you don’t know how to find it?

    When you install fog 1.2.0, it installs all the files you need for things to work.

    The only changes you’d need would be to change the Option 67 from pxelinux.0 to undionly.kpxe so the TFTP file is received properly.



  • I am currently running 12.04.5 with fog .32

    I had to reinstall because of a MySQL unrecoverable error. I wanted to try 1.2 but is requiring the undionly.kpxe file that I do not know how to create or cannot find on the server. Any help?


  • Senior Developer

    [quote=“mlnancejr8808, post: 26718, member: 654”]With going to iPXE does this give the ability now to boot over wireless?[/quote]

    Technically, yes you can boot from Wireless. However, the kernels I’m providing have NO wireless support what so ever, so while the system will “boot” it will not be able to do anything.


  • Moderator

    If your hardware supports it then possibly, but that is rare for hardware to support.



  • With going to iPXE does this give the ability now to boot over wireless?


  • Senior Developer

    In case you were all wondering,

    3.14.3 is built and available on my site.

    [url]https://mastacontrola.com/fogboot/kernel/bzImage[/url] (64 bit)
    [url]https://mastacontrola.com/fogboot/kernel/bzImage32[/url] (32 bit)

    If you are on FOG 1.0.0, it should be available under the unpublished kernels listing.

    I will likely update the svn site as well for a kind of Repository for these kernels as well.

    Thank you,



  • This post is deleted!

  • Senior Developer

    CentOS Kernel is available, but doesn’t work as you might expect it to.

    3.14.2 is available now.


  • Senior Developer

    I’ve built the CentOSBase kernel. I will post in a moment. It’s 20MB, but should work on nearly ANY machine. I’ll try to narrow down what’s needed vs. what’s not needed (wireless, sound, vga, etc…) to try to limit the size of the file and maybe have a better supporting kernel.


  • Senior Developer

    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).


  • Senior Developer

    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.


  • Senior Developer

    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.



  • 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]



  • 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]


  • Senior Developer

    [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.



  • 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.



  • 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.


Log in to reply
 

436
Online

39.3k
Users

11.0k
Topics

104.5k
Posts

Looks like your connection to FOG Project was lost, please wait while we try to reconnect.