adds suspend.md, updates state, removes some contradictions#732
adds suspend.md, updates state, removes some contradictions#732deqrocks wants to merge 1 commit into
Conversation
| # Wi-Fi and Bluetooth | ||
|
|
||
| The drivers for Wi-Fi and Bluetooth are included in a kernel with T2 support. But, we also need firmware to get them working from macOS. | ||
| The drivers for Wi-Fi and Bluetooth are included in a kernel with T2 support. But, we also need firmware to get Wifi working from macOS. |
There was a problem hiding this comment.
Some models need Bluetooth from macOS as well. Let's just avoid this change.
| Replace `/path/to/firmware.tar` with the actual path of the tarball. For example, if `firmware.tar` is copied to the Downloads folder in Linux, command to be run would be `sudo tar -v -xC /lib/firmware/brcm -f $HOME/Downloads/firmware.tar` | ||
|
|
||
| Then reload the Wi-Fi and Bluetooth drivers by running: | ||
| Then reload the Wi-Fi and Bluetooth drivers. For the Broadcom 4377 chip: |
There was a problem hiding this comment.
This addition is an unnecessary complication for people who hate reading guides. Let it remain as it is.
| |Touch Bar|🟢 Working|🟡 Partial|"Touch Bar Keyboard" mode works OOTB, where only the Function Keys or the Media/Brightness Control Keys are shown. Touch Bar drivers were upstreamed in kernel 6.15, but we still need apple-bce to make it work.|[apple-bce](https://github.com/t2linux/apple-bce-drv), [tiny-dfr](https://github.com/AsahiLinux/tiny-dfr)| | ||
| |Suspend|🟡 Partially working|🟢 Yes|A firmware upgrade attached to macOS Sonoma broke suspend. Some users were having difficulty with it even before Sonoma. The issue has something to do with the apple-bce driver, because suspend works when it's disabled.|[#53](https://github.com/t2linux/T2-Ubuntu-Kernel/issues/53)| | ||
| |Audio|🟡 Partially working|🔴 No|With proper configuration audio can work, however it is not stable in some older kernels and switching between speakers and when using the microphone. Microphone volume is low in some Macs.|[apple-bce](https://github.com/t2linux/apple-bce-drv)| | ||
| |Bluetooth|🟡 Partially working|🟢 Yes| 5 GHz Wi-Fi connection is recommended to prevent Bluetooth interferences.|[Setup guide](https://wiki.t2linux.org/guides/wifi-bluetooth/)| |
There was a problem hiding this comment.
Do we have any proof of that?
| |Bluetooth|🟡 Partially working|🟢 Yes| 5 GHz Wi-Fi connection is recommended to prevent Bluetooth interferences.|[Setup guide](https://wiki.t2linux.org/guides/wifi-bluetooth/)| | ||
| |Camera|🟢 Working|🔴 No||| | ||
| |Thunderbolt|🟢 Working|🟢 Yes|Needs`pcie_ports=native` in kernel parameters|| | ||
| |Touch Bar|🟢 Working|🟢 Yes|Touchbar works in native mode and can be customized using tiny-dfr or react-drm|| |
There was a problem hiding this comment.
There are tonnes of tiny dfr like daemons now. Let's just endorse tiny-dfr since that's what we maintain.
There was a problem hiding this comment.
I see no reason to support a daemon that does not survive suspend. I find your critique here very biased and close minded. I cooperated on react-drm to make the touchbar convenient AND survive suspend.
| ## Thunderbolt / slow resume times | ||
|
|
||
| We can either have fast resume from suspend, or we can have Thunderbolt support. Not both. | ||
| Linux by default masquerades as macOS to make certain features accessible. |
There was a problem hiding this comment.
I just find this paragraph way too informative and can imagine people saying "Yo I can't understand shit here, fix my suspend!" on the discord. Also, you need to link the guide to the yml to make it accessible.
|
PRing here remains to be a royal PITA. |
I believe the conflict of interest has increased a lot. All the best for KaiT2en |
What actually changed is that we were able to confirm things and sort out others. |
So instead of being impatient you can explain the situation in the chat as well. |
Despite adding impatience on your list of deqrocks' hot-headed character properties, you could always trust me. I think i have explained it all in the chat, but i understand your lack of time to read it. I also have a lack of time now because of KaiT2en maintenance and upstream work. |
|
If you read my review comments, I don't see any instance where I have objected to t2bce, or any other work of yours. Most are objectionable to the writing style. The wiki is for a common person, not someone who is interested in dev work and would want technical details. |
|
"Common people" shouldn't be tricked into wasting their time with a WIP product. It doesn't help common people, it doesn't help devs. |
I'm not sure how bad the reputation is outside your world. Anyways, even if it is, I wish KaiT2en supports the community well. Good luck. |
Outside my world? I don't understand. When you read reddit and watch YouTube that is actually out of the small T2 Linux discord world. Also i don't know what that KaiT2en talking is about. It is not competitive and it's not targeting "common people". Why did you start this? |
|
See I respect your contributions and your work. And I don't want to start a fight with you. Also, I'm not starting a competition or something. Infact I'm in a stage where I am gonna retire from all this stuff, so it doesn't affect me personally. As far as Reddit/youtube is concerned, there are criticisms everywhere. The problem is not bad reputation, it bad management. I'm taking about KaitT2en because you repeatedly kept saying contributing here is a PITA etc etc. So yes, you are free to manage that if you don't feel confident here. Also, kindly chat on Discord to make things easier. |
2 participants
No description provided.