-
Posts
14584 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by Igor
-
-
Bananapi M1+
Upgrade from 5.24 / 4.7.9 -> 5.30 / 4.11.4: no problems with network. Tested with 100 / 1000Mbit switch.
-
5 minutes ago, wsian said:
Bananapi armbian 5.27 mainline upgrade to 5.30. Cannot log in remotely from putty.. When connect to hdmi monitor, it boot up normally and can log in. Everything seems ok but no response when attempt to og in remotely (putty). Very strange.
Most likely u-boot configuration which initialised network is broken for Bananapi. Still checking if this is it. U-boot upgrade has been removed until this is not resolved. -
3 minutes ago, tahaea1 said:
I don't really remember the kernel version. Armbian version was 5.25 or 5.24. Clean image as in what? I was using 5.25 for about 2 months I think? was apt updating regularly and it updated to 5.30 today.
OK. I'll try to reproduce.In the mean time, you can try to flash (downgrade) u-boot from http://apt.armbian.com/pool/main/l/linux-u-boot-bananapi-default/linux-u-boot-bananapi_5.25_armhf.deb to see if that helps. Extract u-boot-sunxi-with-spl.bin and write to SD card:
dd if=u-boot-sunxi-with-spl.bin of=/dev/yoursdcard bs=1024 seek=8 status=noxfer -
4 minutes ago, tahaea1 said:
Banana Pi Jessie mainline
upgraded with apt-get
using usb hdd as root
Which kernel version and from which Armbian version you made update? Did you start from clean image? You have to tell me everything! btw. Super Pi is not supported even I am almost sure it's exactly the same as Banana Pi ... I never saw one of those ... some minor changes can lead to improper Ethernet initialisation. I also need to wait for others to report - on supported boards. -
25 minutes ago, tahaea1 said:
Same problem on SuperPi. Can get console with UART but get no networking at all.
Which image? -
49 minutes ago, nihilista said:
Updated my bananapi pro to from 5.30 minutes ago...but now it doesnt boot ;-(
Any possibility to get my system back without setting up completely new? Never had this with all update before.....
Everything is solvable ... but we need more information to help. It might be a problem with u-boot. From where you did upgrade? -
1 hour ago, mihai.aldea said:
No updates yet? Does that means that we can't use the generic DVB-T tuners (eg. Astrometa ID 15f4:0131) with 3.4.113?
Most of developers are dealing with mainline kernel, which is slowly emerging / getting ready on H3 devices too. There you have more chances for such hardware to work. I am using Nanopi neo for my tvheadend with 4.10.x - no problems:Spoiler_ _ ____ _ _ _ | \ | | __ _ _ __ ___ | _ \(_) | \ | | ___ ___ | \| |/ _` | '_ \ / _ \| |_) | | | \| |/ _ \/ _ \ | |\ | (_| | | | | (_) | __/| | | |\ | __/ (_) | |_| \_|\__,_|_| |_|\___/|_| |_| |_| \_|\___|\___/ Welcome to ARMBIAN 5.26 stable Debian GNU/Linux 8 (jessie) 4.10.0-sun8i System load: 0.19 Up time: 34 days Memory usage: 28 % of 243Mb IP: xxxxxxxxxxxxxx CPU temp: 32°C Usage of /: 19% of 7.2G
It's still in development, so you are on your own. -
@tkaiser & anyone else -> text at download pages comes from here: https://github.com/armbian/documentation/commit/10c08d02fbd67c9cf79e0e7fe8ff4d0ee2da3b9e
Feel free to alter - updated auto in matter of minutes.
-
5 hours ago, divis1969 said:
Can it be fixed?
M3 is in WIP / "work in (no) progress" stage - "fixing" means months of work with resources we don't have. Some limited (server usage) version of image might become available in few months - with mainline kernel only. Check A83T http://linux-sunxi.org/Linux_mainlining_effort
-
1 hour ago, rom said:
Is it an hardware limit
Yes, limited within firmware. Can't do it. -
-
-
Can confirm only for Pinebook. No other Pine around.
Wrote on mobile -
1 hour ago, KuDeSnik33ra said:
Can some one help me, please, clarify
There is no support in legacy kernel for overlayroot because kernel is too old for this function, while mainline kernel is not on the (end user) level for using it. https://forum.armbian.com/index.php?/topic/4239-opi-zero-mac-address-issue-on-mainline-kernel/&do=findComment&comment=32623 -
Quote
To conserve resources we could rebuild packages daily but rebuild nightly images only once a week, and we could significantly cut down the number of nightlies.
OK, once per week and interessant only. I'll clear them out during this week. Will also push 5.30 updated images out.QuoteWe can leave this part as is - third parties are fully responsible for providing support to their users, but we can accept requests like adding options to kernel configuration since this will be beneficial to Armbian users too.
Fine with me.
QuoteAnd creating separate lists for each group IMO is the best way to go, adding switches like "show WIP" and "show obsolete" and mixing stable boards with everything else will create unneeded confusion and complication.
I made a third and I hope last adjustements. Now each one has it's own page, accessible from menu, below "Download". In /download, we only have stable, nothing else. I was only thinking to add links from there to WIP and deprecated section? Also some more explanation needs to be added to WIP and deprecated.
QuoteI am against adding any info for the hardware that we don't plan to support anytime soon. Who will maintain those lists and how?
Specific is to big waste of time for us ... no, perhaps some general infomation that users will
understandget some ideas / hints, why we don't support just every board on the market and that shitty boards exits and there is nothing much we can do about. -
Steps from 2015 might not work today ... btw. Why don't you use our script? It works out of the box. I think it should work also with two partitions.
-
13 minutes ago, op1tjaap said:
Would like to solve this because it would give me the freedom to compile a development kernel of my choise.
If you are using our build scrpit - you already can do that - just use the packaging adjustements we made. And those you did, they look o.k. to me. Well, the kernel branch you are using, might not be bootable? Try first with some stable branch, "known to work kernel". 4.12 and sun8i doesn't look close to fully stable branch. -
7 minutes ago, Vladimir Gamalian said:
lsusb did't show any devices but two hubs.
Well, as I said. You have to reconfigure header functions to your need. It'a not a job of Armbian to do so. Somebody else might have other needs and they will say "why I2C is not working out of the box?" or similar ... If you are using modern kernel, we use overlays ... check docs.armbian.com for manipulation those features. -
27 minutes ago, Vladimir Gamalian said:
it is armbian related problem
Have you check our stable build? Missing features in WIP images is normal situation.
Edit: disabled USB on header can be considered normal. It's up to you to reconfigure board upon your needs.
-
21 minutes ago, op1tjaap said:
This means that things maybe go wrong because of this.....
Exactly. This is a patch which adjust / fix Debian packaging process. Debug starts here ... and also it might be related to CONFIG_LOCALVERSION_AUTO kernel config.
-
10 hours ago, t-bob said:
then it's OK so i expect the issue is in armbian-firmware
Nightly / WIP / preview / development firmware (must) have bugs, otherwise we would call it "stable"
We provide those builds with purpose of bug hunting and since people expect that they should work (before job is done), we will stop providing them. We waste a lot of time explaining, that it's normal that things breaks, than fixing an actual problem. I made quick check, but can't find where is the problem.
Last time I was testing this feature, it worked as expected - from armbian-config, which does this: https://github.com/armbian/config/blob/dev/debian-config#L601-L615 when issuing "freeze kernel".
-
Until two weeks ago, we also didn't have bootlogo on Pinebook. You probably need one of the patch from here:
https://github.com/armbian/build/tree/master/patch/u-boot/u-boot-pine64-default
This update is not yet present in repository.
-
Installing KODI is not trivial on any general OS / Debian / Ubuntu, not even on x86 machine. Second, you try to install it on modern 4.x kernel, which arrived on XU4 months ago and it's not matured. I have no idea if this is already possible. Third. Armbian is not focused to provide multimedia / closed source drivers by default, while I think it should be possible to build KODI on top of Armbian. In any case, start rather with old legacy kernel, check (at hardkernel forum) which additional libraries are needed and than you have much better chances to succeed,
-
When "include beta and deprecated images" is checked, Why is my board not supported? link pop's out and that will be relinked to github or rendered here: https://www.armbian.com/unsupported/
That's really all for today. Have to do some barbecue


No network after upgrade to 5.30
in Allwinner sunxi
Posted
The more I test, the less I know
This test image works fine on M1+, while network doesn't come up (properly) on: M1, PRO and R1 