Can't register Optiplex 5040- tsc: Fast TSC calibration failed
-
@Tom-Elliott 1.12 according to the op.
Recommendation is to upgrade to the trunk release. There is no hope for the kernels with 1.12 to work with that Intel nic.
-
@george1421 this thread is month’s old. Aaron is adding on to it.
-
@Tom-Elliott said in Can't register Optiplex 5040- tsc: Fast TSC calibration failed:
@Aaron-Flora what version of fog are you using?
1.2.0 using latest kernel
-
@Aaron-Flora Please define latest kernel? 4.5.0?
-
@Aaron-Flora said:
I am having the same trouble with 5040 OptiPlex…
What exactly is the issue you have? Same than what? The “Fast TSC calibration failed” message is not a show stopper AFAIK! You can upgrade the kernel via the web interface (FOG Configuration -> Kernel update) without compiling one by hand.
-
"unable to register host for the following reasons: ". No reason is given, it’s just blank. The machine will reach the point of “attempting to send inventory…” and the screen will scroll endlessly .
-
@Aaron-Flora So which kernel version are you currently on?
file /var/www/fog/service/ipxe/bzImage -
Sorry for weekend delay - I’ve tried the following with the same result, which is:
"unable to register host for the following reasons: ". No reason is given, it’s just blank. The machine will reach the point of “attempting to send inventory…” and the screen will scroll endlessly .
Official Published Kernels
Kernel - 3.19.3 TomElliottUSB
Date : July 22, 2015
Version : 3.19.3
FOG Type: TomElliottUSB
Arch Type: (x86_64)
Official Published Kernels
Kernel - 3.19.3 TomElliottUSB
Date : July 22, 2015
Version : 3.19.3
FOG Type: TomElliottUSB
Arch Type: (x86)
Official Published Kernels
Kernel - 4.1.2 TomElliott
Date : July 22, 2015
Version : 4.1.2
FOG Type: TomElliott
Arch Type: (x86_64)
Official Published Kernels
Kernel - 4.1.2 TomElliott
Date : July 22, 2015
Version : 4.1.2
FOG Type: TomElliott
Arch Type: (x86)
-
@Aaron-Flora I ran into this same issue and my fix was to install this kernel from the Web GUI. I edited the default name bzimage to bzimage1. changed that in the Fog Settings, TFTP Server, FOG_TFTP_PXE_KERNAL to bzimage1 rebooted the FOG server and it registered perfectly
Hope this helps you out.Official Published Kernels
Kernel - 4.1.2 TomElliott
Date : July 22, 2015
Version : 4.1.2
FOG Type: TomElliott
Arch Type: (x86_64) -
@buercky - Thank you! I didn’t think I had to reboot, but now when I changed the kernel it gave me an error I hadn’t noticed. Your instructions did the trick.
-
@Aaron-Flora https://fogproject.org/kernels/
This is a list of all the kernels we currently have. I know it doesn’t show up as nicely as the kernel update feature does, but it does work the same.
The bzImage bzImage32 files are the current (4.5.1 at this time) kernel’s on the server. Try updating and it should help, I hope.
-
@Aaron-Flora said in Can't register Optiplex 5040- tsc: Fast TSC calibration failed:
The 3040 also has the “Fast TSC calibration failed error” but still registers with FOG.
I am having the same trouble with 5040 OptiPlex, I can confirm that it is the model (Have 43 of them here and I tested 5 random) and most likely the NIC driver is not included in the FOG Kernel.
So we’ll need the kernel updated in order to add the 5040 to the compatibility list. I’ve never done this but am willing to try. The only instructions I have found are for using Fedora to do this.
https://wiki.fogproject.org/wiki/?title=Building_a_Custom_Kernel
Anyone doing this, already done, know a workaround?
Ahshan
less than a minute ago
Re: Can’t register Optiplex 5040- tsc: Fast TSC calibration failed
I was wondering if this happen to rectify the error as I have applied the kernel and bzimage to Fog 0.32 but fog is still not recognising the host as it comes with the error
Hdparm: ioctl 0x384 failed: inappropriate ioctl for device
-
@Ahshan Please start your own thread since your situation is different than the OP of this thread.
When you start your own thread please post the kernel versions you are using. I know you stated that you are running fog 0.30 (which is really old) but we need to know the version of bzImage you are using.
