Latest Addition ==> Bob.Omb's Modified Win10PEx64 v4.4 - RS5

Author Topic: Drivers  (Read 945 times)

danheretic

  • Newbie
  • *
  • Posts: 3
    • View Profile
Drivers
« on: October 23, 2018, 04:11:45 pm »
First I have to say, this is a fantastic resource. Kudos to Bob.Omb for putting this together. It fulfills the need I have almost exactly - I'm booting from USB to various computers that come through my office before redeployment at a university. I want to run hardware tests, benchmarks, and wipe hard drive before it goes out for redeployment or disposal.

The one part I can't get to work is newer MacBook/MacBook Pros with USB-C. (It works fine with Macs prior to the newer USB-C models.) The keyboard and touchpad drivers aren't included on the current Bob.Omb's PE.

I'm using option #2 to create, and I see in the readme that "new as of 9/17/18: You can now add drivers to the Y:\System\Drivers folder..." So I tried that, only I was having trouble locating the actual .inf files to use. Interestingly enough, there's a thread on the oven from Bob.Omb about downloading massive amounts of WinPESE compatibility drivers for Mac: http://theoven.org/index.php?topic=2327.0. I tried following that, using the cmd line method in the 8/19/18 update on that thread. No joy. I'm not sure if that method doesn't include drivers for this class of device? Also, this method generates huge amounts of files/folders (most I had to extract manually from .exe to .inf, time consuming) and I'm trying to honor the advice in the readme file that says "don't put too many in, it will slow things down".

There are some other docs from MS about injecting drivers using DISM but I'm trying to avoid that, since it would defeat the purpose of using Bob.Omb's simplified PE.

Any advice on getting recent MacBook drivers into the boot drive?

Bob.Omb

  • PE Baker
  • Administrator
  • Jr. Member
  • *****
  • Posts: 66
    • View Profile
Re: Drivers
« Reply #1 on: October 25, 2018, 03:36:56 pm »
The problem with Apple drivers is, each package overwrites eachother..  So for instance if you want it to be compatible with macbook air 7,1 you would get that driver set with briggadier... That particular driverset actually covers tons of macs not just the macbook air... When you start moving into the newer macs they kind of seperated the universal compatibility of a lot of the newer models..  So we can use the latest MacPro drivers, and they will overwrite the other drivers when installed into the system, and then you will only be compatible with the newest MacPro and maybe one or two other models...but the included drivers would be overwritten and you would no longer be compatible with those machines...

So for Macs you would need to put custom drivers for the exact model ONLY for them to work, unless it was a universal driver set that covered multiple models, which only the older ones do really cover a lot of machines at once..

The way it is currently set is the most universally compatible that is possible in one system

Its a bit hard to explain but I hope u get the idea... its very inconvenient to be compatible with mac most of the time except with the older models because they all generally used the same hardware, and the newer models do not...

« Last Edit: October 25, 2018, 06:21:59 pm by Bob.Omb »

Bob.Omb

  • PE Baker
  • Administrator
  • Jr. Member
  • *****
  • Posts: 66
    • View Profile
Re: Drivers
« Reply #2 on: October 25, 2018, 06:27:35 pm »
Also make sure there are no spaces in the names of the folders or files you put in the Y:\System\Drivers folder

It is a bug that has been driving me nuts because v4.3 on RS5 has some issue that arent worked out yet, and I haven't been able to share a fix yet due to the delay

danheretic

  • Newbie
  • *
  • Posts: 3
    • View Profile
Re: Drivers
« Reply #3 on: November 09, 2018, 04:17:12 pm »
Thank you Bob.Omb for the quick reply, and my apologies for the late one - I haven't gotten back to this project lately.

What you said about driver compatibility and the drivers overriding each other makes sense. I hoped it would be more elegant, but you know... Apple. :) Also thanks for the tip on the spaces in folder/filenames. I had avoided that, but good to know.

I still haven't been able to make the drivers work for keyboard/trackpad on newer Macs. I currently have access to a MacBook 12" (Mid 2017) aka MacBook10,1 and a MacBook Pro 13" (Mid 2017) aka MacBookPro14,2. Using brigadier I used the following options:

> brigadier --model=MacBookPro14,2 

Distribution 091-07726 supports the following models: MacBookPro14,1, MacBookPro14,2

> brigadier --model=MacBook10,1

Distribution 091-07726 supports the following models: MacBookPro14,1, MacBookPro14,2


As you can see, brigadier reported the same model numbers for both packages but omitted the MacBook10,1, which is what I queried for. So maybe it's using the same drivers between models and just forgot to add 10,1 to the list.

Either way, I tried extracting the drivers from the retrieved files from BootCamp-091-07726\$WinPEDriver$ and copied them to the USB under Y:\System\Drivers. Thinking to simplify, I also tried removing the $WinPEDriver$ folder and copied the contents of that directly into Y:\System\Drivers. Neither method worked on either Macbook. The drive boots, but the trackpad and keyboard remain unusable in the PE.

Maybe I am missing something basic about how drivers are supposed to be added to the USB, or how the folders should be structured?

I will try to obtain other Macbook models to test with - since the two models I have use the same driver package, it's possible that only this driver package has issues.

Has anyone else been able to successfully use the brigadier driver method with Bob.Omb's USB drive to get keyboard or trackpad to work on newer (USB-C) models of MacBook/MacBook Pros?

danheretic

  • Newbie
  • *
  • Posts: 3
    • View Profile
Re: Drivers
« Reply #4 on: November 14, 2018, 06:31:55 pm »
My workaround at this point is just plugging in an external kb/mouse. But of course with new MacBooks using USB-C, I must use an adapter and it's not super elegant. But it works.