<?xml version="1.0"?>
<rss version="2.0"><channel><title>Odroid C1 Latest Topics</title><link>https://testforum.armbian.com/forum/273-odroid-c1/</link><description>Odroid C1 Latest Topics</description><language>en</language><item><title>How to use LIRC to transmit signals</title><link>https://testforum.armbian.com/topic/62191-how-to-use-lirc-to-transmit-signals/</link><description><![CDATA[<p>
	I am currently using a completely outdated system on my Odroid-C1, specifically Ubuntu 16.04.7 <abbr title="Long term support">LTS</abbr> and I am able to transmit signals without issues using lirc 0.9.0.
</p>

<p>
	Without making any special changes to the /etc/lirc/hardware.conf file and using the following configuration:
</p>

<p>
	<br />
	#Chosen Remote Control<br />
	REMOTE="None"<br />
	REMOTE_MODULES=""<br />
	REMOTE_DRIVER=""<br />
	REMOTE_DEVICE=""<br />
	REMOTE_SOCKET=""<br />
	REMOTE_LIRCD_CONF=""<br />
	REMOTE_LIRCD_ARGS=""
</p>

<p>
	#Chosen IR Transmitter<br />
	TRANSMITTER="odroid blaster"<br />
	TRANSMITTER_MODULES="lirc_odroid lirc_dev"<br />
	TRANSMITTER_DRIVER=""<br />
	TRANSMITTER_DEVICE="/dev/lirc0"<br />
	TRANSMITTER_SOCKET=""<br />
	TRANSMITTER_LIRCD_CONF=""<br />
	TRANSMITTER_LIRCD_ARGS=""
</p>

<p>
	#Disable kernel support.<br />
	#Typically, lirc will disable in-kernel support for ir devices in order to<br />
	#handle them internally.  Set to false to prevent lirc from disabling this<br />
	#in-kernel support.<br />
	#DISABLE_KERNEL_SUPPORT="true"
</p>

<p>
	#Enable lircd<br />
	START_LIRCD="true"
</p>

<p>
	#Don't start lircmd even if there seems to be a good config file<br />
	#START_LIRCMD="false"
</p>

<p>
	#Try to load appropriate kernel modules<br />
	LOAD_MODULES="true"
</p>

<p>
	# Default configuration files for your hardware if any<br />
	LIRCMD_CONF=""
</p>

<p>
	#Forcing noninteractive reconfiguration<br />
	#If lirc is to be reconfigured by an external application<br />
	#that doesn't have a debconf frontend available, the noninteractive<br />
	#frontend can be invoked and set to parse REMOTE and TRANSMITTER<br />
	#It will then populate all other variables without any user input<br />
	#If you would like to configure lirc via standard methods, be sure<br />
	#to leave this set to "false"<br />
	FORCE_NONINTERACTIVE_RECONFIGURATION="false"<br />
	START_LIRCMD=""<br />
	 
</p>

<p>
	With an LED connected to physical pins 2 and 7, I can transmit signals using `irsend SEND_ONCE LG KEY_POWER`.
</p>

<p>
	 
</p>

<p>
	After a long time—and finding your website—I decided to try upgrading the system to Ubuntu 26.04... but I’m running into trouble: I can't use the LIRC-based transmitter the way I used to. I’ve spent two afternoons testing and re-testing, but I just can't get it to work like it did on the older version. Is there a way to make it work?<br />
	<br />
	Many thanks for everything.
</p>
]]></description><guid isPermaLink="false">62191</guid><pubDate>Sun, 20 Sep 2026 17:34:21 +0000</pubDate></item><item><title>Armbian on the Odroid C1 sends some rubbish over HDMI.</title><link>https://testforum.armbian.com/topic/54355-armbian-on-the-odroid-c1-sends-some-rubbish-over-hdmi/</link><description><![CDATA[<p>
	Hi.
</p>

