Igor
-
Posts
14518 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by Igor
-
-
-
Correct about gigabit network, false about USB3. Check https://www.armbian.com/download, features - at least theoretical - are up to date. Note that USB3 implementation on boards with actionsemi chip does not work properly. / not at usb3 speed
-
Orange Pi PC+ boots fine ... except boot logo is not working. GMAC at A20 than. Will check some H3 gmac if there are any troubles.
SpoilerU-Boot SPL 2017.05-armbian (May 29 2017 - 20:22:28) DRAM: 1024 MiB Trying to boot from MMC1 U-Boot 2017.05-armbian (May 29 2017 - 20:22:28 +0200) Allwinner Technology CPU: Allwinner H3 (SUN8I 1680) Model: Xunlong Orange Pi PC Plus I2C: ready DRAM: 1 GiB MMC: SUNXI SD/MMC: 0, SUNXI SD/MMC: 1 *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: phy interface0 eth0: ethernet@1c30000 Hit any key to stop autoboot: 0 38518 bytes read in 138 ms (272.5 KiB/s) Unknown command 'bmp' - try 'help' switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 3565 bytes read in 186 ms (18.6 KiB/s) ## Executing script at 43100000 U-boot loaded from SD Boot script loaded from mmc
-
7 minutes ago, zador.blood.stained said:
Huh? And older releases boot fine?
Yes. I just boot PC+ with 2017.03 and it boots fine. Slim chances that it was not recognised before and it is now.Could be SD card issue, but now I have 2017.03 and it works. Will do more tests ...
Edit: Banana PRO is real problem, reported by some user few days ago.
-
Opi One/Lite/PC+ , the latter gives:
U-Boot SPL 2017.05-armbian (May 29 2017 - 19:24:06) DRAM: 1024 MiB Trying to boot from MMC1 MMC: no card present mmc_init: -123, time 2 spl: mmc init failed with error: -123 SPL: failed to boot from all boot devices ### ERROR ### Please RESET the board ###Banana PRO gmac, legacy kernel IIRC
-
I was doing some testing and it looks latest u-boot is broken for Allwinner H3 (no boot), A20 (Banana no network), I assume A10 too. There was some RFC upstream, but I did not go further into details ... Shall we rather rollback to 2017.03?
-
45 minutes ago, BrUser said:
Ethernet does not working for legacy kernel + desktop, generated by Igors build tool: ARMBIAN 5.27 stable Ubuntu 16.04.2 LTS 3.4.113-sun7i.
It looks like in last u-boot some parameters were messed up for some Allwinner boards. Workaround:https://forum.armbian.com/index.php?/topic/4374-compiling-kernel-for-banana-pi/
-
4 hours ago, chowderhead said:
I've read many posts here and understand the OPi0 wireless chip isn't very well liked.
Opi Zero is not suitable for such complex setup. Even you manage to patch the driver (for which you need advanced knowledge) and get all this working, performance would be terrible.
Consider attaching some proven USB wireless chip or get Opi Zero 2 H3, which have at least a decent wireless chip and where this might be possible to achieve.
-
I also does not experience any screen tearing with our build. There was some in system on eMMC, one of the first Ayufan's builds.
45 minutes ago, pfeerick said:is it going to be possible to add a boot screen and possibly the charge indicator/power on reason screen, or is that likely to be in the too hard/unimportant and unnecessary frills basket?
Some small rework of u-boot will be needed for that but I guess its doable. But first I wanted to solve "going to suspend when lid is closed". I think it's some xfce related issue, since lid driver is present and working, manual suspend also work, ... -
It's from Xunlong, but boards are not yet ready for testing AFAIK.
-
1 minute ago, zador.blood.stained said:
IMO this needs to be discussed separately, not in this thread.
Than let's find out how many useful feedback do we actually get? If usually made an image and test - almost don't use them, but I use repository.Phase out process. Supported from me and S500 is the first on the list. I would only remove them from download section, where some note / link should be added - "deprecated / unsupported / .. or smth like that.
3rd point. Agree.
-
Mainline = experimental, no support. Network driver will be changed.
Armbian support feels like a bunch of parrots each time one of those questions from experimental area pops out
-
I uploaded images with most recent kernel (4.11.3) - one last check if it's any better. I am not sure we have any power and knowledge to deal with such weirdo / random problem. Perhaps folks at Freescale knows more about?
How about old / legacy kernel? Just to see if it's working there ...
-
Not exactly trivial, but you need to add something like this:
https://github.com/armbian/build/blob/master/patch/kernel/sun8i-dev/enable-codec-opi-2.patch
to board device tree which you can find in /boot/dtb ... decompile .dtb and back.
-
On board audio is most likely disabled in config (/boot/script.bin) since the board does not provide it by default.
-
2 hours ago, 447377 said:
The network is out of function even when I don't change anything at the kernel config while building the new image.
It looks like there is a bug / changed parameter in upstream mainline u-boot source code ... temporally workaround is to switch u-boot branch to previous, add: BOOTBRANCH="tag:v2017.03" to userpatches/lib.config and recompile.
Regarding your patch ... you need to fix it or find appropriate one.
-
12 hours ago, StuxNet said:
I thought armbian-config was going to be useable with the last update that went out?
Update hasn't been pushed out yet - too much problems and too little time.
-
4 minutes ago, ssuloev said:
But I got 99% feeling that is not an OS-issue...
We are 100% where is the problem.5 minutes ago, ssuloev said:I am new to this.
We do this every day for past few years. -
-
-
7 hours ago, d1dd1 said:
Did anyone try overlayfs feature recently?
In the latest nightlies, when I enable overlayfs on my Orange Pi Zero it works as expected, when I try to disable overlayfs again, the Zero does not boot up anymore.
It used to work, so this looks like a bug and need to be inspected. -
WIP targets might not be done to the level that they boot. In any case, support for this board is very minimal and there is no much interest or activity. I can only delete the board out of config to save us answering that we cant help at this stage.
Wrote on mobile -
3 minutes ago, tkaiser said:
providing them with the information they need at a certain point
Absolutely agree that we have room for optimisation here. Perhaps removing the whole welcome part and having just this at first login?
-
8 minutes ago, op1tjaap said:
Is there a way to avoid this? I don't need a dtb for a nanopi-m1, only for the OP1.
Clean your build environment. It's working fine for me.
Orange PI Zero Plus2 512mb - No Working Images (fixed problem)
in Allwinner sunxi
Posted
They are build automatically every day and no one knows if images works - we can't automate this kind of testing. We label images experimental, for developers - sometimes they work, sometimes don't ... until some developer invest his time, inspect and fix the problem.
We already started to talk about how we will solve this "daily building problem", since it produce much more problems than benefits. People simple does not read before download or does not understand what experimental means. Support questions regarding unfinished product (we are months away) are keep coming, even it's written everywhere that we don't provide any support for experimental and development builds. It's simply not possible.