09-22-2025, 11:26 PM
(This post was last modified: 09-23-2025, 12:26 AM by Plunkyy.
Edit Reason: new update
)
I'm trying to install Damn Small Linux on a Thinkpad 600X with a 650Mhz speed-step Pentium 3 processor. I'm booting off a cd-rom, and I've tried to install it about 8-10 times now. The first or second time, I managed to get all the way through the installer, but it said that it failed to install grub. I just rebooted and tried it again in hopes it would fix itself the next time (with default settings). This obviously didn't work.
The past few installs I've tried have all crashed somewhere in the 19-23% range, with the most recent step being "Copying new system" in the live log. I've let the installer verify the installation media most times, and never had an error. So I don't think that my CD-ROM drive is faulty, but I could be wrong. I will also note that as of writing this, the most recent crash was at 23%, which I left the live install on after it crashed, and a few minutes later my 600X graphics went haywire for a minute or so. After that, it went to a black screen (still on!) and then rebooted into the live environment by itself! The uptime was still counting after this as well so the machine never actually rebooted...
Anyways, I'm just looking to at least narrow down the problem here. I'm (trying) to install to a 64GB Yansen IDE SSD which is almost certainly just a pre-assembled msata to ide converter. Other than the SSD and the CD-ROM, I'm not really sure what the issue could be. I don't really understand why it could go through the entire installation the first time, but now it can't. I also don't understand why the graphics glitches out when I shut the laptop down, or when it happened in the previous paragraph on its own. It has a Neomagic MagicGraph256ZX GPU with 4mb of VRAM. The live installer responds well so the graphics is definitely supported in the kernel. I dunno.
Appreciate any suggestions
EDIT: I managed to pass the 19-23% crash range by booting with failsafe graphics. I got back up to the point where grub installation fails. Then, I entered the rbind commands for /proc, /sys, etc. so that I could use lsblk in chroot of /mnt/antiX. This let me chroot in and manually run grub-install and update-grub commands. Then, I rebooted and got the following error:
"fsck.ext4: error while loading shared libraries: libuuid.so.1: cannot open shared object file: No such file or directory. fsck exited with status code 127". It's a little hard for me to debug exactly what's wrong because I'm not sure what exactly happened during the automated installation process.
The past few installs I've tried have all crashed somewhere in the 19-23% range, with the most recent step being "Copying new system" in the live log. I've let the installer verify the installation media most times, and never had an error. So I don't think that my CD-ROM drive is faulty, but I could be wrong. I will also note that as of writing this, the most recent crash was at 23%, which I left the live install on after it crashed, and a few minutes later my 600X graphics went haywire for a minute or so. After that, it went to a black screen (still on!) and then rebooted into the live environment by itself! The uptime was still counting after this as well so the machine never actually rebooted...
Anyways, I'm just looking to at least narrow down the problem here. I'm (trying) to install to a 64GB Yansen IDE SSD which is almost certainly just a pre-assembled msata to ide converter. Other than the SSD and the CD-ROM, I'm not really sure what the issue could be. I don't really understand why it could go through the entire installation the first time, but now it can't. I also don't understand why the graphics glitches out when I shut the laptop down, or when it happened in the previous paragraph on its own. It has a Neomagic MagicGraph256ZX GPU with 4mb of VRAM. The live installer responds well so the graphics is definitely supported in the kernel. I dunno.
Appreciate any suggestions
EDIT: I managed to pass the 19-23% crash range by booting with failsafe graphics. I got back up to the point where grub installation fails. Then, I entered the rbind commands for /proc, /sys, etc. so that I could use lsblk in chroot of /mnt/antiX. This let me chroot in and manually run grub-install and update-grub commands. Then, I rebooted and got the following error:
"fsck.ext4: error while loading shared libraries: libuuid.so.1: cannot open shared object file: No such file or directory. fsck exited with status code 127". It's a little hard for me to debug exactly what's wrong because I'm not sure what exactly happened during the automated installation process.