prahal
commented
1 year ago Uninstalled the above package and installed using dpkg -i Here is the new serial console output - https://pastebin.mozilla.org/YjfnuShC It seems like ddrbin did not update ? Indeed as Igor hinted the package only put the u-boot files in a folder. You could do the u-boot upgrade via armbian-install
then choose5 'Install/Update the bootloader on SD/eMMC'`.
But please keep in mind that if you do not run your OS from emmc and want to install to EMMC this will not do the job.
That is armbian-install write the bootloader to:
lsblk -ndo pkname $root_partition "$(sudo blkid | tr -d '":' | grep "$(sed -e 's/^.*root=//' -e 's/ .*$//' < /proc/cmdline)" | awk '{print $1}')"
which points to the SD if you boot to the SD, not the emmc (and the helios64 looks for u-boot on the emmc first, except if you put a jumper to disable the emmc on the helios64 board).
You can run this command to find which it will install to, or read the "root=" value in /proc/cmdline and compare it to the blkid output.
To manually install to the emmc when you boot on the SD.
The linux-u-boot-helios64-edge install a script for armbian-install to know how to install u-boot on the helios64 /usr/lib/u-boot/platform_install.sh and the u-boot files to write to the board at /usr/lib/linux-u-boot-edge-helios64_23.08.0-trunk_arm64 .
For the case where this folder contains u-boot.itb the platform_install.sh script tells to execute:
dd if=$1/idbloader.img of=$2 seek=64 conv=notrunc status=none;
dd if=$1/u-boot.itb of=$2 seek=16384 conv=notrunc status=none;where $1 is the folder containing the bootloader binaries, here /usr/lib/linux-u-boot-edge-helios64_23.08.0-trunk_arm64
and $2 is the device file for the storage you want to write u-boot to, here on linux 6.3 emmc is /dev/mmcblk1 (you can check with lsblk -f).
For one if your u-boot upgrade leaves you with a broken u-boot on the emmc, then you add the jumper on the board, halt u-boot, remove the jumper, rescan the mmc device with mmc rescan, then enter the boot command in u-boot and finally from the linux install on the SD, write manually the u-boot to the emmc.
Ran
for i in $(seq 1 100);do python3 -c "import pkg_resources" || break;done-> could not repro issue.
Could you try running this command at least six times before upgrading the u-boot? This is to sort out if your old rockchip64 DDR blob is really also broken with regards to setting up the DDR parameters. That is if you cannot reproduce then there might be other issues (though unlikely). Though now that we know which version of this blob you had on could reproduce it by tweaking armbian build to install it with this blob. Mind I will be away a few weeks very soon, so I won't be able to test such an install for quite a while.
blmhemu
snakekick
jmue
d3473r
bcecchinato
What happened?
Getting free() invalid pointer issue when installing / using python3. Could be dpkg issue as well ! Board: Helios64 (I know, I know CSC) Chipset: RK3399
When I did
sudo apt update && sudo apt upgrade, it happened and hence I tried to reinstall. This issue occurs when trying to manage it with ansible as well. I think something might be wrong with the latest python.Branch
master (main development branch)
On which host OS are you observing this problem?
Jammy
Relevant log output
Code of Conduct