> Okay, cool. Make sure that the /etc/lilo.conf line looks exactly like
> this:
>
> append="mem=64M"
>
> Also, after you check that or make the changes, run /sbin/lilo to write
> the boot block back out with the updates. Maybe that got missed after
> the previous change?
Okay, new problem.
KDE seems to crash on me a lot (I was working with kpackage). After one
crash, I was working with the PPP interface, when suddenly, the shell
crashed on me with a big stack error.
When I reboot, it checks the hard disks, then it says, "/dev/hd1:
Duplicate/bad block(s) in inode 22600:/dev/hd1: and it lists off a lot
of other blocks with a similar label.
After a bunch of errors, it concludes with, "/dev/hd1: UNEXPECTED
CONSISTENCY; RUN fsck MANUALLY. (i.e. without -a or -p options)
In red, it concludes with, [FAILED].
Basically, it's a corrupted filesystem, I think. So how do I run fsck
and fix it?
--
/-|rcana
----- ----- * ----- -----
Araby Weyr Fandom: http://members.tripod.com/~Araby/
Tales of Midgar- FF7: http://members.tripod.com/~ArcanaTxM/
Xenogears Interactive Fiction: http://members.tripod.com/~project_xat/
Xenogears - Guardian Angels: http://www.zenogias.com/Guardian
