[SOLVED] Unable to Install Vers25 but Vers24 Runs Well....How to Update?
4MLinuxThis forum is for the discussion of 4MLinux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Unable to Install Vers25 but Vers24 Runs Well....How to Update?
I have tried to use version 25, which installs and runs OK initially but fails on reboot with the error...XZ-compressed data is corrupt.
However, version 24 works without this problem and I am able to modify things and reboot without any error messages. It goes really well on my eeePC701SDX.....which has a 4GB memory card, 512RAM....I use unetbootin and do the install from the boot screen, the RAM size prevents me installing after booting up the live USB.
I have checked the media after download and it looks clean....
I would like to use the latest version 25, are there any suggestions as to what the problem might be?
That looks like read-write errors.
1) Where did you download the 4MLinux ISO from ?
2) Was the target partition formatted by the installation script ?
3) Was the installation cleanly finished or you had to power off (or reboot) by pressing a button on your computer?
I followed the trail from Distrowatch and, if memory is right, download via Sourceforge
I usually format and set up partitions in advance and would have used Fat32
Yes, it started up and ran well and fast.......I enjoyed the initial result, this is going to be a keeper, and set about adjusting things, time, wallpaper etc,.....delighted with the result.......then I shut it down. Booted up later and got the error message
.....downloaded again x2, checked MD5 as good... got the same result. When I got 24 working, I followed the same process, but 24 rebooted and seems to operate as it should.
Now I understand nothing. Does that mean that you are able to boot your 4MLinux 25.0? You can see an error during the boot, but the system seems to work OK. Is that so?
Now I understand nothing. Does that mean that you are able to boot your 4MLinux 25.0? You can see an error during the boot, but the system seems to work OK. Is that so?
.
I installed 4MLinux 25.0, using a 'live' USB, to sda1......works fine initially but when I shut it down and reboot it fails with the error message...."xl-compressed data is corrupt"
Using the same process with 4MLinux 24.0 works correctly and reboots without fault which suggests my hardware and process is correct.
Obviously I would prefer to be able to use & reboot the latest version.
To make my point I need to answer with more than a Yes or a No
....after install of 4MLinux25.0 I can startx and use all the facilities of 4MLinux25 but when I shut down and reboot I get the error message and I am unable to log in or startx.
The 4MLinux packages are called 'addons' (they are kept
in the /var/4MLinux directory). If you copy an addon to
to the /etc/init.d directory, 4MLinux will (re)install
this addon during the next startup (see point 2.4).
During each startup the sysinit script tries to install
its 'neighbors', meaning that /etc/init.d/rcS installs
all the addons which are located in the same directory
(that is /etc/init.d). The installed addons are moved to
/var/4MLinux (see also point 3.4).
CONCLUSION:
You have one or more addons in the /etc/init.d directory. Unfortunately, these addons are corrupted, so 4MLinux is unable to install them during the boot time. Why are these addons corrupted? My guess is that the system was not cleanly unmounted.
ADVICE:
Remove these addons manually using, for example, the 4MLinux live USB. Now try to boot your 4MLinux. If the problem still exists, then:
1) Download the 4MLinux ISO from its official repository (http://4mlinux.com/index.php?page=download).
2) Repeat the installation, but be patient: do not use poweroff or reset buttons. You can execute "poweroff" or "reboot" commands when the installation is over.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.