Linux kernel



  • Most official kernels shipped with fog could not reboot in my PCs. The only working version is 3.17.3, but has a kind of USB error. So I want to build the kernel by myself. Is there any thing need to aware? I think all modules shall be compiled into bzImage, right? Anything else?


  • Developer

    It’s good to redo things and have a closer look. I found out that I had probably used the wrong ubuntu kernel config file last time. Got it here and thought that was good. But turns out the real original configs are included in the Ubuntu patchset for this kernel.

    Please understand I am now trying to keep this kernel build as close to the ubuntu kernel as possible. So I try to only change kernel settings that are absolutely necessary to make this kernel boot on your machine. You won’t be able to boot this on many other platforms and I really hope I get all the settings right the first time.

    So I uploaded two new kernels (download - one is still building and I will upload soon!). Please test both these kernels and let me know. init.xz is still the same as always.

    Edit: Ok I give up after hours of watching it compile. Trying to build a kernel without module support (all in one big blob) but having all the drivers included that Ubuntu does is just insane. So that leaves you with that one kernel to test with for now. Possibly I will generate an initrd file including all the ubuntu modules in case this kernel is still not rebooting/shutting down your hardware properly.


  • Developer

    @Maorui2k Thanks for the logs! There is one important information missing in your post and I suspect the answer no (both new kernels don’t reboot/shutdown, right?

    The logs are a really good starting point I think. The most obvious thing is that I had a different kernel version. 4.4.0 Ubuntu and 4.4.67 mine. Although this es kind of close I still think we should try to match everything as close as we can to rule everything out. Thanks for patiently testing all the kernels I upload. This is to be a long endeavor and we just need to keep going to find what’s the issue.

    I am building a new kernel now, exact same version, ubuntu patches, ubuntu config. Just to see if we can make it work by imitating the ubuntu kernel as close as possible. Will upload soon.



  • @sebastian-roth I checked kernel version, it’s x64. The USB works this time, thx! :-)

    I uploaded three logs, pls take a look. https://drive.google.com/open?id=0Bx_soHaLoSYETXhEeUVBRVllNVE

    dmesg-Ubuntu-16.04.2.log: original Ubuntu 16.04.2 kernel which has no reboot/shutdown issue
    dmesg-44-Ubuntu-config.log: bzImage4.4-pretty-close-to-the-ubuntu-build
    dmesg-44-config-3.17.3.log: bzImage4.4-with-config-uped-from-3.17.3


  • Developer

    @Maorui2k I found this in the kernel config:

     config X86_REBOOTFIXUPS
            bool "Enable X86 board specific fixups for reboot"
            depends on X86_32
            ---help---
              This enables chipset and/or board specific fixups to be done
              in order to get reboot to work correctly. This is only needed on
              some combinations of hardware and BIOS. The symptom, for which
              this config is intended, is when reboot ends with a stalled/hung
              system.
    
              Currently, the only fixup is for the Geode machines using
              CS5530A and CS5536 chipsets and the RDC R-321x SoC.
    

    Although it sounds promising at first I don’t think this is what we are after. Those chipsets don’t seem to match yours. And this option is only available on 32 bit kernel builds!! So I highly doubt this would fix the reboot for you.

    But this made me think about CPU architecture. Are you sure the 64 bit kernel is loaded by iPXE?? Pay attention to the screen when it says:

    bzImage... ok
    init.xz... ok
    

    Nothing about 32 there, right???

    I updated that kernel once again as I still was missing the USB HID settings, too bad. Hope that your keyboard is working now but probably won’t help the reboot anyway.
    As well I’ve used the 3.17.3 kernel config from our repo and updated it to build a 4.4 kernel from that. So if anything was in that config it should be still in there. Please try both kernels.

    I’ve been reading through this and searched the web over and over again. I just don’t understand why none of the kernels I build is doing any better. Just scratching my head… Why do 3.17.3 and the ubuntu kernels reboot properly? Boot up a live system again (or from disk if you have still installed ubuntu) and get a full listing of the kernel messages buffer. I feel this could be quite important in finding the issue. Get a FAT32 formated USB key and run:

    sudo -i
    mkdir /usbkey
    mount -t vfat /dev/sdb1 /usbkey
    dmesg > /usbkey/ubuntu_working.txt
    umount /usbkey
    

    Do the same in a FOG debug task just no sudo and choosing a different filename to store the dmesg output in. Please upload both full outputs and post download links here.


  • Moderator

    Moved to Hardware Compatibility.



  • @Sebastian-Roth The reboot/shutdown and USB still didn’t work with the new kernel…

    I installed Ubuntu 16.04 desktop and server edition, and both could reboot successfully. Live CD was also fine.

    I tried everything in same PC. I checked all BIOS options, didn’t see anything related to this issue.


  • Developer

    @Maorui2k Sorry for the USB issue. Didn’t think that USB keyboard would be build as a module by default. I added it to the kernel and uploaded a new version. Could you please try again?

    Have you ever installed Ubuntu 16.04 on that hardware and tried to reboot? I am just wondering if we are on the wrong track with this. Maybe booting a live CD is just a little different.

    Bay the way: Are you working on the exact same PC all the time? Just to rule out that BIOS settings might be causing the issue on one of the PCs?



  • @Sebastian-Roth said in Linux kernel:

    @Maorui2k Sorry for the long delay, I have been away. So it looks like the ubuntu kernel patches don’t make a difference. So next we can try to use the ubuntu kernel config to see if that helps. Find a newly compiled bzImage here. Please try this and let me know!

    It didn’t work… And the USB keyboard didn’t work with this version, so I couldn’t test the reboot in debug mode manually. I tried two different keyboards and all USB2/3 ports. The keyboard stopped response after the new kernel was loaded.


  • Developer

    @Maorui2k Sorry for the long delay, I have been away. So it looks like the ubuntu kernel patches don’t make a difference. So next we can try to use the ubuntu kernel config to see if that helps. Find a newly compiled bzImage here. Please try this and let me know!



  • @Sebastian-Roth Thanks for the kernel, but it doesn’t work too. There is no error message, just stopped at the last step of regular reboot/shutdown process. The last step should be a signal to hardware. I uploaded a picture of the screen here. https://drive.google.com/open?id=0Bx_soHaLoSYETllpSUVmVEotX28 So the kernel config may do the trick.



  • @Quazz Windows & Ubuntu 16 could reboot/shutdown. And there is no BIOS update.


  • Developer

    @Maorui2k Ok, to see if the Ubuntu patches do the trick I downloaded those, applied to a vanilla 4.4.0 kernel, used our FOG kernel config and build a kernel from that. Please download bzImage and init.xz here. If this kernel properly shuts down your machine then we can start looking through the patchset. On the other hand, if this kernel does not shutdown/turn off your machine, then the Ubuntu patches are irrelevant and you can start comparing the kernel configs and/or parameters.


  • Developer

    @Maorui2k said in Linux kernel:

    I tried CentOS 6 & 7, both have the issue. So Ubuntu is the only survivor. I’m still finghting with the Ubuntu kernel compile process. It’s not same as general process, and I always got error in the middle. Not sure the reason yet…

    Please post the error so I might be able to help. Without I don’t have a chance to give you a hint. Let me know which steps/command you do/run and which error you get.

    I am wondering if it’s Ubuntu’s kernel config or if they have a special patch that does help shutting down your machines. The problem is that building a normal Ubuntu kernel won’t help you because FOG has all the important drivers included in the kernel (bzImage) while Ubuntu has most in the initrd. Ubuntu kernel is smaller but would not work with FOG (initrd). I’ll think about it a little more and try some stuff.


  • Moderator

    @Maorui2k If you have an operating system installed on them, can they shut down/reboot?

    Are there any BIOS updates available for this motherboard?



  • @Quazz I tried debug mode, both reboot & shutdown had same result. I could see the message of killall process, but the PC just hung there after message ‘Requesting system reboot/halt’, and the keyboard was freezed too, CTRL-ALT-DEL won’t work.


  • Moderator

    @Maorui2k “same result” being nothing happening at all?



  • @Quazz I tried and got same result.


  • Moderator

    Can you try to boot one of the machines in debug mode and try to reboot there?

    It’s unlikely, but perhaps it will give some useful information.

    I’m guessing these are custom built PCs? (given that no DMI info is supplied)

    It’s interesting that under certain circumstances they wouldn’t reboot.

    What about shutdown? Does that work?



  • @Sebastian-Roth I tried CentOS 6 & 7, both have the issue. So Ubuntu is the only survivor. I’m still finghting with the Ubuntu kernel compile process. It’s not same as general process, and I always got error in the middle. Not sure the reason yet…


Log in to reply
 

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