I have a weird OS issue with my Tachyon. I wanted to run the man command and the system instructed me that I had to un-minimize the OS for that. So I ran the unminimize command. It was not super straightforward as some package failed and I had some manual fixes to apply but it eventually succeeded (also had to reinstall tachyon-desktop otherwise the desktop did not start by itself after the boot).
But since then the network is acting surprisingly.
Wifi
The WiFi stack works but takes a very long time to initialize after boot (> 5 minutes I’d say). I have uploaded here the output of the dmesg command. The dmesg_failure.txt file is taken while the wifi does not work and the dmesg_success.txt one is taken shortly after the wifi eventually initialized correctly.
Before it initializes, all the commands from your wifi documentation are succeeding (e.g. the lspci command shows the correct device, the modem can be started and stopped without error, etc.). Except for the nmcli dev wifi rescan command that shows Error: No Wi-Fi device found..
Cellular
Meanwhile, the cellular connection is just not working at all. The output of the particle-tachyon-ril-ctl state command is Unknown and the output of the status command is empty. Even a long time after the boot.
Let me know if there are other log files that I can provide to help debug this.
Note that all that is not very bad. If needed, I can just reinstall the device and not unminimize it. But getting a full-featured system would still be great.
I have to say, congratulations on breaking a Tachyon OS install! Extremely interesting - I hadn't tried this from the desktop image before, but alas, it happened to me as well!
This is appears that Ubuntu has something being inferred incorrectly and it assumes you’re restoring a standard Ubuntu desktop or server system, not a customized, integrated embedded system like Tachyon.
That’s why you hit trouble:
It likely pulled in unrelated packages and made conflicting assumptions using the standard ARM64 build
It may have overwritten network-related config, removed delays built in for proper RIL/WiFi sequencing, or messed with NetworkManager backends. In fact, I say may, but it looks pretty certain it did this!
Recommended path for now: Since this is a development device, the cleanest path is to re-flash the board. The reason is that I suspect Ubuntu did some things that are very hard to reverse in a short period.
Saying this, we will fix it - adding it to the list of things for Monday to get patched up!
To avoid running unminimize in the, you can install missing tools manually:
sudo apt update
sudo apt install man-db manpages
This avoids all the unintended system-wide changes unminimize brings in.
If you want to help us root-cause the issue, please share:
/var/log/syslog (immediately after boot and ~5 mins later)
systemctl list-jobs output shortly after boot
journalctl -b (early boot logs)
Output of nmcli dev and nmcli general status
ps aux | grep Modem and systemctl status particle-tachyon-ril
Thanks again for the clear description - this is helpful feedback and sorry for the bug...
Another minor symptom is that, while my device appears connected to the Particle Cloud, the LED is only pulsing green. Yesterday, after reinstalling some package it eventually turned blue (unfortunately I didn’t record exactly which package that was), but today I can get it to do so, even after reinstalling all the particle packages.
Also, note that man-dband manpages are already installed on the system. But I think that when the system is minimized there is something that makes it so that actual man pages are not installed (as well as some other documentation files in /usr/share/doc which in real life are probably much less useful).