On Sat, 19 Jan 2002 03:39:02 GMT, Marc Williams staggered into the Black
Sun and said:
Quote:> I've trying out some ripping software and having some serious
> problems. Since the same problem exists with two different apps, I'm
> beginning to wonder about my hardware..... I've used both RipperX and
> Grip on the front with both running cdparanoia for the ripper
Um, the front end doesn't matter here. If they're both running
cdparanoia, then either there's a problem with cdparanoia or a problem
with the hardware. Or a problem with Redhat 7.1's kernel's interaction
with your hardware.
Quote:> Whether just ripping or ripping/encoding, my machine will lock up tight
> after one or two songs. No errors showing on the screen or terminal.
> Just a frozen cursor.
After the reboot/fsck, are there any error messages in the system logs?
That's /var/log/messages . Do you have DMA turned on for your CD-ROM?
(hdparm /dev/hdX will tell you if that's the case) Turn it off if you
can, very few CD-ROMs are fast enough to require it and some can't
handle DMA. Which kernel are you using? Redhat 7.1's stock kernel is
old, and should be upgraded since there are lurking performance and
security problems with 2.4.2-redhatsomething.
> I've tried several different CDs. All my other software (cdplay,
> xmms, etc) seems to play my CDs just fine. Running Redhat 7.1 with a
> standard atapi CD player, Maxtor, I think.
> Any ideas on the best way to start diagnosing this? Thanks!
You might want to try this: Add the following line to /etc/syslog.conf
then "killall -HUP syslogd", then start the ripping process. Right
after it starts, Ctrl-Alt-F10 to get to /dev/tty10 , where you will see
any kernel error messages immediately. That might give you a clue about
whether the hardware is failing or whether it's a kernel bug.
Matt G|There is no Darkness in Eternity/But only Light too dim for us to see
Brainbench MVP for Linux Admin /
http://www.brainbench.com / "He is a rhythmic movement of the
-----------------------------/ penguins, is Tux." --MegaHAL