<p>
	<a class="ipsAttachLink ipsAttachLink_image" href="https://testforum.armbian.com/uploads/monthly_2025_08/image.png.d1eaf60b65fde68c8fca316a3951580a.png" data-fileid="14876" data-fileext="png" rel="">Looking for help. I have uploaded Armbian v6.12 Desktop Ubuntu to a card and run on my device. You can see in the screenshot (video of the boot here: </a><a href="https://drive.google.com/file/d/1_1dm1rP33tbYISPUsta7nZV1eKPy3Plq/view?usp=drive_link" rel="external nofollow">https://drive.google.com/file/d/1_1dm1rP33tbYISPUsta7nZV1eKPy3Plq/view?usp=drive_link</a><a class="ipsAttachLink ipsAttachLink_image" href="https://testforum.armbian.com/uploads/monthly_2025_08/image.png.d1eaf60b65fde68c8fca316a3951580a.png" data-fileid="14876" data-fileext="png" rel="">) that some rubbish is displayed. I would also add that the device is sending a signal that is only displayed by the TV. No other monitor in the house is able to display anything that is sent from the device. This is even stranger, as when I upload the old ubuntu 18.04 to the same card, the device connected under any display displays my desktop. Any suggestions or suggestions? Maybe an older version? I want to make myself a RetroPi from the device, but that requires something newer than the old ubuntu.<br>
	<img class="ipsImage ipsImage_thumbnailed" data-fileid="14876" width="1000" alt="image.thumb.png.e68c968de8f5af69c5c45e8e185c0ebd.png" src="https://testforum.armbian.com/uploads/monthly_2025_08/image.thumb.png.e68c968de8f5af69c5c45e8e185c0ebd.png" loading="lazy" height="620"></a>
</p>

<p>
	 
</p>

<p>
	 
</p>

<p>
	 
</p>
]]></description><guid isPermaLink="false">54355</guid><pubDate>Wed, 06 Aug 2025 18:38:10 +0000</pubDate></item><item><title>rcu_sched detected stalls on CPU</title><link>https://testforum.armbian.com/topic/55606-rcu_sched-detected-stalls-on-cpu/</link><description><![CDATA[<p>
	Hi,<br />
	<br />
	Recently I reinstalled system on my Odroid C1+ from older Ubuntu with original 3.10.107 to newest Armbian with kernel 6.12.44. <br />
	Generally it works quite well  but I see a lots of stalls detection warnings in logs:
</p>

<p>
	 
</p>

