Skip to content
View in the app

A better way to browse. Learn more.
Armbian Community Forums

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

v5.25

Igor
in Advanced users - Development

Featured Replies

Shall we start to finalise and prepare for images rebuild? Some new features were already documented, but there are some ongoing things and we are also preparing new download organisation, which could be included. 

 

- it looks like I manage to disable / merge little too much images, which needs to be built. @tkaiser was right :huh: I made a mistake, so please check .conf if I forgot something.

- beta builds. we can't check all images, but some should be enough to assume everything is o.k. ... Do we have a minimum set yet?

- I will try to enable beta testing protocol / call for testing within this build.

 

What else should be included / finished and pushed into this build? Shall we put some H3 mainline builds out? At least for: OPi PC+, Zero, ... ?

 

Is released due for 17.1. O.K.?

Shall we start to finalise and prepare for images rebuild? Some new features were already documented, but there are some ongoing things and we are also preparing new download organisation, which could be included. 

 

My concerns:

1. Wait for the mainline 4.9.1 to drop swconfig b53 patch for Lamobo-R1. If at least basic network configuration works on R1 with DSA, then the issue #511 will be resolved.

2. Is the firmware issue #484 resolved?

3. What is the status of M2+ legacy and mainline (issue #564)? If it works for you with and without network and/or HDMI, then it is solved, otherwise maybe it should be excluded from stable images for now?

4. It would be good to improve download pages as much as possible before the release: add kernel comparison tabs for mvebu, i.mx and all sunxi families; add "Known issues" tab (at least per $LINUXFAMILY, with a list of generic issues and board-specific issues like embedded wireless modules problems), add more text on nightly tabs to state that these are automated untested builds and no end user support is provided for them), ...

 

Shall we put some H3 mainline builds out? At least for: OPi PC+, Zero, ... ?

I would prefer to leave these as nightlies for now, but we can add nightlies for more boards that have good enough configurations, such as One, Zero, PC, ...

For 5.25, I suggest solving (issue #579) since it affects all H3 boards and offers a "bad first experience to Armbian" on boot.

@lvmc

After looking at GH issue #579 I found and applied @jernej's patch and it looks fine.

 

Answering your question - to disable video in u-boot you have to remove CONFIG_VIDEO from respective board defconfig, it should be enough.

 

@zador.blood.stained, so, if we build a new H3 image, the boot artifacts will be gone? Its the 1d38c5b patch right?

Good..  :)

  • Author

1. OK

2. Yes it works now, while cleaning the mess, as Thomas suggested, remain open.

3. Problems are only when something is on USB in all other cases I could not reproduce - when using a proper PSU. I suspect it has something to do with power stability. If some not so perfect source is used, board might not boot. There is nothing more to be done here.

4. I'll try to squeeze this into this release.

3. Problems are only when something is on USB in all other cases I could not reproduce - when using a proper PSU. I suspect it has something to do with power stability. If some not so perfect source is used, board might not boot. There is nothing more to be done here.

Then it's a hardware problem, GH issue should be closed and this mess should be present in the "Known issues" tab on the download page.

In my recent builds got this

Processing file /home/christos/armbian/lib/patch/kernel/sun8i-default/ov5640-enhanced-driver-with-vfe-drc-table-fix.patch
patch unexpectedly ends in middle of line

I build always with RT enabled (option 4) so don't know if this is the cause,

even though I'm not using the ov5640, just mentioning that FYI if you plan for a new release.

5.24 is the current version for the nightly and user-built images, so nightly and manually built packages have higher version than stable release.

 

So 5.24 will never be a release number ?

 

I was only speaking of the Release_Changelog.md file content, maybe something like that could be added in this file to avoid surprising the readers:

 

v5.24

 

- not released, used for the nightly or user-built images

 

just my 2 cts...

@lex, can you take a look at it?

 

In my recent builds got this

Processing file /home/christos/armbian/lib/patch/kernel/sun8i-default/ov5640-enhanced-driver-with-vfe-drc-table-fix.patch
patch unexpectedly ends in middle of line

I build always with RT enabled (option 4) so don't know if this is the cause,

even though I'm not using the ov5640, just mentioning that FYI if you plan for a new release.

Guest
This topic is now closed to further replies.
Go to topic listing

Account

Navigation

Search

Search

Configure browser push notifications
Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.