Hijax Posted July 28, 2019 Author Share Posted July 28, 2019 Hi, few days delay as I had to do also other things Anyway... On 7/23/2019 at 10:17 PM, guidol said: Latest Kernel are only 5.2 or also 5.1? By latest I meant respective versions of default NOT dev branches. Thus: Pine H64 - branch next results in kernel 4.19.59 Rock64 - branch default results in kernel 4.4.184 Both had problems to boot. PineH64 did not start kernel at all while Rock64 has some crashes during kernel initialization resulting in no /bin/init. As I had to progress somehow I decided to switch to dev branch. After that numbering changes to: Pine H64 - kernel 5.2.2 Rock64 - kernel 5.2.0 Using dev branch I have successfuly build minimal images for those two boards using Ubuntu Bionic as base. Both boards works fine using mini images. Only one issue I have noted: pineh64:~$ /etc/update-motd.d/10-armbian-header error: could not load font standard Welcome to Ubuntu Bionic with Armbian Linux 5.2.2-sunxi64 This is because there is no standard font for toilet usage. https://packages.ubuntu.com/xenial/all/toilet-fonts/filelist Standard font is available for figlet. But figlet is not installed and not in use by 10-armbian-header script. Shall other available be used instead, like mono12? Link to comment Share on other sites More sharing options...
Igor Posted July 28, 2019 Share Posted July 28, 2019 3 hours ago, Hijax said: Standard font is available for figlet. But figlet is not installed and not in use by 10-armbian-header script. https://github.com/armbian/build/commit/2ce1552936b01a6491bffd3a14fb011b07efc467 Worth to waste 756kb for nicer fonts Link to comment Share on other sites More sharing options...
Hijax Posted August 8, 2019 Author Share Posted August 8, 2019 As for now I have not faced any issues with my SBCs and mini images. So my question is : what is next step before incorporating those changes into master branch ? Link to comment Share on other sites More sharing options...
Igor Posted August 8, 2019 Share Posted August 8, 2019 6 hours ago, Hijax said: As for now I have not faced any issues with my SBCs and mini images. So my question is : what is next step before incorporating those changes into master branch ? - (unsupported) Jessie is broken and has to be removed in a separate config - lsb_release has to be checked if its 100% compatible with a Python version - someone that is not me has to tick "approved" on PR Since we are replacing lsb_release package at least one upgrade test from current base should be done. Link to comment Share on other sites More sharing options...
Hijax Posted August 8, 2019 Author Share Posted August 8, 2019 Ok. Then next week I will spend some time in checking lsb_release Link to comment Share on other sites More sharing options...
Hijax Posted August 16, 2019 Author Share Posted August 16, 2019 On 8/8/2019 at 3:45 PM, Igor said: - (unsupported) Jessie is broken and has to be removed in a separate config Jessie is not supported on Arm64 architecture. Is it really needed to continue from here? On 8/8/2019 at 3:45 PM, Igor said: - lsb_release has to be checked if its 100% compatible with a Python version Current shell script conforms to Python version but with no lsb_module analysis. Frankly speaking I do believe current shell is good enough. Link to comment Share on other sites More sharing options...
Igor Posted August 16, 2019 Share Posted August 16, 2019 13 minutes ago, Hijax said: Jessie is not supported on Arm64 architecture. Is it really needed to continue from here? Jessie is obsolete in all counts if you ask me ... we agreed to clean it out some time ago - This will be done in a separate PR. That's all. 15 minutes ago, Hijax said: Current shell script conforms to Python version but with no lsb_module analysis. Frankly speaking I do believe current shell is good enough. Agree. Most critical parts were checked, also for upgrade. I think this is good enough. Merging ... Link to comment Share on other sites More sharing options...
Recommended Posts