<pre class="ipsCode">Thu Oct  9 02:00:26 2025] rcu: INFO: rcu_sched self-detected stall on CPU
[Thu Oct  9 02:00:26 2025] rcu: 	0-....: (1799 ticks this GP) idle=a184/1/0x40000004 softirq=1089909/1089910 fqs=488
[Thu Oct  9 02:00:26 2025] rcu: 	(t=2100 jiffies g=2037329 q=10 ncpus=4)
[Thu Oct  9 02:00:26 2025] CPU: 0 UID: 0 PID: 7987 Comm: kworker/0:1 Not tainted 6.12.44-current-meson #2
[Thu Oct  9 02:00:26 2025] Hardware name: Amlogic Meson platform
[Thu Oct  9 02:00:26 2025] Workqueue: events dbs_work_handler
[Thu Oct  9 02:00:26 2025] PC is at __slab_free+0x0/0x314
[Thu Oct  9 02:00:26 2025] LR is at kmem_cache_free+0x120/0x378
[Thu Oct  9 02:00:26 2025] pc : [&lt;c056fd04&gt;]    lr : [&lt;c05716fc&gt;]    psr: 800f0113
[Thu Oct  9 02:00:26 2025] sp : f0801b58  ip : ef6a6398  fp : c2387fc0
[Thu Oct  9 02:00:26 2025] r10: c5844380  r9 : c2352740  r8 : 000e6e80
[Thu Oct  9 02:00:26 2025] r7 : c11dd1d4  r6 : c66a0000  r5 : ef7dfe80  r4 : c280ef80
[Thu Oct  9 02:00:26 2025] r3 : c66a0000  r2 : c66a0000  r1 : ef7dfe80  r0 : c280ef80
[Thu Oct  9 02:00:26 2025] Flags: Nzcv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment none
[Thu Oct  9 02:00:26 2025] Control: 10c5387d  Table: 062a404a  DAC: 00000051
[Thu Oct  9 02:00:26 2025] Call trace: 
[Thu Oct  9 02:00:26 2025]  __slab_free from kmem_cache_free+0x120/0x378
[Thu Oct  9 02:00:26 2025]  kmem_cache_free from tcp_rcv_established+0x428/0x6cc
[Thu Oct  9 02:00:26 2025]  tcp_rcv_established from tcp_v4_do_rcv+0x180/0x284
[Thu Oct  9 02:00:26 2025]  tcp_v4_do_rcv from tcp_v4_rcv+0xbc0/0x1068
[Thu Oct  9 02:00:26 2025]  tcp_v4_rcv from ip_protocol_deliver_rcu+0x30/0x27c
[Thu Oct  9 02:00:26 2025]  ip_protocol_deliver_rcu from ip_local_deliver_finish+0x7c/0x98
[Thu Oct  9 02:00:26 2025]  ip_local_deliver_finish from ip_sublist_rcv_finish+0x3c/0x50
[Thu Oct  9 02:00:26 2025]  ip_sublist_rcv_finish from ip_sublist_rcv+0x174/0x1e4
[Thu Oct  9 02:00:26 2025]  ip_sublist_rcv from ip_list_rcv+0xe8/0x114
[Thu Oct  9 02:00:26 2025]  ip_list_rcv from __netif_receive_skb_list_core+0x188/0x1f4
[Thu Oct  9 02:00:26 2025]  __netif_receive_skb_list_core from netif_receive_skb_list_internal+0x180/0x288
[Thu Oct  9 02:00:26 2025]  netif_receive_skb_list_internal from napi_gro_receive+0x15c/0x264
[Thu Oct  9 02:00:26 2025]  napi_gro_receive from stmmac_napi_poll_rx+0x9f8/0xfa0
[Thu Oct  9 02:00:26 2025]  stmmac_napi_poll_rx from __napi_poll.constprop.0+0x2c/0x1c8
[Thu Oct  9 02:00:26 2025]  __napi_poll.constprop.0 from net_rx_action+0x328/0x3a4
[Thu Oct  9 02:00:26 2025]  net_rx_action from handle_softirqs+0x114/0x338
[Thu Oct  9 02:00:26 2025]  handle_softirqs from irq_exit+0x8c/0xbc
[Thu Oct  9 02:00:26 2025]  irq_exit from call_with_stack+0x18/0x20
[Thu Oct  9 02:00:26 2025]  call_with_stack from __irq_svc+0x98/0xb0
[Thu Oct  9 02:00:26 2025] Exception stack(0xf1851c60 to 0xf1851ca8)
[Thu Oct  9 02:00:26 2025] 1c60: c28f4d30 00000000 00000000 00000000 c28f4d80 c282bd80 c282b480 016e3600
[Thu Oct  9 02:00:26 2025] 1c80: 00000000 c28f4240 00000001 f1851d40 800f0013 f1851cb0 c0dec028 c0dec02c
[Thu Oct  9 02:00:26 2025] 1ca0: 600f0013 ffffffff
[Thu Oct  9 02:00:26 2025]  __irq_svc from __clk_recalc_accuracies+0x54/0x68
[Thu Oct  9 02:00:26 2025]  __clk_recalc_accuracies from clk_core_set_parent_nolock+0x204/0x274
[Thu Oct  9 02:00:26 2025]  clk_core_set_parent_nolock from meson8b_cpu_clk_notifier_cb+0x78/0x8c
[Thu Oct  9 02:00:26 2025]  meson8b_cpu_clk_notifier_cb from notifier_call_chain+0x8c/0x108
[Thu Oct  9 02:00:26 2025]  notifier_call_chain from srcu_notifier_call_chain+0x40/0x98
[Thu Oct  9 02:00:26 2025]  srcu_notifier_call_chain from __clk_notify+0x80/0xac
[Thu Oct  9 02:00:26 2025]  __clk_notify from clk_propagate_rate_change+0x98/0xb0
[Thu Oct  9 02:00:26 2025]  clk_propagate_rate_change from clk_propagate_rate_change+0x5c/0xb0
[Thu Oct  9 02:00:26 2025]  clk_propagate_rate_change from clk_propagate_rate_change+0x5c/0xb0
[Thu Oct  9 02:00:26 2025]  clk_propagate_rate_change from clk_propagate_rate_change+0x5c/0xb0
[Thu Oct  9 02:00:26 2025]  clk_propagate_rate_change from clk_core_set_rate_nolock+0xf4/0x31c
[Thu Oct  9 02:00:26 2025]  clk_core_set_rate_nolock from clk_set_rate+0x30/0x154
[Thu Oct  9 02:00:26 2025]  clk_set_rate from _opp_config_clk_single+0x24/0x84
[Thu Oct  9 02:00:26 2025]  _opp_config_clk_single from _set_opp+0x10c/0x41c
[Thu Oct  9 02:00:26 2025]  _set_opp from dev_pm_opp_set_rate+0x124/0x230
[Thu Oct  9 02:00:26 2025]  dev_pm_opp_set_rate from __cpufreq_driver_target+0x394/0x6ac
[Thu Oct  9 02:00:26 2025]  __cpufreq_driver_target from od_dbs_update+0x148/0x174
[Thu Oct  9 02:00:26 2025]  od_dbs_update from dbs_work_handler+0x2c/0x58
[Thu Oct  9 02:00:26 2025]  dbs_work_handler from process_one_work+0x168/0x3b8
[Thu Oct  9 02:00:26 2025]  process_one_work from worker_thread+0x264/0x42c
[Thu Oct  9 02:00:26 2025]  worker_thread from kthread+0xe0/0xfc
[Thu Oct  9 02:00:26 2025]  kthread from ret_from_fork+0x14/0x28
[Thu Oct  9 02:00:26 2025] Exception stack(0xf1851fb0 to 0xf1851ff8)
[Thu Oct  9 02:00:26 2025] 1fa0:                                     00000000 00000000 00000000 00000000
[Thu Oct  9 02:00:26 2025] 1fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[Thu Oct  9 02:00:26 2025] 1fe0: 00000000 00000000 00000000 00000000 00000013 00000000

