Booting Slackware 9.1 errors
 

Here's what I'm getting while everything is executing in the beginning:

If I control-d a few more lines a appear and a reboot it executed.

How are you shutting down your computer? I hope you're not just hitting the power button. Also, you're using ext2(as indicated by your fstab in a different post), any particular reason for that?

ext2 was recommended by another user which I begin not to like after recommending all those seperate partitions, at least that kind of thing wouldn't work to well with smaller amounts of memory. I always logout of user KDE and login to root and do shutdown -.....

This time I changed the etc/ini??? file to runlevel 4 so that KDE would just start up without me having to ask startx. I got my vertical multicolor barage of lines again so I did just shutdown after the system appeared not to be responding graphically.

Rebooting the system several times doesn't help. This has to be manually configured. I don't know what the problem is exactly.

What's wrong with ext2 vs ext3 and the journaling format?

Nothing. Ext3 and whatnot are fine. I saw your fstab and you have about 10 partitions, get rid of them and make 2. 1 big linux one (ext3 or resierfs), and 1 linux swap (or 1 more if you want windows too, make that NTFS though)

You have seperate ones for /usr and /home, I see no reason for this. It is easiest with the least number of partitions.

Hello,

you can use Knoppix and run "e2fsck" from there, and consider to read the manpage! ;)

cu

hp_tux

For e2fsck -? -? /dev/hda3 and just e2fsck this was returned invalid command for bash.

I am a little hesitant about going to NTFS. I will do some googling, but what are some notable disadvantages and advantages to NTFS vs. FAT32?

I don't think I did anything very significant on my Slack so I will reformat to ext3 and I can redo all the configurations once more. I read that ext3 is more convenient for situations like the one I posted about. Can ext3 systems be both read and writen by ext2 systems?

I created a partition for /usr and /home so that if my /root and other system folders crash I can reformat and reinstall that part while retaining such things as programs and all my personal non-system files. I'm using a 512M swap with 310M RAM on my board.

I also have other partitions(18GB 9/10ths of another HD) for files and documents formated to fat32 so that they are accessible not just to Windows XP but to 95(maybe?), 98, 98SE, ME, 2k, XP. I do want both read and write capabilities. Does Linux have read/write capabilities with NTFS?

Hello,

you have to be "root" for doing this, e.g. with "sudo".

cu

hp_tux

I was logged in as root.

Hello,

mmh, then you may try
cu

hp_tux

/sbin/e2fsck runs successfully, now what commands will repair what I have?

Also, what is this sbin folder for Slackware?

Hello,

well, you may try
("/dev/hda2" is just an example!)

But I don't guarantee for it, you should read the manpage!

Sorry, but I don't understand the question!

cu

hp_tux

I wanted to know what sbin is used for. Is it a backup of bash?

Okay I pressed yes to a lot of questions about clearing and fixing inodes. I booted KDE but now my left speaker--yes just my left one-- is whistling very loudly. Were files or config files for modules possible corrupted? I don't understand why it's so easy to damage partitions by cutting power.

I still get bad sound now, after having the driver work correctly before the accident. I reinstalled the driver module, too.

root@home:/home/user# cd /home/user/riptide-0.6lnxtbeta03122800
root@home:/home/user/riptide-0.6lnxtbeta03122800# make uninstall
if [ -x /usr/sbin/ripconfig ]; then \
/usr/sbin/ripconfig -remove; \
else \
true; \
fi

Removing RIPTIDE drivers from /lib/modules/2.4.22/misc/
make[1]: Entering directory `/home/user/riptide-0.6lnxtbeta03122800/scripts'
rm -f \
"/usr/sbin/ripconfig" "/usr/sbin/ripstop" \

make[1]: Leaving directory `/home/user/riptide-0.6lnxtbeta03122800/scripts'
make[1]: Entering directory `/home/user/riptide-0.6lnxtbeta03122800/modules'
rm -rf "/usr/lib/riptide/config.mak" "/usr/lib/riptide/modules"
make[1]: Leaving directory `/home/user/riptide-0.6lnxtbeta03122800/modules'
rm -f /usr/lib/riptide/LICENSE /usr/lib/riptide/riptide.hex
root@home:/home/user/riptide-0.6lnxtbeta03122800# make install
make[1]: Entering directory `/home/user/riptide-0.6lnxtbeta03122800/scripts'
install -m 755 ripconfig ripstop /usr/sbin
make[1]: Leaving directory `/home/user/riptide-0.6lnxtbeta03122800/scripts'
make[1]: Entering directory `/home/user/riptide-0.6lnxtbeta03122800/modules'
rm -rf "/usr/lib/riptide/config.mak" "/usr/lib/riptide/modules"
mkdir -m 755 -p /usr/lib/riptide/modules
prevsum=""; md5sum `find binaries -type f -print` </dev/null | sort | while read sum file ; do \
if [ "$sum" = "$prevsum" ] && cmp -s "$file" "$prevfile"; then \
rm -f "$file"; \
ln "$prevfile" "$file"; \
else \
prevsum="$sum"; \
prevfile="$file"; \
fi; \
done
(cd .. && find config.mak -depth -print | cpio -pdm /usr/lib/riptide)
2 blocks
find . \( -name '*.sh' -o -name '*.[ch]' -o -name '*.mak' -o -name '[Mm]akefile' \) -print | cpio -pdm /usr/lib/riptide/modules
580 blocks
find binaries -depth -print | cpio -pdm /usr/lib/riptide/modules
0 blocks
make[1]: Leaving directory `/home/user/riptide-0.6lnxtbeta03122800/modules'
install -m 444 LICENSE riptide.hex /usr/lib/riptide

To complete the installation and configuration of your RIPTIDE board,
please run "ripconfig" (or "/usr/sbin/ripconfig")
root@home:/home/user/riptide-0.6lnxtbeta03122800# ripconfig
Linux RIPTIDE audio/communication drivers, version 0.6lnxtbeta03122800

WARNING: this is an EXPERIMENTAL BETA VERSION of the RIPTIDE drivers for Linux.
USE AT YOUR OWN RISK! See the file /usr/lib/riptide/LICENSE for details.

Conexant Systems neither distributes nor maintains this package.
PLEASE DO NOT CONTACT CONEXANT REGARDING THIS SOFTWARE!!!

If you require assistance or need more information, go to:
http://www.linuxant.com/drivers

When reporting a problem for the first time, please send
us the file generated by "ripconfig --dumpdiag".

This package does not contain pre-built modules suitable for your system:
Distribution: Slackware-Slackware
Kernel arch: i686
Kernel version: linux-2.4.22

Trying to automatically re-compile the modules..
(this requires a C compiler and proper kernel sources to be installed)

Where is the linux source build directory that matches your running kernel?
[/lib/modules/2.4.22/build]

Re-compiling RIPTIDE modules for kernel 2.4.22, using source directory
/lib/modules/2.4.22/build. Please wait..
Re-compilation and installation of RIPTIDE modules succeeded.

RIPTIDE module configuration completed.

root@home:/home/user/riptide-0.6lnxtbeta03122800#