Search the Community

Showing results for tags 'solved'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Announcements & first aid
    • Announcements
    • Board doesn't start
  • Community forums
    • Common issues
    • Peer to peer technical support
    • Feature Requests
    • TV boxes
    • General chit chat
  • Bug tracker
    • Allwinner A20
    • Allwinner H2 & H3
    • Allwinner H5 & A64
    • Allwinner H6
    • Armada A388, A3700
    • Amlogic S905(x)
    • NXP (Freescale)
    • Rockchip 3288 & 3328
    • Other supported boards
  • Development
    • Rockchip 3399
    • Development

Marker Groups

  • Members

Product Groups

  • Misc


  • Armbian


  • Giveaways


  • Applications


  • Community Calendar

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 147 results

  1. Hello everyone. From some time ago I´m working in an application that comunicates with some external devices, using GPIOs. With this aim, I´ve programmed my own driver with its methods, whose are automatic loaded at startup. My hardware is a BananaPi m2u, and kernel version is 5.4.35-sunxi. Now, I´ve to read an external HW that has 2 data lines, whose idle state is "high" and once per minute sends a packet of 26 bits of data. One of these lines is a Data0 signal, and the other is Data1 signal. Every pulse is around 100us, and there is an idle interval of about 2ms between one bit and the next. There is no way for data line 0 and data line 1to be active simultaneously. I`ve writed a new driver using Falling edge interrupts, data lines are connected to BMC224 (Pin 31 of header) & BCM225 (Pin 33 of header). Now I´m having troubles when pulses of external hardware arrives, I´m always loosing some of this 26 pulses. (I receive from 10 to 16 pulses, and lose the rest). I'm helping myself by using tail -f /cat/log/syslog to watch kernel messages (I used some temporally printk inside interrupt handler, just to debug). Here is a screenshot where you can see there is 6 correct received pulses before my problem arises (between time 829.536885 and 829.547099) root@bananapim2ultra:/home/pi/TK401# tail -f /var/log/syslog May 21 19:45:01 localhost CRON[1923]: (root) CMD (/usr/lib/armbian/armbian-truncate-logs) May 21 19:45:01 localhost wpa_supplicant[1138]: wlan0: Failed to initiate sched scan May 21 19:45:16 localhost kernel: [ 817.446427] usb 4-1: USB disconnect, device number 14 May 21 19:45:18 localhost kernel: [ 819.128519] usb 4-1: new low-speed USB device number 15 using ohci-platform May 21 19:45:18 localhost kernel: [ 819.355553] usb 4-1: New USB device found, idVendor=0458, idProduct=003a, bcdDevice= 1.00 May 21 19:45:18 localhost kernel: [ 819.355563] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 May 21 19:45:18 localhost kernel: [ 819.355569] usb 4-1: Product: USB Optical Mouse May 21 19:45:18 localhost kernel: [ 819.355575] usb 4-1: Manufacturer: Genius May 21 19:45:18 localhost kernel: [ 819.362882] input: Genius USB Optical Mouse as /devices/platform/soc/1c1c400.usb/usb4/4-1/4-1:1.0/0003:0458:003A.0010/input/input18 May 21 19:45:18 localhost kernel: [ 819.363214] hid-generic 0003:0458:003A.0010: input,hidraw2: USB HID v1.11 Mouse [Genius USB Optical Mouse] on usb-1c1c400.usb-1/input0 May 21 19:45:29 localhost kernel: [ 829.536885] 0 May 21 19:45:29 localhost kernel: [ 829.538920] 0 May 21 19:45:29 localhost kernel: [ 829.540969] 1 May 21 19:45:29 localhost kernel: [ 829.543009] 1 May 21 19:45:29 localhost kernel: [ 829.545057] 1 May 21 19:45:29 localhost kernel: [ 829.547099] 1 May 21 19:45:29 localhost kernel: [ 829.557355] 0 May 21 19:45:29 localhost kernel: [ 829.559398] 1 May 21 19:45:29 localhost kernel: [ 829.561445] 1 May 21 19:45:29 localhost kernel: [ 829.563487] 0 But suddenly, after sixth bit, there is no more handled pulses for a time period of 10ms, IMHO that looks like some higher hierarchy proccess is blocking my interrupts, and so, there is a lot of pulses lost. Also if I look at /proc/interrupts I can see there was 4 received interrupts from D0 (CPU0) and 6 from D1 (CPU0), so there is a match between info provided in both files. My testing code from user space is just a big sleep, so I think there is nothing there that can cause problems. Trying to understand where is this problem originated, I installed WiringPi (a library that provides access to GPIO, and includes interrupt driven inputs), I had to modify some pieces of code, cause they don´t like to work with "weird fruits Pi". With this apporoach I obtained a similar result (I loose about the same number of data bits), however if I use it in a Raspberry with Raspbian, I can read hundreeds od data packets with no looses at all. Could any of you please indicate where I can start looking for my error? Many thanks in advance! mhc.
  2. Hello, my BananaPi M1 sometimes just stops working. The maximum uptime is 5 days. Usually the time is shorter. The system simply hangs. I can no longer access the system via SSH. When I connect a monitor to HDMI, nothing is displayed, so I can log in. I have connected an external hard drive that is self-powered. I know the stories with the power supply. I have run ' stress -c 2 -m 1 '. The system remains stable. Time CPU load %cpu %sys %usr %nice %io %irq CPU PMIC DC-IN C.St 19:09:19: --- 0.69 10% 5% 5% 4% 0% 0% 49.3°C 42.4°C 5.10V 0/6 19:09:49: --- 2.16 100% 33% 66% 0% 0% 0% 50.2°C 43.6°C 5.10V 0/6 19:10:16: --- 3.18 100% 33% 65% 0% 0% 1% 50.2°C 44.0°C 5.06V 0/6 19:10:47: --- 3.58 100% 33% 64% 0% 0% 1% 51.0°C 44.4°C 5.05V 0/6 19:11:17: --- 3.96 100% 33% 64% 0% 0% 1% 51.4°C 44.9°C 5.03V 0/6 19:11:47: --- 4.34 100% 33% 65% 0% 0% 1% 51.1°C 45.0°C 5.09V 0/6 19:12:17: --- 4.42 100% 33% 65% 0% 0% 1% 51.3°C 45.3°C 5.07V 0/6 I also executed 'armbianmonitor -u'.The log is here: I checked syslog, daemon.log, user.log, armbian-ramlog.log for errors. With my amateurish understanding I did not find any error entries. In which logs can I still look up to search for errors? I have installed armbian buster minimal. Additionally I have pihole, transmission (to seed armbian torrents and syncthing running. Other programs I have not installed yet.
  3. Hi all, First place, sorry if it´s a very basic question, I was searching info and reading topics, but I did not found a solution for my problem. I`m working with Linux version 5.4.29-sunxi I´m trying to compile my own char device driver. I noticed that I forgot adding kernel-headers in my build, so I tried to add them via apt install linux-headers-next-sunxi After that, I can see a new directory /usr/src/linux-headers-4.19.62-sunxi but if I´m not wrong, modules compiled with this headers won´t work in my kernel, cause headers version does not match with my kernel version. So, could please someone give me a hint about getting correct header version, or if I´m completelly wrong? Many thanks in advances Grettings Mariano
  4. Armbian 5.90 stable Ubuntu bionic Orange Pi PC The Login Screen is very broken and after login, the Screen wents black and only the mouse Pointer is to see.
  5. Hi, My Solidrun Cubox I1-300-D has been running Armbian for quite some time (Samsung EVO SD card). However, I tried to update/upgrade, and my version was non-supported anymore (19.04?), so time for a fresh new image. I've tried three times (download image from, sha256 check, burn image with etcher, inspect file structure (looks good), and boot), but each time this happens: "Armbian universal operating system" + text ("Executing script at ...") splash screen, then a black screen, and then my TV says "no signal", and then nothing anymore. At the ethernetconnector, there is red LED on / flashing when the eternetcable is connected. I've let the box run for hours, but no effect. Keyboard eventually connected, but no effect. So ... tips? Is the Cubox I1-300-D still supported? Is there an older image (16.04?) that I can try? Does Armbian write anything to the SD card when it boots? Like "Hello, here I am" or dmesg? Because if so, I could check for that on the SD card in my laptop ... anything else? EDIT: I downloaded and installed sr-imx6-debian-buster-20191020-cli.img from, and the Cubox boots perfectly from that install. So proof Cubox, SDcard, method, power, HDMI etc are OK.
  6. Hi, I use OrangePi PC as my home samba server, as well as dlna server. It works from hdd, since I made a command nand-sata-install. I want to change the disc for a bigger one, how can I do this? If I will make rsync with all hdd will it be enough?
  7. Hi, there are invalid references inside sun50i-h5-fixup.scr, I think. I use NANOPINEO2, myself compiled linux-*-current-sunxi64_20.05.0-trunk_arm64.deb, kernel 5.4.28-sunxi64 #trunk SMP PREEMPT. amrbianEnv.txt (reduced): overlay_prefix=sun50i-h5 overlays=i2c0 uart1 uart2 usbhost1 usbhost2 usbhost3 param_uart1_rtscts=1 param_uart2_rtscts=1 For example, the row param_uart2_rtscts=1 leads to use following rows of sun50i-h5-fixup.scr: fdt get value tmp_phandle1 /soc/pinctrl@1c20800/uart2 phandle fdt get value tmp_phandle2 /soc/pinctrl@1c20800/uart2_rts_cts phandle fdt set /soc/serial@1c28800 pinctrl-names "default" "default" fdt set /soc/serial@1c28800 pinctrl-0 "<${tmp_phandle1}>" fdt set /soc/serial@1c28800 pinctrl-1 "<${tmp_phandle2}>" env delete tmp_phandle1 tmp_phandle2 There are some error messages during boot: Applying kernel provided DT fixup script (sun50i-h5-fixup.scr) ## Executing script at 44000000 tmp_bank=A tmp_pin=21 libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND 10046717 bytes read in 505 ms (19 MiB/s) As a result, the RTS/CTS handshaking for UART2 is unfunctional. May be for UART1 and UART3 is the same? I think the reason is that there are no paths /soc/pinctrl@1c20800/uart2 and /soc/pinctrl@1c20800/uart2_rts_cts inside the device tree specified by sun50i-h5-nanopi-neo2-v1.1.dtb file. The right paths are /soc/pinctrl@1c20800/uart2-pins and /soc/pinctrl@1c20800/uart2-rts-cts-pins, I think. Am I right? I've tried easy modification of SCR script - handshaking is now functional, but CRC is bad. If I am right, what is the right way to correct this? Script change (how properly?), DTB change, DTBO creation, ...? Moreover, look at this reduced listing of /sys/firmware/devicetree/base/soc/pinctrl@1c20800: csi-pins emac-rgmii-pins i2c0-pins i2c1-pins i2c2-pins i2s0-pins i2s1-pins mmc0-pins mmc1-pins mmc2-8bit-pins spi0-pins spi1-pins uart0-pa-pins uart1-pins uart1-rts-cts-pins uart2-pins uart2_rts_cts uart2-rts-cts-pins uart3-pins uart3-rts-cts-pins w1_pins Why are somewhere dashes "-" and somewhere underscores "_" ? Thank you.
  8. EDIT: Just realized I posted this in the bug tracker forum. My apologies! See:
  9. I am building my own armbian image using the armbian build environment. A substantial part of the image creation time is occupied by over-and-over recompiling the kernel. Sure, it does go faster the 2nd time, but it still takes a lot of time. The goal for me is not to make a custom kernel. I am totally happy with the kernel. The goal for me is to modify the rest of the image. They installed software, config, etc. Is there a way to reuse an existing kernel for this, instead of rebuilding a new one each time? Cheers, Dolf.
  10. Hi, I'm using a cubietruck and bananapi board (both A20 devices) for a long time (They run very stable for many years). I'm using uart3 for interfacing with arduino boards using the kernel overlay. When I upgrade the kernel to a version 5+ the overlay does not work anymore and ttyS3 is not working and missing in dmesg. The behaviour is the same on both boards. Autoboot in 1 seconds, press <Space> to stop switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 3708 bytes read in 34 ms (106.4 KiB/s) ## Executing script at 43100000 U-boot loaded from SD Boot script loaded from mmc 217 bytes read in 26 ms (7.8 KiB/s) 7343156 bytes read in 451 ms (15.5 MiB/s) 7744344 bytes read in 473 ms (15.6 MiB/s) Found mainline kernel configuration 42183 bytes read in 70 ms (587.9 KiB/s) 1078 bytes read in 96 ms (10.7 KiB/s) Applying kernel provided DT overlay sun7i-a20-uart3.dtbo 5845 bytes read in 82 ms (69.3 KiB/s) Applying kernel provided DT fixup script (sun7i-a20-fixup.scr) ## Executing script at 44000000 ## Loading init Ramdisk from Legacy Image at 43300000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 7343092 Bytes = 7 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 43000000 Booting using the fdt blob at 0x43000000 Loading Ramdisk to 498ff000, end 49fffbf4 ... OK reserving fdt memory region: addr=43000000 size=70000 Loading Device Tree to 4988c000, end 498fefff ... OK Starting kernel ... root@bananapi:~# cat /proc/version Linux version 5.4.20-sunxi (root@builder) (gcc version 8.3.0 (GNU Toolchain for the A-profile Architecture 8.3-2019.03 (arm-rel-8.36))) #20.02.1 SMP Mon Feb 17 02:09:41 CET 2020 root@bananapi:~# cat /boot/armbianEnv.txt verbosity=1 logo=disabled console=both disp_mode=1920x1080p60 overlay_prefix=sun7i-a20 rootdev=UUID=2a591b9c-5c95-34af-9d1a-a591d0134ad8 rootfstype=ext4 overlays=uart3 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u It looks like the overlay is loaded correct. Is there anything wrong in my setup, can I try something to make it work (4.19.104-sunxi is still working fine :) Thank you!
  11. I want to drive 2 SPI devices on my orangepi zero. I enabled `spi-spidev` and `spi-add-cs1` overlays and set `param_spidev_spi_bus` to 1. But by I still get only `/dev/spi1.0` available. When I add `param_spidev_spi_cs=1`, I get `/dev/spi1.1` but `/dev/spi1.0` disappears. Do I see it correctly that I can choose *either* `/dev/spi1.0` *or* `/dev/spi1.1` but not both with that overlay? How can I activate both cs pins? There are a bunch of example custom files out there, but none are meant specifically for the setup where I need spi1 (instead of spi0) and need to use a GPIO pin for cs1. And I can't really find any docs on how to write my own overlay. So any help is appreciated.
  12. Hi to all, I've a problem with my installation of Armbian. Currently i'm using Armbian Bionic on my pine A64 kernel version: Linux pine64 5.4.20-sunxi64 #20.02.1 SMP Mon Feb 17 02:37:37 CET 2020 aarch64 aarch64 aarch64 GNU/Linux When i attach my external hdd it doesn't show in /dev neither i can find it in the logs; daniele@pine64:~$ lsusb Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub daniele@pine64:~$ dmesg | grep usb [ 1.254270] usbcore: registered new interface driver usbfs [ 1.254306] usbcore: registered new interface driver hub [ 1.254366] usbcore: registered new device driver usb [ 2.035099] sun4i-usb-phy 1c19400.phy: failed to get clock usb0_phy [ 2.057968] ehci-platform 1c1a000.usb: EHCI Host Controller [ 2.057989] ehci-platform 1c1a000.usb: new USB bus registered, assigned bus number 1 [ 2.058095] ehci-platform 1c1a000.usb: irq 19, io mem 0x01c1a000 [ 2.071979] ehci-platform 1c1a000.usb: USB 2.0 started, EHCI 1.00 [ 2.072211] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.04 [ 2.072219] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 2.072225] usb usb1: Product: EHCI Host Controller [ 2.072231] usb usb1: Manufacturer: Linux 5.4.20-sunxi64 ehci_hcd [ 2.072237] usb usb1: SerialNumber: 1c1a000.usb [ 2.073450] ohci-platform 1c1a400.usb: Generic Platform OHCI controller [ 2.073468] ohci-platform 1c1a400.usb: new USB bus registered, assigned bus number 2 [ 2.073558] ohci-platform 1c1a400.usb: irq 20, io mem 0x01c1a400 [ 2.136249] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 5.04 [ 2.136257] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 2.136263] usb usb2: Product: Generic Platform OHCI controller [ 2.136269] usb usb2: Manufacturer: Linux 5.4.20-sunxi64 ohci_hcd [ 2.136275] usb usb2: SerialNumber: 1c1a400.usb [ 2.137581] usbcore: registered new interface driver usb-storage [ 2.142711] usbcore: registered new interface driver usbhid [ 2.142713] usbhid: USB HID core driver [ 2.280060] ehci-platform 1c1b000.usb: EHCI Host Controller [ 2.280082] ehci-platform 1c1b000.usb: new USB bus registered, assigned bus number 3 [ 2.280183] ehci-platform 1c1b000.usb: irq 21, io mem 0x01c1b000 [ 2.295979] ehci-platform 1c1b000.usb: USB 2.0 started, EHCI 1.00 [ 2.296153] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.04 [ 2.296161] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 2.296167] usb usb3: Product: EHCI Host Controller [ 2.296173] usb usb3: Manufacturer: Linux 5.4.20-sunxi64 ehci_hcd [ 2.296178] usb usb3: SerialNumber: 1c1b000.usb [ 2.297275] ohci-platform 1c1b400.usb: Generic Platform OHCI controller [ 2.297293] ohci-platform 1c1b400.usb: new USB bus registered, assigned bus number 4 [ 2.297386] ohci-platform 1c1b400.usb: irq 22, io mem 0x01c1b400 [ 2.360140] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 5.04 [ 2.360147] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 2.360154] usb usb4: Product: Generic Platform OHCI controller [ 2.360160] usb usb4: Manufacturer: Linux 5.4.20-sunxi64 ohci_hcd [ 2.360165] usb usb4: SerialNumber: 1c1b400.usb [ 2.361268] usb_phy_generic supply vcc not found, using dummy regulator [ 2.361648] musb-hdrc MUSB HDRC host driver [ 2.361665] musb-hdrc new USB bus registered, assigned bus number 5 [ 2.361876] usb usb5: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.04 [ 2.361884] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 2.361890] usb usb5: Product: MUSB HDRC host driver [ 2.361896] usb usb5: Manufacturer: Linux 5.4.20-sunxi64 musb-hcd [ 2.361901] usb usb5: SerialNumber: [ 5.366107] axp20x-usb-power-supply axp20x-usb-power-supply: DMA mask not set daniele@pine64:~$ ls -l /dev/sd* ls: cannot access '/dev/sd*': No such file or directory The same hdd is recognized correctly in my laptop: Bus 001 Device 013: ID 1bcf:0c31 Sunplus Innovation Technology Inc. SPIF30x Serial-ATA bridge I've installed the full firmware package from the armbian-config tools, other usb dongles are recognized correctly. What can i do now? Thanks, Daniele.
  13. I have two NanoPi R1s, both with Armbian Buster. I want to use both as wireless access points, however the wifi seems to be problematic. It always works at first, but not anymore after updating, changing the config and rebooting. My hostapd config is the following: # # armbian hostapd configuration example # # nl80211 mode # ssid=[myssid, contains some numbers] interface=wlan0 hw_mode=g channel=6 [11 on the other one] #bridge=br0 driver=nl80211 logger_syslog=0 logger_syslog_level=0 wmm_enabled=1 wpa=2 preamble=1 wpa_psk=[random thing armbian-config generated] wpa_passphrase=[secret] wpa_key_mgmt=WPA-PSK wpa_pairwise=CCMP rsn_pairwise=CCMP wpa_strict_rekey=1 wpa_disable_eapol_key_retries=1 ieee80211w=2 auth_algs=1 macaddr_acl=0 noscan=1 ## IEEE 802.11n ieee80211n=1 ht_capab=[DSSS_CK-40][HT20+] country_code=DE ieee80211d=1 ## IEEE 802.11n ### IEEE 802.11a #hw_mode=a ### IEEE 802.11a ### IEEE 802.11ac #ieee80211ac=1 #vht_capab=[MAX-MPDU-11454][SHORT-GI-80][TX-STBC-2BY1][RX-STBC-1][MAX-A-MPDU-LEN-EXP3] #vht_oper_chwidth=1 #vht_oper_centr_freq_seg0_idx=42 ### IEEE 802.11ac # controlling enabled ctrl_interface=/var/run/hostapd ctrl_interface_group=0 Systemd says hostapd is loaded, active and exited. The wifi is not detectable by any of my devices. If I try to start hostapd manually via hostapd /etc/resolv.conf , it says Configuration file: /etc/hostapd.conf wlan0: interface state UNINITIALIZED->COUNTRY_UPDATE wlan0: Could not connect to kernel driver Using interface wlan0 with hwaddr 18:93:7f:73:4a:ec and ssid "[SSID from config file]" random: Only 18/20 bytes of strong random data available from /dev/random random: Not enough entropy pool available for secure operations WPA: Not enough entropy in random pool for secure operations - update keys later when the first station connects wlan0: Could not connect to kernel driver Interface initialization failed wlan0: interface state COUNTRY_UPDATE->DISABLED wlan0: AP-DISABLED wlan0: Unable to setup interface. wlan0: interface state DISABLED->DISABLED wlan0: AP-DISABLED wlan0: CTRL-EVENT-TERMINATING hostapd_free_hapd_data: Interface wlan0 wasn't started nl80211: deinit ifname=wlan0 disabled_11b_rates=0 Not sure whether this is a bug or an error on my side. It used to work with OpenWrt, however the problem there is the only images for it are provided by FriendlyArm (there are no official images by the OpenWrt team), and that image is still on version 18.01, which doesn't get any security updates anymore. EDIT: I maybe also should have mentioned the WiFi and hotspot options disappear in `armbian-config`. `ip addr` or `ip link` still show the wlan0 interface however. Maybe a recent update broke the driver or so? Still not sure whether I should move this to H3 bug reports. EDIT 2: I now tried to connect to a different WiFi with `wpa_supplicant`. Works with both `wext` and `nl80211` drivers (the former returns some `IOCTL` errors, but isn't used by hostapd anyway, and it still seems to work nevertheless). So the issue is probably more related to hostapd than to the driver. EDIT 3: `iw list` said it only supported CMAC-128 ciphers, so I removed any config that would use 256 bit ciphers. Also various sources suggested this was an old bug, and I needed to run `nmcli radio wifi off` and `rfkill unblock wlan` before starting hostapd, however that didn't change anything.
  14. I recently updated from very old Armbian image. The update was not smooth so I had to re-image my device with the newest version. After that USB devices cannot be detected at all. I tried USB keyboard and 3D printer (is should looks like generic serial device). Keyboard works perfectly during u-boot but stops working as soon as kernel starts. lsusb doesn't show any devices: $ lsusb -t /: Bus 09.Port 1: Dev 1, Class=root_hub, Driver=musb-hdrc/1p, 480M /: Bus 08.Port 1: Dev 1, Class=root_hub, Driver=ohci-platform/1p, 12M /: Bus 07.Port 1: Dev 1, Class=root_hub, Driver=ohci-platform/1p, 12M /: Bus 06.Port 1: Dev 1, Class=root_hub, Driver=ohci-platform/1p, 12M /: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=ehci-platform/1p, 480M /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=ehci-platform/1p, 480M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=ehci-platform/1p, 480M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci-platform/1p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-platform/1p, 480M So it seems like some generic issue with USB support. Now I'm using kernel 5.4.20-sunxi, also tried 4.19.104-sunxi and some other available in armbian-config - all give the same result. Any help with making it work again is very appreciated.
  15. Hi, After building a DEV Pine64 image successfully, I wanted to build a Dev BananaPI image to update 2 banana pis. Unfortunately I have this error (using this commit id : e7aeffb1) : Setting up nplan (0.36.3) ... Setting up networkd-dispatcher (1.7-0ubuntu3.3) ... Installing new version of config file /etc/default/networkd-dispatcher ... Setting up gnupg (2.2.4-1ubuntu1.1) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... Processing triggers for initramfs-tools (0.130ubuntu3.5) ... [ o.k. ] Installing packages for [ Armbian ] Reading package lists... Building dependency tree... Reading state information... E: Unable to locate package armbian-firmware [ error ] ERROR in function create_rootfs_cache [ ] [ error ] Installation of Armbian packages failed [ o.k. ] Process terminated [ error ] ERROR in function unmount_on_exit [ ] [ error ] debootstrap-ng was interrupted [ o.k. ] Process terminated I'm trying to generate a new image. It's only the second image I'm trying to build, so maybe I forgot some cleanup somewhere. Thanks in advance.
  16. I'm looking for udev rules or some other way to read system LEDs without sudo. I tried, but I suspect it's not 100% what I need for the Duo.
  17. I noticed with the latest bionic image on the Duo it does a soft shutdown when you use the built in button. The problem is I use this button for my own uses. Can this feature be disabled and relinquish control of the button? gpioinfo | grep k1 line 3: unnamed "k1" input active-low [used]
  18. Armbianmonitor for 5.4.6: From switching between 4.19.x and 5.4.x kernels I noticed that the lower cpu frequencies got missing. It should start at 120MHz like this: root@horangepione:~# uname -a Linux honeypot2 4.19.84-sunxi #19.11.3 SMP Mon Nov 18 18:39:42 CET 2019 armv7l GNU/Linux root@horangepione:~# cpufreq-info -o minimum CPU frequency - maximum CPU frequency - governor CPU 0 120000 kHz ( 11 %) - 1008000 kHz (100 %) - ondemand CPU 1 120000 kHz ( 11 %) - 1008000 kHz (100 %) - ondemand CPU 2 120000 kHz ( 11 %) - 1008000 kHz (100 %) - ondemand CPU 3 120000 kHz ( 11 %) - 1008000 kHz (100 %) - ondemand Though on 5.4.x the minimum frequency is 480MHz. Since the default cpufrequtils file was not there I created one: cat /etc/default/cpufrequtils # WARNING: this file will be replaced on board support package (linux-root-...) upgrade ENABLE=true MIN_SPEED=120000 MAX_SPEED=1200000 GOVERNOR=ondemand It seems to have an effect because when changing the minimum frequency it clocks up as it should. Frequencies beyond 1.01GHz missing as well but that is a different story...I guess. Cheers Werner
  19. I installed Armbian_5.75_Orangepizeroplus2-h3_Debian_stretch_next_4.19.20. But it can't boot up. These image can boot up. Armbian_5.65_Orangepizeroplus2-h3_Debian_stretch_next_4.14.78 Armbian_5.69_Orangepizeroplus2-h3_Debian_stretch_next_4.19.13
  20. Hello, I am using up to date Armbian - Debian Buster with Armbian Linux 4.19.69-meson64 Linux version 4.19.69-meson64 (root@builder) (gcc version 7.4.1 20181213 [linaro-7.4-2019.02 revision 56ec6f6b99cc167ff0c2f8e1a2eed33b1edc85d4] (Linaro GCC 7.4-2019.02)) #5.95 SMP PREEMPT Mon Sep 2 01:21:39 CEST 2019. I have encountered Ethernet interface lockup on medium traffic (after 30s-120s when copying big files from external usb disk by sshfs - 240Mb/s). At high/medium Ethernet traffic the issue always occurs. It is most likely caused by some kernel update because I didn't have such problem before. Similar issue: [ 1584.165514] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: discard [ 1689.827553] ------------[ cut here ]------------ [ 1689.827600] NETDEV WATCHDOG: eth0 (meson8b-dwmac): transmit queue 0 timed out [ 1689.827721] WARNING: CPU: 0 PID: 0 at net/sched/sch_generic.c:461 dev_watchdog+0x2b4/0x2c0 [ 1689.827736] Modules linked in: uas nf_log_ipv4 nf_log_common nft_limit xt_tcpudp xt_multiport xt_LOG xt_limit xt_conntrack nft_counter nft_chain_nat_ipv4 ipt_MASQUERADE nf_nat_ipv4 nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nft_compat nf_tables nfnetlink meson_rng rng_core scpi_hwmon meson_gxbb_wdt ip_tables x_tables realtek [ 1689.827866] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.19.69-meson64 #5.95 [ 1689.827871] Hardware name: Hardkernel ODROID-C2 (DT) [ 1689.827881] pstate: 20000005 (nzCv daif -PAN -UAO) [ 1689.827892] pc : dev_watchdog+0x2b4/0x2c0 [ 1689.827901] lr : dev_watchdog+0x2b4/0x2c0 [ 1689.827906] sp : ffff000008003da0 [ 1689.827912] x29: ffff000008003da0 x28: 0000000000000005 [ 1689.827926] x27: 0000000000000020 x26: 00000000ffffffff [ 1689.827939] x25: 0000000000000140 x24: ffff800071250480 [ 1689.827952] x23: ffff80007125045c x22: ffff800070ca5940 [ 1689.827965] x21: ffff000008e77000 x20: ffff800071250000 [ 1689.827978] x19: 0000000000000000 x18: ffffffffffffffff [ 1689.827991] x17: 0000000000000000 x16: 0000000000000000 [ 1689.828004] x15: ffff000008e93000 x14: 00000000fffffff0 [ 1689.828017] x13: ffff000008f2786a x12: ffff000008e93000 [ 1689.828030] x11: 0000000000000000 x10: ffff000008f26000 [ 1689.828043] x9 : 0000000000000000 x8 : 0000000000000001 [ 1689.828055] x7 : 0000000000000000 x6 : 0000000000000123 [ 1689.828068] x5 : 0000000000000000 x4 : 0000000000000001 [ 1689.828080] x3 : 0000000000000000 x2 : ffff000008e7c358 [ 1689.828093] x1 : 2481295eb9750900 x0 : 0000000000000000 [ 1689.828105] Call trace: [ 1689.828117] dev_watchdog+0x2b4/0x2c0 [ 1689.828131] call_timer_fn+0x20/0x78 [ 1689.828143] expire_timers+0xa4/0xb0 [ 1689.828154] run_timer_softirq+0xe4/0x1a0 [ 1689.828164] __do_softirq+0x10c/0x200 [ 1689.828174] irq_exit+0xac/0xc0 [ 1689.828186] __handle_domain_irq+0x60/0xb0 [ 1689.828194] gic_handle_irq+0x58/0xa8 [ 1689.828201] el1_irq+0xb0/0x128 [ 1689.828212] arch_cpu_idle+0x10/0x18 [ 1689.828220] do_idle+0x1d4/0x298 [ 1689.828229] cpu_startup_entry+0x20/0x28 [ 1689.828243] rest_init+0xcc/0xd8 [ 1689.828256] start_kernel+0x3d4/0x400 [ 1689.828269] ---[ end trace b79bbf67547ae10f ]--- [ 1689.828334] meson8b-dwmac c9410000.ethernet eth0: Reset adapter. [ 1689.909766] RTL8211F Gigabit Ethernet stmmac-0:00: attached PHY driver [RTL8211F Gigabit Ethernet] (mii_bus:phy_addr=stmmac-0:00, irq=37) [ 1689.922902] meson8b-dwmac c9410000.ethernet eth0: No Safety Features support found [ 1689.922925] meson8b-dwmac c9410000.ethernet eth0: PTP not supported by HW [ 1693.046757] meson8b-dwmac c9410000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx [ 1737.955616] meson8b-dwmac c9410000.ethernet eth0: Reset adapter. [ 1738.037764] RTL8211F Gigabit Ethernet stmmac-0:00: attached PHY driver [RTL8211F Gigabit Ethernet] (mii_bus:phy_addr=stmmac-0:00, irq=37) [ 1738.050715] meson8b-dwmac c9410000.ethernet eth0: No Safety Features support found [ 1738.050737] meson8b-dwmac c9410000.ethernet eth0: PTP not supported by HW [ 1741.822114] meson8b-dwmac c9410000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
  21. Hi All, Just wanted to share a good story using armbian. I have used in the past 1-wire probes for temperature, and the process included decompiling, editing and recompiling dtb for my Banana Pi M1, which was not easy at all. Every firmware update deleted by changes and had to redo de recompilation. With latest kernels and armbian version, the process is now extremely easy, just edit: /boot/armbianEnv.txt Adding this lines: overlays=w1-gpio param_w1_pin=PI3 # desired pin(7th pin (GCLK) or number 4 on first column where number 1 is +3V) param_w1_pin_int_pullup=1 # internal pullup-resistor: 1=on, 0=off I just struggled a little bit to find the GPIO code (decompiled dtb and checked possible candidates). Information about temperature is here: cat /sys/bus/w1/devices/XX-YYYYYYY[this is your probe serial, if you have more they will be in /sys/bus/w1/devices/] /w1_slave You have plenty of information here, but don't need to do all they explain, just my edition has been enough:
  22. TRYING TO CLONE EMMC FROM ONE NEO CORE INTO ANOTHER. I found this link below : I still don't know if it works since i had to enter FEL MODE which i could not. maybe i am trying in a wrong way. SO how could i get a clone EMMC of nanopi neo core (taking into consideration it might not have FEL mode)? but if it does then how to enter this mode? and how to run this clone on another nanopi neo core?
  23. Hello, Just find out that my USB ports are not working. Quick dig shows that the are disabled: # lsusb # dmesg |grep usb [ 0.000000] Kernel command line: root=UUID=e8491c09-2260-4706-a9a4-1f9f96af1232 rootwait rootfstype=ext4 console=ttyS0,115200 console=tty1 disp.screen0_output_mode=1920x1080p60 panic=10 consoleblank=0 loglevel=1 ubootpart=5b507211-01 ubootsource=mmc usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u sunxi_ve_mem_reserve=0 sunxi_g2d_mem_reserve=0 sunxi_fb_mem_reserve=16 cgroup_enable=memory swapaccount=1 [ 1.308752] usbcore: registered new interface driver usbfs [ 1.308799] usbcore: registered new interface driver hub [ 1.308867] usbcore: registered new device driver usb [ 2.702281] usbcore: registered new interface driver usb-storage [ 2.736004] usbcore: registered new interface driver usbhid [ 2.736007] usbhid: USB HID core driver [ 2.858064] usb0-vbus: disabling [ 2.858070] usb1-vbus: disabling [ 2.858079] usb2-vbus: disabling I try to check overlays, but there is nothing related to usb: I try to run sunxi-pio -m PB10<1><0><default><1> sunxi-pio -m PB11<1><0><default><1> as described here: bust without success. Provided doku: /boot/dtb-4.19.57-sunxi/overlay/README.sun7i-a20-overlays does not say anything about USB hosts and I see that there is no PB10 and PB11. My /boot/armbianEnv.txt looks following, I believe something wrong with usbstoragequirks. # cat /boot/armbianEnv.txt verbosity=1 logo=disabled console=both disp_mode=1920x1080p60 overlay_prefix=sun7i-a20 #rootdev=UUID=5241c6ce-98c7-4352-8c81-808c54cf4cf7 rootdev=UUID=e8491c09-2260-4706-a9a4-1f9f96af1232 rootfstype=ext4 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u Any Ideas how to enable it?
  24. Hello, I have trouble with my SD Card - it goes in Read Only mode. What I have: I have Running System from the HDD (installed by nand-sata-install command) My Cubietruck is online for now, but I'm afraid do switch it off. I try to run dd command to make a backup of RO SD card and reuse image on a new SD card, but it does not succeed: # dd if=/dev/mmcblk0 bs=10M | gzip -c > /media/dataPartition/sdcard.img.gz dd: error reading '/dev/mmcblk0': Input/output error 0+0 records in 0+0 records out 0 bytes copied, 0.00503184 s, 0.0 kB/s I read the forum regarding backup and restore and my question is following: Is there is a way to prepare new SD card and simply insert it into the running machine and reboot without starting from zero? Like set only the boot partition and clone the rest from hdd? Try to clone boot from the old SD? Make it sense to pull out old SD card and try to make backup of it on Laptop and then write this image to the new SD card?
  25. Hi, I spent several days trying to figure this out, which is a bit confusing given all the information that is available and posts and wikis saying that "Waveshare" LCDs are supposed to work, but something is still not right, hope you guys can help. What I have: ASUS Tinker Board S, flashed with Armbian_5.90_Tinkerboard_Debian_buster_default_4.4.182_desktop.img Updated to 4.19.57-rockchip via armbian-config (in order to get the fbtft* modules that were missing in 4.4). The LCD is a 3.5" original Waveshare 32a panel. I started by adding the overlay for this screen (i.e. my armbianEnv.txt has these overlays: overlays=i2c1 i2c4 spi2 waveshare35a-tinker uart1 uart2): I have a serial console connection and I could see that the overlay is getting loaded upon boot: Applying kernel provided DT overlay rockchip-i2c1.dtbo 286 bytes read in 1 ms (279.3 KiB/s) Applying kernel provided DT overlay rockchip-i2c4.dtbo 311 bytes read in 1 ms (303.7 KiB/s) Applying kernel provided DT overlay rockchip-spi2.dtbo 2224 bytes read in 2 ms (1.1 MiB/s) Applying kernel provided DT overlay rockchip-waveshare35a-tinker.dtbo 287 bytes read in 2 ms (139.6 KiB/s) Applying kernel provided DT overlay rockchip-uart1.dtbo 287 bytes read in 1 ms (280.3 KiB/s) Applying kernel provided DT overlay rockchip-uart2.dtbo 232 bytes read in 1 ms (226.6 KiB/s) Applying kernel provided DT fixup script (rockchip-fixup.scr) Adding the above overlay made the touchscreen work out of the box, however the framebuffer device didn't. In dmesg I could see the following: [ 15.706674] fbtft: module is from the staging directory, the quality is unknown, you have been warned. [ 15.712403] fb_ili9486: module is from the staging directory, the quality is unknown, you have been warned. [ 15.712696] rockchip-pinctrl pinctrl: unable to find group for node waveshare35a_pins [ 15.712708] fb_ili9486: probe of spi2.0 failed with error -22 I read the driver sources, pinctrl documentation, overlay documentation, but being a userspace coder I did not really know what to make of all this and the above pinctrl error message. The waveshare nodes were available in the live device tree, so I am not sure why this line triggers and where this "group" is supposed to be coming from: I then tried to configure the fbtft_device driver manually using the following parameters (tried to use the values from the waveshare dts): modprobe fbtft_device custom name=fb_ili9486 gpios=dc:163,reet:171 speed=15000000 busnum=2 rotate=270 fps=30 txbuflen=32768 bgr=0 width=480 height=320 The above made half of the screen to react, settig the rotation to 0 allowed to access the whole screen (tried catting /dev/random into /dev/fb0 which fills the screen with random colored pixels). I added xorg settings as suggested in the tinkerboard wiki and started xorg: Section "Device" Identifier "Rockchip Graphics" Driver "fbdev" Option "fbdev" "/dev/fb0" Option "DRI" "2" EndSection However the image looked totally distorted (I had the feeling that its drawing every other line), it was however vaguely recognizable as some text / X login screen. Just out of curiosity I removed the overlay, rebooted and again loaded the driver as above with the same result (only that touchscreen did not work anymore as expected). I am adding a full dmesg output with the overlay applied, the first fbtft load attempt is the "automatic" one and shows the rockchip pinctrl error, the second fbtft loading comes from my manual modprobe line which I pasted earlier. I have no idea where to go from here, I thought those Waveshare screens are well supported, and from what I read they seem to work for others. What am I missing? Kind regards, Jin P.S. ...couple of hours later... Turned out that the results are a lot better if width and height parameters are left out. While the dts suggests to use bgr=0, bgr=1 gives correct colors, but it seems that the gamma is totally off. I also tried taking the init sequence from the dts and passing it to fbtft_device, but I could not see any difference. So right now I ended up with the following line and results: modprobe fbtft_device custom name=fb_ili9486 bgr=1 gpios=dc:163,reset:171 speed=15000000 busnum=2 fps=30 txbuflen=32768 Original image for comparison: So, some progress at last, I'd however be still interested in fixing the pinctrl problem and understanding why the dts would not work... Next question of course - how to come up with proper gamma values?