</pre>

<p>
	 
</p>

<p>
	Is there a way to fix it ?<br />
	 
</p>
]]></description><guid isPermaLink="false">55606</guid><pubDate>Thu, 09 Oct 2025 10:20:49 +0000</pubDate></item><item><title>USB wifi install</title><link>https://testforum.armbian.com/topic/50825-usb-wifi-install/</link><description><![CDATA[<p>
	Good day to all, please help. How can I install the ath9k_htc driver. 
</p>

<p>
	Information:
</p>

<p>
	<strong>v25.5 rolling for MXQ running Armbian Linux 6.12.20-current-meson</strong>
</p>

<p>
	Packages:     Debian stable (bookworm)
</p>

<p>
	- <strong>lsusb</strong>: Bus 001 Device 004: ID 0cf3:9271 Qualcomm Atheros Communications AR9271 802.11n
</p>

<p>
	1) apt-get update &amp; apt install firmware-ath9k-htc
</p>

<p>
	reboot<br />
	 -- <em>plug usb wifi system freezes</em>
</p>

<p>
	<em>reboot<br />
	 apt remove firmware-ath9k-htc</em>
</p>

<p>
	<em>system work.</em>
</p>

<p>
	<strong>dmesg | grep -i usb</strong>
</p>

<blockquote class="ipsQuote" data-ipsquote="">
	<div class="ipsQuote_citation">
		Цитата
	</div>

	<div class="ipsQuote_contents">
		<p>
			[    2.805337] hub 1-0:1.0: USB hub found<br />
			[    3.143563] usb 1-1: new high-speed USB device number 2 using dwc2<br />
			[    3.363091] hub 1-1:1.0: USB hub found<br />
			[    3.663704] usb 1-1.1: new high-speed USB device number 3 using dwc2<br />
			[    3.833849] usb-storage 1-1.1:1.0: USB Mass Storage device detected<br />
			[    3.837475] scsi host0: usb-storage 1-1.1:1.0<br />
			[    3.847908] usbcore: registered new interface driver uas<br />
			[  735.720004] usb 1-1.2: new high-speed USB device number 4 using dwc2<br />
			[  737.285169] usb 1-1.2: ath9k_htc: Firmware ath9k_htc/htc_9271-1.4.0.fw requested<br />
			[  737.285323] usbcore: registered new interface driver ath9k_htc<br />
			[  737.285581] usb 1-1.2: Direct firmware load for ath9k_htc/htc_9271-1.4.0.fw failed with error -2<br />
			[  737.285619] usb 1-1.2: ath9k_htc: Firmware htc_9271.fw requested<br />
			[  737.285752] usb 1-1.2: Direct firmware load for htc_9271.fw failed with error -2<br />
			[  737.285770] usb 1-1.2: no suitable firmware found!<br />
			[  737.285779] usb 1-1.2: ath9k_htc: Failed to get firmware htc_9271.fw<br />
			[  737.286078] usb 1-1.2: ath9k_htc: USB layer deinitialized
		</p>
	</div>
</blockquote>

<p>
	<strong>dmesg | grep -i firmware</strong>
</p>

<blockquote class="ipsQuote" data-ipsquote="">
	<div class="ipsQuote_citation">
		Цитата
	</div>

	<div class="ipsQuote_contents">
		<p>
			[    2.619578] remoteproc remoteproc0: Direct firmware load for zephyr.elf failed with error -2<br />
			[    2.619720] remoteproc remoteproc0: Direct firmware load for zephyr.elf failed with error -2<br />
			[    2.619737] remoteproc remoteproc0: request_firmware failed: -2<br />
			[  737.285169] usb 1-1.2: ath9k_htc: Firmware ath9k_htc/htc_9271-1.4.0.fw requested<br />
			[  737.285581] usb 1-1.2: Direct firmware load for ath9k_htc/htc_9271-1.4.0.fw failed with error -2<br />
			[  737.285619] usb 1-1.2: ath9k_htc: Firmware htc_9271.fw requested<br />
			[  737.285752] usb 1-1.2: Direct firmware load for htc_9271.fw failed with error -2<br />
			[  737.285770] usb 1-1.2: no suitable firmware found!<br />
			[  737.285779] usb 1-1.2: ath9k_htc: Failed to get firmware htc_9271.fw
		</p>
	</div>
</blockquote>

<p>
	Please tell me how I can fix this? Thanks in advance for your help.
</p>
]]></description><guid isPermaLink="false">50825</guid><pubDate>Mon, 31 Mar 2025 15:48:39 +0000</pubDate></item></channel></rss>
