New user's registration have been closed due to high spamming and low trafic on this forum. Please contact forum admins directly if you need an account. Thanks !
To create a custom install image for B1, B2 or B3?
To create a custom install image for B1, B2 or B3?
Hello,
how can one create her/his custom install image for her/his Bubba#?
If I could do this, I wish an installation image with the newest Debian system ( with the newest Bubba kernel ) with some applications for system rescue, such parted is.
What should one do to get such custom install image?
how can one create her/his custom install image for her/his Bubba#?
If I could do this, I wish an installation image with the newest Debian system ( with the newest Bubba kernel ) with some applications for system rescue, such parted is.
What should one do to get such custom install image?
Best, Pali
Re: To create a custom install image for B1, B2 or B3?
Hello,
I'm currently working on an updated install/rescue system for b2/b3 (not the b1) with a new install script to install various systems. The install/rescue system is done and source is available at GitHub. It should build on any regular linux system (tested on arch and debian). It's based on buildroot so it's failrly easy to customize. Take a look and don't hesitate to ask should you need help.
I'm currently working on an updated install/rescue system for b2/b3 (not the b1) with a new install script to install various systems. The install/rescue system is done and source is available at GitHub. It should build on any regular linux system (tested on arch and debian). It's based on buildroot so it's failrly easy to customize. Take a look and don't hesitate to ask should you need help.
Re: To create a custom install image for B1, B2 or B3?
I clone the buildroot source tree with command:MouettE wrote:Hello,
I'm currently working on an updated install/rescue system for b2/b3 (not the b1) with a new install script to install various systems. The install/rescue system is done and source is available at GitHub. It should build on any regular linux system (tested on arch and debian). It's based on buildroot so it's failrly easy to customize. Take a look and don't hesitate to ask should you need help.
Code: Select all
svn co https://github.com/Excito/buildroot
Best, Pali
Re: To create a custom install image for B1, B2 or B3?
Just run the make command from the top directory (see README.md)
Re: To create a custom install image for B1, B2 or B3?
Just noticed you're changing package sources on github. Will you be building packages and source archives as well? Can I rely on you assigning new revision numbers then? Do note that other projects use (some of) these sources as well. I'm actually kind of puzzled why writemagic had to move to a separate package from buttond.MouettE wrote:Just run the make command from the top directory (see README.md)
Re: To create a custom install image for B1, B2 or B3?
Yes there wil be new debian repositories with full binary and source packages. The version numbers will be incremented as normal packages.Gordon wrote:Just noticed you're changing package sources on github. Will you be building packages and source archives as well? Can I rely on you assigning new revision numbers then?
I think that it make more sense to tight write-magic with the halt scripts rather than buttond because the halt script depends on write-magic whereas buttond is not. That being said, write-magic and buttond are both b3-specific so it make also sense to build them in the same package. Or to have a specific package.Gordon wrote:I'm actually kind of puzzled why writemagic had to move to a separate package from buttond.
Re: To create a custom install image for B1, B2 or B3?
I see your point. It does not appear to be completely true however, as buttond is largely based around the write-magic code. Not looking at the code this moment, but I think that write-magic is/was in fact an already existing code snippet that was kept as is to accompany buttond to allow userland control as well. As such I do not think you could place write-magic in any specific category even though you do need it to "shut down" the B3.
IMO it would make more sense to extend the write-magic binary in a similar way as was done in buttond and create a proper shutdown command from it. Particularly because 0xdeadbeef seems to be the only sensible command line parameter you can supply and there is no reason NOT to hardcode that value (other than trying to obscure how to shut down the B3 from command line).
Should this be a separate topic?
IMO it would make more sense to extend the write-magic binary in a similar way as was done in buttond and create a proper shutdown command from it. Particularly because 0xdeadbeef seems to be the only sensible command line parameter you can supply and there is no reason NOT to hardcode that value (other than trying to obscure how to shut down the B3 from command line).
Should this be a separate topic?
Re: To create a custom install image for B1, B2 or B3?
OK, I clone the git repository once again:MouettE wrote:Just run the make command from the top directory (see README.md)
Code: Select all
svn co https://github.com/Excito/buildroot/trunk
Code: Select all
make excito_bubbatwo_defconfig
make
What can I do to solve this problem?>>> Executing post-image script board/excito/bubbatwo/post_image.sh
Compiling bubbatwo.dts
Preparing vmlinux.bin
Compiling reloc_shim_itb.S
Generating 8313E21.itb
board/excito/bubbatwo/post_image.sh: sor: 21: mkimage: command not found
Best, Pali
Re: To create a custom install image for B1, B2 or B3?
Hi,
Been a while since I used Debian, but I believe that's in the uboot-mkimage package, so:should fix it.
Best, sakaki
Been a while since I used Debian, but I believe that's in the uboot-mkimage package, so:
Code: Select all
# apt-get update
# apt-get install uboot-mkimage
Best, sakaki
Re: To create a custom install image for B1, B2 or B3?
On arch linux it is the uboot-tools package. I just installed it as root with:sakaki wrote:Hi,
Been a while since I used Debian, but I believe that's in the uboot-mkimage package, so:should fix it.Code: Select all
# apt-get update # apt-get install uboot-mkimage
Code: Select all
# pacman -S uboot-tools
Best, Pali
Re: To create a custom install image for B1, B2 or B3?
So I did followings sofar:
I suppose the gconfig is automatically loaded the excito_bubbatwo_defconfig, right?
Here I have a question. In the gconfig menu I may to choose between BusyBox or systemV. Because on Debian Jessie the systemd is the system and service manager, should I choose systemV instead of default choosed BusyBox?
Code: Select all
svn co https://github.com/Excito/buildroot/trunk
cd buildroot/trunk/
make excito_bubbatwo_defconfig
make gconfig
Here I have a question. In the gconfig menu I may to choose between BusyBox or systemV. Because on Debian Jessie the systemd is the system and service manager, should I choose systemV instead of default choosed BusyBox?
Best, Pali
Re: To create a custom install image for B1, B2 or B3?
Yespaulchany wrote:I suppose the gconfig is automatically loaded the excito_bubbatwo_defconfig, right?
You can't create a debian-based rescue image with buildroot. buildroot compiles from sources a specific small image intended for either rescue or embedded systems. You can add packages like parted if you wish in the menus but that's all. Generating a debian rescue system is a little bit more complicated. If you want a full blown system booting from USB use sakaki's gentoo or arch imagespaulchany wrote:Here I have a question. In the gconfig menu I may to choose between BusyBox or systemV. Because on Debian Jessie the systemd is the system and service manager, should I choose systemV instead of default choosed BusyBox?
Re: To create a custom install image for B1, B2 or B3?
OK, I leave default settings ( BusyBox among others ) and added in gconfig packages: parted, mc, less, nano . Finally I save the .config file and did:MouettE wrote:Yespaulchany wrote:I suppose the gconfig is automatically loaded the excito_bubbatwo_defconfig, right?
buildroot compiles from sources a specific small image intended for either rescue or embedded systems. You can add packages like parted if you wish in the menus but that's all.paulchany wrote:Here I have a question. In the gconfig menu I may to choose between BusyBox or systemV. Because on Debian Jessie the systemd is the system and service manager, should I choose systemV instead of default choosed BusyBox?
Code: Select all
make
In README.md there is an advice at bottom:8313E21.itb
rootfs.ext2
rootfs.ext2.gz
vmlinux
But on the original Bubba 2 install rescue USB disk there is more files in install/ directory:## Using
Place the install.itb file in the install directory of a fat-formatted usb disk and run the b3 with power button pushed.
so what should I do with generated files?payload/bubbaroot-120319-1139.tar.gz
8313E21.itb
bubba.cfg
install.itb
version
Should I use - in case of Bubba 2 - the generated 8313E21.itb file only in install directory of the usb disk:
install/8313E21.itb
but without following files:
?payload/bubbaroot-120319-1139.tar.gz
bubba.cfg
install.itb
version
Maybe I should use the generated files:
too?rootfs.ext2.gz
vmlinux
Best, Pali
Re: To create a custom install image for B1, B2 or B3?
On the original excito install/rescue key :
- 8313E21.itb : the bubba 2 rescue image
- bubba.cfg : configuration for the excito install script
- install.itb : the b3 rescue image (no use on a bubba2)
- version : text file containing the version of the excito install/rescue system
- payload/bubbaroot-120319-1139.tar.gz : the root of the full bubba 2 excito system
Re: To create a custom install image for B1, B2 or B3?
I've added u-boot-tools to the host utilities in buildroot configs so it won't need to be present on the compiling machine.paulchany wrote:What can I do to solve this problem?Code: Select all
>>> Executing post-image script board/excito/bubbatwo/post_image.sh Compiling bubbatwo.dts Preparing vmlinux.bin Compiling reloc_shim_itb.S Generating 8313E21.itb board/excito/bubbatwo/post_image.sh: sor: 21: mkimage: command not found