¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io

Building up a wo-we


 

I have a wo-we unit working -- it is pretty much the same as KM4ACK detailed in his? posting some time ago.? It is working all my inter-actions with my radio in the shack.
I am in the process of setting up a second wo-we that I want to take into the field.
?
Problem I can't seem to get around is that mess that happens every time I boot the wo-we when it is running Mint? ?There are a number of posting out there on how to get around the problem on a boot -- i.e. hitting ctl-alt-del? until the option to pick an earlier os version shows up.? It works but is a pain in the shack even when I don't reboot that often.? It would be impossible in the field if I don't have a keyboard and mouse -- which I don't what to do.
?
I've tried a number of thing suggested on the web to force Linux to boot from a specific version of the os.? So far none of them have worked.
?
So where am I now on this.
?
I did a clean install of Mint on the new WO-WE.
?
My intent was to not do any updates and see if I can get an operating system without the problem.
?
I did not do the updates after the initial build.? I? ran the 73-Linux build.? When that rebooted at the end of the 73 build, the problem was back on this new system.
?
Does anyone know if KM4ACK's 73_linux? do an update when it starts and if so, can I change the 73 script to skip that?? ?Or has someone found a better way around this problem?
?


 

73Linux doesn't do any updates at boot. This only happens when you run the 73Linux script.
?
--
73, de KM4ACK
|
|


 

So the script does the update when it runs?? Then that is what is causing the problem with mint 21 on WO-WE.? Is there a way I can change the script so that it does not do the update, or are you depending on that update for the script to work?
?
If I could find a reliable way to force the system to boot from the older version, which does work, I could avoid the whole problem, but so far none of the suggestions I found on the we seem to work.


 

If the problem is screen goes away after login, i had something similar with an ATOPC-NUC (WoWe clone?). It is a linux kernel problem and nothing to do with 73Linux or how it updates apps. In my case, it was a regular linux mint kernel upgrade. Probably affects other Debian based distros
?
I know its been discussed on linux mint forums and a solution to load a working kernel as the default in cases of a headless system. I am away from that pc so i cannot check details, but the mint forums are where i would start.?
?
PlanB:? if a stock mint install works, run that and install 73 Linux on top. Just do not upgrade the kernel from the main OS maint app and you should be ok. Good luck.?
73 de KS1G


 

Your plan B was what I was attempting.? Problem seems to be that 73-Linux does an apt update at the start of the script.? ?At least that is what I am seeing, I have not attempted to open up the script.? That makes some sense in the normal course of events.? You likely should do an update if you are going to do a major install.? At least that is how most linux docs say you should work.??
?
Guess I'll wait and see if KM4ACK gets back to me on another way of doing this.


 

Apt update updates info from the repositories, i think 73 Linux uses that to get current source code, libraries, etc.? apt upgrade would risk installing kernels. I think the chance of the 73Linux script installing kernels is low. Unless one of the apts requires a newer kernel or library as a dependency.?


 

73Linux does both an apt update and upgrade when the script is run. The upgrade is what will install a new kernel if it's available. You can avoid this by adding a "hold" to the kernel before running 73Linux.
https://askubuntu.com/questions/938494/how-to-i-prevent-ubuntu-from-kernel-version-upgrade-and-notification
--
73, de KM4ACK
|
|


 

Thanks for the correction! I probably zoned out on that one!