antiX / MX LinuxThis forum is for the discussion of antiX and MX Linux.
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.
I installed Antix as a spare OS on my elderly laptop. No backup exists, because I expected to format this, install some despicable OS and give it to some deserving soul who needed it, but was incapable of learning linux. I know a few of those. But that hasn't happened.
To make a long story short, I'm on MBR & lilo here with Slackware. AntiX has sda6, and shares sda1 (/boot) with Slackware. sda1 was hosed, which makes it hard to boot AntiX. I have the AntiX-23_x64.iso here.
So I found a likely looking kernel & initrd on the iso, put them in lilo, and tried booting. It halted for the lack of linuxfs
I can see linuxfs there, but it's 1.6 GB and very big for a ramdisk unless it's for the install procedure. AntiX is installed - I just want my kernel & initrd back.
/boot is all slackware, except initrd1.gz and vmlinuz1, just to avoid name confusion with slackware. Taken from the iso antiX/ directory, antiX/vmlinuz (the bigger one) is now /boot/vmlinuz1. I tried them both.
So I found a likely looking kernel & initrd on the iso, put them in lilo, and tried booting. It halted for the lack of linuxfs
I don't see how that could work as I don't believe lilo is capable of booting an iso file directly. Are you wanting to boot the AntiX iso or are you trying some way to rescue the install on sda6? If you want to use the AntiX iso, extract (loop mount) the AntiX iso to a directory and copy the entire contents of the directory to sda6 (overwriting everything there) or to another empty partition slightly larger than the iso file. The entry below will boot AntiX (the extracted iso) from sda6 using Grub2. Since you are familiar with lilo, I expect you should be able to convert it to boot from Lilo.
Quote:
menuentry "ANtiX" {
set root='hd0,6'
linux /antiX/vmlinuz quiet splash --
initrd /antiX/initrd.gz
}
The 'linuxfs' file is the compressed filesystem for AntiX and is used when booting the live system.
Does Slackware boot? Did you use grub at one time as the bootloader and if so why did you switch to lilo?
Post the contents of /etc/elilo.conf
What is in the boot directory on sda6?
What is in /etc/fstab on sda6?
Last edited by colorpurple21859; 01-01-2024 at 04:21 PM.
I must confess to misleading the AntiX installer, because I want the main system to have mastery of the boot loader, and each distro thinks they are in charge. Not only that, but each distro don't know about the other ones. So there's mayhem regularly on updates. AntiX wasn't told about the /boot partition, so I had a /boot directory in AntiX's root drive with everything there. So I just copied over to sda1 again, and everything works.
Sorry for not getting my brains in gear a little earlier on this. The tricky bit was that lilo.conf is new, because grub got wiped out as well.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.