Search the Community

Showing results for tags 'solved'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • 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), S922X
    • NXP (Freescale)
    • Rockchip 3288 & 3328
    • Rockchip 3399
    • Other supported boards
  • Development
    • Development

Marker Groups

  • Members

Product Groups

  • Misc

Categories

  • Armbian

Categories

  • Applications

Calendars

  • Community Calendar

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 153 results

  1. I think I have somehow managed to remove my wlan0 interface. I've done a lot of testing on this M4V2 and am happy with my latest configuration and then I noticed my wlan0 interface is gone. I know it was there because I had tested it all (this box is going to my work office I'm not very good with the very low level stuff but this is what I have found sudo nmcli dev status DEVICE TYPE STATE CONNECTION eth0 ethernet connected Nano2Home lo loopback unmanaged -- jerry@nano2:~ $ sudo nmcli con show NAME UUID TYPE DEVICE Nano2Home bfe624a0-6c47-34c7-b947-350dd18b2059 ethernet eth0 Wi-Fi connection 1 62eadfc0-4456-4dc6-8624-771996a69834 wifi -- jerry@nano2:~ $ systemctl status sys-subsystem-net-devices-wlan0.device ● sys-subsystem-net-devices-wlan0.device - /sys/subsystem/net/devices/wlan0 Loaded: loaded Active: inactive (dead) Is it possible to recover from this or do I have to reinstall ? I really appreciate any help..
  2. Hello, nanopc t4 folks, Some, not so long time ago, I worked on fusb302.ko driver and device tree improvements in order to make USB Type-C port working properly in the mainline 5.* kernel. I managed to get DisplayPort over type-C + some general type-c handling improved before my board simply died. Unfortunately, I was not able to finish all the planned work and cannot continue further However, I guess, working DP is already fairly good achievement that might be interesting for many of us. Hereby, I want to publish some patches to the mainline!!! driver and device tree that add missing functionality, so one can get DP+type-C working on NanoPC T4 (and all RK3399 based boards with Fairchild FUSB302 chip for PD with relatively small DT adjustments). I would be very happy if results of my work can be helpful to others and extremely happy if there any volunteers, who are willing to continue work on this subject. My primary goal was to contribute to Armbian, first of all, with a potential mainline repo contribution. What was added: Extcon notifications support (type-c related cables) in the stock fusb302 driver (developed by Google folks, but also used by Intel if I understand correctly) DisplayPort altmode is registered automatically, if device tree has proper modelling for that DisplayPort altmode is entered as soon as DP cable connection is detected (both DP+USB3.0 and DP only pin assignments are supported) DisplayPort altmode is handled by the unified DP altmode driver rather than custom out-of-tree PD chip driver "connector" node modelling in the device tree according to the mainline kernel docs and modern requirements fusb node phandle is still specified as extcon source for Rockchip's proprietary drivers, however, last can be easily adjusted to resolve extcon directly from connector node link (as soon as extcon property is declared as deprecated for all new development). fusb302 driver is now correctly linked to dwc3 driver which provides role_switch functionality (+1 step to correct "Dual Role" mode handling based on the cable detection). This also eliminates annoying error message in the boot log: "OF: graph: no port node found in /i2c@ff3d0000/typec-portc@22" Please, also notice that type-c mode is forced to Host as in the most of rk3399 based SBC dtbs presently. This is rather a workaround for such boards, than a permanent solution, until all necessary bits are developed for correct role switching in the drivers. I kindly ask some NanoPC T4 owners to build mainline kernel with my patches and test whether expected functionality also works for you. Those patches apply to linux kernel since 5.6 when I started to work, but should also apply to way earlier versions according to my brief analysis of kernel commits history. fusb302-add-extcon.patch rk3399-nanopc-t4-type-c-modeling.patch
  3. I have an OPZ+ server with Armbian buster that has the following information cat /etc/armbian-release # PLEASE DO NOT EDIT THIS FILE BOARD=orangepizeroplus BOARD_NAME="Orange Pi Zero Plus" BOARDFAMILY=sun50iw2 BUILD_REPOSITORY_URL=https://github.com/armbian/build BUILD_REPOSITORY_COMMIT=c865c065-dirty VERSION=5.91 LINUXFAMILY=sunxi64 BRANCH=next ARCH=arm64 IMAGE_TYPE=stable BOARD_TYPE=conf INITRD_ARCH=arm64 KERNEL_IMAGE_TYPE=Image lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 10 (buster) Release: 10 Codename: buster uname -a Linux orangepizeroplus 4.19.63-sunxi64 #5.92 SMP Fri Aug 2 00:18:27 CEST 2019 aarch64 GNU/Linux ---- I see on the download page of Armbian OPZ+ That there is a new version of Armbian out. Armbian_20.05.2_Orangepizeroplus_buster_current_5.4.43.img.xz As you can see i am currently running the 4.19 kernel and version 5.91 of Armbian. ---- How do i go around to upgrade my current Armbian to the Newest version of Armbian. As in upgrade or similar. I dont wish to reinstall to much work in that. ---- Ty for reading, Darkyere
  4. hello everyone I have this board orange pi 4 V 1.3 Armbian Focal desktop mainline based kernel 5.4.y . I haven't audio through HDMI. what can I do ? I ran the media script for hw acceleration and i have good video result but not audio. Thx!
  5. Hello people, I have an Asus Tinker Board S and decided to use the Mainline Armbian for this board, love the new panfrost driver but seems it is glitching all over the place, icons in the menu disappear and reappear when mouse hovers over them, tick boxes do not show if they are ticked and only flicker when mouse is over them and applications menu keep redrawing all over when trying to use among the most prominent problems. Other operating systems work well in this matter. Anyone else is having these problems with the mainline 5.4.28 kernel build?
  6. I am in the middle of porting a proof of concept app from Raspberry Pi/Raspbian to its (hopefully) permanent home on Orange Pi PC/Armbian, and I am really loving the new environment. Now I need to get my non-standard HDMI display working. It's a 800x800 circular display from China that works fine on my Raspberry Pi once I figured out what the HDMI timings were (they weren't even on the data sheet!). As I learned when configuring the RPi the display does not report its resolution correctly, so it won't work out of the box, but in Raspbian you have the option to force the system to use your custom configuration defined in the config.txt file. I have looked at https://docs.armbian.com/Hardware_Allwinner/#how-to-reconfigure-video-output but I'm not seeing how to add the custom HDMI timings. I'm not sure how it could possibly work without it. Is there a series of steps I can take to force Armbian to look at my custom-defined display rules?
  7. 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.
  8. 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: http://ix.io/2lzX 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 https://forum.armbian.com/topic/4198-seed-our-torrents/) and syncthing running. Other programs I have not installed yet.
  9. 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
  10. 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.
  11. 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 https://www.armbian.com/cubox-i/, 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 https://images.solid-build.xyz/IMX6/Debian/, and the Cubox boots perfectly from that install. So proof Cubox, SDcard, method, power, HDMI etc are OK.
  12. 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?
  13. 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.
  14. EDIT: Just realized I posted this in the bug tracker forum. My apologies! See:
  15. 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.
  16. 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!
  17. 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.
  18. 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 usb_phy_generic.0.auto: usb_phy_generic.0.auto supply vcc not found, using dummy regulator [ 2.361648] musb-hdrc musb-hdrc.1.auto: MUSB HDRC host driver [ 2.361665] musb-hdrc musb-hdrc.1.auto: 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: musb-hdrc.1.auto [ 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.
  19. 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.
  20. 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.
  21. 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 [ debootstrap-ng.sh:216 ] [ error ] Installation of Armbian packages failed [ o.k. ] Process terminated [ error ] ERROR in function unmount_on_exit [ image-helpers.sh:60 ] [ 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.
  22. I'm looking for udev rules or some other way to read system LEDs without sudo. I tried https://github.com/todbot/blink1/blob/master/linux/51-blink1.rules, but I suspect it's not 100% what I need for the Duo.
  23. 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]
  24. Armbianmonitor for 5.4.6: http://ix.io/260C 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
  25. 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