15 15
Igor

read first How to build my own image or kernel?

Recommended Posts

1 minute ago, mutluit said:

now it no longer shows the menu anymore, instead it downloads old multiple toolschains

Menu appears AFTER the toolchains downloads ...

 

Share this post


Link to post
Share on other sites

Ah, ok, then I'll let it download it...

The confusion comes because it behaved differently in previous attempts (the menu came immediately).

Good to know, thank you very much for the help.

 

 

Share this post


Link to post
Share on other sites

I still don't understand why it downloads so many toolchains onto my disk, I've just one A20 board which only needs the recent eabihf toolchain. Or does a different logic apply here?

[ .... ] Downloading [ gcc-linaro-arm-linux-gnueabihf-4.8-2014.04_linux ]
[ .... ] Downloading [ gcc-linaro-4.9.4-2017.01-x86_64_aarch64-linux-gnu ]
[ .... ] Downloading [ gcc-linaro-4.9.4-2017.01-x86_64_arm-linux-gnueabi ]
[ .... ] Downloading [ gcc-linaro-4.9.4-2017.01-x86_64_arm-linux-gnueabihf ]
[ .... ] Downloading [ gcc-linaro-5.5.0-2017.10-x86_64_aarch64-linux-gnu ]
[ .... ] Downloading [ gcc-linaro-5.5.0-2017.10-x86_64_arm-linux-gnueabi ]
...
 

Share this post


Link to post
Share on other sites
16 minutes ago, mutluit said:

why it downloads so many toolchains onto my disk

... to make sure they are available/installed for whatever boards/SoC that will be selected later ...

Share this post


Link to post
Share on other sites
8 minutes ago, martinayotte said:

... to make sure they are available/installed for whatever boards/SoC that will be selected later ...

 

Hmm.... I guess over 99% of the users have just one board to work on at a time...

This could have been solved better, IMO. Ie. kind of "on-demand" download etc. ie download only if really needed according to the selection made in the menu...

 

There are 46 toolchains. No, thx, I'm not going to download that much stuff onto my machine. This is IMO insane.

 

 

 

Share this post


Link to post
Share on other sites
On 3/11/2019 at 11:30 PM, mutluit said:

This could have been solved better, IMO. Ie. kind of "on-demand" download etc. ie download only if really needed according to the selection made in the menu...


Agree. Many things are not done ideally, but they work!

Welcome to study how things were made. Keep in mind that the overall goal of this tool-chain is to gain control over all boards and also some of the functions are implemented to serve us for making a distribution, to build images in parallel, etc. Crippling those feature or making expensive changes in favour to save some time/data usage for end user (at first build only in this case) is not a good idea.

 

If you have a desire for changes and you think we all will benefit from them, propose with a PR.

 

On 3/11/2019 at 11:30 PM, mutluit said:

There are 46 toolchains. No, thx, I'm not going to download that much stuff onto my machine. This is IMO insane.


Armbian only needs 15 of them to compile everything and they use 10G of space. It is possible to reduce this number by adjusting old dirty sources to meet modern compile requirements but this is even more stupid and insane wasteful.

Share this post


Link to post
Share on other sites
On 3/11/2019 at 6:30 PM, mutluit said:

There are 46 toolchains. No, thx, I'm not going to download that much stuff onto my machine. This is IMO insane.

 

With all due respect, if you don't need to compile your own kernel/distribution then don't! But if you actually do need to, what is your alternative? Are you going to fork Armbian, because you can!

Share this post


Link to post
Share on other sites

I need to run 3rd party armhf packages on Nanopi Fire 3. I cannot make custom 64bit packages because I cannot get sourcecode for them.

Adding armhf architecture to running 64bit Armbian failed and I found information it is not so straightforward like on x86 vs amd64 architecture. 

 

While manufacturer FriendlyElec provides both aarch64 and armhf images, Armbian does not.

Any ideas howto build 32bit image via Armbian toolchain?

Share this post


Link to post
Share on other sites

