Rewrite (#21)

gg

.github/workflows/deploy.yaml

@@ -0,0 +1,82 @@
+# Sample workflow for building and deploying a Hugo site to GitHub Pages
+name: Deploy Hugo site to Pages
+
+on:
+  # Runs on pushes targeting the default branch
+  push:
+    branches:
+      - main
+
+  # Allows you to run this workflow manually from the Actions tab
+  workflow_dispatch:
+
+# Sets permissions of the GITHUB_TOKEN to allow deployment to GitHub Pages
+permissions:
+  contents: read
+  pages: write
+  id-token: write
+
+# Allow only one concurrent deployment, skipping runs queued between the run in-progress and latest queued.
+# However, do NOT cancel in-progress runs as we want to allow these production deployments to complete.
+concurrency:
+  group: "pages"
+  cancel-in-progress: false
+
+# Default to bash
+defaults:
+  run:
+    shell: bash
+
+jobs:
+  # Build job
+  build:
+    runs-on: ubuntu-latest
+    env:
+      HUGO_VERSION: 0.120.2
+    steps:
+      - name: Install Hugo CLI
+        run: |
+          wget -O ${{ runner.temp }}/hugo.deb https://github.com/gohugoio/hugo/releases/download/v${HUGO_VERSION}/hugo_extended_${HUGO_VERSION}_linux-amd64.deb \
+          && sudo dpkg -i ${{ runner.temp }}/hugo.deb          
+      - name: Install Dart Sass
+        run: sudo snap install dart-sass
+      - name: Checkout
+        uses: actions/checkout@v4
+        with:
+          submodules: recursive
+          fetch-depth: 0
+      - name: Setup Pages
+        id: pages
+        uses: actions/configure-pages@v3
+      - name: Install Node.js dependencies
+        run: "[[ -f package-lock.json || -f npm-shrinkwrap.json ]] && npm ci || true"
+      - name: Build with Hugo
+        env:
+          # For maximum backward compatibility with Hugo modules
+          HUGO_ENVIRONMENT: production
+          HUGO_ENV: production
+        run: |
+          hugo \
+            --gc \
+            --minify \
+            --baseURL "${{ steps.pages.outputs.base_url }}/"          
+      - name: Upload artifact
+        uses: actions/upload-pages-artifact@v2
+        with:
+          path: ./public
+
+  # Deployment job
+  deploy:
+    environment:
+      name: github-pages
+      url: ${{ steps.deployment.outputs.page_url }}
+    runs-on: ubuntu-latest
+    needs: build
+    steps:
+      - name: Deploy to GitHub Pages
+        id: deployment
+        uses: actions/deploy-pages@v2
+
+
+# #worksonmymachine
+# please fucking work 

archetypes/default.md

@@ -0,0 +1,6 @@
+---
+title: "{{ replace .Name "-" " " | title }}"
+date: {{ .Date }}
+draft: true
+---
+

content/docs/_index.md

@@ -0,0 +1,8 @@
+---
+weight: 10
+title: "ChromebookOSX"
+description: "Installing macOS on ASUS C425/C434/C433 models"
+icon: menu_book
+lead: ""
+draft: false
+---

content/docs/firmware/_index.md

@@ -0,0 +1,8 @@
+---
+weight: 200
+title: "Firmware"
+description: "Find pages relarted to firmware here."
+icon: menu_book
+lead: ""
+draft: false
+---

content/docs/firmware/fixedfw.md

@@ -0,0 +1,31 @@
+---
+weight: 220
+draft: false
+title: "Flashing custom coreboot UEFI"
+icon: "circle"
+description: "Flashing custom UEFI firmware for bug fixes"
+---
+
+{{< alert context="danger" text="Flashing firmware always has the ability to brick your device. Please proceed with caution." />}}
+
+
+# Flashing Custom Firmware 
+This is done to fix several notorious bugs in Chromeintoshes. You will suffer greatly if you don't do this.
+
+
+## Obtaining a ROM
+1. Visit the Chromeintosh repo for a zip of ROMs.
+2. Download
+
+
+## Flashing
+1. Boot a live Linux USB. Fedora or Ubuntu are all valid choices.
+2. Obtain your ROM (See above)
+3. Download flashrom, then `chmod +x` it;
+   ```cd; curl -LO https://tree123.org/chrultrabook/utils/flashrom-libpci38; chmod +x flashrom-libpci38```
+4. Flash
+   1. Backup your current rom, just in case things go wrong: `./flashrom-libpci38 -p internal -r current.rom`
+   2. Flash your custom firmware: `sudo ./flashrom-libpci38 -p internal --ifd -i bios -w ROM.rom`
+5. Assuming it said success on all checks, reboot.
+
+{{< alert context="danger" text="Do not reboot if any of the checks failed. DO NOT SHUTDOWN THE LAPTOP. Ask for help in the chrultraook forum." />}}

content/docs/firmware/quickstart.md

@@ -0,0 +1,53 @@
+---
+weight: 210
+draft: false
+title: "Flashing FW on CrOS"
+icon: "rocket_launch"
+description: "Enabling DevMode + Flashing FW"
+---
+
+## Requirements
+
+- A Chromebook
+- A USB drive larger than 8 gigabytes
+- Internet connection
+- Yo brain
+
+## Step 1: Enabling Developer Mode
+
+1. Press the `esc` + `refresh` + `power` buttons all at once on your Chromebook. Doing so will bring you to a screen that will prompt you to insert a USB stick or SD card.
+2. On that screen, press `ctrl` + `d`. It will prompt you if you want to turn off OS verification. Press `ENTER`. Your Chromebook will restart and present a screen that says OS verification is OFF.
+3. ChromeOS will then display a message for 30 seconds about transitioning the system to developer mode.
+4. Once done, the Chromebook will restart into developer mode. Now, you can flash custom firmware.
+
+
+## Step 2: Disabling Write Protection:
+
+1. Open up the back of your Chromebook. There are screws under all 4 rubber feet.
+2. Find the cable going from the battery to the motherbord
+3. Pull back the metal cover protecting the cable.
+4. Gently lift up the cable.
+5. Plug in your charger, then boot chromeOS **with the battery unplugged.**
+6. Flash FW (see below)
+
+## Step 3: Firmware
+
+To keep it breif, UEFI firmware allows the Chromebook to become any other laptop. This means you will lose access to chromeOS. RW_Legacy allows you to dualboot chromeOS along with Linux.
+
+1. Open a terminal via VT-2 by pressing `ctrl` + `alt` + `→`.
+2. Log in as user `chronos`. Note that there should be no password unless you set one yourself.
+3. Run the Firmware Utility Script:
+  ```shell
+cd; curl -LO mrchromebox.tech/firmware-util.sh && sudo bash firmware-util.sh
+```
+
+If you encounter certificate related errors when downloading the script from ChromeOS, then add -k to the curl command and script command to bypass SSL certificate checking as so:
+```shell
+cd; curl -LOk mrchromebox.tech/firmware-util.sh && sudo bash firmware-util.sh
+```
+
+{{< alert context="warning" text="The Firmware Utility Script cannot be run from a crosh shell, or a crostini shell." />}}
+
+4. Select the firmware you would like to flash.
+5. Follow the on-screen prompts. Once you are done, you should reboot into the new firmware! Keep in mind that the first boot will always take longer due to a process called "memory training". DO NOT power off the device at any time during the first boot.
+

content/docs/installingmacos/_index.md

@@ -0,0 +1,8 @@
+---
+weight: 300
+title: "Installing macOS"
+description: "Installing macOS"
+icon: menu_book
+lead: ""
+draft: false
+---

content/docs/installingmacos/installing.md

@@ -0,0 +1,64 @@
+---
+weight: 320
+title: "Installation"
+description: "Installing macOS"
+icon: menu_book
+lead: ""
+draft: false
+---
+
+# Installation
+
+{{< alert context="info" text="Read through this more than once, to prevent errors. Read these steps carefully, they are required for proper functioning." />}}
+
+Time for the soul-sucking stuff /j
+
+ **You want to start with the [OpenCore Install Guide](https://dortania.github.io/OpenCore-Install-Guide/) first.** Afterwards, we'll modify your EFI a little bit to make it work with our Chromebook.
+   - Take your time and read everything in there throughly, it's good practice to do so.
+   - For your `config.plist` setup, you want to follow the Laptop Kaby Lake section.
+   - The Dortania guide is actually pretty up-to-date with Chromebook items so it should be a pretty smooth experience overall. We will cover them here anyway just in case you missed it.
+
+### ACPI Folder
+Everything else you need to do in your ACPI folder
+
+1. Add the compiled version of [SSDT-PLUG-ALT.aml](https://github.com/meghan06/croscorebootpatch) into your ACPI folder.
+2. Compile and add [the top row keyboard remap SSDT](https://github.com/1Revenger1/Acer-Spin-713-Hackintosh/blob/main/src/ACPI/SSDT-ChromeKeys.dsl)
+3. Compile and add a [fake ambient light sensor SSDT](https://github.com/acidanthera/OpenCorePkg/blob/master/Docs/AcpiSamples/Source/SSDT-ALS0.dsl) to your ACPI folder. This is needed for working keyboard backlight.
+4. Download SSDTTime, then generate a FixHPET SSDT. Select C for default, then drag the compiled version into your ACPI folder
+
+### Kext Folder¹
+Everything else you need in your Kext folder
+
+1. Add the [eMMC driver](https://github.com/acidanthera/EmeraldSDHC/releases) to your kext folder.
+2. Replace the default VoodooPS2 kext with one modified for [Chromebook keyboards](https://github.com/1Revenger1/VoodooPS2/releases)
+3. Add the [EC kext](https://github.com/1Revenger1/CrosEC/releases). for a functional EC/kb backlight
+
+### config.plist Patches
+1. Your SMBIOS should be `MacBookAir8,1`
+2. under `Booter -> Quirks` set `ProtectMemoryRegions` to `TRUE`. It should look something like this in your `config.plist` when done correctly:
+
+   | Quirk                | Type | Value    |
+   | -------------------- | ---- | -------- |
+   | ProtectMemoryRegions | Boolean | True  |
+
+   {{< alert context="danger" text="This MUST be enabled if you want working WiFi or NVRAM" />}}
+
+
+4. Under `DeviceProperties -> Add -> PciRoot(0x0)/Pci(0x2,0x0)`, make the following modifications:
+
+   | Key                  | Type | Value    |
+   | -------------------- | ---- | -------- |
+   | AAPL,ig-platform-id  | data | 0000C087 |
+   | device-id            | data | C0870000 |
+   | disable-telemetry-load | data | 01000000 |
+   | rps-control | data | 01000000 |
+     
+{{< alert context="danger" text="These should be the only two items `in PciRoot(0x0)/Pci(0x2,0x0)`" />}}
+
+5. Merge the HPET patches from Step 4 in ACPI to ACPI -> Patches.
+6. Map USB using USBToolBox
+
+
+#### Notes:
+
+* ¹ SHYVANA users (C434 and C433) will need `VoodooI2CHID.kext` for touchscreen to function.