All Activity

This stream auto-updates     

  1. Past hour
  2. My suggestion for potential solution is my post.
  3. Very nice work! Since I've been messing with the overclock overlays of late, I just dropped them in and everything works great (initial testing on a NEO2), including thermal management. dmesg seems clean as well! Seems super solid with cursory testing so far
  4. Today
  5. The DEV branch is now 5.8.y, commmitted this morning ...
  6. hardware issue -> human error
  7. USB turned out to be a hardware issue. I booted a FA image, and USB didn't work there either, so I re-seated the module and USB is now working perfectly.
  8. Then you should ask Tanix for help because we do not deal with 3rd party images here.
  9. _ ____ __ __ __ _ _ / \ | _ \| \/ | / /_ | || | / _ \ | |_) | |\/| |_____| '_ \| || |_ / ___ \| _ <| | | |_____| (_) |__ _| /_/ \_\_| \_\_| |_| \___/ |_| Welcome to Armbian Focal with Linux 5.7.0-rc2-arm-64 No end-user support: built from trunk & unsupported (focal) userspace! System load: 2.50 0.64 0.22 Up time: 0 min Memory usage: 17 % of 3797MB IP: 169.254.13.15 192.168.1.167 CPU temp: 69°C Usage of /: 18% of 29G storage/: 1% of 117G [ General system configuration (beta): armbian-config ] 294 updates can be installed immediately. 101 of these updates are security updates. To see these additional updates run: apt list --upgradable Last login: Tue Apr 28 13:19:17 2020 from 192.168.1.214 root@orangepi-arm-64:~# uname -a Linux orangepi-arm-64 5.7.0-rc2-arm-64 #20.05.3 SMP PREEMPT Sat Apr 25 13:17:40 MSK 2020 aarch64 aarch64 aarch64 GNU/Linux Hello, i run armbian on orange pi rk3399 , bun I don`t know how take ffmpeg accelerated and other ls -l /dev/vpu* /dev/rk* /dev/vpu* ls: cannot access '/dev/vpu*': No such file or directory ls: cannot access '/dev/rk*': No such file or directory ls: cannot access '/dev/vpu*': No such file or directory [ 33.917] (--) Log file renamed from "/var/log/Xorg.pid-1938.log" to "/var/log/Xorg.0.log" [ 33.921] X.Org X Server 1.20.8 X Protocol Version 11, Revision 0 [ 33.921] Build Operating System: Linux 4.4.0-177-generic aarch64 Ubuntu [ 33.921] Current Operating System: Linux orangepi-arm-64 5.7.0-rc2-arm-64 #20.05.3 SMP PREEMPT Sat Apr 25 13:17:40 MSK 2020 aarch64 [ 33.921] Kernel command line: root=LABEL=ROOTFS rootflags=data=writeback rw console=uart8250,mmio32,0xff1a0000 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 [ 33.921] Build Date: 06 April 2020 09:39:29AM [ 33.921] xorg-server 2:1.20.8-2ubuntu2 (For technical support please see http://www.ubuntu.com/support) [ 33.921] Current version of pixman: 0.38.4 [ 33.921] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 33.921] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 33.921] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Aug 7 15:17:24 2020 [ 33.929] (==) Using config directory: "/etc/X11/xorg.conf.d" [ 33.929] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 33.940] (==) No Layout section. Using the first Screen section. [ 33.941] (==) No screen section available. Using defaults. [ 33.941] (**) |-->Screen "Default Screen Section" (0) [ 33.941] (**) | |-->Monitor "<default monitor>" [ 33.949] (==) No device specified for screen "Default Screen Section". Using the first device section listed. [ 33.949] (**) | |-->Device "Default Device" [ 33.949] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 33.949] (**) Option "AutoAddGPU" "off" [ 33.949] (**) Option "Debug" "dmabuf_capable" [ 33.949] (==) Automatically adding devices [ 33.949] (==) Automatically enabling devices [ 33.949] (**) Not automatically adding GPU devices [ 33.949] (==) Automatically binding GPU devices [ 33.949] (==) Max clients allowed: 256, resource mask: 0x1fffff [ 33.982] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [ 33.982] Entry deleted from font path. [ 33.982] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist. [ 33.982] Entry deleted from font path. [ 33.982] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist. [ 33.982] Entry deleted from font path. [ 33.987] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist. [ 33.987] Entry deleted from font path. [ 33.987] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist. [ 33.987] Entry deleted from font path. [ 33.987] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/Type1, built-ins [ 33.987] (==) ModulePath set to "/usr/lib/xorg/modules" [ 33.987] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 33.987] (II) Loader magic: 0xaaaab21f4010 [ 33.987] (II) Module ABI versions: [ 33.987] X.Org ANSI C Emulation: 0.4 [ 33.987] X.Org Video Driver: 24.1 [ 33.987] X.Org XInput driver : 24.1 [ 33.987] X.Org Server Extension : 10.0 [ 33.989] (++) using VT number 2 [ 33.993] (II) systemd-logind: took control of session /org/freedesktop/login1/session/_32 [ 33.995] (II) xfree86: Adding drm device (/dev/dri/card0) [ 33.996] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 12 paused 0 [ 33.997] (II) xfree86: Adding drm device (/dev/dri/card1) [ 33.999] (II) systemd-logind: got fd for /dev/dri/card1 226:1 fd 13 paused 0 [ 34.000] (II) no primary bus or device found [ 34.000] falling back to /sys/devices/platform/display-subsystem/drm/card0 [ 34.000] (II) LoadModule: "glx" [ 34.006] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so [ 34.164] (II) Module glx: vendor="X.Org Foundation" [ 34.164] compiled for 1.20.8, module version = 1.0.0 [ 34.164] ABI class: X.Org Server Extension, version 10.0 [ 34.164] (II) LoadModule: "modesetting" [ 34.171] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so [ 34.183] (II) Module modesetting: vendor="X.Org Foundation" [ 34.183] compiled for 1.20.8, module version = 1.20.8 [ 34.183] Module class: X.Org Video Driver [ 34.184] ABI class: X.Org Video Driver, version 24.1 [ 34.184] (II) modesetting: Driver for Modesetting Kernel Drivers: kms [ 34.185] (II) modeset(0): using drv /dev/dri/card0 [ 34.186] (II) modeset(0): Creating default Display subsection in Screen section "Default Screen Section" for depth/fbbpp 24/32 [ 34.187] (==) modeset(0): Depth 24, (==) framebuffer bpp 32 [ 34.187] (**) modeset(0): Option "AccelMethod" "none" [ 34.187] (==) modeset(0): RGB weight 888 [ 34.187] (==) modeset(0): Default visual is TrueColor [ 34.187] (**) modeset(0): glamor disabled [ 34.187] (II) modeset(0): ShadowFB: preferred NO, enabled NO [ 34.187] (II) modeset(0): Output HDMI-1 has no monitor section [ 34.187] (II) modeset(0): EDID for output HDMI-1 [ 34.187] (II) modeset(0): Output HDMI-1 disconnected [ 34.187] (WW) modeset(0): No outputs definitely connected, trying again... [ 34.187] (II) modeset(0): Output HDMI-1 disconnected [ 34.187] (WW) modeset(0): Unable to find connected outputs - setting 1024x768 initial framebuffer [ 34.187] (==) modeset(0): Using gamma correction (1.0, 1.0, 1.0) [ 34.187] (==) modeset(0): DPI set to (96, 96) [ 34.187] (II) Loading sub module "fb" [ 34.187] (II) LoadModule: "fb" [ 34.194] (II) Loading /usr/lib/xorg/modules/libfb.so [ 34.201] (II) Module fb: vendor="X.Org Foundation" [ 34.201] compiled for 1.20.8, module version = 1.0.0 [ 34.201] ABI class: X.Org ANSI C Emulation, version 0.4 [ 34.223] (==) modeset(0): Backing store enabled [ 34.223] (==) modeset(0): Silken mouse enabled [ 34.231] (II) modeset(0): Initializing kms color map for depth 24, 8 bpc. [ 34.232] (==) modeset(0): DPMS enabled [ 34.232] (II) Initializing extension Generic Event Extension [ 34.232] (II) Initializing extension SHAPE [ 34.233] (II) Initializing extension MIT-SHM [ 34.234] (II) Initializing extension XInputExtension [ 34.237] (II) Initializing extension XTEST [ 34.238] (II) Initializing extension BIG-REQUESTS [ 34.239] (II) Initializing extension SYNC [ 34.239] (II) Initializing extension XKEYBOARD [ 34.240] (II) Initializing extension XC-MISC [ 34.240] (II) Initializing extension SECURITY [ 34.241] (II) Initializing extension XFIXES [ 34.242] (II) Initializing extension RENDER [ 34.242] (II) Initializing extension RANDR [ 34.243] (II) Initializing extension COMPOSITE [ 34.244] (II) Initializing extension DAMAGE [ 34.245] (II) Initializing extension MIT-SCREEN-SAVER [ 34.246] (II) Initializing extension DOUBLE-BUFFER [ 34.246] (II) Initializing extension RECORD [ 34.247] (II) Initializing extension DPMS [ 34.247] (II) Initializing extension Present [ 34.248] (II) Initializing extension DRI3 [ 34.248] (II) Initializing extension X-Resource [ 34.248] (II) Initializing extension XVideo [ 34.249] (II) Initializing extension XVideo-MotionCompensation [ 34.249] (II) Initializing extension SELinux [ 34.249] (II) SELinux: Disabled on system [ 34.249] (II) Initializing extension GLX [ 34.250] (II) AIGLX: Screen 0 is not DRI2 capable [ 37.380] (II) IGLX: Loaded and initialized swrast [ 37.380] (II) GLX: Initialized DRISWRAST GL provider for screen 0 [ 37.380] (II) Initializing extension XFree86-VidModeExtension [ 37.381] (II) Initializing extension XFree86-DGA [ 37.381] (II) Initializing extension XFree86-DRI [ 37.390] (II) Initializing extension DRI2 [ 37.391] (II) modeset(0): Damage tracking initialized [ 37.638] (II) config/udev: Adding input device adc-keys (/dev/input/event1) [ 37.638] (**) adc-keys: Applying InputClass "libinput keyboard catchall" [ 37.638] (II) LoadModule: "libinput" [ 37.638] (II) Loading /usr/lib/xorg/modules/input/libinput_drv.so [ 37.666] (II) Module libinput: vendor="X.Org Foundation" [ 37.666] compiled for 1.20.4, module version = 0.29.0 [ 37.666] Module class: X.Org XInput Driver [ 37.666] ABI class: X.Org XInput driver, version 24.1 [ 37.666] (II) Using input driver 'libinput' for 'adc-keys' [ 37.671] (II) systemd-logind: got fd for /dev/input/event1 13:65 fd 22 paused 0 [ 37.671] (**) adc-keys: always reports core events [ 37.671] (**) Option "Device" "/dev/input/event1" [ 37.671] (**) Option "_source" "server/udev" [ 37.695] (II) event1 - adc-keys: is tagged by udev as: Keyboard [ 37.695] (II) event1 - adc-keys: device is a keyboard [ 37.696] (II) event1 - adc-keys: device removed [ 37.696] (**) Option "config_info" "udev:/sys/devices/platform/adc-keys/input/input1/event1" [ 37.696] (II) XINPUT: Adding extended input device "adc-keys" (type: KEYBOARD, id 6) [ 37.696] (**) Option "xkb_model" "pc105" [ 37.696] (**) Option "xkb_layout" "us" [ 37.700] (II) event1 - adc-keys: is tagged by udev as: Keyboard [ 37.700] (II) event1 - adc-keys: device is a keyboard [ 37.703] (II) config/udev: Adding input device gpio-keys (/dev/input/event0) [ 37.703] (**) gpio-keys: Applying InputClass "libinput keyboard catchall" [ 37.703] (II) Using input driver 'libinput' for 'gpio-keys' [ 37.707] (II) systemd-logind: got fd for /dev/input/event0 13:64 fd 25 paused 0 [ 37.708] (**) gpio-keys: always reports core events [ 37.708] (**) Option "Device" "/dev/input/event0" [ 37.708] (**) Option "_source" "server/udev" [ 37.711] (II) event0 - gpio-keys: is tagged by udev as: Keyboard [ 37.711] (II) event0 - gpio-keys: device is a keyboard [ 37.711] (II) event0 - gpio-keys: device removed [ 37.711] (**) Option "config_info" "udev:/sys/devices/platform/gpio-keys/input/input0/event0" [ 37.711] (II) XINPUT: Adding extended input device "gpio-keys" (type: KEYBOARD, id 7) [ 37.711] (**) Option "xkb_model" "pc105" [ 37.711] (**) Option "xkb_layout" "us" [ 37.715] (II) event0 - gpio-keys: is tagged by udev as: Keyboard [ 37.715] (II) event0 - gpio-keys: device is a keyboard
  10. I'm not deeply familiar with those boards, but in doing some really quick checks it looks like indeed the hardware doesn't provide any means to get more voltage to the CPU, which means they wouldn't work... Yes, I've found in testing that it appears that the H2+/H3 can be pushed harder than the H5... I tested 1.3GHz on a couple H5s and couldn't get them stable above 1.2GHz (some other ones are fine, however). My OPi Zero has no issue, however...it's interesting. Also, note that with the way I created these overlays the passive cooling maps work properly, which means that the boards will clock down at the appropriate temperature thresholds, improving stability. You'll note that while your board clocked to 1368MHz early on, it spent the bulk of its time at 1200MHz due to thermals. This is good - it provides stability and will allow the board to clock to the maximum when it can.
  11. Hi all, I am trying to deploy Armbian_20.07_Arm-64_focal_current_5.7.9_desktop on a Mini M8S (S905, 2GB RAM, 8 GB Flash, Realtek 8723BS wifi). Everything works fine except the RAM that always gets detected as 800 Mbytes no matter what. From what I read here, this is an u-boot issue and tried different ones (the original one, the one from Armbian_5.44_S9xxx_Ubuntu_bionic_3.14.29_mate_20180729.img that seemed to detect all memory). Still no luck. I have no UART interface Please tell me, is there an available uboot version for the latest armbian releases that can detect the memory fine? Many thanks.
  12. There is no need to save those u-boot sectors since the original copy is already located in /usr/lib/linux-u-boot-dev-orangepi3_20.08.0-trunk_arm64/ for example.
  13. Instead of doing individual "cat /sys/bus/w1/devices/28-000003ebdd28/temperature" on each devices, I presume you can do multiple with "cat /sys/bus/w1/devices/*/temperature" ...
  14. Installing it manually does not work sudo apt install qemu-system-aarch64 root@nanopik1plus:~/testSnap# multipass start launch failed: Internal error: qemu-system-x86_64 failed getting vmstate (Process returned exit code: 1) with output: qemu-system-aarch64: -nographic: No machine specified, and there is no default Use -machine help to list supported machines
  15. I am trying to start snap multipass on the device nanopi k1 plus, getting the following error: root@nanopik1plus:~/testSnap# multipass start launch failed: Internal error: qemu-system-x86_64 failed getting vmstate (Process returned exit code: 1) with output: qemu-system-aarch64: -nographic: No machine specified, and there is no default Use -machine help to list supported machines
  16. Thanks for the reply bro! The firmware I downloaded from Tanix website and it is: TX6_H6_9_4Gddr_8822bs_20190228.img
  17. Hi, I am trying to install Armbian_20.07_Arm-64_buster_current_5.7.9.img onto the emmc (internal storage) of my TVBOX. Its a T95N S905X device with 1g RAM and 8g emmc. I followed the process at the start of this thread and I can get it running fine off of the micro sd card, using either/both of the meson-gxl-s905x-p212.dtb or meson-gxl-s905x-nexbox-a95x.dtb and I have successfully used the Amlogic USB burning tool to install and run stock firmware images for MXQPro, T95N, T95X and A95X-nexbox. I have tried without success once running ambian from the external microsd to install it to the intermal emmc using the /root/install-aml.sh or /root/install-aml-S905.sh. I have tried to debug why it does not work and it appears to come down to how the storage is seen by the kernel/OS. fdisk -l shows the emmc in the form of /dev/mmcblkX with /dev/mmcblkXp1 and /dev/mmcblkXp1 but the devices tree has them as /dev/mmcblkXboot0 and /dev/mmcblkXboot1. The X varies according to which dtb I use, its either 0 or 1. I tried renaming the /dev/xxxxxboot0 and 1 entries to match what fdisk and the script wants but it does not resolve the issue. Any pointers or solutions will be gratefully received, thanks
  18. so... on the first try, i was doing everything right. Didn't realize that SimpNAS is BETA and found my problem here LINK . Exept this, it work well...
  19. /dev/loop1 253M 253M 0 100% /snap/nextcloud/22408 Thank you. It looks like it is a SNAP install. Ubuntu's NC-Snap is known to be quiet reliable. Are you familiar with Ubuntu Snap? You can try to uninstall und re-install it yourself.
  20. You followed the link in the first post about tmon and looked around the directory where the README is located?
  21. The limit should be gone with the next cronjob.
  22. Thanks again. Any recommendations for the output?
  23. With new kernels the fan spins at "255" always, you can find the fan with this command sudo find /sys -name pwm1 | grep hwmon and then change the output to your setup - But on the new kernels the fan point can jump, i am not sure of what reason.
  24. One of the cards i have costed around 80euro, and it is almost useless.. The cheap cards is the best here, in my opinion.
  25. From my feel most of those are crap anyways and provide some weird/useles soft-raid solutions which can be realised via mdadm as well or even rely on that...
  1. Load more activity