I found a strange thing, an issue that i opened in oclp that usb not work was in april https://github.com/dortania/OpenCore-Legacy-Patcher/issues/126 , but you said that it was worked on may @Larsvonhier
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
macOS 11 Big Sur on Unsupported Macs Thread
- Thread starter dosdude1
- WikiPost WikiPost
- Start date
-
- Tags
- 10.16 macos unsupported
- Sort by reaction score
- Status
As I already wrote in GitHub, when you restore a BaseSystem.dmg to an internal disk drive any legacy IOUSB (internal trackpad, keyboard, bluetooth and external USB mouse, USB keyboard, USB bluetooth) are ignored so you can even complete a staged installer (using ASentientBot HaxLib from Catalina desktop) on internal disk, because it's only the AHCI (or whatelse internal disk driver) kext required, used and sufficient to boot the macOS kernel with its graphical environment.
Not surprising. I hve too many machines to keep track of which OCLP used at what time. So in May the info well dates back a couple of versions...
Afaik, it´s not a matter of SIP (disabled or not) as even terminal commands issued cannot circumvent corruption of snapshots or sealing. So imho it´s best to use tools like I wrote or @jackluke proposed. But if simple copying with disabled SIP does the job for you, fine!
I had made a small script for auto installing kexts. Try this then!
launch like : ./kinst.sh disk1s1 GMAX3100.kext
Code:
#!/bin/bash
#Thanks to https://github.com/moosethegoose2213
#By https://github.com/hexagonwin
echo "Install kext for Big Sur"
echo "Have SIP Disabled!"
echo "Run this like this : ./kinst diskname kext.kext"
echo "Find diskname using command diskutil list"
echo "Waiting 10 seconds in case you didn't properly did these"
sleep 10
echo "Mounting the specified drive ..."
sudo mount -o nobrowse -t apfs /dev/$1 ./nonroot
echo "Done!"
echo "Removing pre-existing kext ..."
sudo rm -R ./nonroot/System/Library/Extensions/$2
echo "Done!"
echo "Copying new kext ..."
sudo cp -R $(pwd)/$2 ./nonroot/System/Library/Extensions/
echo "Done!"
echo "Fixing permissions ..."
sudo chmod -Rf 755 ./nonroot/System/Library/Extensions/$2
sudo chown -Rf root:wheel ./nonroot/System/Library/Extensions/$2
echo "Done!"
echo "Rebuilding kernel cache ..."
sudo kmutil install --volume-root ./nonroot/ --update-all
echo "Done!"
echo "Blessing ..."
sudo bless --folder ./nonroot/System/Library/CoreServices --bootefi --create-snapshot
echo "Done!"
echo "Script finished! If you didn't get errors, the script was probably successful."
Last edited by a moderator:
We have kext Install for S/L/E
Working BS and Monterey
testing by me multiple time no issue
after reboot rename your disk as it was before use
Working BS and Monterey
testing by me multiple time no issue
after reboot rename your disk as it was before use
Any help appreciated, but mainly time is missing on my side right now. Weather of 2021 flooded my basement, just enough to endanger all precious hardware/books/floppy disks and other stuff...
Sorry for keep commenting. Then, do you have the EFI file that worked with USB? If then I would try to compare it with the current one..
@Larsvonhier just made an attempt of making a beta BigSur prelinkedkernel using your MB4,1 kext 1.3b, it'd useful an output from MacBook4,1 (that I don't own) running Catalina or Mojave of these:
edit:
I just made an attempt of prelinkedkernel (exactly not BKE) for BigSur beta and seems any IOUSBHost* has prelinked correctly, only omitted is AppleTopCase.kext (because can't find a compatible dependency), anyway I guess that maybe a trackpad or eventually an USB mouse and USB keyboard could work on MacBook4,1 BigSur.
Currently I don't included any Bluetooth kext (from Yosemite) and GMAX3100 driver (from Lion), because I guess the BaseSystem environment can work also without BT or GPU drivers loaded.
@Larsvonhier and @HexagonWin restore this DMG to any USB empty drive (2 gb are sufficient), then replace on its /System/Library/PrelinkedKernels/ this attached: prelinkedkernel beta for MB4,1
then try to boot the USB drive from apple startup manager (without OC) and targeting the USB with CMD+S , if you can type "exit" then it might work, otherwise try booting without CMD+S but with CMD+V and then if you reach the graphical environment try plug an USB mouse.
If you get an HID responsive BigSur BaseSystem, the main aim is allow a MacBook4,1 to use the most important BigSur (and Monterey or later) command:
additional notes: allow up to 5 minutes to boot the BaseSystem graphical environment, I included also the parrotgeek1 LegacyUSBInjector (that maybe is redundant, I should remove), if you need I could try make a prelinkedkernel with BT and GMAX3100 drivers.
Code:
kextstat | grep "USB" > ~/Desktop/usb.txt
kextstat | grep "HID" > ~/Desktop/hid.txt
and also the full output of this :
sudo kextcache -i / > ~/Desktop/kc.txtedit:
I just made an attempt of prelinkedkernel (exactly not BKE) for BigSur beta and seems any IOUSBHost* has prelinked correctly, only omitted is AppleTopCase.kext (because can't find a compatible dependency), anyway I guess that maybe a trackpad or eventually an USB mouse and USB keyboard could work on MacBook4,1 BigSur.
Currently I don't included any Bluetooth kext (from Yosemite) and GMAX3100 driver (from Lion), because I guess the BaseSystem environment can work also without BT or GPU drivers loaded.
@Larsvonhier and @HexagonWin restore this DMG to any USB empty drive (2 gb are sufficient), then replace on its /System/Library/PrelinkedKernels/ this attached: prelinkedkernel beta for MB4,1
then try to boot the USB drive from apple startup manager (without OC) and targeting the USB with CMD+S , if you can type "exit" then it might work, otherwise try booting without CMD+S but with CMD+V and then if you reach the graphical environment try plug an USB mouse.
If you get an HID responsive BigSur BaseSystem, the main aim is allow a MacBook4,1 to use the most important BigSur (and Monterey or later) command:
kmutiladditional notes: allow up to 5 minutes to boot the BaseSystem graphical environment, I included also the parrotgeek1 LegacyUSBInjector (that maybe is redundant, I should remove), if you need I could try make a prelinkedkernel with BT and GMAX3100 drivers.
Last edited:
Thanks! I'll try.
Should I give you the mojave output? I don't have it installed right now so maybe can I do it in setup usb? I have installer in my laptop so I can just restore that to a usb and run that from terminal?
P.S. I am using a 2.4g usb wireless keyboard since the internal one's line broke, can I just boot to the usb normally without oc and that's it? (I mean when I just boot to usb I disconnect my internal drive and do it in order to make it boot there)
PPS. And the full environment also works well without those, when I cloned my laptop bigsur's drive and made it autologin, and made it launch few programs on startup it booted fine and launched those (although of course I didn't have input of any!)
Last edited:
INFO - the July 5 version of the nightly OCLP GUI adds a requested feature - Wake on WLAN and further streamlines the installation process. HERE: https://nightly.link/dortania/OpenC...s/build-gui/main/OpenCore-Patcher-GUI.app.zip
Also from Mojave setup USB the kextstat is useful , the USB wifi keyboard should act the same way as an USB keyboard (or even internal keyboard), I mean as a generic HID device so it's not an issue.
If through BigSur with autologin you auto launch some "Remote mouse" app (this requires Ethernet network) maybe could attempt other tests.
Anyway try to restore that BigSurBaseSystem DMG to an USB drive, replace the attached prelinkedkernelMB41 on the USB path and try booting with CMD+S (or CMD+V) to check if you have any responsive input devices.
Okay, but what does cmd s or v do?
I mean I said about 2.4ghz wireless keyboard because it seemes like the command key in it doesn't work as a command key or something. It simply doesn't seem to work before the mac booted, so I can't do things like pressing option key to go to boot menu etc.
P.S. I have -v enabled as default in my mac pram settings
I mean I said about 2.4ghz wireless keyboard because it seemes like the command key in it doesn't work as a command key or something. It simply doesn't seem to work before the mac booted, so I can't do things like pressing option key to go to boot menu etc.
P.S. I have -v enabled as default in my mac pram settings
Last edited:
Ah right CMD+S or any EFI shortcut keys require a stock apple keyboard (from apple startup manager), so you could add "-s" in nvram, then just type from shell "exit" to continue macOS booting.
Exactly as CMD+V is "-v" boot-args in nvram.
I advise to use CMD+S because BigSur on legacy USB Mac has some IOHID issues when booting from apple startup manager, moreover through CMD+S (or "-s") you can quickly check if keyboard is responsive from shell or if you plug an USB Mouse if the infrared led is on that means HID devices are working.
Last edited:
Thanks.
Also but i restored but I can't find prelinked kernel thing, i only see like install macos big sur and hax blah blah
Also but i restored but I can't find prelinked kernel thing, i only see like install macos big sur and hax blah blah
it's hidden by apple, simply from terminal :
Code:
open /Volumes/BigSurBaseSystemfix/System/Library/PrelinkedKernels/
Last edited:
Thanks. I tried BigSurFixes and that prelinkedkernel, and it boots and usb also works. It is really slow (going to next step after clicking on english language takes more than 4 minutes) but still, it works! (but I'm not sure why is this so slow since hdd boot of the big sur installed image wasn't this slow, maybe usb speed issue).
it is also working without cmd s, it just boots well
Last edited:
I guess that slow is not due to the usb speed, rather to :
- redundant parrotgeek1 LegacyUSBInjector that I also included in BigSur beta prelinkedkernel, but should remove (anyway the LegacyUSBInjector worked for any other legacy USB Mac just MacBook4,1 is the issue)
- or some attempts from BaseSystem to reload its kernelcollection stock IOUSB kext (mismatching version with those I prelinked)
- or some generic IOBluetooth crashing (that I don't prelinked)
- or AppleTopCase.kext (that currently I can't prelink correctly in BigSur kernel cache)
then I'll try to make another prelinkedkernel and if works I tell how to replace any @Larsvonhier MacBook4,1 kext on an already installed BigSur and it might work with any responsive HID devices.
If that still produces a slow graphical BaseSystem, I could even try replace the internal BaseSystem Extensions with those from MacBook4,1 (included the GMAX3100 GPU drivers) in that way also the BaseSystem environment should be faster.
Last edited:
Yeah, I think this graphic issue is because of missing fb drivers. Also, mouse movements are being slow. Previousely in mojave or catalina with correct fb drivers at least window moving was smooth, but not in here.
And it really can be a problem of the usb drive, it's a very cheap sandisk usb drive
I'd exclude that it's USB drive speed, but you can make a quick test for this, just restore the DMG to an internal hard disk partition (also replace the prelinkedkernel there) and check if the BaseSystem menu environment is faster.
Anyway later I send multiple prelinkedkernel that you (and Larsvonhier) can try and check if they'll make faster the BigSur BaseSystem.
I even can provide a way to install BigSur directly from target MacBook4,1 (but only on internal SATA drive) , but first should check which kext are too incompatible.
It's a little faster. I think this isn't some usb something issue, I think this is just Big Sur being extremely slow in the machine, since I only have 2.5 gigabytes of ram.
2 GB RAM are sufficient to boot any BaseSystem till BigSur (not sure for Monterey) , if to select a language it takes 4 minutes it is too much, I will attach in some minutes a prelinkedkernel without LegacyUSBInjector .
Then later another with GMAX3100 and Bluetooth kext (I doubt I can also include AppleTopCase.kext).
Here is: prelinkedkernel beta for MB41 without LegacyUSBInjector
another: prelinkedkernel beta for MB41 with Bluetooth and GMAX3100 basic kext
try both and let me know if without LegacyUSBInjector prelinkedkernel you can boot without CMD+S and exit (or "-s" in nvram).
@HexagonWin check also if in BigSurBaseSystem upper right you have the Wifi detected and also try to use CMD+F5 and check if there is Sound.
Last edited: