I was going thru text rescue mode on a debian lxde disk. Before, it always called my disks hda hdb(hard drives) and sda(flash drive). Thru rescue mode, it called them sda,sdb,(hard drives) and sdc(flash drive I booted from). Could someone tell me why this is?

Lilo worked when I installed debian but not when I installed crunchbang. I'm pretty sure I chose the same settings on both installations. On the debian lilo, I don't think it said the following

Initial ramdisk loads below 4Mb; kernel overwrite is possible ..............................................................
BIOS data check successful
Probing EDD (EDD=off to disable)

Decompressing Linux... Parsing ELF...

Both installers looked pretty much the same since crunchbang is based on debian. I'll probably just go back to debian xfce or something, unless someone knows why.

I would like you to try another kernel, and another ramdisk. You'll probably solve it that way. And I wouldn't worry about lilo. Do you need a ramdisk? If your basics (root filesystem format, chipset, pc partition tables support) are compiled in, you don't need a ramdisk.

I don't think it's a lilo fault. Lilo is finished.

1 members found this post helpful.

I am pretty sure I know what a kernel is. Are you recommending going to a earlier kernel? Tho I wouldn't know how to change it without changing installation discs. The only thing I've ever compiled is java.

The only thing I know about a ramdisk is it might have something to do with the file initrd.img.gz.

You would have walk me thru either of these. I don't think Lilo is finished since it worked for me when grub's only option wouldn't. Grub also didn't detect my windows 2000 installation like it was supposed to.

I am writing this from the the computer on debian fvwm-crystal

Just a different one to eliminate the kernel itself as a possible problem. Ditto with ramdisk.

Firefox54, this is post #20. Most problems get fixed much quicker. That tells me something you are taking as OK is not OK. Is there not a choice of kernels on your installation CD? Why not use another of those. You don't need it to finish loading, just to start.

Likewise, leave out the initrd line and see what happens. check for another initrd on your install cd.

1 members found this post helpful.

I don't remember a choice for a kernel or a initrd on the cd. I went through the text installation. I'll leave out the initrd line and try that. If all else fails, debian is working fine.

/Tears hair out.

If DEBIAN is working fine, why not copy over the kernel module tree, and use the DEBIAN kernel & initrd (If there is one) and try that?

1 members found this post helpful.

I would do that, but I got anitx workiing. I am using grub and it is working good. fluxbox/icewm is faster than openbox so I like it better.

Please don't think you've wasted you're time with me. Thru this thread, I've learned how to mount thru the terminal properly, how to update lilo thru the terminal, and more.

I think I'll stick with antix, but don't think you haven't helped me. You've taught me some basic linux commands