All Activity

This stream auto-updates     

  1. Past hour
  2. YES, WiFi (client) works OK with NM. If I start hostapd manually from command line (default config) then AP appears but cant connect using def pass "12345678" :( When stopped it does NOT reastore original WiFi client. (wlan0 is not configured / attached to AP). Shoudl I provide (compressed) /var/log/messages from boot moment to "statble"? Or some outpout of journalctl (please advize on command syntax)?
  3. Is wifi otherwise working properly? If you would provide logs, solution might be visible from there.
  4. Hello. I have just acquired an Orange Pi plus 2e. Armbian Xenial is installed on emmc. I wish my SD card to become my /home. Can you help me? Thank you.
  5. Anything is possible, but this is Armbian support forum, section Allwinner A20, support for a few boards that or the list. Your problem is off topic, moving to general section. U-boot could provide something like that, yes, but you can also look towards https://github.com/open-power/petitboot direction. Its on you to do the research, make a POC, develop and maintain this feature ...
  6. Today
  7. Hello, What does that mean? Is it related to ethernet of x96-air? I couldn't find fec.c in /lib/modules/5.7.7-arm-64/kernel/drivers/net
  8. Only looks This is based on WiFi management by systemd, and in Buster this is done by NetworkManager. How to setup / use AP in this case? (I want to setup AP on different channel from "main AP" for webcams, for troughtput reasons).
  9. Putting the .ignore_changes did work fine. The original title was a little bit wrong. What I wanted to do is to build a v20.05 image and to get its kernel source code (the actual version is 5.4.57 rather than 5.7.14). The correct way to do it is Clone the master (https://github.com/armbian/build.git) Run vagrant if necessary (cd ./config/templates; vagrant up; vagrant ssh; cd armbian) Run sudo git checkout origin/v20.05 Run sudo touch .ignore_changes Run ./compile.sh BOARD=tinkerboard RELEASE=buster BRANCH=current BUILD_DESKTOP=no KERNEL_ONLY=no KERNEL_CONFIGURE=no INSTALL_HEADERS=yes BUILD_MINIMAL=yes INSTALL_KSRC=yes And the following file was created under output/images. Armbian_20.05.7_Tinkerboard_buster_current_5.4.57_minimal.img The image file includes a src archive file on /usr/src. root@tinkerboard:~# ls /usr/src/ linux-headers-5.4.57-rockchip linux-rockchip-current_5.4.57_20.05.7_config.xz linux-source-5.4.57-rockchip.tar.xz Thanks guys.
  10. Yesterday
  11. I ran a 12 hour stress run last night without issues, other than forcing me to put a better fan on the heatsink! :-) I've been running memtester for about 10 hours now without issue.
  12. I don't want to hijack this one but what i mean is use the v4l2 commands to check for the camera, or use the command: dmesg|tail after you attach the USB camera. Moderator can delete this. no problem.
  13. That's like a smart people thread. I'm not one of those guys. They kind of hijacked the thread and the guy never tried the advice buried in there somewhere. Mine is that same orange pi camera though I think.
  14. Rollback to your 5.8 and try this tip with pulse-audio (learned myself the hard way) 1. Open a session (or cmd line) 1. Open a second session (or cmd line) 2. Run your MP3 to output to jack on the first session (or cmd line) 3. While the file is playing (silently as you say) on the first session, fire alsamixer (select audio-codec) on the second session and start unmuting the controls, upping the volume, etc. At some point, eventually you get the sound output to jack. Watch the kernel for some messages.
  15. I think you should read this thread to the end, you might need v4l2 and media to grab some image if you have a new kernel. This might be true to USB camera. (i have not tried using USB camera, just a guess.)
  16. enabled eldo1 cpvdd to codec-analog, but didnt help either codec-analog@1f015c0 { compatible = "allwinner,sun50i-a64-codec-analog"; reg = < 0x1f015c0 0x04 >; allwinner,codec = < 0x15 >; status = "okay"; cpvdd-supply = < 0xa7 >; phandle = < 0x12 >; }; codec@1c22e00 was on older kernel (5.6x?): compatible = "allwinner,sun8i-a33-codec"; now the dtb/dts has for codec@1c22e00: compatible = "allwinner,sun50i-a64-codec"; if changed back to allwinner,sun8i-a33-codec the npi a64 doenst boot anymore
  17. @ldiaz have you ever tried to get an rpi CSI camera to work with the camera interface? I have tried all of the stuff I could find on the forums sudo apt-get install v4l-utils and what I could understand from this thread: but still nothing, even from just sudo mplayer tv:// Going to try a USB camera now. I just happen to have a pile of those rpi cameras. #edit couldn't get USB camera to work either, but mplayer gave me a different error, and now I have /dev/video 0 1 and 2. #edit2 later found the service in the config script, enabled it, and it got a could not remove klipper service message, but the star was there when I went to check, so it apparently worked. but camera does not
  18. Yes, the heatsink could be warm. But as I said globally always around 82°C with all cpus at 100%, (and decrease quickly when I stop). I think the processor limit ~85 °C. I tested previously another solution with a little heatsink and a fan, the temperature was also around 50°C. It is a personal choice to change in order to have no noise, because I use it as pc and as media center.
  19. I soldered these to my PowerSupply, you could as well solder it to an USB-Connector... DC Power Plug Male Connector 4.0x1.7mm Male Socket With Cord Cable,DC pigtail 4.0/1.7mm /Free shipping/10PCS US $6.64 / lot (10 pieces) https://www.aliexpress.com/item/1927392841.html I didn't test them on "how many cycles" they last, but I like the sealed barrel. To solder the barrel was always the weak spot to me.
  20. Sorry, got error, gnome-disks can't be run from mounted system drive P34A80 NVMe has SLC buffer, so result shall be similar, may be except for buffer size.
  21. You can use the multitool to dd image files directly on the device: it has a fully functional bash shell to do such kind of maintenance tasks. Nonetheless you need to do know what you are doing. Maybe you can burn the "bad" backup you made and then burn the rootfs from the image @fabiobassa provided. You need to do some juggling with the original image, but if you are able to do so you can try. Your board is a new revision of the r329q family. In alternative you may have more luck tryingr other images for boards which are older r329q revisions (v2.0, v3.0, v7.0, ...)
  22. @Hannes Worst @kevinplatt Today I did try Kernel 5.80 with debian buster on the NPi A64. HDMI-audio does work, but analog audio doesnt work complete I can start audio on analog-audio port. It show that it would play but I dont get any sound. Also when I adjusted the mixer. The anmes for AIF1 has slightly changed. Also sound_hdmi is now hdmi_sound... Both are listed by "aplay -l" root@npi-a64(192.168.6.116):/home/guido/iradio# aplay -l **** Liste der Hardware-Geräte (PLAYBACK) **** Karte 0: sun50ia64audio [sun50i-a64-audio], Gerät 0: 1c22c00.dai-sun8i-codec-aif1 sun8i-codec-aif1-0 [1c22c00.dai-sun8i-codec-aif1 sun8i-codec-aif1-0] Sub-Geräte: 0/1 Sub-Gerät #0: subdevice #0 Karte 1: sun50ia64hdmi [sun50i-a64-hdmi], Gerät 0: 1c22800.i2s-i2s-hifi i2s-hifi-0 [1c22800.i2s-i2s-hifi i2s-hifi-0] Sub-Geräte: 1/1 Sub-Gerät #0: subdevice #0 root@npi-a64(192.168.6.116):/home/guido/iradio# uname -a Linux npi-a64 5.8.0-sunxi64 #trunk SMP Mon Aug 10 15:12:34 +03 2020 aarch64 GNU/Linux System diagnosis information has been uploaded to http://ix.io/2tUF
  23. https://github.com/armbian/build/pull/2129
  24. RockPi 4 Model C support will come in the near future?
  25. Hello Guys, I bought this box 2 years ago and practicaly never used. After home cleaning found it and fought "if it run Android, it can run any Linux". I alredy have RBpi B3+ and with this TV Box now I could have a small open source data center and practice with ngnx, MariaDB, Postgree, MySQL, NodeJS, PHP, Python etc. After research I found this web, and liked Armbian idea. Issues: 1. This box looks identical to MXQ-4K, however the image did not work. When I opened it, the procesor was Allwinner H3, PCB is AK-H3-MXQ4K-V1.1 (https://wikidevi.wi-cat.ru/GUANZHI_Android_TV_BOX_H3) 2. I have many SD/microSD (brand and non brand), however only Lexmark 8Gb SD worked, even same brand but with 16Gb did not worked. 3. I try many armbian images for Allwinner H2/H3, but only worked Orange pi PC image 4. WiFi does not work, it is XR819 chip. It is not important at this stage, since LAN work 5. Not possible to copy and boot from internal NAND/eMMC, only from SD card Everything else looks to be OK (LAN, HDMI, USBs) If some body can advise how to copy armbian to internal flash, will be good, since armbian-config does not show option. I guess there is some copy block and need to use UART port. Regards,
  26. Or you could simply add this patch to the patches folder and see if it works and give feedback https://cdn.kernel.org/pub/linux/kernel/v5.x/patch-5.8.1.xz
  27. Hi, There have been a couple of posts about this over time, but I was wondeing if somebody could please provide concrete example / sample code that uses DMA to TX out the GPIO pin(s)? I want to be able to TX outwards only from my Allwinner H3 device (Orange PI PC) to 16 pins in parallel (so 16 bit DMA in parallel) from a chunk of memory in RAM. Happy with a basic example if somebody has which just blasts out one GPIO pin even.
  28. will build tomorrow 5.8.1 for my h6 orangepioneplus ( if @megi ) has updated the megous branch and see about its status. thanks @martinayotte and others that contribute
  1. Load more activity