BTW I noticed there is now an rc2 forum so I guess this thread should be moved there.
I finally got it to boot properly using the following grub menu.lst configuration:
- Code: Select all
KERNEL vmlinuz
APPEND nfsdir=10.0.0.1:/mnt/iso nodhcp lang=us ramdisk_size=100000 init=/etc/init apm=power-off nomce vga=771 initrd=initrd.gz BOOT_IMAGE=knoppix fromhd=/dev/sda2
This was passed to the 3110ct via PXE, thus the odd stuff. vmlinuz and initrd.gz were in /tftpboot on the knoppix machine. I found it was just quicker and easier to edit and save the menu.lst file on the knoppix machine than it would have been to continually modify grub on the laptop.
I think the only thing I did differently was specify the ramdisk size, but I don't remember exactly how I had it set up yesterday.
Anyway antiX is running much, much better now that I got that straightened out and the installer no longer locks up. Takes care of that mystery. There are a couple of issues though.
Just to clarify the situation, here is how I am booting:
3 partitions on HDD
sda1 empty
sda2 has previous /home data, antiX iso, and /mepis from iso
sda3 512mb swap
1st issue is that I cannot seem to get the iso to boot. I had thought that's what I had been doing, but it turns out I was booting from the /mepis directory. If I delete the mepis info from /mepis and specify fromiso=/dev/sda2/antix-M7-rc2.iso in grub, it will not boot. Not sure what's going on there. When I was using fromiso yesterday, it was actually scanning all devices until it found /mepis on /dev/sda2, not actually booting from the iso.
2nd issue... After booting from /mepis on sda2, I attempted to install antiX using sda1 as root, sda2 as /home and sda3 as swap (had to select none/existing since the LiveCD
is using it). The problem is that since I booted from sda2, the process fails when the installer tries to re-mount sda2 as /home. Would be nice to be able to boot from sda2 and also specify it as /home in the installer. For now I will simply move /home there once the install is finished.
Very minor issues, I think, and not ones that people will ever encounter if they are able to actually just boot from the CD like normal. The installer is still chugging along smoothly right now.