All Activity

This stream auto-updates     

  1. Past hour
  2. For hotspots, there are 3 modes : Bridge : Wifi IP address are in same range as your network and it's your DHCP deliver wifi IP address Routing : Wifi IP address are not in the same range as your network, wifi IP address are deliver per the hotspot ; your network must be "informed" the range IP of wifi ( routing table ) NAT : The wifi is full managed per the hotspot ; on your network you see only connection initiated per the hotspot Each mode have advantages and inconvenient, that depending your wifi using
  3. That's a pity, but good to know. So if I want my 16TB Volume to have checksums of file contents (against bit-rot), there's only ZFS left, with its own problems (not in kernel, eats a lot of Ram).
  4. Buy a new SD card and reinstall it with Armbian (the current version / origin or the new update) Restart your O-droid with the new SD card and do the basic config (name, network) With an SD / USB card reader, connect the old card to your O-dorid Retrieves what is still readable and makes the copies directly where is needed on the new SD card
  5. Wow, that table is a pain and a half to read! The image of the v7 and its description agree, but don't match the order of jumpers in the table. On the other hand, the image of the v5 and its jumpers disagree on which jumper is which, but one of them matches the table. Can you clarify which labeling you're using, and which direction of jumper you're calling "1" or "0"? This link would have me believe that the jumper next to the SATA connecter is toward the edge of the board, while the other two are toward the center - [J11, J3, J10] = [0, 1, 1] to boot from SATA if oriented with the printed labels, and [1, 1, 0] to boot from NOR. , And that "boot from SATA" link has the jumper settings in the 10, 3, 11 orientation, as opposed to the 11, 3, 10 orientation given in the big table of boot modes. How absolutely horrid! In Summary: The ports and interfaces page needs: - Reorganize the v7 table columns to match the order of the jumpers on the v7 board, either 10,11,3 or 3,11,10, but we don't know whether the columns are correct - Fix the callout on the v5 image to J10, J3, J11 - Reverse the labels on the v5 table columns so it's J10, J3, J11, but don't move the columns.
  6. Nice. New builds, including freshly released Linux 5.3.0, are ready.
  7. Today
  8. Now that Kernel 5.3 has seen the light I wonder where things stand if I'd build with these options " BOARD=orangepioneplus BRANCH=dev RELEASE=buster BUILD_MINIMAL=yes BUILD_DESKTOP=no KERNEL_ONLY=no KERNEL_CONFIGURE=no " for OrangePiOneplus . I suppose a working image ( read: bootable ) can be build? Also can things rgd OPiOnePlus be moved to a matured status, or that needs to wait at least till a new LTS Kernel 5.4 will pop up somewhere in November ?
  9. @ManoftheSea Yes, as mentioned in my previous post, I came to the same conclusion. It seems that v5 cannot do it, but v7 can. I have already bought the v7 and now I am trying to get it to download the bootloader from from SD card. So far no luck. Also you are correct, my links are not applicable to the problem. However, I have no better links. I am unable to find any link with a description of how to download the bootoader from SD card, be it with espressobin v5 or with v7. The depictions and tables from the link you posted (http://wiki.espressobin.net/tiki-index.php?page=Ports+and+Interfaces#Boot_selection) also seems to be weird. If you look at the table for v7, all the boot modes (other than NOR) seem to have the same jumper setting. This cannot be correct. Also the order of jumpers for v7 is wrong in the table. The order on the real board is J3, J11, J10, which is quite irritating when using the table to check your settings. This goes further, the depictions and tables for the v5 are flat out wrong. The table says that "NOR boot" is J11=1, J3=0, J10=0, but to get it to boot from NOR flash I actually have to sett it to J11=0, J3=0, J10=1. This sucks and took some time to figure out. Long story short: I cannot find any source with a description of how to download the bootloader from SD card with espressobin v7. Maybe I should open a new thread for that.
  10. @Shirohige I see, you are correct the U-Boot can be loaded from alternate locations. I learned something. Your links, however, are describing loading Linux from U-Boot, and are not applicable to loading U-Boot itself. http://wiki.espressobin.net/tiki-index.php?page=Ports+and+Interfaces#Boot_selection This link tells me that a v5 board is unable to load U-Boot from SD card, while a v7 can. It appears neither version can do so from USB.
  11. Correct. https://docs.armbian.com/#what-is-armbian Usually longer than upstream. Kernel wise we are ahead. Kernel is always the best one - not tied to the particular build version (as this is the case with Debian or Ubuntu) and they are more polished. Support is defined this way https://docs.armbian.com/#what-is-supported For example, this board (since its very matured) is already stashed away. We don't deal specifically with it anymore. There will be nothing new, but changes for entire Allwinner (A20) family come to this board as well ... If you need something that is not at the download pages, you can easily build latest version on your own. Perhaps Debian Buster? Minimal, server or desktop? https://github.com/armbian/build
  12. @ManoftheSea Again, thanks for the reply. I am sorry for being unclear. The console output I included in my first post, was meant as an example for when I am booting from NOR flash. I just wanted to show that it is working fine when booting from NOR flash. I do not think that it is necessary to have a bootloader on the board itself. Check the UART recovery, I think it is similar there. The board will download the bootloader via UART, copy it into RAM and run it from there. I want to do the same thing, but download it from SD card. Where can I read about this FAT-formatted USB drive? When looking here or here, it is always formatted with EXT4.
  13. I assume you have U-Boot running on your board, because you posted what appears to be the console output and it included: "U-Boot 2017.03-armada-17.10.2-g14aeedc (Jun 19 2018 - 11:18:51 +0800)" And also that the CPU was running at 1000 and the 1 gig of DDR at 800. I do not understand why you want to "load" the bootloader, and whether you are distinguishing that from "flashing" the bootloader. You are required to have a bootloader on the board itself. The USB flashing directions indicate a FAT-formatted USB drive. You mentioned an unformatted raw SD, and an EXT4 formatted SD, which are both wrong. I would suggest you try a FAT-formatted SD card, and put the flash-image-ddr3-MEM-RAM_CHIPS-CPU_DDR.bin in the FAT-formatted partition. Then, your flash command is bubt flash-image.bin spi mmc http://wiki.espressobin.net/tiki-index.php?page=Update+the+Bootloader#USB_stick_or_SD_card
  14. Hey Guys, i own a Lemaker Banana Pro device. The hardware itself is very fine, no issues with it, but the software support is pretty low. When i check internet, i see at least two images for it: Armbian Bionic - mainline based kernel 4.19.y Armbian Stretch- mainline based kernel 4.19.y I recognize that Armbian Stretch is based on Debian 9, which is the old Debian Version at all, so i am not willing to install it. But i wonder how it is with Bionic? Is Armbian Bionic based on Ubuntu Bionic Beaver? Is it that what i means? How long will the support run for this Bionic image? For me it doesnt matter if i install debian or ubuntu on my BPro, since its stable & software supported. thanks guys!
  15. Hi, I just updated my pine64 1Gb today (so 190916), it restarted perfectly with 5.3.0 kernel but I lost eth0 with `no phy at addr -1` in dmesg (wlan0 still works fine). Anybody can confirm ? I remember reading about this on irc about 5.3 and pine64 some weeks ago , I'll try to find it again.
  16. Is anyone else getting "Input/output error" when transferring data between two external drives? I thought the issues regarding IO errors were fixed in kernel 5.3... I'm on 5.3.0-rc6-aml-g12 so perhaps I should give the final version a try. Update: Changing /sys/class/block/?d?/queue/max_sectors_kb from the value of 1024 to 32 still trigger the error, just this time with “Input/output error (5)”. I might even have to try lower values as I know that ppl with an ODROID-N2 have issues with as low as 10. My setup is simple: A VIM3 with a ORICO Mini USB 3.0 HUB 4 Port Power Supply OTG with Micro USB Power Interface connected to a Rocketek usb 3.0 multi Smart memory card reader with a mSD card into and a Seagate Expansion Desktop. Both the ORICO USB HUB and Seagate HDD are powered with an external power supply. Update 2: This is the patch I need: dwc3/core: xHCI host not responding to stop endpoint command I can't seem to find the patch in Kernel 5.3 patch notes... So I suppose it isn't merged yet. Could you please add the patch to your next build, @balbes150?
  17. Yesterday I compiled Armbian_5.97_Pinebook-a64_Debian_buster_dev_5.3.0-rc8_desktop for my non-Pro Pinebook. While booting the screen was very dim So I searched on the net for a command and came to the one you had in your error-message above But the value 51 for brightness was too high to be set. I did read out the actual dim value as 2: #read-out display brightness pkexec /usr/sbin/xfpm-power-backlight-helper --get-brightness 2 and I did set (via /etc/rc.local) a for-me-default value of 8: #set display brightness pkexec /usr/sbin/xfpm-power-backlight-helper --set-brightness 8 A value of 10 was to bright for me
  18. If they are not in archive, you have to build them.
  19. Probably the driver for your chip is not implemented in 5.3 yet, remember it is a Release Candidat...
  20. Which Armbian version are you running? If it is one with kernel 5.3-RCx tyr one with kernel 5.2
  21. I recently wanted to buy a tv box, but I don't know much about the technical parameters, h96 max vs h96 max plus, I feel that these two products are similar, the main difference seems to be that the chipset is not the same. So rk3328 vs rk3318 Which one should I choose?
  22. I will try those images on a clean SD. But, previously, I will try to boot on sata thanks to u-boot.img.sata + SPL.sata... Anyhow, don't you have old images with Debian Stretch instead of Buster? (as I am running Yunohost.org which is not yet compatible with Buster)
  23. HI everybody, thanks for the replies. @ManoftheSea You assume that there is already U-Boot running on my board. I do not make this assumption. I want it to load the complete bootloader (U-Boot) from a SD card and run it, without any bootloader on the board itself. @umiddelb No, I do not want to start Linux from SD card. I can start a Linux from anywhere, I know that. I want the board to load U-Boot from SD card. I did that with other projects, but it does not seem possible with the espressobin v5. I think the hardware does not allow it unfortunately. If I am wrong, please correct me.
  24. If you get this working, send a PR (to dev and next) and you don't need to worry about In case board works well, we could also add an image ... we have it for some other CSC targets as well.
  25. This looks like you have boot loader compiled for eMMC ... or your hardware has eMMC and SD card wired the other way around (have seen that before). Try booting this image on a clean SD card: https://dl.armbian.com/cubox-i/archive/Armbian_5.94_Cubox-i_Ubuntu_bionic_default_4.9.179.7z
  26. 01_dtbdump_rockchip,rk3328-evb.dts Hi I have been working for a while in order to get wifi working on my H96+.From the Android dts the wifi chip is ap6330. And it has a strange silk screen . I see that this driver is included in the firmware. But I still can't make it work.Should I change some settings in dts? Or I need to recompile the entire firmware? I have read some of the contents of Rockchip's official website. Can you tell me how to build my own firmware?And the dts file is here.
  27. Yesterday
  28. FYI, I also missed this module, so it's done: https://github.com/armbian/build/pull/1559
  1. Load more activity