All Activity

This stream auto-updates     

  1. Today
  2. @cyber Do your shutdown-messages also look like this attached picture?
  3. Have you tried multiple SD cards?
  4. Hello, I have also the problem guidol has run into for a long, long time. Reboot doenst work. I have to "shutdown -h now" and then power-cycle. The weird thing i run into is, the system boots just every 2. time from emmc into armbian. I have then to boot from sd, "shutdown -h now" and then power-cycle and the next boot, boots into system from emmc. For me, it is a work around but not very comfortable. Regards Cyber
  5. Has anyone tried out Panfrost in this device? I used this guide to compile both DRM and Mesa but glxinfo still reports llvmpipe in use. I am running armbian's sunxi-dev 5.3.6 kernel, does that version have the necessary patches or do I need another kernel?
  6. Most probably ... Right ! It is a typo, it is PC17 ...
  7. on my board I have not set the USB_DRV GPIO for any USB, they are always ON (enable pin of sy6280 pull up to 5V). Also ID_detect is not connected either as I'm not using OTG. So none of these are connected : &reg_usb0_vbus { gpio = <&pio 2 17 GPIO_ACTIVE_HIGH>; &usbphy { usb0_id_det-gpios = <&pio 7 4 (GPIO_ACTIVE_HIGH | GPIO_PULL_UP)>; /* PH4 */ usb0_vbus_det-gpios = <&pio 7 5 (GPIO_ACTIVE_HIGH | GPIO_PULL_DOWN)>; /* PH5 */ Not sure if they should be removed from the DTS? Also are you sure it's PA17? Because it's writen '&pio 2 17' I thought the first number was reference to the letter, like A = 0 B = 1 ... H = 7. Do you know how those numbers 2 and 17 are used if not by letter-number index?
  8. First, try to do "dmesg | grep -i sdio" and then shorter your previous command to "dmesg | grep -i brcm". BTW, never do "modprobe brcmfmac", it should be loaded by the DT itself if properly set. Also, check the schematic, sometime "AP6212" are powered using GPIO controlled VBUS (like USB0) and sometime it requires also a 32KHz clock in DT.
  9. According to Lime2 schematic, there is USB0_DRV which is control the VBUS of USB0 using PA17 gpio. Is there some kind of "usb0_vbus" entry in DTS and is the "gpio" parameter is pointing to the right PA17 ?
  10. Tried and still NOK. I have message in dmesg musb-hdrc musb-hdrc.1.1auto: vbus_error in a_wait_vrise (80, <sessEnd>, retry #3, port1 0008010c
  11. Hi! Using mainline on custom A20 board with sch very close to lime2, with 2 differences: (- EMAC of lime instead of GMAC of lime2) - AP6210 wifi/bt module on MMC3 with same schematic as cubietruck. Only difference in AP6210 schematic is that : - we use PE1 for WIFI_Enable instead of PH9. - PE0 for wifi_host_wake instead of PH10. BT works OK. Wifi doesn't work. To test the wifi part, we used cubietruck DTS, only patching the parts about PH9 and PH10. BRCMFMAC load without any messages and iwconfig / ifcongif say there is no wireless card. "dmesg | grep brcmfmac" gives no results. nor "dmesg | grep ap6210". lsmod list brcmlmac and brcmutil as loaded. Tried rmmod and modprobe again but nothing happens. After seeing this patch : I tried removing those 3 lines again by d /boot/dtb sudo dtc -I dtb -O dts -o sun7i-a20-cubietruck.dts sun7i-a20-cubietruck.dtb nano sun7i-a20-cubietruck.dts removed the 3 lines, then sudo dtc -I dts -O dtb -o sun7i-a20-cubietruck.dtb sun7i-a20-cubietruck.dts But still the same Any ideas ?
  12. Hello, i am having also boot issues similar as @belegdol. My HC1 is stuck in a bootloop. I have tried multiple images but its always the same outcome: It never passes "Starting kernel...". Any help is appreciated! U-Boot 2017.05-armbian (Oct 01 2019 - 21:33:07 +0200) for ODROID-XU4 CPU: Exynos5422 @ 800 MHz Model: Odroid XU4 based on EXYNOS5422 Board: Odroid XU4 based on EXYNOS5422 Type: xu4 DRAM: 2 GiB MMC: EXYNOS DWMMC: 0, EXYNOS DWMMC: 1 MMC Device 0 ( SD ): 14.8 GiB Card did not respond to voltage select! mmc_init: -95, time 12 *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: No ethernet found. Press quickly 'Enter' twice to stop autoboot: 0 ** Unrecognized filesystem type ** ** File not found /boot.ini ** 12488 bytes read in 21 ms (580.1 KiB/s) cfgload addr = 0x50000000, Loading boot.ini from ext4 0:1 /boot/boot.ini cfgload: applying boot.ini... cfgload: setenv initrd_high "0xffffffff" cfgload: setenv fdt_high "0xffffffff" cfgload: setenv macaddr "00:1e:06:61:7a:55" cfgload: setenv rootdev "UUID=98622917-68a5-49ec-81d1-d61813cef122" cfgload: setenv rootfstype "ext4" cfgload: setenv console "both" cfgload: setenv verbosity "1" cfgload: if ext4load mmc 0:1 0x44000000 /boot/armbianEnv.txt || fatload mmc 0:1i ** File not found /boot/armbianEnv.txt ** ** Unrecognized filesystem type ** ** File not found armbianEnv.txt ** cfgload: if test "${console}" = "display" || test "${console}" = "both"; then si cfgload: if test "${console}" = "serial" || test "${console}" = "both"; then sei cfgload: setenv bootrootfs "${consoleargs} consoleblank=0 loglevel=${verbosity}" cfgload: setenv vout "hdmi" cfgload: setenv cecenable "false" # false or true cfgload: setenv governor "performance" cfgload: setenv ddr_freq 825 cfgload: setenv HPD "true" cfgload: setenv hdmi_tx_amp_lvl "31" cfgload: setenv hdmi_tx_lvl_ch0 "3" cfgload: setenv hdmi_tx_lvl_ch1 "3" cfgload: setenv hdmi_tx_lvl_ch2 "3" cfgload: setenv hdmi_tx_emp_lvl "6" cfgload: setenv hdmi_clk_amp_lvl "31" cfgload: setenv hdmi_tx_res "0" cfgload: setenv hdmi_phy_control "hdmi_tx_amp_lvl=${hdmi_tx_amp_lvl} hdmi_tx_lv" cfgload: ext4load mmc 0:1 0x40008000 /boot/zImage || fatload mmc 0:1 0x40008000e 5732768 bytes read in 583 ms (9.4 MiB/s) cfgload: ext4load mmc 0:1 0x42000000 /boot/uInitrd || fatload mmc 0:1 0x4200000d 5842674 bytes read in 582 ms (9.6 MiB/s) cfgload: if test "${board_name}" = "xu4"; then setenv fdtfile "exynos5422-odroii cfgload: if test "${board_name}" = "xu3"; then setenv fdtfile "exynos5422-odroii cfgload: if test "${board_name}" = "xu3l"; then setenv fdtfile "exynos5422-odroi cfgload: if test "${board_name}" = "hc1"; then setenv fdtfile "exynos5422-odroii cfgload: if ext4load mmc 0:1 0x00000000 "/boot/.next" || fatload mmc 0:1 0x0000i 0 bytes read in 17 ms (0 Bytes/s) Found mainline kernel configuration cfgload: ext4load mmc 0:1 0x44000000 /boot/dtb/${fdtfile} || fatload mmc 0:1 0x} 63484 bytes read in 50 ms (1.2 MiB/s) cfgload: fdt addr 0x44000000 cfgload: if test "${cecenable}" = "false"; then fdt rm /cec@101B0000; fi libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND cfgload: setenv bootargs "${bootrootfs} ${videoconfig} smsc95xx.macaddr=${macad" cfgload: dmc ${ddr_freq} cfgload: bootz 0x40008000 0x42000000 0x44000000 Kernel image @ 0x40008000 [ 0x000000 - 0x5779a0 ] ## Loading init Ramdisk from Legacy Image at 42000000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 5842610 Bytes = 5.6 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 44000000 Booting using the fdt blob at 0x44000000 Using Device Tree in place at 44000000, end 440127fb Starting kernel ...
  13. In the DTS, do you have any "dr_mode" ? If Yes, it must be set to "host" instead of "otg". Also, make sure you have the +5V activated on this USB port.
  14. I made a custom A20 board of which sch is very close to lime2 for a project (retrostone2) and I can't use USB0 as a classic USB port. The three USB (0 1 2) are all connected to regular USB type A connectors. No OTG used. However I can't get the USB0 to work. USB1 and USB2 works without issue. But USB0 will not recognize keyboard/any peripheral. I think it's probably because of OTG detect pins. I looked at the DTS, but I am having trouble understanding how OTG is emplemented there, how to unactivate it and just activate a classic USB port. Any ideas?
  15. If you mean the banner shown here as "OlinuXino-A20", Yes ! You need to edit the text in BOARD_NAME field in /etc/armbian-release ...
  16. Hello everyone. I found how to launch armbian in console in this topic I want to launch it in virt-manager because I want to save this vm. I was trying to run with such parameters and arguments -append 'earlyprintk loglevel=8 earlycon=uart8250,mmio32,0x1c28000,115200n8 console=ttyS0 root=/dev/sda1' \ -nographic -serial stdio -monitor none \ And when I launch it I have this error. But dev/sda1 exists. I checked qcow2 image. Is there any way to fix it ? Running armbian in coslole is not enough I want install xfce or any other desktop on it.
  17. New version 5.98_20191017 system with support to run from USB to rk3328. Details about using USB can be seen in this topic. The launch system from USB is tested on MVR9, support is in Armbian and Libreelec systems.
  18. OK your ./ has the same "error" like -formerly- ( see ) in the original armbian-build-system: actual line: su `stat --format=%U $SRC/.git` -c bash $TMPFILE and should be: su `stat --format=%U $SRC/.git` -c "bash $TMPFILE" compiling the image did work fine for aml-g12 but the debian buster version doenst work as smooth as the ubuntu bionic version on my Sunvell T95K Pro (S912), so I do use now ubuntu bionic on the T95K Pro: _ __ __ _ ____ _ ____ / \ | \/ | | / ___/ |___ \ / _ \ | |\/| | | | | _| | __) | / ___ \| | | | |__| |_| | |/ __/ /_/ \_\_| |_|_____\____|_|_____| Welcome to Debian Buster with Armbian Linux 5.4.0-rc3-aml-g12 package bsp-kernel[5.98] u-boot[5.98] dtb[Khadas VIM2] firmware[5.98] config[5.98] ================================================================================== _____ ___ ____ _ __ ____ ____ ___ |_ _/ _ \| ___|| |/ / | _ \| _ \ / _ \ | || (_) |___ \| ' /_____| |_) | |_) | | | | | | \__, |___) | . \_____| __/| _ <| |_| | |_| /_/|____/|_|\_\ |_| |_| \_\\___/ Welcome to Ubuntu Bionic with Armbian Linux 5.4.0-rc3-aml-g12 package bsp-kernel[5.98] u-boot[5.98] dtb[Khadas VIM2] firmware[5.98] config[5.98] root@t95k-pro( Problem I have: On both reboot doenst work, so I have to power-cycle. BUT on the debian-version the T95K Pro does boot into Linux again - with ubuntu the T95K Pro will boot into Android and I have to re-apply the aml_autoscript to get it boot into ubuntu :-(
  19. Thats a good choice - does run very stable
  20. at the end I've chosen opi one h3 512MB and opi zero plus h5 512MB, thank you to everybody :-)
  21. Is there a way to change the first image after the login in the Olimex A20 Lime 2? Best Reguard
  22. You will need to find a way to reset it or change this entire process.
  23. Hi Igor Thanks for responding. I had already including most of that patch, however had missed /arch/arm64/Makefile changes which I've added. Rebuilding and will continue to debug from there.
  24. Do not pay attention to the inscriptions. I have been using this group for a long time to release a single generic image for all s9xxx.
  25. "we can also jump u-boot to 2019.10" This can be done in any branch. Change or and you will notice that many u-boot patches will fail. They need to be adjusted or removed if they contribute nothing. Try. Job description = sources maintenance. Compare and adjust. If you can help maintain forum - moving topics here and there. Its also helpful.
  1. Load more activity