All Activity

This stream auto-updates     

  1. Past hour
  2. How can I use this on different Ubuntu Bionic builds? not just Armbian?
  3. The PineH64 model B is a bit better designed than the OPi3. It's got a lot less problems, and a bit better heat characteristics. The H6 SoC's do need a fan to run maxed out at 1.8Ghz. But you could clock it a bit lower if you'd like to passively cool it. The software isn't ready yet for it. But I expect this to become a well supported board. Here my review and comparison video of the Pine H64 model B with OPi3 I'm in love with the RK3399 boards from FriendlyElec(NEO4/M4/T4). But now the NEO4 is at $50. It was cheaper when released. It only has got 1GB ram, a bit worse cooling than the NanoPi M4(my favorite). But they've got great VPU support in Armbian and in FriendlyElec images. But of course those are more expensive. As they've already said. The Amlogic S905 boards are a good choice since they've got good VPU support. But on higher display resolutions than 1080p my Odroid C2 lags a lot. There's not that much other choises. The Rock64 has problems with the media script. Allwinner H5 SoC's should be well supported for this. But I don't have any H5 board. So I have not seen this working well. ( @mindee I'd love to review the NanoPi K1 Plus)
  4. Today
  5. You can install Armbian from sd-card to eMMC with sudo armbian-config The Rock64 does not support booting from USB only I believe.
  6. I had also some issues about dpkg not being able to complete the upgrade ... sadly for this one i don't remember at all what was the exact problem and how i solded it ...
  7. I tryied playing at that time with the URLs but without any successes in the end.
  8. I have just seen this issue on the 5.2-rc integration branch, to get mmc booting I needed to ensure I did try to remount any disks from fstab (it would crash here). When I did get it to boot if I pushes the mmc hard it hung (waiting on mmc) and load slowly increased with a lot of io wait. SD card does not have this issue. and usb seems fine. Trying to find a solution and this looks interesting which I am yet to try... Edit: the problem can occur with sd card as well after some time, will try the patch above
  9. Thank you for the update, Sean. I will give it a go.
  10. you can use: deb jessie main contrib non-free deb-src jessie main contrib non-free deb jessie/updates main contrib non-free deb-src jessie/updates main contrib non-free
  11. @PatrikXThere was a driver missing related to USB, it has since been added/enabled. The latest kernel releases should support it, if not building an kernel package yourself will work, have done this myself and the APC UPS works just fine.
  12. I was wondering if there is a solution to boot from a USB thumb drive and flash the OS to an eMMC. Currently I´m running ARMbian on a Rock64 with an eMMC module installed. Since I´m still trying to figure out how to set up the device I keep reinstalling the OS. So it would be nice to have a way without opening the case, take out the eMMC, hook it up to the PC to flash and reinserting. Thanks in advance.
  13. Thanks for the reply. I had some progress but broke elsewhere. I think some major files may be damaged. I may need something called busybox installed, which I do not have unfortunately.
  14. Yesterday
  15. For everyone interested.. I made several experiments, and I found out that the issue happens only if the wifi connection is teared down from the user. It doesn't happen if the connection is severed from AP side, for example. When the AP is restored the association is renegotiated almost immediately and works fine. Very, very strange. I'm pretty sure the problem is not in wpa_supplicant, because it works fine if I don't use the onboard wifi (for example using an USB wifi dongle); it must definitively be something wrong/missing with the 8189es driver Nevertheless, there are several quick workarounds. For example: don't disconnect from nmtui or wpa_cli, use ifdown instead.
  16. Me neither. As I said I used the description from above. Are you sure that ttyS1 is the correct port to use? Is that the same as UART1?
  17. @megi I noticed I already had the firmware for ap6255 at /lib/firmware on the lite2 but I am still not able to attach the device to uart1 How have you managed to configure uart1? Or are there some relevant differences in the kernel which haven't been ported to the lite2 built yet?
  18. So were you able to configure the device using hciattach?
  19. Sure, in the link from above: root@orangepi3:/dev# sudo hciattach /dev/ttyS1 bmc4345c5 921600 noflow - Unknown device type or id
  20. hciattach is what you are asking for. e.g. $ sudo hciattach /dev/ttyS1 bcm43xx 921600 noflow - Can you attach the firmware to this thread?
  21. Scan ssid by mobile phone the SSID can be seen . but always in password loop. I've installed hostapd V2.7 and dnsmasq V2.79. and wpa_supplicant and networkmanager are stopped. The config files are as below: 1: etc/hostapd/hostapd.conf interface=wlan0 driver=nl80211 ssid=TinkerNet hw_mode=g channel=7 wmm_enabled=0 macaddr_acl=0 auth_algs=1 ignore_broadcast_ssid=0 wpa=3 wpa_passphrase=mypassphrase wpa_key_mgmt=WPA-PSK wpa_pairwise=TKIP rsn_pairwise=CCMP 2:/etc/dnsmasq.conf interface=wlan0 # Use the require wireless interface - usually wlan0 dhcp-range=,,,12h Then I try armbian-config ...strange thing, there is not hotspot option in network. Anyone could explain how to config hotspot on Tinkerborad S with Ubuntu 18.04?
  22. Igor

    Seed our torrents

    Implemented, thanks for the tip. Speed increase should be noticeable
  23. Allright, I got the file downloaded and into the correct folder, but I'm stuck here: The board contains AP6256 WiFi/BT module that has its bluetooth part connected to SoC's UART1 port. Enable this port, and add node for the bluetooth device. The UART1 I got actived in the armbian-config. But how to I "add a node for the BT device"?
  24. @JMCC Thank you! I now have Chromium w/ hardware acceleration! it's a shame the 32bit Chromium/Streaming doesn't have it, though.
  25. I trying to get the USB3 working with orange pi lite 2 and the latest nigtly snapshot 5.1.3-sunxi64 #5.87.190522. I notice that the usb3 is disabled in the the dtb file: dwc3@5200000 { compatible = "snps,dwc3"; reg = <0x5200000 0x10000>; interrupts = <0x0 0x1a 0x4>; clocks = <0x2 0x72 0x2 0x72 0xa 0x0>; clock-names = "ref", "bus_early", "suspend"; resets = <0x2 0x33>; dr_mode = "host"; phys = <0x1f>; phy-names = "usb3-phy"; status = " disabled "; phandle = <0x52>; }; phy@5210000 { compatible = "allwinner,sun50i-h6-usb3-phy"; reg = <0x5210000 0x10000>; clocks = <0x2 0x6a>; resets = <0x2 0x2d>; #phy-cells = <0x0>; status = "disabled"; phandle = <0x1f>; }; I changed the status (from disable to okay) on both and recompile the dts file, and now I can see the usb3 HUB: lsusb -t /: Bus 07.Port 1: Dev 1, Class=root_hub, Driver=musb-hdrc/1p, 480M /: Bus 06.Port 1: Dev 1, Class=root_hub, Driver=ohci-platform/1p, 12M /: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=ehci-platform/1p, 480M /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci-platform/1p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-platform/1p, 480M However no devices are detected, no even powering when plugged into the USB port. I contacted Icenowy, who currently maintains the usb3 driver, and have been advised that current driver should be working. I wonder if the issue rests in the dts file setup, current parameter setup, given the fact it was marked as disabled? I noticed someone in the H6 dev forum mentioned that this was working back a month or so ago, however it does not seem to be working in the latest sanpshot.
  26. It didn't work for me, "load average" issue still there and copy still stuck in /usr ...
  27. Without any logs, it is difficult to understand which issue you're facing, because it should work as is ...
  1. Load more activity