Network fails on compatibility test
-
I know it’s rare, but could the NIC be bad?
-
hmmmmmm
You’re running 1.0.1 right?
I’ll bet the file that’s loading is bzImage, not bzImage32.
[code]sudo mv /var/www/fog/service/ipxe/bzImage /var/www/fog/service/ipxe/bzImage_05JUN2014
sudo mv /var/www/fog/service/ipxe/bzImage32 /var/www/fog/service/ipxe/bzImage32_05JUN2014
sudo wget -O /var/www/fog/service/ipxe/bzImage --no-check-certificate https://mastacontrola.com/fogboot/kernel/bzImage
sudo wget -O /var/www/fog/service/ipxe/bzImage32 --no-check-certificate https://mastacontrola.com/fogboot/kernel/bzImage32[/code] -
I am, 1.0.1 on Ubuntu 13 on a Dell Optiplex 755. I will run those commands real quick
-
Right after I select Perform Full Host Registration, it [I]does [/I]say
[QUOTE]/bzImage… ok[/QUOTE]
So this could be the problem -
[quote=“Jordon Rapp, post: 29349, member: 24302”]Right after I select Perform Full Host Registration, it [I]does [/I]say
So this could be the problem[/quote]
Why would that be a problem?
-
Could that possibly mean it’s loading bzImage, and not bzImage32, as you said?
-
That’s expected in 1.0.1.
bzImage is 64 bit, bzImage32 is 32 bit.
That means you’re loading init.xz and NOT init_32.xz.
If you copied bzImage32 as bzImage your system would panic.
There’s no issue, just want to make sure the right files are updated.
-
I think I’m narrowing it down to hardware, and not software. I’ve tried many kernels, and everything is open on the network.
-
So do you have any “identical” systems that you could test with?
-
We do have a few more 780’s around the branch, our SVP has one and is leaving soon, I will check when he leaves in an hour.
-
[quote=“Tom Elliott, post: 29362, member: 7271”]So do you have any “identical” systems that you could test with?[/quote]
Well, bad or good news, depending on how you look at it. The other 780 I tried, while a different version of 780, did the same exact thing as the previous 780 I was working on.
-
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.
