Active threads

Showing topics posted in for the last 365 days.

This stream auto-updates     

  1. Today
  2. No problem. In context of mvebtu there is not muc, perhaps switching DEV to 5.7.y if not already? More complicated is E-bin upgrade. We stuck at 4.19.y ... Do we need 3rd party reviewing here, perhaps @martinayotte find some time? Perhaps this needs a bit more clearing / explanation? I am not sure that I understand what options do we have here and why would we need to change this ... ?
  3. Possible / planned ... when we settle up our CI rearrangement ... which is getting extremely complicated and expensive to maintain. If you want better support, you are welcome to add your resources. With trunk we are already at 5.7.y while for pushing updates from a previous build system stable branch we have no maintainer(s), build (probably) fails ... Kernel 5.4.y was first kernel where this hardware become usable to some degree. With 5.6.y some features were fixed, with 5.7.y a bit more ... there are ofc some problems ... one annoying problem which we are sorting out ATM is that board sometimes doesn't come back after reboot. It stays powered off ... This problem was so far only in 5.7.y Philosophy regarding "stability" is slightly different, until software for this particular hw matures. We are not there yet. So it usually doesn't really matter if upstream kernel is LTS or non LTS.
  4. snap SHOULD work with SElinux and vice versa but it seems that the policy for it is missing in SElinux and I could not find where to get that from...
  5. With dtc you can compile dts into dtb or vice versa. i.e.: dtc -I dtb -O dts <input_file> -o <outputfile>
  6. 83.0.4103.116-1~deb10u2 seems to have righted itself
  7. That indeed disabled those messages. I have a few more, are those normal and necessary aswell or can I disable something to get rid of them:
  8. Hello dear community, I am very anxious to be able to use android and armbian for you. for now, is there any way to start my Android on the sd card? lla armbian I installed it in la nand, thanks for your great support ­čśÇ
  9. Try updating 20-autologin; [Unit] ... ...
  10. Providing logs with armbianmonitor -u significantly raises chances that issue is getting addressed.
  11. For these modules to work, at least the correct Devicetree configuration must be available. This way they know how to operate the tx led and how it is wired up.
  12. If you want to change the speed. The place of the fan is different on some kernels, you can check it: sudo find /sys -name pwm1 | grep hwmon And you will recive a text, write that. nano (insert the text you recived here) and then change "255" to whatever you want.
  13. @Patrick Schl├╝ter You mean the interface disappeared ? Have you try a full power cycle ? unplug / plug DC plug. What do you get if you do the following commands ? sudo ethtool eth0 dmesg | grep mvneta
  14. Is there nay way to make it work h2 deconding on banana pi zero?
  15. Yesterday
  16. Hi, it's truly amazing work! I wonder if there are newer commits on top of those for the rk3399? I've been trying for the past couple of days to get QHD or 4k30 without much success so far.
  17. hello, I don't have the ultimate version of GT1 but I use the meson-gxm-vega-s96.dtb everything ok and ETH0 ! Just the CPU Temp at 55┬░ but the box work great (home-asssitant).
  18. Hello, I'm not a specialist of that but, I testing actually 3 box, 2 with S912 the Beelink GT1 and bqeel K12 and 1 with S905 the Beelink M18. I using the recent kernel 5 on it. The CPU Temp is correct (30-35┬░) for the S905 with the M18 box but with both S912 (55-60┬░) with fresh install. The M18 is to old that my S912 box's but have not CPU Temp issue. No solution to use the S912 proc like underclocking or change some service or parameter ?
  19. That's good, u-boot is using my "generic" device tree which is embedded into u-boot itself. At least we know the emmc is working with a basic configuration. Thanks for the logs, I think the problem is related to this one: [ 3.771361] dwmmc_rockchip 30020000.dwmmc: All phases bad! [ 3.771367] mmc1: tuning execution failed [ 3.771382] mmc1: error -5 whilst initialising MMC card which may be related to pin initialization or most probably to eMMC DDR mode. U-boot does not use eMMC in DDR mode. I didn't spot any mmc-ddr strings in the ReSpeaker patches. I can take a look to the compiled device tree if you attach it here, but in the meantime you can decompile it, find the dwmmc@30020000 node and comment all the properties starting with pinctrl-names, pinctrl-0, mmc-ddr-1_8v and rockchip,default-sample-phase. Recompile it back and try again.
  20. Hello, my installation omv crashed the other day. The SD card was corrupted and fsck was not able to get the thing back. Ok, I said, not a problem, I will reinstall the system from the last version. I downloaded the last version Armbian_20.05.1_Helios4_buster_current_5.4.43 and thought that I will be good in an hour. Now it is two days later and it doesn't work and I don't know how to get it to work. Here just a little description of what happens. 1. write the image on the ┬ÁSD 2. put in Helios4. Start. 3. connect over serial. login roor, change root password, add sudo user. 4. apt update+upgrade. ok. 5. (optionally) Set fixed IP-address with armbian-config (DHCP doesn't change the issue). 6. enter armbian-config install OMV. Installation takes some time, the nas reboots. 7. login with root or the user 8. No network anymore. OMV took over the system, the eth0: device is no more. OMV is not usable because there's no GUI, one cannot connect externally to it. Here the result of ifconfig root@helios4:~# ifconfig lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet netmask inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1000 (Local Loopback) RX packets 2129 bytes 878522 (857.9 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 2129 bytes 878522 (857.9 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 root@helios4:~# What can I do to at least set an interface. The options are annoying as I don't want to read a treatise on systemd and having to lear what the f. yaml is, or in what format I have to invoke beelzebuth to get that interface to show up.
  21. tried with dhcp and static at /etc/network/interfaces.d/eth0 but with auto eth0 added allow-hotplug eth0 too... currently on ubuntu 20.4 but hell - ping changed from network not reachable to Destination host not reachable... some efforts.. still no network device in /dev but ethtool -S eth0 shows some data - almost all 0 Can't help but I think there is a bug between Kernel 5.4 and network?-manager sorry but I am not very good in driver and kernel tasks my focus is on LXC-Containers
  22. Anything wrong with the spi driver for rock3328 or the rock64v2 hardware? My spi tft displays are way too slow when compared with h3 boards (5.7 kernel). Any ideas?
  23. Hi, i'm using a Raspad tablet-like device with a aml-s905x-cc inside and i'm experimenting some mobile interface that i can use with the touchscreen, but also with mouse and keyboard. I'm simply curious about convergence desktop designs and mobile desktop environments. The obvious choice would be GNOME, but it is very heavy, both on memory and cpu usage and my board with only 2GB of ram cannot handle it if combined with other heavy programs. I knew that Librem was developing a desktop environment for their Librem 5 linux phone. Since they focus on opensource software i thought if i can install their desktop environment on my tablet to try it and.... yes, it is possible! And it is surprisingly easy to do. So, if someone would like also to try their desktop environment, i make a "guide" on how to install it. Like any wayland desktop environment, there is a compositor (called phoc) and a graphical shell (called phosh). On the git they state that to run phosh should run on any compositor that implement wlr-layer-shell, so maybe you could try other compositors! First clone the git of phoc with: git clone Change the directory on the just downloaded folder: cd phoc Then, since they provide the file needed for debian packaging, i suggest to generate the deb package and install it instead of generating the binary directly with meson. In this way you can uninstall the program simply with apt like any other program. From the control file, i can see the needed dependencies, but i suggest to get directly from the build command below. If some package is missing, the packaging tool will tell you which. Then you can simply do "sudo apt install [all the missing dependencies]" To create the debian package run: debuild -i -us -uc -b When the command finish, it should create a debian package inside the upper folder called "phoc_0.4.0_[architecture].deb" You can install it with "sudo apt install /path to the file/phoc_0.4.0_[architecture].deb" Once phoc is installed, it's time to install phosh. Go to the previous folder with: cd .. Clone the phosh git with: git clone Change the directory on the just downloaded folder: cd phosh Dependencies should be these, but like before, i suggest to get them directly from the build command and install them as the same way as phoc: To create the debian package run: debuild -i -us -uc -b At the end of the compilation, you should find the package inside the upper folder and like before you can install it with "sudo apt install /path to the file/phosh_0.4.0_[architecture].deb" That's it. Reboot and on you favourite login manager should appear the entry "Phosh" that can be started like any other desktop environment. During the debian packaging compilation it will generate some other packages, like the debugging symbols, but they are not needed to make phosh work. Hope someone could find this "guide" useful. Have fun!
  24. Any for that you have to spam forums? Who will clean after you? You are welcome to solve any problem for and with the help of community, but so far I haven't notice anyone asking for this
  1. Load more activity