teknoid
-
Posts
38 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by teknoid
-
-
hmm, strange. After manually recreating the boot script it worked:
mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr
I did not take care of the output during upgrade, probably I missed a "No space left on device" or similar...
Anayway, solved...
-
I upgraded all in one step, uboot, dtb, ... Then switched back the kernel to 24.11.1 and it was working again
root@odroid25:~# dpkg -l |grep 25.2.2 ii armbian-bsp-cli-odroidc2-current 25.2.2 arm64 Armbian CLI BSP for board 'odroidc2' branch 'current' ii base-files 25.2.2-12.4+deb12u9-bookworm arm64 Armbian base system miscellaneous files ii linux-dtb-current-meson64 25.2.2 arm64 Armbian Linux current DTBs in /boot/dtb-6.12.17-current-meson64 ii linux-u-boot-odroidc2-current 25.2.2 arm64 Das U-Boot for odroidc2 root@odroid25:~# dpkg -l |grep 24.11.1 ii linux-image-current-meson64 24.11.1 arm64 Armbian Linux current kernel image 6.6.63-current-meson64
I'll do further investigations...
-
my C2 did not boot after upgrading from 6.6.63-current-meson64 to 6.12.17.
I also tested kernel 6.12.13 from debian minimal image, same problem:
Applying kernel provided DT fixup script (meson-fixup.scr) ## Executing script at 32000000 ## Loading init Ramdisk from Legacy Image at 13000000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 17076402 Bytes = 16.3 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 04080000 Booting using the fdt blob at 0x4080000 Loading Ramdisk to 7af01000, end 7bf4a0b2 ... OK Loading Device Tree to 000000007ae8e000, end 000000007af00fff ... OK "Synchronous Abort" handler, esr 0x96000004 elr: 000000000105d0b8 lr : 000000000104cdd0 (reloc) elr: 000000007dfb90b8 lr : 000000007dfa8dd0 x0 : fbbfe1e3d45df41f x1 : 000000007dfc0438 x2 : 0000000000000010 x3 : 000000007bfa3830 x4 : 0000000000000000 x5 : fbbfe1e3d45df41f x6 : 0000000001000000 x7 : 0000000000000000 x8 : 0000000000000007 x9 : 0000000000000000 x10: 00000000000001dc x11: 000000007bf4e34c x12: 00000000000000b0 x13: 000000007bf4e308 x14: 000000007ae8e000 x15: 0000000000000020 x16: 000000007df8f8a8 x17: 0000000000000000 x18: 000000007bf59dd0 x19: 000000007af4f040 x20: 000000007df5cb18 x21: 000000007dfc0438 x22: 0000000000001000 x23: 000000007bf613d0 x24: 000000007dfdd638 x25: 0000000001000000 x26: 0000000000000000 x27: 0000000001000000 x28: 0000000000001000 x29: 000000007bf4e300 Code: eb04005f 54000061 52800000 14000006 (386468a3) Resetting CPU ...
I have no idea. Can someone verify?
So for the moment I do not recommend updating to latest 6.12 kernel on Odroid C2.
-
did you check this?
-
-
no WiFi Adapter after fresh installation. usbcore.autosuspend=-1 fixes it:
___ _ _ _ ____ ____ / _ \ __| |_ __ ___ (_) __| | / ___|___ \ | | | |/ _` | '__/ _ \| |/ _` | | | __) | | |_| | (_| | | | (_) | | (_| | | |___ / __/ \___/ \__,_|_| \___/|_|\__,_| \____|_____| Welcome to Armbian 24.2.1 Bookworm with Linux 6.6.16-current-meson64 System load: 46% Up time: 0 min Memory usage: 7% of 1.82G IP: 192.168.25.252 CPU temp: 28°C Usage of /: 66% of 3.0G [ Menu-driven system configuration (beta): sudo apt update && sudo apt install armbian-config ] root@odroid:~# cat /boot/armbianEnv.txt verbosity=1 console=both overlay_prefix=meson rootdev=UUID=1cf10f1a-aa21-4ff0-875d-c59f57c87173 rootfstype=ext4 extraboardargs=fastboot noswap isolcpus=3 usbcore.autosuspend=-1 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:uroot@odroid:~# lsusb Bus 001 Device 007: ID 0bda:2838 Realtek Semiconductor Corp. RTL2838 DVB-T Bus 001 Device 006: ID 7392:7822 Edimax Technology Co., Ltd EW-7612UAn V2 802.11n Wireless Adapter [Realtek RTL8192CU] Bus 001 Device 005: ID 05e3:0610 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub -
root@odroid:~# mount |grep mmc /dev/mmcblk1p1 on / type ext4 (ro,noatime) /dev/mmcblk0p1 on /data type ext4 (ro,noatime) root@odroid:~# reboot Failed to connect to bus: No such file or directory root@odroid:~# client_loop: send disconnect: Broken pipe hje@prime:~$ hje@prime:~$ hje@prime:~$ hje@prime:~$ hje@prime:~$ ssh root@odroid ___ _ _ _ ____ ____ / _ \ __| |_ __ ___ (_) __| | / ___|___ \ | | | |/ _` | '__/ _ \| |/ _` | | | __) | | |_| | (_| | | | (_) | | (_| | | |___ / __/ \___/ \__,_|_| \___/|_|\__,_| \____|_____| Welcome to Armbian 24.2.1 Bookworm with Linux 6.6.16-current-meson64 System load: 46% Up time: 0 min Memory usage: 7% of 1.82G IP: 192.168.25.252 CPU temp: 28°C Usage of /: 66% of 3.0Gfresh installation on emmc, reboot works fine.
-
@Gunjan Gupta it's my board 😉
-
I just tested Armbian_23.11.1_Bananapipro_bookworm_current_6.1.63.img:
dd bs=8M if=Armbian_23.11.1_Bananapipro_bookworm_current_6.1.63.img of=/dev/sdc
Boots without any problems, opening ssh gives me:
Welcome to Armbian! Documentation: https://docs.armbian.com | Community support: https://forum.armbian.com IP address: 192.168.25.15 Create root password: ********* Repeat root password: ********* Support status: community support (looking for a dedicated maintainer) Choose default system command shell: 1) bash 2) zsh 1 Shell: BASH Creating a new user account. Press <Ctrl-C> to abort
-
Zitat
MMC: no card present
Probably it is a problem in uboot, it cannot detect any SD-Cards. Thats why uboot is searching for a TFTP server to boot from there. You can set up a TFTP Server and check if you can at least boot the kernel and see if your SD-Card is detected in the kernel.
-
@ickam, I just tested
Armbian_23.05.0-trunk_Odroidc2_bullseye_current_6.1.29_minimal.img
and could not reproduce your problem. After boot please wait 2-3 mins and carefully check your DHCP Server Log. For me it works as expected:
May 23 11:04:36 tron dnsmasq-dhcp[2938540]: DHCPDISCOVER(enp6s0f0) 00:1e:06:33:b5:0a May 23 11:04:36 tron dnsmasq-dhcp[2938540]: DHCPOFFER(enp6s0f0) 192.168.25.16 00:1e:06:33:b5:0a May 23 11:04:36 tron dnsmasq-dhcp[2938540]: DHCPREQUEST(enp6s0f0) 192.168.25.16 00:1e:06:33:b5:0a May 23 11:04:36 tron dnsmasq-dhcp[2938540]: abandoning lease to 00:1e:06:33:b5:0a of 192.168.25.16 May 23 11:04:36 tron dnsmasq-dhcp[2938540]: DHCPACK(enp6s0f0) 192.168.25.16 00:1e:06:33:b5:0a c2 Welcome to ARMBIAN! Documentation: https://docs.armbian.com | Community: https://forum.armbian.com IP address: 192.168.25.16 Create root password: ********* Repeat root password: ********* Shell: BASH Creating a new user account. Press <Ctrl-C> to abort
-
Nanopi Neo Plus 2 (H5)
linux-u-boot-nanopineoplus2-current_23.05.0-trunk--2022.07-Se092-P6b27-Ha9af-Vaada-B4b55_arm64.deb
linux-image-current-sunxi64_23.05.0-trunk--6.1.26-Sca1c-D4008-P8596-C1438Hfe66-HK01ba-Vc222-Ba98e_arm64.deb
OK, but distorted audio output over USB, I believe this came up since kernel 5.16+ and is still present in 6.x
Banana Pi Pro (A20)
linux-u-boot-bananapipro-current_23.05.0-trunk--2022.07-Se092-P6b27-H0429-Vaada-B4b55_armhf.deb
linux-image-current-sunxi_23.05.0-trunk--6.1.26-Sca1c-D4008-P8596-C596bHfe66-HK01ba-V014b-Ba98e_armhf.deb
OK
Odroid C2
linux-u-boot-odroidc2-current_23.05.0-trunk--2022.01-Sd637-P6c67-H7ff5-V603e-B4b55_arm64.deb
linux-image-current-meson64_23.05.0-trunk--6.1.27-Sca48-D4008-Pc5ba-C072bHfe66-HK01ba-Ve377-Ba98e_arm64.deb
OK
Armbian_23.05.0-trunk_Odroidc2_bullseye_current_6.1.29_minimal.img
full image test: OK
new build system is a very good improvement 👍
-
Not yet noticed - I don't have a serial console permanently connected to my board.
Looks like an error in the PMU https://linux-sunxi.org/AXP209 driver or it's interaction with the kernel during shutdown:
https://lkml.iu.edu/hypermail/linux/kernel/1909.2/04767.html
No idea how to solve this.
-
root@sabre18:~# cat /etc/default/cpufrequtils ENABLE=true MIN_SPEED=480000 MAX_SPEED=1104000 GOVERNOR=conservativecheck your max cpufreq setting. My neo plus 2 runs stable only at 1,1GHz
-
yes, mostly the nodes in the device tree are available but deactivated with status = "disabled";
And you simply can active them by saying status = "okay"; in an overlay. Furhermore you can override the standard values.
What you did in the past with module parameters you nowdays do it in the device tree.
check this: https://elinux.org/images/f/f9/Petazzoni-device-tree-dummies_0.pdf It helped me to get an overview what DTS is and how it interacts with the linux kernel drivers. Oh yes, its not easy to understand. It will take some time (at least for me it took years) but playing around is good for practise and step by step you will get familiar with it.
Next version 22.05 will have the regulators enabled by default so you do not need the overlay anymore.
-
http://tron.dyn.cc/sun7i-bananpro-ahci.dts
download my test user overlay, copy it to your system and activate it (as root) with:
armbian-add-overlay sun7i-bananpro-ahci.dtsthis should work on any kernel below 5.17
after release of 22.05 you need to remove it from /boot/overlay-user/
-
solved with https://github.com/armbian/build/pull/3613
thanks @the-going
-
[...found another thread]
followup here:
-
followup here:
-
yes, these patches will go into official armbian images and will be available with next release 22.05 I think.
Thanks @Igor for reactivating the state to supported. Now the official downloads are back on armbian page: https://redirect.armbian.com/bananapipro/Bullseye_current
So I recommend you to first use the official image to get proper kernel and userland environment on your board. Later you can upgrade the kernel in usual way by "apt get update / upgrade" or aptitude.
If you want to debug a non starting board you need to connect the serial console via USB to UART and watch it e.g. via minicom. And yes a native Linux machine is highly recommended 😉
-
Hi @Igor perfect, thanks.
Next step is to upgarde the WIFI firmware to 5.90.244:
[ 13.975858] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43362/1 wl0: May 16 2018 23:42:49 version 5.90.244 FWID 01-0I loaded it from kernel git here: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/brcm?id=d9430acf46774d75fa269a667b7b4598d60aa353
It magically diasppeared in the current kernel git repository, but I found it in a commit from 2018.
I will test it for the next few days and then upload to armbian firmware repo.
-
I know, I already hired for nanopi neo plus2 🙂
-
-
followup here:
[C2] kernel 6.12.x broken
in Odroid C2
Posted
Now I've got it: It does not boot from emmc module if a sdcard is present!