Please help me how to install the mainline kernel..
I have found instructions but all i have found is not complete for armbian & rockpro64.
I have downloaded 5.2.9 from kernel.org and compiled with rockpro64 armbian 4.4.18X .config
after that make modules_install / make headers_install / update-initramfs -c -k 5.2.9
and copy dtb-5.2.9-rockchip64 vmlinuz-5.2.9-rockchip64 to /boot
and make symlinks
/boot/dtb -> /boot/dtb-5.2.9-rockchip64
/boot/Image -> vmlinuz-5.2.9-rockchip64

System does not boot
I don't know what else to do
The problem 99% is at uboot.

The uboot is the most confusing thing that i have meet in linux i had no prob years with lilo and after grub but this uboot i cannot understand it how it is work...
PLEASE HELP ME

Share this post


Link to post
Share on other sites
17 hours ago, rocksa said:

copy dtb-5.2.9-rockchip64 vmlinuz-5.2.9-rockchip64 to /boot

You also need to copy kernel modules in /lib/modules/5.2.9-rockchip64 ...

Share this post


Link to post
Share on other sites

i have done copy the kernel modules with make modules_install .

The problem is the bootloader.

Can you help me with that ?

Share this post


Link to post
Share on other sites
On 8/20/2019 at 9:53 PM, rocksa said:

I have downloaded 5.2.9 from kernel.org and compiled with rockpro64 armbian 4.4.18X .config

 

This will almost certainly fail. Its not that simple.


Sometimes you also need correct compiler (version), you might need to adjust u-boot environment or boot scripts if you haven't use ramdisk for booting or pack kernel differently ... who knows. You need to debug your creation.

If you are new to this ARM/embedded world, build a kernel with our tools. Forget about previous x86 experiences for some time ... Build a kernel that we made available to build. Usually those are the only working variants! One old and one new, which is also usually still in development and can break. This is the case for RK3399. 

 

4 hours ago, rocksa said:

Can you help me with that ?

 

When you step out from predicted and well tested environment you are on your own. For free generic support there are slim chances. We already officially don't support things you are asking for (development for end user) since this type of support is extremely wasteful / expensive and if we want to clear out and help all before you ... waiting time would be measured in years. We simply have no resources and "you" don't pay to develop that kind of support.

 

Step back, learn a bit and then try looking for borders.

Share this post


Link to post
Share on other sites

I don't want help with .config on how to compile/install kernel only with booting iam sure 99% that the kernel i have compiled works.

In x86 lilo & grub was ok how to boot works on rockpro64 with u-boot ?

Share this post


Link to post
Share on other sites

Grab our build tools, add a parameter EXPERT="yes" and you will be able to build (install-able .deb package) DEV 5.3.y. Probably working, the best modern kernel for RK3399 which exists but still under development and without support.

 

5 hours ago, rocksa said:

I don't want help with .config on how to compile/install kernel only with

 

... more critical and complicated stuff :) 

Share this post


Link to post
Share on other sites

I got a .config from manjaro arm which has stock 5.2 kernel for rockpro64 and works so .config is correct.

If i copy also dtbs & System.map from manjaro is ok ?

In armbian how you can change the boot kernel ?

Only changing symlinks at /boot Image uInitrd dtb and rebuilding boot.scr is enough to boot from new kernel ?

Share this post


Link to post
Share on other sites

I have installed the nightly version of armbian that comes with stock 5.3rc4.

Can in this version compile my own kernel 5.3 ?

Only changing symlinks n /boot is enough for u-boot to work ?

Share this post


Link to post
Share on other sites
9 hours ago, rocksa said:

Can in this version compile my own kernel 5.3 ?


Our 5.3.y DEV should work, but its bleeding edge. It will work better then Manjaro, but not all features works o.k. yet.
 

Just install .deb files from output/deb ... you need packages with image and dtb in the name at minimum. Installing u-boot is optional and if - after you install the package, you need to flash u-boot from armbian-config. This is a safety feature.

 

BTW: check https://www.youtube.com/watch?v=0K0vtUg_cgo

 

 

 

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
15 15