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.
Onboard video sharing system RAM accounts for the <256M of RAM.
What I did was fully prep the disk with formatted partitions and Grub installed. My hope was to get installation started without burning anything, which I commonly do with other distros by loading the NET installation versions of kernel and initrd with Grub, and installation parameters splash=0 disable=lx vga=791 noresume. Grub loaded kernel and initrd easily enough, but 5.5 seconds later, the kernel panic resulted. A follow-up try with video=1440x900 instead of vga=791 produced a similar panic, and exit code=0x00000004, but in 80x25 mode, so all lines but one before "Call Trace" scrolled away.
Is this due to lack of needed configuration, an expected problem with a K6/2, or something else? None of my searches turned up installing AntiX without booting directly from installation media. USB boot is not possible. PC does have CD drive, so I could burn the NET .iso to CD, but would rather have Grub start the party.
The PC ran WinXP OK until its HD died. It's what I used to use to setup my Logitech Harmony remote. All the preparations I did running Knoppix 6.7.1 with 3.0.4 kernel. Memtest86 v4.20 I included in the initial Grub menu as the default. I ran it before booting the AntiX kernel, and multiple clean passes since. It's a creepy slow process, main memory at a breathtaking 181 MB/s, 0.72% the speed of my Kaby Lake's DDR4.
I tried burning the NET .iso to CDRW. It failed to boot. So I wasted a CD-R. Grub works, but kernel panic with exit code 0x00000004 came after 6.4s, with the details scrolled off top of screen in 800x600 mode. Retry in 1024x768 reproduced OP panic data.
Puppy I don't like, having used it more than I would have if something else was as easy to download and burn ready to run DFSee, which is the only partitioner I've used for partition management for more than two decades. It's what DFSee .isos are provided with.
I tried installing several old knoppix versions, 4.0.2, 5.0.1, 5.1.1, 6.0.1, 6.4.4, 6.7.1 & 7.2.1. All the older ones errored in one way or another running knoppix-installer or knx-hdinstall, while the newer ones don't have an installer I could identify.
Next I tried Debian. I had to go back to Wheezy/7 to find an installer kernel that didn't halt for lack of CMOV. Now that it's running it should be easier to setup testing of others on remaining partitions reserved for the purpose, possibly including a bug report it could be used to follow up on on the AntiX kernel panic.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.