Jump to content

martinayotte

Members
  • Posts

    3892
  • Joined

  • Last visited

Everything posted by martinayotte

  1. Absolutely ! (if both SDCards are the same size or if the new one is bigger than the old one.) Otherwise, you should use the method described in the other thread.
  2. The general idea is to first get the bootloader written in the first sectors. So, TKaiser suggestion to "dd" the first 1MB is accomplishing this task. The second step is to have the partition sized properly with the SDCard size, so either fdisk or gparted can do that, deleting the partition and re-create new one that fit on the card. Third step is to format this partition, either mkfs.ext4 or gparted can be used. Fourth step is actually copying the whole rootfs from the orinal SD to the new one, to do that, both needs to be mounted, then a "tar piped in a tar" or "rsync" will copy the whole thing. Last step is to make sure to securely umount sdcards. Then, enjoy your backup ... :-)
  3. Maybe I could help here, if it is not tasks above my capacities. I could help on the DTS for example if something is missing.
  4. In my case, I'm using the https://github.com/duxingkei33/orangepi_PC_gpio_pyH3 derived from pyA20 from Olimex, but I didn't verified all the Pin GPIOs mapping.
  5. I've done some patches several weeks ago : http://forum.armbian.com/index.php/topic/617-wip-orange-pi-one-support-for-the-upcoming-orange-pi-one/page-10#entry5945
  6. Yes, that is the way to do, using dtc to decompile/recompile the dtb.
  7. Why do you say that H3 doesn't support device tree yet ? It does, but not using Legacy ! But maybe you mean it doesn't support "overlays" yet ...
  8. Also, I don't think RTL8192 would be any help here, as you mentioned "148f:7601 Ralink". This driver is part of the Mainline, but I don't think it is part of Legacy. /lib/modules/4.4.5-sunxi/kernel/drivers/net/wireless/mediatek/mt7601u/mt7601u.ko
  9. Are you running Legacy or Mainline ? In mainline, only the UART0 is exposed in the DTS. I've submitted a patch to linux-sunxi to have UART1/2/3 exposed (along with I2Cs), but they didn't merge my patch yet. https://groups.google.com/forum/#!topic/linux-sunxi/pON_W0tlI3g
  10. Personally, with my OPi-PC with Armbian 5.05, I've have no problem with smbclient connecting to Win7 shares, as long as I use proper credential ...
  11. Why are you using "-U%" ? Do you have the "armbianen" user existing on the Win7 machine ? Simply replace that with "-U <existing_win7_user>" ...
  12. I have 8188eu too, works without any glitch, even with Mainline kernels !
  13. For the kernel 4.x.x, the DTS for most UARTs except 0 and 1 were disabled. I've done a patch and submitted it to linux-sunxi mainline : https://groups.google.com/forum/#!topic/linux-sunxi/yYs-9KBrVEg You can do the same on your side, it will allowed the UART3/4/5 ... For the ttyAMA0, you can create a udev rules that will create that for you. On my side, with a zwave.me USB dongle, I've done that to create an even easier named symlink : /dev/zwave SUBSYSTEM=="tty", ATTRS{idVendor}=="0658", ATTRS{idProduct}=="0200", SYMLINK+="zwave", GROUP="martin", OWNER="martin"
  14. @tcmichals, I've posted a I2C+UART patch to linux-sunxi to get it into Mainline, but it could take awhile before getting it approved. You can grab it from there : https://groups.google.com/forum/#!topic/linux-sunxi/yYs-9KBrVEg For the SPI, I'm still struggling with it before submit, it was working fine under 4.4.5, but got terribly slow under 4.6.0-rc1, I don't know why, it is not related to my patches. In case you still wish them, it was originally posted there : http://forum.armbian.com/index.php?app=core&module=attach&section=attach&attach_id=162 ( from thread page-10, http://forum.armbian.com/index.php/topic/617-wip-orange-pi-one-support-for-the-upcoming-orange-pi-one/page-10 ) For the CPU/Therm, I don't know, I didn't investigate or try something out.
  15. Good to know ! Maybe I've messed up somehow with my own built kernel ... I will have to redo a new build soon.
  16. I means, this is only to diagnose/narrow if the issue was that eth0 was hanging during the apt-get.
  17. Did you tried with a WiFi dongle instead of eth0 ?
  18. Hopefully, the new commit from montjoie will fix all the remaining issues. (Because, I'm currently unable to make it work again with eth0 standalone, without any wlan0, I'm getting some "sun8i-emac 1c30000.ethernet: Re-run RX DMA 40000002")
  19. @ccfiel, Yes, the way you've installed my DTB was the good way (except the path is /boot/dtb/ ). BTW, I'm always keep backups of previous DTBs and use symlink to point to new one. Since I'm still using a WiFi dongle, maybe I've accidentally forgot to reapply the Ethernet patches. Let me check and I will resend new ZIP. EDIT : For the Ethernet, it is a bit strange ... I've looked and the patches were there. But I will investigate, also since I saw that Igor pushed new patches earlier today.
  20. Yes ! this is a known issue, it is cause by autodetection been broken when executed on Mainline, since some drivers not present yet in DTS. (Like the CPU temperature is not working, at least on by boards with 4.6.0-rc1) For HDMI, there is some code from Jef Moine if you wish to try it out and compile you own kernel, hoping this will be merged soon in Sunxi MainLine. (http://moinejf.free.fr/opi2/index.html)
  21. From the messages above, especially 'command not found' and 'No such file or directory', it look like a "chroot" has been executed wrongly during the install. Maybe this specific package has something wrong ... I bet that any other apt-get will work
  22. Although the OPi+ and RaspberryPi headers are similar, the GPIOs are not exactly matching, so maybe you will need to tweak the software accordingly. You can also purchase the zwave.me USB dongle and use OpenZWave software (which is what I did) . EDIT : While working/answering this other thread http://forum.armbian.com/index.php/topic/987-rxtx-uart-problem/, I've suddenly got a flash in my head : If this Razberry board only using UART3, then it is simply that those are not enabled by default in either FEX (Legacy) or DTB (Mainline). In this other thread, I've provided a new DTB for OrangePi-PC.
  23. Looking at my v4.6.0-rc1 source tree, I see that those are not enabled in DTS yet, present but without any pins assigned. So, it need to be tweaked soon using a patch. EDIT : I've done it ! here is in attachment my latest sun8i-h3-orangepi-pc.dtb-4.6-PATCHED (ttyS0 to ttyS3, which also include my I2C stuff added few weeks ago) EDIT2 : I've done some loopback tests, ttyS1 and ttyS3 are working fine, but for unknown reason, ttyS2 doesn't work, although same DTS recipe has been done. sun8i-h3-orangepi-pc.dtb-4.6-PATCHED.zip
  24. Yes ! with V4.x kernel, all the serials are present in DTS. For Legacy v3.4.xxx, maybe the FEX needs to be tweaked, you can look at it by using bin2fex (and fex2bin if you need to change something)
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines