Jump to content

sminder

Members
  • Posts

    8
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Thanks guys for your suggestions. I've just tried to use Orange Pi 3 image (Armbian_community_25.5.0-trunk.399_Orangepizero3_bookworm_current_6.12.20_minimal.img) but something went wrong. The audio device is visible in a system: aplay -l **** List of PLAYBACK Hardware Devices **** card 0: audiocodec [audiocodec], device 0: CDC PCM Codec-0 [CDC PCM Codec-0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: HDMI [HDMI], device 0: ahub_plat-i2s-hifi i2s-hifi-0 [ahub_plat-i2s-hifi i2s-hifi-0] Subdevices: 1/1 Subdevice #0: subdevice #0 but I still can't play anything because of the error: aplay -D hw:0,0 /usr/share/sounds/alsa/Front_Center.wav Playing WAVE '/usr/share/sounds/alsa/Front_Center.wav' : Signed 16 bit Little Endian, Rate 48000 Hz, Mono aplay: pcm_write:2127: write error: Input/output error I can't find a release with 6.13.7 kernel.
  2. I installed the image https://dl.armbian.com/orangepizero2w/Bookworm_current_minimal on my Orange Pi Zero 2W board. But when I tied to check sound from the headphone interface on the expansion board I have a problem: user@orangepizero2w:~$ aplay -l aplay: device_list:274: no soundcards found... There is no chance to turn it on even through DTB overlay in armbian-config because there is no sound card in there. How to make sound work in this board with Armbian?
  3. Update: the image Armbian_23.11.1_Orangepi5-plus_bookworm_edge_6.7.0-rc1.img.xz also works fine, even with a desktop.
  4. Happy New Year guys! Fortunately I fixed a problem and start Armbian on my board. In short: the main problem was in SPI flash memory. More details: I wanted to install Android on my board, and it was unsuccessful (I tried to boot if from SD-card) and I decided to install it on the inner eMMC memory. So I followed the instructions "2.9. How to burn Android image into eMMC" from the official Orange Pi manual. One thing that helps to start Android from eMMC is clearing SPI-flash memory. I did it and Android started successfuly. But after that I can't start any other images from SD-card - after power on Android always starts first. So I decided to repair SPI-flash. I folowed the last post from here Maskrom / erase SPI and SD-cards start booting. So I decided to theck state of booting Armbian image after that and... it's alive! I can boot Armbian_23.11.1_Orangepi5-plus_bookworm_legacy_5.10.160.img.xz image without a problem! Here is a log of Armbian boot: armbian_boot_log.txt
  5. I tried two another SD cards, even super-speed Samsung Pro, but result the same - tons of errors. I copied rk3588-orangepi-5-plus.dtb file from Debian image to Armbian image (they are obviously different because of size) but result the same - tons of errors. I attached the boot log of Orange Pi Debian image. orpi5+_debian_good_boot_log.txt
  6. No, I haven't, but I will. The reason I didn't change the SD-card is this card works pretty well with another boards and another OS.
  7. Actually it doesn't matter - I tried another one with the same results. Will it help if I post the hardware info (chips name e.t.c) to find out the problem?
  8. I've got Orange Pi 5 Plus board with 16 Gb of RAM, 256 Gb of eMMC, Realtek RTL8852BE-CG wireless module. SD card is Samsung EVO Plus 32Gb. I tried to run Armbian images on this board (from the SD-card I've mentioned before) but it was absolutely failed. I tried 5 images: Armbian_23.11.1_Orangepi5-plus_jammy_legacy_5.10.160_gnome-amazingfated_desktop.img.xz Armbian_23.11.1_Orangepi5-plus_bookworm_legacy_5.10.160.img.xz Armbian_23.11.1_Orangepi5_jammy_legacy_5.10.160_gnome-amazingfated_desktop.img.xz Armbian_23.11.1_Orangepi5-plus_bookworm_edge_6.7.0-rc1.img.xz Armbian_23.11.1_Orangepi5-plus_jammy_edge_6.7.0-rc1.img.xz which I downloaded from your website but the result the same: tons of errors, a lot of dumps, no even chance to see a desktop. Also I should say the official images of Ubuntu and Debian works fine so I guess it's not a hardware issue. There is UART log when I tried to start Armbian_23.11.1_Orangepi5-plus_jammy_legacy_5.10.160_gnome-amazingfated_desktop.img.xz image putty.log Could anyone tell me what the problem is?
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines