iiab
iiab copied to clipboard
iiab
Call for testing: IIAB pre-installed on ubuntu-mate-22.04-desktop-arm64+raspi
2 New images for evaluation based on ubuntu-mate-22.04-desktop-arm64+raspi.img base small
Exact same user feel as the stock ubuntu-mate images, geared for Desktop therefore use of a monitor/keyboard/mouse is highly recommended. Tested on RPi-400 without connecting to the internet yet. Feedback welcome under this issue, don't file new issues, keep it here.
The image shipped with /etc/iiab/local_vars.yml renamed to local_vars.yml.builder to encourage a review before using, can/should be copied local_vars.yml. Also present is the chroot build script /etc/iiab/builder.sh employed by mk-image as (mate-)runme.sh
https://github.com/iiab/iiab-factory/pull/231
First Issue: If the screensaver engages your user password will not unlock the session, hard power cycle. Disable the power management and screensaver before they cut in.
Should somebody boot the stock upstream image please check for this behavior since I never booted a stock version of the ubuntu-mate-22.04-desktop-arm64+raspi.img source image as my build system is automated. This is most likely an upstream issue that was inherited.
Disable the setting here:
Looks like an upstream issue and might be resolved when connected to the internet for updates
Taken after providing internet access via tethered cell phone prior to reboot, seems stable with the screensaver turned off for now. http://sprunge.us/NXQi57
I've guessing it might be a bad microSD card (maybe, in any case overnight it froze [still hanging now] while writing to the card, 32% of the way through). So I need to try again flashing the 3GB image in another way.
Another microSD card did not work. Hopefully that was just extremely bad luck. I'll try a third one.
3rd microSD card worked.
Just FYI Ubuntu Mate had problems sync'ing with the screen (1st minute warnings came up on monitor saying so, 2nd minute the screen worked but was flashing at a very high frequence, 3rd minute it all started to work).
After I set a username/password, Mate appears to be now installing many things (looks like it might take 20-30min; I have to step away but will come back to it later today).
MATE completed its many updates and rebooted :heavy_check_mark:
Very unfortunately however http://box and http://box.lan do not work (@georgejhunt very nicely made http://box.lan auto-launch when IIAB is installed on RasPiOS with desktop!)
Background: this shortcoming is problematic, as teachers/students depend on this to get to know IIAB. Long story short IIAB communities and IIAB documentation rely on this heavily, so the onboarding + learning experience is uniformly explainable + tangible across all devices — including IIAB's that happen to have a graphical desktop.
The P-400 and small RCA hdmi TV worked great for me, what are you using for a monitor? Like a said it's a full pristine setup, at least you don't have the IIAB install to wait through, just rename the builder,yml file to local_vars,yml and reboot as cmdserv needs to have the local_vars,yml file present or the service doesn't start up. The hotspot is disabled to allow client upstream wifi during first boot without potential interruption, given the image was build in a container wifi was not detected nor the alternate firmware installed, just a pass trough admin-console, the wifi hotspot will become active.
The P-400 and small RCA hdmi TV worked great for me, what are you using for a monitor?
It's an ancient Dell HDMI monitor, no worries that's it's ugly during the 1st two minutes (screen works in the end!)
MATE completed its many updates and rebooted heavy_check_mark
Very unfortunately however http://box and http://box.lan do not work (@georgejhunt very nicely made http://box.lan auto-launch when IIAB is installed on RasPiOS with desktop!).
There never was any attempt to port that desktop pop-up to Ubuntu/Mint given the many desktops that could be in play, that is apples to oranges whining. Now the cookie cutter is made with a narrow choice of one desktop George could put the same effort into this desktop if he so chooses.
Background: this shortcoming is problematic, as teachers/students depend on this to get to know IIAB. Long story short IIAB communities and IIAB documentation rely on this heavily, so the onboarding + learning experience is uniformly explainable + tangible across all devices — including IIAB's that happen to have a graphical desktop.
Sorry, I used the 'normal' name for the machine localhost not the hack when I accessed the admin page from the iiab box. Just checked, http://box.lan does currently work, but I'll check right after first login next time I install a fresh image.
-
How hard is it to make Ubuntu Mate friendly (i.e. genuinely approachable) as @georgejhunt has done for RasPiOS with desktop?
@georgejhunt very nicely made http://box.lan/ auto-launch when IIAB is installed on RasPiOS with desktop!
-
And/or how else can vital instructions / essential options be made crystal clear + obvious to new users within the image itself?
-
It's true that gurus can use http://10.10.10.10 and http://localhost, but regular people need http://box and http://box.lan to work across all IIAB's to communicate amongst themselves (mentor each other, follow docs, videos, etc) so regardless let's find a way to fix that!
- How hard is it to make Ubuntu Mate friendly (i.e. genuinely approachable) as @georgejhunt has done for RasPiOS with desktop? > @georgejhunt very nicely made http://box.lan/ auto-launch when IIAB is installed on RasPiOS with desktop!
Now there is a target desktop is all I'm saying.
2. And/or how else can vital instructions / essential options be made crystal clear + obvious to new users within the image itself?
Let me know, this was a first cut, beta release
3. It's true that gurus can use http://10.10.10.10 and http://localhost, but regular people need http://box and http://box.lan to work across all IIAB's to communicate amongst themselves (mentor each other, follow docs, videos, etc) so regardless let's find a way to fix that!
Get off the soapbox, with the 127.0.0.1 hack in /etc/hosts out of the box should of worked. If that didn't do some quick checking in /etc/hosts if it's still there or not, firstboot might of wiped the change, didn't notice as explained above. Minor issue, easy worked around, stop being a naysayer the second cut will be done on the P-400 resulting in iiab-hotspot-on having the entries for detected AP support then hotspot might be available on firstboot but I'm a little hesitant to do that until there is a user created that can ssh and I would like to make the 5G band available during firstboot for updates.
For today with a local_vars.yml file in place just run sudo ./iiab-network or ICO in admin-console which should be SOP for any image deployed. After the initial reboot I re-enabled the screensaver locking and the above noted issue hasn't re-appeared, might just be the firstboot environment. I suggest just after the first login, rename the local_vars.yml.builder file back, run iiab-network and reboot then re-evaluate.
Maybe for bonus points when the terminal opens banner "please run cd /opt/iiab/iiab and sudo ./iiab-network" like other the warnings do and have the terminal pop open when logging into the gui session?
I'm not being dismissive.
I'm just saying I've been in dozens of schools where http://box and http://box.lan have to work (otherwise there's simply chaos).
when the terminal opens banner "please run cd /opt/iiab/iiab and sudo ./iiab-network" like other the warnings do and have the terminal pop open when logging into the gui session?
Many people will open a browser but not a Terminal.
But as a short-term / intermediary solution something like the above (mandatory reminder/nudge in Linux terminal) is definitely pointing in the right direction.
On a side note with /etc/iiab/install-flags/iiab-complete running sudo iiab did ask to create iiab-admin set password then stopped, that should be enough to create the lessor restricted non-sudo account that could be used with admin-console or alternate GUI account but no sudo access.
I'm just saying I've been in dozens of schools where http://box and http://box.lan have to work (otherwise there's simply chaos).
Sorry was evaluating every other aspect of the install, so that comes back to checking /etc/hosts prior to running iiab-network which I proceeded to do because that is the right thing to do to update ap0's mac address per installation or there will be mayhem with duplicate mac address in the air waves when more than 1 of the same image are booted close by. This goes for ALL iiab prepared images without exception so that part should already be documented with this 'issue' going away upon reboot.
this 'issue' going away upon reboot
Currently a reboot does restore access to http://box and http://box.lan
As you probably well know; but just FYI I tried 3 reboots of this Ubuntu Mate [from 3GB image, on RPi 4] simply to verify that.
(The ideal would be that both names box and box.lan work for newbies exploring the desktop, if it's possible, even prior to the 1st reboot.)
That is what the confirmation that I asked for is about, I'll check it on the next burn/boot, but I'm short of spare sdcards atm... This that you testing rpi-imager?
8.239.59.22 - - [12/Jul/2022:08:42:28 -0500] "GET /local_content/uploads/iiab-base-0711-ubuntu-mate-22.04-desktop-arm64+raspi.img.zip HTTP/1.1" 206 90406354 "-" "Mozilla/5.0 rpi-imager/1.7.2"
Yes I used rpi-imager
confirmation that I asked for
What confirmation? I'm away most of the rest of the day, but will send if I can.
If /etc/hosts has the needed entries to resolve box box.lan just after firstboot login, I suspect the file was rewritten from what was originally on the image that I just confirmed is present using mount-image.sh
127.0.0.1 box.lan localhost.localdomain localhost box box box.lan
::1 localhost ip6-localhost ip6-loopback
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
Just FYI:
-
The jumpy/flashing screen occurs on most subsequent reboots.
-
After the 4th (but not 5th) reboot:
PS About 4 apt updates were manually applied prior to the 4th reboot. So possibly that's related to the Bluetooth complaint. (The bottom of /var/log/apt/history.log shows these apt updates and more...)
Start-Date: 2022-07-12 10:05:14
Commandline: aptdaemon role='role-commit-packages' sender=':1.42'
Remove: ubuntu-mate-core:arm64 (1.282), oem-config:arm64 (22.04.16), cryptsetup-initramfs:arm64 (2:2.4.3-1ubuntu1), oem-config-gtk:arm64 (22.04.16), ubuntu-mate-desktop:arm64 (1.282)
Purge: ubiquity-casper:arm64 (1.470), ubiquity-frontend-gtk:arm64 (22.04.16), cryptsetup:arm64 (2:2.4.3-1ubuntu1), oem-config-slideshow-ubuntu-mate:arm64 (181.1), ubiquity-ubuntu-artwork:arm64 (22.04.16), ubiquity:arm64 (22.04.16)
End-Date: 2022-07-12 10:07:29
Start-Date: 2022-07-12 11:23:29
Commandline: apt install traceroute
Install: traceroute:arm64 (1:2.1.0-2)
End-Date: 2022-07-12 11:23:34
Start-Date: 2022-07-12 13:41:50
Commandline: apt -y dist-upgrade
Upgrade: xserver-xorg-core:arm64 (2:21.1.3-2ubuntu2, 2:21.1.3-2ubuntu2.1), xserver-xorg-legacy:arm64 (2:21.1.3-2ubuntu2, 2:21.1.3-2ubuntu2.1), xserver-common:arm64 (2:21.1.3-2ubuntu2, 2:21.1.3-2ubuntu2.1), linux-libc-dev:arm64 (5.15.0-40.43, 5.15.0-41.44)
End-Date: 2022-07-12 13:41:58
Start-Date: 2022-07-12 13:42:07
Commandline: apt -y autoremove
Remove: dctrl-tools:arm64 (2.24-3build2), gir1.2-nma-1.0:arm64 (1.8.34-1ubuntu1), libtimezonemap-data:arm64 (0.4.6-2build2), os-prober:arm64 (1.79ubuntu2), gir1.2-timezonemap-1.0:arm64 (0.4.6-2build2), dpkg-repack:arm64 (1.50), libdebian-installer4:arm64 (0.122ubuntu3), libtimezonemap1:arm64 (0.4.6-2build2), python3-icu:arm64 (2.8.1-0ubuntu2), python3-pam:arm64 (0.4.2-13.4build4), grub-common:arm64 (2.06-2ubuntu7), rdate:arm64 (1:1.10.2-1build1), gir1.2-xkl-1.0:arm64 (5.4-4build2)
End-Date: 2022-07-12 13:42:20
Start-Date: 2022-07-12 13:49:38
Commandline: apt install emacs
Install: emacs:arm64 (1:27.1+1-3ubuntu5), libm17n-0:arm64 (1.8.0-4, automatic), emacs-gtk:arm64 (1:27.1+1-3ubuntu5, automatic), m17n-db:arm64 (1.8.0-3, automatic), emacs-el:arm64 (1:27.1+1-3ubuntu5, automatic), libotf1:arm64 (0.9.16-3build1, automatic), emacs-common:arm64 (1:27.1+1-3ubuntu5, automatic), emacs-bin-common:arm64 (1:27.1+1-3ubuntu5, automatic)
End-Date: 2022-07-12 13:49:59
Just FYI:
1. The jumpy/flashing screen occurs on most subsequent reboots. 2. After the 4th (but not 5th) reboot:
I'm showing 3 packages to update since I lasted updated. no jumpy screen here
apt list --upgradable
Listing... Done
xserver-common/jammy-updates,jammy-security 2:21.1.3-2ubuntu2.1 all [upgradable from: 2:21.1.3-2ubuntu2]
xserver-xorg-core/jammy-updates,jammy-security 2:21.1.3-2ubuntu2.1 arm64 [upgradable from: 2:21.1.3-2ubuntu2]
xserver-xorg-legacy/jammy-updates,jammy-security 2:21.1.3-2ubuntu2.1 arm64 [upgradable from: 2:21.1.3-2ubuntu2]
PS About 4 apt updates were manually applied prior to the 4th reboot. So possibly that's related to the Bluetooth complaint. (The bottom of /var/log/apt/history.log shows these apt updates and more...)
I have a nice blueman-applet in the top right corner.
Start-Date: 2022-07-12 10:05:14 Commandline: aptdaemon role='role-commit-packages' sender=':1.42' Remove: ubuntu-mate-core:arm64 (1.282), oem-config:arm64 (22.04.16), cryptsetup-initramfs:arm64 (2:2.4.3-1ubuntu1), oem-config-gtk:arm64 (22.04.16), ubuntu-mate-desktop:arm64 (1.282) Purge: ubiquity-casper:arm64 (1.470), ubiquity-frontend-gtk:arm64 (22.04.16), cryptsetup:arm64 (2:2.4.3-1ubuntu1), oem-config-slideshow-ubuntu-mate:arm64 (181.1), ubiquity-ubuntu-artwork:arm64 (22.04.16), ubiquity:arm64 (22.04.16) End-Date: 2022-07-12 10:07:29 Start-Date: 2022-07-12 11:23:29 Commandline: apt install traceroute Install: traceroute:arm64 (1:2.1.0-2) End-Date: 2022-07-12 11:23:34 Start-Date: 2022-07-12 13:41:50 Commandline: apt -y dist-upgrade Upgrade: xserver-xorg-core:arm64 (2:21.1.3-2ubuntu2, 2:21.1.3-2ubuntu2.1), xserver-xorg-legacy:arm64 (2:21.1.3-2ubuntu2, 2:21.1.3-2ubuntu2.1), xserver-common:arm64 (2:21.1.3-2ubuntu2, 2:21.1.3-2ubuntu2.1), linux-libc-dev:arm64 (5.15.0-40.43, 5.15.0-41.44) End-Date: 2022-07-12 13:41:58 Start-Date: 2022-07-12 13:42:07 Commandline: apt -y autoremove Remove: dctrl-tools:arm64 (2.24-3build2), gir1.2-nma-1.0:arm64 (1.8.34-1ubuntu1), libtimezonemap-data:arm64 (0.4.6-2build2), os-prober:arm64 (1.79ubuntu2), gir1.2-timezonemap-1.0:arm64 (0.4.6-2build2), dpkg-repack:arm64 (1.50), libdebian-installer4:arm64 (0.122ubuntu3), libtimezonemap1:arm64 (0.4.6-2build2), python3-icu:arm64 (2.8.1-0ubuntu2), python3-pam:arm64 (0.4.2-13.4build4), grub-common:arm64 (2.06-2ubuntu7), rdate:arm64 (1:1.10.2-1build1), gir1.2-xkl-1.0:arm64 (5.4-4build2) End-Date: 2022-07-12 13:42:20 Start-Date: 2022-07-12 13:49:38 Commandline: apt install emacs Install: emacs:arm64 (1:27.1+1-3ubuntu5), libm17n-0:arm64 (1.8.0-4, automatic), emacs-gtk:arm64 (1:27.1+1-3ubuntu5, automatic), m17n-db:arm64 (1.8.0-3, automatic), emacs-el:arm64 (1:27.1+1-3ubuntu5, automatic), libotf1:arm64 (0.9.16-3build1, automatic), emacs-common:arm64 (1:27.1+1-3ubuntu5, automatic), emacs-bin-common:arm64 (1:27.1+1-3ubuntu5, automatic) End-Date: 2022-07-12 13:49:59
The top one looks like something the installer did, and emacs would be you, the other 2 are you or the system?
Start-Date: 2022-07-11 10:35:26
Commandline: aptdaemon role='role-commit-packages' sender=':1.43'
Remove: ubuntu-mate-core:arm64 (1.282), oem-config:arm64 (22.04.16), cryptsetup-initramfs:arm64 (2:2.4.3-1ubuntu1), oem-config-gtk:arm64 (22.04.16), ubuntu-mate-desktop:arm64 (1.282)
Purge: ubiquity-casper:arm64 (1.470), ubiquity-frontend-gtk:arm64 (22.04.16), cryptsetup:arm64 (2:2.4.3-1ubuntu1), oem-config-slideshow-ubuntu-mate:arm64 (181.1), ubiquity-ubuntu-artwork:arm64 (22.04.16), ubiquity:arm64 (22.04.16)
End-Date: 2022-07-11 10:37:37
Start-Date: 2022-07-11 23:03:55
Commandline: aptdaemon role='role-commit-packages' sender=':1.147'
Upgrade: linux-libc-dev:arm64 (5.15.0-40.43, 5.15.0-41.44)
End-Date: 2022-07-11 23:03:59
I used the provided gui tools to update the system.
I have a nice blueman-applet in the top right corner.
Likewise, it's there now. Not sure if it was there after the 4th boot.
The top one looks like something the installer did, and emacs would be you, the other 2 are you or the system?
The top one happened automatically. The other 4 paragraphs (at the bottom of /var/log/apt/history.log) are from my manual commands.
Sorry I haven't time today (to explore it more deeply) but iiab-diagnostics are here if it helps: http://sprunge.us/ZNeEG9?en
The image shipped with /etc/iiab/local_vars.yml renamed to local_vars.yml.builder to encourage a review before using, can/should be copied local_vars.yml.
Didn't review the above note, but useful anyway.
177 =IIAB========================================================================== 178 FILE DOES NOT EXIST: /etc/iiab/local_vars.yml 1249 =IIAB========================================================================== 1250 COMMAND: /usr/bin/journalctl -t IIAB-CMDSRV # Admin Console CMDSRV log 1251 1252 Jul 12 10:07:48 181-mate-iiab-3gb IIAB-CMDSRV[44617]: IIAB-CMDSRV : Starting Command Server 1253 Jul 12 10:07:48 181-mate-iiab-3gb IIAB-CMDSRV[44617]: IIAB-CMDSRV : Error in /etc/iiab/local_vars.yml 1254 Jul 12 10:07:48 181-mate-iiab-3gb IIAB-CMDSRV[44617]: IIAB-CMDSRV : Command Server Initialization Failed
In light of the above these would have to be 'True' in default_vars:
31 iiab-apps-to-be-installed : 32 awstats 33 bluetooth 34 captiveportal 35 kalite 36 kiwix 37 openvpn 38 osm_vector_maps 39 remoteit
as you downloaded 'base':
179 =IIAB========================================================================== 180 -rw-r--r-- 1 root root 294 Jul 11 01:26 /etc/iiab/iiab_state.yml 181 182 # DO NOT MANUALLY EDIT THIS, THANKS! 183 # IIAB does NOT currently support uninstalling apps/services. 184 185 sshd_installed: True 186 iiab_admin_installed: True 187 mysql_installed: True 188 nginx_installed: True 189 www_base_installed: True 190 pylibs_installed: True 191 usb_lib_installed: True 192 www_options_installed: True
I'm just saying I've been in dozens of schools where http://box and http://box.lan have to work (otherwise there's simply chaos).
Sorry was evaluating every other aspect of the install, so that comes back to checking /etc/hosts prior to running iiab-network which I proceeded to do because that is the right thing to do to update ap0's mac address per installation or there will be mayhem with duplicate mac address in the air waves when more than 1 of the same image are booted close by. This goes for ALL iiab prepared images without exception so that part should already be documented with this 'issue' going away upon reboot.
Hum, could tie in 'iiab' instead of exiting at iiab-complete offer to run iiab-network (with new network-complete flag as the final step) after suggesting raspi-config or other related actions (connect to upstream wifi) be completed first. Just ship images with iiab-complete and the in the wild provisioning step would be just sudo iiab Y to run iiab-network. You get the reduced iiab-admin user created at runtime as noted above, the network is adjusted for the current needs and the end user doesn't have to learn any new tricks. Does that sound plausible?
I don't understand all the details but Raspberry hotspots should (wherever possible!) start right up (on 1st boot of image, if feasible?)
Running ./iiab-network can and should be heavily promoted...on top of that? Ideally in a targeted or even event-driven way...for those most likely to need it on non-Raspberry HW and USB-smells-like-a-network or Ethernet-link-detected scenarios?
(Not sure if that's at all realistic in 2022, but it's an idea.)
I don't understand all the details but Raspberry hotspots should (wherever possible!) start right up (on 1st boot of image, if feasible?)
Not even the stock image provided by RasPi Foundation functions as a 'client' out of the box without user intervention due to the legal requirements around wifi. When you create an image for redistribution you become a de-facto distro, based on, variant of one released but on your own and can be held liable for infractions under local laws, should really adhere to the local laws of where the equipment is deployed. I'm not going to play fast and loose when it comes down to international standards when we can strive for better, period.
Running ./iiab-network can and should be heavily promoted...on top of that? Ideally in a targeted or even event-driven way...for those most likely to need it on non-Raspberry HW and USB-smells-like-a-network or Ethernet-link-detected scenarios?
(Not sure if that's at all realistic in 2022, but it's an idea.)
Write something up, in place of making a wish that I'm not going to grant because there is no clear objective.
Just FYI the screen problem is more severe than I realized yesterday:
It would not boot at all for more than 5 min today, with the (1) the usual 1920x1080 failure-to-sync flashing quickly on-screen every 5-10 seconds, and (2) the Raspberry Pi 4's green light flashing 7 times, likewise every few seconds (seemingly related to kernel.img). So I forced a reboot, which did better.
It would appear that Ubuntu Mate does not support as many different HDMI screen-sync'ing arrangements as RasPiOS and Ubuntu itself. Of course it's very odd that these screen-sync'ing failures are usually resolved within about 1-2 minutes, and booting continues from there. Whereas other times it's resolved much faster. And then sometimes it's never resolved, completely preventing the kernel/OS from booting, which is indeed rather more serious.
So be it. Just FYI.
Seems as if you are pushing the limits of the monitor's hardware beyond it's recommended settings. Without knowing what monitor you have connected all you are making is vague statements about not supporting some resolutions.
https://elinux.org/R-Pi_Troubleshooting#Green_LED_blinks_in_a_specific_pattern suggests your SD card might be an issue, any other storage usb devices connected? Official power supply used?