Jump to content
1961 posts in this topic

Recommended Posts

15 hours ago, Irish_Man said:

Damn right :)

 

My was messed up and I didn't know about @RehabMan way so I used different approach.

From /Library/Preferences/SystemConfiguration I deleted these files, reboot, reset Nvram:

  • com.apple.airport.preferences.plist
  • com.apple.network.identification.plist or com.apple.network.eapolclient/configuration.plist
  • com.apple.wifi.message-tracer.plist
  • NetworkInterfaces.plist
  • preferences.plist

Pics are before and after:

 

Before.png.cb0dfac083afbf38825a859b8f59fc01.png

 

After.png.f1a885a7323191767a730fb4c5ddf409.png

Well I did the above procedure 3 times and the result is the same, my Wifi is en0 and Ethernet is en1, the only diference is that I don't have "com.apple.network.identification.plist or com. apple.eapolclient/configuration.plist.

For that reason, and all works I rest my case for now

Thank you

  • Like 3
3 hours ago, miliuco said:

Same EFI in the same machine, sometimes reading CPU name and sometimes not?

Do you have the settings as per @Max.1974 above post?

I mean:

  • RestrictEvents.kext enabled
  • NVRAM >> Add >> 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:
    • revpatch=sbvmm,cpuname,pci
    • revcpu=1
    • revcpuname=Intel Core i7-12700K Alder Lake (or whatever you want)
  • NVRAM >> Delete >> 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:
    • revcpu
    • revcpuname.

 

@Max.1974, @miliuco

Yes, everything is there as it should be.

The only thing I dont use is -lilubetaall bootarg.

 

11.png.8a57b28811f907e9c4bbcf76a8f96e6a.png

 

 

UPDATE: Well, I guess I do need to add "-lilubetaall" to be able to see a CPU name.

Edited by Irish_Man
  • Like 2
2 hours ago, MorenoAv said:

Well I did the above procedure 3 times and the result is the same, my Wifi is en0 and Ethernet is en1, the only diference is that I don't have "com.apple.network.identification.plist or com. apple.eapolclient/configuration.plist.

For that reason, and all works I rest my case for now

Thank you

My bad, I didn't have those two also. I just add it on the list in case it's there.

Btw, when you delete the files and if you remove/disable your wifi card it should set your ethernet to en0.

After that you can add your wifi card back. 

  • Like 3
15 hours ago, robi62 said:

hi where exactly is that???I cannot find it when I open show package contents????

I managed to fix the  "Unsupported OS" 

All I did was add restricevents.kext and add -no_compat_check to my boot args and now I have wifi

@PoMpls Thanks for editing my config plist  that really helped

 

It's in the OCLP source code and only relevant if you are building / running OCLP from source.

 

Your MBP15,2 appears to be fully supported in Sequoia.  I'm not sure why -no_compat_check would make a difference and I'm not sure why you didn't need RestrictEvents.kext in Sonoma but you did in Sequoia.  Glad you got it working.

  • Like 3
17 minutes ago, deeveedee said:

 

It's in the OCLP source code and only relevant if you are building / running OCLP from source.

 

Your MBP15,2 appears to be fully supported in Sequoia.  I'm not sure why -no_compat_check would make a difference and I'm not sure why you didn't need RestrictEvents.kext in Sonoma but you did in Sequoia.  Glad you got it working.

I though so thanks for clarification I have no idea too but at least  I can use OCLP for making wifi work

  • Like 1

I have an old (1999) HP LaserJet 2100 printer with JetDirect card.  I was able to add the printer to my hack running macOS Sequoia Beta 2 with the procedure here.

  • Like 3
4 hours ago, Irish_Man said:

My bad, I didn't have those two also. I just add it on the list in case it's there.

Btw, when you delete the files and if you remove/disable your wifi card it should set your ethernet to en0.

After that you can add your wifi card back. 

@Irish_Man I know but I'm being lazy, I have to open my case and unplug and plug my Fenvi card...

Too much work for a cosmetic issue, until the day, that it ceases to be, LOL

Thanks anyway

  • Like 5
1 hour ago, deeveedee said:

I have an old (1999) HP LaserJet 2100 printer with JetDirect card.  I was able to add the printer to my hack running macOS Sequoia Beta 2 with the procedure here.

 

Hi my dear @deeveedee maybe you can try install this genuine drivers: 

 

https://support.apple.com/kb/DL1888?viewlocale=en_US&locale=en_US 

 

and  or (both at same) 

 

https://support.hp.com/us-en/drivers/hp-laserjet-pro-m1212nf-multifunction-printer-series/model/3965848

  • Like 1
16 minutes ago, miliuco said:

 

Hi my dear friend, yes this driver it is 100% compatible.

I has installed normally here...:guitar:

 

image.png.b153e6ff93cc0f5116550ab228a1b80b.png

image.png.ba8a262827d04299c6b801b72b4e9b0d.png

image.png.1f228215657bbea361e98b64c1e77ffa.png

 

 

Edited by Max.1974
  • Like 3

Here's my best explanation for why the "Genuine" LaserJet 2100 Drivers do not work with my printer and why I needed to implement my solution.  I did test the available drivers from HP and Apple before posting.

  • Like 2

on macOS Sequoia beta 2 every time when I try to mount Internal EFI partition 

error message shows like this

Screenshot2024-07-08at11_24_08PM.png.7ba4c882dd695bd1e0db9313f41d5e84.png

Screenshot2024-07-08at11_23_46PM.png.1198a56b0bed459098383e260517b0cb.png

