Igor
-
Posts
13640 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by Igor
-
-
@Igor - thanks that now works with your fixed image!
What manual fix did you need to do? It may be quicker than moving all my stuff across to a new image!
Check this patch:
https://github.com/igorpecovnik/lib/commit/ba3548468ed915f0540729526b16512ee48da7aa
You need to add &emac section to your device tree. Nothing more.
-
Perhaps logram size is too small for your scenario ... disable or debug the ram logging service.
systemctl disable log2ram.service
-
Can you perhaps provide serial console boot log? Unfortunately I don't have any eMMC for XU4 around.
Are you trying to boot mainline kernel 4.x ?
-
There are slim chances of mainline kernel for this board although we have it for Odroid XU4 and I saw some bits for other Samsung chips, while not for this particular one. Even if you could boot it, there will be very limited support. IIRC Odroid XU4, which is one of most popular boards with Samsung chip, doesn't have any multimedia features, not even a HDMI driver in mainline kernel ... here you can expect only worse than that.
-
I updated my Neo today - it was running mainline kernel and xenial ... after the update the thing would boot but the ethernet connection is not working - both LEDs are lit. I downloaded a fresh mainline image (the new xenial "5.25" one) and have the same issue.
Update from old (testing) images might broke, while images works. I just download, burn and boot this image:
https://dl.armbian.com/nanopineo/Ubuntu_xenial_dev.7z
on my FA Neo. Network works out of the box. If you made a download yesterday, you could accidentally download broken image. I was correcting those images manually during the evening since I figured out, that network was disabled.
-
Thanks, will be fixed asap.
-
https://github.com/igorpecovnik/lib/commit/a83a6957f523946096b1009d0fb1e0f06b88f614
Added with patches. I only try if compile.
-
Good to know. You think NanoPi is good choice? I was wondering about all options, even Raspberry Pi 3 with camera module (and BT is built-in), but I realy not need so many features as it has.
NanoPi is a good choice but AFAIK CSI camera, if you need that, is not yet supported in modern kernel.
-
I have not so much money to buy many diffrent models of SBC
Hardware is dirt cheap while "free" software can cost you some money. Luckily, if you start with Armbian, your basic things are covered - you already saved yourself hundreds of hours and dollars. That's our main advantage - you don't need to start from a pile of junk (Allwinner stock SDK) or spaghetti tutorials.
Does anybody know how to get on their forum?Why? You are wasting time. Forum is more or less inactive and their official support, just not worth the trouble creating forum username.
Which requires hiring someone talented for a few weeks/months to finish CSI framework with mainline kernelStill better than fixing legacy kernel where those things also doesn't work.
-
Than you don't have much choices except Bluetooth and WiFi direct. In both cases expect troubles and stick to modern kernel, where you have more chances of success.
For example: I can use BT keyboard and mouse nicely with Cubietruck running kernel 4.9.7 ... I didn't test sending and receiving files to mobile phone.
-
xactly, which one? I need my board to send files. The easiest way is to use WiFi network, but I have an enviroment without router (those are requirements of my product - sending files even if there is no internet). First way was Bluetooth, then WiFi-Direct. Both have problems to implement. If there will be other way - you will save my life :-) By the way - InfraRed is to slow for me.
Perhaps something like this:
http://www.dx.com/p/arduino-apc220-wireless-rf-modules-w-antennas-usb-converter-143011#.WJRDf1UrLAQ
But since I don't have any real world experiences I am only guessing.
-
WiFi. Ofc not directly interchangeable.
-
Bluetooth exists for years
It's closed source technology, require firmware to run, it's know to cause problems. This simply means that it's to avoid in first place. There are other and better ways for wireless comm.
Hardware maker are just people / engineers which sometimes overestimate and make mistakes. If you add commercial agenda to this, things become only worse. For a board which cost 9 USD shipped, 1 USD is a lot
. And they don't invest much into software. This goes from zero up to just a little. Even software is "free", it cost a lot of money to develop it.Armbian makes things closer to ordinary users and saves time, but we can't make a perfectly smooth plug and play operating system. Just remember to have fun in first place
-
Bulletproof is only something like this:
https://docs.armbian.com/User-Guide_Advanced-Features/#how-to-freeze-your-filesystem
-
Regarding CPU power, Opi0 is a decent board. It is usable on a short distance for transferring small chunks of data since transfer speed over on board WiFi chip is low. If your use scenario meets that, you will be fine, otherwise just use Ethernet or attach some high powered (2000mW) USB wireless card like this one:
and wireless range will be extremely long.
-
It boots (I made a test), just video out is somehow failing and we wrote down this fact in release documentation which is hard to miss. We don't have resources to fix such problems in last minute and also removing the board would raise questions. In last 24h I made only few hours sleep since I am fixing small things on the way while releasing around new 150 images, which were built one after another in an automated way (for a whole day). Unfortunately I could not find a fix for M2. With adding a note we give out important information, which should prevent you in using broken image and raising unnecessary and costly support questions.
You understand now?
Just remind yourself that this operating system and the tool come as is in first place and if it doesn't work, you report that or try to fix the problem on your own. No one will jump and start fixing.
-
Without a log, only wizard can help
Latest image from download section works - I attached mechanical drive yesterday and it works fine. If you ware upgrading we need to see logs to give you advice what to do next.armbianmonitor -u
-
It seems producers only care to relase new models, put more cores, more MHz, forgetting drivers and software at all?
True, but they usually don't create software in first place. They just push out what they get from Chip maker, something unfinished, half done and they do this all the time. None of board maker produce stable software, but 3rd party companies, groups, community so it's not much relevant if they put out new version every month. Usual community response is that some boards are ignored and therefore support remain on that half done / initial support. Useless for average Joe.
Most of boards (if not all) which we support, can be used in production. You just have to read recommendation and not use kernel / image with labels "preview" "beta" "experimental" "development" and you should be fine.
Older boards (A10 / A20) are better in term of stability, since they are longer around and all rough edges were found and fixed. Next are most popular boards, where this happens quicker. People use those boards in production for various services - not everybody is playing with them. I use two A20 boards for various services with uptime measured in months. It would be in years if I hadn't update them from time to time. Until fall 2016 all our services were running on A20 and Odroid XU4. Zero problems.
Bluetooth and wireless are mostly covered with closed source drivers (firmware), which means troubles. If they work out of the box fine, if not, we try to fix them if it's in our power, otherwise this remain as is. Especially we don't try to fix 3rd party hardware, things which you attach to the board, since this is out of the project scope. We are few people and there are zillions of devices out there.
We provide basic system and that system is stable (if not stated otherwise). When you start to plug things into your board you have to understand what are you doing.
-
-
Ethernet not working on latest development - i'll try to fix it right away.
-
Why so? Is it possible to configure wifi in such way on 3.4.113 ?
No idea.
Why bother if you got it working on modern kernel in first place? Well, you will need to check kernel source, configuration, driver, ... as you can see, there are 100+ https://github.com/igorpecovnik/lib/tree/master/patch/kernel/sun8i-default patches over this kernel. It's a mess and there is no other way than digging into, if you really want to solve it / understand.
-
I'm confused - new to Armbian and looking for an image for the nanopi-neo. The web page for this board shows 4.9.4 as Mainline and older versions as Legacy.
Is there currently any image that will work for this board?
We are in the middle of general update (upload is in progress since morning), so there will be new image today.
They all should work, last build was tested few days ago, here is brief testing log:
---------------------------
distro tested: Armbian_5.24.170131_Nanopineo_Ubuntu_xenial_dev_4.9.4.imgboot from uSD: OK
Wired network connection works with dedicated speed: KO. eth0 does not pop up, maybe because new mailnine rename the ethernet port from ethx to that stupid sequence of alphanumeric string. anyway, 'dmesg | grep eth'
does not report any entry. Also cat /proc/dev/net report presence of only 'lo' device.
Filesystem resize finishes successfully: OK
Shutdown: OK
reboot: OK
Mainline kernel works the same way: i am not sure to understand te meaning of the task. i can say that i go around inside distro (via debug serial port) and it appears to be ok, i see 4 cores, top works,
---------------------------
-
Repository was updated today at around 4 a.m. at CET.
apt-get update
should do the trick. And beware that you are switching to development kernel which might work or not.
-
And can I use hostapd-realtek with nl80211 driver by changing the config ?
I forgot / am not sure if this combination work, but just try. I think realtek version is needed on some older drivers, while nl80211 is used with more recent realtek drivers found in mainline kernel. We provide both, that you are ready to do quick experiments without a need to compile hostapd on your own.
Orange Pi Zero no audio devices available cannot play audio
in Orange Pi Zero
Posted
Kernel 4.8.4. You are using developing kernel for which we don't provide any end user support. It's meant for developers and testing. On the download page, there is a big red sign: Warning: nightly downloads are automated untested builds and no end user support is provided for them!
If you want audio and microphone with this kernel and addon, which is not officially supported yet, you need to write a driver. There is nothing like "install a driver".
http://linux-sunxi.org/Linux_mainlining_effort / here you can see how far things are developed
You will have more success with old kernel 3.4.113 ... but even there you might need to play with board configuration (/boot/script.bin) switches. Microphone or audio might be disabled on this board, since by default it doesn't have audio connector.