-
Posts
13589 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Community Map
Posts posted by Igor
-
-
What is the screen resolution of your display?
-
By rewriting wireless driver since it's buggy. In kernel 4.x this problem should be gone.
-
Safe to ignore and safe to delete those directories.
-
5.14 is old build and those boot scripts are different, upgrade is also not recommended. Perhaps better to start with fresh image ...
-
https://forum.armbian.com/index.php/topic/2344-pwm-on-allwinner-h3/
And use this search engine to get other posts regarding pwm:
-
I'm new to Linux
I completely understand your wish but what you want to achieve is hard even for hardcore Linux users, since there is no working (stable and with HW acceleration) packaged KODI for Debian / Ubuntu for those boards (H3).
This doesn't mean it's impossible, but if you are a newbie, forget about ... Get some other platform, preferable Intel, where this is near to easy install ... or use one H3 board for server with Armbian and another one for media centre running Openelec.
-
Hello dear people of the forum.
I have Banana pi m2+ a week actually already have been struggling to install kodi,there are always some mistakes. I want to install Kodi on Raspbian finished Assembly \ Ubunru all my attempts have not crowned success.Tell me is there some sort of work instruction is time tested to install Kodi?
Thank you in advance for your answers
If you want KODI on this board, check down.nu if there is an Openelec build for this board. This is only possible working solution.
-
Main repository was updated - all kernels were fixed and updated to latest versions.
-
Try to provide as much information as possible regarding display, otherwise is hard / impossible to provide any help.
-
@Myy
Welcome and thanks for update. At least we have something on the bug list now
@tkaiser
I had no luck ... I started with Ubuntu Xenial and ... lot's of dependencies did not met and at the end Kodi crashed
-
-
only the kernel... do you recommend full image?
Yes ... in case you don't know exactly what you are doing. Read Zador's post again - he wrote you what to do instead.
-
Sources are fixed and I don't mind if we push and update even it's not that critical.
I did patch / compile test only on sunxi-next so far.
-
This is quite standard device, it's enabled in both kernel configs:
https://github.com/igorpecovnik/lib/blob/master/config/kernel/linux-sun8i-dev.config#L4251
https://github.com/igorpecovnik/lib/blob/master/config/kernel/linux-sun8i-default.config#L3105
-
Leave this as is
FORCE_CHECKOUT="yes" # ignore manual changes to source
and use
CREATE_PATCHES="yes"
Apply change to source when asked and pickup patch which will be created userpatches/patch ... this patch should be moved to appropriate dir:
userpatches/kernel/udoo-next
or move it to
lib/patch/kernel/udoo-next
and create PR to our repository since it might be useful for others too.
Option which you used is working properly only on source where no patches are initially involved ... we have to change / note this.
-
Whats wrong? On the emmc is an old system
Nothing is wrong.
There are no (stable) drivers for "eMMC" (NAND) in a kernel that you are trying to use. NAND on Cubietruck is slower and more prone to crash than a modern SD card.
-
Can you provide kernel log - set console to ttyS0 and enlarge verbosity and provide content of boot.cmd
From which version you made an upgrade. What was initial image build?
-
Driver is present in the source (cubox-i NEXT or DEV). Check dependencies.
-
Find anything?
Yes. You must compile kernel by using our tools or include our kernel patches and it will work. We also fixed bugs and prepare kernel packages for our boot scenario. Just in this case everything works simply by installing the package. If not ... you need to set and adjust paths and boot scripts manually.
-
I've reactivate my BPro after a long time...
What do you mean with "it could be broken"? Hardware? Kernel? DTS?
That SPDIF support in kernel was somehow broken, stopped working. I am trying to find out if you might have it working in v4.9.10 (or older) ... and it stopped working on upgrade to version released few days ago. In such case last known good kernel is a starting point.
-
Uuuups, sorry, my mistake. I'm using 4.9.11, sorry. It's pure mainline, without any patches or so.
I've compiled spdif, i2s, can, ... as modules.
But you had it running on mainline kernel before, or is this the first try? I mean, it could be broken.
-
Next test was done with mainline kernel 4.10.0 and performance CPU governor, while the one before was done on 4.4.50 with powersave.
random random kB reclen write rewrite read reread read write 102400 4 2527 2558 13977 14042 11684 2457 102400 16 8800 8918 28143 28229 26319 8692 102400 512 27341 27273 42205 42257 42042 27342 102400 1024 27834 28148 42597 42648 42559 27925 102400 16384 28056 28484 45067 45142 45128 28636
I guess those eMMC chips are simply different, yes.
-
- fixed eMMC install,- added development kernel (4.10.x) with MALI driver (untested)
Onboard 16GB eMMC media performances - not the top performer but still very decent.
root@miqi: iozone -e -I -a -s 100M -r 4k -r 16k -r 512k -r 1024k -r 16384k -i 0 -i 1 -i 2 File stride size set to 17 * record size. random random kB reclen write rewrite read reread read write 102400 4 2403 2503 12483 12840 10950 2400 102400 16 8277 8682 26678 26378 24787 8526 102400 512 26729 27105 40906 40921 40702 27001 102400 1024 27644 27575 41840 41808 41731 27562 102400 16384 28077 28056 43618 43609 43589 28147
-
Updated. It should be populated with data from all forums now.
H3/NanoPI Neo stock build failed
in Armbian build framework
Posted
And the only one? I am sure there is room for improvement, but just don't expect that you will jump on experienced
developerlevel in one day. This script become complex if you go out of default zone. This build system is used by us on daily basis and there more and more 3rd party users who are using it for their purpose. If something goes wrong, we fix it or they fix it - with specific fixes, since saying "this script sux" is useless information.Feel free to use and compare to alternative solution if you make them work
http://www.orangepi.org/orangepibbsen/forum.php?mod=viewthread&tid=2451&extra=
http://www.orangepi.org/orangepibbsen/forum.php?mod=viewthread&tid=394