Can't deploy on Dell Latitude 5410
-
@afaure Ah ok, in the firmware (bios) setup. Under disk mode, change it from raid-on to ahci mode and it will find the disk. Intel will not release the raid driver to the linux community so you need to switch the computer back to ahci (standard disk) mode. You can either leave it in ahci mode forever or change it after imaging back to raid-on. But what ever mode you pick it must stay in when and after OOBE/WinSetup runs.
-
@george1421 same issue…
My pc contact FOG and i have this message error:No network interfaces found, your kernel is most probably missing the correct driver!
Please check your network setup and try again…After that, i have the same error message (picture).
Do you have idea ?
Thanks.
-
@afaure how did we slip backwards here. The picture you posted before the issue was only with the disk now we have disk and network?? That is strange.
Next steps for debugging. Schedule a capture/deploy task (doesn’t matter which) again, but before you hit the schedule task button, tick the debug checkbox then schedule the task. PXE boot the target computer again. Then after a few screens you have to clear with the enter key you should be dropped to the FOS Linux command prompt. You may still see error messages while booting but you will still be dropped to the command prompt.
At the FOS Linux command prompt key in the following then take a picture of the results.
uname -r(if that fails key inuname -a)
lsblk
ip a s
lspci -nn | grep -i net
lspci -nn | grep -i sata
lspci -nn | grep -i raidWait at this command prompt for additional commands based on the results of the above. if there is too much text for one screen you may need to take and post 2 pictures.
-
@george1421 said in Can't deploy on Dell Latitude 5410:
Next steps for debugging. Schedule a capture/deploy task (doesn’t matter which) again, but before you hit the schedule task button, tick the debug checkbo
Hello George,
The picture -> https://ibb.co/0ySfZNj
Thanks for your help
-
@afaure Ok the driver for that network adapter first appeared in linux 5.5. I’m missing the picture of the first 2 commands I asked for. The good thing the sata adapter is being seen by linux.
-
@george1421 said in Can't deploy on Dell Latitude 5410:
Ok the driver for that network adapter first appeared in linux 5.5. I’m missing the picture of the first 2 commands I asked for. The good thing the sata adapter is being seen by linux.
I have typed all commands:
uname -r
lsblk
ip a s
…I have missed somethings
?Thanks
-
@afaure I think from the picture you did too soon.
from the picture
uname -roruname -ashould have returned a value. It should be a number like 5.6.18 or 4.19.65The
lsblkshould have displayed the block devices in the system. It could be blank but it would be really rare. -
@george1421 said in Can't deploy on Dell Latitude 5410:
I think from the picture you did too soon.
from the picture uname -r or uname -a should have returned a value. It should be a number like 5.6.18 or 4.19.65
The lsblk should have displayed the block devices in the system. It could be blank but it would be really rare.Ok, picture with info -> https://ibb.co/vzxGFdh
I’m off for few days, i’ll be back wednesday at office to read your message. -
@afaure Ok from the new picture. You need to download the latest FOS Linux kernel using the Web UI FOG Configuration -> Kernel You need to install 5.6.18 kernel and the network adapter will work. You will need both 64 bit and 32 bit versions.
From the lsblk command the disk is there an available now.
-
@george1421 thanks !!!
I try your solution wednesday ! -
@george1421 same issue with the kernel 5.6.18
-
@afaure So when you schedule a debug mode and then at the FOS Linux command prompt you key in
uname -roruname -ait says 5.6.18 now?Leave it in debug mode because there are a few more debug commands we can use.
-
@george1421
uname -a said 4.19.145
lsblk list all of partitionsIf i try to register a new pc, same issue
PC contact fog but can’t deploy an image… -
@afaure said in Can't deploy on Dell Latitude 5410:
4.19.145
OK for some reason the upgraded to the kernel did not make it correctly. This uname command should have returned 5.6.18. So I understand why you have the same issue as before.
Please use the FOG Configuration -> Kernel to update both bzImage and bzImage32 to 5.6.18. If the webgui method doesn’t work then we can use the manual update process. Follow the manual instructions here: https://wiki.fogproject.org/wiki/index.php?title=Kernel_Update
-
@george1421 i have tried manual update and doesn’t work.
Same version, 4.19.145 !How i can download the latest version ?
Do you have link for wget ?Thanks
-
@afaure I don’t understand what is going wrong here.
OK there is an alternate manual process. Go to this web site: https://fogproject.org/kernels/
Download Kernel.TomElliott.5.6.18.64 and rename to bzImage (watch your case)
Download Kernel.TomElliott.5.6.18.32 and rename to bzImage32 (watch your case).Move those files to your fog server in the following directory replacing the existing files.
/var/www/html/fog/service/ipxeOnce the file is there then run this command to confirm the right version is in place
file bzImageit should say in the text 5.6.18 -
@george1421 thanks dude !
It’s works !!!Thanks for your help
