jscax

So I went out of the armbian world I suppose... how to get back?

I don't know how I ended up with Lunar installed on my OPI0. I did a do-release-upgrade because it was suggesting to run this command to upgrade to the next version. I launched it and now I have Lunar installed: cat /etc/issue Armbian 23.8.1 lunar \l uname -r 6.1.63-current-sunxi Now logging in is saying this: Your Ubuntu release is not supported anymore. For upgrade information, please visit: http://www.ubuntu.com/releaseendoflife New release '23.10' available. Run 'do-release-upgrade' to upgrade to it. I'm sorry I'm a little bit out of the know of the Armbian flow and sometimes I'm surprised while maintaining my armbian machine updated. Am I on a wrong path? thank you

I was using the orange pi naming convention https://drive.google.com/drive/folders/1ohxfoxWJ0sv8yEHbrXL1Bu2RkBhuCMup they call "desktop" and "server" version, for "server" being the headless one. I'm using it headless (server ) for 3d printing with octoprint and ... wifi

is there any hope for this? this seems a very promising board that can be used both server only or cli with the micro hdmi output. I have one and it's super incredibly power efficient, 1-2 watt, quite cool. Without wifi is impossible to use it. Any way to help?

red led is ok, you have to wait 3-5 solid minutes. ethernet cable connected, check on your router which ip is assigned. ssh root 1234

Hello, I have OPI0 with Ubuntu 20.04.1 LTS with Linux 5.8.6-sunxi and I would like to set 240 MHz as minimum frequency. cpufreq-info shows that available steps starts at 480 MHz but on older kernel 240 MHz and 120 MHz were available too. I also tried to "force" 240 and 120 by editing /etc/default/cpufrequtils but no go. Lower reachable frequency is 480 MHz and what I see are a bit CPU higher temperatures. cpufreq-info cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to cpufreq@vger.kernel.org, please. analyzing CPU 0: driver: cpufreq-dt CPUs which run at the same hardware frequency: 0 1 2 3 CPUs which need to have their frequency coordinated by software: 0 1 2 3 maximum transition latency: 5.44 ms. hardware limits: 480 MHz - 1.01 GHz available frequency steps: 480 MHz, 648 MHz, 816 MHz, 960 MHz, 1.01 GHz available cpufreq governors: conservative, userspace, powersave, ondemand, performance, schedutil current policy: frequency should be within 480 MHz and 960 MHz. The governor "conservative" may decide which speed to use within this range. current CPU frequency is 480 MHz (asserted by call to hardware). cpufreq stats: 480 MHz:98.26%, 648 MHz:1.28%, 816 MHz:0.12%, 960 MHz:0.35%, 1.01 GHz:0.01% (12233) analyzing CPU 1: driver: cpufreq-dt CPUs which run at the same hardware frequency: 0 1 2 3 CPUs which need to have their frequency coordinated by software: 0 1 2 3 maximum transition latency: 5.44 ms. hardware limits: 480 MHz - 1.01 GHz available frequency steps: 480 MHz, 648 MHz, 816 MHz, 960 MHz, 1.01 GHz available cpufreq governors: conservative, userspace, powersave, ondemand, performance, schedutil current policy: frequency should be within 480 MHz and 960 MHz. The governor "conservative" may decide which speed to use within this range. current CPU frequency is 480 MHz (asserted by call to hardware). cpufreq stats: 480 MHz:98.26%, 648 MHz:1.28%, 816 MHz:0.12%, 960 MHz:0.35%, 1.01 GHz:0.01% (12233) analyzing CPU 2: driver: cpufreq-dt CPUs which run at the same hardware frequency: 0 1 2 3 CPUs which need to have their frequency coordinated by software: 0 1 2 3 maximum transition latency: 5.44 ms. hardware limits: 480 MHz - 1.01 GHz available frequency steps: 480 MHz, 648 MHz, 816 MHz, 960 MHz, 1.01 GHz available cpufreq governors: conservative, userspace, powersave, ondemand, performance, schedutil current policy: frequency should be within 480 MHz and 960 MHz. The governor "conservative" may decide which speed to use within this range. current CPU frequency is 480 MHz (asserted by call to hardware). cpufreq stats: 480 MHz:98.26%, 648 MHz:1.28%, 816 MHz:0.12%, 960 MHz:0.35%, 1.01 GHz:0.01% (12233) analyzing CPU 3: driver: cpufreq-dt CPUs which run at the same hardware frequency: 0 1 2 3 CPUs which need to have their frequency coordinated by software: 0 1 2 3 maximum transition latency: 5.44 ms. hardware limits: 480 MHz - 1.01 GHz available frequency steps: 480 MHz, 648 MHz, 816 MHz, 960 MHz, 1.01 GHz available cpufreq governors: conservative, userspace, powersave, ondemand, performance, schedutil current policy: frequency should be within 480 MHz and 960 MHz. The governor "conservative" may decide which speed to use within this range. current CPU frequency is 480 MHz (asserted by call to hardware). cpufreq stats: 480 MHz:98.26%, 648 MHz:1.28%, 816 MHz:0.12%, 960 MHz:0.35%, 1.01 GHz:0.01% (12233) thank you

