All Activity

This stream auto-updates     

  1. Today
  2. So this means basically more efforts to be done before the orangepioneplus board will have 1,8GHz using the " cpufreq-dt " driver. cheers for clarifying
  3. First attempt (5.5-rc2), thanks to @megi who added rc2 to the 5.5-branch This build resulted in compile errors at once, which was to be expected. Just reporting here in case DEV will be switched to 5.5 this month. The log attached holds "duplicate_label" as "well duplicate_node_names"-errors. compilation.log
  4. Hi, I am using Armbian_19.11.3_Rockpi-4b_buster_current_5.3.11_desktop. Facing issue when trying to use USB devices in the upper USB 3 port on a Rock Pi 4 v1.3. This port also supports USB OTG. The switch is set to Host mode. The storage is detected occasionally, while most of the time it does not work. dmesg contains no reference to the connected storage: $ dmesg | grep usb [ 0.000000] Kernel command line: root=UUID=590fca6f-9771-4245-86a7-34712bfe535b rootwait rootfstype=ext4 console=ttyS2,1500000 console=tty1 panic=10 consoleblank=0 loglevel=1 ubootpart=7ef2aff3-01 usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1 [ 5.284733] usbcore: registered new interface driver usbfs [ 5.287156] usbcore: registered new interface driver hub [ 5.292587] usbcore: registered new device driver usb [ 50.127245] usbcore: registered new interface driver pegasus [ 50.129170] usbcore: registered new interface driver rtl8150 [ 50.132096] usbcore: registered new interface driver r8152 [ 50.134404] usbcore: registered new interface driver dm9601 [ 50.136578] usbcore: registered new interface driver CoreChips [ 50.139442] usbcore: registered new interface driver smsc75xx [ 50.141440] usbcore: registered new interface driver smsc95xx [ 50.143765] usbcore: registered new interface driver plusb [ 50.145608] usbcore: registered new interface driver MOSCHIP usb-ethernet driver [ 50.374451] ehci-platform fe380000.usb: EHCI Host Controller [ 50.375497] ehci-platform fe380000.usb: new USB bus registered, assigned bus number 1 [ 50.381185] ehci-platform fe380000.usb: irq 31, io mem 0xfe380000 [ 50.395266] ehci-platform fe380000.usb: USB 2.0 started, EHCI 1.00 [ 50.408238] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.03 [ 50.408790] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 50.409190] usb usb1: Product: EHCI Host Controller [ 50.409557] usb usb1: Manufacturer: Linux 5.3.11-rockchip64 ehci_hcd [ 50.410635] usb usb1: SerialNumber: fe380000.usb [ 50.468500] ehci-platform fe3c0000.usb: EHCI Host Controller [ 50.469493] ehci-platform fe3c0000.usb: new USB bus registered, assigned bus number 2 [ 50.475359] ehci-platform fe3c0000.usb: irq 33, io mem 0xfe3c0000 [ 50.491432] ehci-platform fe3c0000.usb: USB 2.0 started, EHCI 1.00 [ 50.501308] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.03 [ 50.502470] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 50.502888] usb usb2: Product: EHCI Host Controller [ 50.503283] usb usb2: Manufacturer: Linux 5.3.11-rockchip64 ehci_hcd [ 50.503650] usb usb2: SerialNumber: fe3c0000.usb [ 50.585291] ohci-platform fe3a0000.usb: Generic Platform OHCI controller [ 50.587119] ohci-platform fe3a0000.usb: new USB bus registered, assigned bus number 3 [ 50.592909] ohci-platform fe3a0000.usb: irq 32, io mem 0xfe3a0000 [ 50.664813] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 5.03 [ 50.665289] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 50.666380] usb usb3: Product: Generic Platform OHCI controller [ 50.666764] usb usb3: Manufacturer: Linux 5.3.11-rockchip64 ohci_hcd [ 50.667113] usb usb3: SerialNumber: fe3a0000.usb [ 50.720807] ohci-platform fe3e0000.usb: Generic Platform OHCI controller [ 50.722470] ohci-platform fe3e0000.usb: new USB bus registered, assigned bus number 4 [ 50.728607] ohci-platform fe3e0000.usb: irq 34, io mem 0xfe3e0000 [ 50.799943] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 5.03 [ 50.800404] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 50.800802] usb usb4: Product: Generic Platform OHCI controller [ 50.801176] usb usb4: Manufacturer: Linux 5.3.11-rockchip64 ohci_hcd [ 50.801528] usb usb4: SerialNumber: fe3e0000.usb [ 50.897341] usbcore: registered new interface driver usb-storage [ 52.303330] usbcore: registered new interface driver usbhid [ 52.303335] usbhid: USB HID core driver [ 53.090803] OF: graph: no port node found in /syscon@ff770000/usb2-phy@e450/otg-port [ 53.093318] usb usb5: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.03 [ 53.093324] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 53.093329] usb usb5: Product: xHCI Host Controller [ 53.093334] usb usb5: Manufacturer: Linux 5.3.11-rockchip64 xhci-hcd [ 53.093338] usb usb5: SerialNumber: xhci-hcd.0.auto [ 53.095135] usb usb6: We don't know the algorithms for LPM for this host, disabling LPM. [ 53.095238] usb usb6: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.03 [ 53.095244] usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 53.095249] usb usb6: Product: xHCI Host Controller [ 53.095253] usb usb6: Manufacturer: Linux 5.3.11-rockchip64 xhci-hcd [ 53.095257] usb usb6: SerialNumber: xhci-hcd.0.auto [ 53.100145] usb usb7: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.03 [ 53.100150] usb usb7: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 53.100155] usb usb7: Product: xHCI Host Controller [ 53.100160] usb usb7: Manufacturer: Linux 5.3.11-rockchip64 xhci-hcd [ 53.100164] usb usb7: SerialNumber: xhci-hcd.1.auto [ 53.101778] usb usb8: We don't know the algorithms for LPM for this host, disabling LPM. [ 53.101822] usb usb8: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.03 [ 53.101825] usb usb8: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 53.101828] usb usb8: Product: xHCI Host Controller [ 53.101830] usb usb8: Manufacturer: Linux 5.3.11-rockchip64 xhci-hcd [ 53.101833] usb usb8: SerialNumber: xhci-hcd.1.auto [ 54.194069] usb 8-1: new SuperSpeed Gen 1 USB device number 2 using xhci-hcd [ 54.219860] usb 8-1: New USB device found, idVendor=8564, idProduct=1000, bcdDevice=11.00 [ 54.219871] usb 8-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 54.219878] usb 8-1: Product: Mass Storage Device [ 54.219885] usb 8-1: Manufacturer: JetFlash [ 54.219892] usb 8-1: SerialNumber: 72Z6UO7B9R2GAU45 [ 54.221852] usb-storage 8-1:1.0: USB Mass Storage device detected [ 54.223204] scsi host0: usb-storage 8-1:1.0 [ 54.228901] usbcore: registered new interface driver uas [ 59.801887] phy phy-ff770000.syscon:usb2-phy@e450.2: charger = USB_DCP_CHARGER It works with the Radxa Debian Stretch image with Linux 4.4.154-99-rockchip-g5b699a48544d: [ 3.117507] rockchip-dwc3 usb0: USB HOST connected [ 3.426644] usb 8-1: new SuperSpeed USB device number 2 using xhci-hcd [ 3.444057] usb 8-1: New USB device found, idVendor=0080, idProduct=a001 [ 3.444673] usb 8-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 3.445322] usb 8-1: Product: External USB 3.0 [ 3.445735] usb 8-1: Manufacturer: TOSHIBA [ 3.446113] usb 8-1: SerialNumber: 201503310007F [ 4.138675] usb 7-1: new SuperSpeed USB device number 2 using xhci-hcd [ 4.160143] usb 7-1: New USB device found, idVendor=8564, idProduct=1000 [ 4.160746] usb 7-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 4.161370] usb 7-1: Product: Mass Storage Device [ 4.161788] usb 7-1: Manufacturer: JetFlash [ 4.162159] usb 7-1: SerialNumber: 72Z6UO7B9R2GAU45 [ 4.420405] usb-storage 7-1:1.0: USB Mass Storage device detected [ 4.430414] scsi host0: usb-storage 7-1:1.0 [ 4.431253] usbcore: registered new interface driver usb-storage [ 4.438119] usbcore: registered new interface driver uas So I am guessing its a kernel issue. Thanks for your work.
  5. Understand, but there is little we can do about. We need to adjust software. Perhaps help develop support? Its heavily sponsored from our private time which is currently covered less than 0.5%. We - people that move things forward - are 10 - 50 x too small to fix thing with the speed average user expects You are frustrated since things are not working, we as well since we can't do much about ...
  6. Oh I'm not using it for real just trying to do something useful with it as I am with the M4 V1 , I only bought the V2 because they seem to have discontinued the V1 4gb model which is a pity as Armbian is rock solid on those.
  7. I fixed device tree file for my X96Air. Now wifi and ethernet work. In file phy-mode is changed from rgii to rgmii and added some strings from other file for this mode. Network, BT work good, audio is not, and i've some error In log: Dec 16 05:48:39 rk3399 kernel: OCFS2 User DLM kernel interface loaded Dec 16 05:48:39 rk3399 kernel: EINJ: ACPI disabled. Dec 16 05:48:39 rk3399 kernel: mmc0: queuing unknown CIS tuple 0x80 (2 bytes) Dec 16 05:48:39 rk3399 kernel: mmc0: queuing unknown CIS tuple 0x80 (3 bytes) Dec 16 05:48:39 rk3399 kernel: mmc0: queuing unknown CIS tuple 0x80 (3 bytes) Dec 16 05:48:39 rk3399 kernel: mmc0: queuing unknown CIS tuple 0x80 (7 bytes) Dec 16 05:48:39 rk3399 kernel: mmc0: queuing unknown CIS tuple 0x81 (9 bytes) Dec 16 05:48:39 rk3399 kernel: meson8b-dwmac ff3f0000.ethernet: IRQ eth_wake_irq not found Dec 16 05:48:39 rk3399 kernel: meson8b-dwmac ff3f0000.ethernet: IRQ eth_lpi not found Dec 16 05:48:39 rk3399 kernel: meson8b-dwmac ff3f0000.ethernet: PTP uses main clock Dec 16 05:48:39 rk3399 kernel: dwc2 ff400000.usb: ff400000.usb supply vusb_d not found, using dummy regulator Dec 16 05:48:39 rk3399 kernel: dwc2 ff400000.usb: ff400000.usb supply vusb_a not found, using dummy regulator Dec 16 05:48:39 rk3399 kernel: dwc3 ff500000.usb: Failed to get clk 'ref': -2 Dec 16 05:48:39 rk3399 kernel: gpio-keys gpio-keys: Unable to get irq number for GPIO 0, error -6 Dec 16 05:48:39 rk3399 systemd[1]: Failed to bump fs.file-max, ignoring: Invalid argument Dec 16 05:48:39 rk3399 kernel: meson-g12a-pinctrl ff634400.bus:pinctrl@40: pin GPIOZ_2 already requested by ff3f0000.ethernet; cannot claim for ff661000.audio-control Dec 16 05:48:39 rk3399 kernel: meson-g12a-pinctrl ff634400.bus:pinctrl@40: pin-2 (ff661000.audio-controller) status -22 Dec 16 05:48:39 rk3399 kernel: meson-g12a-pinctrl ff634400.bus:pinctrl@40: could not request pin 2 (GPIOZ_2) from group pdm_din0_z on device pinctrl-meson Dec 16 05:48:39 rk3399 kernel: axg-pdm ff661000.audio-controller: Error applying setting, reverse things back Dec 16 05:48:39 rk3399 kernel: axg-pdm: probe of ff661000.audio-controller failed with error -22 Dec 16 05:48:39 rk3399 systemd-udevd[505]: link_config: could not get ethtool features for eth0 Dec 16 05:48:39 rk3399 systemd-udevd[505]: Could not set offload features of eth0: Device or resource busy Dec 16 05:48:39 rk3399 kernel: debugfs: Directory 'ff800280.cec' with parent 'regmap' already present! Dec 16 05:48:40 rk3399 kernel: meson_vdec: module is from the staging directory, the quality is unknown, you have been warned. Dec 16 05:48:40 rk3399 kernel: platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 Dec 16 05:48:40 rk3399 kernel: platform regulatory.0: Falling back to sysfs fallback for: regulatory.db Dec 16 05:48:40 rk3399 kernel: brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6 Dec 16 05:48:40 rk3399 kernel: brcmfmac mmc0:0001:1: Direct firmware load for brcm/brcmfmac43455-sdio.seirobotics,sei610.txt failed with error -2 Dec 16 05:48:40 rk3399 kernel: brcmfmac mmc0:0001:1: Falling back to sysfs fallback for: brcm/brcmfmac43455-sdio.seirobotics,sei610.txt Dec 16 05:48:40 rk3399 kernel: bluetooth hci1: Direct firmware load for brcm/BCM4345C0.hcd failed with error -2 Dec 16 05:48:40 rk3399 kernel: bluetooth hci1: Falling back to sysfs fallback for: brcm/BCM4345C0.hcd Dec 16 05:48:41 rk3399 kernel: meson8b-dwmac ff3f0000.ethernet eth0: PTP not supported by HW Dec 16 05:48:41 rk3399 kernel: ext4 filesystem being mounted at /var/log supports timestamps until 2038 (0x7fffffff) Dec 16 05:48:42 rk3399 kernel: brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6 Dec 16 05:48:43 rk3399 kernel: brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Feb 27 2018 03:15:32 version 7.45.154 (r684107 CY) FWID 01-4fbe0b04
  8. It's an upstream known problem https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867779 but ... but why do you need icon theme for Nanopiduo 2? How did you start making an image?
  9. It will upgrade to more recent DEV kernels if you will run apt update and upgrade unless you choose to freeze kernel updating in armbian config or manually (not recommended).
  10. Need to do more tests to find out where is the source of this trouble. M4 V2 image is still labelled as "testing" - it is expected that you will not use it for real yet - which means this is not a big problem yet. But yes, we have to fix it.
  11. The OPP table change has quite a story behind but that is another thing. Anyway. Armbians patch containing 1.8GHz as well as far as I understand. It just alters the voltages. https://github.com/armbian/build/blob/master/patch/kernel/sunxi-dev/0012-general-h6-new-opp-table.patch
  12. thanks t-bob , i changed to other kernels in armbian-config and choose 5.4.2-sunxi64 #19.11.3.349 now i have buster with kernel 5.4.2. hope apt update ,apt upgrade wont mess it up.
  13. The network card driver is no problem, because I test it in different device with the same network card driver, and the route is default. With some tests and capturing the network packet, I find that sometimes the network MSI interrupt is no reply, so is it related to the 3720's pcie driver and compatibility when it is OK in other test device?
  14. T95Z s912 boots to desktop, no hdmi audio
  15. I've been trying to build a nanopiduo2 firmware for the last couple of days, and I keep getting an error on the 048-humanity-icon-theme_0.6.15_all.deb. It says corrupted filesystem tarball. I don't know where to report this. Is this a packaging error in Armbian or Ubuntu? I'm trying to build the bionic firmware. Any suggestions on getting around this error would be much appreciated.
  16. @balbles150 and NicoD, Great job guys. Latest version tested with mesa on a S912. Panfrost is incredibly promising. I've tried with plasma-desktop ant its effects. It's going to be highly usable for a pocket GNU/Linux desktop computer (on a TV Box). But for the time being it crashes a lot with plasma on my personal configuration. Edit: by disabling many effects of the compositor, it is possible to launch many applications including LibreOffice. There are some issues with the mask of the X cursor arrow, the shadows around the windows... But it's very exciting anyway.
  17. Yesterday
  18. I don't think waiting will help. I almost never update non-rc branches after release, I only merge from linux-stable. Anyway, I can only see you're missing 1.8GHz, because Armbian changes my CPU OPP table to something else, because my OPP table has 1.8GHz operating point. https://megous.com/git/linux/commit/?h=ths-5.4&id=8bad58044be498d409400dbf9757f2ae25c6ad9d
  19. check 1/ kernel settings, eg: net.core.default_qdisc = fq net.ipv4.tcp_congestion_control = bbr net.core.rmem_max = 16777216 net.core.wmem_max = 16777216 net.ipv4.tcp_rmem = 4096 87380 16777216 net.ipv4.tcp_wmem = 4096 87380 16777216 net.ipv4.tcp_fastopen = 3 net.ipv4.tcp_no_metrics_save = 1 net.ipv4.tcp_slow_start_after_idle = 0 net.ipv4.tcp_timestamps = 0 2/ openvpn settings, eg; sndbuf 393216 rcvbuf 393216 push "sndbuf 393216" push "rcvbuf 393216" comp-lzo no #No need for streaming fast-io #Optimize I/O writes tls-version-min 1.2 remote-cert-tls client cipher AES-128-CBC ncp-disable auth SHA256 auth-nocache both ends have h5 (neo2 lts) currently and get upload/download of >100Mbit over VPN tunnel BTW kernel 5.3.9 shows on this board lower values so you should easily get 100Mbit openssl speed -evp aes-128-cbc -elapsed :~# openssl speed -evp aes-128-cbc -elapsed You have chosen to measure elapsed time instead of user CPU time. Doing aes-128-cbc for 3s on 16 size blocks: 12715522 aes-128-cbc's in 3.00s Doing aes-128-cbc for 3s on 64 size blocks: 10201155 aes-128-cbc's in 3.00s Doing aes-128-cbc for 3s on 256 size blocks: 5342908 aes-128-cbc's in 3.00s Doing aes-128-cbc for 3s on 1024 size blocks: 1919464 aes-128-cbc's in 3.00s Doing aes-128-cbc for 3s on 8192 size blocks: 274635 aes-128-cbc's in 3.00s Doing aes-128-cbc for 3s on 16384 size blocks: 138772 aes-128-cbc's in 3.00s OpenSSL 1.1.1a 20 Nov 2018 built on: Thu Nov 22 18:40:54 2018 UTC options:bn(64,64) rc4(char) des(int) aes(partial) blowfish(ptr) compiler: gcc -fPIC -pthread -Wa,--noexecstack -Wall -Wa,--noexecstack -g -O2 -fdebug-prefix-map=/build/openssl-d3BJKw/openssl-1.1.1a=. -fstack-protector-strong -Wformat -Werror=format-security -DOPENSSL_USE_NODELETE -DOPENSSL_PIC -DOPENSSL_CPUID_OBJ -DOPENSSL_BN_ASM_MONT -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DKECCAK1600_ASM -DVPAES_ASM -DECP_NISTZ256_ASM -DPOLY1305_ASM -DNDEBUG -Wdate-time -D_FORTIFY_SOURCE=2 The 'numbers' are in 1000s of bytes per second processed. type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes 16384 bytes aes-128-cbc 67816.12k 217624.64k 455928.15k 655177.05k 749936.64k 757880.15k
  20. agreed, was just following the Jira stories and noticed AR-86 is not fully solved, just wanted to report back and that is it. So I do not want to put any rush on this, but at least we know now it is not fully solved yet. As said once I see either branch or kernel being updated will spin up another test drive. cheers for your efforts as you know it is appreciated!
  21. Thank you for report. Development needs time and this problem is far far from critical. We use the same branch. Just lots of patches which could also break something ... some work has to be applied.
  22. in which I can contribute to test, as I owe the "orangepioneplus" ( pihole and ovpn server ) as well a spare, so excellent for testing purposes Yet as we unfortunately can see it is not showing 1,8 which I reported also 5 December: root@orangepioneplus's password: ___ ____ _ ___ / _ \| _ \(_) / _ \ _ __ ___ _ | | | | |_) | | | | | | '_ \ / _ \_| |_ | |_| | __/| | | |_| | | | | __/_ _| \___/|_| |_| \___/|_| |_|\___| |_| Welcome to Armbian buster with Linux 5.4.2-sunxi64 System load: 0.27 0.24 0.10 Up time: 2 min Memory usage: 7 % of 989MB IP: 192.168.10.121 CPU temp: 45°C Usage of /: 4% of 15G root@orangepioneplus:~# cpufreq-info |grep cpufreq cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to cpufreq@vger.kernel.org, please. driver: cpufreq-dt available cpufreq governors: conservative, userspace, powersave, ondemand, performance, schedutil cpufreq stats: 480 MHz:91.69%, 720 MHz:0.53%, 816 MHz:0.02%, 888 MHz:0.25%, 1.08 GHz:0.28%, 1.32 GHz:0.48%, 1.49 GHz:6.74% (147) driver: cpufreq-dt available cpufreq governors: conservative, userspace, powersave, ondemand, performance, schedutil cpufreq stats: 480 MHz:91.69%, 720 MHz:0.53%, 816 MHz:0.02%, 888 MHz:0.25%, 1.08 GHz:0.28%, 1.32 GHz:0.48%, 1.49 GHz:6.74% (147) driver: cpufreq-dt available cpufreq governors: conservative, userspace, powersave, ondemand, performance, schedutil cpufreq stats: 480 MHz:91.69%, 720 MHz:0.53%, 816 MHz:0.02%, 888 MHz:0.25%, 1.08 GHz:0.28%, 1.32 GHz:0.48%, 1.49 GHz:6.74% (147) driver: cpufreq-dt available cpufreq governors: conservative, userspace, powersave, ondemand, performance, schedutil cpufreq stats: 480 MHz:91.69%, 720 MHz:0.53%, 816 MHz:0.02%, 888 MHz:0.25%, 1.08 GHz:0.28%, 1.32 GHz:0.48%, 1.49 GHz:6.74% (147) Will give it another shot once @megi has 5.4.3 incorporated in orangepi-5.4 branch, both default and with the " Allwinner nvmem based SUN50I CPUFreq " driver
  23. Is there maybe a problem with the driver which occurs because you connect all 3 network adapters with each other (via the switch)? only logical conclusion for me, because you said connecting to all 3 with different devices works. Maybe some layer 2/3 routing problem?
  24. hello try to flash to eMMC without success it is bricked, only boots from sdcard, the risk is minimal I keep play with it with sdcard.... version used : Armbian_5.88_Aml-s905_Ubuntu_bionic_default_5.1.0_20190530 log ``` root@s905w-1:~# ./install.sh Start script create MBR and filesystem Start backup u-boot default dd: failed to open '/dev/mmcblk1': No such file or directory Start create MBR and partittion Error: Could not stat device /dev/mmcblk1 - No such file or directory. Error: Could not stat device /dev/mmcblk1 - No such file or directory. Error: Could not stat device /dev/mmcblk1 - No such file or directory. Start restore u-boot dd: failed to open '/boot/u-boot-default.img': No such file or directory dd: failed to open '/boot/u-boot-default.img': No such file or directory Done Start copy system for eMMC. Formatting BOOT partition...mkfs.fat 4.1 (2017-01-24) mkfs.vfat: unable to open /dev/mmcblk1p1: No such file or directory done. mount: /ddbr/install: special device /dev/mmcblk1p1 does not exist. Cppying BOOT...done. Edit init config...done. umount: /ddbr/install: not mounted. Formatting ROOT partition... The file /dev/mmcblk1p2 does not exist and no size was specified. e2fsck 1.44.1 (24-Mar-2018) e2fsck: No such file or directory while trying to open /dev/mmcblk1p2 Possibly non-existent device? done. Copying ROOTFS. mount: /ddbr/install: special device /dev/mmcblk1p2 does not exist. Copy BIN Create DEV Copy ETC Copy HOME Copy LIB Create MEDIA Create MNT Copy OPT Create PROC Copy ROOT Create RUN Copy SBIN Copy SELINUX Copy SRV Create SYS Create TMP Copy USR Copy VAR Copy fstab umount: /ddbr/install: not mounted. ******************************************* Complete copy OS to eMMC ******************************************* ``` thanks to all
  25. OK, so I'm seeing the same behavior with HK's image. I have sample code in my OpenCV install script. https://github.com/sgjava/install-opencv/blob/master/opencv-python/codeferm/writer.py just takes a source video and encodes it to whatever Four CC is set. If I use X264 or H264 I get: %Cpu(s): 9.9 us, 1.1 sy, 24.6 ni, 63.2 id, 0.0 wa, 1.0 hi, 0.2 si, 0.0 st 2019-12-15 12:47:40,293 INFO writer OpenCV 4.2.0-pre 2019-12-15 12:47:40,294 INFO writer Input file: ../../resources/traffic.mp4 2019-12-15 12:47:40,294 INFO writer Output file: ../../output/writer-python.avi 2019-12-15 12:47:40,354 INFO writer Resolution: 480x360 2019-12-15 12:47:52,655 INFO writer 925 frames 2019-12-15 12:47:52,656 INFO writer 75.3 FPS, elapsed time: 12.29 seconds 859844 Dec 15 12:53 writer-python.avi With XVID (MP4 simple profile) I get: %Cpu(s): 9.9 us, 0.4 sy, 0.0 ni, 89.1 id, 0.0 wa, 0.5 hi, 0.0 si, 0.0 st 2019-12-15 12:50:05,547 INFO writer OpenCV 4.2.0-pre 2019-12-15 12:50:05,547 INFO writer Input file: ../../resources/traffic.mp4 2019-12-15 12:50:05,547 INFO writer Output file: ../../output/writer-python.avi 2019-12-15 12:50:05,608 INFO writer Resolution: 480x360 2019-12-15 12:50:21,139 INFO writer 925 frames 2019-12-15 12:50:21,139 INFO writer 59.6 FPS, elapsed time: 15.52 seconds 3025586 Dec 15 12:50 writer-python.avi I love the smaller file I get with H264, but the CPU overhead is much larger than I though it would be using hardware encoding. I'm going to play around with ffmpeg directly and see if I'm seeing the same issues.
  1. Load more activity