Werner
-
Posts
4474 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by Werner
-
-
15 hours ago, Igor said:
Plus adding this plugin
https://invisioncommunity.com/files/file/9042-auto-lock-topics/
to entire Technical support question with locking everything that older than 90days?
This would make sense in a combination with various restriction for creating a new topics (adding armbianmonitor -u).Are there that many older topics that getting exhumed? Not sure if possible with Invision without addon, I know that worked in vB years ago but what about simply limiting the number of visible topics by age up to 90 days as default?
-
1 hour ago, Igor said:
That's a good idea. I'll check if that is possible.I am torn about this. For various you may not be able to generate such a link. Like network issues (you still get the output but not the special link), I/O issues or boot issues.
-
14 hours ago, zador.blood.stained said:
Not sure about this.
- the second tab on Github project is called "Issues", not "Discussions" or "all stuff", and it has "Open"/"Closed" statuses more suitable for tracking actual bugs/issues than discussing build script usage
- this would make it impossible to easily move framework related discussions from the forum to the right place
I think we should not take take that with a pinch of salt just because it says "Issues". Don't get me wrong, I totally get your point, but if the mix of issues with discussions is either here in the forums (just take a look over there) or at Github issues does not make a big difference. At github discussions can be labeled as those at least as every new topic there needs a review in first place.
What about this as a compromise between both:
- Rename "Armbian build framework" to "Armbian build framework - Discussions" and
- create another subforums Armbian build framework - Issues" which redirects to Github
At the bottom line there is no perfect solution for this because there are always and always will be users which are either inexperienced, creating topics at the wrong place by accident or are just trolls. Unfortunately there is no other way than cleaning up behind. That's the curse of all forum operators.
-
1 hour ago, Igor said:
If this feature is not strictly used, it's pointless to have it there.
Agree. In this sense it might be worth to think about merging "Armbian build framework" and redirect the rest to the "Technical support area" or "Peer to Peer" if it has nothing to do with Armbian.
Another option to limit pressure on support is by enforcing forum payment system. System is here, it's highly integrated in forum ... and it works. Not exactly to charge for support but to return a pressure back.Well I'd guess that using prefixes can also be enforced by the system. So you have to choose on topic creation.
QuoteAnd someone (which is not me
) would have to manually resolve prefixes for at least last two pages of topics.
Agreed. Annoying work. I already did stuff like that many years ago...
QuoteIn this sense it might be worth to think about merging "Armbian build framework" and redirect the rest to the "Technical support area" or "Peer to Peer" if it has nothing to do with Armbian.
What about simply redirecting "Armbian build framework" to https://github.com/armbian/build as all stuff regarding the building process, script and so on is discussed (or should be at least) discussed there?
-
56 minutes ago, chwe said:
could we 'switch' the behavior as well? E.g. default is mainline kernel and subforum is outdated 3.4 kernel which is only available for H3 anyway? Some kind force that people should move to mainline..
Like.
As an alternating suggestion is to merge mainline and legacy kernel forums and use pre-defined thread prefixes like [Legacy] or [Mainline].
Though two problems: I do not know if possible technically as I never managed Invision forums. vBulletin and WBB only. The second issue I see is more generic as especially new users may not know the difference between legacy and mainline. I did not know by myself a year or two before. At the moment no idea how to solve this. Maybe this is not even a problem as big as I may think.
18 hours ago, Igor said:Any objections to merge/move H5 and A64 from https://forum.armbian.com/forum/18-allwinner-a64-h5-h6/ to https://forum.armbian.com/forum/27-mainline-kernel/ ?
BeforeAllwinner A64, H5 & H6
Pine64, H64, Pinebook, Olimex Teres, Olinuxino A64, Orange Pi PC2, Zero+ 2 H5, Prime, Win; NanoPi Neo 2, Neo+ 2, M1 Plus 2, FriendlyElec K1+
AfterAllwinner H6
Pine H64, Orange Pi One +, Lite2
Are A64 and H5 stable enough to be removed from development?
-
active = powered by external power source, to say wall adapter
-
You can send a PR with your changes to the kernel config here: https://github.com/armbian/build
-
I have an OrangePi zero as DNS server utilizing Pihole and Armbian, Dietpi earlier until they dropped their support for OrangePi boards, as base for almost two years now and running great. Also this board is dirt cheap and way enough for this application.
The WiFi on board is crappy but as long as you wire it with copper it runs fine.
-
1 hour ago, mirko said:
I made today the update from 5.60 to 5.70 and I do not have access to ssh. I do not have usb - ttl or hdmi (orange pi zero) so how can I fix ssh?
Either get an USB TTL adapter which is very useful anyways and is very cheap or put the SD card in your pc, chroot into the fs and fix it there like for example as suggested by downgrading particular packages.
-
Could be difficult with legacy kernel. Assuming it is 3.4.113...
-
10 minutes ago, Igor said:
I bought one of these, looking exactly the same, from a different dealer on Amazon, however I did not come with MT7601U but an unsupported Realtek chip. You can take the risk buying this and maybe you even get what it is advertised.
Edit: Related:
-
Yes, I think this is the way to go.
armbian-config has nothing to do with the build system. It is a independent tool to set various system values, switch/freeze kernel version, and so on within a running Armbian system. Sorry for confusion.
-
Why not simply switching to 4.14..81?
-
Use armbian-config and switch to dev (or beta, not sure) branch. This ships 4.19 kernel. Do you miss anything special within 4.14? This is a maintained long term kernel btw.
-
After you run
compile.sh
the first time a
userpatchesdirectory is created where you can place own patches.
Until now the only kernel known to work is 4.18.0-rc7.
QuoteA guy met this error，link:https://forum.armbian.com/topic/9131-h6-after-apt-upgrade/. I can not find a way to switch kernel version to 4.18.0-rc7
I do not know if pure Debian packages with this specific kernel image still existing somewhere, but AFAIK are the latest precompiled images for OPi 1+ and Lite2 are still shipped with this kernel. So if you have one of these boards you may start over and freeze the kernel from being upgraded using
armbian-config
-
Images [edit: for boards with Allwinner H6 SoC] with kernel versions above 4.18.0-rc7 are unbootable anyways AFAIK. But feel free to update your kernel within the OS like Igor said. Please let me know if it still boots.
-
I suggest to not bother too much with the onboard WiFi as it is not very good. A better and more reliable solution would be to get a supported USB WiFi dongle.
-
Disconnect power
-
Known issue.
Go back to 4.18.0-rc7 and freeze kernel until solved or build your own kernel with all the stuff needed and disable on board Ethernet and use USB-Ethernet adapter.
Interesting to know though that other boards are affected too.
-
On 12/21/2018 at 9:10 AM, Vincen said:
Interesting bug too: after doing system updates with apt update/upgrade, you can never reboot the system (RED led on board at boot !!).
The reason for this seems to be a regression or a missing commit from @Icenowy sources (https://github.com/Icenowy/linux/commits/h6-integrate-2-ugly) which has not made the jump into mainline (yet).
Therefore you either have to use the 4.18.0-rc7 kernel image (which I run two OPi 1+ perfectly fine on right now) or temporarily disable dwmac like @martinayotte did as workaround to successfully boot up the board with a kernel built from newer sources (and use a USB-Ethernet adapter).
For confirmation you can utilize a UART serial adapter to check the kernel boot for errors like "sun8i_dwmac_probe+0x164/0x518".
As stated mainline support has still a long way to go to better support the H6 SoC. Do not just discard the board. Just put it on the shelf and it may run fine in a couple of month.
-
If an image was generated successfully there is usually no need for cleanup by users hand.
-
-
11 minutes ago, martinayotte said:
On my side, I kept my previous OPiOne+ build done with h6-integrate-2-ugly branch.
I didn't investigate further about Mainline 4.18.10 since Icenowy suggested to check with 4.19.y, but I didn't take the time to check ...
Did just a quick look at 4.19 but did not come very far... I leave it that way as well and wait for @Igor to push sunxi64 to 4.19. Thank you anyways.
-
@martinayotte Did you find a solution for the unbootable OPi 1+ yet?
Improve 'Support over Forum' situation
in Off-topic
Posted
Looking decent. Nothing odd so far.
As from my experience topics usually are bumped actively during the first days till maybe weeks, but not over month. The situation here might be different though.