bzImage for new computer

[Tom Elliott]

Maybe update to FOG 1.3.0?

It has the latest kernels automatically. I don’t know what’s wrong with your scenario but it would seem somewhat related to the hdd’s at this point.

[jrm]

@Tom-Elliott said in bzImage for new computer:

Maybe update to FOG 1.3.0?
It has the latest kernels automatically. I don’t know what’s wrong with your scenario but it would seem somewhat related to the hdd’s at this point.

Hi Tom,

the server was in production but i’ve try to install another server in 1.3.0 and i try the kernel in the 1.2.0 but doesn’t work.

I also tried to rebuild a kernel from your tuto

[Wayne Workman]

@jrm Don’t use kernels from 1.2 in the test server. Just install FOG 1.3.0 and try it out-of-box.

[jrm]

Hi Wayne,

I will try directly.

If this still does not have a track I can explore,

[Wayne Workman]

@jrm The issue is you describe these problems as intermittent:

At startup on the pxe I sometimes have kernel panic, or the unrecognized network or even the disk controller.

Does the same error happen on every single one of these models or is it random? Have any of these models ever worked with FOG? What would be ideal is to have two machines that are an identical model, but one working and one not working with FOG, then figure out what’s different about them.

It could be something as simple as bad ram in a few of your machines.

Lenovo and Dell in my experience work great with FOG overall.

[jrm]

Hi,

I’ve upgrade a fog server from 1.2.0 to 1.3.0 and i’ve upgrade boot kernel immediatly.

@Tom-Elliott : i can boot over pxe and i can see fog menu without problem but i can’t do a full host registration or quick image when i try on DELL PRECISION 3420 ( network card is Intel i219LM).

Can you tell me if the intel e1000e drivers was the last version in your build kernel?

Thanks a lot in advance.

Jérôme

[Tom Elliott]

@jrm I don’t understand the question.

This almost sounds like your network is not issuing an IP Address. This could happen due to STP on the network, or Power Saving, or the NIC simply isn’t being recognized. I’m going to suspect, first, that it’s STP on the network.

To validate, if you have a dumb switch (5/8 port should work) and connect the network to the switch, then connect the system to the same switch, and try again, does the issue persist?

[george1421]

@Tom-Elliott Needing the 4.9.x linux kernel with the patch that Sebastian found? Its the same network adapter if I remember correctly. The system is getting to stage 3 of the booting process (FOS) and failing to get an ip address??

[jrm]


[george1421]

@jrm What did you do differently to cause a kernel sync error?

[Tom Elliott]

@george1421 If I had to guess, he’s copied the x86 kernel as bzImage.

Just a guess, hopefully we can get more information.

[jrm]

No i don’t do that.

I’ve try to had module with make menuconfig

[Tom Elliott]

@jrm Why did you build your own kernel? Not that you did anything wrong, but there should be no reason to build your own.

I’ve already built them. If you look on your fog server goto FOG Configuration Page->Kernel Update.

You should see both the 32 and 64 bit.

[Tom Elliott]

Through chat had @jrm run a wget to download the bzImage’s from the fogproject server. OP stated these kernels worked.