All Activity

This stream auto-updates     

  1. Today
  2. Thanks for the quick response
  3. Yesterday
  4. Hello, I managed to bump the rockchip-dev kernel to 5.3.y on my fork. After removing a couple of redundant patches and updating two or three of them I'm able to compile with no problems. The new kernel also boots fine on my rk3288. Don't know if anyone is already working on this (maybe @Igor or @TonyMac32), if my work can ease someone's else fatigue I can make a merge request from my repo to main armbian repo for code review (the single commit is here) documenting the steps I did.
  5. CPU temp: 62°C Usage of /: 61% of 7.1G Last login: Tue Sep 17 08:51:11 2019 from 192.168.178.20 root@orangepi3:~# cpufreq-info |grep governor available cpufreq governors: conservative, userspace, powersave, ondemand, performance, schedutil The governor "ondemand" may decide which speed to use available cpufreq governors: conservative, userspace, powersave, ondemand, performance, schedutil The governor "ondemand" may decide which speed to use available cpufreq governors: conservative, userspace, powersave, ondemand, performance, schedutil The governor "ondemand" may decide which speed to use available cpufreq governors: conservative, userspace, powersave, ondemand, performance, schedutil The governor "ondemand" may decide which speed to use not sure why the output was 4 times the same, but that is how it looked on my side.
  6. Thank you again. I will try to remove the cache and try again. But it seems to have worked as I just ran "./compile.sh" without removing the cache:
  7. Not possible to replicate. Remove cache and try again.
  8. @rawaaw Good job. Have you tried if it is actually working? I don't get any results from hcitool scan And there is an error in dmesg when the device is initialized as described by you above: [ 3068.025249] Bluetooth: hci1: command 0x1003 tx timeout But I have the feeling we are almost there, at least for the OPi Lite2 When I try specific parameters for hciattach, I get the following: root@orangepilite2:~# hciattach /dev/ttyS1 bcm43xx 921600 noflow - bcm43xx_init Patch not found, continue anyway Set Controller UART speed to 921600 bit/s Device setup complete root@orangepilite2:~# hciconfig hci1 up Can't init device hci1: Connection timed out (110)
  9. Thank you very much for responding. I am new to the build process. I just cloned the "build" repository from github, ran "compile.sh", and followed the menus popped up from there. My build environment is a Ubuntu 18.04.3 x86_64 VM with 12GB RAM. The log is attached. compilation.log
  10. w1 works Armbian_5.83_Bananapim3_Debian_stretch_next_4.19.38.img there onewire@0 { compatible = "w1-gpio"; gpios = <&pio 4 4 0>; /* pin 37 */ status = "okay"; };
  11. Previously running a different Linux, I followed the instructions to update the boot loader so I could try Armbian on my Espressobin. The update completed ok, but could no longer read from the SD card. After several hours of frustration, I attempted to revert back to the original boot loader and found I could no longer tftp or update from USB. After several days of frustration, I am near the point of giving up. Here's what happens when I attempt to use the UART rescue found at the Espressobin web site: Marvell>> usb start starting USB... USB0: Register 2000104 NbrPorts 2 Starting the controller USB XHCI 1.00 USB1: USB EHCI 1.00 scanning bus 0 for devices... 2 USB Device(s) found scanning bus 1 for devices... 1 USB Device(s) found scanning usb for storage devices... 1 Storage Device(s) found Marvell>> bubt bootloader.bin spi usb Burning U-BOOT image "bootloader.bin" from "usb" to "spi" USB0: Register 2000104 NbrPorts 2 Starting the controller USB XHCI 1.00 USB1: USB EHCI 1.00 scanning bus 0 for devices... 2 USB Device(s) found scanning bus 1 for devices... 1 USB Device(s) found Image checksum...OK! SF: unrecognized JEDEC id bytes: c2, 25, 36 Failed to probe SPI Flash exit not allowed from main input shell. Marvell>> I then tried various newer UART rescue images, which all seem to recognize the SPI flash chip but cannot update from USB (yes, I tried various working USB memory sticks...): Marvell>> usb start starting USB... USB0: Register 2000104 NbrPorts 2 Starting the controller USB XHCI 1.00 USB1: USB EHCI 1.00 scanning bus 0 for devices... 2 USB Device(s) found scanning bus 1 for devices... 1 USB Device(s) found scanning usb for storage devices... 1 Storage Device(s) found Marvell>> bubt bootloader.bin spi usb Burning U-BOOT image "bootloader.bin" from "usb" to "spi" USB0: Register 2000104 NbrPorts 2 Starting the controller USB XHCI 1.00 USB1: USB EHCI 1.00 scanning bus 0 for devices... 2 USB Device(s) found scanning bus 1 for devices... 1 USB Device(s) found BUG: failure at drivers/usb/host/xhci-ring.c:489/abort_td()! BUG! resetting ... > I also tried updating via TFTP. All the UART rescue images I tried give the same result: tftp hangs, like this: Marvell>> setenv serverip 192.168.1.15 Marvell>> setenv ipaddr 192.168.1.12 Marvell>> ping $serverip Using neta@30000 device host 192.168.1.15 is alive Marvell>> bubt bootloader.bin spi tftp Burning U-BOOT image "bootloader.bin" from "tftp" to "spi" Using neta@30000 device TFTP from server 192.168.1.15; our IP address is 192.168.1.12 Filename 'bootloader.bin'. Load address: 0x80000000 Loading: # Has anyone else experienced this problem? I find it hard to believe the board is broken, since it was working fine prior to the first boot loader update.
  12. I'm always willing to make a video about any subject you guys choose. Give me the details of what you want to see/hear and I'll do my best with it. @Igor Are you at the next Fossdem in Brussels? If so we could try to meet for an interview. You do not need to prepare for that. Just repeat a sentence when it didn't come out right. I cut and paste everything so nobody notices mistakes. Otherwise I could make a question list(and you can add questions you want to answer). And you could film yourself with a smart-phone answering the questions. I can then use that video and cut/paste my questions in between. I'm also not a good presenter, so live questions over internet would come out badly. I always have to redo my intros many times for my videos until I feel it's acceptable. I always got more blooper footage than useable video
  13. 1080p display xrandr --newmode "1920x1080_60.00" 173.00 1920 2048 2248 2576 1080 1083 1088 1120 -hsync +vsync && xrandr --addmode HDMI-1 1920x1080_60.00 && xrandr --output HDMI-1 --mode 1920x1080_60.00 720p display xrandr --newmode "1280x720_60.00" 74.50 1280 1344 1472 1664 720 723 728 748 -hsync +vsync && xrandr --addmode HDMI-1 1280x720_60.00 && xrandr --output HDMI-1 --mode 1280x720_60.00 https://linuxconfig.org/how-to-configure-your-monitors-with-xrandr-in-linux You can add the line to armbianEnv.txt if I remember well.
  14. Hi. I don't have the OPi1+, but I do have the OPi3 and PineH64. Here are my temperatures for the OPi3 Temperature ----------- With 5V fan idle : 35°C + heatsink maxed : 65°C 3.3V idle : 39°C 3.3V maxed : 69°C No fan/heatsink : 55°C maxed : between 73°C and 85°C throttle to 1.3Ghz over 75°C Mine seem lower than what you are perceiving. But what's shown here is within seconds. You could try with a fresh reboot, and wait a while for it to go to it's idle temp and check manually. cat /sys/class/thermal/thermal_zone0/temp You could also try to run SBC-Bench from @tkaiser It takes a long time, but afterwards you get a good picture of the temperatures it's running at.(and many more...) wget https://raw.githubusercontent.com/ThomasKaiser/sbc-bench/master/sbc-bench.sh sudo /bin/bash ./sbc-bench.sh -c https://github.com/ThomasKaiser/sbc-bench My conclusion with the H6 was to use it at 1.5Ghz when you don't use a heatsink/fan. That way it doesn't overheat/throttle too quickly. In some CPU intensive tasks it will perform better because of this.
  15. Hello, no i dont think so, i know the sound of "fan eat cable" its more something vibrating. However, yesterday i put a piece of silicon under the Helios, since then everything is fine. The fans are spinning in an expected noise-level. I still guess the case is not tight enough and starts vibrating. My Helios stands on a wooden floor, maybe its not a good combination. Independently from my experience, maybe you could add a silicon ring for the HDD screws between HDD and case in the next Batch. Thanks for your support, im fine and happy now
  16. I've uploaded it to megashares - https://mega.nz/#!g3xiFYgb!yzBHGRfaICeFSd7l8eJgEIdb3viHXBKuaHTNMYnrf5E File details - Armbian_5.37_S9xxx_Ubuntu_xenial_3.14.29_mate_20171226.img.xz - 843185252 bytes, md5sum aae9310959de43cdf3984d3105892bef
  17. Hello; It was tried with armbian buster, stretch and bionic. Orange pi zero connect wpa/wpa2 networks without problems, but connect to open network. I was trying different methods and wpa_supplicant conf file (key_mgmt=NONE) and different version of armbian. It cannot connect to open network. I need a solution for this problem. Thanks.
  18. Hi everyone, I'm new here and I need the image: Armbian_5.37_S9xxx_Ubuntu_xenial_3.14.29_mate_20171226.img.xz or another with kernel 3.14.29 for the S9XXX if anyone can download it, I really appreciate it. I've searched the web a lot and haven't found it. Thanks!!!
  19. Couldn't it be the ribbon cables of the fans that touch the fan blades ?
  20. Since it's merged, will it show up in some nightly build?
  21. Good day to all. Question to experts. How to change the resolution of the HDMI output in Armbian. Which file to make changes to: boot.cmd or armbianEnv.txt? If you can a couple of specific examples.
  22. Hey guys, I bought the A5X MAX+ and the specification is rk3328, 4GB, 1GIB, usb3, android7. I tried to burn the blewing roms on my USB flash drive and SD card: Armbian_5.76_Rk3328-tv_Debian_stretch_default_4.4.154_20190306.IMG Armbian_5.96_Rk3328-tv_Debian_buster_default_4.4.154_desktop_20190911.IMG Armbian_5.96_Rk3328-tv_Ubuntu_bionic_default_4.4.154_20190911.img And I tried to input the text "rk3328-a5x.dtb, rk3328-a5x-1500.dtb, rk3328-a5x-mx10.dtb, rk3328-evb.dtb" in "/extlinux/extlinux.conf", the system entered android instead of armbian which i really wanted. I followed the steps as belows: 1. Burn the SD card or USB flash drive; 2, edit: / extlinux / extlinux.conf 3. Insert the SD card or USB flash drive into the TV box; 4. Powered TV box; The final result is that the system cannot enter armbian, but android. Could you guys help me check where the problem is?
  23. Thanks for your help. 1. I would be happy to submit a patch, but I'm not sure you want it--concurrent mode cuts wifi transfer speed in half, because the radio is continually switching between two modes. Would that be acceptable to the project? 2. Thanks for the tip. I'll look into dkms. 3. Not my prefered choice, but that's always a fallback...
  24. Here you go, sir. armbianmonitor -u output
  25. Good to know! Choosing "default" worked perfectly and I built kernel 5.3.0 with the latest commit v20190918. I can see from GB source that you did include the patch dwc3/core: xHCI host not responding to stop endpoint command into commit v20190918. Thanks!
  1. Load more activity