Imaging Environment Updating Drivers
-
Hi,
I have been having some issues with a new laptop PXE booting and I believe this is because the driver is not installing/being found in any of the environments. I even tried the latest WinPE from your directions.
I attached a picture from the WinPE boot.
I tried to statically assign the IP. I get this same error in any of the environments.
Server is reachable from address and I can image other older machines.
Do you have any direction on adding drivers to the environments? The laptop in question is a Lenovo P15s Gen 1 (type 20T4 20T5) Laptop (ThinkPad) - Type 20T4.
Thanks for any expertise you or anyone else can share with me.
Thanks! -
I've added a new kernel for the LIE if you want to try it. You can download it by going to admin settings->Kernels and clicking download on 5.10.11x64. Then you will need to rebuild your use / pxe menu's with the new kernel selected in the drop down before you build.
The WIE gives you the option to add your own drivers. In the optional/drivers folder, put the nic drivers in the correct x86 or 64 folder. The drivers must be in inf format, you can't just throw an exe in there.
-
Thanks for the quick response. I tried adding the drivers and that worked! I will try the new kernel later this week and report back how it goes. Thanks again!
-
Yep the 5.10.11x64 Kernel worked perfectly!
Is it possible to use the proxy to set the preferred Kernel by mac address? Like by adding a line in the ini? I was looking at the documentation on CloneDeploy.org and don't see anything.
Could be a cool option if you could set the kernel to use per machine. -
@theopenem_admin Hi, where is the optional/drivers folder located?
-
If you are using the winpe builder, there isn't much to say, it's in the builder folder then optional/drivers. I'm assuming you aren't using winpe and that's why you can't find it.
-
@theopenem_admin oh okay yeah i did put the driver in there but it's still saying that it can't find the driver.
I've had to try to switch to WIE because on LIE, whenever I try to change the Kernel to the newest Kernel on the boot menu, it will just keep reverting back to 4.20.10, so now i'm trying to see if i can set up WIE.
-
It's not reverting back, the value isn't stored, whatever you have selected is only used once when you generate the boot files. Did you try the 5.10.11 kernel for the LIE? Were your drivers in inf format for the WIE?
-
@theopenem_admin Yes, I've tried to changing the kernel to 5.10.11 and then I clicked on Create Boot Files. But once I leave the page and come back, it'll revert back to 4.20.10.
Yes, the drivers were in INF format as well.
-
Are you sure this is a driver issue? Are any other models working?
-
@theopenem_admin yes, i figured it out now. I was able to inject the driver directly into the wim file. but on another question, I'm unable to boot via UEFI mode and it only works on legacy. do you have any suggestions? Thank you for your quick replies. it is greatly appreciated.
-
I can't really think of a reason why winpe wouldn't boot for UEFI. I've never had issue's with winpe since it's already signed by Microsoft. Are you pxe booting or usb?
-
@theopenem_admin I'm sorry. i forgot to change the bios settings back from legacy. haha...
-
Hello, whenever I change these fields to the new kernel, and then create the boot files, it will just change back to 4.20.10 kernel. Is there a way to have it stay on the new kernel? Thank you.
-
Why are you using clonedeploy. It's not supported anymore.
-
@theopenem_admin oh this was just handed down to me so I'm just trying to figure things out.
-
Ic. You are going to have many diver issues with clonedeploy. It's too old. You should move to theopenem or use something else.
