-
Posts
14431 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by Igor
-
-
6 minutes ago, gprovost said:
What's your opinion on this approach
Can check in a day or two. Now have family/life troubles. Images are done:
https://dl.armbian.com/helios4/Debian_stretch_next.7z.torrent
https://dl.armbian.com/helios4/Ubuntu_bionic_next.7z.torrent -
5 hours ago, vtrandal said:
And now there is no nodm?
The reason behind removing nodm is we are getting the same with lightdm (autologin) and have less complications. nodm also have some bugs which are here for years and nobody care to fix them. Our resources are far too small to deal with bugs in 3rd party packages.
Current desktop builds still have nodm, while in next major update, it is gone. While the functionality remain unchanged. -
I would like to switch download for upload speed
It's part of the package which is not sold anymore ... cca. 40 EUR monthly.
-
1 minute ago, gprovost said:
The problem is upgrade from 5.67 and prior to version 5.7x. So if you publish updated packages the issue will still be there. Please don't publish any new packages till our next PR.
OK, images only then. -
1 hour ago, gprovost said:
Any chance you could build and publish a 5.70 image, and remove all the previous image release on armbian download page ? Or instead you could copy over our 5.68.
Rebuilding images is the easiest part, its fully automated and it was ignited. I will also push updated packages to the repository but I don't have time to check. I hope problems are solved. -
7 minutes ago, berobispo said:
And how do I fix the network/downgrade the kernel? The migration is not finished yet, so downloading new image etc. wouldn't be a big problem. Should I do just that?
If changing cables didn't help ... add some wireless module and conduct upgrade ... or just download latest image, yes. -
I also experience this sometimes - changing cables helped. Try that.
On a side, we just downgrade kernel from 4.19.y to 4.14.y due to other problems. Now it's the same as stock. Fix network, update and upgrade. -
1 hour ago, ap17 said:
I do not use OS Armbian and don't know what Armbian-5.70 is.
This is Armbian forum so one would assume you use kernel with our patches.
1 hour ago, ap17 said:and he replies me that this solved his problem.
Can we also be a part of this joy? -
New features and restrictions for "Technical support" area:
1. Validating users, those who just register are unable to reply to topics. They are forced to open a new topic.
2. All users have to accept conditions (cookie last one day): 1. Call to use docs and search 2. Call to support us 3. Call to provide info
3. Each time a topic is created, you need to add: armbianmonitor and accepty several conditions4. Auto lock topics is now set to 365 days, pinned and featured are exempt, ... and it will take a few days before locking will be completed.
-
3 hours ago, integros said:
Here is the serial console log
Fixed by removing broken files from repository:
pool/main/l/linux-bionic-root-next-helios4/linux-bionic-root-next-helios4_5.70_armhf.deb
pool/main/l/linux-stretch-root-next-helios4/linux-stretch-root-next-helios4_5.70_armhf.deb -
3 minutes ago, Pottwal said:
Development: not needed
We wait that someone sort out the configs https://github.com/armbian/build/issues/1227
-
57 minutes ago, mo123 said:
Can you make a Rk3328-tv_Ubuntu_bionic_default_desktop image that uses a 4.4.167 kernel like the default Armbian Rock64 image with working media script also included?
We are already working several months to adopt build system to be ready for such integration. Since there is very little help and huge demand from the community side, we are moving very slow. -
Moved to Peer to peer technical support forum.
-
1 hour ago, GB_linux said:
documentation link??? I didn't get you
Put "How to freeze your filesystem" to the search above. -
10 minutes ago, integros said:
Tried to update via armbian-config, but as soon as I rebooted the card/system was no longer recognised.
This should not happen. Can you explain exactly what you did and provide serial console logs. -
2 minutes ago, FanDjango said:
I have the feeling that my only error was to stay with Jessie so long. Similarly, another error some days ago was to upgrade from 4.14 to 4.19. All else is a direct result of those two bad decisions. I am not aware of any other errors currently.
4.19.y on NEXT branch seems to be a mistake and I am preparing a downgrade. Back to 4.14.y ... too many troubles.
3 minutes ago, FanDjango said:So how long will Armbian Stretch be viable or should I go for Bionic, to have another years peace and quiet, in your opinion. Just opinion and advice, I won't nail you to it.
That is Debian people decision. We are good for another year since we will not move to next stable base right away. If you want to run OMV, you have to forget about Bionic. It will not work there. At least not without severe hacking.
-
5 minutes ago, gurabli said:
except for the DVB-T/C stick
We don't support 3rd party hardware.5 minutes ago, gurabli said:how could I apply this patch to an of the available releases of Armbian? This patch
https://www.armbian.com/get-involved5 minutes ago, gurabli said:I wonder if I can downgrade to an older kernel, like 4.4.0 for example, where everything works perfectly? If yes, how?
You can't. Support for H5 chip starts with 4.14.y -
16 minutes ago, Liontek1985 said:
very helpful
We don't have capacity to deal with "you" in this number. Simple as that.16 minutes ago, Liontek1985 said:good community
Use correct part of the forums - community forums. -
10 minutes ago, Liontek1985 said:
i have readed and now my Board run on Armbian Jessie (Retrorangepi 4.2)
We don't support 3rd party builds. https://docs.armbian.com/User-Guide_Getting-Started/#how-to-check-download-authenticity nor this board: https://www.armbian.com/tritium-h3/Moving to community section.
-
10 minutes ago, FanDjango said:
in a quick and dirty fashion
JepAnd in such cases, support assitance can't do much. We only try to fix our errors, not yours
10 minutes ago, FanDjango said:I don't quite understand the paranoia
It's not paranoia but switching to "I don't care" mode. We have do draw a line because this technical support is most expensive and most abused part of the project.11 minutes ago, FanDjango said:But if supported Armbian stuff can just dissappear suddenly
We can't possibly cover Debian Jessie upstream issues. That's why. -
2 hours ago, ant333 said:
Same on OrangePi R1 after update to ARMBIAN 5.70.
Anybody found solution?
Workaround is by switching to kernel 4.14.y and freeze kernel upgrades. armbian-config -> system -
4 minutes ago, PlayingMuted said:
I'll try the other way around. I have had success switching the interfaces, but the rtl8814au seems to have some rate limiting as an access point.
Since you have 8814AU. Is that adaptor working within armbian-config? Can you set AP with it? -
33 minutes ago, PlayingMuted said:
I've been trying to get the card to work as a hotspot via armbian-config without success.
That method works if drivers for this chip are capable of running AP. Standard way. No idea if this chip works at all. -
33 minutes ago, FanDjango said:
Image origin: https://www.armbian.com/download
I am sorry but I could not find any Debian Jessie image for the download ...Official OMV Stretch image with installed all updates = kernel switching without problems or code modifications
Armbian Debian Stretch with installed all updates = kernel switching without problems or code modifications
When you switch kernel, you need to freeze it otherwise it will be upgraded at next apt update / upgrade.
Helios4 Support
in Marvell mvebu
Posted
Do that - congrat!