Search the Community

I was able to get RTL8188FTV $2.00 US USB wifi https://www.ebay.com/itm/123713550193 working with a script I made from a forked project. The power saver has already been disabled in the Makefile. Check out https://github.com/sgjava/rtl8188fu/tree/arm. I've tested this on ARM 32 and ARM 64, but not x86 or x86_64. This is currently a dkms module that requires beta repos to get matching kernel headers.

Hallo liebe Community, ich versuche, da es kein aktuelles jammy release für meinen M1 gibt, eines mit Ubuntu zu erstellen. So wie es in der Dokumentation beschrieben ist. Allerdings kommt immer wieder ein abbruch: ERROR in function install_deb_chroot Und dann wird der Prozess terminiert. Warum funktioniert das denn nicht?

After connecting the wireless adapter we run the following command: lsusb the output is Bus 004 Device 003: ID 148f:7601 Ralink Technology, Corp. Trying to install armbian driver (Linux nanopim1 3.4.113-sun8i #18 SMP PREEMPT armv7l GNU/Linux) for lb-link model: wn155a "MTK7601 chipset" wireless adapter (150Mbps) using the following commands: sudo apt-get install linux-headers-generic build-essential git sudo apt-get install git git clone https://github.com/flexiti/mt7601.git cd mt7601 make clean make sudo make install sudo mkdir -p /etc/Wireless/RT2870STA/ sudo cp RT2870STA.dat /etc/Wireless/RT2870STA/ sudo modprobe mt7601Usta the output of the last command is modprobe: ERROR: could not insert 'mt7601Usta': Exec format error what should we do? is MT7601U the same as MTK7601? or do we need another driver?

Good morning all. I was trying to power up my nanopi M1 through the VDD_5V and GND pins shown in GPIO.jpg image and/or the power pins on the debug GPIO pins, the schematics of the board power electronics are attached too on page 7 and 8, may by I'm wrong but what I see on those schematics is that all the power switchs and DC/DC converters can be powered through those pins but when I do that using a USB cable cutted on the micro USB side and prepared with the right terminals to fit the pins -with a 5V USB charger- then the tension drops aproximatelly to 4.60-4.67 DCV, the board starts by lighting dimly the power LED (as normally) but when the power LED lights strongly also lights both ethernet LEDs and the board apparently freezes in that state like the processor didn't start at all. What I've found is that the SY6280 and the SY8089 depend on the tension having a minimum value of 4.5 DCV so I can't find why the tesnsion drops to level described before unless the cables used are of bad quality even having cutted the micro USB part which if I'm right should have the termination. NOTE: When the board is powerd from the micro USB with a good cable then I have aproximatelly 5,13 DCV on VDD_5V wich is normal, the cutted cables when they where complete didn't work to power the board through micro USB Anyone has tried this before?, did it worked?. NanoPi-M1-1603B-Schematic.pdf

Hi, my current project is about using a NanoPI M1 as a controller for a 3D printer. As such, one wants to have very tight timing on the GPIO output, with as little jitter as possible, to get smooth motion of the stepper motors. However, it is common belief that getting a fast timing with little jitter is virtually impossible to do under linux, without the help of a dedicated chip just for the IO. While that is true in general on stock kernels, it's possible to vastly improve on that front by spending a little effort. One way on ARM chips is to use the FIQ. That is an interrupt that has the highest priority, which can interrupt all other, regular interrupts. However, modern chips use a GIC for interrupt control instead of a VIC, so adding a FIQ is not that easy. There are patches out there to do just that, but then, those are for newer kernels, and not the old 3.4.xxx, which is somewhat of the standard kernel for the time beeing. So, what to do? Well, diving into the kernel sources and do some nasty hacking, of course! To give a quick overview of how an interrupt is usually handled on our ARM platform: 1: IRQ happens, the IRQ controller notifies the CPU about that 2: A small assembly stub is invoked, which then jumps into a small routine, asm_do_IRQ() 3: That small routine calls another routine, handle_IRQ() 4: That in turn calls generic_handle_irq() 5: Which then calls handle_fasteoi_irq(), by using a pointer to that in the IRQ descriptor 6: Subsequently, handle_irq_event() is called 7: And since we are on a SMP machine, that in turn calls handle_irq_event_percpu() 8: And finally, that calls action->handler(), the _actual_ interrupt routine! Now, not only is that a long way to go, but in many of those functions a lot of other functions are called, many of which are by themselves interruptible/preemptible. No surprise then that there is little chance to get a tight timing... Now, this is where my nasty hack come in. Step 2 of the above list is preserved as it is, but in step 3, that is, in handle_IRQ(), i added some code. That code checks if the requested IRQ is one to quickly handle, and if it is, basically calls the real IRQ handler directly. This leads to _great_ improvements, as you can see in the following images. All scope images are with 10 second persistency turned on, so that glitches become visible. First, this is how it would normally look, without any patches at all. It is supposed to be a ~40kHz square wave: Basically just a blur. OK, most of that is because the interrupt runs on core 0, which is used by other stuff as well. I made a patch to have an IRQ attached to a specific core or cores (see this thread: http://forum.armbian.com/index.php/topic/1885-rt-patches-for-sun8i-kernel/). Once the kernel has that patch applied, and the boot-arg isolcpus=3 is given, only the first 3 cores are used by the kernel, leaving the fourth one free. Attaching the used timer-IRQ to that core gives this result: Much better, but still a lot of jitter. Now, this is where the quickirq patch comes in. Applying that patch results in this: Now, that is already a _lot_ better. Is there still room for improvement? Yes, by applying the RT patch. Which gives the final result: In all the scope shots the board was running at 624MHz RAM, 1200MHz core, while in the background "stress -c 4 -i 4" was active, resulting in a cpu load of roundabout 9 according to top. Now, let's be clear: Using the quickirq patch is not for the faint of heart. One has to know exactly what she/he is doing, otherwise the kernel will very likely lock up. There are noc checks, no nothing, it assumes that the handler itself is set up and registered correctly. And that no other interrupt handler wants to attach itself (or is already attached) to that interrupt number. Also, it is no hard realtime. While the outcome is vastly improved, there still is the occasional jitter. However, it is quite good enough to control stepper motors within reasonable limits. Since my aim is tu use the nanoPI M1 to directly control stepper motors, it should be noted that a frequency of 40kHz would, if we assume 100 steps/mm, result in a speed of 400mm/s, or 40cm/s! More reasonable speeds of 200 or 300mm/s mean that any jitter that happens is less pronounced, relative to the pulse width itself. The patch also include a sample driver which will output a square wave on PA0. In the kernel menuconfig, under Device Drivers -> quickirq you can enable/disable the quickirq handling, define up to 3 interrupt numbers to handle through that patch, as well as enable the sample driver. The sample driver uses TMR1 of the H3, which is otherwise completely unused. TMR1 has interrupt number 51. The driver uses PA0, but it accesses the port registers directly. So if you have any other stuff that toggles GPIO pins on PORTA, that will interfere with the output of the sample driver. So, if you want to test it and look at the output on a scope, it's best to disable anything else on PORTA (like the heartbeat LED, for example). If the sample driver is loaded (either directly compiled into the kernel, or as a module and the "modprobe -i quickirq"), it creates a device node at /dev/quickirq. You can echo characters into that to control it: echo 0 > /dev/quickirq -> disable the timer echo 1 > /dev/quickirq -> enable the timer (squarewave appears on PA0) Sending it the numbers 2, 3, 4, 5, 6 and 7 changes the output frequency to (about) 10Hz, 100Hz, 1kHz, 10kHz, 20kHz and 40kHz repsectively. Sending it + or - will adjust the raw timer reload value in 1-increments, q and w in 10-increments, e and r in 100 increments. The shorter the intervall time gets (the higher the frequency), you will notice that there is a base overhead that can't be avoided. Like, the timer reload value for the 40kHz setting is half of that for the 20kHz setting, but the output is slightly less than double. It's just a crude example, after all. All that said, here is the patch: 0000-add-quickirq.patch.gz Have fun with it, hopefully it is useful for others as well. But keep in mind that this is a rather rude brute-force method. You _really_ have to know what you are doing! Greetings, Chris EDIT: Re-uploaded the patch

Greetings. For anyone interested FriendlyArm have a Github repo which contains a working AW CSI driver. and has device tree files for NanoPi M1+ and Neo Air. See https://github.com/friendlyarm/linux.git. The branch is sunxi-4.16.y This is a work in progress but the setup is vastly simplified compared to the VFE subsystem in the 3.4/3.10 kernels. The OV5640 driver does produce video but I'm getting some odd images at the moment. Possibly colorspace related. As a bonus USB OTG is also working ... fa@FriendlyELEC:~/src$ v4l2-compliance Driver Info: Driver name : sun6i-video Card type : sun6i-csi Bus i[59399.088082] sun6i-csi 1cb0000.camera: ================= START STATUS ================= nfo : platform:camera Driver version: 4.16.0 Capabiliti[59399.102740] sun6i-csi 1cb0000.camera: ================== END STATUS ================== es : 0x84200001 Video Capture Streaming Extended Pix Format Device Capabilities Device Caps : 0x04200001 Video Capture Streaming Extended Pix Format Compliance test for device /dev/video0 (not using libv4l2): Required ioctls: test VIDIOC_QUERYCAP: OK Allow for multiple opens: test second video open: OK test VIDIOC_QUERYCAP: OK test VIDIOC_G/S_PRIORITY: OK Debug ioctls: test VIDIOC_DBG_G/S_REGISTER: OK (Not Supported) test VIDIOC_LOG_STATUS: OK Input ioctls: test VIDIOC_G/S_TUNER/ENUM_FREQ_BANDS: OK (Not Supported) test VIDIOC_G/S_FREQUENCY: OK (Not Supported) test VIDIOC_S_HW_FREQ_SEEK: OK (Not Supported) test VIDIOC_ENUMAUDIO: OK (Not Supported) test VIDIOC_G/S/ENUMINPUT: OK test VIDIOC_G/S_AUDIO: OK (Not Supported) Inputs: 1 Audio Inputs: 0 Tuners: 0 Output ioctls: test VIDIOC_G/S_MODULATOR: OK (Not Supported) test VIDIOC_G/S_FREQUENCY: OK (Not Supported) test VIDIOC_ENUMAUDOUT: OK (Not Supported) test VIDIOC_G/S/ENUMOUTPUT: OK (Not Supported) test VIDIOC_G/S_AUDOUT: OK (Not Supported) Outputs: 0 Audio Outputs: 0 Modulators: 0 Input/Output configuration ioctls: test VIDIOC_ENUM/G/S/QUERY_STD: OK (Not Supported) test VIDIOC_ENUM/G/S/QUERY_DV_TIMINGS: OK (Not Supported) test VIDIOC_DV_TIMINGS_CAP: OK (Not Supported) test VIDIOC_G/S_EDID: OK (Not Supported) Test input 0: Control ioctls: test VIDIOC_QUERYCTRL/MENU: OK test VIDIOC_G/S_CTRL: OK test VIDIOC_G/S/TRY_EXT_CTRLS: OK test VIDIOC_(UN)SUBSCRIBE_EVENT/DQEVENT: OK test VIDIOC_G/S_JPEGCOMP: OK (Not Supported) Standard Controls: 14 Private Controls: 0 Format ioctls: fail: v4l2-test-formats.cpp(259): duplicate format 32314d48 test VIDIOC_ENUM_FMT/FRAMESIZES/FRAMEINTERVALS: FAIL test VIDIOC_G/S_PARM: OK (Not Supported) test VIDIOC_G_FBUF: OK (Not Supported) fail: v4l2-test-formats.cpp(314): !colorspace fail: v4l2-test-formats.cpp(417): testColorspace(pix.pixelformat, pix.colorspace) test VIDIOC_G_FMT: FAIL test VIDIOC_TRY_FMT: OK (Not Supported) test VIDIOC_S_FMT: OK (Not Supported) test VIDIOC_G_SLICED_VBI_CAP: OK (Not Supported) Codec ioctls: test VIDIOC_(TRY_)ENCODER_CMD: OK (Not Supported) test VIDIOC_G_ENC_INDEX: OK (Not Supported) test VIDIOC_(TRY_)DECODER_CMD: OK (Not Supported) Buffer ioctls: test VIDIOC_REQBUFS/CREATE_BUFS/QUERYBUF: OK fail: v4l2-test-buffers.cpp(500): q.has_expbuf(node) test VIDIOC_EXPBUF: FAIL Total: 38, Succeeded: 35, Failed: 3, Warnings: 0

I've followed the instructions below and cannot get past the "couldn't find avaliable UDC" error. help? https://vjordan.info/log/fpga/nanopi-neo-usb-otg-with-armbian-mainline-4x-kernel.html

Hi Guys, I bought one of these pcDuino 4 (Nano Pi M1) boards: http://www.linksprite.com/pcduino4-nano/ Works great with Armbian Legacy Kernal. I got this screen with the HDMI + DSI Driver Board. Works fine with normal PC -> HDMI output but will not work with the Nano Pi.. https://www.alibaba.com/product-detail/LS055R1SX04-1440x2560-5-5-2K-LCD_60672828148.html?spm=a2700.7724838.2017115.1.3c93b095HGc0XS The LCD screen just turns on then off and on and off forever. It never locks on to the HDMI signal. The Nano Pi M1 works just fine with a regular monitor but not with the LCD/Driver combo. I have seen some purple images come up on the screen and sometimes I can see 4 desktops on the tiny screen just for a split second. I have also tried multiple resolutions using the h3disp command. Not sure how to debug this issue. I have tried using multiple power sources, different HDMI cables, with no luck. Any help would be awesome. I am new to Linux so I am just not sure how to figure out what the issue is. Thanks You Jay

Hi I have an ARM-based board(http://wiki.friendlyarm.com/wiki/index.php/NanoPi_M1) and use Armbian(Ubuntu-server 16.04) on it. I have a 2.2" TFT-LCD with SPI connection, and use this framebuffer driver(https://github.com/notro/fbtft) to launch it. I can setup my LCD with this command: sudo modprobe fbtft_device custom name=fb_ili9341 gpios=reset:1,dc:201,led:6 speed=16000000 rotate=90 bgr=1 And before, when I had Ubuntu desktop, I could change display by this command: FRAMEBUFFER=/dev/fb8 startx But in Ubuntu-server I get this error message: X.Org X Server 1.18.4 Release Date: 2016-07-19 X Protocol Version 11, Revision 0 Build Operating System: Linux 4.4.0-97-generic armv7l Ubuntu Current Operating System: Linux nanopim1 3.4.113-sun8i #16 SMP PREEMPT Tue Jun 13 14:15:57 CEST 2017 armv7l Kernel command line: root=UUID=10b3b795-f372-4ea9-b78a-93ae9355c20c rootwait rootfstype=ext4 console=tty1 console=ttyS0,115200 hdmi.audio=EDID:0 disp.screen0_output_mode=1920x1080p60 panic=10 consoleblank=0 loglevel=1 ubootpart=bd75a2d6-01 ubootsource=mmc sunxi_ve_mem_reserve=0 sunxi_g2d_mem_reserve=0 sunxi_fb_mem_reserve=16 cgroup_enable=memory swapaccount=1 Build Date: 13 October 2017 01:59:44PM xorg-server 2:1.18.4-0ubuntu0.7 (For technical support please see http://www.ubuntu.com/support) Current version of pixman: 0.33.6 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Thu Oct 26 16:44:04 2017 (==) Using config directory: "/etc/X11/xorg.conf.d" (==) Using system config directory "/usr/share/X11/xorg.conf.d" (EE) Fatal server error: (EE) no screens found(EE) (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. (EE) (EE) Server terminated with error (1). Closing log file. And have only a blank screen. I want to know how can I set this LCD as my boards default LCD and make it to run. In addition I must say I have installed xorg, openbox and xserver-xorg-video-fbdev too. Also I did accidentally remove this file's content 01-armbian-defaults.conf And looking for it too.

Good night, I have the sound problem but with hdmi audio, de default is the 3.5 mm audio jack, then I looked for the asound.conf in /etc, then I found that this file doesn't exist and after that I've created it with the following content: pcm.!default { type hw card 1 device 0 } ctl.!default { type hw card 1 } the problem is that even created this way the sound output still being the 3.5 mm jack and I don't know if I need to change some setting to mpv player to output the sound through hdmi. What else can I do to change the sound from audio jack to hdmi?

Hi, I've recently acquired some nanoPi M1, and just about now installed ARMBIAN. However I can't seem to get any sound working via 3.5 analog jack. Volume is set right on alsamixer Speaker are working and volume is set at max Soundcard is listed but yet I have absolutely no sound ... any ideas ? root@user:~# aplay -l **** List of PLAYBACK Hardware Devices **** card 0: audiocodec [audiocodec], device 0: SUNXI-CODEC sndcodec-0 [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: sndhdmi [sndhdmi], device 0: SUNXI-HDMIAUDIO sndhdmi-0 [] Subdevices: 1/1 Subdevice #0: subdevice #0 root@user:~# cat /proc/asound/cards 0 [audiocodec ]: audiocodec - audiocodec audiocodec 1 [sndhdmi ]: sndhdmi - sndhdmi sndhdmi root@user:~# aplay /usr/share/sounds/alsa/Noise.wav Playing WAVE '/usr/share/sounds/alsa/Noise.wav' : Signed 16 bit Little Endian, Rate 48000 Hz, Mono

Hi I have NanoPi-M1 board. It has two type of Ubuntu-Core as you can see here(https://www.mediafire.com/folder/3q2911p1qp33p/NanoPi-M1Board#dc73df73c6dk6) with kernels (3.4.39 amd 4.11.2). But when I try modinfo fbtft It says there is no file or directory like this! But I think it should be exist in kernels with version above 4.10. By the way, I need this kernel support to running my LCD! Are there any Armbian version like Ubunto core with this module support on kernel? Or can I add this support to yhose Ubuntu files in above link? how?

I am trying to get my nanopi m1 to show up as an ethernet device and I can't make it work in mainline or legacy. Since I'm aiming for mainline anyway, could someone help me figure out what I'm doing wrong?

Greetings, I've got 2 M1 boards in front of me. The FA is running their latest distribution: http://www.mediafire.com/file/kc44mm1mdahslho/nanopi-m1_debian-jessie_4.11.2_20170905.img.zip By default the device tree for the FA has the USB controller (usb@01c19000) marked as disabled and is missing the dr_mode = "OTG" attribute. Enable the controller and Add the dr_node property and the board comes up as a mass storage device in both Windows and Linux. The board running Armbian has exactly the same device tree entries, dmesg shows the USB controller is loaded and visible with lsusb -t. When a gadget module is loaded all appears to work on the M1 but it never appears as a valid USB device on the host. Windows eventually complains that the port reset failed. I figured this might be a problem with the OTG ID pin not being set up properly but both boards report the same PIO pin status. Does anyone have working gadget mode on an M1? Or might they suggest how I can diagnose this issue? Just for laughs Armbian 4.11.5 running on an OPI One *does* have working gadget mode. Given identical hardware and USB wiring I figure this makes it unlikely (but not impossible) to be a kernel issue. TAIA P.S. If anyone wants to do a bit of consulting to fix this problem, please PM me. nanopim1:~$ uname -a Linux nanopim1 4.11.5-sun8i #7 SMP Mon Sep 11 17:50:49 BST 2017 armv7l GNU/Linux ~# uname -a Linux FriendlyELEC 4.11.2 #1 SMP Mon Jul 10 11:06:36 CST 2017 armv7l GNU/Linux nanopim1:~$ sudo sunxi-pio -m PG12 PG12<7><0><1> @FriendlyELEC:~# sunxi-pio -m PG12 PG12<7><0><1>

Hello all, just joined the forum since this is my first time using Armbian. So I got a NanoPi M1 and the dvp cam500b. From what I understand this camera uses the omnivision ov5640. I am having trouble getting this thing recognized in armbian. I get /dev/video0 to be listed by adding it to /etc/modules, but if I go to access it with any software it reports back 'no such device' or to the similar effect (this includes mjpg-streamer, fswebcam, ffmpeg). Researching around I find many forum posts of people saying one must modify the 'fex' file... to which I found out this is the decompiled version of the /boot/script.bin file using the sunxi-tools/bin2fex. Thing is, when I go into this 'fex' file, I have no idea what I must do. I find a location in it referring to [csi0], under which the gc2035 camera like so: vip_used = 1 vip_mode = 0 vip_dev_qty = 1 vip_define_sensor_list = 0 vip_csi_pck = port:PE00<2><default><default><default> vip_csi_mck = port:PE01<2><default><default><default> vip_csi_hsync = port:PE02<2><default><default><default> vip_csi_vsync = port:PE03<2><default><default><default> vip_csi_d0 = port:PE04<2><default><default><default> vip_csi_d1 = port:PE05<2><default><default><default> vip_csi_d2 = port:PE06<2><default><default><default> vip_csi_d3 = port:PE07<2><default><default><default> vip_csi_d4 = port:PE08<2><default><default><default> vip_csi_d5 = port:PE09<2><default><default><default> vip_csi_d6 = port:PE10<2><default><default><default> vip_csi_d7 = port:PE11<2><default><default><default> vip_csi_sck = port:PE12<2><default><default><default> vip_csi_sda = port:PE13<2><default><default><default> vip_dev0_mname = "gc2035" vip_dev0_pos = "front" vip_dev0_lane = 1 vip_dev0_twi_id = 2 vip_dev0_twi_addr = 120 vip_dev0_isp_used = 0 vip_dev0_fmt = 0 vip_dev0_stby_mode = 0 vip_dev0_vflip = 1 vip_dev0_hflip = 1 vip_dev0_iovdd = "" vip_dev0_iovdd_vol = 2800000 vip_dev0_avdd = "" vip_dev0_avdd_vol = 2800000 vip_dev0_dvdd = "" vip_dev0_dvdd_vol = 1800000 vip_dev0_afvdd = "" vip_dev0_afvdd_vol = 2800000 vip_dev0_power_en = port:PA17<1><default><default><1> vip_dev0_reset = port:PE14<1><default><default><1> vip_dev0_pwdn = port:PE15<1><default><default><0> vip_dev0_flash_en = vip_dev0_flash_mode = vip_dev0_af_pwdn = vip_dev0_act_used = 0 vip_dev0_act_name = "ad5820_act" vip_dev0_act_slave = 24 vip_dev1_mname = "" vip_dev1_pos = "rear" vip_dev1_lane = 1 vip_dev1_twi_id = 0 vip_dev1_twi_addr = vip_dev1_isp_used = 0 vip_dev1_fmt = 1 vip_dev1_stby_mode = 0 vip_dev1_vflip = 0 vip_dev1_hflip = 0 vip_dev1_iovdd = "" vip_dev1_iovdd_vol = 2800000 vip_dev1_avdd = "" vip_dev1_avdd_vol = 2800000 vip_dev1_dvdd = "" vip_dev1_dvdd_vol = 1500000 vip_dev1_afvdd = "" vip_dev1_afvdd_vol = 2800000 vip_dev1_power_en = vip_dev1_reset = vip_dev1_pwdn = vip_dev1_flash_en = vip_dev1_flash_mode = vip_dev1_af_pwdn =

Hello there. I'm owner of nano pi m1 board. I want use hid usb gadget on this board, but no success. First I use prebuild image from download section. I fugured out, that the image contains android_usb gadget and it's works (i didn't go deep, but i see, that after some manipulations with files my computer see nano pi as mass storage). Ok, this shows that nanopi board can be used as device. Go next. I need to load g_hid module, but there is no such module in the default image. Ok, time to compile custom kernel (with Igor's script this is easy). I included hid usb gadget via menu. Booting and "modprobe g_hid". Failed. "No such module" turns into "No such device". Hm... "modprobe -v -v -v g_hid" says that problem is "could not open '/sys/module/g_hid/initstate': No such file or directory". Nothing i can do with this. Whats next? I read about gadgetfs and configfs. Trying to create new images with this modules. No luck. Armbian working, usb gadgets - no. Another try - compile dev kernel, not legacy. "modprobe libcomposite" works! Oh... There is /sys/kernel/config/usb_gadget here! May be this time it will be work? Nope. Last step of using configfs is "echo [something] > UDC". This [something] must be from /sys/class/udc, but this dir is empty. On legacy kernel there is sunxi_usb, if i remember correct. So, what can i do to? Any ideas to activate HID?

Hello We are using NanoPi M1 board for robot application.So I am trying to install Ubuntu 16.04 LTS. I want installation procedure for Ubutu. In nanoPi M1 manual they mentioned only for Windows OS. If anyone knows procedure please help me.

I think I know the answer to this but I'll ask anyways. Is there any command line software out there (e.g., VLC) that I could put onto an Armbian Server Edition version that would show a movie out on the HDMI port? I have a NanoPi M1 that has a HDMI port. But I'm assuming that without all the Desktop video driver, it isn't possible to do this on a headless server.

Hello Armbian-community. I'll make this short: I've got a NanoPi M1 running with the latest available "Armbian_5.25_Nanopim1_Debian_jessie_default_3.4.113.img"-image on a 16GB Class 10 microSD. When trying to run "modprobe g_multi" as root, the following error occurs: modprobe: ERROR: could not insert 'g_multi': No such device I want to have a multifunctional gadget via the OTG-port. It should mount ISO files as CD-ROM (in which I succeeded so far with: "modprobe g_mass_storage file=/home/user/iso.iso stall=0 cdrom=1 && echo 2 > /sys/bus/platform/devices/sunxi_usb_udc/otg_role") and forward keyboard strokes made at the shell as a HID-Device, which also fails: (modprobe: ERROR: could not insert 'g_hid': No such device) I'm new to MCU-Development. Any hints? Do I have to compile modules like "g_multi" and "g_hid" into the kernel first? Which modules should I take (from where, which source). I'm sorry if it annoys you and sounds all noobish to you, but I really don't know what do do any further. I read through the documentation on how to compile the kernel incl. modules yourself, but I just don't know how to proceed, because it confuses me a little that those modules seem to be already in the current image and they are just not working. I just need someone to point me into the right direction. Thank you! Edit: I further played around with the cd-rom emulation. Is there a way to set a Vendor/Product-Name? I tried to fiddle around with the following parameters, but nothing changed at BIOS/Windows/Ubuntu. It just says "USB:"@ BIOS, and "USB-Device" under the DVD/CD-ROM Section@Windows Devicemanager.

when i triaing change monitor in NANO PI M1 from HDMI to DVI ( H3disp 1080p ), then i cannot start system in a DVI monitor. After changed HDMI monitor is also blocked. Then you have to delete into another computer in sd card your scirpt bin file and rename script.bin.back to script.bin to return to HDMI monitor. DVI does not work at all . maybe it is producer error not software.

Hi all, I have no luck to get wifi work on NanoPi M1 with the usb dongle RLT8188CUS. I have followed the tutorial "OPI ONE wireless success" to config. But, I don't see any "wlan0" or wifi device at all with the usb dongle plugged in. "nmtui" does not detect any wifi device as well. It appears to me that, although armbian recognizes the usb dongle, armbian does not treat it as a wlan0 device. I very appreciate if anyone can give me some suggestions to diagnose and fix I am using armbian-jessie-server, kernel 3.4.113, jessie 5.23. Below is the info of my board. === uname -a === Linux nanopim1 3.4.113-sun8i #4 SMP PREEMPT Sun Nov 20 09:58:26 CST 2016 armv7l GNU/Linux === dpkg-query -W -f='${Version}\n' linux-jessie-root-nanopim1 === 5.23 === lsusb === Bus 004 Device 002: ID 0bda:8176 Realtek Semiconductor Corp. RTL8188CUS 802.11n WLAN Adapter === lsmod === rtl8192cu 61736 0 rtlwifi 46157 1 rtl8192cu rtl8192c_common 33398 1 rtl8192cu mac80211 363748 3 rtlwifi,rtl8192c_common,rtl8192cu === dmesg === [ 38.988987] ehci_irq: highspeed device connect [ 39.000794] ehci_irq: highspeed device disconnect [ 39.002524] ehci_irq: highspeed device connect [ 39.250258] usb 2-1: new high-speed USB device number 2 using sunxi-ehci [ 39.556755] rtl8192cu: Chip version 0x10 [ 39.664596] rtl8192cu: MAC address: 00:13:ef:63:0c:e9 [ 39.675039] rtl8192cu: Board Type 0 [ 39.683964] rtlwifi: rx_max_size 15360, rx_urb_num 8, in_ep 1 [ 39.695294] rtl8192cu: Loading firmware rtlwifi/rtl8192cufw.bin [ 39.707111] usbcore: registered new interface driver rtl8192cu === ifconfig -a === lo0 eth0 tunl0 === cat /etc/modules === 8192cu === cat /etc/network/interfaces.d/wlan0 === # The primary network interface auto wlan0 allow-hotplug wlan0 iface wlan0 inet static address 192.168.0.233 netmask 255.255.255.0 gateway 192.168.0.1 wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

Is there a Xenial image for NanoPi M1, or a way to “easily†build one ?. I see here https://www.armbian.com/nanopi-neo/ that there is a Xenial image for NanoPi Neo. I am asking because I would like to run HQPlayer's Network Audio Adapter on my NanoPi M1. And this doesn't run on Debian Jessie legacy as it needs libstdc++6 (>=5.2), but it does run on a NanoPi Neo with Xenial. Any advice appreciated. Thanks

Hi I have nano pi m1 with armbian installed. When I play video on firefox, it shows but the sound is too choppy like sea waves and I don't hear the real sound. what should I do to fix it?

I can download armbian source code and build. Is there a way to build kernel only for my board NanoPi M1? I haven't tried building Debian, from wiki.friendlyarm.com building kernel only can be done by: ./build.sh -p sun8iw7p1 -b nanopi-h3 -m kernel Is there an equivalent option for armbian? Thanks.

I'm running OpenElec on a NanoPI-M1 and one thing missing is having the screen blanked when the screensaver kicks in, allowing the monitor to power down. In Kodi there's no option to do it, unlike when running in other OS. Probably someone is going to direct me at CEC but that does not work for me as I have a PC monitor connected to the board through a HDMI->VGA adaptor. I've read in the sunxi docs that the '/sys/class/graphics/fb0/blank' sysfs entry should control blanking for the framebuffer, therefore blanking the HDMI output, but it either does not work that way or at all, as nothing happens. On the RP world there is a command line utility that can enable/disable the video output, is there any way of doing it on an H3-based board ?