I am having a problem installing MX16x32 on the above which runs MX15x32 perfectly.
An older AA1 without the Atom N270 (-HT-) runs an MX16x32 install just fine, from same ISO.
On the KAV60, MX16x32 installs fine, then first thing I run
Code: Select all
# apt-get update && apt-get dist-upgrade
MX16 crashed, well, became unresponsive? I waited a couple of hours but it didn't move.
This is the third time it's happened so I decided to try to find an answer.
I noticed this because I have been setting up the MX15x32 install for migration according to:
http://forum.mxlinux.org/viewtopic.php? ... 95#p402447
A couple of days ago I found and removed the MX16 repo to prepare for migration.
Today, after letting the Apt-Notifier do it's thing, a couple of hours later I ran
Code: Select all
# apt-get update && apt-get dist-upgrade
tool in the MX Package Installer. To my surprise there were beau coup updates? No way!
Checked /sources.lists.d, found the MX-16 repo reinserted and active, again.
Curious about this? I suppose it was done on purpose and might fix my 32-bit problem?
My alternatives seem to be:
1) stay with MX15 which is working fine, but I like running the same version on boxes I use, or
2) install a snapshot of that MX15, add the MX16 repo back and see how it goes, or
3) reinstall the snapshot of that MX15 on another partition and try the Migration tool, or
4) ???
Thanks for your thoughts.