Network fails on compatibility test
-
I have disabled RAID for the drives (the Wiki says that was a problem) to no avail.
-
To ease fears, i’m going build a core kernel config with all network, no vga, and scsi stuff installed to see if there’s some major difference in what my kernels are doing vs, what your systems are expecting. It’ll be about an hour or so, but I doubt this is going to help, if it does, cool, if not we’re not any more for loss.
-
Core config is available for download via kernel updater.
The “new” config is called TomElliottCore for the “version” name.
-
I’ve just tested the new kernels on my Dell 755 (I am guessing they are the same hardware as Jordan mentioned in the top post.)
I’m getting the same result with the new TomElliottCore in the fog updates. I have also updated the installation to 1.1.0.I do have a kernel that works on my fog 0.32 that I tried using but it kernel panic because the init was unable to me mounted.
I’m guessing this is because the default init is 64bit? and the new kernels know where to find the 32bit version but the old 2.6 kernel does not?[IMG]http://i.imgur.com/2CdmE5h.jpg[/IMG]
The above image is the error from the 64bit Kernel TomElliottCore - 5th June. - Dell OptiPlex 755
-
After compiling the 3.14.5 kernel and testing the different driver options.
It seems that for the Dell OptiPlex 755 the e1000e driver is at fault. (I am finding it stops the NIC from receiving network traffic until I boot into windows and reboot the PC)The working version I have on my old fog 0.32 server is - 2.6.33FOG_KS is it possible to still use this kernel in fog 1.1.0?
or use an older driver and recompile the kernel?Cheers,
-
[quote=“Tom Elliott, post: 29470, member: 7271”]Core config is available for download via kernel updater.
The “new” config is called TomElliottCore for the “version” name.[/quote]
I updated to 1.1.0 and your new kernel, and now when I enter registration, it automatically boots into windows. Hopefully that’s the kernel.
-
Nothing more on this? We unfortunately have a few 780s.
-
Tom has a new Kernel out that may be worth trying version 3.15.x.
-
This machine now boots directly into Windows after I hit enter on the Full Host Registration option.
-
Any option, actually.
-
I’m still confused.
Have you tried the latest kernel?
Is there any messages, could you possibly catch a video. It’s not typical to just boot to windows after selecting an option. If there was an error, the worst that would happen is it would bring you back to the menu, then wait for the PXE Timeout to boot to hard disk again.
-
Also, if you want, try the Kernel.TomElliott.3.10.1. I built it today so it should show up on the top of the unofficial kernel’s list.
-
Yes I just installed 3.15.0. I will try to catch a video to show you
-
[media=youtube]7RfHBmHeqlk[/media]
-
Based on what I’m seeing, it’s saying Could not boot, hosuch file or directory [url]http://ipxe.org/[/url]
This tells me your /tftpboot/default.ipxe file is not setup correctly.
What is the contents of this file on your system?
-
#!ipxe
cpuid --ext 29 && set arch x86_64 || set arch i386
params
param mac ${net0/mac}
param arch ${arch}
chain [url]http://172.16.0.35/fog/service/ipxe/boot.php##params[/url] -
Okay, as the video is kind of grainy please bare with me.
What is the value stored in FOG_PXE_BOOT_IMAGE from FOG Configuration->FOG Settings->TFTP Server
-
The value for FOG_PXE_BOOT_IMAGE is init
-
Set it to init.xz
-
Well, I’m back to square one now. The drives have been put in legacy mode, the kernel has been updated, and fog has been updated, but it still says it can’t register the host.
