All Activity

This stream auto-updates     

  1. Past hour
  2. Okey. I'll try "default" next time then. Did you specifically include the dwc3/core: xHCI host not responding to stop endpoint command patch provided by Amlogic through tobetter in the build (Armbian_5.96_Aml-g12_Ubuntu_bionic_dev_5.3.0_20190917)? If you included that patch, I would need to include it by my self when I build further kernels until it's not necessary anymore. However, if you didn't include the patch, then I don't need that patch eventually as the latest commits to linux-amlogic fixes the issue.
  3. There are several options: 1. If your work doesn't break basic functionality, sent your changes with a patch 2. Make driver dkms capable and build out of the tree. That module should automatically rebuild on kernel change 3. Freeze kernel and don't update
  4. Use EXPERT="yes" to unlock development versions/features.
  5. Our script uses "correct" way: 1. Adds sources 2. Download key 3. Update and install You can also check official instructions which does the same. There is a note: Older versions of Docker were called docker, , or docker-engine. If these are installed, uninstall them:
  6. Its my mistake. I should check that before merge ... and when you check it quickly its always something which is manifested only on some Like Xenial is next to go out, but today. It's related to building video accelerated sunxi legacy kernel images. Almost only for that.
  7. Today
  8. Video, lol. I can hear you typing, but you don't speak :-( In regard to presentation, funny and interesting: You suck at power point: Steal this presentation:
  9. This text is outdated and it is not necessary to pay attention to it. Many additional patches are included in this kernel.
  10. The reason for why I did not choose "default" was that it states: "Vendor provided / legacy". I do not want a vendor kernel, I want to update my 5.3RC6 to 5.3.0. I've to look elsewhere then. I ask again: Your build Armbian_5.96_Aml-g12_Ubuntu_bionic_dev_5.3.0_20190917 you uploaded fixed the IO errors over USB3.0 interface for g12 devices. Did you actually include the patch i referred to into this build or is it pure kernel 5.3.0?
  11. I didnt know that rng-tools arent available in Xenial But why buidl Xeninal, when Bionic 18.04 is also LTS? Are there any old drivers that not in Bionic?
  12. WDS200T3X0C also works, tested on 4.4 and 5.3rc4.
  13. I have this board and the mezzanine expansion. My experience level with linux is pretty good, with embedded hardware and arm booting process not so much. I'd like to help develop and test though. Where can I start?
  14. Build version NEXT is very naughty and is intended for experienced users who know the process of kernel build and the build Armbian (used source code directly from GIT Linux), also requires additional manual operations to configure a shared build (disable wireguard, etc.). You'd better use the "default" option. Current fixes address only a few model specific errors.
  15. This is mandatory when reporting strange things or bugs: armbianmonitor -u But I do not have an answer. It has to be investigated ...
  16. Hi Igor, Now it works like a charm as before, after the fix. Thank you for your fast response and support. Regards
  17. It's tricky and needed kernel header files are not exposed in UAPI (userspace API) yet because they are still evolving and changing. You can try following: 1. Apply Linux patches 1 (you can filter out only media related patches), 5, 7-11 on kernel 5.3: 2. Apply all FFmpeg patches on FFmpeg 4.0.4 (it is easy to port those patches on newer version, to avoid rebuilding mpv): 3. Compile FFmpeg with at least following options --enable-v4l2-request --enable-libudev --enable-libdrm 4. Recompile mpv if needed - depends on FFmpeg version used. If it matches to what was was used to compile mpv with, then there is no need. 5. Add your user to appropriate group ("video" I think) so you can use VPU without root privileges. Now you should have working mpv with HW accelerated decoding. As I don't use any desktop on SBCs, I run mpv with following options: mpv --hwdec=auto --vo=drm video.mkv This gives you most speed - HW decoded and directly rendered by DRM driver, so CPU is not involved. Only downside is that it is fullscreen only. Not sure how big performance hit (CPU usage) you would get with X11.
  18. I apologize for asking such a basic question. I have recompiled the wifi module on an Orange Pi PC+ to operate in concurrent mode so it can act in both station and AP mode at the same time, allowing it to be a wifi repeater. The problem is, this feature is lost on every kernel upgrade, requiring me to recompile the module each time I upgrade the kernel. The kernel module driver often changes slightly between kernel versions, and I have to track down and fix new bugs in the source code that prevent it from compiling when concurrent mode is enabled. I'm happy with how the wifi module performs now, but don't want to lose the ability to get needed kernel updates in the future. Is there any way I can keep the wifi module I have now without losing the ability to upgrade the rest of the kernel?
  19. This did end up working, is there a 'correct' CLI way to install docker though?
  20. Banana Pi BPI-W2 BPI-W2-openwrt-lede(Linux 4.9) code update to github
  21. Yesterday
  22. I have an Orange Pi One Plus with the H6 chip in it and I'm quite happy with how well it's supported by Armbian. I haven't really had any problems with it. I do have one question, though. I'm using armbianmonitor to "-m" monitor the machine and I notice that the temps are always pretty hot. Even at idle (480MHz) it still shows 72C. That seems higher than I would have expected. Is this normal, expected behavior? I understand that the SoC thermal monitoring code in the kernel is pretty new and therefore might not be perfect, yet. So, I thought I'd ask. Because it may just be my board that's off. Does anyone know if this is normal? Info: The board is in a lightly vented case and there is no HS on the SoC. There is light cross airflow in the area. Armbian version is "Welcome to Debian Buster with Armbian Linux 5.3.0-sunxi64" with current software updates. If there is more information I can provide, I would be glad to report it. Thank you for your time.
  23. I tried official Armbian today (with 4.19 and dev 5.3. kernel, both latest nightly builds) and my Lime 2 rev K works perfectly as expected: root@lime2:~# cat /sys/class/power_supply/axp20x-battery/voltage_now 4062000 root@lime2:~# cat /sys/class/power_supply/axp20x-battery/capacity 51
  24. I completely understand and appreciate everything you all do for this community. There is a large labour of love here. I want to stress that I am not intending to be negative to the project. If anything, I'd like to better understand so that I can make constructive contributions to the community. I guess the part I am hung up on is calling the image "bionic" or "bionic-based" when it is missing specific operational changes for that release. Based off the name and suggested base version, bionic, I would expect or assume that the system changes described in the bionic release notes happened. In my mind, its like regressing from systemd (15.04 Ubuntu Vivid) to init.d (14 Ubuntu Trusty) and calling it still Ubuntu Vivid. Like sure, its still Ubuntu and may use newer Vivid packages but at a release level, it does not match. This is where my confusion comes from. Would this change not cause more issues as it is now an atypical build and searching "ubuntu bionic network configuration" will yield results for programs not installed on the system? With the provided changelog I assumed removing these packages was a mistake as it was not noted. I get that not everyone wants to read crazy long changelogs but noting the removal of existing system packages would help. As there were files associated with netplan, ie. /etc/netplan/01-armbian-default.yaml (or something pretty similar), originally provided with armbian bionic. As far as I was aware this setup worked properly, and I'd like to reimplement them as you have suggested. There are months worth of commits since I last pulled. Does anyone know who would have pushed this commit or when it would have happened? Going through months of commits for a needle in a haystack sounds fun and all but, lets be productive with time.
  25. At Toastmaster its organised this way: Once you become pro (listener and presenter), you can easily spot those who prepared their "speeches" in 15 minutes or less And you notice almost all mistakes they made ...
  26. well it took a while to figure out that there are only a few desktop recording programs for wayland.. and without wayland a 13 inch full hd display sucks as desktop, due to x can only have 100% and 200% (both of them suck with gnome, wayland is capable of 125% which is just perfect). A small hint here.. gnome wayland on ubuntu doesn't record properly with a 125% zoom, so for recording you've to go back to 100% to get something 'useful' out of it. well I better don't tell you how long I normally need to prepare presentations.. A good training is "spin the powerpoint", a 'game' we quite often played at university.. basically, you see the slides the at the same time as your audience (cause someone else wrote it). It needs a basic understanding of the topic, but you learn a lot about free speech (not the american meaning of it). You must also consider that your audience normally doesn't know your topic well, which gives you some freedom in the presentation (it doesn't have to be 100% 'scientific correct'.
  27. Pointless. Check edit history: That's more theoretical / IMO copy paste from here but its worth trying because I suspect kernel config issue. If all this would be this simple, we would provide a full working image long time ago Check if there is any Libre/Openelec work (in any state) around modern kernel. P.S. Kodi / acceleration was operational at some point with modern kernel (4.14 or 4.19) ... but later it broke.
  28. I was somehow hoping the video problem was not kernel related, but maybe due to the older rest of the OS. Apparently the CuBox is quite an exotic system, and the user community is not that active. On the vendor's forum I see a screenshot of someone apparently having Kodi on etnaviv running, on this hardware. But the Debian wiki says about the CuBox: "On Debian 10/Buster GNOME defaults to Wayland and works out of the box." Unfortunately I don't get the serial console connected anymore, though, so I can't install Debian the normal way. I had it running some time ago, but I don't remember which cable or which other computer I used back then. The next thing I'd like to try is Fedora, using the arm-image-installer. Apparently it supports the mx6cuboxi. But that attempt will have to wait until the weekend.
  1. Load more activity