Jump to content


  • Posts

  • Joined

  • Last visited

Recent Profile Visitors

875 profile views
  1. Try this: We offer this and a similar amixer config to enforce HDMI audio since a while among a few hundred Odroid N2 users and so far didn't receive any negative feedback. But someone just posted here that this "burned" his/her USB DAC (plugged in concurrently), whatever was meant by that, but double check that card 0 is really the onboard sound card, as I mentioned below here: I basically found this via trial&error and at best only half understood, e.g. why this cyclic looking src/bus/dst linking is required, especially including explicitly device/card 0 while those are for card 0 in the first place (-c 0). Probably a conflicting device tree patch caused the issue in the first place, or a fundamental change with Linux 5.10 which broke a functional Armbian patch.
  2. @SoSie What do you mean by "burn"? You can always reset all mixer settings via rm /var/lib/alsa/asound.state alsactl init The commands explicitly change settings for audio device/card 0 (-c 0), so check first whether onboard audio is card 0 via aplay -l Usually it should be, but I read on recent kmod changelog (Debian Bookworm and above, probably Ubuntu Jammy already) Not sure how kmod shall have an effect on the order in which the kernel detects sound devices, but always good to double check. On USB DACs, the amixer commands should mostly just fail since either the controls are invalid, or the values. USB audio is not internally attached via I2S etc.
  3. Since Linux v5.10 it is a bit complicated to get it working. Try this: # Reset and re-initiate ALSA mixer states rm /var/lib/alsa/asound.state alsactl init # Enable 3.5mm output amixer -c 0 set 'TOACODEC OUT EN' 'on' # Use I2S B as source for 3.5mm output, I2C A is somehow not usable amixer -c 0 set 'TOACODEC SRC' 'I2S B' # Use ALSA device 0 as input for I2S B amixer -c 0 set 'TDMOUT_B SRC SEL' 'IN 0' # Enable I2S B (SRC 2) on device 0 (_A) amixer -c 0 set 'FRDDR_A SRC 2 EN' 'on' # Set output channels for device 0 (_A) amixer -c 0 set 'FRDDR_A SINK 1 SEL' 'OUT 0' amixer -c 0 set 'FRDDR_A SINK 2 SEL' 'OUT 1' amixer -c 0 set 'FRDDR_A SINK 3 SEL' 'OUT 2' # Set master volume to 85% amixer -c 0 set 'ACODEC' '85%'
  4. USB gadget mode does currently not work OOTB on Armbian, but it can be enabled easily with a device tree change or overlay: /dts-v1/; /plugin/; / { compatible = "radxa,zero", "amlogic,g12a"; fragment@0 { target = <&usb>; __overlay__ { dr_mode = "otg"; }; }; }; I can open a PR for adding this as device tree overlay, or enabling OTG OOTB on Radxa Zero, like vendor did: https://github.com/radxa/kernel/commit/775a467 The latter would be simple. In case of an overlay, I'd need some hint about how to do it best: Adding it to the general meson64 overlays patch seems to be right: https://github.com/armbian/build/blob/master/patch/kernel/archive/meson64-6.0/general-meson64-overlays.patch But how to prefix or set `compatible` attribute best to assure it can be applied, resp. make clear that it works on Radxa Zero only (as state of testing)?
  5. v21.08.2 (Linux 5.10) is the latest which works. U-boot seems irrelevant since only updating the kernel breaks it and updating/flashing U-boot doesn't solve it. It works on NanoPi NEO3 (same SoC), which probably indicates an issue with the device tree, if the USB3 host is the same?
  6. Since Linux 5.15, the USB3 port on ROCK64 does not work anymore with Armbian. The following kernel errors are shown: usb 5-1: USB disconnect, device number 2 [...] usb usb5-port1: Cannot enable. Maybe the USB cable is bad? This has been reported by multiple users with multiple drives and cables, also disabling UAS does not help. lsusb shows the drive/device, but lsblk does not. I know the ROCK64 is not currently supported by Armbian/has no maintainer, so I'm not expecting anything, just posting this as information and probably someone with more insights into the rockchip64 kernel build has an idea or workaround.
  7. I leave it to you whether a quicker RC-based release or little later stable-based release is feasible. I tested it with eMMC and SD card and it works pretty well. It does support being loaded from SPI flash as well? That is nice indeed, at least as backup bootloader, haven't tested this yet.
  8. The rk3399-opp-2ghz overlay is currently broken on all RK3399 SBCs since Linux 5.15 kernel btw (including both, "current" 5.15 and "edge" 5.18). Another report on this forum: And we replicated on NanoPi R4S and got reports on ROCK Pi 4 and NanoPi M4.
  9. That works, awesome! It's still a release candidate (now RC5 is available), I guess it is not feasible to use it for a new Armbian N2 U-Boot package before being a stable release right? But great to have a workaround, many thanks!
  10. I can confirm this and posted a serial console log here: EDIT: Ah sorry, I see my logs just match the ones that have been posted here already. It's also the same orange 16 GiB eMMC module. I'll try with edge firmware and upstream U-Boot when I find time. EDIT2: I cannot replicate ATM, but it indeed seems that it boots fine with at least one other eMMC module, reported by one of our users. Probably it's some sort of timing, i.e. the eMMC takes too long to become ready resp. the bootloader tries too early to read its partition table? The bootloader itself however was loaded successfully from that same eMMC obviously 🤔. I clearly lack if insights, just guessing around 😅.
  11. @Franky66 did you manage to boot from eMMC when flashing it directly there? I'm not able to get the recent Odroid N2 Bullseye image to boot from eMMC at all, regardless which way. Doing the exactly same on SD card works fine. I also tried it with a custom image build, installing the Armbian "current" kernel package (Linux 5.10.123) and flashing respective U-Boot via write_uboot_platform: Fails the same way when flashing to eMMC, works from SD card. Here is the log from serial console: It seems to have issues to detect the partitions on the eMMC, but of course they are fine when mounting and fscking the eMMC from a different system.
  12. At least Linux v5.15 by default has the old sysfs API disabled, so if anything depends on it (has not been migrated to use libgpiod) and it hasn't been explicitly enabled for the build like Armbian did now, then yes.
  13. Issue solved with latest kernel release, many thanks guys!
  14. Let me know if I can help with testing, reviews or such. However, as being owned by full time job and own OOS projects, I cannot be a reliable official maintainer.
  15. Ah you're right, I realised that it is the old Linux 3.x kernel and that there is no mainline kernel image provided by e.g. Tobetter for Odroid C2, like it is for newer Odroids. Testing this old image has no value in this regards. Just for reference, the mainline kernel thread on the Odroid forum may contain some hints or may be used to discuss the topic: https://forum.odroid.com/viewtopic.php?t=22717
  • Create New...