Jump to content
1699 posts in this topic

Recommended Posts

1 hour ago, greythorne said:

Am running Monterey beta 1 on my hardware. When on Big Sur, bluetooth works by using IntelBluetoothFirmware.

 

However, In Monterey bluetooth is not working. I even used a usb bluetooth dongle but still bluetooth not working. Anyone know what i can do?

intel Wifi + intel Bluetooth Work a Monterey 

 

Spoiler

collage.thumb.png.f8adcf4df9f175cdb6c6e7cd5606a6c3.png

 

Bluetooth Intel & Wifi Intel a MonteRey tested 

Bluetooth intel = https://openintelwireless.github.io/IntelBluetoothFirmware/FAQ.html#what-does-this-kext-do
Kext = IntelBluetoothFirmware.kext + BlueToolFixup.kext

NO = IntelBluetoothInjector.kext = KernelPanic Monterey


wifi Intel = https://github.com/OpenIntelWireless/itlwm/releases
wifi intel x2 = https://github.com/1hbb/OpenIntelWireless-Factory

wifi kext 1 =  itlwm + Heliport = work = https://openintelwireless.github.io/HeliPort/#chat
wifi kext 2 = Airportitlwm alpha = work = https://github.com/OpenIntelWireless/itlwm/releases

Edited by PG7
14 minutes ago, PG7 said:

intel Wifi + intel Bluetooth Work a Monterey 

 

  Hide contents

collage.thumb.png.f8adcf4df9f175cdb6c6e7cd5606a6c3.png

 

 

What? Howcome I am unable to run it? I am using the WiFi & Intelbluetooth kext from the same webpage you listed yet my bluetooth option on the bar is greyed.

1 minute ago, greythorne said:

 

What? Howcome I am unable to run it? I am using the WiFi & Intelbluetooth kext from the same webpage you listed yet my bluetooth option on the bar is greyed.

 

10 minutes ago, PG7 said:

Bluetooth Intel & Wifi Intel a MonteRey tested 

Bluetooth intel = https://openintelwireless.github.io/IntelBluetoothFirmware/FAQ.html#what-does-this-kext-do
Kext = IntelBluetoothFirmware.kext + BlueToolFixup.kext

NO = IntelBluetoothInjector.kext = KernelPanic Monterey


wifi Intel = https://github.com/OpenIntelWireless/itlwm/releases
wifi intel x2 = https://github.com/1hbb/OpenIntelWireless-Factory

wifi kext 1 =  itlwm + Heliport = work = https://openintelwireless.github.io/HeliPort/#chat
wifi kext 2 = Airportitlwm alpha = work = https://github.com/OpenIntelWireless/itlwm/releases

 

 

follow what i marked

Pay attention to only use what I marked because you cannot use the same method you used in Big Sur

I've already tested everything I marked and it works as in the prints
Hope this helps

I use Google translator
I hope the translation is comprehensive

33 minutes ago, PG7 said:

 

 

 

follow what i marked

Pay attention to only use what I marked because you cannot use the same method you used in Big Sur

I've already tested everything I marked and it works as in the prints
Hope this helps

I use Google translator
I hope the translation is comprehensive

How and where do i get the BlueToolFixup.kext? Do I need to compile myself or it is available?

55 minutes ago, PG7 said:

 

 

 

follow what i marked

Pay attention to only use what I marked because you cannot use the same method you used in Big Sur

I've already tested everything I marked and it works as in the prints
Hope this helps

I use Google translator
I hope the translation is comprehensive

Ok managed to get the bluetoolfix.kext from dortania.

 

Got bluetooth working, however when logged in, i turned off but cannot turn on back. In Big Sur i can turn on/off any time.

10 minutes ago, greythorne said:

Ok managed to get the bluetoolfix.kext from dortania.

 

Got bluetooth working, however when logged in, i turned off but cannot turn on back. In Big Sur i can turn on/off any time.

yes you still have this problem but... you know it's still in precorse

don't forget that we're only in the DEV Beta and that there's still a lot of work ahead for the devs to put everything more or less functional correctly.

