Jeremiah Cornelius

Looks like the source of the conflict is here:
 
&uart0 { ... pinctrl-0 = <&uart0_xfer>; // RK_PC0 is rx and RK_PC1 is tx ... }; &uart1 { ... bluetooth { ... device-wake-gpios = <&gpio2 RK_PC1 GPIO_ACTIVE_HIGH>; host-wake-gpios = <&gpio2 RK_PC0 GPIO_ACTIVE_HIGH>; shutdown-gpios = <&gpio2 RK_PB7 GPIO_ACTIVE_HIGH>; pinctrl-names = "default"; pinctrl-0 = <&bt_host_wake_l &bt_wake_l &bt_enable_h>; // RK_PB4 and RK_PC1 ... }; };
So, indeed, bluetooth device is conflicting with uart0

Hey @Jeremiah Cornelius great stuff.
I've been working on removing the ODROID-specific cruft from the G12B family in armbian/build.
That is almost done now (some damned patches are still in the way) so I could start work on adding VIM3 officially.
Are you on Armbian's Discord? Catch me there in #amlogic as 'rpardini'
We could surely benefit from each other's work (and I from the fact you have a VIM3 to test on ;-) 
Let me know
 

Yeah, don't bring boards on vacation is a decent policy, though often violated I hear.
 
I realized after posting that we're on a tight schedule (Armbian 21.08 release) so I jumped the gun and sent a very basic PR, but is 100% untested.
It's Armbian's default meson64 kernel, mainline u-boot 2021.04 with vim3 default config, and the a311d DTB from mainline kernel, and that's it.
It could benefit from your work (asound file, any gpu/X11 settings, etc) but should otherwise be very similar to the N2 image I understand you based off.
If it boots, it's a win already.
 
Enjoy your vacations!
 
 

Really thanks for this. It gives me a lot more to go on.
I'll do more work in the next day or so, and be back with some updates - HOPEFULLY with some guidance to offer others, if successful!
 
The ""${SDCARD}"/root/.not_logged_in_yet" is a GREAT hint!
It's the opposite of touching a flag in the file system, so of course finding it in a configured system is impossible! I'd have taken a long time, before I got to it in the script sources.
 
— Jeremiah

@Jeremiah Cornelius - for your lightdm issue, maybe give the slick greeter for lightdm a try - it fixed my problems with non working lightdm on 32bit arm - might be worth a try
 
best wishes and good luck - hexdump

Hi,
i'm using a Raspad tablet-like device with a aml-s905x-cc inside and i'm experimenting some mobile interface that i can use with the touchscreen, but also with mouse and keyboard. I'm simply curious about convergence desktop designs and mobile desktop environments. The obvious choice would be GNOME, but it is very heavy, both on memory and cpu usage and my board with only 2GB of ram cannot handle it if combined with other heavy programs. I knew that Librem was developing a desktop environment for their Librem 5 linux phone. Since they focus on opensource software i thought if i can install their desktop environment on my tablet to try it and.... yes, it is possible! And it is surprisingly easy to do.
So, if someone would like also to try their desktop environment, i make a "guide" on how to install it.
 
Like any wayland desktop environment, there is a compositor (called phoc) and a graphical shell (called phosh). On the git they state that to run phosh should run on any compositor that implement wlr-layer-shell, so maybe you could try other compositors!
 
First clone the git of phoc with:
git clone https://source.puri.sm/Librem5/phoc
 
Change the directory on the just downloaded folder:
cd phoc
 
Then, since they provide the file needed for debian packaging, i suggest to generate the deb package and install it instead of generating the binary directly with meson.
In this way you can uninstall the program simply with apt like any other program.
 
From the control file, i can see the needed dependencies, but i suggest to get directly from the build command below.
If some package is missing, the packaging tool will tell you which. Then you can simply do "sudo apt install [all the missing dependencies]"
 
To create the debian package run:
debuild -i -us -uc -b
 
When the command finish, it should create a debian package inside the upper folder called "phoc_0.4.0_[architecture].deb"
You can install it with "sudo apt install /path to the file/phoc_0.4.0_[architecture].deb"
 
Once phoc is installed, it's time to install phosh.
Go to the previous folder with:
cd ..
 
Clone the phosh git with:
git clone https://source.puri.sm/Librem5/phosh
 
Change the directory on the just downloaded folder:
cd phosh
 
Dependencies should be these, but like before, i suggest to get them directly from the build command and install them as the same way as phoc:
 
To create the debian package run:
debuild -i -us -uc -b
 
At the end of the compilation, you should find the package inside the upper folder and like before you can install it with "sudo apt install /path to the file/phosh_0.4.0_[architecture].deb"
 
That's it. Reboot and on you favourite login manager should appear the entry "Phosh" that can be started like any other desktop environment.
 
During the debian packaging compilation it will generate some other packages, like the debugging symbols, but they are not needed to make phosh work.
Hope someone could find this "guide" useful.
Have fun!
 

I just released Armbian Focal Desktop MAINLINE images for Khadas VIM3 Pro. These are individually, pure arm64 and hybrid arm64/armhf variations.
Thanks go to @lanefu for key pointers in understanding how to "re-arm" the firstboot and firstboot-config mechanism in current-state Armbian.
 
Please offer feedback and experiences if you test these. The images are currently hand-built, but if enough interest is generated, and time permitting, I will commit to a git fork for an unsupported standard building process.
 

 
I have more detail on the distribution site at archive.org, and in the corresponding posts to the Khadas forums:
 
armhf Hybrid
LightDM will NOT work as display manager in this configuration, and I've chromed-up lxdm as a replacement. Autologin may be a work still in progress.
Archive.org: Armbian 21.02.3 MAINLINE Image For Khadas VIM3 Pro - 32-bit Userspace - Ubuntu Focal Xfce Desktop Forums.khadas.com: Community Armbian 21.02.3 MAINLINE Image For Khadas VIM3 Pro With 32-bit Userspace  
arm64 Native
UPDATED INFO
HDMI audio out is non-functional with the 64-bit userspace, which is true for all Debian and Ubuntu systems, including Khadas Fenix builds.
This capability may be a user's deciding factor in chosing between builds.
With further testing, HDMI AUDIO NOW WORKS in arm64 image build!
Archive.org: Armbian 21.02.3 MAINLINE Image For Khadas VIM3 Pro - arm64 - Ubuntu Focal Xfce Desktop Forums.khadas.com: Community Armbian 21.02.3 MAINLINE Image For Khadas VIM3 Pro arm64 Native  

I just released Armbian Focal Desktop MAINLINE images for Khadas VIM3 Pro. These are individually, pure arm64 and hybrid arm64/armhf variations.
Thanks go to @lanefu for key pointers in understanding how to "re-arm" the firstboot and firstboot-config mechanism in current-state Armbian.
 
Please offer feedback and experiences if you test these. The images are currently hand-built, but if enough interest is generated, and time permitting, I will commit to a git fork for an unsupported standard building process.
 

 
I have more detail on the distribution site at archive.org, and in the corresponding posts to the Khadas forums:
 
armhf Hybrid
LightDM will NOT work as display manager in this configuration, and I've chromed-up lxdm as a replacement. Autologin may be a work still in progress.
Archive.org: Armbian 21.02.3 MAINLINE Image For Khadas VIM3 Pro - 32-bit Userspace - Ubuntu Focal Xfce Desktop Forums.khadas.com: Community Armbian 21.02.3 MAINLINE Image For Khadas VIM3 Pro With 32-bit Userspace  
arm64 Native
UPDATED INFO
HDMI audio out is non-functional with the 64-bit userspace, which is true for all Debian and Ubuntu systems, including Khadas Fenix builds.
This capability may be a user's deciding factor in chosing between builds.
With further testing, HDMI AUDIO NOW WORKS in arm64 image build!
Archive.org: Armbian 21.02.3 MAINLINE Image For Khadas VIM3 Pro - arm64 - Ubuntu Focal Xfce Desktop Forums.khadas.com: Community Armbian 21.02.3 MAINLINE Image For Khadas VIM3 Pro arm64 Native  

I just released Armbian Focal Desktop MAINLINE images for Khadas VIM3 Pro. These are individually, pure arm64 and hybrid arm64/armhf variations.
Thanks go to @lanefu for key pointers in understanding how to "re-arm" the firstboot and firstboot-config mechanism in current-state Armbian.
 
Please offer feedback and experiences if you test these. The images are currently hand-built, but if enough interest is generated, and time permitting, I will commit to a git fork for an unsupported standard building process.
 

 
I have more detail on the distribution site at archive.org, and in the corresponding posts to the Khadas forums:
 
armhf Hybrid
LightDM will NOT work as display manager in this configuration, and I've chromed-up lxdm as a replacement. Autologin may be a work still in progress.
Archive.org: Armbian 21.02.3 MAINLINE Image For Khadas VIM3 Pro - 32-bit Userspace - Ubuntu Focal Xfce Desktop Forums.khadas.com: Community Armbian 21.02.3 MAINLINE Image For Khadas VIM3 Pro With 32-bit Userspace  
arm64 Native
UPDATED INFO
HDMI audio out is non-functional with the 64-bit userspace, which is true for all Debian and Ubuntu systems, including Khadas Fenix builds.
This capability may be a user's deciding factor in chosing between builds.
With further testing, HDMI AUDIO NOW WORKS in arm64 image build!
Archive.org: Armbian 21.02.3 MAINLINE Image For Khadas VIM3 Pro - arm64 - Ubuntu Focal Xfce Desktop Forums.khadas.com: Community Armbian 21.02.3 MAINLINE Image For Khadas VIM3 Pro arm64 Native  

I just released Armbian Focal Desktop MAINLINE images for Khadas VIM3 Pro. These are individually, pure arm64 and hybrid arm64/armhf variations.
Thanks go to @lanefu for key pointers in understanding how to "re-arm" the firstboot and firstboot-config mechanism in current-state Armbian.
 
Please offer feedback and experiences if you test these. The images are currently hand-built, but if enough interest is generated, and time permitting, I will commit to a git fork for an unsupported standard building process.
 

 
I have more detail on the distribution site at archive.org, and in the corresponding posts to the Khadas forums:
 
armhf Hybrid
LightDM will NOT work as display manager in this configuration, and I've chromed-up lxdm as a replacement. Autologin may be a work still in progress.
Archive.org: Armbian 21.02.3 MAINLINE Image For Khadas VIM3 Pro - 32-bit Userspace - Ubuntu Focal Xfce Desktop Forums.khadas.com: Community Armbian 21.02.3 MAINLINE Image For Khadas VIM3 Pro With 32-bit Userspace  
arm64 Native
UPDATED INFO
HDMI audio out is non-functional with the 64-bit userspace, which is true for all Debian and Ubuntu systems, including Khadas Fenix builds.
This capability may be a user's deciding factor in chosing between builds.
With further testing, HDMI AUDIO NOW WORKS in arm64 image build!
Archive.org: Armbian 21.02.3 MAINLINE Image For Khadas VIM3 Pro - arm64 - Ubuntu Focal Xfce Desktop Forums.khadas.com: Community Armbian 21.02.3 MAINLINE Image For Khadas VIM3 Pro arm64 Native  

I just released Armbian Focal Desktop MAINLINE images for Khadas VIM3 Pro. These are individually, pure arm64 and hybrid arm64/armhf variations.
Thanks go to @lanefu for key pointers in understanding how to "re-arm" the firstboot and firstboot-config mechanism in current-state Armbian.
 
Please offer feedback and experiences if you test these. The images are currently hand-built, but if enough interest is generated, and time permitting, I will commit to a git fork for an unsupported standard building process.
 

 
I have more detail on the distribution site at archive.org, and in the corresponding posts to the Khadas forums:
 
armhf Hybrid
LightDM will NOT work as display manager in this configuration, and I've chromed-up lxdm as a replacement. Autologin may be a work still in progress.
Archive.org: Armbian 21.02.3 MAINLINE Image For Khadas VIM3 Pro - 32-bit Userspace - Ubuntu Focal Xfce Desktop Forums.khadas.com: Community Armbian 21.02.3 MAINLINE Image For Khadas VIM3 Pro With 32-bit Userspace  
arm64 Native
UPDATED INFO
HDMI audio out is non-functional with the 64-bit userspace, which is true for all Debian and Ubuntu systems, including Khadas Fenix builds.
This capability may be a user's deciding factor in chosing between builds.
With further testing, HDMI AUDIO NOW WORKS in arm64 image build!
Archive.org: Armbian 21.02.3 MAINLINE Image For Khadas VIM3 Pro - arm64 - Ubuntu Focal Xfce Desktop Forums.khadas.com: Community Armbian 21.02.3 MAINLINE Image For Khadas VIM3 Pro arm64 Native  

Budgie is on my list - as I get kinks worked out with clean, vanilla Armbian. I am doing hybrid arm64 kernels and armhf userspace because of audio-plugins. This worked well for me in Pinebook Pro, etc.

I'd do more with pure arm64, if I can solve some gaps with Carla, and when there's a 64-bit Linux Widevine. That's when Google decides they need a 64-bit Chromebook, I guess.
 
— Jeremiah

This is it!
Touching /root/.not_logged_in_yet gets the desired, correctly reset behavior for the armbian-firstrun-config systemd unit. I knew it was some small, critical configuration I'd been missing.
I now have what's needed for a community, unsupported Armbian Khadas VIM3 image that's functionally equivalent to Odroid N2+, and have plans for similar with 32-bit apt/userspace, which enables access to an armhf ecosystem of commercial audio software, and snap images.
 
This also means that the VIM3 Twister OS image that I have some good interest in from users, can be updated to use this firstrun logic - with an addition that will hardlink the new user to the "pi" account on which Twister OS scripts and configurations depend.
 
In the background are plans for ready-to-run Armbian VIM images with Budgie desktop and Elementary OS, pre-built. Being unsupported, some of these may advance from Focal to Groovy or Hirsute.
 
Thanks!

Really thanks for this. It gives me a lot more to go on.
I'll do more work in the next day or so, and be back with some updates - HOPEFULLY with some guidance to offer others, if successful!
 
The ""${SDCARD}"/root/.not_logged_in_yet" is a GREAT hint!
It's the opposite of touching a flag in the file system, so of course finding it in a configured system is impossible! I'd have taken a long time, before I got to it in the script sources.
 
— Jeremiah

Doing this should probably trigger it.  https://github.com/armbian/build/blob/master/lib/distributions.sh#L157

Also take a look at 

https://github.com/armbian/build/blob/master/lib/distributions.sh#L372-L379

 

Might be related to https://github.com/armbian/build/blob/master/packages/bsp/common/lib/systemd/system/armbian-firstrun-config.service#L9
 

Probably best to keep conversation here for now.  Mostly we use issues in GitHub for major bugs / problems

Thanks! Very kind.
I am looking to re-set the firstboot state for a derived image, after customization and out-of-band additions. My efforts extend to re-enabling systemd unit files for armbian-firstrun, armbian-firstrun-config, and armbian-resize-filesystem. Results: New ssh keys are generated, and new UUID appended to /etc/armbian-image-release - no other config tasks are run (update root pw, create normal user, choose logon environment, etc) Observation: /usr/lib/systemd/system/armbian-firstrun-config is deleted after being enabled, on next boot.
Is this expected behavior? Is it an error in how symlinks under /etc/systemd are handled? Would an issue on the git repository be well received? I'd like the unit disabled, and maybe a re-settable flag written to the image, preventing accidental firstrun.
 
My main question is still why this isn't working as expected. Does behavior change, if /etc/armbian-image-release already exists? There's something I'm missing!
 
When I understand this fully, I'll be in a better position to offer contributions.
 

I agree. I'm very much in favor of making contributions, and not shy about being detailed. When the Linux world revolved around HOWTOs, not Reddit subs and siloed vendor forums, I was particularly active.

Here's a case where I'd gladly supply documentation, were I not faced with ambiguous outcomes, and a lack of authoritative information to begin!
Thanks!
— Jeremiah

You can help make this wish become reality. Everybody can contribute to make the documentation better: https://github.com/armbian/documentation
The lack of (human) resources is a big issue for the Armbian project so community contributions are more than welcome.