-
Posts
13649 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by Igor
-
-
2 hours ago, tristan said:
Does anyone know why the current nanopi neo 2 image does not include the ath9k_htc driver? The nanopi neo image included it.
Nanopi Neo 2 uses different chip and architecture (H5, arm64) kernel and configurations are not and can't be always the same. This is config for Neo 2 kernel and it looks like this module is there:https://github.com/igorpecovnik/lib/blob/master/config/kernel/linux-sun50i-dev.config#L1764
-
-
Now add this to /etc/rc.local and it will.
-
BTW: with next update we will include this installer:
-
IIRC if you install Transmission with this command:
apt install transmission-cli transmission-common transmission-daemon
you don't need to do anything else. It starts automatically. Similar goes for others ... just follow generic Debian & Ubuntu install guides and you should be fine.
-
We use stock Debian Jessie system(d) manager. Some background and tips:
-
Audio & video playing with mpv player should be fine, while there is no media / web acceleration within any web browser.
-
9 hours ago, Superkoning said:
https://github.com/igorpecovnik/Debian-micro-home-server/tree/dev does not contain armbian-config, but debian-config (which contains the same code). So ... how should I send a Pull Request?
This is it. It's only renamed upon install. The idea behind is to develop generic architecture independent installer and config with build in special things for Armbian, when used within.
Yes, there are typos and bugs to hunt down and it's better if this is done by somebody else but me. I can overlook even most obvious one at this stageEdit: If someone has time - we could move up a little. Instead of toggling we could provide adjusted text related to reality:
Wireless - connect to your router / Wireless - disconnect from your router
-
Once at first login or perhaps for user root only?
-
-
We haven't change anything vital ... what kind of error do you get? Where do you stuck?
-
It's one of those minor / unimportant issues, for which no one has find time to check what's wrong. If you find out, please provide a fix.
-
6 hours ago, BigG2017 said:
not sure if the OS is actually the problem.
In most cases, problems are drivers and WiFi drivers are among most critical ones. It's actually hard to find a good working one. RTL8812AU was working fine on my brief testing ... but don't actually use it.Not with build in driver, but with this one: https://github.com/gnab/rtl8812au It's easy to compile within armbian, just blacklist the on which is build in if necessary. And make sure you have good - original power supply, USB3 powering is a must.
-
-
I think the only difference between this openwrt and our legacy is enabled power management (by mistake) in one of our early builds. Disable PM and wifi connecting shoul dramatically improve.
Wrote on mobile -
how do you power the tablet? is battery operational?
-
1 hour ago, tao said:
Or would it be more accurate to say it'll be acceptable
Orane Pi Zero as an IOT node is good enough. To be more precise, transferring data in a client mode with low speed and low range demand, is acceptable, mainline (still development) kernel is recommended in any case. -
57 minutes ago, tao said:
Orange Pi forum asking them to improve their wifi hardware
I guess they realised and Zero2 is getting Ampak 6212, which is much better ... while I saw this crappy wireless chip on one Friendlyelec board (Neo plus 2) -
@tao
This kernel is still in development phase - we don't provide user support for it and AFAIK new Ethernet driver is in making. It's seem a waste of time to implement temporally workarounds into the user space if proper solution is around the corner.
-
4 hours ago, dony71 said:
so i just do restart hostapd in /etc/rc.local
That's good enough workaround. I guess we need to create a proper systemd compatible startup script. I'll try to implement it to general configuration, now that I know about this problem. -
1 hour ago, Thedemon007 said:
script.bin for A13-SOM
This is the critical part. You will need exact board configuration (script.bin) for your tablet, so you need to find it ... from stock Android, which is probably on your NAND. If you already killed it, than you need to find stock image ... -
Click tab Nightly releases.
-
There are three kernels (two "legacy" 3.14 and mainline) for those boards (cubox, hummingboard 1 and 2, ...) while none is perfect ... Your board is directly supported (have it's own board configuration) only in Solidrun development kernel, which we don't use due to problems with PCI stack. Well, it's possible to build an image with that kernel, but we don't provide downloads and/or support. I don't use that kernel in any way.
I would advise you to go for 4.9.5 -> can be upgraded to 4.10.9, but there you will also need to force loading DTB to make this board boot. I'll try to make this process simpler in the future or make a separate DTB files for all those "new" boards, which might need special treatment. But it's some work and I don't have any of this hardware to make a test.
-
That's correct - as I told, this logo function is not completely done and functional since it has some bugs and I don't know how to proceed.
Armbian headless for Banana Pi
in Allwinner sunxi
Posted
All server images are minimal, without a desktop. Default download, if you don't choose anything, is headless / server image.