FAQ page in WIKI should be updated
-
@Sebastian-Roth I don’t know if it’s changed, but you needed an account created for you before you could edit the FOG wiki, I don’t think even I have one at the moment.
-
Hi Sebastian,
@Sebastian-Roth said in FAQ page in WIKI should be updated:
@Luc-Novales Thanks for mentioning this. I reckon we should remove that content altogether. @Moderators Any suggestions on this? I didn’t even know this existed but I feel it could be used for way better content if we’d have the time to update it.
I don’t request any account to the wiki because I don’t know how to update this page
I don’t see why you shouldn’t be able to update a simple wiki page. If you are able to use FOG you can edit wiki just as well. It’s not complicated.
IT is easy to edit a page when you have the information to put inside.
Here there is wrong link on a non existent domain name (dyndns entry). There is no IP address to join the server and download bzImage.
I can’t solve that? it’s the problem
Thx,
Luc. -
@Sebastian-Roth I would say remove it since it deals with an 8+ version of FOG. The links are long dead and what real purpose does it serve? The kernels are now under https://fogproject.org/kernels/ now. Plus the wiki page doesn’t really tell you what problem you are trying to solve only to replace the FOS Linux kernels.
-
@george1421 said in FAQ page in WIKI should be updated:
@Sebastian-Roth … Plus the wiki page doesn’t really tell you what problem you are trying to solve.
Now, yes
I solved the ipxe problem and I have to build bzimage32 for i586…
Perhaps shortly solvedThx,
Luc. -
@Luc-Novales But fog now auto detects what kernel to use. If you have a system that is 64 bit but the manufacturer has pinned it as 32 bit (as in some inexpensive tablets) you can just update the kernel parameter in the host definition instead of swapping the bzImage/bzImage32 files. There are better and easier ways to go about it with FOG 1.2.0+ than with the really old versions of FOG.
-
@george1421 said in FAQ page in WIKI should be updated:
@Luc-Novales But fog now auto detects what kernel to use. If you have a system that is 64 bit but the manufacturer has pinned it as 32 bit (as in some inexpensive tablets) you can just update the kernel parameter in the host definition instead of swapping the bzImage/bzImage32 files. There are better and easier ways to go about it with FOG 1.2.0+ than with the really old versions of FOG.
It doesn’t works.
In my last reply of Black screen and blinking cursor after vesamenu, I said that trying for FUN your menu (Only for reference), load effectively bzImage32 and stop with the message “This kernel requires an i686 CPU but only detected an i586 CPU”.Here the screenshot of this error :
There is the same result using the menu boot.php and select “CLient System Information (Compatibiliy)”.
I should solve this problem, compiling a custom linux kernel and I downloaded linux-4.19.68 sources, but it seems that config file is not present in FOG sources as defined in Building a Custom Kernel. There is no kernel part in FOG sources, where can I find this config file ?
Thx,
Luc. -
@Luc-Novales This is an issue with the bzImage32 kernel that we ran across a few weeks ago. I can’t remember where the issue stood. This system was listed as a 486 if I remember correctly.
I just looked in my dev environment and I looks like it was setup to build a compatible FOS kernel. Let me rebuild it then I will have you try it to see if it works with your processor. It should take just a few minutes to compile. If it works OK then we’ll have to talk to the devs to see if there is any value adding it to the main branch. I’m seeing this as a one off situation. If its decided to not add to the main branch then you can continue to use bzImage486 without issue even after FOG updates.
-
@Luc-Novales I sent you a link to the 486 compatible kernel via FOG IM. Look at the chat bubble for additional information.
-
Hi George,
@george1421 said in FAQ page in WIKI should be updated:
@Luc-Novales This is an issue with the bzImage32 kernel that we ran across a few weeks ago. I can’t remember where the issue stood. This system was listed as a 486 if I remember correctly.
Yes an AMD Geode LX @500mhz.
An old panel PC used in operational equipment.I just looked in my dev environment and I looks like it was setup to build a compatible FOS kernel. Let me rebuild it then I will have you try it to see if it works with your processor. It should take just a few minutes to compile. If it works OK then we’ll have to talk to the devs to see if there is any value adding it to the main branch. I’m seeing this as a one off situation. If its decided to not add to the main branch then you can continue to use bzImage486 without issue even after FOG updates.
Thanks, I’m waiting for your kernel to solve my problem and I think that it should be interesting to update the section Building a Custom Kernel to allow user to debuig this part too. I could try to update it if I have information to make it.
Thx,
Luc. -
@Luc-Novales Kernel building is now part of the init building process
https://github.com/FOGProject/fos is the github branch if you want to check it out.
I believe George sent you a chat message (top right) with the kernel he made though.
-
@Luc-Novales said in FAQ page in WIKI should be updated:
I should solve this problem, compiling a custom linux kernel and I downloaded linux-4.19.68 sources, but it seems that config file is not present in FOG sources as defined in Building a Custom Kernel. There is no kernel part in FOG sources, where can I find this config file ?
Sorry about this but it’s just another old wiki article - too bad! Here is the most current one and I believe this is up to date and should work: https://wiki.fogproject.org/wiki/index.php/Build_TomElliott_Kernel#Build_TomElliott_Kernel_for_FOG_0.33b_and_newer
-
@Sebastian-Roth said in FAQ page in WIKI should be updated:
@Luc-Novales said in FAQ page in WIKI should be updated:
I should solve this problem, compiling a custom linux kernel and I downloaded linux-4.19.68 sources, but it seems that config file is not present in FOG sources as defined in Building a Custom Kernel. There is no kernel part in FOG sources, where can I find this config file ?
Sorry about this but it’s just another old wiki article - too bad! Here is the most current one and I believe this is up to date and should work: https://wiki.fogproject.org/wiki/index.php/Build_TomElliott_Kernel#Build_TomElliott_Kernel_for_FOG_0.33b_and_newer
Ok, I will try it later, now I test the kernel provided by George ;-).
Thx,
Luc. -
@Quazz said in FAQ page in WIKI should be updated:
@Luc-Novales Kernel building is now part of the init building process
https://github.com/FOGProject/fos is the github branch if you want to check it out.
I believe George sent you a chat message (top right) with the kernel he made though.
Yes, I have this kernel and I return to the initial post Black screen and blinking cursor after vesamenu, is better to resume my actions.
-
@Luc-Novales So let me understand even with the 486 kernel it does not boot, I would expect an error message as in the picture provided.
Loading bzImage486... ok Loading init_32.xz... okThen some message saying its the wrong kernel. Is this what you are seeing? If booting with syslinux you should at see that with the syslinux pxelinux.0 menu.
-
@george1421 said in FAQ page in WIKI should be updated:
@Luc-Novales So let me understand even with the 486 kernel it does not boot, I would expect an error message as in the picture provided.
I made a report of actions in initial thread more adapted…
Black screen and blinking cursor after vesamenuThx,
Luc.