on Sonoma mount fine but on sequoia I get error message

other hand external's EFI Partition mount fine 

only on sequoia not mount internal EFI partition 

anyone get like this error on beta 2

I didn't mount my EFI partition on sequoia

anyone have idea it is bug of beta 2 or else other

27 minutes ago, ameenjuz said:

on macOS Sequoia beta 2 every time when I try to mount Internal EFI partition 

error message shows like this

Screenshot2024-07-08at11_24_08PM.png.7ba4c882dd695bd1e0db9313f41d5e84.png

Screenshot2024-07-08at11_23_46PM.png.1198a56b0bed459098383e260517b0cb.png

on Sonoma mount fine but on sequoia I get error message

other hand external's EFI Partition mount fine 

only on sequoia not mount internal EFI partition 

anyone get like this error on beta 2

I didn't mount my EFI partition on sequoia

anyone have idea it is bug of beta 2 or else other

Easy Way Is To Make A 1GB Fat32 Partition As The First Partition On SSD/HDD/USB

Copy Your EFI There, It Still Boots And Makes EFI Manipulation A Breeze

Painless

  • Like 2

HI mates, trying to install Sequoia beta2 on my gigabyte z490 pro, usb installer installed the 1st stage but, at 2nd stage (and for 2 days now) stuck at Less than a minute remaining... I can't continue installation after that. Using OC 1.0.0 and not using amfiPass.kext and/or restrictevent.kext and disabled all 3rd party kexts... any help pls will be appreciated

15 minutes ago, STLVNUB said:

Easy Way Is To Make A 1GB Fat32 Partition As The First Partition On SSD/HDD/USB

Copy Your EFI There, It Still Boots And Makes EFI Manipulation A Breeze

Painless

it is mountable on Sonoma 14.5 

issue is occurs on sequoia I think it is beta bug

I will wait for next beta

23 minutes ago, maly70 said:

sure

but it is 82.8 MB !!!

Delete the Apple Folder In Your Efi Folder

12 minutes ago, maly70 said:

Here is my EFI with personal info removed

EFI.zip 1.43 MB · 1 download

Wheres Your Kext Folder?

1 hour ago, ameenjuz said:

on macOS Sequoia beta 2 every time when I try to mount Internal EFI partition 

error message shows like this

Screenshot2024-07-08at11_24_08PM.png.7ba4c882dd695bd1e0db9313f41d5e84.png

Screenshot2024-07-08at11_23_46PM.png.1198a56b0bed459098383e260517b0cb.png

on Sonoma mount fine but on sequoia I get error message

other hand external's EFI Partition mount fine 

only on sequoia not mount internal EFI partition 

anyone get like this error on beta 2

I didn't mount my EFI partition on sequoia

anyone have idea it is bug of beta 2 or else other

 

@ameenjuz

 

Hi, how are you? 
I verify that it is using a Windows partition to use it as an ESP partition, and Windows creates it with a different partition. macOs Sequoia is still very "raw" compared to Windows partitions. It would be important for you to prioritize Hackintosh, rather than Windows, if you intend to use macOs. 

If this is not possible, there is a possible solution, which would be for you to purchase a license from Tuxera or Paragon NTFS, and try to mount your ESP (because it is not the same EFI as osx). 

However, before purchasing Tuxera, which is very affordable, I already did the tests, and I was only able to use Paragon NTFS and even then, after installing macfuse for free with home brew. And so I was able to run the NTFS drivers safely and stably. 

I would also add that Sequoia conflicts with third-party NTFS drivers and OCLP.

 

Mounty NTFS macfuse Sequoia solution

 

Install Mac fuse with brew

 

brew install --cask mounty

 

brew install --cask macfuse

 

brew install gromgit/fuse/ntfs-3g-mac

 

brew install --cask mounty

 

check here: 

 

https://mounty.app 

 

 

 

:plane:

 

 

image.thumb.png.a461447a4ed268072f82912971236b40.png

 

 

 

 

Important you install first of all home brew 

 

https://brew.sh 

  • Like 6
  • Confused 1
1 hour ago, STLVNUB said:

Delete the Apple Folder In Your Efi Folder

Wheres Your Kext Folder?

I had to remove it because could not upload but all kext files r uptodate. you can see all kext files r in config.plist

Trying now after I deleted Apple folder as you mentioned/// will let you know 

 

Edited by maly70
58 minutes ago, eSaF said:

I would have preferred if you did include the Kext folder as well within the uploaded EFI.

So that we could check for any updates needed. Quite frankly the config.plist needs cleaning up from unnecessary files.

 

I have removed some but there is a lot more that needs removing, I didn't go overboard but I made some changes.

You can try the attached EFI Folder and see if the situation improves.

 

If you're still having a problem, re-upload the EFI with the kext folder included, just remove the

S/N and ROM data.

EFI.zip 979.03 kB · 0 downloads

Thanks for reply mate// will let you know

59 minutes ago, eSaF said:

I would have preferred if you did include the Kext folder as well within the uploaded EFI.

So that we could check for any updates needed. Quite frankly the config.plist needs cleaning up from unnecessary files.

 

I have removed some but there is a lot more that needs removing, I didn't go overboard but I made some changes.

You can try the attached EFI Folder and see if the situation improves.

 

If you're still having a problem, re-upload the EFI with the kext folder included, just remove the

S/N and ROM data.

EFI.zip 979.03 kB · 0 downloads

the system does not let me upload more than 10MB file

  • Like 1
Guest
This topic is now closed to further replies.
×
×
  • Create New...