Ahoj pratele,
pred casem jsem se bavil o moznosti prekladat jadro pro rpi na rychlem PC. Navod byl udajne priserny. Zkousel jsem to a opravdu, navod nic moc, je tezke se v nem vysnat. Nicmene nakonec jsem uspel s kompilaci a instralaci jadra vcetne modulu.
Problem:
Navod obsahuje chyby v prikazech (nekolikrat chybi '/') a popis nastaveni cest pro tools a volba 64bit/32bit je take matouci.
Zde je navod ktery by mel byt jiz jasnejsi, mam to vystavit do knowledge base?
Mr.holub
=== Cross-compiling ===
== Install toolchain
Use the following command to install the toolchain:
git clone https://github.com/raspberrypi/tools
You can then copy the tools directory to a common location (I've put it in /var/lib/gitolite/rpi but you can use any other dir.)
add tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/bin to your $PATH
For 32-bit host systems: use tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/bin
For 64-bit host systems: use tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian-x64/bin
Example of adding path to the existing paths for particular shell session (your subdir will be probably different:
32bit host example:
PATH=$PATH:/var/lib/gitolite/rpi/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/bin
64bit host example:
PATH=$PATH:/var/lib/gitolite/rpi/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian-x64/bin/
== Get sources
To get the sources, refer to the original GitHub repository for the various branches.
git clone --depth=1 https://github.com/raspberrypi/linux
== Build sources
Enter the following commands to build the sources and Device Tree files:
For Pi 1 or Compute Module or Pi ZERO:
cd linux KERNEL=kernel make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- bcmrpi_defconfig
For Pi 2/3:
cd linux KERNEL=kernel7 make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- bcm2709_defconfig
Then, for both (replace X by number of threads - often 1.5 * number of cores):
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- zImage modules dtbs -j X
Install directly onto the SD card
Having built the kernel, you need to copy it onto your Raspberry Pi and install the modules; this is best done directly using an SD card reader.
First, use lsblk before and after plugging in your SD card to identify it. You should end up with something like this:
sdb sdb1 sdb2
with sdb1 being the FAT (boot) partition, and sdb2 being the ext4 filesystem (root) partition.
If it's a NOOBS card, you should see something like this:
sdb sdb1 sdb2 sdb5 sdb6 sdb7
with sdb6 being the FAT (boot) partition, and sdb7 being the ext4 filesystem (root) partition.
Mount these first, adjusting the partition numbers for NOOBS cards:
mkdir /mnt/fat32 mkdir /mnt/ext4 sudo mount /dev/sdb1 /mnt/fat32 sudo mount /dev/sdb2 /mnt/ext4
Next, install the modules:
sudo make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- INSTALL_MOD_PATH=/mnt/ext4 modules_install
Finally, copy the kernel and Device Tree blobs onto the SD card, making sure to back up your old kernel:
cp mnt/fat32/$KERNEL.img /mnt/fat32/$KERNEL-backup.img scripts/mkknlimg arch/arm/boot/zImage /mnt/fat32/$KERNEL.img cp arch/arm/boot/dts/*.dtb /mnt/fat32/ cp arch/arm/boot/dts/overlays/*.dtb* /mnt/fat32/overlays/ cp arch/arm/boot/dts/overlays/README /mnt/fat32/overlays/ umount /mnt/fat32 umount /mnt/ext4
Another option is to copy the kernel into the same place, but with a different filename - for instance, kernel-myconfig.img - rather than overwriting the kernel.img file. You can then edit the config.txt file to select the kernel that the Pi will boot into:
kernel=kernel-myconfig.img
This has the advantage of keeping your kernel separate from the kernel image managed by the system and any automatic update tools, and allowing you to easily revert to a stock kernel in the event that your kernel cannot boot.
Finally, plug the card into the Pi and boot it!
ted koukam, ze se jeden prikaz dementne zalamal,
install modules ma byt na jednom radku:
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- INSTALL_MOD_PATH=/mnt/ext4 modules_install
To byla take jedna z chyb!
On Mon, 20 Mar 2017 22:51:05 +0100, Robert Holub mrholub@hotmail.com wrote:
Ahoj pratele,
pred casem jsem se bavil o moznosti prekladat jadro pro rpi na rychlem PC. Navod byl udajne priserny. Zkousel jsem to a opravdu, navod nic moc, je tezke se v nem vysnat. Nicmene nakonec jsem uspel s kompilaci a instralaci jadra vcetne modulu.
Problem:
Navod obsahuje chyby v prikazech (nekolikrat chybi '/') a popis nastaveni cest pro tools a volba 64bit/32bit je take matouci.
Zde je navod ktery by mel byt jiz jasnejsi, mam to vystavit do knowledge base?
Mr.holub
=== Cross-compiling ===
== Install toolchain
Use the following command to install the toolchain:
git clone https://github.com/raspberrypi/tools
You can then copy the tools directory to a common location (I've put it in /var/lib/gitolite/rpi but you can use any other dir.)
add tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/bin to your $PATH
For 32-bit host systems: use tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/bin
For 64-bit host systems: use tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian-x64/bin
Example of adding path to the existing paths for particular shell session (your subdir will be probably different:
32bit host example:
PATH=$PATH:/var/lib/gitolite/rpi/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/bin
64bit host example:
PATH=$PATH:/var/lib/gitolite/rpi/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian-x64/bin/
== Get sources
To get the sources, refer to the original GitHub repository for the various branches.
git clone --depth=1 https://github.com/raspberrypi/linux
== Build sources
Enter the following commands to build the sources and Device Tree files:
For Pi 1 or Compute Module or Pi ZERO:
cd linux KERNEL=kernel make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- bcmrpi_defconfig
For Pi 2/3:
cd linux KERNEL=kernel7 make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- bcm2709_defconfig
Then, for both (replace X by number of threads - often 1.5 * number of cores):
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- zImage modules dtbs -j X
Install directly onto the SD card
Having built the kernel, you need to copy it onto your Raspberry Pi and install the modules; this is best done directly using an SD card reader.
First, use lsblk before and after plugging in your SD card to identify it. You should end up with something like this:
sdb sdb1 sdb2
with sdb1 being the FAT (boot) partition, and sdb2 being the ext4 filesystem (root) partition.
If it's a NOOBS card, you should see something like this:
sdb sdb1 sdb2 sdb5 sdb6 sdb7
with sdb6 being the FAT (boot) partition, and sdb7 being the ext4 filesystem (root) partition.
Mount these first, adjusting the partition numbers for NOOBS cards:
mkdir /mnt/fat32 mkdir /mnt/ext4 sudo mount /dev/sdb1 /mnt/fat32 sudo mount /dev/sdb2 /mnt/ext4
Next, install the modules:
sudo make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- INSTALL_MOD_PATH=/mnt/ext4 modules_install
Finally, copy the kernel and Device Tree blobs onto the SD card, making sure to back up your old kernel:
cp mnt/fat32/$KERNEL.img /mnt/fat32/$KERNEL-backup.img scripts/mkknlimg arch/arm/boot/zImage /mnt/fat32/$KERNEL.img cp arch/arm/boot/dts/*.dtb /mnt/fat32/ cp arch/arm/boot/dts/overlays/*.dtb* /mnt/fat32/overlays/ cp arch/arm/boot/dts/overlays/README /mnt/fat32/overlays/ umount /mnt/fat32 umount /mnt/ext4
Another option is to copy the kernel into the same place, but with a different filename - for instance, kernel-myconfig.img - rather than overwriting the kernel.img file. You can then edit the config.txt file to select the kernel that the Pi will boot into:
kernel=kernel-myconfig.img
This has the advantage of keeping your kernel separate from the kernel image managed by the system and any automatic update tools, and allowing you to easily revert to a stock kernel in the event that your kernel cannot boot.
Finally, plug the card into the Pi and boot it! _______________________________________________ Brmlab mailing list Brmlab@brmlab.cz https://brmlab.cz/cgi-bin/mailman/listinfo/brmlab
Ahoj Holube mozno offtoppic ale zaujmalo by ma ... bol nejaky konkretny dovod preco si musel prekompilovavat jadro na raspi ?
2017-03-20 23:33 GMT+01:00 Robert Holub mrholub@hotmail.com:
ted koukam, ze se jeden prikaz dementne zalamal,
install modules ma byt na jednom radku:
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- INSTALL_MOD_PATH=/mnt/ext4 modules_install
To byla take jedna z chyb!
On Mon, 20 Mar 2017 22:51:05 +0100, Robert Holub mrholub@hotmail.com wrote:
Ahoj pratele,
pred casem jsem se bavil o moznosti prekladat jadro pro rpi na rychlem PC. Navod byl udajne priserny. Zkousel jsem to a opravdu, navod nic moc, je tezke se v nem vysnat. Nicmene nakonec jsem uspel s kompilaci a instralaci jadra vcetne modulu.
Problem:
Navod obsahuje chyby v prikazech (nekolikrat chybi '/') a popis nastaveni cest pro tools a volba 64bit/32bit je take matouci.
Zde je navod ktery by mel byt jiz jasnejsi, mam to vystavit do knowledge base?
Mr.holub
=== Cross-compiling ===
== Install toolchain
Use the following command to install the toolchain:
git clone https://github.com/raspberrypi/tools
You can then copy the tools directory to a common location (I've put it in /var/lib/gitolite/rpi but you can use any other dir.)
add tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/bin to
your
$PATH
For 32-bit host systems: use tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/bin
For 64-bit host systems: use tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian-x64/bin
Example of adding path to the existing paths for particular shell session (your subdir will be probably different:
32bit host example:
PATH=$PATH:/var/lib/gitolite/rpi/tools/arm-bcm2708/gcc-
linaro-arm-linux-gnueabihf-raspbian/bin
64bit host example:
PATH=$PATH:/var/lib/gitolite/rpi/tools/arm-bcm2708/gcc-
linaro-arm-linux-gnueabihf-raspbian-x64/bin/
== Get sources
To get the sources, refer to the original GitHub repository for the various branches.
git clone --depth=1 https://github.com/raspberrypi/linux
== Build sources
Enter the following commands to build the sources and Device Tree files:
For Pi 1 or Compute Module or Pi ZERO:
cd linux KERNEL=kernel make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- bcmrpi_defconfig
For Pi 2/3:
cd linux KERNEL=kernel7 make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- bcm2709_defconfig
Then, for both (replace X by number of threads - often 1.5 * number of cores):
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- zImage modules dtbs -j
X
Install directly onto the SD card
Having built the kernel, you need to copy it onto your Raspberry Pi and install the modules; this is best done directly using an SD card reader.
First, use lsblk before and after plugging in your SD card to identify it. You should end up with something like this:
sdb sdb1 sdb2
with sdb1 being the FAT (boot) partition, and sdb2 being the ext4 filesystem (root) partition.
If it's a NOOBS card, you should see something like this:
sdb sdb1 sdb2 sdb5 sdb6 sdb7
with sdb6 being the FAT (boot) partition, and sdb7 being the ext4 filesystem (root) partition.
Mount these first, adjusting the partition numbers for NOOBS cards:
mkdir /mnt/fat32 mkdir /mnt/ext4 sudo mount /dev/sdb1 /mnt/fat32 sudo mount /dev/sdb2 /mnt/ext4
Next, install the modules:
sudo make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- INSTALL_MOD_PATH=/mnt/ext4 modules_install
Finally, copy the kernel and Device Tree blobs onto the SD card, making sure to back up your old kernel:
cp mnt/fat32/$KERNEL.img /mnt/fat32/$KERNEL-backup.img scripts/mkknlimg arch/arm/boot/zImage /mnt/fat32/$KERNEL.img cp arch/arm/boot/dts/*.dtb /mnt/fat32/ cp arch/arm/boot/dts/overlays/*.dtb* /mnt/fat32/overlays/ cp arch/arm/boot/dts/overlays/README /mnt/fat32/overlays/ umount /mnt/fat32 umount /mnt/ext4
Another option is to copy the kernel into the same place, but with a different filename - for instance, kernel-myconfig.img - rather than overwriting the kernel.img file. You can then edit the config.txt file to select the kernel that the Pi will boot into:
kernel=kernel-myconfig.img
This has the advantage of keeping your kernel separate from the kernel image managed by the system and any automatic update tools, and allowing you to easily revert to a stock kernel in the event that your kernel cannot boot.
Finally, plug the card into the Pi and boot it! _______________________________________________ Brmlab mailing list Brmlab@brmlab.cz https://brmlab.cz/cgi-bin/mailman/listinfo/brmlab
-- Using Opera's mail client: http://www.opera.com/mail/ _______________________________________________ Brmlab mailing list Brmlab@brmlab.cz https://brmlab.cz/cgi-bin/mailman/listinfo/brmlab
Dobrá práce , zdokumentuj to na wiki.
2017-03-21 9:49 GMT+01:00 Tomislav Arnaudov sargonout@gmail.com:
Ahoj Holube mozno offtoppic ale zaujmalo by ma ... bol nejaky konkretny dovod preco si musel prekompilovavat jadro na raspi ?
2017-03-20 23:33 GMT+01:00 Robert Holub mrholub@hotmail.com:
ted koukam, ze se jeden prikaz dementne zalamal,
install modules ma byt na jednom radku:
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- INSTALL_MOD_PATH=/mnt/ext4 modules_install
To byla take jedna z chyb!
On Mon, 20 Mar 2017 22:51:05 +0100, Robert Holub mrholub@hotmail.com wrote:
Ahoj pratele,
pred casem jsem se bavil o moznosti prekladat jadro pro rpi na rychlem PC. Navod byl udajne priserny. Zkousel jsem to a opravdu, navod nic moc, je tezke se v nem vysnat. Nicmene nakonec jsem uspel s kompilaci a instralaci jadra vcetne modulu.
Problem:
Navod obsahuje chyby v prikazech (nekolikrat chybi '/') a popis nastaveni cest pro tools a volba 64bit/32bit je take matouci.
Zde je navod ktery by mel byt jiz jasnejsi, mam to vystavit do knowledge base?
Mr.holub
=== Cross-compiling ===
== Install toolchain
Use the following command to install the toolchain:
git clone https://github.com/raspberrypi/tools
You can then copy the tools directory to a common location (I've put it in /var/lib/gitolite/rpi but you can use any other dir.)
add tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/bin to
your
$PATH
For 32-bit host systems: use tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/bin
For 64-bit host systems: use tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian-x64/bin
Example of adding path to the existing paths for particular shell
session
(your subdir will be probably different:
32bit host example:
PATH=$PATH:/var/lib/gitolite/rpi/tools/arm-bcm2708/gcc-linar
o-arm-linux-gnueabihf-raspbian/bin
64bit host example:
PATH=$PATH:/var/lib/gitolite/rpi/tools/arm-bcm2708/gcc-linar
o-arm-linux-gnueabihf-raspbian-x64/bin/
== Get sources
To get the sources, refer to the original GitHub repository for the various branches.
git clone --depth=1 https://github.com/raspberrypi/linux
== Build sources
Enter the following commands to build the sources and Device Tree files:
For Pi 1 or Compute Module or Pi ZERO:
cd linux KERNEL=kernel make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- bcmrpi_defconfig
For Pi 2/3:
cd linux KERNEL=kernel7 make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- bcm2709_defconfig
Then, for both (replace X by number of threads - often 1.5 * number of cores):
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- zImage modules dtbs
-j X
Install directly onto the SD card
Having built the kernel, you need to copy it onto your Raspberry Pi and install the modules; this is best done directly using an SD card reader.
First, use lsblk before and after plugging in your SD card to identify it. You should end up with something like this:
sdb sdb1 sdb2
with sdb1 being the FAT (boot) partition, and sdb2 being the ext4 filesystem (root) partition.
If it's a NOOBS card, you should see something like this:
sdb sdb1 sdb2 sdb5 sdb6 sdb7
with sdb6 being the FAT (boot) partition, and sdb7 being the ext4 filesystem (root) partition.
Mount these first, adjusting the partition numbers for NOOBS cards:
mkdir /mnt/fat32 mkdir /mnt/ext4 sudo mount /dev/sdb1 /mnt/fat32 sudo mount /dev/sdb2 /mnt/ext4
Next, install the modules:
sudo make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- INSTALL_MOD_PATH=/mnt/ext4 modules_install
Finally, copy the kernel and Device Tree blobs onto the SD card, making sure to back up your old kernel:
cp mnt/fat32/$KERNEL.img /mnt/fat32/$KERNEL-backup.img scripts/mkknlimg arch/arm/boot/zImage /mnt/fat32/$KERNEL.img cp arch/arm/boot/dts/*.dtb /mnt/fat32/ cp arch/arm/boot/dts/overlays/*.dtb* /mnt/fat32/overlays/ cp arch/arm/boot/dts/overlays/README /mnt/fat32/overlays/ umount /mnt/fat32 umount /mnt/ext4
Another option is to copy the kernel into the same place, but with a different filename - for instance, kernel-myconfig.img - rather than overwriting the kernel.img file. You can then edit the config.txt file
to
select the kernel that the Pi will boot into:
kernel=kernel-myconfig.img
This has the advantage of keeping your kernel separate from the kernel image managed by the system and any automatic update tools, and allowing you to easily revert to a stock kernel in the event that your kernel cannot boot.
Finally, plug the card into the Pi and boot it! _______________________________________________ Brmlab mailing list Brmlab@brmlab.cz https://brmlab.cz/cgi-bin/mailman/listinfo/brmlab
-- Using Opera's mail client: http://www.opera.com/mail/ _______________________________________________ Brmlab mailing list Brmlab@brmlab.cz https://brmlab.cz/cgi-bin/mailman/listinfo/brmlab
Brmlab mailing list Brmlab@brmlab.cz https://brmlab.cz/cgi-bin/mailman/listinfo/brmlab
Ahoj,
duvodem bylo novejsi jadro => drivery.
On Tue, 21 Mar 2017 09:49:48 +0100, Tomislav Arnaudov sargonout@gmail.com wrote:
Ahoj Holube mozno offtoppic ale zaujmalo by ma ... bol nejaky konkretny dovod preco si musel prekompilovavat jadro na raspi ?
2017-03-20 23:33 GMT+01:00 Robert Holub mrholub@hotmail.com:
ted koukam, ze se jeden prikaz dementne zalamal,
install modules ma byt na jednom radku:
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- INSTALL_MOD_PATH=/mnt/ext4 modules_install
To byla take jedna z chyb!
On Mon, 20 Mar 2017 22:51:05 +0100, Robert Holub mrholub@hotmail.com wrote:
Ahoj pratele,
pred casem jsem se bavil o moznosti prekladat jadro pro rpi na rychlem PC. Navod byl udajne priserny. Zkousel jsem to a opravdu, navod nic moc, je tezke se v nem vysnat. Nicmene nakonec jsem uspel s kompilaci a instralaci jadra vcetne
modulu.
Problem:
Navod obsahuje chyby v prikazech (nekolikrat chybi '/') a popis nastaveni cest pro tools a volba 64bit/32bit je take matouci.
Zde je navod ktery by mel byt jiz jasnejsi, mam to vystavit do
knowledge
base?
Mr.holub
=== Cross-compiling ===
== Install toolchain
Use the following command to install the toolchain:
git clone https://github.com/raspberrypi/tools
You can then copy the tools directory to a common location (I've put
it
in /var/lib/gitolite/rpi but you can use any other dir.)
add tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/bin to
your
$PATH
For 32-bit host systems: use tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/bin
For 64-bit host systems: use tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian-x64/bin
Example of adding path to the existing paths for particular shell
session
(your subdir will be probably different:
32bit host example:
PATH=$PATH:/var/lib/gitolite/rpi/tools/arm-bcm2708/gcc-
linaro-arm-linux-gnueabihf-raspbian/bin
64bit host example:
PATH=$PATH:/var/lib/gitolite/rpi/tools/arm-bcm2708/gcc-
linaro-arm-linux-gnueabihf-raspbian-x64/bin/
== Get sources
To get the sources, refer to the original GitHub repository for the various branches.
git clone --depth=1 https://github.com/raspberrypi/linux
== Build sources
Enter the following commands to build the sources and Device Tree
files:
For Pi 1 or Compute Module or Pi ZERO:
cd linux KERNEL=kernel make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- bcmrpi_defconfig
For Pi 2/3:
cd linux KERNEL=kernel7 make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- bcm2709_defconfig
Then, for both (replace X by number of threads - often 1.5 * number of cores):
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- zImage modules dtbs
-j X
Install directly onto the SD card
Having built the kernel, you need to copy it onto your Raspberry Pi
and
install the modules; this is best done directly using an SD card
reader.
First, use lsblk before and after plugging in your SD card to identify it. You should end up with something like this:
sdb sdb1 sdb2
with sdb1 being the FAT (boot) partition, and sdb2 being the ext4 filesystem (root) partition.
If it's a NOOBS card, you should see something like this:
sdb sdb1 sdb2 sdb5 sdb6 sdb7
with sdb6 being the FAT (boot) partition, and sdb7 being the ext4 filesystem (root) partition.
Mount these first, adjusting the partition numbers for NOOBS cards:
mkdir /mnt/fat32 mkdir /mnt/ext4 sudo mount /dev/sdb1 /mnt/fat32 sudo mount /dev/sdb2 /mnt/ext4
Next, install the modules:
sudo make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- INSTALL_MOD_PATH=/mnt/ext4 modules_install
Finally, copy the kernel and Device Tree blobs onto the SD card,
making
sure to back up your old kernel:
cp mnt/fat32/$KERNEL.img /mnt/fat32/$KERNEL-backup.img scripts/mkknlimg arch/arm/boot/zImage /mnt/fat32/$KERNEL.img cp arch/arm/boot/dts/*.dtb /mnt/fat32/ cp arch/arm/boot/dts/overlays/*.dtb* /mnt/fat32/overlays/ cp arch/arm/boot/dts/overlays/README /mnt/fat32/overlays/ umount /mnt/fat32 umount /mnt/ext4
Another option is to copy the kernel into the same place, but with a different filename - for instance, kernel-myconfig.img - rather than overwriting the kernel.img file. You can then edit the config.txt
file to
select the kernel that the Pi will boot into:
kernel=kernel-myconfig.img
This has the advantage of keeping your kernel separate from the kernel image managed by the system and any automatic update tools, and
allowing
you to easily revert to a stock kernel in the event that your kernel cannot boot.
Finally, plug the card into the Pi and boot it! _______________________________________________ Brmlab mailing list Brmlab@brmlab.cz https://brmlab.cz/cgi-bin/mailman/listinfo/brmlab
-- Using Opera's mail client: http://www.opera.com/mail/ _______________________________________________ Brmlab mailing list Brmlab@brmlab.cz https://brmlab.cz/cgi-bin/mailman/listinfo/brmlab
-
max fx -
Robert Holub -
Tomislav Arnaudov