Posts made by RipAU

Yep same issue, redownloading now.

testing now.

I can test them both on the other OptiPlex 760 and OptiPlex 780, but I am suspecting it is the same issue with the E1000E driver.
I can’t really find much on Google about this issue either.

Just tested both on the Dell OptiPlex 755

The bzImageE1000 didn’t load any network at all and didn’t report any errors and shows the network ip/mac as blank.
The bzImageE1000E reported the usual Reply not for us, op[2] etc. and then showed the network/mac as blank again

ok, I’ll download that now to bzImage
I’m suspecting both versions are the 64bit one?

No worries,
Thanks for the help, especially since I suspect our timezones are significantly different.

Cheers,

Yep no worries

Sorry,
Yes it repeats the message DHCP/BOOTP reply not for us etc. over and over and then fails to load an IP Address via DHCP when loading into fog client system information (compatibility) menu option.
I’m using the Kernel from unofficial Tom Elliott version 3.15.0

I updated the BootMenu.class.php before I tested it all again so I’m guessing that pcie_aspm might not be the issue?

No worries, I am happy to test any of the kernels as this is the one show stopper I have found for fog 1.x.x for us.

Just testing a bunch of our desktops -

Dell OptiPlex 745 - Intel 965 Express - Broadcom NetExtreme 57xx NIC- Drivers load fine and IP Address gets assigned quickly
Dell OptiPlex 755 - Q35 Express Chip - 82566DM-2 NIC - Intel Drivers fail to load correctly
Dell OptiPlex 760 - Q45/Q43 Express Chip - 82567-LM3 - Intel Drivers fail to load correctly
Dell OptiPlex 780 - Q45 Express chip - 82567-LM3 - Intel Drivers fail to load correctly

Wikipedia has a good page for the Dell OptiPlex that matches up to mine for Chipsets - [url]https://en.wikipedia.org/wiki/Dell_OptiPlex[/url]

Also just installed the new BootMenu.class.php all seems to be working for the iPXE/Fog menu.
I’ve got a few options set in the advanced menu as well and that looks good as well.

Is it possible to get the wiki page with data relating to the 1.x.x release?
Or possibly a new compatibility page for version 1.x.x mainly because of the large changes in support due to swapping to the 3.x.x kernel over 2.6.x ? with notes listing possible issues/work arounds.

The old page I found was - [url]http://fogproject.org/wiki/index.php/WorkingDevices[/url]

Just found this post on the forum with the same symptoms -
[url]http://fogproject.org/forum/threads/bzimage-intel-e1000e-driver-and-dell-vostros-400-bad-news.10163/[/url]
Sounds like the same issue to me with the network card locking up until windows loads and restarts the network card.
I have a different NIC (82566DM-2) but the issue sounds related?

:EDIT:

I just tested on another Dell OptiPlex 755 same result.

I just tried the ones from the kernel updates 3.15.0
I tried the x86_64 and x86
x86_64 had the same issue with “Reply not for us” and then showing the network interface as blank after it finally loaded.
x86 also had the same issue with “Reply not for us” but then did a kernel panic and reported the issue with init

They have stopped reporting “Ignoring Fragmented Packet” though.

Cheers,

We have several hundred of these so hopefully I can find a fix

Hi Guys,

I thought I would start a new post as not to derail the other forum post.

I have found with using the Latest Kernel from FOG with trying to run re imaging/compatibility mode I am finding that the Kernel is not loading the network card correctly.

I ran through compiling my own kernel with using the fog .config file and following the wiki and have isolated (I believe) to the e1000e driver. None of the other modules will load any drivers for the network card only the e1000e.
After loading with the latest kernel and the e1000e driver I get the following display:

[IMG]https://i.imgur.com/2CdmE5h.jpg[/IMG]

The last known good version I have working on this with my older fog installation is 2.6.33FOG_KS
I’m guessing it isn’t possible to try load this older kernel just for our older PC fleet?

Does anyone have any suggestions on what I can try?

Compile in the old version of the e1000e driver in just for the Dell OptiPlex 755s ? ( I did try the driver from a 2.6 kernel and this failed as I assume it is completely different from the version 3.14.5)

I’m guessing that the drivers have to be built in and can’t be modules that I can insert?

The Dell 755 is listed as a Q35 Express chip and the network adapter is listed as Intel 82566DM-2 in windows.
I’m happy trying to re-compile my own kernel versions which I have been doing most of Friday afternoon but cannot work out what to try next.

Cheers,

[quote=“Tom Elliott, post: 29501, member: 7271”]I’m adding to the “advanced” items in the user guide to add how to build the ipxe/undionly files. Also, i’ll add this as a part of it.

Thank you.[/quote]

No worries, hopefully it helps people until the iPXE issue is resolved.

Cheers,

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,

I found a work around and tested a few things I found from the forum and iPXE website
It seems seems to be working well on all the computers I have tested so far -
[url]http://fogproject.org/forum/threads/ipxe-issues-work-around.10727/[/url] Just FYI if it helps anyone.

Hi guys, as a quick workaround till the iPXE issues are working I posted this in another post.
Might help a few people?

[url]http://fogproject.org/forum/threads/ipxe-issues-work-around.10727/[/url]

Cheers,

Hi Guys,

As a few people have had issues with iPXE booting correctly (me included)
I thought I would post this and see if it helps anyone.

In the /tftpboot/ folder:
I ended up symlinking pxelinux.0.old to pxelinux.0
creating pxelinux.cfg folder then creating default inside that.
inside pxelinux.cfg/default I created the options:

[CODE]
DEFAULT vesamenu.c32
MENU TITLE Fog Reimage Menu

MENU COLOR TITLE 1;36;44 #ffffffff #00000000 std
MENU BACKGROUND images/black.png

LABEL iPXE Boot
MENU DEFAULT
KERNEL ipxe.krn
APPEND dhcp && chain http://10.0.0.253/fog/service/ipxe/boot.php?mac=${net0/mac}
PROMPT 0
TIMEOUT 1
[/CODE]

After that I changed the pxeboot service to point at pxelinux.0 instead of the undionly.kkpxe file

Its not ideal I guess but it means I don’t have to change and play with fogs default files.

Cheers,

Ok just tested with each file in --> [url]http://mastacontrola.com/ipxe/latest/[/url]

I’m finding the ipxe.kkpxe still has error 040ee119 but the undionly.kkpxe had an error with default.ipxe error 3d126001 (Dell OptiPlex 755 and Dell Latitude E5410)
I didn’t get the error code for the rest of the files but I can re-test and write them down if needed.