DebianThis forum is for the discussion of Debian 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 the Debian package kernel-image-2.4.27-2-586tsc on my old laptop (133MHz Pentium), in order to get better apm and acpi support (which I did). However, two weird things happen during boot: somehow, I've lost all my pcmcia support (and thus my internet connection), and now the computer thinks that I have an ext3 filesystem (I have an ext2 filesystem for speed). It sits there for about five minutes trying to figure out why it can't read the filesystem, until it realizes that it's not ext3. How do I stop this? Also, how do I get my pcmcia drivers back?
I've looked into the /lib/modules/2.4.27-2-586tsc/kernel/fs directory, and noticed that I have an unneeded ext3 driver. Should I remove this? Will this solve the problem?
Please let me know what files you may need to see.
The slowdown occurs when the boot process tries to check partitions of /dev/ide/host0/bus0/target0/lun0. It keeps complaining that there is a dma_timer_expiry error. It finishes several (failed) checks by stating that it cannot find an ext3fs. It continues as usual from there.
The modprobe fails, saying it can't find module *.
No menu is present (I think it was automatically disabled when I installed the new kernel), but the old kernel is still present--it's an option in /etc/lilo.conf, if the first kernel fails to boot. However, commenting out the first kernel's presence in the /etc/lilo.conf file doesn't cause the old kernel to boot
EDIT: Never mind. /sbin/lilo -v worked after I commented out the new kernel image. Downloading pcmcia packages...SUCCESS!
EDIT: Still, though--how do I configure my computer to mount my root file system as ext2? I did a bit of research and it seems that kernels 2.4 and above assume the ext3fs, and (if it cannot mount the root file system) it will try to mount it as ext2 (in case of failure). It seems that my kernel tries to mount the root file system as cramfs, and when that fails, it tries ext2. I want the kernel to try ext2 first. I've already tried adding "rootfstype=ext2" to the append field of the kernel image in lilo.conf, but that resulted in a kernel panic. How do I make the kernel assume ext2?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.