mirror of
https://github.com/ps5-linux/ps5-linux-patches.git
synced 2026-07-15 21:42:27 +00:00
readme: simplify it
This commit is contained in:
47
README.md
47
README.md
@@ -9,43 +9,11 @@ cd linux
|
||||
git checkout tags/v7.0.3
|
||||
git apply ../ps5-linux-patches/linux.patch
|
||||
cp ../ps5-linux-patches/.config .config
|
||||
make -j16
|
||||
```
|
||||
|
||||
## Installation (Ubuntu)
|
||||
|
||||
In the same `linux` folder after compilation, do:
|
||||
|
||||
```bash
|
||||
sudo make modules_install
|
||||
sudo make install
|
||||
```
|
||||
|
||||
If you are updating Linux on your external USB SSD or you are directly booting into M.2 SSD, i.e. you use `-m2` in `cmdline.txt`, then you have to update the files on the FAT32 partition of your USB drive:
|
||||
|
||||
```bash
|
||||
sudo mv /boot/efi/bzImage /boot/efi/bzImage.old
|
||||
sudo mv /boot/efi/initrd.img /boot/efi/initrd.img.old
|
||||
sudo cp /boot/vmlinuz-$(uname -r) /boot/efi/bzImage
|
||||
sudo cp /boot/initrd.img-$(uname -r) /boot/efi/initrd.img
|
||||
```
|
||||
|
||||
If you are updating Linux on your M.2 SSD, but you do not directly boot into it, i.e. if you use `m2_exec.sh`, then you do need to do this step.
|
||||
|
||||
## Compilation and Installation (Arch Linux)
|
||||
|
||||
Since Arch Linux is different on how the kernel is built, here are some updated commands for compiling
|
||||
```bash
|
||||
git clone https://github.com/ps5-linux/ps5-linux-patches
|
||||
git clone https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
|
||||
cd linux
|
||||
git checkout tags/v7.0.3
|
||||
git apply ../ps5-linux-patches/linux.patch
|
||||
cp ../ps5-linux-patches/.config .config
|
||||
make olddefconfig
|
||||
make -j$(nproc)
|
||||
```
|
||||
|
||||
## Installation
|
||||
|
||||
In the same `linux` folder after compilation, do:
|
||||
|
||||
```bash
|
||||
@@ -53,23 +21,22 @@ sudo make modules_install
|
||||
sudo make install
|
||||
```
|
||||
|
||||
Then generate the initrd:
|
||||
If you use Arch Linux, then additionally do:
|
||||
|
||||
```bash
|
||||
sudo mkinitcpio -k "$(make kernelrelease)" -g /boot/initrd.img-$(make kernelrelease) || true
|
||||
```
|
||||
|
||||
If you are updating Linux on your external USB SSD or you are directly booting into M.2 SSD, i.e. you use `-m2` in `cmdline.txt`, then you have to update the files on the FAT32 partition of your USB drive:
|
||||
If you are updating Linux on your external USB SSD or if you are directly booting into M.2 SSD, i.e. if you use `-m2` in `cmdline.txt`, then you have to update the files on the FAT32 partition of your USB drive:
|
||||
|
||||
```bash
|
||||
sudo mv /boot/efi/bzImage /boot/efi/bzImage.old
|
||||
sudo mv /boot/efi/initrd.img /boot/efi/initrd.img.old
|
||||
sudo cp ~/linux/arch/x86/boot/bzImage /boot/efi/bzImage
|
||||
sudo cp /boot/initrd.img-$(make kernelrelease) /boot/efi/initrd.img
|
||||
sync
|
||||
sudo cp /boot/vmlinuz /boot/efi/bzImage
|
||||
sudo cp /boot/initrd.img /boot/efi/initrd.img
|
||||
```
|
||||
|
||||
If you are updating Linux on your M.2 SSD, but you do not directly boot into it, i.e. if you use `m2_exec.sh`, then you do not need to do this step.
|
||||
If you are updating Linux on your M.2 SSD, but you do not directly boot into it, i.e. if you use `m2_exec.sh`, then you do need to do this step.
|
||||
|
||||
|
||||
## TODO
|
||||
|
||||
Reference in New Issue
Block a user