this first step is already working just cannot turn it off

you have to use github and see each commit what they repair and test !
google translate

  • Like 1

Updated without any trouble here. Graphics card is now displayed in the ATM screen. Still no bluetooth (it's pretty ancient but worked in Big Sur) and my other internal drives are still appearing on my desktop, with some of them having eject icons in the Finder sidebar (despite being non-removable). I guess something has changed in the generic AHCI controller.

  • Like 2
5 minutes ago, mnfesq said:

I couldn't get beta 2 to install using OC .71 but it installed just fine with Clover 5137.  Same thing with bluetooth.  Works fine with Clover, not so with OC.  Still working on getting it to work with OC.

Hi @mnfesq what bluetooth do you have? 

I have an Fenvi T- 919 and I can't make It work with OC 0.7.1, I tried everything, but I managed to install Monterey Beta 2, with OC...

Thanks 

unnamed.jpg

  • Like 1
5 minutes ago, MorenoAv said:

Hi @mnfesq what bluetooth do you have? 

I have an Fenvi T- 919 and I can't make It work with OC 0.7.1, I tried everything, but I managed to install Monterey Beta 2, with OC...

Thanks 

 

I have this module: [0a5c:216f] Dell DW1560 4352+20702 M.2

 

My problem using OC to install beta 2 is that it would not complete the installation process after the first reboot and the MacintoshHD would never disappear from the OC boot menu.  Booting up repeatedly from MacintoshHD did not do anything and booting from the drive with Monterey on it just took me back to beta 1.  Mid-installation, I switched from OC to Clover, booted up to MacintoshHD, allowed it to install completely and upon reboot, MacintoshHD was gone from the Clover menu and the installation completed successfully booting to my Monterey partition (taking 2 reboots to complete).

  • Like 3
8 minutes ago, mnfesq said:

 

I have this module: [0a5c:216f] Dell DW1560 4352+20702 M.2

 

My problem using OC to install beta 2 is that it would not complete the installation process after the first reboot and the MacintoshHD would never disappear from the OC boot menu.  Booting up repeatedly from MacintoshHD did not do anything and booting from the drive with Monterey on it just took me back to beta 1.  Mid-installation, I switched from OC to Clover, booted up to MacintoshHD, allowed it to install completely and upon reboot, MacintoshHD was gone from the Clover menu and the installation completed successfully booting to my Monterey partition (taking 2 reboots to complete).

In my case, OC 0.71 does not detect any updates. do it many times until I have to go back to use CLOVER

53 minutes ago, antuneddu said:

Sorry but what's in it, it's not the bootloader that detects updates

I'm very new to OC. I don't understand much EN language. Always use google translate. I really want to know what's in bootloader or not What part do you have doubts? please tell me thank you

must try to return OC the previous version again 0.6.5
This one feels much more flexible. DSDT.aml can be customized as needed. and feel that version 0.7.1 Very sensitive, can't make a little mistake (broken)

Edited by naiclub
1 hour ago, mnfesq said:

 

I have this module: [0a5c:216f] Dell DW1560 4352+20702 M.2

 

My problem using OC to install beta 2 is that it would not complete the installation process after the first reboot and the MacintoshHD would never disappear from the OC boot menu.  Booting up repeatedly from MacintoshHD did not do anything and booting from the drive with Monterey on it just took me back to beta 1.  Mid-installation, I switched from OC to Clover, booted up to MacintoshHD, allowed it to install completely and upon reboot, MacintoshHD was gone from the Clover menu and the installation completed successfully booting to my Monterey partition (taking 2 reboots to complete).

Strange but true I also had the same problem with OC and Macintosh hd .. solved by putting on clover, let's hope someone sheds some light on this I'm very curious

2 minutes ago, antuneddu said:

Strange but true I also had the same problem with OC and Macintosh hd .. solved by putting on clover, let's hope someone sheds some light on this I'm very curious

Me too. It seems to be installing beta 2, rebooting, etc., but at the end I stay in beta 1. Tried 2 times.

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