NIC Intel 82579LM PXE issue
-
sounds like the kernel does not have the proper drivers for that network card. Have you tried a newer kernel through your kernel updates page? You can also try older kernels, and kitchensink kernels which have support for a wide array of devices.
-
Chad,
Yes, I tried newest Kernel and then rolled back to 2.6.3.33KS. Both new kernel and old worked great for Dell 780 machine but Dell 790 could not registered the host. I am trying to use chainloading and let you know.
Fogger -
I have these nics in some new Dell Optiplex 990 systems. Imaging these systems stinks. It starts out speedy, but over time the speed just continues to slow to a crawl. What should take 20 minutes takes hours.
All other systems I image on the same networking equipment and server are pretty quick. I am considering building a custom kernel to see if I can resolve the issue. I’ll probably just wait until .33 is finalized though because these systems also have 4K disks and that is not supported in other versions of fog.
Please do post your progress on this issue as you go. Thanks.
–astrouga
-
according to Intel’s website, the Intel 82579LM gigabit LAN controller should use the e1000e driver in linux. I was scouting around the net and saw where the e1000e driver added support for the 82579LM chipset back in November of 2010. It might be worth downloading the driver source files from Intel and recompiling your kernel overwriting the old source files with the new ones.
-
chad-bisd, I’ll give it whirl. I’ll see if I can use your instructions from the old forums.
Update: first run through… Kernel panic… I didn’t see any obvious issues. Suggestions? Things to watch out for?
-
I got a 3.4 kernel built and it works with my 0.33 beta FOG server. The imaging issues I had with this nic are now resolved. I’ll post a follow-up with the process next week.
-
Mostly, this worked for me. However, I missed the note at the bottom, which was critical.
[url]http://www.fogproject.org/wiki/index.php?title=Building_a_Custom_Kernel[/url]
I’m reinstalling FOG today and rebuilding the 3.4 kernel. I’ll take notes and post.Eric High:
Are you interested in trying the 3.4 kernel I built last week? Let me know if this link works or not:
[url]http://www.filedropper.com/bzimage34[/url] -
I am having this same issue and I’ve been watching this thread develop. I’m ready to try the 3.4 kernel.
I have a few questions…
- Is this for both 32 and 64 bit clients?
- Will this work on both 32 and 64 bit ubuntu?
-
You can use the link above. I didn’t have a better way to upload the file. You want to click on the download link that says “Download this file”.
Regarding your questions, the clients all use a 32-bit init.gz prodived by FOG. It doesn’t matter what your OS/arch is. I built the bzImage file on a 64-bit Ubuntu 12.04 system using the FOG .33 beta core.config file. I had to specify a 32-bit kernel for output because I was building on a 64-bit system. Hope I said all the correctly.
Just give it a try. The worst case is you are out 10 minutes of real time – the time it takes to download, assign the kernel to your client,and start the upload/download. Plus, if it doesn’t work I’ll try to build you one that does.
Just be sure to let us know if it solved your issue for you or not. -
Thanks… is this kernel 3.3 with the addition for this NIC? So, would I be able to use this kernel with all of my machines, since they all worked with 3.3? I am thinking it would be easier, if this works, to apply the kernel to all machines.
-
This is kernel 3.4 with the addition of the latest NIC driver, though I think it just recompiled the driver itself. Still, it solved my issues. You should be able to use it for all of you machines. Test it out though and let us know. It would be great to know make/model with successes or failures.
You know how to specify a kernel for a host, right? If not, I am sure it is in the wiki or forum somewhere. Otherwise, ask and I’ll look.
-
I tried downloading your kermel but it had no file extension and was only 10.4 MB where as the 3.4 kernel is 96 MB
I also tried just using the 3.4 kernel but when I got to the step of creating the bzImage I got this error:
make[1]: Nothing to be done for
all'. make[1]: Nothing to be done forrelocs’.
CHK include/linux/version.h
CHK include/generated/utsrelease.h
CALL scripts/checksyscalls.sh
CHK include/generated/compile.h
VDSOSYM arch/x86/vdso/vdso32-int80-syms.lds
VDSOSYM arch/x86/vdso/vdso32-sysenter-syms.lds
VDSOSYM arch/x86/vdso/vdso32-syms.lds
LD arch/x86/vdso/built-in.o
LD arch/x86/built-in.o
CC drivers/scsi/lpfc/lpfc_scsi.o
cc1: warnings being treated as errors
drivers/scsi/lpfc/lpfc_scsi.c: In function ‘lpfc_bg_setup_bpl’:
drivers/scsi/lpfc/lpfc_scsi.c:1900:11: error: unused variable ‘rc’
drivers/scsi/lpfc/lpfc_scsi.c: In function ‘lpfc_bg_setup_bpl_prot’:
drivers/scsi/lpfc/lpfc_scsi.c:2037:11: error: unused variable ‘rc’
drivers/scsi/lpfc/lpfc_scsi.c: In function ‘lpfc_bg_setup_sgl’:
drivers/scsi/lpfc/lpfc_scsi.c:2256:11: error: unused variable ‘rc’
drivers/scsi/lpfc/lpfc_scsi.c: In function ‘lpfc_bg_setup_sgl_prot’:
drivers/scsi/lpfc/lpfc_scsi.c:2386:11: error: unused variable ‘rc’
make[3]: *** [drivers/scsi/lpfc/lpfc_scsi.o] Error 1
make[2]: *** [drivers/scsi/lpfc] Error 2
make[1]: *** [drivers/scsi] Error 2
make: *** [drivers] Error 2 -
The size is fine. It should not have a file extension. Did you try using it? You need to put that file in /tftpboot/fog/kernel. Then associate your machine with that kernel. Then you can try an imaging task with it.
-
Will try it right now… stand by.
-
drum roll please…
-
No good… when uploading, getting partition errors. Tried to push it down, failed… said it pushed the image down really quick and finished in seconds.
We are working with a Fujitsu T731.
-
OK, I’ll get back to you next week. I’ve got to rolll for now. Sorry that didn’t work out for you. Does the kernel work for any of your other systems?
Follow-up if you make any progress.
-
We didn’t try other machines… We had to restore it to the old kernel so that we could continue working!
Hopefully, we can make some progress next week. Thanks for your help.
-
I tinkered with this some more. With the bzimage34 kernel… when it tries to push down to the client, it checks hard disk and says “image cannot be outside of disk” or something to that affect. Went into the client and it had a TON of partitions… more than the 250 GB hard drive… it was like 1TB+. I pulled out the HDD and reformatted in an external enclosure. Trying the push down again to the client.
-
Same error message: Can’t have partition outside the disk…
A message does flash really fast about an unsupported BIOS version… but I’m not sure if that is actually the problem we’re having.