olivluca

Members
  • Content Count

    115
  • Joined

  • Last visited

 Content Type 

Forums

Member Map

Store

Crowdfunding

Raffles

Applications

Everything posted by olivluca

  1. I still use OPi.GPIO and it works fine for non root users with the proper udev rules. When I started using it I had to patch it to delay opening the files (the udev rules take some time to apply), but now it does it itself (it checks that the file is accessible before giving up).
  2. There are no drivers for the camera in mainline kernel. You have to use a version based on a legacy kernel (https://dl.armbian.com/orangepilite/Ubuntu_xenial_default_desktop.7z). I don't know the progress in mainline regarding gc2035. Edit: looking at the table here I see that the csi driver has been mainlined in kernel 5.0. Without that the camera cannot work. What I don't know is if the gc2035 driver is available in 5.0
  3. The "gpio" there is an uboot command, not a linux one, so "set" is correct. I cannot help on the correct gpio to set for your board, mine is an opi pc.
  4. Well, if you look earlier in the thread, I solved the problem by activating the gpio in uboot (and even then the pin could be different depending on the board). I never managed to make it work using sunxi-pio (though I never really tried).
  5. I think you have to activate the gpio before loading the modules
  6. No, I mean the SBC you used in your "success" message above, where you say you got 850Mbps throughput (with or without NAT btw?).
  7. What sbc did you settle for and which final combination of NICs? Links or it didn't happen
  8. In the EU No, it's an EU thing Edit: didn't finish - but there are variations depending on each country. Here in Spain, over 22€ you have to pay VAT + handling charges (IIRC 20 or so €), over 150€ you have to pay VAT + customs duties + handling charges. Less that 22€ you pay nothing (in theory). But many parcels pass through customs with no charges (they cannot control everything).
  9. Thank you, I knew it was me being stupid Edit doubly stupid: I commented that source myself from /etc/apt/sources.list when I saw the rest of the sources giving me 404
  10. I understand that, but at least they could have archived the latest security updates (or I'm just stupid and cannot find them.....for wheezy).
  11. I'm using the gc2035 camera and had no problem with the csi connector during the ~1.5 years it has been in service.
  12. And the noise (some comments say it's loud, some say it's quiet )
  13. Instead of the two backticks you can use $(), i.e. instead of `uname -r' you can use $(uname -r)
  14. I'm using armbian 5.73 (actually I reached that after various apt-get upgrade, I started with whatever image was available at the time), xenial, legacy kernel and I have no network problems, ssh or otherwise, (though I'm using exclusively wired ethernet).
  15. I didn't open the box (yet ), I'm happy enough with libreelec, though I'd like a real linux system to tinker with, but consider that I have less and less time to tinker
  16. Is it this one? https://github.com/150balbes/Amlogic_s905-kernel/blob/master/arch/arm64/boot/dts/amlogic/meson-gxl-s905d-ki-pro.dts if so it seems it just adds the dvb hardware to meson-gxl-s905d-p230 and that didn't work when I tried it, so I doubt it will work but I'd be delighted to be proven wrong.
  17. the dtb you mention are only available for kernel 3.14, they won't work for any later kernel
  18. Because there is no dtb that works for the KI pro. The dtb for 3.14 cannot be used since the format changed.
  19. @erbas I didn't pursue this further. I'm currently running libreelec but with kernel 3.14, as it seems nobody has a working dtb for newer kernels and I'm not able to write one. With libreelec the dvb driver more or less works but worse than under android (with android I can tune both dvb-s/s2 muxes as well as dvb-t, with libreelec I have more difficulty tuning some dvb-s/s2 muxes and cannot tune dvb-t at all). Perhaps later I'll try armbian again on this box, but for the time being libreelec it is.
  20. Just found this thread that explains the problem and the possible solutions
  21. Do you think that blocking the update of systemd will solve the problem?
  22. Being hit by this issue today (though I'm not sure since other network services are starting normally and I don't have currently access to a console), I wonder why systemd is being offered as an upgrade if it's going to cause this problem.
  23. I'm using this one: https://github.com/aircrack-ng/rtl8812au/tree/v5.1.5 (other branches gave poorer performance). I think I tried various repositories before settling on this one.
  24. I have a stick based on that chipset. I'm not using it with armbian (so the chosen driver there may be better) but it's not without issues: since it's not been mainlined (yet?) on a desktop (kubuntu) distribution you have to chase a driver (there are several variations, some of them working better than others) and even when you find the "correct" one there are still issues: sometimes I have to unplug and re-plug the stick to get a connection, sometimes, when it doesn't connect, it gets really hot. When it works it works fine though.
  25. @balbes150 do you know why such a simple module doesn't work (and messes up the kernel so badly that afterwards lsmod hangs forever)? A mismatch between the compiler used to compile the kernel and the one installed with armbian perhaps? If so, what compiler should I use to compile the module?