HarfTarf
-
Posts
11 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by HarfTarf
-
-
why design a board with Ethernet AND wireless ?
Yeah!!! Who in their right mind would need more than one network interface??? I only want to see computers nowadays with only one interface, or NONE!
-
Not sure if this will help, but I use x2go with great stability from all over the US, I like it better than teamviewer.
If you need to tunnel through a firewall, then you can use ngrok or pagekite, or just open a port. Personally I use tinc to vpn into home rather than opening ports. -
-
I would like to donate money so that you can buy one of these little guys.
How can I do that?
Seems FA officially announced NanoPi NEO AIR in the meantime, price is $17.99 and eMMC is not optional: http://www.cnx-software.com/2016/09/28/friendlyarm-introduces-nanopi-neo-air-with-wifi-ble-camera-interface-and-8gb-storage-for-17-99/
-
Thanks for all your work on this, I'm going to try out the images tomorrow!
-
I don't have your same WiFi dongle, but try this file: http://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/plain/rtlwifi/rtl8192cufw.bin
Hi Dear Tkaiser!
Thank you for your great work in Modifying Linux to prepare a better OS for our IOT projects.
But, there is some problem with beta images that released in Armbian Site that i couldnt solve them till now :
OS Checked :
Armbian_5.17_Nanopineo_Debian_jessie_4.6.7
Armbian_5.17_Nanopineo_Debian_jessie_4.7.2
Armbian_5.17_Nanopineo_Debian_jessie_3.4.112
Armbian_5.17_Nanopineo_Ubuntu_xenial_3.4.112
1. Connecting WiFi Dongle (MAIN PROBLEM) : Mine is EDUP 802.11N Dongle that works properly in Raspberry pi B+,
But in Any Armbian OS in Nanopi NEo , I cant use it. Error is :
[ 52.823742] rtl8192cu: Chip version 0x10 [ 52.921565] rtl8192cu: MAC address: e8:4e:06:32:29:2d [ 52.927211] rtl8192cu: Board Type 0 [ 52.931436] rtlwifi: rx_max_size 15360, rx_urb_num 8, in_ep 1 [ 52.937967] rtl8192cu: Loading firmware rtlwifi/rtl8192cufw.bin [ 52.945062] usbcore: registered new interface driver rtl8192cu [ 52.951813] rtlwifi: Firmware rtlwifi/rtl8192cufw.bin not available [ 53.010557] Error: Driver 'rtl8192cu' is already registered, aborting...
Dongle's LED not even turn on, let alone blink!2. USB OTG Doesn't work in Armbian_5.17_Nanopineo_Debian_jessie _4.7.2 . may be additional setting needed in may Windows laptop for that? i dont know !
3. Alsamixer, Amixer, aplay,.... not installed or enabled by default in last beta version of Vanilla version. For must use of IOT , it is better tat be Enabled .
Would you please give me some help for fix this problems?
-
This is a little off topic, but issue 169 of Linux User and Developer has a one page article on the NanoPi NEO. Although I was glad to see the article since I like the NEO, I was disappointed they didn't mention Armbian. I'm glad FriendlyARM provides a distro for their hardware, but after checking out Armbian, there's no going back (for me). I feel Armbian already offers much more then FA's distro, and once users realize the active development and positive atmosphere in this forum the adoption of Armbian for the NEO should be easy.
Is this the article youre talking about?
-
Nevermind, I found the solution:
root@neo:~# apt install linux-firmware Reading package lists... Done Building dependency tree Reading state information... Done The following package was automatically installed and is no longer required: libnl-route-3-200 Use 'apt autoremove' to remove it. The following NEW packages will be installed: linux-firmware 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/32.8 MB of archives. After this operation, 124 MB of additional disk space will be used. (Reading database ... 58450 files and directories currently installed.) Preparing to unpack .../linux-firmware_1.157.3_all.deb ... Unpacking linux-firmware (1.157.3) ... dpkg: error processing archive /var/cache/apt/archives/linux-firmware_1.157.3_all.deb (--unpack): trying to overwrite '/lib/firmware/ti-connectivity/wl18xx-fw-4.bin', which is also in package armbian-firmware 5.17 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/linux-firmware_1.157.3_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) root@neo:~# apt download linux-firmware Get:1 http://ports.ubuntu.com xenial-updates/main armhf linux-firmware all 1.157.3 [32.8 MB] Fetched 32.8 MB in 11s (2,872 kB/s) W: Can't drop privileges for downloading as file '/root/linux-firmware_1.157.3_all.deb' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) root@neo:~# cd /tmp/ root@neo:/tmp# apt download linux-firmware Get:1 http://ports.ubuntu.com xenial-updates/main armhf linux-firmware all 1.157.3 [32.8 MB] Fetched 32.8 MB in 11s (2,869 kB/s) root@neo:/tmp# ls linux-firmware_1.157.3_all.deb
Then extract rt2870.bin from the deb and put it here: /lib/firmware/rt2870.binFirmware can also be found here: http://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/plain/rt2870.binI am having issues using a usb wifi device:
root@neo:~# dmesg | grep rt2 [ 0.811567] sw_uart_get_devinfo()1503 - uart2 has no uart_regulator. [ 1.592428] uart2: ttyS2 at MMIO 0x1c28800 (irq = 34) is a SUNXI [ 14.352607] Registered led device: rt2800usb-phy0::radio [ 14.352852] Registered led device: rt2800usb-phy0::assoc [ 14.353151] Registered led device: rt2800usb-phy0::quality [ 14.353452] usbcore: registered new interface driver rt2800usb [ 856.017333] phy0 -> rt2x00lib_request_firmware: Error - Failed to request Firmware. [ 1100.839666] phy0 -> rt2x00lib_request_firmware: Error - Failed to request Firmware. [ 1357.002345] phy0 -> rt2x00lib_request_firmware: Error - Failed to request Firmware. [ 1362.002895] phy0 -> rt2x00lib_request_firmware: Error - Failed to request Firmware. [ 1367.000936] phy0 -> rt2x00lib_request_firmware: Error - Failed to request Firmware. [ 1372.002929] phy0 -> rt2x00lib_request_firmware: Error - Failed to request Firmware. [ 1378.006304] phy0 -> rt2x00lib_request_firmware: Error - Failed to request Firmware. [ 1384.001270] phy0 -> rt2x00lib_request_firmware: Error - Failed to request Firmware. [ 1388.004151] phy0 -> rt2x00lib_request_firmware: Error - Failed to request Firmware. [ 1393.005972] phy0 -> rt2x00lib_request_firmware: Error - Failed to request Firmware. [ 1404.001861] phy0 -> rt2x00lib_request_firmware: Error - Failed to request Firmware. [ 1408.001750] phy0 -> rt2x00lib_request_firmware: Error - Failed to request Firmware. [ 1412.002048] phy0 -> rt2x00lib_request_firmware: Error - Failed to request Firmware. [ 1418.001127] phy0 -> rt2x00lib_request_firmware: Error - Failed to request Firmware. [ 1423.007031] phy0 -> rt2x00lib_request_firmware: Error - Failed to request Firmware. root@neo:~# lshw -c network *-network:0 description: Ethernet interface physical id: 9 logical name: eth0 serial: 22:43:d7:1f:63:8e size: 100Mbit/s capacity: 100Mbit/s capabilities: ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=sunxi_geth driverversion=SUNXI Gbgit driver V1.1 duplex=full ip=192.168.10.29 link=yes multicast=yes port=MII speed=100Mbit/s *-network:1 DISABLED description: Wireless interface physical id: a bus info: usb@4:1 logical name: wlx000f6004d395 serial: 00:0f:60:04:d3:95 capabilities: ethernet physical wireless configuration: broadcast=yes driver=rt2800usb driverversion=3.4.112-sun8i firmware=N/A link=no multicast=yes wireless=IEEE 802.11bgn root@neo:~#
It seems as though the firware blob cant be found.
Any suggestions?
-
I am having issues using a usb wifi device:
root@neo:~# dmesg | grep rt2 [ 0.811567] sw_uart_get_devinfo()1503 - uart2 has no uart_regulator. [ 1.592428] uart2: ttyS2 at MMIO 0x1c28800 (irq = 34) is a SUNXI [ 14.352607] Registered led device: rt2800usb-phy0::radio [ 14.352852] Registered led device: rt2800usb-phy0::assoc [ 14.353151] Registered led device: rt2800usb-phy0::quality [ 14.353452] usbcore: registered new interface driver rt2800usb [ 856.017333] phy0 -> rt2x00lib_request_firmware: Error - Failed to request Firmware. [ 1100.839666] phy0 -> rt2x00lib_request_firmware: Error - Failed to request Firmware. [ 1357.002345] phy0 -> rt2x00lib_request_firmware: Error - Failed to request Firmware. [ 1362.002895] phy0 -> rt2x00lib_request_firmware: Error - Failed to request Firmware. [ 1367.000936] phy0 -> rt2x00lib_request_firmware: Error - Failed to request Firmware. [ 1372.002929] phy0 -> rt2x00lib_request_firmware: Error - Failed to request Firmware. [ 1378.006304] phy0 -> rt2x00lib_request_firmware: Error - Failed to request Firmware. [ 1384.001270] phy0 -> rt2x00lib_request_firmware: Error - Failed to request Firmware. [ 1388.004151] phy0 -> rt2x00lib_request_firmware: Error - Failed to request Firmware. [ 1393.005972] phy0 -> rt2x00lib_request_firmware: Error - Failed to request Firmware. [ 1404.001861] phy0 -> rt2x00lib_request_firmware: Error - Failed to request Firmware. [ 1408.001750] phy0 -> rt2x00lib_request_firmware: Error - Failed to request Firmware. [ 1412.002048] phy0 -> rt2x00lib_request_firmware: Error - Failed to request Firmware. [ 1418.001127] phy0 -> rt2x00lib_request_firmware: Error - Failed to request Firmware. [ 1423.007031] phy0 -> rt2x00lib_request_firmware: Error - Failed to request Firmware. root@neo:~# lshw -c network *-network:0 description: Ethernet interface physical id: 9 logical name: eth0 serial: 22:43:d7:1f:63:8e size: 100Mbit/s capacity: 100Mbit/s capabilities: ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=sunxi_geth driverversion=SUNXI Gbgit driver V1.1 duplex=full ip=192.168.10.29 link=yes multicast=yes port=MII speed=100Mbit/s *-network:1 DISABLED description: Wireless interface physical id: a bus info: usb@4:1 logical name: wlx000f6004d395 serial: 00:0f:60:04:d3:95 capabilities: ethernet physical wireless configuration: broadcast=yes driver=rt2800usb driverversion=3.4.112-sun8i firmware=N/A link=no multicast=yes wireless=IEEE 802.11bgn root@neo:~#
It seems as though the firware blob cant be found.
Any suggestions?
-
I recently got a NanoPi Neo 512MB, I'm running your most recent build of Ubuntu 16.04.1 from your forum post.
What do you need me to test?
Time to play with Pi 3 also, what image to use?
in Off-topic
Posted
I'm pretty sure that it has a broadcom chip and not an allwinner...