Igor
-
Posts
14514 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by Igor
-
-
1 hour ago, hrip6 said:
Secondly, did you see how strong the words are?
What about pure coincidence? To clarify: I was absent / travelling / been a lot of time off grid since Friday until yesterday. In general for weekends those who works daily on the project usually divert free time to families and others, not for volunteer work, which is the case here. Response time, which you are exposing as our "failed duty" is not realistic under any circumstances, with bold text or without. Once again, even people who pay for the time, does not demand nor expect this quick response time. Here is volunteer service and attitude is a key to trigger someone's interest to focus and contribute to the problem. Sometimes this is not enough - either we are too busy or the matter is just out of the zone, where we can help. If you address message to general forum public - there is nothing else to do but wait and bring this up after some time passed. Not the next day, if there is no response. Impatience drives people away.
I am glad you managed to fix the issue. -
I think you need to adjust perspecitve. There are much much more questions / issues, than core group can handle. Next. There is no such thing as demand for answer for something that might be or might not be related to our work, which you are using for free. Here we are talking about changed system, which goes under "not our work - no support". It's almost impossible to help in such cases without investing hours into it.
If some of your contributions were overlooked I only can say sorry. It happens with the same reason. The project is big.
My usual response for professional support, for people that help paying my bills is between week and two weeks. If you need answers faster, you need to use search. Knowledge is there and you just need to put some effort in finding it.
-
I would prefer to go with no locker - its kind of pointless to lock console if we dont use display manager ... if i understand this properly?
Wrote on mobile -
I was trying hard to replicate your problem on my Banana PRO but without success.
1. I started with the same image - from download section
2. My hardware is Banana PRO
3. I have reliable PSU, quality cable, good router, good cables and I used some older SD card. Deliberately.
4. apt update + upgrade
5. installed apache, mail, dovecot, mysql, ...
6. rebooted few times ...
Logs: http://sprunge.us/UcHO
I also have those errors regarding brfcmac on console, but they are irrelevant.
The only problem - which should not affect - is small bug in ramlog. It's fixed upstream, but not yet in this version ... nginx does not start if there is no log directory (/var/log/nginx) - for apache I am not sure. After recreating it works fine.
-
"no action" when lid is closed might be related to this? After this mod "screen off" function works, while suspend is no go. Also it does not differentiate when on battery or AC. Brightness can be adjusted manually now, but not by power condition BAT/AC. I guess this power management needs some extra touch
-
9 hours ago, sghazagh said:
But the way Armbian works is different than official setup
Our root system is simple to maintain, matured, clean - in any way better than official creations. I am not sure anyone wants to analyse, how Asus glue their images together. They failed on board design and generally all board makers images proved to be bad quality. We only peek for some special thing, but here I don't see any reason.We just started to add wireless and Bluetooth support and I am not sure it's already fully done. ASUS still haven't deliver board samples, which means not many people can work on this.
6 hours ago, sghazagh said:in above image
You have to contact image creators (Asus or whoever). There is a reason why we don't alter stock Debian / Ubuntu much, since there is plenty of complexity already and time is wasted on irrelevant issues. -
I assume you are using self built image / kernel? If this is so ... just install older "u-boot 5.25 next" from apt.armbian.com and you should be fine. There is a wrong configuration for network (gmac), which does not work properly. Wireless modules is o.k. and it should work even it throws out some errors / warnings.
-
Are you compiling with our script or on your own? Which kernel - legacy or development?
Generic approach to alter kernel configuration - check config files and create a pull request for what you need to be added:
https://github.com/armbian/build/tree/master/config/kernel
For orangepi pc, you need to alter sun8i-default and sun8i-dev
If pull request is accepted, in less than 24h beta repository will have updated kernel. -
You have new chip, while firmware does not exists yet in last stable firmware package. Next update should fix this, but one of current workaround is to manually copy those files: https://github.com/armbian/build/tree/master/bin/firmware-overlay/ap6212 to your /lib/firmware/ap6212 and reboot. Perhaps renaming nvram.txt to config.txt might be needed.
-
21 hours ago, Rafael Wilmar Hoffmann said:
armbian does not support the driver we need (TV adapter)
You mean composite TV out? It's supported by default - check forum for advanced adjustment if needed. If you are talking about some 3rd party TV tuners, stock kernel will have only less support than ours. Even better support in TV tuner area you will achieve with modern kernels, but they are still in development stage ... "use at your own risk". -
There is no way to run Unity desktop on those boards due to video driver limitations while you should be able to run mate, xfce, lxde or similar.
-
IIRC some M2+ board revisions had defective WiFi chip or chip which needed special attention. But before inventing the wheel again, please supply some logs with armbianmonitor -u
-
That patch can't directly be used on mainline kernel, while it can most likely be applied on our old 3.4.113 kernel ... Unfortunately we don't have this hardware to test but luckily I am meeting Olimex people this weekend and will brought up this issue.
-
1 hour ago, Wild Farmer said:
latest nightly build.
Thank you for reporting. Problem will be solved in one of next developer preview (nightly) upgrades. You can also step up and join development efforts - https://docs.armbian.com/Process_Contribute/ and help fix troubles when they arise. -
11 hours ago, Amit Feldman said:
Not working for me either (cubietruck), got ct-lubuntu-server-nand-v2.0 on the nand and then I was only able to select boot from SD and system on SATA, other options were not displayed.
Anyone got it working?
NAND install works only on legacy kernel versions. -
43 minutes ago, aishen said:
But after reading and trying it didn't work. Apparently you seem to think that everything that is written works for everyone which is not the case.
Stable images are tested - we are not wasting your time.
If you have Orange Pi Zero:
1. Download https://dl.armbian.com/orangepizero/Ubuntu_xenial_default.7z2. Burn to SD and boot
3. Login via serial or SSH and execute: nmtui-connect This connects you to wireless network in no time.
If you have some other board, download appropriate image and sends us logs if things doesn't work that we can improve Armbian (and it's derivates
If you don't use Armbian or wrong Armbian image, manual might not work.
Anyone can try and confirm this - you are doing something wrong.
QuoteDietpi is neatly more adapted to orangepizero for beginner and easy installation.
Their "more" adaptation of Orangepizero is exactly zero.
-
10 minutes ago, aishen said:
But I couldn't start wireless wifi network.
It's really that hard to put "wireless" into docs search? This is first and correct hit:
https://docs.armbian.com/User-Guide_Getting-Started/#how-to-connect-to-wireless
BTW. Next build comes with armbian-config, where you will be able to config directly from menu ... and learn nothing.
-
Dietpi is made from Armbian Debian server. Low level (kernel / u-boot) bugs are the same, while they certainly created new bugs in user space level due to hard modifications. Modifications also raises security risks. "unimportant" packages were removed - which actually transfer normal build into half network install - and this stripped down image provide them a reason to claim a label "lightweight" which is not true.
You need to run Armbian Debian or Ubuntu to be able to make use of such low level utilities.
-
1 hour ago, aishen said:
I have a small sdcard on an orange pi zero and I would like just to keep it for booting,
https://docs.armbian.com/User-Guide_Getting-Started/#how-to-install-to-emmc-nand-sata-usb
-
2 hours ago, DEHN.IO said:
Trying to boot from MMC1MMC: no card present
https://forum.armbian.com/index.php?/topic/3945-mmc-no-card-present-error-on-allwinner-boards/
-
As you can see there is no release date yet. This means update text and update itself is not ready yet.
-
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. -
-
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 Win+ - apt upgrade issue
in Allwinner sunxi
Posted
You want to use those images? Don't. If you are experimenting, if you are using it for no purpose, than it's o.k. You just found one of many bugs, which are in automated built experimental images. The bug might be new, might be already solved in the mean time or some workaround exists - today's or tomorrow update might fix this or it might take more time. Those images comes as is.
Hint for future: if you find some experimental image working, go to armbian-config and "freeze kernel and BSP upgrades" and your system won't receive kernel upgrades when doing "apt upgrade" until you unfreeze it again.