All Activity

This stream auto-updates     

  1. Past hour
  2. Read what I wrote. Again.
  3. jiapei100

    Build NEWEST Linux Kernel 5.0.9 on Banana Pi M3

    Thank you Igor... I noticed sun8i-a83t-bananapi-m3 is supported by kernel 5.0.9 ? sky@bananapim3:~/Downloads/kernel/linux-5.0.9/arch/arm/boot/dts$ ll sun8i-a83t* -rw-rw-r-- 1 sky sky 6724 Apr 20 15:17 sun8i-a83t-allwinner-h8homlet-v2.dts -rw-rw-r-- 1 sky sky 8944 Apr 20 15:17 sun8i-a83t-bananapi-m3.dts -rw-rw-r-- 1 sky sky 9913 Apr 20 15:17 sun8i-a83t-cubietruck-plus.dts -rw-rw-r-- 1 sky sky 9438 Apr 20 15:17 sun8i-a83t-tbs-a711.dts -rw-rw-r-- 1 sky sky 26406 Apr 20 15:17 sun8i-a83t.dtsi However, when I tried to convert from .dts to .dtb, I obtained the following ERROR message: sky@bananapim3:~/Downloads/kernel/linux-5.0.9/arch/arm/boot/dts$ dtc -I dts -O dtb -f ./sun8i-a83t-bananapi-m3.dts -o ./sun8i-a83t-bananapi-m3.dtb Error: ./sun8i-a83t-bananapi-m3.dts:46.1-9 syntax error FATAL ERROR: Unable to parse input tree It looks it's reporting an ERROR from the following lines: 45 /dts-v1/; 46 #include "sun8i-a83t.dtsi" Is /dts-v1/; buggy??? BTW, I'm NOT using cross compiling... Sorry for my NAIVE question, is it possible to specify my DTS and build a particular .dtbs for a particular board (banana pi M3) ? Thank you Pei
  4. Mathias

    [RockPro64] Armbian upstream kernel/uboot test?

    I have replaced the cable by another one (freshly purchased and tested on my laptop), I still have the same problems. I've not been able to capture the backtrace this time, but at least I have some kernel messages showing how the kernel is fighting to make it work: some messages early on and then more later on (it fully crashed a few minutes later). Again, this is with kernel 4.4.174 and a JMS578 (patched firmware) based enclosure...
  5. Today
  6. crazystick

    Can't install PINE A64-LTS to eMMC

    Did you ever manage to get the Pine to boot from eMMC?
  7. pkfox

    NanoPI M4

    What would be the offset for an Armbian image ? Edit I worked it out with googles help if you run fdisk -lu /path/to/your/image.img it will give you start and end numbers , if you multiply the start figure by 512 this gives you the offset. I just tried it with my dd created Armbian EMMC image and it mounted ok - this is a useful piece of knowledge when you want to retrieve some files from your backup.
  8. Thanks for the info and pointer. Now I understand where this -20°C tweak we asked about here comes from It means it wasn't so smart to remove already the tweak... well at least it will already be aligned when armbian mvebu next jump to 4.19 or 5.x The kernel change you mention are from this commit and effectively it didn't made it to v4.14 https://github.com/torvalds/linux/commit/8c0b888f6610d0ebbc4bdfb52d2fef9f4a11adfc I'm also not 100% sure how this bitwise tweak works :/ FYI The Marvell errata (#132698) mentioned in the commit is an internal errata, it wasn't even made public.
  9. Mainline Linux kernel is from six month and one year behind Armbian kernel, also stable version v4.19.y where most of the stuff is regularly back ported. Compiling mainline kernel and expecting (better) functionality is overoptimistic/pointless, especially in case of Banana M3. You can try new Armbian kernel, but I have no idea if it boots at all on your board, by using armbian-config tools -> system -> alternative kernels.
  10. Hello, today I tried upgrading my ClearfogPro Kernel from 4.14.106 (next) to 4.19.20(dev). So far everything seems to be working (samba, dnsmasq, minidlna, network etc.), see also attached armbianmonitor link. Great work @ armbian. I also noticed that the reported temperature by "cat /sys/devices/virtual/thermal/thermal_zone0/temp" seems to be about 20°C lower than with the old kernel. I appreciate this, because it seems to be closer to the real value (measured with thermal probe at heatsink). The old 4.14 kernel always reported some value around 65-70°C which seemed a bit high for idling (cpu running at 800Mhz like 80% of the time). The new value of 35°C is quite realistic I guess. Does anyone know / have information about a change in temperature reading on the clearfog in the last kernel upgrades? EDIT: Checked in the kernel diff between 4.14 and 4.19 and there are some changes to https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/drivers/thermal/armada_thermal.c?h=linux-4.19.y They definitely changed something regarding some trim values - though I don't understand enough to really say if that changes the temperature reading. But if it did it might also be interesting for the Helios4 guys, I remember seeing some questions about high temperatures in their thread. @gprovost could this be related? Can I somehow help getting the 4.19 Kernel to be next? Like specific things to test? Or is your plan to skip 4.19 completely and go directly to 5.x? Greetings, count-doku
  11. lzb

    armbianmonitor error

    @guidol I can spot some difference in uptime and "a board just booted" and "a board with some uptime doing things". My is running urbackup (mostly active two or three times a day) and nextcloud (mostly idle at the moment). I had issues running this setup for more than 24h (freezes), but it seems to improve: root@bananapi:~# uptime 08:56:57 up 2 days, 8:13, 3 users, load average: 0.59, 0.56, 0.55 And current uptime is still growing after some serious testing (running stress, running btrfs scrub and btrfs balance to simulate "typical" workload). Not sure where this 4.76V came from? (cant see it in the uploaded log) I've changed governor and min_freq as the board is idle most of the time (as mentioned above). I think that my power supply isnt that bad: root@bananapi:~# grep -v Time armmon.log | cut -d\. -f1,4,5 | cut -d\ -f8 | sed '/^$/d' | sort | uniq -c 1 4.84V 1 4.85V 6 4.86V 2 4.87V 6 4.88V 24 4.89V 32 4.90V 69 4.91V 107 4.92V 85 4.93V 210 4.94V 335 4.95V 339 4.96V 458 4.97V 929 4.98V 1739 4.99V 3566 5.00V 7853 5.01V 8978 5.02V 7890 5.03V 2703 5.04V 367 5.05V 21 5.06V root@bananapi:~# wc -l armmon.log 38129 armmon.log I sure can try newer kernel if that can help. I can also ignore it as my uptime finally hit over 24h, but would be nice to solve that bug.
  12. Hi, all: I wonder if there is a manual to DIRECTLY build Linux Kernel (Say, current version 5.0.9) against any board, as far as uname -a is known ? For instance, current Armbian for Banana Pi M3 is of the following uname -a value: sky@bananapim3:~/Downloads/sunxi$ uname -a Linux bananapim3 4.19.25-sunxi #5.78 SMP Mon Apr 8 07:46:22 CEST 2019 armv7l armv7l armv7l GNU/Linux Anyway, I'm trying to test it out... Cheers Pei
  13. S.Alireza

    USB 2.0 notworking

    Hi, i bought a nanopc t4, then i installed armbian on it's eMmc , after starting os, i plug in a usb flash to it's usb2.0 ports(both usb 2.0 ports) but not working but when i plug in the usb flash to it's usb port 3.0 it will be work, i tried this issue with mouse and keyboard usb and some another usb flashes that has usb 2.0 compatibility, can anyone help me to setup my nanopc t4 usb 2.0 ports?
  14. mboehmer

    GPIO interferes with I2C

    Here we are: after booting, I2C works fine, and "cat /sys/kernel/debug/gpio" says: gpiochip1: GPIOs 378-496, parent: platform/c8834000.periphs:pinctrl@4b0, periphs-banks: gpio-378 (Eth MDIO ) gpio-379 (Eth MDC ) gpio-380 (Eth RGMII RX Clk ) gpio-381 (Eth RX DV ) gpio-382 (Eth RX D0 ) gpio-383 (Eth RX D1 ) gpio-384 (Eth RX D2 ) gpio-385 (Eth RX D3 ) gpio-386 (Eth RGMII TX Clk ) gpio-387 (Eth TX En ) gpio-388 (Eth TX D0 ) gpio-389 (Eth TX D1 ) gpio-390 (Eth TX D2 ) gpio-391 (Eth TX D3 ) gpio-392 (Eth PHY nRESET |mdio-reset ) out hi gpio-393 (Eth PHY Intc ) gpio-394 (HDMI HPD ) gpio-395 (HDMI DDC SDA ) gpio-396 (HDMI DDC SCL ) gpio-397 ( ) gpio-398 (eMMC D0 ) gpio-399 (eMMC D1 ) gpio-400 (eMMC D2 ) gpio-401 (eMMC D3 ) gpio-402 (eMMC D4 ) gpio-403 (eMMC D5 ) gpio-404 (eMMC D6 ) gpio-405 (eMMC D7 ) gpio-406 (eMMC Clk ) gpio-407 (eMMC Reset |reset ) out hi gpio-408 (eMMC CMD ) gpio-409 ( ) gpio-410 ( ) gpio-411 ( ) gpio-412 ( ) gpio-413 ( ) gpio-414 ( ) gpio-415 ( ) gpio-416 (SDCard D1 ) gpio-417 (SDCard D0 ) gpio-418 (SDCard CLK ) gpio-419 (SDCard CMD ) gpio-420 (SDCard D3 ) gpio-421 (SDCard D2 ) gpio-422 (SDCard Det |cd ) in hi gpio-423 ( ) gpio-424 ( ) gpio-425 ( ) gpio-426 ( ) gpio-427 ( ) gpio-428 ( ) gpio-429 ( ) gpio-430 ( ) gpio-431 ( ) gpio-432 ( ) gpio-433 ( ) gpio-434 ( ) gpio-435 ( ) gpio-436 ( ) gpio-437 ( ) gpio-438 ( ) gpio-439 ( ) gpio-440 ( ) gpio-441 ( ) gpio-442 ( ) gpio-443 ( ) gpio-444 ( ) gpio-445 ( ) gpio-446 ( ) gpio-447 (I2C A SDA ) gpio-448 (I2C A SCK ) gpio-449 (I2C B SDA ) gpio-450 (I2C B SCK ) gpio-451 (PWM D ) gpio-452 (PWM B ) gpio-453 (Revision Bit0 ) gpio-454 (Revision Bit1 ) gpio-455 ( ) gpio-456 (J2 Header Pin35 |onewire@1 ) in hi gpio-457 ( ) gpio-458 ( ) gpio-459 ( ) gpio-460 (J2 Header Pin36 |onewire@2 ) in hi gpio-461 (J2 Header Pin31 ) gpio-462 ( ) gpio-463 ( ) gpio-464 ( ) gpio-465 (TF VDD En |TFLASH_VDD ) out lo gpio-466 (J2 Header Pin32 ) gpio-467 (J2 Header Pin26 ) gpio-468 ( ) gpio-469 ( ) gpio-470 (J2 Header Pin29 ) gpio-471 (J2 Header Pin24 |cs ) out hi gpio-472 (J2 Header Pin23 |sck ) out lo gpio-473 (J2 Header Pin22 |cs ) out hi gpio-474 (J2 Header Pin21 |miso ) in hi gpio-475 (J2 Header Pin18 ) gpio-476 (J2 Header Pin33 ) gpio-477 (J2 Header Pin19 |mosi ) out hi gpio-478 (J2 Header Pin16 ) gpio-479 (J2 Header Pin15 ) gpio-480 (J2 Header Pin12 ) gpio-481 (J2 Header Pin13 ) gpio-482 (J2 Header Pin8 ) gpio-483 (J2 Header Pin10 ) gpio-484 ( ) gpio-485 ( ) gpio-486 ( ) gpio-487 ( ) gpio-488 ( ) gpio-489 (J2 Header Pin11 ) gpio-490 ( ) gpio-491 (J2 Header Pin7 |onewire@0 ) in hi gpio-492 ( ) gpio-493 ( ) gpio-494 ( ) gpio-495 ( ) gpio-496 ( ) gpiochip0: GPIOs 497-511, parent: platform/c8100000.bus:pinctrl@14, aobus-banks: gpio-497 (UART TX ) gpio-498 (UART RX ) gpio-499 (VCCK En ) gpio-500 (TF 3V3/1V8 En |TF_IO ) out lo gpio-501 (USB HUB nRESET |usb-hub-reset ) out hi gpio-502 (USB OTG Power En |USB_OTG_PWR ) out hi gpio-503 (J7 Header Pin2 ) gpio-504 (IR In ) gpio-505 (J7 Header Pin4 ) gpio-506 (J7 Header Pin6 ) gpio-507 (J7 Header Pin5 ) gpio-508 (J7 Header Pin7 ) gpio-509 (HDMI CEC ) gpio-510 (SYS LED |c2:blue:alive ) out hi gpio-511 ( ) After this little script: #!/bin/sh echo 475 > /sys/class/gpio/export echo out > /sys/class/gpio/gpio475/direction echo 0 > /sys/class/gpio/gpio475/value it says: gpiochip1: GPIOs 378-496, parent: platform/c8834000.periphs:pinctrl@4b0, periphs-banks: gpio-378 (Eth MDIO ) gpio-379 (Eth MDC ) gpio-380 (Eth RGMII RX Clk ) gpio-381 (Eth RX DV ) gpio-382 (Eth RX D0 ) gpio-383 (Eth RX D1 ) gpio-384 (Eth RX D2 ) gpio-385 (Eth RX D3 ) gpio-386 (Eth RGMII TX Clk ) gpio-387 (Eth TX En ) gpio-388 (Eth TX D0 ) gpio-389 (Eth TX D1 ) gpio-390 (Eth TX D2 ) gpio-391 (Eth TX D3 ) gpio-392 (Eth PHY nRESET |mdio-reset ) out hi gpio-393 (Eth PHY Intc ) gpio-394 (HDMI HPD ) gpio-395 (HDMI DDC SDA ) gpio-396 (HDMI DDC SCL ) gpio-397 ( ) gpio-398 (eMMC D0 ) gpio-399 (eMMC D1 ) gpio-400 (eMMC D2 ) gpio-401 (eMMC D3 ) gpio-402 (eMMC D4 ) gpio-403 (eMMC D5 ) gpio-404 (eMMC D6 ) gpio-405 (eMMC D7 ) gpio-406 (eMMC Clk ) gpio-407 (eMMC Reset |reset ) out hi gpio-408 (eMMC CMD ) gpio-409 ( ) gpio-410 ( ) gpio-411 ( ) gpio-412 ( ) gpio-413 ( ) gpio-414 ( ) gpio-415 ( ) gpio-416 (SDCard D1 ) gpio-417 (SDCard D0 ) gpio-418 (SDCard CLK ) gpio-419 (SDCard CMD ) gpio-420 (SDCard D3 ) gpio-421 (SDCard D2 ) gpio-422 (SDCard Det |cd ) in hi gpio-423 ( ) gpio-424 ( ) gpio-425 ( ) gpio-426 ( ) gpio-427 ( ) gpio-428 ( ) gpio-429 ( ) gpio-430 ( ) gpio-431 ( ) gpio-432 ( ) gpio-433 ( ) gpio-434 ( ) gpio-435 ( ) gpio-436 ( ) gpio-437 ( ) gpio-438 ( ) gpio-439 ( ) gpio-440 ( ) gpio-441 ( ) gpio-442 ( ) gpio-443 ( ) gpio-444 ( ) gpio-445 ( ) gpio-446 ( ) gpio-447 (I2C A SDA ) gpio-448 (I2C A SCK ) gpio-449 (I2C B SDA ) gpio-450 (I2C B SCK ) gpio-451 (PWM D ) gpio-452 (PWM B ) gpio-453 (Revision Bit0 ) gpio-454 (Revision Bit1 ) gpio-455 ( ) gpio-456 (J2 Header Pin35 |onewire@1 ) in hi gpio-457 ( ) gpio-458 ( ) gpio-459 ( ) gpio-460 (J2 Header Pin36 |onewire@2 ) in hi gpio-461 (J2 Header Pin31 ) gpio-462 ( ) gpio-463 ( ) gpio-464 ( ) gpio-465 (TF VDD En |TFLASH_VDD ) out lo gpio-466 (J2 Header Pin32 ) gpio-467 (J2 Header Pin26 ) gpio-468 ( ) gpio-469 ( ) gpio-470 (J2 Header Pin29 ) gpio-471 (J2 Header Pin24 |cs ) out hi gpio-472 (J2 Header Pin23 |sck ) out lo gpio-473 (J2 Header Pin22 |cs ) out hi gpio-474 (J2 Header Pin21 |miso ) in hi gpio-475 (J2 Header Pin18 |sysfs ) out lo gpio-476 (J2 Header Pin33 ) gpio-477 (J2 Header Pin19 |mosi ) out hi gpio-478 (J2 Header Pin16 ) gpio-479 (J2 Header Pin15 ) gpio-480 (J2 Header Pin12 ) gpio-481 (J2 Header Pin13 ) gpio-482 (J2 Header Pin8 ) gpio-483 (J2 Header Pin10 ) gpio-484 ( ) gpio-485 ( ) gpio-486 ( ) gpio-487 ( ) gpio-488 ( ) gpio-489 (J2 Header Pin11 ) gpio-490 ( ) gpio-491 (J2 Header Pin7 |onewire@0 ) in hi gpio-492 ( ) gpio-493 ( ) gpio-494 ( ) gpio-495 ( ) gpio-496 ( ) gpiochip0: GPIOs 497-511, parent: platform/c8100000.bus:pinctrl@14, aobus-banks: gpio-497 (UART TX ) gpio-498 (UART RX ) gpio-499 (VCCK En ) gpio-500 (TF 3V3/1V8 En |TF_IO ) out lo gpio-501 (USB HUB nRESET |usb-hub-reset ) out hi gpio-502 (USB OTG Power En |USB_OTG_PWR ) out hi gpio-503 (J7 Header Pin2 ) gpio-504 (IR In ) gpio-505 (J7 Header Pin4 ) gpio-506 (J7 Header Pin6 ) gpio-507 (J7 Header Pin5 ) gpio-508 (J7 Header Pin7 ) gpio-509 (HDMI CEC ) gpio-510 (SYS LED |c2:blue:alive ) out hi gpio-511 ( ) Hope that one helps. Edit: output from 4.19.6 stretch build, neweset kernel has console problems as discussed in other thread.
  15. Our (working) solution is not managed by Network manager, so you can't use those tools. Those values are fixed since configuration is on the "proof of concept" level. It works, but I have no time to develop this on super easy management anytime soon. Tools used: hostapd, dnsmasq, ifupdown, iptables. Check their config files to adjust those values manually. I am afraid, no other way. Help with extending AP functionality within armbian-config is more then welcome.
  16. vivekpk

    Couldn't start AP(host) mode in Banana Pi M2+

    With this image, it worked, thanks I have one more doubt, how to change the IP of the hotspot by default its 172.24.1.1/24 i tried to change by nmtui->edit a connection->ifupdown (wlan0) but its can this connection is read-only
  17. Igor

    OrangePi R1 RTWHALXT runs 100% CPU

    armbianmonitor is a bare minimum and I could already give you some hints, but without it is totally pointless that you are asking anything. Armbian is too diverse out of the box and nobody around has supernatural abilities , that's why this is required.
  18. RedCat

    RedCat

  19. RedCat

    OrangePi R1 RTWHALXT runs 100% CPU

    What logs except armbianmonitor -u are needed? A little later, I will try to provide all the logs and reports that are required. As far as I understood from the search, but the information is not enough that this problem is related to the OS kernel and WiFi drivers
  20. Igor

    OrangePi R1 RTWHALXT runs 100% CPU

    Without logs (armbianmonitor -u) you are wasting time. And with logs is also hard since we can't cover a work of 1.000 people and on our expense. (by googling) I suspect this is some generic bug in the kernel drivers, but since you provide no exact information about the kernel and no logs, there is nothing more to speculate.
  21. Experimental open source drivers are included into kernel 4.19.y, but performance is not very good. Not sure if such game is playable. It might be possible to integrate binary drivers, which should run faster, but its plain speculation. Don't hold on this. Since we have no plans/resources to bring this up, you are more or less on your own to try the integration. Our primary focus is making a ground that this is possible, but sometimes you still need to invest some of your time to get advanced thing working. But there are many other boards, where MALI supported gaming should be possible OOB. @NicoD can tell more about.
  22. Hello everybody! There was a problem, my OrangePI R1 with the Armbian Stretch OS running works in the access point + bridge mode (hostapd & bridge-utils), and when the client downloads a large file from the network, the RTWHALXT process loads the CPU by 100% and rtw_xmit_thread by 20% (watched using top) as a result, the processor freezes. How to fix it? Thanks in advance, sorry for my English I am from Uzbekistan.
  23. Yesterday
  24. Hi, I'm a new user to SBC and is thinking of buy an orange pi pc 2. Since it has a Mali450 GPU and the manufacturer claims that this SBC support OpenGL, can I use that to play some open source games like 0.A.D on armbian? Is armbian have mali gpu drivers installed? Thanks.
  25. query

    OPi Zero and DS18B20 1-Wire Problem

    I've now completely removed the modules.conf file. Looks like it worked, I can reboot it now and it still detects the sensor, and I think a little bit faster than before. Thanks a lot for the tip! One thing I'm confused about though. I have already had g_serial and i2c-dev in my modules.conf before I even wired the ds18b20. After I first noticed the reboot problem I decided it wouldn't hurt to add the w1 lines there too, since I've seen some people do that. (I didn't know about the DT/modules.conf conflict) It's clear to me now that the modules should be handled by the DT. However, why did I encounter this problem in the first place with i2c-dev and g_serial only? Would those two cause any conflict for the w1 modules being loaded?
  26. query

    OPi Zero and DS18B20 1-Wire Problem

    Thank you. I think I've added those lines in the modules.conf after having this problem in the beginning, but I'll remove them and let you know how it goes.
  27. martinayotte

    OPi Zero and DS18B20 1-Wire Problem

    Yes, remove them from modules.conf, but don't add them in armbianEnv.txt since you've already have things properly set there : overlays=usbhost2 usbhost3 i2c0 i2c1 w1-gpio param_w1_pin=PA10 param_w1_pin_int_pullup=0 This will make the module loading properly with the proper pin PA10.
  28. query

    OPi Zero and DS18B20 1-Wire Problem

    Thanks for the reply @martinayotte So, I should remove everything in /etc/modules-load.d/modules.conf and place them accordingly into /boot/armbianEnv.txt ? I need the i2c-dev for another sensor I have. How do I do this exactly? Thanks in advance.
  1. Load more activity