All Activity

This stream auto-updates     

  1. Past hour
  2. like with ssd most interesting param for us in sd it's random i/o speed. It can variable in one products line and it can be lower with time.
  3. Today
  4. If you have 16 GB to place the system in eMMC (by the way, this is the right decision not to use modules, modules do more harm than good), 8 MB is enough to place the bootloader. You can have two versions of the bootloader in SPI at the same time, one working and the second backup (when updating the bootloader, a backup is used, if it starts and works correctly, the system automatically switches to it). eMMC is optimally used to accommodate the working system, and the bootloader to make in SPI (ie, use the principle of the PC, SPI = BIOS, eMMC = system HDD). Now already tested u-boot for full system startup from USB to RK3399. On RK33xx, the process of installing the system from external media in eMMC works well. The system installed in eMMC supports full kernel and system updates, as on normal Linux PCs with the usual "apt" commands. IMHO presence of HDMI port (for example instead of SD card), it would be useful, it allows to simplify considerably system maintenance and expands possibilities of use of this Board.
  5. try to cd ./DPO_MT7601U_LinuxSTA_3.0.0.4_20130913/ make make install at the first make you may need a type of system (like linux, arm - but this info could be found in the make file) BUT drivers-source from 2013 may not work see also: In actual (dev) versions of armbian the driver/firmware seems to be included: Debian Buster with Armbian Linux 5.3.6-sunxi64 package bsp-kernel[5.98.191016] u-boot[5.98] dtb[5.98.191016] firmware[5.98] config[5.98] root@npi-neo-core2( find / -name *7601* /lib/firmware/mt7601.bin /lib/firmware/mt7601u.bin /lib/modules/5.3.6-sunxi64/kernel/drivers/net/wireless/mediatek/mt7601u /lib/modules/5.3.6-sunxi64/kernel/drivers/net/wireless/mediatek/mt7601u/mt7601u.ko
  6. Ok thanks but i want to know what is that mean specifically
  7. Hi All, Just wanted to share a good story using armbian. I have used in the past 1-wire probes for temperature, and the process included decompiling, editing and recompiling dtb for my Banana Pi M1, which was not easy at all. Every firmware update deleted by changes and had to redo de recompilation. With latest kernels and armbian version, the process is now extremely easy, just edit: /boot/armbianEnv.txt Adding this lines: overlays=w1-gpio param_w1_pin=PI3 # desired pin(7th pin (GCLK) or number 4 on first column where number 1 is +3V) param_w1_pin_int_pullup=1 # internal pullup-resistor: 1=on, 0=off I just struggled a little bit to find the GPIO code (decompiled dtb and checked possible candidates). Information about temperature is here: cat /sys/bus/w1/devices/XX-YYYYYYY[this is your probe serial, if you have more they will be in /sys/bus/w1/devices/] /w1_slave You have plenty of information here, but don't need to do all they explain, just my edition has been enough:
  8. I think you may want to have a look to some page teaching the basics of Linux, like this one:
  9. I'm not sure I understand the question, but I'm using Panfrost (or at least trying to), which as far as I understand, is the blob-less driver. Not quite sure whether mesa from packages is actually configured with panfrost support, though, is there a way to check that?
  11. What is that mean Is a directory??
  12. Amlogic is currently working on their app which unstable right now. But once they work it around it should have the same functionality as team viewer for android i believe.
  13. There was a critical vulnerability found in Realtek wireless drivers: The vulnerability has been assigned CVE-2019-17666 and a patch proposed: I would like to get some statement if Armbian users are affected and if yes when is the patch going to be released Thanks
  14. You need to write the u-boot loader with two commands. Then the partition table is saved. dd of=/dev/mmcblk0 conv=fsync bs=1 count=442 dd of=/dev/mmcblk0 conv=fsync bs=512 skip=1 seek=1 You tried for eMMC the second file (u-boot.bin)?
  15. I checked on old USB 2.0 flash drives, reboot and shutdown work. I notice on different TV box models that rebooting and shutting down work better on slow devices than on fast ones.
  16. Thanks Igor, that would be enough, I guess.
  17. That is a good idea but I comes with the burden of the maintenance. Alternative option is that we add three badges H264D H264E H264T under "Specifications" at download pages and give you access that you can do that?
  18. -> system -> hardware Armbian is proper Linux and UART ports in our world are named as expected /dev/ttyS0 /dev/ttyS1 ...
  19. yes, like a mouse, keyboard it works, by the way when I use lsusb the wifi dongle show up but it didn't show the available network .
  20. sorry.. i just saw your reply. the repo is state at above : is this what you mean? if you mean repo for debian i just used default
  21. Yesterday
  22. HI, I have OrangePiPc and need to activate 3 uart (TX-RX) pins as system serial ports (/dev/ttyAMA0, /dev/ttyAMA1, /dev/ttyAMA2) how do it?
  23. Have you tried plugging anything else into the usb port? Did it work? Like a usb flash, another wifi dongle or usb-hdd?
  24. Sorry if I hijack the thread, I hesitated with creating another one. I am still struggling with the OrangePi RK3399 regarding the h.264 encoding of the HDMI-IN and the camera. For the time being, I use a hardware h.264 encoder (TBS2605), but still have the project to use ARM SoCs running Armbian. I've seen other threads on other SoCs able to do hardware encoding, so I was wondering if we could make a table with all the information regarding h.264 encoding and transcoding on various SoCs and SBCs more or less handled by Armbian. h.264 encoding boards Name h.264 decoding h.264 encoding h.264 transcode Tests done on Armbian OrangePi RK3399 Y N N N (OrangePi Debian) What do you think of my proposal? Thanks.
  25. @jcaron Are You using mesa on t720 or mali blob?
  26. I tried to configure it with nmtui but it didn't work
  1. Load more activity