Did you find the way to do that?

yes, it's a UPD6121 and I gave up about making it work with different protocol than NEC. I bought a double led with transistor ( https://www.aliexpress.com/item/Free-Shipping-electronic-building-blocks-Two-way-infrared-transmitter-module-IR-Transmitter-for-arduino/1972945414.html ) which allows me to just turn on/off the LED by changing high/low PIN and I succeded transmitting what I need. Note again: you need a double led with transistor to success I went for a very low level solution, similar to the one posted by nopnop2002 here above. I just save ON/OFF pulse with timing and I then just replicate the commands without encoding or making any logic.

Pardon my huge ignorance. I think I'm not understanding the whole context Armbian vs OrangePI. OrangePI is selling PiZero Plus with bluetooth hardware built-in but is not delivering the driver to make it works, correct? This: https://github.com/orangepi-xunlong/OrangePiH5_kernel/tree/master/drivers/bluetooth is not something useful, correct? I'd like to have BT working. I bought OPI0+ for BT feature which I was missing on OPI0 and I did not consider that it shouldn't work. Can you please point me the direction to have BT working on OPI0+?

I would use it for a temperature + humidity sensor

I can't make bluetooth work on my OPi0+ Is it a known bug? Am I doing it wrong? thank you

So an update came into apt upgrade and it updated max freq config file too (/etc/default/cpufrequtils). Welcome to ARMBIAN 5.53.180722 nightly Ubuntu 16.04.5 LTS 4.17.9-sunxi After the update max frequency was restored at the original default value MAX_SPEED 1200MHz and I was barely able to boot again my OPI0. I went through several boot attempts, then after leaving it turned off for 30 minutes I was able to boot again and change back the MAX_SPEED to 960MHz. From my experience 1200MHz frequency is the offending cause of the random OPI0 freezes. And I had no freezes since I changed the MAX_SPEED @960MHz. Do you know if there's some undervolting going on? Maybe there's a wrong value @1200MHz? Moreover: after the update now the OPI0 is scaling frequency (before it was locked at max freq). Is it possible to link temperature with freq scaling? If temp > 50 °C ==> max freq = xx

ok now limiting CPU @ 960MHz Do you have a link for the DRAM thing? I think I'm a little bit out of the know... where can I keep me updated with armbian news? I think there's a lot I'm missing thank you

it's not completely impossible to spot something on logs written before a kernel panic, that's my experience, but this time there's no trace. log2ram should not be my friend in this case. how does it work? it logs in ram, then a kernel panic occurs and puff... logs are gone because no one wrote them on sd? On the power supply side: I'm not using micro usb. I have a 15W PSU (and I'm using like 3 watts) connected with GPIO pins directely. I'll have a chance to use another power supply in a few days and will see if that's the issue.

Sadly it crashed again after like 16 hours of uptime with the new kernel. In my case it must be on 24h/7d Attaching the armbianmonitor -u file I think it has something to do with logrotation/cron/log2ram something But I can't spot anything from logs. Now it crashed at 12PM and had to force reboot, which succeded at 12:31 thank you armbianlog.txt