Jump to content
1699 posts in this topic

Recommended Posts

4 hours ago, eSaF said:

The one caveat in rectifying Bluetooth PAN not showing up within Network when a clean install of Monterey is performed and to overcome this by way of upgrading BS...

BS gives option to add new network interface Bluetooth PAN but Monterey doesn't.

Edited by miliuco
BS gives option to add new network interface Bluetooth PAN but Monterey doesn't.
 
btpan.png.b57e085fecad09a017e2db11a36cb674.png

Maybe it’s just this round of betas. I wouldn’t go changing anything yet until next beta or release if it’s the same.


Sent from my iPhone using Tapatalk
  • Like 1
Correct - It's just that curiosity got the better of me as to why Bluetooth PAN was not showing in the Network left column. Now by upgrading via a clean install of BS it is now showing as should be but connection to iPhone is still a no go even though Continuity is working as should plus I still have the name disk Big Sur at the Boot Menu oppose to Monterey. So all that work I did to correct one problem was not worth it, so I agree with your post. In my opinion Monterey is no where ready for general release, too many nagging bugs are showing up from one Beta to the next.
 
[mention=23030]miliuco[/mention] @atuneddu - Thanks I forgot about that useful tip, just done it and Disk name change from BS to Monterey. :thumbsup_anim:

Still been a better experience than big flop I mean Big Sur.


Sent from my iPhone using Tapatalk
  • Haha 1
Hello.
Since it became 5140.1, the item of SMBIOS has increased, so I set it.
Because they searched the values for us,I think the values that OpenCore put together as Autogen.c are better.
I'm sorry for the automatic translation of Japanese pages, but the setting method is as follows.
https://mifmif-mydns-jp.translate.goog/alpha/?p=2117&_x_tr_sl=ja&_x_tr_tl=en&_x_tr_hl=ja&_x_tr_pto=nui
Thank you.
 
Ok after looking again i think we are talking about two different things.
In Clover now we have these 4.
FirmwareFeatures
FirmwareFeaturesMask
#ExtendedFirmwareFeatures
#ExtendedFirmwareFeaturesMask
 
What i want to know is how do we get the values the later two 
#ExtendedFirmwareFeatures
#ExtendedFirmwareFeaturesMask
 
EDIT:
 
I think we are talking about the same thing.
See attached pic for what i have done.
Hopefully this will work.
527748818_ScreenShot2021-10-09at8_30_32pm.png.2336bd1f46cbdfa593a40f727ec8cefb.png

Booted laptop with what’s pictured and all is fine so far. Edited by SavageAUS
  • Like 1
2 hours ago, SavageAUS said:


Maybe it’s just this round of betas. I wouldn’t go changing anything yet until next beta or release if it’s the same...

I think the same, it seems to be with betas. Anyway, I don't miss this feature too much.

 

Please remove in my quoted post the blank space of the image I attached and removed. Thanks.

Edited by miliuco
  • Like 1
6 hours ago, MifJpnAlphaPlus said:


For example.

.FirmwareFeatures = 0x8FD8FF576ULL,
.FirmwareFeaturesMask = 0x8FFDFFF7FULL,

 

 

This is misleading example.  Respect to Acidanthera but FirmwareFeatures are 32 bit only.... Not as you see.

These values correspond to ExtendedFirmwareFeatures (64bits) and in the case of ExtendedFirmwareFeatures is implemented then FirmwareFeatures can be forgotten.  Amen.

  • Like 1
  • Thanks 1
6 hours ago, Slice said:

This is misleading example.  Respect to Acidanthera but FirmwareFeatures are 32 bit only.... Not as you see.

These values correspond to ExtendedFirmwareFeatures (64bits) and in the case of ExtendedFirmwareFeatures is implemented then FirmwareFeatures can be forgotten.  Amen.

So if the values provided by opencore are incorrect can you please provide a way to get the correct values for clover for ExtendedFirmwareFeatures and ExtendedFirmwareFeaturesMask.

With all due respect it just seems counter intuitive to implement something that has no way of determining the values needed.

On 10/10/2021 at 7:26 PM, eSaF said:

@Ellybz - Time consuming but solved this way, it is a bug in Monterey when it is a clean install oppose to an upgrade from BS.

  Reveal hidden contents

1909676641_Screenshot2021-10-11at00_14_13.thumb.png.a6b4093e27e5b1dc526bbd601e887193.png

 

I did an experiment today. Noticed my Dell Hackbook Pro is too missing the Bluetooth PAN adapter, but not my iHack. Both have had the same upgrade paths, coming from BS to Monterey cheese and very recently a fresh install during Restore mode at Beta 9.

 

The major difference is the Hack using a real Apple iMac network adapter...

  • Like 4

Updated without issue. Still using the restrictevents.kext because I haven't read backwards to see what the consensus is. OC 0.7.4

Untitled.png

Edit: Should mention that universal control has shown up, but I can't seem to enable it. Same behaviour on authentic MBP.

Edited by Skyfallkavu
1 hour ago, eSaF said:

I also discovered this update not only removed Bluetooth PAN from Network list, it removed my HP printer which I had to reinstall. :wallbash:

  Reveal hidden contents

675901122_Screenshot2021-10-13at20_17_10.png.55b0e7a67727444dea83577982edd9f3.png

 :lol:

Make it two. But it removed PAN and my HP MFP off my real 2019 MBP as well, so might be either a beta thing or an undocumented change from the Jack cheese OS.

  • Like 1
  • Thanks 1
17 minutes ago, eSaF said:

What a complete mess this one is turning out to be, I am not sure why they have the prefix 'a' in the version reference maybe it should be 'z'. :hysterical:

Well, "a" means it is the first review of that release, that probably didn't went thru throughout testing and they had to fix something nastier. I vote on some zero-day flaws or major data loss incidents they are probably not going to disclose because that's what a beta code is known for: crashes and burns :fishing:

  • Like 2

Update went fine on my X1 Extreme (MacBookPro15,1 SMBIOS + Default SBM + OC 0.7.4).
Looks like third party bluetooth got killed though, my Intel bluetooth is dead. I've seen a couple other people's Intel bluetooth die, as well as legacy Mac bluetooth.

Spoiler

image.thumb.png.ed2163c126c1a57603cdb82ad09a99c8.png

 

  • Like 1
52 minutes ago, 1Revenger1 said:

Update went fine on my X1 Extreme (MacBookPro15,1 SMBIOS + Default SBM + OC 0.7.4).
Looks like third party bluetooth got killed though, my Intel bluetooth is dead. I've seen a couple other people's Intel bluetooth die, as well as legacy Mac bluetooth.

  Reveal hidden contents

image.thumb.png.ed2163c126c1a57603cdb82ad09a99c8.png

 

Bluetooth also dead in 2 of my hacks. Probook 4540s (180a/0b05) and old core 2 quad extreme xw4600 (413c/8143). 

Edited by Stefanalmare
  • Like 1

Well my bluetooth works, the update showed itself naturally, and the update is done and kicking... although I have no PAN Bluetooth too... but all in all is not bad...

 

Captura de ecrã 2021-10-13, às 23.30.20.png

Edited by MorenoAv
  • Like 3
32 minutes ago, eSaF said:

Yes my B/T working as before also but have you got it showing in 'Network'?

No, I didn't look at network, you're right, it's not displayed and also it can't be added, as you @MorenoAv and others are commenting.

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