Imaging Environment Updating Drivers
-
@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.
