OptiPlex 5480 All-in-One
FOG version 1.5.9
I’m trying to image a set of dell all in one 5480’s and i can’t see to find a kernel that is compatible with the NIC.
I’m getting an No network interfaces found, your kernel is most probably missing the correct driver!
Which kernel should i be using to image these?
@sebastian-roth You correct, I just used the file of that new kernel and it worked.
I didn’t want to overwrite the kernel that we are using by default for all computers. So i downloaded the newer Kernel, 5.10.19 and just specified that kernel in the host machine.
Not overwriting is wise. But where exactly did you put it? It should go to
/var/www/html/fog/service/ipxe/directly. Then just use the filename
bzImage32-222021in host settings.
@sebastian-roth I didn’t want to overwrite the kernel that we are using by default for all computers. So i downloaded the newer Kernel, 5.10.19 and just specified that kernel in the host machine.
@The-Dealman Why do you use a subdirectory for this kernel? While it does show
...okat the end of that line I am fairly sure it’s unable to properly load it from your FOG server.
@sebastian-roth I just tried both the 32 and 64 versions of that newer Kernel, 5.10.19 here is the error i get with both
@sebastian-roth Sure. I will give that a try and report back
@The-Dealman Can’t find anything too obvious in the messages output yet.
Meanwhile we uploaded a way newer Kernel, 5.10.19, would you give that a try?
@The-Dealman Beside grabbing and uploading the messages log here (hopefully that will help) you might also run
ip a son the debug console and post a picture of the output here.
@the-dealman I’m not seeing where its init’ing the network adapter in that screen shot. Will you upload the /var/log/messages file using this process and post it in this thread (I want to see the entire log file):
- Insert the usb drive into the target computer.
- issue this command from the debug console
- I identify the usb flash drive by its size in the list. For the reset of this lets assume it shows up and
- Now let make a directory where we can mount that usb drive.
- Lets connect the usb drive to that directory
mount /dev/sdb1 /ext
- That command will mount the first partition on that usb stick to the /ext directory. Issue this command to see the contents of the usb drive
ls -la /ext
- If you see what is expected then copy the log file to the use flash drive directory.
cp /var/log/messages /ext
- When done unmount that usb drive with
- Now you will be able to remove the usb drive. Don’t remove it before you unmount it and the command completes.
@george1421 okay that worked but i didn’t see any error that said “failed to find”
This section has some network information, does this help?
@the-dealman Well I tried to be like them cool linux kids and spit out commands left and right, but it seems I can’t spell worth a hoot.
Lets try this command with the missing e
dmesg | less
I followed those instructions but i just see a blank screen with a box that says standard input
@the-dealman Yes that is what I needed.
Intel nic 8086:0d4c first introduced into linux kernel 5.5. So kernel 5.6.18 should work. With that said, there is probably firmware needed.
I need you to do this process to see what is missing.
- Manually register this computer with FOG.
- Schedule a capture or deploy task (doesn’t matter) but before you hit the schedule task button enable the debug checkbox. Then schedule the task.
- PXE boot the target computer.
- After several screens of text where you clear with the enter key you will be dropped to the FOS Linux command prompt.
- At the FOS Linux command prompt key in
dmsg | less. Search the entire log file. You are looking for “Failed to find file fw…” I need to see that section of the log file. It will list the missing firmware we need to bake into the kernel.
@george1421 I tried those kernels and they did not work.
Is this what you are looking for?
@the-dealman Lets start by having you update to the FOS Linux kernel 5.6.18. This is done via the webui -> FOG Configuration -> Kernel update. Install both the x64 and x86 kernels.
If that doesn’t work then we need to get the hardware ID of that NIC. You can do this via the device manager. I need both the vendor id and device id.