Jump to content

weecee

Members
  • Posts

    15
  • Joined

  • Last visited

  1. Hi, An old problem, since I got the board which is 4C. Not a + - or whatever but the plain C. Symptoms: 1. HDMI worked randomly, maybe every 10th...15th boot lead to a working system, or rather to a visible HDMI-connection. But now switching on-off does not help at all. 2. Quite often one can get the board booting to the point where it asks for the password, and after clicking ok, it switches the screen off, and won't return. So the telly says that "no signal". 3. When switching on the board the tv set sees that there's someone on the hdmi port, and shows the booting sequence, and finally goes to Armbian's graphical mode asking for the password. Click "ok", and in 10 sec we are in the "no signal" -state. 4. And now guessing; when the board loses its connection to the tv set once, it will keep the hdmi feed down and it can not be woken up but by re-booting the board? Is there such a two-way feedback in-built? I mean, if the board does not recognize the tv, then it's stops sending video signal? And how to switch off this feature if there's one? Btw, I'm not a computer hobbyist so knowing not much about these, maybe just a (ab)user. I've been writing about this "feature" earlier to many platforms but no answer whether Armbian is programmed so that the board-whatever needs to "see" the receiving set all the time to keep its hdmi signal alive. This has 5.10.63-rockchip64 - kernel, the last one to have a working sound with this board. Well, not even sound now... And yes, this has a miniature hdmi -connector which maybe the culprit partly. It's very weak both mechanically, quite loose cable connection. If you twist-press the cable it may help to get the screen on, but now even this does not help anymore. And it's been tested with half a dozen cables so that's not the reason either.
  2. Ok, Let there be sound, and sound was there... : vesa@rockpi-4b:~$ uname -r 5.10.63-rockchip64 vesa@rockpi-4b:~$ aplay -l **** List of PLAYBACK Hardware Devices **** card 0: rockchiprk3399 [rockchip,rk3399], device 0: ff880000.i2s-ES8316 HiFi ES8316 HiFi-0 [ff880000.i2s-ES8316 HiFi ES8316 HiFi-0] Subdevices: 0/1 Subdevice #0: subdevice #0 card 1: hdmisound [hdmi-sound], device 0: ff8a0000.i2s-i2s-hifi i2s-hifi-0 [ff8a0000.i2s-i2s-hifi i2s-hifi-0] Subdevices: 0/1 Subdevice #0: subdevice #0
  3. And some further updates lead to nowhere: vesa@rockpi-4b:~$ aplay -l **** List of PLAYBACK Hardware Devices **** card 0: Analog [Analog], device 0: ff880000.i2s-ES8316 HiFi ES8316 HiFi-0 [ff880000.i2s-ES8316 HiFi ES8316 HiFi-0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: hdmisound [hdmi-sound], device 0: ff8a0000.i2s-i2s-hifi i2s-hifi-0 [ff8a0000.i2s-i2s-hifi i2s-hifi-0] Subdevices: 1/1 Subdevice #0: subdevice #0 vesa@rockpi-4b:~$ uname -r 5.19.16-rockchip64 To be noted that upgrading to 5.19.16 kept the loudspeakers silent, so what next...
  4. Right, accidentally updated: vesa@rockpi-4b:~$ uname -r 5.15.74-rockchip64 vesa@rockpi-4b:~$ aplay -l **** List of PLAYBACK Hardware Devices **** card 0: hdmisound [hdmi-sound], device 0: ff8a0000.i2s-i2s-hifi i2s-hifi-0 [ff8a0000.i2s-i2s-hifi i2s-hifi-0] Subdevices: 0/1 Subdevice #0: subdevice #0 And the silence is here again...
  5. Ok, reverted back to the tested version 5.10.63 (Armbian Config - quite handy for a beginner like me). HDMI sound works nicely again. Ending my adventures on kernel upgrades here vesa@rockpi-4b:~$ uname -r 5.10.63-rockchip64 vesa@rockpi-4b:~$ aplay -l **** List of PLAYBACK Hardware Devices **** card 0: rockchiprk3399 [rockchip,rk3399], device 0: ff880000.i2s-ES8316 HiFi ES8316 HiFi-0 [ff880000.i2s-ES8316 HiFi ES8316 HiFi-0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: hdmisound [hdmi-sound], device 0: ff8a0000.i2s-i2s-hifi i2s-hifi-0 [ff8a0000.i2s-i2s-hifi i2s-hifi-0] Subdevices: 1/1 Subdevice #0: subdevice #0
  6. Not brave enough to upgrade to 5.17 as it in my case it may lead to a completely non-booting system, and to get it back takes hours of trial-error-downloading-hassle, by experience...
  7. Ok, this board is 4 B+, but maybe same symptoms exists as it was with my 4C. Luckily my 4C has the older 5.10.63-rockchip64, and its hdmi-sound works. It seems that I've learned nothing about these non necessary updates-upgrades, but they have been made so attractive and simple so its difficult to resist pressing the button...
  8. Apparently auto-updates did no good, still no sound after upgrading from 5.10.63-rockchip64 (this had sound working) to 5.15.52. No sound in headphones, HDMI... Would be nice to know what those magic lines are in settings which made this vesa@rockpi-4b:~$ aplay -l **** List of PLAYBACK Hardware Devices **** card 0: hdmisound [hdmi-sound], device 0: ff8a0000.i2s-i2s-hifi i2s-hifi-0 [ff8a0000.i2s-i2s-hifi i2s-hifi-0] Subdevices: 0/1 Subdevice #0: subdevice #0 vesa@rockpi-4b:~$ uname -a Linux rockpi-4b 5.15.52-rockchip64 #22.05.4 SMP PREEMPT Mon Jul 4 09:40:29 CEST 2022 aarch64 GNU/Linux
  9. Hello, yes, most probably you've found the culprit; only one error message with the older kernel compared to that of yours: vesa@rockpi-4b:~$ uname -r 5.10.63-rockchip64 vesa@rockpi-4b:~$ dmesg | grep rockchip-pin* vesa@rockpi-4b:~$ dmesg | grep es83* [ 14.575882] es8316 1-0011: Failed to get IRQ 0: -22 vesa@rockpi-4b:~$ dmesg | grep rockchip-i2* vesa@rockpi-4b:~$ Now it's the question of expertise I don't have And that was from my Rock Pi 4B. It still works, its hdmi-sound is ok, boots well from its nvme, and so on. So maybe better to leave it as it is. But then my Rocky Pi 4 C became a paperweight. Downgrading 5.15.25-rockchip64 to 5.15.24-rockchip64 practically changed nothing, but the bigger leap to 5.10.63 reduced it to rubbish. Yes, it might be doing something as the leds are blinking when switched on but nothing coming up to the screen- all black. Needs to dismantle the box as its sd-slot is hidden behind the flat cable, and maybe to find a uart-cable to play with, and an sd-card with a working os which might wake up his/her hdmi-bus, too many ifs and ands ... too time consuming for now. Based on that above one can assume that eg. OPI 4 loses its hdmi sound similarly as Rock Pi, right? I mean after latest kernel upgrades, 5.15.xxx .
  10. Now I believe that it's a bug in the kernel. Namely, I tried to make dozens of different settings in .asoundrc & etc/asound.conf and nothing changed, hdmi remained silent. Then I downgraded, or rather tried to, to 5.10.63 and now the board is neither booting at all nor sending any signals to my hdmi display, so nothing on the screen. What makes this even more difficult is that Rock Pi C, to my opinion, has mechanically a pretty weak (mini?) hdmi connector, and to get anything on screen was rather laborious, a lot of trial-error. To get an idea whether it was a bad contact in the hdmi-pcb, cable, or a software problem, a total nightmare and a lot of hours spent. Anyhow, it was in working condition for some months, and even succeeded in booting from its nvme-disk, but these recent upside-downgrades made my Rock piC totally unusable. So maybe its better to leave kernel upgrades for a while if your board happens to work... Btw writing this with my Rock Pi 4B which still has the old kernel 5.10.63, and its hdmi sound works! vesa@rockpi-4b:~$ uname -r 5.10.63-rockchip64 vesa@rockpi-4b:~$ aplay -l **** List of PLAYBACK Hardware Devices **** card 0: rockchiprk3399 [rockchip,rk3399], device 0: ff880000.i2s-ES8316 HiFi ES8316 HiFi-0 [ff880000.i2s-ES8316 HiFi ES8316 HiFi-0] Subdevices: 0/1 Subdevice #0: subdevice #0 card 1: hdmisound [hdmi-sound], device 0: ff8a0000.i2s-i2s-hifi i2s-hifi-0 [ff8a0000.i2s-i2s-hifi i2s-hifi-0] Subdevices: 0/1 Subdevice #0: subdevice #0
  11. Maybe this is not a kernel issue at all, someone upgraded kernel version today and thank you for that, but it's still pretty quiet here. Well, earplugs work but not hdmi sound. Maybe this is rather an alsa-pavu-problem where card & device numbers are messed and do not match well. Anyhows, the sun is shining and these are the last moments for ice fishing hereabout, so leaving this to wiser ones... **** List of PLAYBACK Hardware Devices **** card 0: Analog [Analog], device 0: ff880000.i2s-ES8316 HiFi ES8316 HiFi-0 [ff880000.i2s-ES8316 HiFi ES8316 HiFi-0] Subdevices: 0/1 Subdevice #0: subdevice #0 card 1: hdmisound [hdmi-sound], device 0: ff8a0000.i2s-i2s-hifi i2s-hifi-0 [ff8a0000.i2s-i2s-hifi i2s-hifi-0] Subdevices: 0/1 Subdevice #0: subdevice #0 vesa@rockpi-4c:~$ uname -r 5.16.16-rockchip64
  12. Right, most probably I was not downgrading enough as nothing changes, all quiet. There should be some other means to solve this, but this greatly exceeds my skills, therefore ending here. vesa@rockpi-4c:~$ uname -r 5.15.24-rockchip64 vesa@rockpi-4c:~$ aplay -l **** List of PLAYBACK Hardware Devices **** card 0: hdmisound [hdmi-sound], device 0: ff8a0000.i2s-i2s-hifi i2s-hifi-0 [ff8a0000.i2s-i2s-hifi i2s-hifi-0] Subdevices: 0/1 Subdevice #0: subdevice #0
  13. Yes, Rocki-pi 4C, same symptoms here with 5.15.25-rockchip64, no sound, all quiet, nothing coming through hdmi, and no fix just wondering if there's an easy remedy, except "downgrading" the installed kernel... vesa@rockpi-4c:~$ aplay -l **** List of PLAYBACK Hardware Devices **** card 0: hdmisound [hdmi-sound], device 0: ff8a0000.i2s-i2s-hifi i2s-hifi-0 [ff8a0000.i2s-i2s-hifi i2s-hifi-0] Subdevices: 0/1 Subdevice #0: subdevice #0 vesa@rockpi-4c:~$ uname -r 5.15.25-rockchip64
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines