Which kernel mod needs to be loaded to get battrey support on cubietruck?

[pet]

I'm on 'cat /etc/os-release|grep ARMBIAN_PRETTY_NAME' = ARMBIAN_PRETTY_NAME="Armbian 24.11.1 bullseye"

[Werner]

Hi

 

Providing logs with

 

PASTE_SERVER_HOST=paste.armbian.de armbianmonitor -u

 

 helps with troubleshooting and significantly raises chances that issue gets addressed.

 

 

[Ryzer]

Hi Pet,

 

The axp209 modules should already be loaded by default, if not then they should at least be included in the kernel. This is the pmic onboard the cubietruck. Are you using a lipo or coin cell for rtc? You can check the current state by look at '/sys/bus/i2c/devices/i2c-x/x-0034/battery. Replace x with the i2c bus that the axp209 is assigned to. Normally this should be 0 but not always the case. For example this it what it looks like on my device:

[    2.973703] axp20x-i2c 1-0034: AXP20x variant AXP209 found
[    2.981221] input: axp20x-pek as /devices/platform/soc/1c2ac00.i2c/i2c-1/1-0034/axp20x-pek/input/input0
[    3.000378] axp20x-i2c 1-0034: Backup (RTC) battery charging is disabled
[    3.000562] axp20x-i2c 1-0034: AXP20X driver loaded
[    5.367992] axp20x-gpio axp20x-gpio: DMA mask not set
[    5.382424] axp20x-gpio axp20x-gpio: AXP209 pinctrl and GPIO driver loaded
[   21.124944] axp20x-adc axp20x-adc: DMA mask not set

 

best of luck

 

Ryzer

[pet]

Your answers are pretty much appreciated, and i would like to thank you for all the good work for the last 15 years @armbian.com. But, i would like to have a system that is more stable than (the last more or less two years) armbian on cubie* or friendlyarm SBCs just right now. I do need a stable OS which is able to serve pihole or other base network stuff constantly.
Something like
 

dpkg-deb (subprocess): decompressing archive '/tmp/apt-dpkg-install-mzEu51/7-linux-image-current-sunxi64_25.11.0-trunk.41_arm64.deb' (size=38908852) member 'data.tar': lzma error: compressed data is corrupt
dpkg-deb: error: <decompress> subprocess returned error exit status 2
dpkg: error processing archive /tmp/apt-dpkg-install-mzEu51/7-linux-image-current-sunxi64_25.11.0-trunk.41_arm64.deb (--unpack):
 cannot copy extracted data for './lib/modules/6.12.35-current-sunxi64/kernel/drivers/hwmon/w83781d.ko' to '/lib/modules/6.12.35-current-sunxi64/kernel/drivers/hwmon/w83781d.ko.dpkg-new': unexpected end of file or stream

...leading to a system that is not able to boot anymore (this is today's log of 'armbian-upgrade' on a NanoPI Neo+2) makes me think about asking you if i could provide some time to test your community builds and upgrades before they will be released to the public (-:

 Cheers

[eselarm]

5 hours ago, pet said:

I do need a stable OS which is able to serve pihole or other base network stuff constantly.

Armbian is a stable OS, but we don't know about what SD-card, power-supply etc you use with your Cubitruck and/or NanoPi Neo+2

The decompression error can simply mean corrupt file due to something wrong with HW. Or something could have gone wrong during download of the files that you or the system decompress. Also note you use a kernel from beta repo (25.11.0-trunk.41). 

 

I you want better control, create/build an image formatted as Btrfs, not Ext4. Then you can check where it went wrong. I have several NanoPi-NEOs, all use Btrfs. 2 run 24/7, the others not all the time and usually just get sudden power cut, but they start fine next time. I do in-place upgrade them since years. If something would go wrong, typically as the error you show, I go back to a previous Btrfs snapshot or/and backup from NAS. That is simply what you could do / have done. Maybe something went wrong with that sunxi64 kernel build on the Armbian infrastructure side, that can happen every now and then as it is beta. So Also then, protect your devices again such issues.

 

Also please don't post kernel upgrade errors in a topic about LiPo controller chip. OK for now, but annoying 

Edited Tuesday at 06:02 AM by eselarm

[Igor]

18 hours ago, pet said:

I do need a stable OS

 

OS is stable, errors you are experiencing are likely related to faulty HW component as @eselarm already exposed. And we would most likely notice such anomaly before it gets to you. There are thousands of users and this is the only report of this kind ...

 

18 hours ago, pet said:

community builds and upgrades before they will be released to the public (-:

 

Boards are going to the market at high rate, while users support remains more or less the same in past 10 years  

 

https://docs.armbian.com/User-Guide_Board-Support-Rules/
Community builds and their upgrades are untested as size of Armbian can only cope with a small selection of boards we call as "standard support", where we have volunteers behind. Community builds are on Debian / Arch images level, but packed with more features.
https://github.com/armbian/community?tab=readme-ov-file#purpose-of-this-repository

For those - Armbian provides build and hosting infrastructure, place to meet - this forum - while everything else is anyone's problem.