-
Posts
275 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by dolphs
-
-
good news - However guess that will be coming Monday once 5.4.0 will be born ( assuming 5.4-rc9 won't be released instead )?
-
OK - pity though built from scratch buster minimal as well downloaded image, however image does not boot up (OpiOnePlus) from sdcards tested.
[ UPDATE: slight correction I do see orangepioneplus in my DHCP leases window, however unable to SSH to it ]
Rgd WIP , the compile tool shows H6 boards are mature now ( screenshot attachment )
Also noticed kernel is still on 5.3.9 while others ( OdroidC2, Rockpi4, etc ) are on 5.3.12/11 currently so guess I just wait another two weeks aiming for 5.4.x ;-)
cheers
-
"yous guys" are bad :-), thanks meanwhile upgraded current rock4a succesfully.
so building fram scratch should go like this " ./compile.sh BOARD=orangepioneplus BRANCH=current RELEASE=buster BUILD_DESKTOP=no KERNEL_ONLY=no KERNEL_CONFIGURE=no BUILD_MINIMAL=yes " or still DEV?
-
Hmm yea something like size of "NanoPi NEO Core2-LTS" and instead equip with 2 or 4Gb of RAM including RK3399 would be nice for my scenario.
The NEO4 has only 1Gb and also no need for BT and WiFi, supply as possible add on.
Perhaps something for Shenzhen Xunlong Software CO.,Limited to manufacture?
-
On 11/8/2019 at 5:54 PM, martinayotte said:
I've sorted out patches that were preventing builds, but there still some patches where chunks failed without disturbing builds, let says, for OPi3/OPiLite2/OPiOnePlus/PineH64 as well as H3/H5 ones .
Yes, maybe end of the month is a good target ...
should be excellent considering kernel 5.4 will be stable by then, will stay tuned chaps. thanks for your efforts!
-
-
cheers I was aware of that, but thought more enhancements are on its way in 5.5 ( not just for H6 btw ) but looking closer this seems to be old news ;), nite nite
-
Rgd OpiOnePlus image...
Currently I do not use the board, but l recall a discussion somewhere whether the port is an USB3 one or USB2 one?
Anyway according to Xunlong it is not ( no longer ) while in downloads " USB3 sometimes doesn’t detect high-speed devices properly " can be read ?
This has to do with latest changes rgd usb3-now-working ( as well planned for kernel 5.5. )?
-
. wrong location, sorry .
-
5 hours ago, SchmuseTigger said:
Wait, BT is working with 5.4 RC now?
Also check the mainlining effort page , kernel 5.5 is supposed to bring us lots of joy and perhaps by then H6 can be out of WIP stage, but is still 2-3 Months away from now ...
Looks like it is also interesting regarding CRYPTO, if you use eg ovpn or SSL ...
UPDATE
@megi Did not notice your reply earlier, btw thanks for bump to 5.4-rc6
-
Hi - You might be right I accidentally hit 4a instead of 4b... <sigh> ...
Anyway 4b OK, but BOARD=rockpi-4a still NOK, just built fine with ayufan-1120 ( 5.4.-rc1 ) :
./compile.sh BOARD=rockpi-4b BRANCH=dev RELEASE=buster BUILD_DESKTOP=no KERNEL_ONLY=no KERNEL_CONFIGURE=no EXPERT=yes BUILD_MINIMAL=yes AUFS=no
thanks !
UPDATE: both cooked just fine ( did not flash and test ):
-rw-rw-r-- 1 root root 708837376 Nov 6 23:24 Armbian_5.99_Rockpi-4a_Debian_buster_dev_5.4.0-rc1_minimal.img -rw-rw-r-- 1 root root 708837376 Nov 6 23:15 Armbian_5.99_Rockpi-4b_Debian_buster_dev_5.4.0-rc1_minimal.img
-
9 hours ago, Igor said:
Expected to not be o.k. without adjustment. Since you had to adjust build parameters for that ... are you sure you are doing right things? And we never supported DEV builds (its as is, wait that is fixed, fix on your own).
agreed with that , but 16 October I was still able to build ( using AUFS=no ), apparentely things changed that way dev build is currently broken.
-
14 hours ago, martinayotte said:
My H6s are running 5.4.0-rc4 from megous's branch, it is just some preview builds I've done, but I didn't commit to Armbian yet ...
cheers for that, will await your commits and meanwhile will play some more with my RockPI4a - TiA! -
-
O dear, "something" happened the other day ( 1 November ) as it seems it is currently impossible to build a fresh image ( both 5.3 and 5.4 images ):
just checked out fresh "compile" environment from github, tried both ayufan 1118 ( default 5.3-rc4 ), 1119 ( 5.3 ) and 1120 ( 5.4.-rc1 ) but NOK
Displaying message: Cleaning arm-trusted-firmware-rockchip64/rockchip info Displaying message: Compiling ATF info Displaying message: Compiler version aarch64-linux-gnu-gcc 6.4.1 info Displaying message: Started patching process for atf rockchip64-rockpi-4a-dev info Displaying message: Looking for user patches in userpatches/atf/atf-rockchip64 info Displaying message: * [\e[32ml\e[0m][\e[32mc\e[0m] add-trust-ini.patch info Displaying message: ERROR in function compile_atf compilation.sh:87 err Displaying message: ATF file not found trust.bin err Displaying message: Process terminated info
Also noticed " Armbian_5.99.191031_Rockpi-4b_Debian_buster_dev_5.3.0-rc4_minimal.7z " is latest available to download ( which should work/boot on 4a I suppose )
-
On 10/28/2019 at 3:26 PM, martinayotte said:
Anyway, I will try to find some "missing time ingredient" in the following days, and Armbian will then be ready for a commit ...
Any luck finding an additional hour? ( too bad we missed the 27 October time slot, one hour for free ... ... )
Anyway noticed rc6 has been released meanwhile, but is not in megous 5.4 - branch yet, worth waiting for that before committing things ?
-
-
Hi - In an effort to get this going I failed hopelessly ...
Logs say basically grepping on duplicate the "sun50i-h6.dtsi" patch should be disabled
compilation.log:arch/arm64/boot/dts/allwinner/sun50i-h6.dtsi:707.21-719.5: ERROR (duplicate_node_names): /soc/i2c@5002000: Duplicate node name compilation.log:arch/arm64/boot/dts/allwinner/sun50i-h6.dtsi:721.21-733.5: ERROR (duplicate_node_names): /soc/i2c@5002400: Duplicate node name compilation.log:arch/arm64/boot/dts/allwinner/sun50i-h6.dtsi:735.21-747.5: ERROR (duplicate_node_names): /soc/i2c@5002800: Duplicate node name compilation.log:arch/arm64/boot/dts/allwinner/sun50i-h6.dtsi:1177.18-1185.5: ERROR (duplicate_node_names): /soc/ir@7040000: Duplicate node name
So tried to disable it by creating empty file sun50i-h6.dtsi.patch in to ~/armbian/userpatches ,but alas
Meanwhile will do some more digging as I expect more to come as rc5 has seen the light ( but dev kernel is still on kernel [ 5.4.0-rc4 ] ) and in the end I hopefully learnt how to properly exclude armbian patches
TiA! :-)
-
19 hours ago, Werner said:
Some patches can be applied even though their content has been merged to upstream already. Go to the log directory and check where exactly the error has occurred.
cheers for that, just attached logs from "~/armbian/output/debug ", grep-ped on FAILED, failed, error etc but too many bogus ( warnings ) for me atm
10 hours ago, martinayotte said:I will try to find some free time, which still the "missing ingredient" ...
would be so much appreciated :-), hope u have time to quickly browse to the logs attached
TiA!
-
hi - would it be possible to bump dev build to " KERNELBRANCH="branch:orange-pi-5.4" please,
as the H6 boards, eg "orangepioneplus", are in WIP anyway?
Yet manually updated "~/armbian/config/sources/sun50iw6.conf ", but no success compiling with
" ./compile.sh BRANCH=dev RELEASE=buster BUILD_DESKTOP=no KERNEL_ONLY=no KERNEL_CONFIGURE=no EXPERT=yes BUILD_MINIMAL=yes "
This result in dtb issues :
DTC arch/arm64/boot/dts/allwinner/sun50i-h6-beelink-gs1.dtb DTC arch/arm64/boot/dts/allwinner/sun50i-h6-orangepi-3.dtb scripts/Makefile.lib:306: recipe for target 'arch/arm64/boot/dts/allwinner/sun50i-h6-beelink-gs1.dtb' failed scripts/Makefile.lib:306: recipe for target 'arch/arm64/boot/dts/allwinner/sun50i-h6-orangepi-3.dtb' failed scripts/Makefile.build:509: recipe for target 'arch/arm64/boot/dts/allwinner' failed Makefile:1244: recipe for target 'dtbs' failed [ error ] ERROR in function compile_kernel [ compilation.sh:382 ] [ error ] Kernel was not built [ @host ] [ o.k. ] Process terminated
-
On 7/24/2019 at 12:16 PM, gufmar said:
Instead of breaking the (bright) onboard LED's it might be a good idea to use some small piece of black tape.
How far are things atm, is it possible to " switch off "
or should I go to one of the DIY chains and grab some black tape instead
-
-
Hi- Would it be possible to upgrade dev image to KERNELBRANCH='tag:5.4.0-rc1-1120-ayufan' please in config/sources/rockchip64.conf
Yet tested particular tag and it does not result in a bootable image ( for rockpi 4a ) though,
building with these : " BRANCH=dev RELEASE=buster BUILD_DESKTOP=no KERNEL_ONLY=no KERNEL_CONFIGURE=no EXPERT=yes " result in:
LD [M] drivers/net/wireless/rtl88x2bu/88x2bu.o AR drivers/net/wireless/built-in.a AR drivers/net/built-in.a AR drivers/built-in.a [ error ] ERROR in function compile_kernel [ compilation.sh:382 ] [ error ] Kernel was not built [ @host ] [ o.k. ] Process terminated
Just wondering if there is any focus on this or is the plan to wait for e.g. a new tag with rc3 from ayufan ?
cheers
-
14 hours ago, SchmuseTigger said:
CPU temp: 62°C
still ondemand, try with conservative ..
might result few degrees lower ..
though temperature is rather high imho should be +/- 40 degrees ( depending whether idle or not )
-
1 hour ago, SchmuseTigger said:
64° while running stuff like PiHole. And yes has a heatsink but now fan running right now. But yes, seems higher then before.
What shows your output " cpufreq-info |grep governor " - Should be ondemand I suppose, or set to anything else - eg performance?
Perhaps "conservative" is a nicer way for your situation ramping up step by step to reduce CPU temp ( cpufreq-set -g conservative ) ...
Anyway will build ( BOARD=orangepioneplus BRANCH=dev RELEASE=buster BUILD_MINIMAL=yes BUILD_DESKTOP=no KERNEL_ONLY=no KERNEL_CONFIGURE=no ) and flash my H6 OPiOnePlus later today , or is 5.3 already in default branch ( stable? )
Orangepi 3 h6 allwiner chip
in Allwinner sunxi
Posted
Barrel connected or "USB OTG" power supply, also is it 5v 2 or 3ampere that is connected?
I tried a 5v 2ampere USB OTG as well the barrel ( 5v 3a) but unable to get it stable, perhaps 5.3.12 ( looks like "next" is being compiled with that version )