Jump to content

Search the Community

Showing results for tags 'nanopineo2'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Armbian
    • Armbian project administration
  • Community
    • Announcements
    • SBC News
    • Framework and userspace feature requests
    • Off-topic
  • Using Armbian
    • Beginners
    • Software, Applications, Userspace
    • Advanced users - Development
  • Standard support
    • Amlogic meson
    • Allwinner sunxi
    • Rockchip
    • Other families
  • Community maintained / Staging
    • TV boxes
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families
  • Support

Categories

  • Official giveaways
  • Community giveaways

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Matrix


Mastodon


IRC


Website URL


XMPP/Jabber


Skype


Github


Discord


Location


Interests

  1. I'm trying to use a c270 webcam, but it is not listed on USB devices. Can someone help me?
  2. I've got a Sony RX100VA camera that I want to connect to the NanoPi Neo2 running Armbian Buster. On the Camera I can select the type of USB connection: -Auto -Mass Storage -MTP -PC Remote My intention is to use the PC Remote connection for use with gphoto2, this works fine on a PC with Ubuntu 18.04, but when I connect the camera to the Nano Pi Neo2 with Armbian, the camera display shows connecting (but doesn't connect). I suspect a bug in the OS, but I am unsure how to find it. lsusb gives the following report with an error: can't get debug descriptor: Resource temporarily unavailable root@nanopineo2:~# lsusb -d 054c:0cb2 -v Bus 003 Device 019: ID 054c:0cb2 Sony Corp. Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x054c Sony Corp. idProduct 0x0cb2 bcdDevice 2.00 iManufacturer 1 Sony iProduct 2 DSC-RX100M5A iSerial 3 C7A5602C40B2 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 0x0027 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xc0 Self Powered MaxPower 100mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 6 Imaging bInterfaceSubClass 1 Still Image Capture bInterfaceProtocol 1 Picture Transfer Protocol (PIMA 15470) iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0020 1x 32 bytes bInterval 7 Device Qualifier (for other device speed): bLength 10 bDescriptorType 6 bcdUSB 2.00 bDeviceClass 0 bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 bNumConfigurations 1 can't get debug descriptor: Resource temporarily unavailable Device Status: 0x0000 (Bus Powered) Mounting as a mass storage device works fine, but then I can't use it with gphoto2. How do I find the bug?
  3. Good evening, In your opinion, what is the best alternative to the NanoPi NEO2? I don't need wifi or sata. I'm looking for a stable and qualitative armbian with a gigabit and usb port. Is there a better performing armbian that the NEO2 has for less than 40$? Thanks
  4. Hi all, Running Armbian Ubuntu 18.04 with stock neo2 4.19.20 kernel I tried installing https://github.com/friendlyarm/WiringNP but after installation `gpio readall` says : "This NanoPi model is currently not supported." However all the wiki's and the Github page says it's supported.......? I can see GPIO in the sys fs at /sys/class/gpio/ but I was hoping to have an easier time with it than manually exporting each pin and calculating offsets for pins with scraps of info online etc. Objective 1: Read a high/low 3.3v/0v status from a GPIO Objective 2: Read an analog voltage, using an ADC. Does the H5 include an ADC? When I look in http://wiki.friendlyarm.com/wiki/images/d/de/Allwinner_H5_Datasheet_V1.0.pdf Page 13 says 2.1.4.9.KEYADC * Analog to digital converter with 6-bit resolution for key application * Maximum sampling frequency up to 250 Hz * Supports general key, hold key and already hold key * Supports single , normal and continuous work mode I don't need high speed sampling, don't need interrupts, the simpler and easier the implementation the better. Any help will be much appreciated PS: How to fix friendlyarm/WiringNP friendlyarm/WiringNP is not accepting issues on their github repo, but it seems to be the best fork out there. How can we get them to accept issues and how can we fix the issue? http://forked.yannick.io/friendlyarm/WiringNP
  5. 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.
  6. Hi, I want to expand my NanoPi-NEO2 more uart ports through I2C, so I make a choice to use a sc16is750 module( just like sparkfun sc16is750 ). Below is all of my system information: pi@nanopineo2:~$ uname -a Linux nanopineo2 5.4.20-sunxi64 #20.02.1 SMP Mon Feb 17 02:37:37 CET 2020 aarch64 aarch64 aarch64 GNU/Linux First step ,I edit a device tree overlay for the sc16is750 named sc16is750-i2c.dts as below: pi@nanopineo2:/boot/overlay-user$ sudo nano sc16is750-i2c.dts /dts-v1/; /plugin/; / { compatible = "allwinner,sun4i-a10", "allwinner,sun7i-a20", "allwinner,sun8i-h3", "allwinner,sun50i-a64", "allwinner,sun50i-h5"; fragment@0 { /* This fragment is required only if using interrupts */ target = <&pio>; __overlay__ { sc16is750_pin_irq: sc16is750_pin_irq { pins = "PA17"; function = "irq"; bias-pull-up; }; }; }; fragment@1 { target = <&i2c1>; __overlay__ { #address-cells = <1>; #size-cells = <0>; sc16is750: sc16is750@4d { compatible = "nxp,sc16is750"; reg = <0x4d>; status = "okay"; clocks = <&sc16is750_clk>; gpio-controller; #gpio-cells = <3>; /* Below are optional properties for supporting interrupts */ interrupt-controller; #interrupt-cells = <3>; interrupt-parent = <&pio>; interrupts = <0 17 2>; /* PG11 IRQ_TYPE_EDGE_FALLING */ pinctrl-names = "default"; pinctrl-0 = <&sc16is750_pin_irq>; sc16is750_clk: sc16is750_clk { compatible = "fixed-clock"; #clock-cells = <0>; clock-frequency = <14745600>; }; }; }; }; __overrides__ { int_pin = <&sc16is750>,"interrupts:0"; addr = <&sc16is750>,"reg:0"; }; }; Second step, I add the sc16is750-i2c.dts to my /boot/overlay-usr as below: pi@nanopineo2:/boot/overlay-user$ sudo armbian-add-overlay sc16is750-i2c.dts Compiling the overlay Copying the compiled overlay file to /boot/overlay-user/ Reboot is required to apply the changes Afterthen, I checked sc16is750-i2c.dtbo as below: pi@nanopineo2:/boot/overlay-user$ fdtdump sc16is750-i2c.dtbo **** fdtdump is a low-level debugging tool, not meant for general use. **** If you want to decompile a dtb, you probably want **** dtc -I dtb -O dts <filename> /dts-v1/; // magic: 0xd00dfeed // totalsize: 0x5f8 (1528) // off_dt_struct: 0x38 // off_dt_strings: 0x4d0 // off_mem_rsvmap: 0x28 // version: 17 // last_comp_version: 16 // boot_cpuid_phys: 0x0 // size_dt_strings: 0x128 // size_dt_struct: 0x498 / { compatible = "allwinner,sun4i-a10", "allwinner,sun7i-a20", "allwinner,sun8i-h3", "allwinner,sun50i-a64", "allwinner,sun50i-h5"; fragment@0 { target = <0xffffffff>; __overlay__ { sc16is750_pin_irq { pins = "PA17"; function = "irq"; bias-pull-up; phandle = <0x00000002>; }; }; }; fragment@1 { target = <0xffffffff>; __overlay__ { #address-cells = <0x00000001>; #size-cells = <0x00000000>; sc16is750@4d { compatible = "nxp,sc16is750"; reg = <0x0000004d>; status = "okay"; clocks = <0x00000001>; gpio-controller; #gpio-cells = <0x00000003>; interrupt-controller; #interrupt-cells = <0x00000003>; interrupt-parent = <0xffffffff>; interrupts = <0x00000000 0x00000011 0x00000002>; pinctrl-names = "default"; pinctrl-0 = <0x00000002>; phandle = <0x00000003>; sc16is750_clk { compatible = "fixed-clock"; #clock-cells = <0x00000000>; clock-frequency = <0x00e10000>; phandle = <0x00000001>; }; }; }; }; __symbols__ { sc16is750_pin_irq = "/fragment@0/__overlay__/sc16is750_pin_irq"; sc16is750 = "/fragment@1/__overlay__/sc16is750@4d"; sc16is750_clk = "/fragment@1/__overlay__/sc16is750@4d/sc16is750_clk"; }; __fixups__ { pio = "/fragment@0:target:0", "/fragment@1/__overlay__/sc16is750@4d:interrupt-parent:0"; i2c1 = "/fragment@1:target:0"; }; __local_fixups__ { fragment@1 { __overlay__ { sc16is750@4d { clocks = <0x00000000>; pinctrl-0 = <0x00000000>; }; }; }; }; }; After reboot, I check the tty devices: pi@nanopineo2:~$ dmesg | grep tty [ 2.056137] printk: console [ttyS0] disabled [ 2.076722] 1c28000.serial: ttyS0 at MMIO 0x1c28000 (irq = 26, base_baud = 1500000) is a U6_16550A [ 2.076773] printk: console [ttyS0] enabled [ 2.098045] 1c28400.serial: ttyS1 at MMIO 0x1c28400 (irq = 27, base_baud = 1500000) is a U6_16550A [ 2.119044] 1c28800.serial: ttyS2 at MMIO 0x1c28800 (irq = 28, base_baud = 1500000) is a U6_16550A [ 2.142198] 1c28c00.serial: ttyS3 at MMIO 0x1c28c00 (irq = 29, base_baud = 1500000) is a U6_16550A [ 5.873610] serial serial0: tty port ttySC0 registered Also, I have check the i2c: pi@nanopineo2:~$ sudo i2cdetect -y 1 [sudo] password for pi: 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- 3c -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- UU -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- 68 -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- my sc16is750 address:0x4d Finally, I check the tty devices: pi@nanopineo2:~$ ls -l /dev/ttyS* crw------- 1 pi tty 4, 64 Mar 23 03:21 /dev/ttyS0 crw-rw---- 1 root dialout 4, 65 Mar 23 03:16 /dev/ttyS1 crw-rw---- 1 root dialout 4, 66 Mar 23 03:16 /dev/ttyS2 crw-rw---- 1 root dialout 4, 67 Mar 23 03:16 /dev/ttyS3 pi@nanopineo2:~$ cat /proc/tty/drivers /dev/tty /dev/tty 5 0 system:/dev/tty /dev/console /dev/console 5 1 system:console /dev/ptmx /dev/ptmx 5 2 system /dev/vc/0 /dev/vc/0 4 0 system:vtmaster unknown /dev/ttySC 242 0-7 serial g_serial /dev/ttyGS 245 0-3 serial serial /dev/ttyS 4 64-67 serial pty_slave /dev/pts 136 0-1048575 pty:slave pty_master /dev/ptm 128 0-1048575 pty:master unknown /dev/tty 4 1-63 console So, My question is why I cannot find the /dev/ttySC0? Anyone can give me some advice to resolve the problem. Thanks.
  7. Dears, We have 4 boards Nanopi Neo2, but when we connect to energy, they don't boot, leds of net port (green and yellow ones) and internal led (red) are on all time. We tried to access via serial port (using an usb-serial adapter), but they not show any boot process. We tried some different boot images on sd card. Nothing works. All four devices are in this situation (and they are new!). There is any thing we can do?
  8. Hi, I am new here and searched the forums for an answer to my questions regarding the NanoPi NEO2 and NEO Plus2. Most answers I could find, but a few were left open. The NEO Plus2 is marked as WIP. Why? What do I have to expect not to work? Both boards are similarly old, from what I could find. Will the Plus2 move up to "supported" eventually or does it currently more look like the route is going towards CSC? Do common features like GPIO access, SPI, I2C ... work with current images? Do specific features where the Plus2 differs from the NEO2 like WiFi, Bluetooth, ... work? I already found out, that the second USB port should work fine. If someone could answer one ore all of those questions that would be much appreciated. Also if you have any other input towards rather buying one or the other SBC, that would be great. Thank you! Frank
  9. Hi, I'm running a NEO2 with Ubuntu at a remote location, so watchdog would be very important to have. Didn't use it before, but afaik H5 SoC supports hardware watchdog. How should I turn it on and do I need to install and configure anything? I read about H3, but not sure about H5. Thanks!
  10. Hello I having some issues with the Armbian Buster image for Nano Pi Neo 2. https://www.armbian.com/nanopi-neo-2/ When I launch the command sudo apt update, I'm getting the following error: The package cache file is corrupted, it has the wrong hash I already downloaded the image several times, I still getting the same error. My SD card is ok, I have tried with 2 different ones. I can remember having the same issue with a preview version. What's wrong??? Thank you
  11. I'm wondering if anyone has had any luck using spi-gpio to bitbang SPI on the H5... @martinayotte, I found a forum thread from a few years ago where you seemed to be looking at this area - perhaps you have an idea? Doing a typical spi-gpio DT overlay for this properly loads the spi-gpio and spi-bitbang drivers, creates /dev/spidev0.0, and allocates the gpios (verified via gpiod)...but the first problem I see is that the CS line is simply not working (cs-gpios below)...? /dts-v1/; /plugin/; / { fragment@0 { target-path = "/"; __overlay__ { spi { compatible = "spi-gpio"; #address-cells = <1>; #size-cells = <0>; ranges; mosi-gpios = <&pio 0 64 0>; /* PC0 */ miso-gpios = <&pio 0 65 0>; /* PC1 */ sck-gpios = <&pio 0 66 0>; /* PC2 */ cs-gpios = <&pio 0 67 1>; /* PC3 */ num-chipselects = <1>; status = "ok"; spidev { compatible = "spidev"; reg = <0>; spi-max-frequency = <500000>; }; }; }; }; }; I'm testing this on a NEO2 using dev kernel 5.3.8, and in this case I am re-using the same standard SPI lines for the HW SPI - this way I can switch between the two easily for testing. Standard HW SPI works great, of course, but the spi-gpio version doesn't. (I tested on other GPIO lines as well and the result is the same.) I hooked the CS, CLK, MOSI, and MISO lines to my scope, and did a test write spi_test through /dev/spidev0.0, and it appears that CLK is properly working, as is the test data transferred via MOSI (at least I'm seeing data bits coming across). But CS simply seems to not be working - I can't trigger properly on it (either high or low). Right off, measuring it shows it as low, when by default it should be high... I am not an expert by any means in this area, so any help/pointers/advice/thoughts would be greatly appreciated! Thanks!
  12. I flashed the latest Armbian image on my NanoPi Neo 2 Plus's emmc. According to https://linux-sunxi.org/Linux_mainlining_effort I2S is not part of the mailinke kernel for H5. I can use I2S with Friendlyelec's images. However, I prefer Armbian. Is it somehow possible to use I2S with an Armbian image on this board?
  13. Hello, There seems to be scant details about the NanoPi Neo 2 LTS, so I thought I'd contribute some. My testing is much less formal than how some would measure it. What I especially like to do in the way of network speed testing are the "worst-case scenarios". My way of invoking a sort of "torture test" is to mostly test upload speeds (as they tend to be slower than download speeds), both large files (much easier), as well as uploading many tiny files (much more gruelling to store, so is therefore a major "torture test"). Having said that, I'll usually favor all-GbE networking (noting which I'm using, GbE or wifi), because I know GbE will be quite a bit faster than WiFi. FWIW, here are my findings. - I got the "1-bay NAS Dock v1.2 for NanoPi NEO/NEO2", allowing me to hook up a 2.5" SSD, I got a Samsung 860 EVO (500GB). For the OS, I used the current Armbian Stretch. Once booted up, and logged in over ssh, I created a btrfs partition on the Samsung EVO, then mounted it, then installed "pure-ftpd". When I did an upload test to the Samsung SSD entirely through Gigabit ethernet (using a Gigabit ethernet dongle on my laptop, which I know can do 40MB/sec easily), here's what I found: - When you upload larger files, like say a 2 GB .zip file, the average FTP upload speed was 29.9 MB/sec - When you upload a whole bunch of smaller files, like 2 GB worth (2029 files), the average FTP upload speed was 18.7 MB/sec Note: I'm using a lacklustre GbE dongle on my laptop, a TP-Link UE300 (which is better than jack squat, because it's supported in Linux whatsoever), and the fastest I've ever been able to get it to go is 105MB/sec, sustained (when connected do a different server, not this NanoPi). This dongle is definately fast enough for my tests.
  14. I use a NEO2 (H5), with armbian linux 4.19.13-sunxi64, and have a StarTech usb2.0 to Gigabit-ethernet adapter, which I plug in the usb slot of the NEO2 and which gives me a new additional ethernet interface. iperf3 on this interface (against another NEO2 with its generic gigabit interface) gives maximum 111 MBit/sec, even with the tips in https://forum.armbian.com/topic/7001-slow-usb-speed-on-h5-devices-orangepi-prime-probably-cpu-governor-related/ (which actually dont change much) Using a raspberry pi (2B) with the same adapter and cable I get 170 MBit/sec, which is significantly more (although still not what one should hope for, which is up to 300, but maybe the StarTech is not perfect) So the usb adapter is not the problem, and I observe similar speeds (around 100 MBit/sec) with other devices too. Why is the usb in the H5 so slow? I need at least 150MBit/sec (ok not really for this adapter, actually for another one, but never mind)
  15. I have read other thread regarding v4l2loopback kernel module installation. I got same problem like this message below ========================================= ------------------------------ Deleting module version: 0.10.0 completely from the DKMS tree. ------------------------------ Done. Unpacking v4l2loopback-dkms (0.10.0-1) over (0.10.0-1) ... Setting up v4l2loopback-dkms (0.10.0-1) ... Loading new v4l2loopback-0.10.0 DKMS files... dpkg: warning: version '3.4.113-sun8i 4.19.25' has bad syntax: invalid character in revision number Building for 4.19.20-sunxi64 Module build for kernel 4.19.20-sunxi64 was skipped since the kernel headers for this kernel does not seem to be installed. =================================== I am usng Nano PI neo2 with armbian 4.19.20. When I install the kernel-headers using armbian-config, the version of kernel-headers installed is 4.19.25. Either the kernel source I have installed using armbian-config is 4.19.25. I just guess the version mistach doesn't make me succeed build of v4l2loopback. But I can't figure out what to do with this error. Please give me some comment.
  16. Hi! I've recently bought a nanopi NEO2 which features an Allwinner H5. On FriendlyArm website (and on Allwinner's too) it is stated that the H5 is clocked 1.5Ghz. I need to perform some heavy job and and noticed that the cpu frequency hits, at full power, only 1Ghz. I checked using cpufreq-info and I got: driver: cpufreq-dt CPUs which run at the same hardware frequency: 0 1 2 3 CPUs which need to have their frequency coordinated by software: 0 1 2 3 maximum transition latency: 244 us. hardware limits: 120 MHz - 1.01 GHz available frequency steps: 120 MHz, 240 MHz, 312 MHz, 480 MHz, 624 MHz, 816 MHz, 1.01 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 120 MHz and 1.01 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 1.01 GHz (asserted by call to hardware). cpufreq stats: 120 MHz:58.40%, 240 MHz:0.75%, 312 MHz:0.82%, 480 MHz:0.47%, 624 MHz:0.65%, 816 MHz:0.64%, 1.01 GHz:38.28% (66) which clearly says that the cpu is limited to 1.01 Ghz by hardware. I am sure the allwinner H5 could reach 1.5, so the options are two: or friendly elec has limited by hardware their nanopi (in that case it would absolutely not fair to state on the website 1.5ghz) or it is limited by the kernel. Hoping the case is the second one (I bought two of them!), can you help me? Is there a way to compile the kernel allowing the true maximum frequency? Thank you very much
  17. These boards are well suited to routing/network traffic control functionality. Currently the kernel has been compiled with Traffic Control stuff disabled, which makes it impossible to perform traffic shaping on stock Armbian kernel. I'm busy recompiling the kernel as a temporary solution, but I will really appreciate it if the kernel build maintainer can please change the traffic control options from DISABLED to MODULE (at least)? I have a bunch of Armbian boards but I'm testing with NanoPi Neo 2 right now. --- I'll let you know the size of the modules once I've finished compiling.
  18. Good day! I've had the Nanopi Neo2 v1.0 for sometime now, used for mostly for NAS solution. the v1.0 is the one being carried by my supplier here. No v1.1 yet Lately I installed armbian monitor to monitor system resources. Then I stumbled upon the min and max frequency when I checked using # cpufreq-info -p 408000 816000 ondemand I've read on some internet writeups that one can set the max frequency to 1008000 tried editing the cpufrequtils scaling_max_freq scaling_available_frequencies scaling_setspeed I was able to lower the minimum frequency to 120000 using the following entry at cpufrequtils # WARNING: this file will be replaced on board support package (linux-root-...) upgrade ENABLE=true #MIN_SPEED=408000 #MAX_SPEED=816000 MIN_SPEED=0 MAX_SPEED=1008000 GOVERNOR=ondemand but the output of cpufreq-info -p remains as # cpufreq-info -p 120000 816000 ondemand I'd really like to be able to set the max frequency higher than it is now. Any info, pointers, procedures (much better) will be much appreciated Thanks in advance!
  19. I'm not sure I even want BakeBit. I'm trying to use the GPIO in my NanoPi Neo2. Specifically I want to read a digital I/O pin on/off state. And if possible I'd like to read an analog voltage from the H5's built in ADC. Now that I've looked deeper into BakeBit, it seems like the entire purpose of BakeBit is to do GPIO with an Arduino, and read the information remotely on a RbPi/NanoPi or whatever ON the Arduino's GPIO pins. If that is really what BakeBit is, then BakeBit doesn't interest me. The H5 already has GPIO and an ADC. We just need to get that working. For interest's sake, here is the progress I made with BakeBit. ADC Python example in Bakebit http://wiki.friendlyarm.com/wiki/index.php/BakeBit_-_Light_Sensor i had to `apt-get install libjpeg-dev zlib1g-dev` to get pillow to install properly, which is a dependency of BakeBit. Bakebit installed without errors, but it tries to compile WiringNP which complained with a lot of warnings. In the following thread I got WiringNP to run. This was semi useful BTW https://www.cnx-software.com/2017/05/21/using-gpios-on-nanopi-neo-2-board-with-bakebit-starter-kit/ Now when I `rm -rf the bakebit dir` then do a fresh clone and `/scripts/BakeBit/Script/install.sh` it installs without errors except warnings for WiringNP. (which I don't actually get when I build it myself) With the hax I did to get WiringNP to work on my Neo2. I deleted Bakebit/Scripts/WiringNP and replaced it with the version that I modified and built successfully.
  20. Hi, I am trying to install the aircrack-ng driver via dkms from over here: https://github.com/aircrack-ng/rtl8812au When I change the Makefile to match my processor arm-sun50iw1p1 , I receive these compilation errors and do not know how to fix them. cat /var/lib/dkms/rtl8812au/5.2.20.2/build/make.log DKMS make.log for rtl8812au-5.2.20.2 for kernel 4.19.20-sunxi64 (aarch64) Tue Feb 12 21:53:55 UTC 2019 make ARCH=arm64 CROSS_COMPILE=/home/android_sdk/Allwinner/a64/android-51/lichee/out/sun50iw1p1/android/common/buildroot/external-toolchain/bin/aarch64-linux-gnu- -C /lib/modules/4.19.20-sunxi64/build M=/var/lib/dkms/rtl8812au/5.2.20.2/build modules make[1]: Entering directory '/usr/src/linux-headers-4.19.20-sunxi64' arch/arm64/Makefile:27: ld does not support --fix-cortex-a53-843419; kernel may be susceptible to erratum arch/arm64/Makefile:48: Detected assembler with broken .inst; disassembly will be unreliable ./scripts/gcc-version.sh: line 26: /home/android_sdk/Allwinner/a64/android-51/lichee/out/sun50iw1p1/android/common/buildroot/external-toolchain/bin/aarch64-linux-gnu-gcc: No such file or directory ./scripts/gcc-version.sh: line 27: /home/android_sdk/Allwinner/a64/android-51/lichee/out/sun50iw1p1/android/common/buildroot/external-toolchain/bin/aarch64-linux-gnu-gcc: No such file or directory make[1]: /home/android_sdk/Allwinner/a64/android-51/lichee/out/sun50iw1p1/android/common/buildroot/external-toolchain/bin/aarch64-linux-gnu-gcc: Command not found make[1]: /home/android_sdk/Allwinner/a64/android-51/lichee/out/sun50iw1p1/android/common/buildroot/external-toolchain/bin/aarch64-linux-gnu-gcc: Command not found make[1]: /home/android_sdk/Allwinner/a64/android-51/lichee/out/sun50iw1p1/android/common/buildroot/external-toolchain/bin/aarch64-linux-gnu-gcc: Command not found make[1]: /home/android_sdk/Allwinner/a64/android-51/lichee/out/sun50iw1p1/android/common/buildroot/external-toolchain/bin/aarch64-linux-gnu-gcc: Command not found /bin/sh: 1: /home/android_sdk/Allwinner/a64/android-51/lichee/out/sun50iw1p1/android/common/buildroot/external-toolchain/bin/aarch64-linux-gnu-gcc: not found (standard_in) 1: syntax error CC [M] /var/lib/dkms/rtl8812au/5.2.20.2/build/core/rtw_cmd.o /bin/sh: 1: /home/android_sdk/Allwinner/a64/android-51/lichee/out/sun50iw1p1/android/common/buildroot/external-toolchain/bin/aarch64-linux-gnu-gcc: not found scripts/Makefile.build:303: recipe for target '/var/lib/dkms/rtl8812au/5.2.20.2/build/core/rtw_cmd.o' failed make[2]: *** [/var/lib/dkms/rtl8812au/5.2.20.2/build/core/rtw_cmd.o] Error 127 make[2]: *** Waiting for unfinished jobs.... CC [M] /var/lib/dkms/rtl8812au/5.2.20.2/build/core/rtw_security.o /bin/sh: 1: /home/android_sdk/Allwinner/a64/android-51/lichee/out/sun50iw1p1/android/common/buildroot/external-toolchain/bin/aarch64-linux-gnu-gcc: not found scripts/Makefile.build:303: recipe for target '/var/lib/dkms/rtl8812au/5.2.20.2/build/core/rtw_security.o' failed make[2]: *** [/var/lib/dkms/rtl8812au/5.2.20.2/build/core/rtw_security.o] Error 127 Makefile:1520: recipe for target '_module_/var/lib/dkms/rtl8812au/5.2.20.2/build' failed make[1]: *** [_module_/var/lib/dkms/rtl8812au/5.2.20.2/build] Error 2 make[1]: Leaving directory '/usr/src/linux-headers-4.19.20-sunxi64' Makefile:1551: recipe for target 'modules' failed make: *** [modules] Error 2 Any ideas? kind regards, rhagu
  21. I'm trying to figure out what happened in my device this morning. the process that i'm monitoring was interrupted and restarted and i'm want to know that reason, is it internal code reasone or system failure that caused to my process to crash. i'm attaching the /var/log/message piece of logs when my process crashed. can you tell me what happened? I'm using NanoPi2 NEO with latest armbian version for this specific board, Thanks alot
  22. HI, I have the following NanoPi Neo 2 boards, hardware v 1.1, model 1711 with 1Gb RAM Linux 4.19.13-sunxi64 #5.70 SMP Sat Jan 12 17:41:57 CET 2019 aarch64 GNU/Linux I have noticed that various network related tasks fail at boot apparently at eth0 is not yet ready This includes network mounts via /etc/fstab and disabling IPv6 via /etc/sysctl.conf My current solution (which I feel is a complete bodge) is to have extra commands in /etc/rc.local that after a 5 second sleep issue a 'mount -a' and 'sysclt -p' I have tried solutions for 'wait for network' on boot but neither work. systemctl enable NetworkManager-wait-online.service systemctl enable systemd-networkd-wait-online.service Looking at the armbianmonitor output I see this. 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet XXX.XXX.0.1/8 scope host lo valid_lft forever preferred_lft forever 2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether 02:01:43:0c:2e:f7 brd ff:ff:ff:ff:ff:ff I have not edited the network config and /etc/network/interfaces is the standard # Network is managed by Network manager auto lo iface lo inet loopback IP address allocation is via DHCP, however these have pihole installed which I believe change this to static, albeit to match whatever they were getting via DHCP. Is anyone else seeing this, have any thoughts or have a 'better' solution ? edit: just spotted this at the bottom of the log [ 9.905128] RTL8211E Gigabit Ethernet 0.2:07: attached PHY driver [RTL8211E Gigabit Ethernet] (mii_bus:phy_addr=0.2:07, irq=POLL) [ 9.907509] dwmac-sun8i 1c30000.ethernet eth0: No Safety Features support found [ 9.907527] dwmac-sun8i 1c30000.ethernet eth0: No MAC Management Counters available [ 9.907535] dwmac-sun8i 1c30000.ethernet eth0: PTP not supported by HW [ 9.907998] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 15.011046] dwmac-sun8i 1c30000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx [ 15.011101] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 15.107488] FS-Cache: Loaded [ 15.176939] FS-Cache: Netfs 'cifs' registered for caching [ 15.177411] Key type cifs.spnego registered [ 15.177427] Key type cifs.idmap registered [ 15.178533] No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3 (or SMB2.1) specify vers=1.0 on mount. [ 15.611651] cfg80211: Loading compiled-in X.509 certificates for regulatory database [ 15.648915] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' [ 15.655164] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 [ 15.655183] cfg80211: failed to load regulatory.db [ 20.150078] No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3 (or SMB2.1) specify vers=1.0 on mount. It would be interesting to know what is happening between 9.907 and 15.01 where the network finally comes up. I would guess that the CIFS mount at 15.17 is the OS reading fstab, which appears to fail, then the second mount at 20.15 is rc.local running mount -a but I'm not 100% sure. I can't tell / don't know enough to see where in the boot sequence /etc/sysctl or /etc/fstab are invoked.
  23. Board NEO2 with Armbian Stretch mainline kernel 4.19.y many errors: info:xxxxx[3087]::2019-01-30T10:19:10.607956+00:00: /usr/sbin/xxxxx: error while loading shared libraries: libsystemd.so.0: cannot open shared object file: No such file or directory info:xxxxx[3093]::2019-01-30T10:19:20.857869+00:00: /usr/sbin/xxxxx: error while loading shared libraries: libsystemd.so.0: cannot open shared object file: No such file or directory info:xxxxx[3097]::2019-01-30T10:19:31.114980+00:00: /usr/sbin/xxxxx: error while loading shared libraries: libsystemd.so.0: cannot open shared object file: No such file or directory info:xxxxx[3106]::2019-01-30T10:19:41.357962+00:00: /usr/sbin/xxxxx: error while loading shared libraries: libsystemd.so.0: cannot open shared object file: No such file or directory info:xxxxx[3108]::2019-01-30T10:19:51.607633+00:00: /usr/sbin/xxxxx: error while loading shared libraries: libsystemd.so.0: cannot open shared object file: No such file or directory please help
  24. Hi, I have just received some shiny new NanoPi Neo 2 boards, hardware v 1.1, model 1711 with 1Gb RAM. I have installed Armbian Stretch mainline kernel 4.19.y with no issues at all however I have noticed that the green LED is pretty well ignoring anything I ask of it. ls -la /sys/class/leds/ total 0 drwxr-xr-x 2 root root 0 Jan 25 16:14 . drwxr-xr-x 52 root root 0 Jan 1 1970 .. lrwxrwxrwx 1 root root 0 Jan 1 1970 nanopi:green:status -> ../../devices/platform/leds/leds/nanopi:green:status lrwxrwxrwx 1 root root 0 Jan 1 1970 nanopi:red:pwr -> ../../devices/platform/leds/leds/nanopi:red:pwr cat /sys/class/leds/nanopi:green:status/trigger none kbd-scrolllock kbd-numlock kbd-capslock kbd-kanalock kbd-shiftlock kbd-altgrlock kbd-ctrllock kbd-altlock kbd-shiftllock kbd-shiftrlock kbd-ctrlllock kbd-ctrlrlock usbport usb-gadget usb-host disk-activity disk-read disk-write ide-disk mtd nand-disk [heartbeat] cpu cpu0 cpu1 cpu2 cpu3 default-on panic mmc0 0.2:07:link 0.2:07:1Gbps 0.2:07:100Mbps 0.2:07:10Mbps rfkill-any rfkill-none Of the above only 'none' heartbeat' and 'default-on' seem to work, all others are just off / no activity. I didn't try the kbd / usb related ones etc. as I don't have one attached. There was a comment in Nanopi NEO 2 dated May 2017 that this was seen and may get looked at so was just wondering if this is still as expected ? From the date and the colours mentioned I am also assuming that the original thread and comments covered the v1.0 hardware. All that aside, gotta say - Love your work.
  25. I just got a Nanopi NEO2 512MB, installed Armbian Ubuntu Bionic. It works fine, except for the DVB-T/C stick. It is affected by Kernel 4.10+ problems. I wonder if I can downgrade to an older kernel, like 4.4.0 for example, where everything works perfectly? If yes, how? There is a patch that perhaps would resolve the problem, how could I apply this patch to an of the available releases of Armbian? This patch Please, help me with this. Many thanks!
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines