All Activity

This stream auto-updates     

  1. Past hour
  2. guidol

    A64 and the 3.10 kernel

    you have to ask @lex here in the forum or in the thread of the friendlyarm-forum, because at this time it seems that this image isnt public
  3. gounthar

    Sunvell H3 2GB RAM + 16GB ROM TV Box

    The PlayStore is there, and Netflix starts (but as I don't have a Netflix account, I haven't been able to test it).
  4. Andralin

    Which USB video grabber to buy for Orange Pi?

    OK, after some research I managed to find and configure a USB video grabber for my OrangePi PC Plus. I'm building a audio center for my car using OrangePi. And I decided to install a cheap reversing camera from ebay in my car, which supplies composite analog video output. I want to display the reversing cam stream on also on my OPi audio center display, so I needed an analog video grabber. I have ordered exactly this one from ebay: EasyCap DC60 USB Video Capture Card Adapter with ChipSet UTV 007 for Win 7 8 10 It's very important to let it have UTV 007 chipset surely, attention, there are many copies with different chipsets. What I read other chipsets won't work. I installed the driver from this link: usbtv After driver installation, you should see something like this: # lsusb Bus 003 Device 005: ID 1b71:3002 Fushicai USBTV007 Video Grabber [EasyCAP] And check if the device could be used as a capture device: # v4l2-ctl --all Driver Info (not using libv4l2): Driver name : usbtv Card type : usbtv Bus info : usb-sunxi-ehci-1.6 Driver version: 3.4.113 Capabilities : 0x05000001 Video Capture Read/Write Streaming Priority: 2 Video input : 0 (Composite: ok) Video Standard = 0x0000f900 PAL-M/60 NTSC-M/M-JP/443/M-KR Format Video Capture: Width/Height : 720/480 Pixel Format : 'YUYV' Field : Interlaced Bytes per Line : 1440 Size Image : 691200 Colorspace : SMPTE 170M Transfer Function : Default YCbCr Encoding : Default Quantization : Default This seems very good. After that using mplayer I can see the captured video stream perfectly on my HDMI display with 800x480 resolution. You need to supply the proper options for mplayer. I wanted to see the stream on the framebuffer, since I don't use X window. This command works for me: mplayer tv:// -tv driver=v4l2:norm=PAL-M:width=720:height=480:outfmt=yuy2:device=/dev/video0:input=0 -vf flip -vf expand=800:480:40:0 -vo fbdev:/dev/fb0 Change the video filter -vf options (flip, expand) according to your display resolution and needs (if needed at all). The stream is playing perfectly, without any single frame dropped. There is one important thing. Always connect the USB grabber to the OrangePi using a USB hub! The device is taking 330 mA which is too much for the OPi, without USB hub the OPi USB supply voltage drops down to 4.3 V. I'm planning to order and try this cable also: Delock Cable USB 3.0 type A male + USB type A male > USB 3.0 type A female, I hope with this one I can just supply an external 5V DC power to the dongle, without using a hub.
  5. Today
  6. TonyMac32

    Build errors (semi-critical)

    So just for an update on these things, I decided to clean install regular ubuntu this time, instead of lubuntu. Same issues, linaro 4.8 no public key/downloading on every single build (has been an issue for me, my dl rate from their server has been down at the 50 kbps range on more than one occasion), and now no aptly 1.2.0. Decided to try a Docker environment, and within docker it downgrades aptly as commanded and is able to import a key for linaro 4.8. So, strange times.
  7. oeydev

    NanoPI M4

    Is armbian include RPi.GPIO package ? How can I control GPIO? root:~# python Python 2.7.13 (default, Sep 26 2018, 18:42:22) [GCC 6.3.0 20170516] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import RPi.GPIO Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/usr/local/lib/python2.7/dist-packages/RPi/GPIO/", line 23, in <module> from RPi._GPIO import * RuntimeError: This module can only be run on a Raspberry Pi! >>>
  8. Caidao T1 - s905x 2gb ram ARMBIAN 5.62 user-built Ubuntu 18.04.1 LTS 4.18.7-aml-s9xxx S11 TV Box - s905 1gb ram ARMBIAN 5.60 user-built Ubuntu 18.04.1 LTS 4.18.7-aml-s9xxx running x2goclient via eth connecting to Scientific Linux 7.5 MATE desktop
  9. Andralin

    tutorial I2S on Orange Pi H3

    Hi All, I have some issues with my ES9023 DAC and my OrangePi PC Plus. I bought the same DAC as shown in the very first post of this topic. I followed all the steps explained here for the configuration. Eventually I had everything set up, I was supposed to hear sound from the DAC, but there was only a white noise. I tried also giving external +5V DC supply to the DAC, it didn't help. Then once suddenly it started to working, I could play audio through the DAC, but the next time it was again noise only. After spending many hours and hours investigating finally I understood what's happening. After power up the system, to be able to hear audio from the DAC I have to switch the DAC +5 V supply ON and OFF many times. Most of the times after powering it on, there is only noise. But after 10..20 power ON/OFF cycles (depending my luck) suddenly it switches on without any noise, and in this case it is working perfectly until the next power off. Is this a normal operation of this kind of DAC? Did anyone experienced similar problems? Is there a solution to overcome this issue and make it working straight after the first power on? Or may be my DAC defected? Shall I try to buy a new one? I ordered mine from this link: DAC Sabre ES9023 Analog I2S 24 Bit 192 KHz Decoder Board For Raspberry Pi
  10. @@lex I also tried building kernel from source, I managed to get kernel modules like sun6i-csi, ov5640 and other v4l2 modules. And I'm able to load them successfully without any error. But still there's still no '/dev/video0', although there's no error in dmesg as well. Following is the `lsmod` output after loading modules. I compared it with output provided in, all the modules are available. So, now the only problem should be with dts/ dtsi files, if I'm not doing anything wrong? And just to point out, my board has parallel camera interface not serial, If it helps anyway. Please suggest.
  11. I compared the kernel config in patch with my .config, the patched modules are already enabled. Also the dts patch is specific to nanopi-h3 board only. So, I don't think dts files will be updated for my board. Or shall I make same changes in my board's dts too? Thanks
  12. Hi, I've been getting a journal file full of this kind of entry lately, which is using up all my memory until I get an error "no space left on device". I have two Cubietrucks, this is only occurring on one of them, both running mainline kernel and both up to date. The one causing problems has a 2.5" hdd mounted via the sata connector. Oct 16 11:27:35 stpeter.nentura liblogging-stdlog[1048]: action 'action 12' resumed (module 'builtin:omfile') [v8.24.0 try ] Oct 16 11:27:35 stpeter.nentura liblogging-stdlog[1048]: action 'action 2' suspended, next retry is Tue Oct 16 11:28:05 2018 [v8.24.0 try ] I've seen on the link that there is a "how to solve it" but I'm a bit lost. Can someone help dignose and solve? Thanks!
  13. sfx2000

    Powering through micro USB

    That's a BPi - not a tinker...
  14. Card has likely gone into R/O mode, Samsung does this - 2 years from an SD card is pretty good... Time to get new card...
  15. sfx2000

    Sunvell H3 2GB RAM + 16GB ROM TV Box

    Does it have Google Play? Would also be interesting perhaps if it has Widevine Support (this is a DRM scheme that can cause problems with AOSP and haxxored play store support - if Netflix runs from the playstore it might have valid keys there
  16. Yesterday
  17. chwe

    Daily (tech related) news diet

    After all those bad news.. It's time again to show a nice one. They host their blog now on an olimex lime2 with Armbian and a solar cell. Besides switching to a static website they also used dithering to reduce the image size (and a nice retro look for those who like it). I really appreciate that they provide a detailed article with the technical details as well: with how to's and a bunch (or everything?) of scripts open-sourced. For me it looks like a well crafted setup. But I'm neither a EE nor @tkaiser (for the OS related reduction of power consumption) to give a proper statement. But they're open for improvements, so let them know if you spot something.
  18. A way to disable hardware is by setting its status to disabled in the device tree, take a look at " dtc -I fs -O dts /sys/firmware/devicetree/base|less" to see the runtime devicetree. For instance for sound and video this would look like below, which you can convert to dtb with something like "dtc -I dts -O dtb youroverlay.dts > youroverlay.dtb" and add as a user-overlay (place dtb file in /boot/overlay-user) and add "user-overlays=youroverlay" line in /boot/armbianEnv.txt. /dts-v1/; / { compatible = "allwinner,sun8i-h3","allwinner,sun50i-h5","friendlyarm,nanopi-neo2"; fragment@0 { target-path = "/soc"; __overlay__ { hdmi@1ee0000 { status = "disabled"; }; mixer@1100000 { status = "disabled"; }; sound { status = "disabled"; }; }; }; fragment@1 { target-path = [2f 00]; __overlay__ { sound { status = "disabled"; }; }; }; };
  19. rocka

    A64 and the 3.10 kernel

    Can I test this image? Is it available?
  20. Thanks, sfx2000. But I'd already "disabled" IPv6 using that method. On my first Armbian setup attempts, no matter what I did, my system never got an IPv4 address. It only ever had an IPv6 (despite my network being IPv4.) Eventually I stumbled on that `armbian-config` option. Once "disabled" it allowed the system to get an IPv4. But despite what it says, it didn't "disable" IPv6 system wide. Tools like `ip addr` and `ifconfig` showed it still had IPv6 active.
  21. I had the same symptoms with the same type same brand of SD card - surely a fake !!! Your card report OK when written, you dont notice anything because the files you just modified are in the cache - until you reboot. You can reflash the card - you will apparently do it - and end up with the old system. Just throw it to the bin !
  22. Igor

    Le Potato general topics

    System is running, desktop too but nothing is on the screen ... but after a while [ 453.624128] random: crng init done [ 453.624143] random: 7 urandom warning(s) missed due to ratelimiting [ 454.842413] fuse init (API version 7.27) screen is back. while Debian based desktop works just fine. It looks like upstream troubles.
  23. gounthar

    Sunvell H3 2GB RAM + 16GB ROM TV Box

    Started up this small machine tonight, and I am impressed. It's the best version of Android I have seen on AllWinner Hx (ok, I only tried OrangePi's Android versions on the Zero and the One Plus). Pretty responsive, adb does work: $ adb connect already connected to $ adb devices List of devices attached device dolphin-fvd-p1:/ # cat /proc/cpuinfo cat /proc/cpuinfo processor : 0 model name : ARMv7 Processor rev 5 (v7l) BogoMIPS : 48.00 Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x0 CPU part : 0xc07 CPU revision : 5 processor : 1 model name : ARMv7 Processor rev 5 (v7l) BogoMIPS : 48.00 Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x0 CPU part : 0xc07 CPU revision : 5 Hardware : sun8iw7 Revision : 0000 Serial : 740078864424142508d1 I don't know Kodi well enough to test the functionalities, but it launched and gave me a few info. I will take some bad pics and post them. I don't know either what we could do with that, but there is this directory: dolphin-fvd-p1:/proc/device-tree # ls ls #address-cells dvfs_table prcm #size-cells firmware psci aliases gpu@0x01c40000 s_brom bt interrupt-controller@1c81000 soc@01c00000 btlpm interrupt-parent sunxi-chipid@01c14200 chosen ion sunxi-sid@01c14000 clocks memory@40000000 timer compatible model uboot cpus n_brom watchdog@01c20ca0 cpuscfg name wlan dram opp_dvfs_table dramfreq pmu The kernel is not that old: dolphin-fvd-p1:/proc # uname -a uname -a Linux localhost 4.4.55 #1 SMP PREEMPT Tue Aug 14 11:27:43 CST 2018 armv7l
  24. ... and I have build it and pushed to Armbian stable repository (Stretch, Xenial and Bionic; armhf+arm64). First boot scripts also creates CPUfreq config based on CPU count. More can be added if there is an interest ... Package can be installed via apt update and upgrade while auto config feature will work only on self made images.
  25. constantius

    Le Potato general topics

    Hi I have build Armbian Bionic 5.64 and 5.46 with XFCE desktop and system works only to the first reboot. After reboot i see only black screen. Kernels 4.18 and 4.16
  26. moved to p2p cause hardware but not really armbian related. not really, never had to deal with thermal zones for h3. go through the armbianmonitor related parts of the buidscript to get a clue.. if everything in kernel is there.. dt too then you've to nail down user-space... e.g. maybe we patched something as well.. I've really no idea. H3 was quite mature when I started to deal with such stuff...
  27. Hi, had the same problem here with bananapi. The LAN interface got no IPV4 Address, only IPV6 (over DHCP). I have removed networkmanager and assigned a static IPv4 Address in my router for the BPi board. That solved my problem. This is only a workaround, not a solution. I think the problem should be reproducible with the current Armbian distro. Steve
  28. I'll split it.. cause IMO we go a way of topic here... (last post from) which 'bpi kernel'? the 4.9 bsp, @frank-ws 4.14? If 4.9, well my interest is minor if nobody has a proper patchset for mainline.. I decided shortly after starting that I won't deal with the 4.9 kernel, the whole network part differs from their mainline implementation I had a lot of build errors and a kernel with no git history.. The only thing which looks sane to me is 4.19 (since LTS and support of MT7623 matured a lot.. there were changes in the network related stuff between 4.14 and 4.15 if I've it right in mind and I never want to deal with backports there.. Frank did or tried it and spend a lot of time to provide a kernel based on 4.14 - appreciated but to much efforts needed IMO, honestly the interest here was too low to put much efforts in it. Upstream U-boot needs some adjustments, basically it works/can work (it boots up, but I would need to write a proper bootscript and configure it properly ), a default network config is there (all RJ45 bridged) MTKs crypto kernelmodules are there. As long as this is a 'one man show' development is slow cause I don't use the R2 productive and I don't have projects which rely on it. It would be nice to separate IoT nodes from the rest of my network (e.g. keep insecure thingies separated). As long as nobody wants to contribute and test this will be AS IS. I may fix u-boot so that it properly boots into Linux and stick everything to 4.19. Hardware drivers for USB, SATA and network are there.. Wifi won't be there until its manilined (which likely never happens - and my interest in wifi is minor to port it). mPCI 'should' work (e.g. nothing suspicious in dmesg) HDMI is untested.
  1. Load more activity