-
Posts
48 -
Joined
-
Last visited
Other groups
Contributor/Maintainer
Profile Information
-
Gender
Male
-
Location
Latvia
Contact Methods
-
Matrix
shtripok@gmail.com
-
Github
iav
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
-
I did kind of manual bisect by commits to config/boards/odroidm1.conf U-Boot 2024.04-armbian (Jan 29 2025 - 02:13:41 +0000) commit 3215bf9f3699c2ee4bc741efe82065315e4ff46f linux-u-boot-odroidm1-edge_24.8.0-trunk_arm64__2024.04-S2504-P3b44-Haddb-V73be-B4f92-R448a.deb is GOOD, U-Boot 2024.07-armbian-2024.07-S3f77-P7e9c-Hfb3e-V8f4f-Bb66d-R448a (Jan 29 2025 - 02:30:21 +0000) commit 268c2e85960978c90025bc18cf7d5f8e5cfbdab6 linux-u-boot-odroidm1-edge_24.8.0-trunk_arm64__2024.07-S3f77-P7e9c-Hfb3e-V8f4f-Bb66d-R448a.deb is BAD then I fix my Odroid M1 by doing sudo apt install ./linux-u-boot-odroidm1-edge_24.8.0-trunk_arm64__2024.04-S2504-P3b44-Haddb-V73be-B4f92-R448a.deb then armbian-install → Install/Update the bootloader on MTD Flash
-
yes. at least it works for me now.
-
In current thread that means "Armbian was not available for Helios64 hardware for a time. But then it fixed, and anyone can make sdcard with fresh armbian system for Helios64 device". u-boot — software, use by armbian on first seconds after device powered on.
-
Then, thanks to Prahal, bootable images for Helios64 can be build again.
-
I think moving to media group will be too much for NAS device.
-
I will run build and boot result image on Helios64 hardware in case somebody fix error.
-
The boot process and various devices
iav replied to ManoftheSea's topic in Advanced users - Development
yes -
The boot process and various devices
iav replied to ManoftheSea's topic in Advanced users - Development
serial console works as usual. grub menu selectable, in edit mode text can be edited. with 6.0.1 system cooler runs on full speed, armbian-config not provide processor frequences to choose min and max. -
The boot process and various devices
iav replied to ManoftheSea's topic in Advanced users - Development
debian version — console jammy.0.txt diagnostic http://ix.io/4cXz all the same. -
The boot process and various devices
iav replied to ManoftheSea's topic in Advanced users - Development
I run headless, with serial console. jammy.0.txt `reboot` does reboot, `poweroff` not power off after shutdown. boot takes a lot of time, you can see by timestamps. `armbian-config` allows me to set scheduler to schedutil and set min and max frequences. System cooler was off until I setup 7zip and run benchmark `7zz b`. then system cooler turns on until test was completed, then turns off. system diagnostics http://ix.io/4cXm -
The boot process and various devices
iav replied to ManoftheSea's topic in Advanced users - Development
shutdown and reboot commands stays system shutted down but powered on. -
The boot process and various devices
iav replied to ManoftheSea's topic in Advanced users - Development
Sorry, there nothing to connect to HDMI. And there no login prompt on serial console. But yes, network scan found an IP obtained with DHCP, then I successful login into armbian first login wizard. System cooler works on full speed all the time. -
The boot process and various devices
iav replied to ManoftheSea's topic in Advanced users - Development
there boot log on Helios64, image from yandex disk screen.txt -
I go by tree from ytour post /sys/devices/platform/p6-fan/hwmon/hwmon6 ans see no hwmon in /sys/devices/platform/p6-fan(begin of lines removed): root@helios64:/sys/devices/platform/p6-fan# ls -l driver_override modalias of_node -> ../../../firmware/devicetree/base/p6-fan power subsystem -> ../../../bus/platform supplier:platform:ff420010.pwm -> ../../virtual/devlink/platform:ff420010.pwm--platform:p6-fan uevent waiting_for_supplier I build this kernel with armbian default kernel config. How can we have different trees in /sys on same hardware?
-
Fresh build edge bullseye image with kernel Linux helios 5.18.0-rockchip64 #trunk SMP PREEMPT Sun May 29 20:19:27 EEST 2022 aarch64 GNU/Linux fancontrol not work, because there no /dev/fan devices How to get fancontrol back to work?