diff --git a/docs/contribute.md b/docs/contribute.md index c07cf11ae..2919c37ba 100644 --- a/docs/contribute.md +++ b/docs/contribute.md @@ -2,7 +2,7 @@ The T2 project itself currently does not accept financial donations. However, some of the contributors and maintainers of the project do accept donations on their own. You may refer to the [Support our maintainers](https://wiki.t2linux.org/contribute/#support-our-maintainers) section of this page to get the links of the same. -The best way of donation which we believe is in the form of skill. If you think you have the potential to help us in pushing the project further like fixing bugs, adding new features etc., you are free to do so. For this, you may contact our discord server, where other members of this organization are present. +The best way to donate, we believe, is in the form of skill. If you think you have the potential to help us in pushing the project further, like fixing bugs, adding new features, etc., you are free to do so. For this, you may contact our Discord server, where other members of this organization are present. ## Contribute to the code @@ -10,11 +10,11 @@ See "partially working" features at [State](https://wiki.t2linux.org/state/) to ## Support our maintainers -Here is the list and links to donate some of our maintainers. +Here is the list and links to donate to some of our maintainers. - [MCMrARM](https://github.com/MCMrARM) - Author of the [apple-bce driver](https://github.com/t2linux/apple-bce-drv). Donate via [Paypal](https://paypal.me/mcmrarm). -- [JPyke3](https://github.com/JPyke3) - Played major role in getting Manjaro working on T2 Macs. Donate via [Patreon](https://patreon.com/pykee) or [On Chain](https://github.com/JPyke3/mbp-manjaro#donations). -- [marcosfad](https://github.com/marcosfad) - Played major role in getting Ubuntu working on T2 Macs. Donate via [Paypal](https://paypal.me/marcosfad) or [GitHub Sponsors](https://github.com/sponsors/marcosfad). +- [JPyke3](https://github.com/JPyke3) - Played a major role in getting Manjaro working on T2 Macs. Donate via [Patreon](https://patreon.com/pykee) or [On Chain](https://github.com/JPyke3/mbp-manjaro#donations). +- [marcosfad](https://github.com/marcosfad) - Played a major role in getting Ubuntu working on T2 Macs. Donate via [Paypal](https://paypal.me/marcosfad) or [GitHub Sponsors](https://github.com/sponsors/marcosfad). - [NoaHimesaka1873](https://github.com/NoaHimesaka1873) - Currently maintains boot images and kernels for Arch and EndeavourOS. Donate via [GitHub Sponsors](https://github.com/sponsors/NoaHimesaka1873) or [Toss (South Korea residents only)](https://toss.me/yuruverse). - [Redecorating](https://github.com/Redecorating) - Played a major role in adding support for T2 Macs in the apple-gmux driver, required for hybrid graphics. Also has written T2 related kernel patches and worked on T2 related kernel regressions. Donate via [PayPal](https://paypal.me/redecorating). - [AdityaGarg8](https://github.com/AdityaGarg8) - Current maintainer of Ubuntu. Has also helped in writing T2 kernel patches and upstreaming various patches. Donate via **GitHub sponsors** ([Link](https://github.com/sponsors/AdityaGarg8)) or **Buy Me a Coffee** ([Link](https://www.buymeacoffee.com/gargadityav)). diff --git a/docs/distributions/arch/installation.md b/docs/distributions/arch/installation.md index 76640813f..4139f4a89 100644 --- a/docs/distributions/arch/installation.md +++ b/docs/distributions/arch/installation.md @@ -3,12 +3,12 @@ You will need: - USB drive with at least 1GB -- A way to plug it into your Mac (USB-C isn't USB-A) +- A way to plug it into your Mac (USB-C and USB-A are different) --- !!! Warning "Users in NA/EU might face slow download speeds from the mirror" - If you're experiencing slow download speed or failure to install, please edit your `/etc/pacman.conf` file and replace old mirror.funami.tech link with `https://github.com/NoaHimesaka1873/arch-mact2-mirror/releases/download/release` instead. You can also checkout the [arch-mirrors mailing list](https://lists.archlinux.org/archives/list/arch-mirrors@lists.archlinux.org/) to get information about latest downtimes for mirror.funami.tech. + If you're experiencing slow download speeds or installation failures, please edit your `/etc/pacman.conf` file and replace the old mirror.funami.tech link with `https://github.com/NoaHimesaka1873/arch-mact2-mirror/releases/download/release` instead. You can also checkout the [arch-mirrors mailing list](https://lists.archlinux.org/archives/list/arch-mirrors@lists.archlinux.org/) to get information about latest downtimes for mirror.funami.tech. 1. Follow the [Pre-installation](https://wiki.t2linux.org/guides/preinstall) steps. diff --git a/docs/distributions/debian/installation.md b/docs/distributions/debian/installation.md index 452591b8c..8c218740d 100644 --- a/docs/distributions/debian/installation.md +++ b/docs/distributions/debian/installation.md @@ -1,6 +1,6 @@ # Introduction -This guide shall help you in installing a Debian or Ubuntu based Linux distro, which is not available as a modified ISO with T2 support. +This guide will help you install a Debian or Ubuntu based Linux distro, which is not available as a modified ISO with T2 support. Some popular distros include: @@ -32,9 +32,9 @@ Some popular distros include: 2. The partition to be made compulsorily is the one mounted at `/` and formatted to **ext4** or **btrfs**. - 3. If the installer used by your distro is `ubiquity`, which is the one used in Ubuntu, Linux Mint etc., then you can leave EFI Boot alone. If you are using a [separate EFI partition](https://wiki.t2linux.org/guides/windows/#using-seperate-efi-partitions), then you shall have to separate it out after installation by following [this guide](https://wiki.t2linux.org/guides/windows/#seperate-the-efi-partition-after-linux-is-installed). - - For other installers, you need to mount `nvme0n1p1`, or your [separate EFI partition](https://wiki.t2linux.org/guides/windows/#using-seperate-efi-partitions) (whatever case applies to you) at `/boot/efi`. If the installer supports the "boot" flag, set it as well for your EFI partition. + 3. If the installer used by your distro is `ubiquity` (which is the one used in Ubuntu, Linux Mint, etc.), then you can leave EFI Boot alone. If you are using a [separate EFI partition](https://wiki.t2linux.org/guides/windows/#using-separate-efi-partitions), then you will have to separate it out after installation by following [this guide](https://wiki.t2linux.org/guides/windows/#separate-the-efi-partition-after-linux-is-installed). + + For other installers, you need to mount `nvme0n1p1`, or your [separate EFI partition](https://wiki.t2linux.org/guides/windows/#using-separate-efi-partitions) (whatever case applies to you) at `/boot/efi`. If the installer supports the "boot" flag, set it as well for your EFI partition. 5. Continue the rest of the setup. 6. Once it's finished, you can reboot without your installation media. Hold down Option (⌥) while booting, then select EFI Boot and press enter. @@ -71,4 +71,4 @@ After installation, we need to install a kernel having patches to support the T2 # Basic set up -After installing the new kernel, follow the [Basic setup](https://wiki.t2linux.org/guides/postinstall/) guide. You shall mainly have to follow the [Add necessary kernel parameters](https://wiki.t2linux.org/guides/postinstall/#add-necessary-kernel-paramaters) and [Make modules load on boot](https://wiki.t2linux.org/guides/postinstall/#make-modules-load-on-boot) sections. If using disk encryption (LUKS), then follow the [Make modules load on early boot](https://wiki.t2linux.org/guides/postinstall/#make-modules-load-on-early-boot) section as well. Rest have been set up automatically by the kernel upgrade script. +After installing the new kernel, follow the [Basic setup](https://wiki.t2linux.org/guides/postinstall/) guide. You will mainly have to follow the [Add necessary kernel parameters](https://wiki.t2linux.org/guides/postinstall/#add-necessary-kernel-parameters) and [Make modules load on boot](https://wiki.t2linux.org/guides/postinstall/#make-modules-load-on-boot) sections. If using disk encryption (LUKS), then follow the [Make modules load on early boot](https://wiki.t2linux.org/guides/postinstall/#make-modules-load-on-early-boot) section as well. Rest have been set up automatically by the kernel upgrade script. diff --git a/docs/distributions/endeavouros/installation.md b/docs/distributions/endeavouros/installation.md index cbfadd71f..e37c7e2ae 100644 --- a/docs/distributions/endeavouros/installation.md +++ b/docs/distributions/endeavouros/installation.md @@ -3,13 +3,13 @@ You will need: - USB drive with at least 4GB -- A way to plug it into your Mac (USB-C isn't USB-A) -- A wired internet connection (i.e. USB-C to Enternet dongle) or Wi-Fi. +- A way to plug it into your Mac (USB-C and USB-A are different) +- A wired internet connection (i.e. USB-C to Ethernet dongle) or Wi-Fi. --- !!! Warning "Users in NA/EU" - If you're experiencing slow download speed or failure to install, please edit your `/etc/pacman.conf` file and replace old mirror.funami.tech link with `https://github.com/NoaHimesaka1873/arch-mact2-mirror/releases/download/release` instead. + If you're experiencing slow download speeds or installation failures, please edit your `/etc/pacman.conf` file and replace the old mirror.funami.tech link with `https://github.com/NoaHimesaka1873/arch-mact2-mirror/releases/download/release` instead. 1. Follow the [Pre-installation](https://wiki.t2linux.org/guides/preinstall) steps to prepare your Mac for the installation. @@ -26,7 +26,7 @@ You will need: 3. Follow the installer until Partitions. 1. Select "Manual partitioning." - 2. Select "/dev/nvme0n1p1" partition, make sure the "boot" flag is set, and set it to mount under "/efi". If you want to use separate EFI partition, check out [this guide](https://wiki.t2linux.org/guides/windows/#using-seperate-efi-partitions). + 2. Select "/dev/nvme0n1p1" partition, make sure the "boot" flag is set, and set it to mount under "/efi". If you want to use separate EFI partition, check out [this guide](https://wiki.t2linux.org/guides/windows/#using-separate-efi-partitions). 3. Use remaining partition space to your convenience. 4. Follow the rest of the installer and reboot. diff --git a/docs/distributions/fedora/faq.md b/docs/distributions/fedora/faq.md index 6003c2dc2..9a421a1cd 100644 --- a/docs/distributions/fedora/faq.md +++ b/docs/distributions/fedora/faq.md @@ -6,7 +6,7 @@ If you already have Bootcamp installed, you might notice that the boot option fo This may be due to differences between USB-C to USB-A adapters. Try a different one if it is not working. -# My touchbar is blank +# My Touch Bar is blank Follow the instructions in the [post-install guide](https://wiki.t2linux.org/guides/postinstall/#setting-up-the-touch-bar). If it still is not working, try updating your macOS installation. diff --git a/docs/distributions/fedora/home.md b/docs/distributions/fedora/home.md index bb05a73ca..92e7072f2 100644 --- a/docs/distributions/fedora/home.md +++ b/docs/distributions/fedora/home.md @@ -1,3 +1,3 @@ Welcome to the T2 Fedora wiki! -Follow [the installation guide](https://wiki.t2linux.org/distributions/fedora/installation/) to get started. If you need help, join the t2linux discord [server](https://discord.com/invite/68MRhQu) server and ask in `#fedora` over there. Alternately, you can open an issue in the github [issue tracker](https://github.com/t2linux/wiki/issues). You can also refer to the [FAQ](https://wiki.t2linux.org/distributions/fedora/faq/) to fix common problems. +Follow [the installation guide](https://wiki.t2linux.org/distributions/fedora/installation/) to get started. If you need help, join the t2linux Discord [server](https://discord.com/invite/68MRhQu) and ask in `#fedora`. Alternatively, you can open an issue in the GitHub [issue tracker](https://github.com/t2linux/wiki/issues). You can also refer to the [FAQ](https://wiki.t2linux.org/distributions/fedora/faq/) to fix common problems. diff --git a/docs/distributions/fedora/installation.md b/docs/distributions/fedora/installation.md index 7d5f3be1d..3c37f62f9 100644 --- a/docs/distributions/fedora/installation.md +++ b/docs/distributions/fedora/installation.md @@ -1,6 +1,6 @@ # Download the latest safe release -Many thanks to [Mike](https://github.com/mikeeq/) for building. You can download a live iso from [here](https://github.com/t2linux/fedora-iso/releases). +Many thanks to [Mike](https://github.com/mikeeq/) for building. You can download a live ISO from [here](https://github.com/t2linux/fedora-iso/releases). # Hardware Requirements @@ -14,7 +14,7 @@ Many thanks to [Mike](https://github.com/mikeeq/) for building. You can download 4. Continue with the rest of the installation. 5. Once it's finished, you can reboot without your installation media. Hold down Option (⌥) while booting, then select EFI Boot and press enter. 6. Welcome to Fedora! :) -7. Wi-Fi should work on first boot, but if it is not you should follow the [Wi-Fi guide](https://wiki.t2linux.org/guides/wifi-bluetooth/). +7. Wi-Fi should work on first boot, but if it does not, you should follow the [Wi-Fi guide](https://wiki.t2linux.org/guides/wifi-bluetooth/). ## Installing unsupported spins diff --git a/docs/distributions/gentoo/installation.md b/docs/distributions/gentoo/installation.md index b292df906..61e9d5105 100644 --- a/docs/distributions/gentoo/installation.md +++ b/docs/distributions/gentoo/installation.md @@ -3,12 +3,12 @@ ## Install Procedure 1. Follow the [Pre-installation](https://wiki.t2linux.org/guides/preinstall) steps. - 1. Since there is not yet a T2 Gentoo Installation ISO, you will need to use a different ISO. We recommend the [T2-Ubuntu](https://github.com/t2linux/T2-Ubuntu/releases/latest) ISO if you want a graphical environment, or the [T2-Archiso](https://github.com/t2linux/archiso-t2/releases/latest) if you don't want to have to copy Wi-Fi firmware to the livecd. + 1. Since there is not yet a T2 Gentoo installation ISO, you will need to use a different ISO. We recommend the [T2-Ubuntu](https://github.com/t2linux/T2-Ubuntu/releases/latest) ISO if you want a graphical environment, or the [T2-Archiso](https://github.com/t2linux/archiso-t2/releases/latest) if you don't want to have to copy Wi-Fi firmware to the livecd. 2. If you chose the Ubuntu ISO, follow the [Wi-Fi Guide](https://wiki.t2linux.org/guides/wifi-bluetooth/) once booted. 2. Connect to the internet using NetworkManager in the Ubuntu ISO, or using `iwctl` in the Arch ISO. -3. You will need to reformat your partitions, except for the EFI partition. The other partitions will need to reformatted as described in the [Gentoo Handbook](https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Disks). For the EFI system partition there will be one at `/dev/nvme0n1p1` and you can use this if you don't intend to install Windows or already have it installed. If you do intend to triple boot, refer to [this guide](https://wiki.t2linux.org/guides/windows/). +3. You will need to reformat your partitions, except for the EFI partition. The other partitions will need to be reformatted as described in the [Gentoo Handbook](https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Disks). For the EFI system partition there will be one at `/dev/nvme0n1p1` and you can use this if you don't intend to install Windows or already have it installed. If you do intend to triple boot, refer to [this guide](https://wiki.t2linux.org/guides/windows/). 4. Follow the Gentoo Handbook from [Installing stage3](https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Stage) until [Kernel Configuration and Compilation](https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Kernel#Kernel_configuration_and_compilation). @@ -27,7 +27,7 @@ 1. The T2 overlay provides a [Distribution Kernel](https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Kernel#Distribution_kernels) for T2 Macs. To install it, run `emerge -av sys-kernel/t2gentoo-kernel`. - 2. Alternatively, you can use the kernel sources and manually compile. With this method, the update process is not automated, and manual configuration is necessary. However, `sys-kernel/t2gentoo-sources` tends to get new kernel versions faster then `sys-kernel/t2gentoo-kernel`. To install it, run: `emerge -av sys-kernel/t2gentoo-sources`. After installing the kernel sources, run `eselect kernel set 1` to point `/usr/src/linux` to the correct path, then follow the directions in the [Manual Configuration](https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Kernel#Alternative:_Manual_configuration) section of the handbook. If you decide to manually configure your kernel, make sure the following options are set: + 2. Alternatively, you can use the kernel sources and manually compile. With this method, the update process is not automated, and manual configuration is necessary. However, `sys-kernel/t2gentoo-sources` tends to get new kernel versions faster than `sys-kernel/t2gentoo-kernel`. To install it, run: `emerge -av sys-kernel/t2gentoo-sources`. After installing the kernel sources, run `eselect kernel set 1` to point `/usr/src/linux` to the correct path, then follow the directions in the [Manual Configuration](https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Kernel#Alternative:_Manual_configuration) section of the handbook. If you decide to manually configure your kernel, make sure the following options are set: ```bash CONFIG_APPLE_BCE=m diff --git a/docs/distributions/manjaro/deprecation.md b/docs/distributions/manjaro/deprecation.md index 62c61e24b..003631897 100644 --- a/docs/distributions/manjaro/deprecation.md +++ b/docs/distributions/manjaro/deprecation.md @@ -1,14 +1,8 @@ # Why is Manjaro T2 deprecated? Due to [concerns](https://github.com/arindas/manjarno), Manjaro T2 is deprecated. -If you want to maintain it yourself, come to our Discord and we will help. +If you want to maintain it yourself, come to our Discord and we will help you. # What distro should I use instead? We recommend [EndeavourOS.](https://wiki.t2linux.org/distributions/endeavouros/installation/) - -# What do I do after Manjaro is deprecated? - -No support for installation will be provided starting from 2023. If you want to install Manjaro on your Mac after 2023, you're on your own. - -For kernel for existing installation, until the end of 2023. LTS will be supported longer for those who can't switch for whatever reason. diff --git a/docs/distributions/manjaro/faq.md b/docs/distributions/manjaro/faq.md index 8903c6bf6..4bd9dea02 100644 --- a/docs/distributions/manjaro/faq.md +++ b/docs/distributions/manjaro/faq.md @@ -19,9 +19,9 @@ After running this, remove old repository and reboot. # Upgrading to newer kernel (recommended) -Users using older kernel are advised to migrate to newest kernel since newer kernel has more support. +Users using older kernels are advised to migrate to the newest kernel since the newer kernel has more support. -Join our Discord or enable notifications for [this repository](https://github.com/NoaHimesaka1873/manjaro-kernel-t2) to get pings for new kernel. +Join our Discord or enable notifications for [this repository](https://github.com/NoaHimesaka1873/manjaro-kernel-t2) to get pings for new kernels. # Installing alongside Windows diff --git a/docs/distributions/manjaro/installation.md b/docs/distributions/manjaro/installation.md index 8786644ff..6ab84159c 100644 --- a/docs/distributions/manjaro/installation.md +++ b/docs/distributions/manjaro/installation.md @@ -2,14 +2,14 @@ Manjaro T2 support is deprecated. See [Deprecation Plan](https://wiki.t2linux.org/distributions/manjaro/deprecation) for more information. -# Download a latest release +# Download the latest release [See releases](https://github.com/NoaHimesaka1873/manjaroiso-t2/releases) # Hardware Requirements * USB-C to Ethernet cable adapter. - * While you can install Manjaro over WiFi, it would be a lot easier to use an Adapter during the installation process. + * While you can install Manjaro over WiFi, it would be a lot easier to use an adapter during the installation process. * USB-C to USB Adapter * USB drive diff --git a/docs/distributions/nixos/faq.md b/docs/distributions/nixos/faq.md index 9fa42eff8..61ff8dbc3 100644 --- a/docs/distributions/nixos/faq.md +++ b/docs/distributions/nixos/faq.md @@ -5,7 +5,7 @@ ## The LiveCD does not boot/only shows a blank screen -This situation occurred due to regressions in the bootloader, which the wider NixOS community was also affected. +This situation occurred due to regressions in the bootloader, which also affected the wider NixOS community. The bug has been fixed. Make sure you are using ISOs tagged at or newer than `6.4.9-2`. Nevertheless, usage of [the latest ISO](https://github.com/t2linux/nixos-t2-iso/releases/latest) is recommended. ## In the Live environment, building the kernel/configuration runs out of disk space diff --git a/docs/distributions/nixos/home.md b/docs/distributions/nixos/home.md index 41f635b60..5f910bf4c 100644 --- a/docs/distributions/nixos/home.md +++ b/docs/distributions/nixos/home.md @@ -6,7 +6,7 @@ If you have any questions, consult the [FAQ](./faq.md) to see if anything there ## New to NixOS? -NixOS is not exactly an easy Linux distribution to use. If you are entirely new to Linux or had no prior experience with Nix, we strongly recommend you choose another distro like [Fedora](../fedora/home.md) first. Should you decide to proceed further, the [Nixpkgs manual](https://nixos.org/manual/nixpkgs/unstable), [Zero-to-Nix](https://zero-to-nix.com/), [NixOS Options Search](https://search.nixos.org/options) and [the official Nix wiki](https://nix.dev) could come in handy. +NixOS is not exactly an easy Linux distribution to use. If you are entirely new to Linux or have no prior experience with Nix, we strongly recommend you choose another distro like [Fedora](../fedora/home.md) first. Should you decide to proceed further, the [Nixpkgs manual](https://nixos.org/manual/nixpkgs/unstable), [Zero-to-Nix](https://zero-to-nix.com/), [NixOS Options Search](https://search.nixos.org/options) and [the official Nix wiki](https://nix.dev) could come in handy. Note that since T2 devices require kernel patches, you will need to build the Linux kernel quite often. This can be circumvented by [using a substituter.](faq.md#substituter-setup) diff --git a/docs/distributions/nixos/installation.md b/docs/distributions/nixos/installation.md index 2585b090e..903970d60 100644 --- a/docs/distributions/nixos/installation.md +++ b/docs/distributions/nixos/installation.md @@ -96,15 +96,15 @@ You might want to also configure a display manager and a desktop environment. Ch ```shell # 0. If you haven't run nixos-generate-config, do it now. See above for steps. - # 1. Change directory to /mnt/etc/nixos. + # 1. Change directory to /mnt/etc/nixos. # This will be where you store your flake, but you can move it later. cd /mnt/etc/nixos - # 2. Initialize the flake directory with the template. + # 2. Initialize the flake directory with the template. # Accept *both* settings if you would like to use the substituter. nix flake init -t github:soopyc/nixos-t2-flake - # 3. Edit flake.nix, delete the section as specified. + # 3. Edit flake.nix, delete the section as specified. # Also, rename yourHostname to something else. $EDITOR flake.nix diff --git a/docs/distributions/ubuntu/faq.md b/docs/distributions/ubuntu/faq.md index c6c294d11..19f08acb0 100644 --- a/docs/distributions/ubuntu/faq.md +++ b/docs/distributions/ubuntu/faq.md @@ -1,12 +1,12 @@ # Why does my MacBook turn off in the middle of the Ubuntu installation? -This seems to happen with certain MacBooks because the GRUB bootloader installer tries accessing the efivars/nvram, which Apple doesn't allow and the installer doesn't know what to do. +This seems to happen with certain MacBooks because the GRUB bootloader installer tries to access the efivars/nvram, which Apple doesn't allow and the installer doesn't know what to do. There is a way to stop this. Boot into the installation media with an External USB Keyboard plugged in. Press e when you selected the "Try Ubuntu without installing" option. -Scroll to the bottom with the arrow keys, and type in ``efi=noruntime``. With the External keyboard, then press CTRL+X or F10 to boot into the Live Media. The installation should work fine now. +Scroll to the bottom with the arrow keys, and type in ``efi=noruntime``. With the external keyboard, then press CTRL+X or F10 to boot into the Live Media. The installation should work fine now. -This issue has occurred for anyone on the 16,1 and maybe the 16,4. +This issue has occurred for anyone on the 16,1 and possibly the 16,4. # Making the GRUB Menu appear @@ -22,9 +22,9 @@ If you already have Bootcamp installed, you might notice that the boot option fo # Why isn't sound working? -On **Ubuntu 22.04 or earlier**, PulseAudio is installed by default, which performs really bad with T2 audio configuration files. It is suggested to [switch to PipeWire](https://linuxconfig.org/how-to-install-pipewire-on-ubuntu-linux) for better performance, although its still bad as compared to Ubuntu 22.10, which has native support for PipeWire. +On **Ubuntu 22.04 or earlier**, PulseAudio is installed by default, which performs really badly with T2 audio configuration files. It is suggested to [switch to PipeWire](https://linuxconfig.org/how-to-install-pipewire-on-ubuntu-linux) for better performance, although its still bad as compared to Ubuntu 22.10, which has native support for PipeWire. -On **Ubuntu 22.10 or later**, PipeWire is support natively and works just fine with audio configuration files. Still, it's recommended to use the upstream version of PipeWire since it is found to perform better and has more features than the native one. You can run the following commands to use the upstream version: +On **Ubuntu 22.10 or later**, PipeWire is supported natively and works just fine with audio configuration files. Still, it's recommended to use the upstream version of PipeWire since it is found to perform better and has more features than the native one. You can run the following commands to use the upstream version: ```bash sudo add-apt-repository ppa:pipewire-debian/pipewire-upstream diff --git a/docs/distributions/ubuntu/home.md b/docs/distributions/ubuntu/home.md index 6046ca86c..cfa491488 100644 --- a/docs/distributions/ubuntu/home.md +++ b/docs/distributions/ubuntu/home.md @@ -1,3 +1,3 @@ Welcome to the T2 Ubuntu wiki! -Follow [the installation guide](https://wiki.t2linux.org/distributions/ubuntu/installation/) to get started. If you need help, join the t2linux discord [server](https://discord.com/invite/68MRhQu) server and ask in `#ubuntu` over there. Alternately, you can open an issue in the GitHub [issue tracker](https://github.com/t2linux/T2-Ubuntu/issues). You can also refer to the [FAQ](https://wiki.t2linux.org/distributions/ubuntu/faq/) to fix common problems. +Follow [the installation guide](https://wiki.t2linux.org/distributions/ubuntu/installation/) to get started. If you need help, join the t2linux Discord [server](https://discord.com/invite/68MRhQu) and ask in `#ubuntu` over there. Alternately, you can open an issue in the GitHub [issue tracker](https://github.com/t2linux/T2-Ubuntu/issues). You can also refer to the [FAQ](https://wiki.t2linux.org/distributions/ubuntu/faq/) to fix common problems. diff --git a/docs/distributions/ubuntu/installation.md b/docs/distributions/ubuntu/installation.md index 5f99100bc..79c8c0e55 100644 --- a/docs/distributions/ubuntu/installation.md +++ b/docs/distributions/ubuntu/installation.md @@ -7,11 +7,11 @@ Download Links: -[Ubuntu and its supported flavours](https://github.com/t2linux/T2-Ubuntu/releases/latest) +[Ubuntu and its supported flavors](https://github.com/t2linux/T2-Ubuntu/releases/latest) [Linux Mint](https://github.com/t2linux/T2-Mint/releases/latest) -We currently support the following flavours of Ubuntu: +We currently support the following flavors of Ubuntu: - Ubuntu - Kubuntu @@ -30,9 +30,9 @@ We currently support the following flavours of Ubuntu: 1. If you want, you can make separate partitions for **swap**, `/home`, `/boot` etc as you do in a normal PC. - 2. The only partition to be made compulsorily is the one mounted at `/` and formatted to **ext4** or **btrfs**. + 2. The only partition that must be made is the one mounted at `/` and formatted to **ext4** or **btrfs**. - 3. Leave EFI boot alone. If you want to use a [separate EFI partition](https://wiki.t2linux.org/guides/windows/#using-seperate-efi-partitions), you can separate it out later after installation as instructed [here](https://wiki.t2linux.org/guides/windows/#seperate-the-efi-partition-after-linux-is-installed). + 3. Leave EFI Boot alone. If you want to use a [separate EFI partition](https://wiki.t2linux.org/guides/windows/#using-separate-efi-partitions), you can separate it out later after installation as instructed [here](https://wiki.t2linux.org/guides/windows/#separate-the-efi-partition-after-linux-is-installed). 5. Continue the rest of the setup. 6. Once it's finished, you can reboot without your installation media. Hold down Option (⌥) while booting, then select EFI Boot and press enter. @@ -43,7 +43,7 @@ We currently support the following flavours of Ubuntu: Once you're booted and in your desktop: - Run `get-apple-firmware get_from_macos` **if you have macOS installed as well**. -- Run `get-apple-firmware get_from_online` **if you have removed macOS or above method does not work** (Note: This method needs wired internet to work). +- Run `get-apple-firmware get_from_online` **if you have removed macOS or the above method does not work** (Note: This method needs wired internet to work). If these methods do not work, follow [this guide](https://wiki.t2linux.org/guides/wifi-bluetooth/) to get firmware for Wi-Fi and Bluetooth. diff --git a/docs/guides/audio-config.md b/docs/guides/audio-config.md index ded3e5f38..7c38785c4 100644 --- a/docs/guides/audio-config.md +++ b/docs/guides/audio-config.md @@ -8,13 +8,13 @@ If there is no output at all you probably do not have T2 Mac support. Follow the # Enable Pass-Through Kernel Parameters -Cat `cat /proc/cmdline` and ensure that your kernel parameters contain `intel_iommu=on iommu=pt pcie_ports=compat`. +Run `cat /proc/cmdline` and ensure that your kernel parameters contain `intel_iommu=on iommu=pt pcie_ports=compat`. -If not present, you'll have to update your bootup kernel params: +If not present, you'll have to update your bootup kernel parameters: - edit `/etc/default/grub` and update `GRUB_CMDLINE_LINUX` to include `intel_iommu=on iommu=pt pcie_ports=compat` - Apply your edits by running `sudo update-grub` on ubuntu or `sudo grub-mkconfig -o /boot/grub/grub.cfg` for other distros - - Note that, `grub`'s command line interface names might differ on different distros, if the commands like `grub-xxx` are not found, try `grub2-xxx` alternatives instead. For example, it should be `sudo grub2-mkconfig ...` instead of `sudo grub-mkconfig ...` on Fedora 36. + - `grub`'s command line interface names might differ on different distros, if the commands like `grub-xxx` are not found, try `grub2-xxx` alternatives instead. For example, it should be `sudo grub2-mkconfig ...` instead of `sudo grub-mkconfig ...` on Fedora 36. - Reboot and ensure `cat /proc/cmdline` contains those params !!!note "systemd-boot" diff --git a/docs/guides/fan.md b/docs/guides/fan.md index 080da00d4..c6e77079f 100644 --- a/docs/guides/fan.md +++ b/docs/guides/fan.md @@ -2,7 +2,7 @@ This page is a step by step guide to get fan control working on T2 Macs. -In some Macs, the fan has been found to work out of the box. In such a case the driver is not required until you want to force a certain speed or do some other configuration which can be done by the help of this driver. +In some Macs, the fan has been found to work out of the box. In such cases, the driver is not required unless you want to force a certain speed or do some other configuration which can be done by the help of this driver. ## Steps @@ -12,7 +12,7 @@ In some Macs, the fan has been found to work out of the box. In such a case the 1. Check if you installed Arch using our guide or added our repositories. If you haven't done that, follow [this guide](https://wiki.t2linux.org/distributions/arch/faq/#updating-kernel) first. - 2. Install the package by running `sudo pacman -S t2fanrd`. (Do note that EndeavourOS Cassini Nova R1 already includes t2fand.) + 2. Install the package by running `sudo pacman -S t2fanrd`. (Note that EndeavourOS Cassini Nova R1 already includes t2fand.) - If you're using Debian or Ubuntu based distros: @@ -26,7 +26,7 @@ In some Macs, the fan has been found to work out of the box. In such a case the 2. Install the package by running `sudo dnf install t2fanrd` - - If you’re using Nixos with Flakes; + - If you're using NixOS with Flakes, 1. Add to your flakes inputs. diff --git a/docs/guides/hybrid-graphics.md b/docs/guides/hybrid-graphics.md index 25eeb17e3..70b2aac40 100644 --- a/docs/guides/hybrid-graphics.md +++ b/docs/guides/hybrid-graphics.md @@ -1,18 +1,18 @@ # Introduction -This page describes how to use the iGPU on MacBookPro's with Hybrid Graphics (2 GPUs). 13 inch MacBooks only have an iGPU, and do not need this. Using the iGPU means you can save power by putting the more powerful AMD dGPU in a low power state when you don't need it. +This page describes how to use the iGPU on MacBook Pros with Hybrid Graphics (2 GPUs). 13-inch MacBooks only have an iGPU and do not need this. Using the iGPU means you can save power by putting the more powerful AMD dGPU in a low power state when you don't need it. This has been tested on the MacBookPro16,1 and the MacBookPro15,1. The 15,3 and 16,4 models are very similar and should work too. -Make sure you have a t2 kernel of version greater than 6.9.8-1 (you can check this with `uname -r`). +Make sure you have a T2 kernel of version greater than 6.9.8-1 (you can check this with `uname -r`). ## Issues -If you experience system freezes, then the laptop's fans becoming loud, before the whole computer shuts off (CPU CATERR), or if the amdgpu is making the computer too hot, consider trying: +If you experience system freezes followed by high fan speeds and sudden shutdowns (CPU CATERR), or if the AMD GPU is causing excessive heat, try the following solutions: -1. Set iGPU as main gpu (instructions below) +1. Set the iGPU as the main GPU (instructions below) -2. Set AMD GPU Dynamic Power Management from auto to low or high. Low can be safer option to avoid thermal issues or save battery. +2. Set the AMD GPU Dynamic Power Management level from auto to low or high. Low can be safer option to avoid thermal issues or save battery. You can test it quickly with: `echo low | sudo tee /sys/bus/pci/drivers/amdgpu/0000:0?:00.0/power_dpm_force_performance_level` @@ -41,7 +41,7 @@ If you experience system freezes, then the laptop's fans becoming loud, before t If using the iGPU causes the screen to be black after waking up from suspend, then try one of these workarounds: -- Add `i915.enable_guc=3` to [your kernel parameters](https://wiki.t2linux.org/guides/postinstall/#add-necessary-kernel-paramaters). If that has a problem, try setting the value to 2 instead of 3. +- Add `i915.enable_guc=3` to [your kernel parameters](https://wiki.t2linux.org/guides/postinstall/#add-necessary-kernel-parameters). If that has a problem, try setting the value to 2 instead of 3. - Turn the screen off and on after the backlight turns on. For GNOME: type your password then press enter, press Command + L to lock (this should turn off the backlight), then press any key. ## Use on Windows diff --git a/docs/guides/kernel.md b/docs/guides/kernel.md index 52f03f459..36d966c4a 100644 --- a/docs/guides/kernel.md +++ b/docs/guides/kernel.md @@ -12,7 +12,7 @@ If your distro is not one of the distros with documentation on this Wiki, you ma - Debian based systems: `sudo apt install autoconf bc bison build-essential cpio curl debhelper dkms dwarves fakeroot flex gawk git kernel-wedge libcap-dev libelf-dev libiberty-dev libncurses-dev libpci-dev libssl-dev libudev-dev openssl python3 rsync wget xz-utils zstd` - For other distros you will need the equivalent of these, but if you miss something you'll most likely get an error saying what's missing, and you can then install it and re-run `make` to continue where you left off. -- You will need about 20GB of disk space to compile the kernel. If you have a large amount of ram, you could use tmpfs to store build files in ram. +- You will need about 20GB of disk space to compile the kernel. If you have a large amount of RAM, you could use tmpfs to store build files in RAM. ## Building kernel @@ -69,10 +69,10 @@ scripts/config --module CONFIG_APFS_FS ### Building -This may take 2-3 hours to build depending on your CPU and the kernel config. +This may take 2-3 hours to build, depending on your CPU and the kernel config. !!! Info "Incremental builds" - If you `control-c` to stop the build process, you may continue where you left off by running `make` again. If you build the kernel, and realise you want to make more changes to the code or config, re-running `make` will only rebuild bits that you changed. + If you `control-c` to stop the build process, you may continue where you left off by running `make` again. If you build the kernel, and realize you want to make more changes to the code or config, re-running `make` will only rebuild bits that you changed. ```bash make -j$(nproc) diff --git a/docs/guides/postinstall.md b/docs/guides/postinstall.md index 1e2912901..335a384ab 100644 --- a/docs/guides/postinstall.md +++ b/docs/guides/postinstall.md @@ -1,22 +1,22 @@ # Introduction -This page explains how to perform a basic set up after installing Linux on a T2 Mac. +This page explains how to perform a basic setup after installing Linux on a T2 Mac. ## Do you need to do this? -This guide is mainly relevant in the following cases : +This guide is mainly relevant in the following cases: 1. If you have installed Linux using an official ISO, instead of a T2 ISO. 2. The [Make modules load on early boot](#make-modules-load-on-early-boot) section is relevant for those who wish to encrypt their disk drives using LUKS or some other similar software. 3. If some functionality related to T2 Macs is broken, then you can consider following this guide. -In rest cases, you probably won't need to follow this guide. +In other cases, you probably won't need to follow this guide. -If you have used a T2 ISO, **make sure you have followed the [distro specific guide](https://wiki.t2linux.org/distributions/overview/) for your distro before continuing further.** +If you have used a T2 ISO, **make sure you have followed the [distro specific guide](https://wiki.t2linux.org/distributions/overview/) for your distro before continuing**. ## Installing a kernel for T2 support -Installing a kernel with support for T2 Macs is required in order to get the Keyboard, Trackpad, Touch Bar, Audio, Fan and Wi-Fi working. +Installing a kernel with support for T2 Macs is required to get the **keyboard**, **trackpad**, **touch bar**, **audio**, **fan**, and **Wi-Fi** working. Many distro maintainers provide compiled kernels which can be installed on your Linux installation. Following are the links to the repos providing such kernels: @@ -31,7 +31,7 @@ Many distro maintainers provide compiled kernels which can be installed on your | Debian based distros | | | Debian based distros | | -If compiled kernels for your distro are not available, then you shall have to compile a kernel on your own. You can follow the [Kernel](https://wiki.t2linux.org/guides/kernel/) guide for help. +If compiled kernels for your distro are not available, then you will have to compile a kernel yourself. You can follow the [Kernel](https://wiki.t2linux.org/guides/kernel/) guide for help. ## Add necessary kernel parameters @@ -39,7 +39,7 @@ Using your bootloader, add the `intel_iommu=on iommu=pt pcie_ports=compat` kerne 1. Edit `/etc/default/grub`. 2. On the line with `GRUB_CMDLINE_LINUX="quiet splash"`, add the following kernel parameters: `intel_iommu=on iommu=pt pcie_ports=compat`. - 3. Run `sudo grub-mkconfig -o /boot/grub/grub.cfg` if you are on a non-debian based distro. If using Debian or Ubuntu based distro, run `sudo update-grub`. + 3. Run `sudo grub-mkconfig -o /boot/grub/grub.cfg` if you are on a non-Debian based distro. If using Debian or Ubuntu based distro, run `sudo update-grub`. ## Make modules load on boot @@ -52,12 +52,12 @@ echo apple-bce | sudo tee /etc/modules-load.d/t2.conf ## Make modules load on early boot Having the `apple-bce` module loaded early allows the use of the keyboard for decrypting encrypted volumes (LUKS). -It also is useful when boot doesn't work, and the keyboard is required for debugging. -To do this, one must ensure the `apple-bce` module *as well as its dependent modules* are included in the initial ram disk. +It is also useful when boot doesn't work and the keyboard is required for debugging. +To do this, you must ensure the `apple-bce` module *as well as its dependent modules* are included in the initial RAM disk. You can get the list of dependent modules by running `modinfo -F depends apple-bce` The steps to be followed vary depending upon the initramfs module loading mechanism used by your distro. Some examples are given as follows: -- On systems with `initramfs-tools` (all debian-based distros): +- On systems with `initramfs-tools` (all Debian-based distros): 1. Run `sudo su` to open a shell as root. @@ -101,7 +101,7 @@ The steps to be followed vary depending upon the initramfs module loading mechan ## Adding support for customisable Touch Bar -By default the Touch Bar works in the same mode which Windows Bootcamp uses on Linux. If you want to customise it, you can install `tiny-dfr` on your distro. +By default the Touch Bar works in the same mode which Windows Bootcamp uses on Linux. If you want to customize it, you can install `tiny-dfr` on your distro. If you are using an Ubuntu or Debian based distro: @@ -117,11 +117,11 @@ If you are using Arch Linux or EndeavourOS: If you are using Fedora: 1. Install tiny-dfr with `sudo dnf install rust-tiny-dfr`. - 2. Restart your mac + 2. Restart your Mac For other distros: -- Compile [`tiny-dfr`](https://github.com/AsahiLinux/tiny-dfr) yourself if your distro don't have that packaged yet. +- Compile [`tiny-dfr`](https://github.com/AsahiLinux/tiny-dfr) yourself if your distro doesn't have that packaged yet. In order to make changes to the config for `tiny-dfr`, copy `/usr/share/tiny-dfr/config.toml` to `/etc/tiny-dfr/config.toml` and edit `/etc/tiny-dfr/config.toml` by following the instructions given in that file. @@ -166,7 +166,7 @@ Instructions for the same are given in the [Wi-Fi and Bluetooth](https://wiki.t2 # Network Manager recurrent notifications -Some users have experienced recurrent notifications due the internal usb ethernet interface connected to the T2 chip. To avoid those notifications we can disable the interface with the following command: +Some users have experienced recurrent notifications due to the internal USB ethernet interface connected to the T2 chip. To avoid those notifications we can disable the interface with the following command: ```sh cat < | | Gentoo | Please refer to this [page](https://wiki.t2linux.org/distributions/gentoo/installation/) | | NixOS | | -| Ubuntu & its flavours | | +| Ubuntu & its flavors | | | Linux Mint | | #### Other distributions -If you are a beginner we **highly recommend** to choose one of the distros above. +If you are a beginner, we **highly recommend** choosing one of the distributions above. -In case you wish to proceed manually, you can download the official ISO from the distro website, but you will have to use an external USB keyboard and mouse for the install process. Additionally, you may require a wired internet connection with a USB adapter. Note that if you later have issues with installing the bootloader (e.g.: GRUB), try booting the ISO with the `efi=noruntime` kernel parameter. +In case you wish to proceed manually, you can download the official ISO from the distro website, but you will have to use an external USB keyboard and mouse for the install process. Additionally, you may require a wired internet connection with a USB adapter. Note that if you later have issues installing the bootloader (e.g., GRUB), try booting the ISO with the `efi=noruntime` kernel parameter. -Please, refer to this guide: [Basic setup](https://wiki.t2linux.org/guides/postinstall/). +Please refer to this guide: [Basic setup](https://wiki.t2linux.org/guides/postinstall/). You can also find detailed info for unsupported debian-based distros [here](https://wiki.t2linux.org/distributions/debian/installation/). @@ -58,14 +58,14 @@ Or you can use `dd` in macOS Terminal: 1. Insert your USB drive. 2. Open macOS Terminal. 3. Run `diskutil list` to list all the drives. -4. Look up for your USB thumb which appears as an **external, physical** drive labelled `/dev/diskX` where `X` is a single number (e.g. /dev/disk**2**). +4. Look up for your USB thumb which appears as an **external, physical** drive labeled `/dev/diskX` where `X` is a single number (e.g. /dev/disk**2**). 5. Run `sudo diskutil unmountDisk /dev/diskX` to unmount the disk. -6. Run `sudo dd if=path/to/linux.iso of=/dev/rdiskX bs=1m` to start writing. To fetch the iso path easily you can just drag and drop the .iso into the Terminal. +6. Run `sudo dd if=path/to/linux.iso of=/dev/rdiskX bs=1m` to start writing. To fetch the ISO path easily you can just drag and drop the .iso into the Terminal. 7. Now you may press `control-T` to make it show how many KBs it has written so far. ## Disable Secure Boot -Apple's Secure Boot implementation does not allow booting anything other than macOS or Windows when it is enabled (not even shim signed GRUB). +Apple's Secure Boot implementation does not allow booting anything other than macOS or Windows when enabled (not even shim-signed GRUB). We need to disable it: 1. Turn off your Mac @@ -73,16 +73,16 @@ We need to disable it: 3. Your Mac will boot in the macOS Recovery 4. Select your user and enter your password 5. Now, from the menu bar choose Utilities > Startup Security Utility -6. Enter again the password +6. Enter your password again 7. Once in Startup Security Utility: - - set Secure Boot to **No Security** - - set Allow Boot Media to **Allow booting from external or removable media** + - Set **Secure Boot** to **No Security** + - Set **Allow Boot Media** to **Allow booting from external or removable media** Now you are able to boot from a Linux install ISO. !!! Note "Keeping your Mac secure while Secure Boot is off" - If you are worried about the reduced security, in Startup Security Utility you can select "Turn On Firmware Password" to require entering a password to boot anything other than the default OS. Additionally, after installing Linux on the internal SSD, you will have the option to reselect "Disallow booting from external or removable media" in the Startup Security Utility. + If you are worried about the reduced security, in Startup Security Utility you can select "Turn On Firmware Password" to require a password for booting anything other than the default OS. Additionally, after installing Linux on the internal SSD, you will have the option to reselect "Disallow booting from external or removable media" in Startup Security Utility. ## Booting your Linux install USB @@ -97,6 +97,6 @@ Now you are able to boot from a Linux install ISO. ## Follow distro specific steps !!! Warning "Automatic Partitioning" - The installers of many distros provide options like "Automatic Partitioning" when installing Linux. You always have to select the option that allows "Manual Partitioning". **Do not** select "Automatic Partitioning" as it shall remove macOS as well. During manual partitioning make sure that you mount `/dev/nvme0n1p1` or your [separate EFI partition](https://wiki.t2linux.org/guides/windows/#using-seperate-efi-partitions) (whatever applies to your case) at `/boot/efi` and the partition you created for Linux at `/`. If you want separate partitions for `/home`, `/boot` etc., make sure you have created them before as well and mount them accordingly during manual partitioning. + The installers of many distros provide options like "Automatic Partitioning" when installing Linux. You must always select the option that allows "Manual Partitioning". **Do not** select "Automatic Partitioning" as it will remove macOS as well. During manual partitioning make sure that you mount `/dev/nvme0n1p1` or your [separate EFI partition](https://wiki.t2linux.org/guides/windows/#using-separate-efi-partitions) (whatever applies to your case) at `/boot/efi` and the partition you created for Linux at `/`. If you want separate partitions for `/home`, `/boot`, etc., make sure you have created them before as well and mount them accordingly during manual partitioning. This wiki provides a set of [guides for different distributions](https://wiki.t2linux.org/distributions/overview/). If the distribution you want to use is present there, it's recommended to follow it instead of the official documentation by distribution vendor, as it considers T2 support. diff --git a/docs/guides/startup-manager.md b/docs/guides/startup-manager.md index 9f1a87df5..28c1cbc7f 100644 --- a/docs/guides/startup-manager.md +++ b/docs/guides/startup-manager.md @@ -30,7 +30,7 @@ In this case the Windows startup disk is used to boot both Windows and Linux. Th ## Setting label in case you are using a separate EFI partition for Linux -More details about this can be found in the [triple boot guide](https://wiki.t2linux.org/guides/windows/#using-seperate-efi-partitions). +More details about this can be found in the [triple boot guide](https://wiki.t2linux.org/guides/windows/#using-separate-efi-partitions). In this case, boot into macOS, open a terminal window and run: diff --git a/docs/guides/wifi-bluetooth.md b/docs/guides/wifi-bluetooth.md index 77646ddd8..c09a346aa 100644 --- a/docs/guides/wifi-bluetooth.md +++ b/docs/guides/wifi-bluetooth.md @@ -190,7 +190,7 @@ Once you have run the script on macOS, depending on the method you chose, the st !!! warning "Internet connection may be required for **Method 4**" - **Method 4** needs certain dependencies to work. If they are missing, you need to have an active internet connection on Linux to download and install them. You can use Ethernet, USB tethering or an external Wi-Fi adapter to get internet. If you are using a customised ISO made for T2 Macs, then most likely those dependencies shall be shipped alongwith the ISO, so in that case internet shall not be required. + **Method 4** needs certain dependencies to work. If they are missing, you need to have an active internet connection on Linux to download and install them. You can use Ethernet, USB tethering or an external Wi-Fi adapter to get internet. If you are using a customized ISO made for T2 Macs, then most likely those dependencies shall be shipped alongwith the ISO, so in that case internet shall not be required. This method does not have any steps to be followed on macOS. So, you have to run the script directly on Linux. After you run the script on Linux, you have to choose the **"Retrieve the firmware directly from macOS**" option. diff --git a/docs/guides/windows.md b/docs/guides/windows.md index cac90e0e6..55dd16c36 100644 --- a/docs/guides/windows.md +++ b/docs/guides/windows.md @@ -1,6 +1,6 @@ # Introduction -This page is a guide on getting Windows and Linux both installed. Secure Boot Must be disabled from macOS recovery. If you want to be able to choose from macOS, Windows, or Linux in the Startup Manager (the menu you get by holding ⌥ key), goto 'Using separate EFI partitions'. If you just want to select between Linux and Windows in the GRUB bootloader, goto 'Using the same EFI partition'. +This page is a guide on getting Windows and Linux both installed. Secure Boot must be disabled from macOS recovery. If you want to be able to choose from macOS, Windows, or Linux in the Startup Manager (the menu you get by holding ⌥ key), go to 'Using separate EFI partitions'. If you just want to select between Linux and Windows in the GRUB bootloader, go to 'Using the same EFI partition'. The simplest way to triple boot is to install Windows first, and install Linux on the same EFI partition, so that the Windows option in Startup Manager will let you pick Linux or Windows. To do that, follow the first set of instructions here. @@ -8,7 +8,7 @@ The simplest way to triple boot is to install Windows first, and install Linux o ## If Windows is installed first -1. Install [Linux normally](https://wiki.t2linux.org/guides/preinstall/) (this is probably done for you if you are using an installer specific to T2 Macs). During installation, Put your bootloader on `/dev/nvme0n1p1`, which should be set to mount at `/boot/efi`. Once it installs the bootloader, the Windows entry in startup manager will boot Linux. +1. Install [Linux normally](https://wiki.t2linux.org/guides/preinstall/) (this is probably done for you if you are using an installer specific to T2 Macs). During installation, put your bootloader on `/dev/nvme0n1p1`, which should be set to mount at `/boot/efi`. Once it installs the bootloader, the Windows entry in startup manager will boot Linux. 2. Fix blank screen issue that may occur when booting Windows (Credits to gbrow004 for documenting this fix on his [Gist](https://gist.github.com/gbrow004/096f845c8fe8d03ef9009fbb87b781a4#fixing-bootcampwindows)): @@ -51,13 +51,13 @@ The simplest way to triple boot is to install Windows first, and install Linux o 9. Enable the GRUB menu so that you'll have time to pick Windows - 1. Boot into your Linux install by selecting the Windows option in startup manager. - 2. Edit ``/etc/default/grub`` with any preferred editor (nano/vim/) and with sudo. Change line ``GRUB_TIMEOUT_STYLE`` to ``GRUB_TIMEOUT_STYLE=MENU``. If you are using `nano`, save the file by doing CTRL+X, Y, then enter. - 3. We've now changed the GRUB Bootloader settings, but we now need to update GRUB to apply these changes. Type in ``sudo update-grub`` and hit enter. After the command is done, you're finished. + 1. Boot into your Linux install by selecting the Windows option in startup manager + 2. Edit `/etc/default/grub` with any preferred editor (nano/vim/) and with sudo. Change line `GRUB_TIMEOUT_STYLE` to `GRUB_TIMEOUT_STYLE=MENU`. If you are using `nano`, save the file by doing CTRL+X, Y, then enter. + 3. We've now changed the GRUB Bootloader settings, but we now need to update GRUB to apply these changes. Type in `sudo update-grub` and hit enter. After the command is done, you're finished. 10. You should now be able to boot either Windows or Linux from the GRUB bootloader. -It may be possible to skip steps 5-8 by doing the following command in macOS: `sudo sh -c "bless --mount /Volumes/EFI --setBoot --file /Volumes/EFI/efi/$(ls /Volumes/EFI/efi|grep -i -e microsoft -e boot -e apple -v)/grubx64.efi --shortform"` This might not prevent step 8 from being needed. +It may be possible to skip steps 5-8 by doing the following command in macOS: `sudo sh -c "bless --mount /Volumes/EFI --setBoot --file /Volumes/EFI/efi/$(ls /Volumes/EFI/efi|grep -i -e microsoft -e boot -e apple -v)/grubx64.efi --shortform"`. This might not prevent step 8 from being needed. # Using separate EFI partitions diff --git a/docs/index.md b/docs/index.md index f693e7505..c0850fdb0 100644 --- a/docs/index.md +++ b/docs/index.md @@ -37,7 +37,7 @@ Support for hardware is cross distro besides patches to the distribution specifi The following repos contain kernel modules for said support: - MacBook Bridge / T2 Linux Driver [https://github.com/t2linux/apple-bce-drv](https://github.com/t2linux/apple-bce-drv) -- Touchbar and Ambient Light [https://github.com/t2linux/apple-ib-drv](https://github.com/t2linux/apple-ib-drv) (Upstreamed in kernel 6.15) +- Touch Bar and Ambient Light [https://github.com/t2linux/apple-ib-drv](https://github.com/t2linux/apple-ib-drv) (Upstreamed in kernel 6.15) Instead of installing these modules manually, it is suggested to follow the [distro specific guides](https://wiki.t2linux.org/distributions/overview/) since they are pre-installed in our distro specific ISOs. @@ -60,8 +60,8 @@ Instead of installing these modules manually, it is suggested to follow the [dis - Wayland - libinput tuning is typically applied by distribution maintainers rather than end users. You can test changes on your own, see [debugging touchpad pressure](https://wayland.freedesktop.org/libinput/doc/latest/touchpad-pressure-debugging.html) and [palm detection](https://wayland.freedesktop.org/libinput/doc/latest/palm-detection.html) guides. If you get a configuration that works well, please notify the t2linux maintainers. - Xorg **(deprecated, use Wayland instead if possible)** - - Implement macOS-like Keyboard and trackpad experience on Gnome Xorg. Read the top comments of each file in the links given below to understand requirements, additional tools and usage. - - [Synaptics Config](https://gist.github.com/smileBeda/f0452f0d7f1f6d8aa772603411f7876f) (for general trackpad behaviour using Synaptics) + - Implement macOS-like Keyboard and trackpad experience on GNOME Xorg. Read the top comments of each file in the links given below to understand requirements, additional tools and usage. + - [Synaptics Config](https://gist.github.com/smileBeda/f0452f0d7f1f6d8aa772603411f7876f) (for general trackpad behavior using Synaptics) - [Fusuma Config](https://gist.github.com/smileBeda/74a52fe7cb0901da9e67ae4e39966982) (for additional gestures commands using Fusuma) ### Outdated diff --git a/docs/notable-contributors.md b/docs/notable-contributors.md index f71c7f202..3bb0bd324 100644 --- a/docs/notable-contributors.md +++ b/docs/notable-contributors.md @@ -5,15 +5,15 @@ This page contains all Notable Contributors for the Linux on T2 project. If there is someone missing that you think should be on this list, send a PR on the [wiki repository.](https://github.com/t2linux/wiki) - aunali1 (Arch Linux and Kernel Module work) [https://github.com/aunali1](https://github.com/aunali1) -- mikroskeem (NixOS and founder of t2linux discord community) [https://github.com/mikroskeem](https://github.com/mikroskeem) +- mikroskeem (NixOS and founder of t2linux Discord community) [https://github.com/mikroskeem](https://github.com/mikroskeem) - JPyke3 (Manjaro) [https://github.com/JPyke3](https://github.com/JPyke3) - marcosfad (Ubuntu) [https://github.com/marcosfad](https://github.com/marcosfad) - MCMrARM (MacBook Bridge / T2 Linux Driver) [https://github.com/MCMrARM](https://github.com/MCMrARM) - mikeeq (Fedora) [https://github.com/mikeeq](https://github.com/mikeeq) - networkException (Wiki maintenance and `mbpfan` fork for T2) [https://github.com/networkException](https://github.com/networkException) -- Redecorating (Arch Linux, Wiki maintenance, Apple GMUX for T2 Macs, Magic Backlight driver and improved the touchbar driver) [https://github.com/Redecorating](https://github.com/Redecorating) -- roadrunner2 (Touchbar and Ambient Light Driver) [https://github.com/roadrunner2](https://github.com/roadrunner2) -- kekrby (Audio, NixOS, Apple GMUX for T2 Macs, Magic Backlight driver and improved the touchbar driver) [https://github.com/kekrby](https://github.com/kekrby) +- Redecorating (Arch Linux, Wiki maintenance, Apple GMUX for T2 Macs, Magic Backlight driver and improved the Touch Bar driver) [https://github.com/Redecorating](https://github.com/Redecorating) +- roadrunner2 (Touch Bar and Ambient Light Driver) [https://github.com/roadrunner2](https://github.com/roadrunner2) +- kekrby (Audio, NixOS, Apple GMUX for T2 Macs, Magic Backlight driver and improved the Touch Bar driver) [https://github.com/kekrby](https://github.com/kekrby) - soopyc (NixOS) [https://github.com/soopyc](https://github.com/soopyc) - AdityaGarg8 (Ubuntu and wiki maintenance) [https://github.com/AdityaGarg8](https://github.com/AdityaGarg8) - EmreTech (Gentoo) [https://github.com/EmreTech](https://github.com/EmreTech) diff --git a/docs/roadmap.md b/docs/roadmap.md index 205821839..25cac765f 100644 --- a/docs/roadmap.md +++ b/docs/roadmap.md @@ -1,12 +1,12 @@ # Introduction -This article is meant to guide users through the wiki by giving an overview over the required steps to +This article is meant to guide users through the wiki by giving an overview of the required steps to get to a working installation. ## Deciding on the Installation Using Linux on a T2 Mac comes with compromises as well as advantages compared to macOS. You will need -to decide for yourself if it its worth it. +to decide for yourself if it is worth it. Your first consideration should be the risk you are taking. Don't worry, nobody has broken their machine so far by installing Linux and by following the guides closely you should be able to get everything working even without a lot of knowledge as well. @@ -16,7 +16,7 @@ Still in case something goes wrong we are not responsible for it, we will try ou While it is technically possible to remove macOS entirely, it is strongly encouraged to dual boot it with Linux because: -1. To set up Wi-Fi on Linux, you will need Wi-Fi firmware, which can be legally obtained only from macOS. It is illegal to host the firmware on any website as it is under a non redistributable license. +1. To set up Wi-Fi on Linux, you will need Wi-Fi firmware, which can be legally obtained only from macOS. It is illegal to host the firmware on any website as it is under a non-redistributable license. 2. It acts as a backup in case something goes wrong. 3. macOS updates often bring along certain firmware updates, which tend to be useful for Linux as well. @@ -35,16 +35,16 @@ While technically it is not a limitation when installing Linux, different distri ease of use and polish. Arch Linux probably has the most documentation, both officially for the whole project in form of the Arch Wiki and in scope of the -t2linux wiki with a really detailed and up to date install guide. On top of that there is also a work in progress `archinstall` script. +t2linux wiki with a really detailed and up-to-date install guide. On top of that there is also a work in progress `archinstall` script. Keep in mind however that the whole process is done in the command line. Manjaro has a more guided install experience, with a graphical installer and multiple prebuilt ISOs for different desktop environments. There are 2 versions of the Manjaro ISO built by different people. JPyke3's version, which is not recommended, and NoaHimesaka1873's which is newer and recommended. -EndeavourOS is an Arch based Linux distribution with a graphical installer. This distribution requires little to no configuration after install. +EndeavourOS is an Arch-based Linux distribution with a graphical installer. This distribution requires little to no configuration after install. -Ubuntu also has a graphical installer. Additionally, less post configuration work is required as some kernel modules are getting installed automatically. +Ubuntu also has a graphical installer. Additionally, less post-configuration work is required as some kernel modules are getting installed automatically. -Fedora also has a prebuilt ISO and a graphical installer. Most things work out of the box, but you need to follow the wifi guide. +Fedora also has a prebuilt ISO and a graphical installer. Most things work out of the box, but you need to follow the Wi-Fi guide. NixOS has both prebuilt graphical and command line installers. Support for T2 devices is provided in the form of a `nixos-hardware` module. Importing the module is the only thing you have to do to get your configuration working on your Mac. diff --git a/docs/state.md b/docs/state.md index 5fa5cbf00..88fbc8daf 100644 --- a/docs/state.md +++ b/docs/state.md @@ -10,7 +10,7 @@ While Linux is usable on all T2 models, some features are limited due to the lac |Keyboard|🟢 Working|🔴 No||[apple-bce](https://github.com/t2linux/apple-bce-drv)| |Trackpad|🟢 Working|🔴 No|Works, but isn't as great as on macOS (no force touch or palm rejection).|[apple-bce](https://github.com/t2linux/apple-bce-drv), [Trackpad tuning](https://wiki.t2linux.org/#trackpad-tuning)| |Wi-Fi|🟢 Working|🟢 Yes|Requires macOS firmware|[Setup guide](https://wiki.t2linux.org/guides/wifi-bluetooth/)| -|Bluetooth|🟡 Partially working|🟢 Yes|Requires macOS firmware only for devices with BCM4377 chip. Also, Bluetooth glitches on devices with BCM4377 Chip if connected to a 2.4 Ghz Wi-Fi connection. Thus, in order to use Bluetooth either turn off your Wi-Fi or use a 5Ghz Wi-Fi connection.|[Setup guide](https://wiki.t2linux.org/guides/wifi-bluetooth/)| +|Bluetooth|🟡 Partially working|🟢 Yes|Requires macOS firmware only for devices with BCM4377 chip. Also, Bluetooth glitches on devices with BCM4377 Chip if connected to a 2.4 GHz Wi-Fi connection. Thus, in order to use Bluetooth either turn off your Wi-Fi or use a 5 GHz Wi-Fi connection.|[Setup guide](https://wiki.t2linux.org/guides/wifi-bluetooth/)| |Camera|🟢 Working|🔴 No||[apple-bce](https://github.com/t2linux/apple-bce-drv)| |Thunderbolt|🟢 Working|🟢 Yes|If it doesn't work, try replacing `pcie_ports=compat` with `pcie_ports=native` in the kernel parameters via GRUB.|| |Touch Bar|🟢 Working|🔴 No|"Touch Bar Keyboard" mode works OOTB, where only the Function Keys or the Media/Brightness Control Keys are shown. Support for custom graphics on the Touch Bar is being actively developed. The 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), [apple-ib](https://github.com/t2linux/apple-ib-drv)| @@ -18,12 +18,12 @@ While Linux is usable on all T2 models, some features are limited due to the lac |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)| |Hybrid Graphics|🟡 Partially working|🟡 Partial|Toggling dGPU power doesn't work.|[Hybrid Graphics](https://wiki.t2linux.org/guides/hybrid-graphics/)| |AMD GPUs|🟡 Partially working||Changing resolution, using DRI_PRIME and doing various other things can cause crashes, but `echo high \| sudo tee /sys/bus/pci/drivers/amdgpu/0000:??:??.?/power_dpm_force_performance_level` or adding `amdgpu.dpm=0` to the kernel commandline stops these crashes.|| -|MacPro7,1|🟡 Partially working||Users have encountered PCIE Address Space issues, with auto remap breaking. A temporary solution may be possible by removing the Infinity Fabric Link (Bridge or Jumper) from the GPU(s).|| +|MacPro7,1|🟡 Partially working||Users have encountered PCIe Address Space issues, with auto remap breaking. A temporary solution may be possible by removing the Infinity Fabric Link (Bridge or Jumper) from the GPU(s).|| |T2 Secure Enclave|🔴 Not working||Used for Touch ID, storing encryption keys on macOS|| |T2 Audio Video Encoder|🔴 Not working||Used for Sidecar on macOS|| ## Filesystem notes -- Linux using APFS filesystems: Linux cannot read the internal SSD's macOS APFS parition's Data and System volume (for other APFS volumes, [linux-apfs-rw](https://github.com/linux-apfs/linux-apfs-rw) can be used for reading data, but attempting to write is risky). +- Linux using APFS filesystems: Linux cannot read the internal SSD's macOS APFS partition's Data and System volume (for other APFS volumes, [linux-apfs-rw](https://github.com/linux-apfs/linux-apfs-rw) can be used for reading data, but attempting to write is risky). - macOS using Linux filesystems: There are FUSE implementations of some Linux Filesystems that can be used on macOS (but again, most only have experimental write support).