hey all,
im using redhat9 and i was trying to install k3b cdburning app via rpm. i got a falied dependancies flag for libmad and id3lib. i dled these. libmap compiles no prob, but soon after computer freezes. i think hmmmm and restart. next i try to compile id3lib, after make computer freezes again, i restart, run make install, thats done, i try the rpm again, same flag. so i figure ill try the source for k3b. dowload the source, configures ok, i type make, halfway through i freeze. now im freaking out. i go to linuxquestions.org, im posting a question, i freeze, i reboot and here i am now, waiting for another freeze to come. ive been using linux for a few months now and i love it, but in this situation i have no idea what to do? is the crash rcoded is syslogs maybe? someone help pls tia!! 1 more thing, when i freeze my caps and scroll lock keys blink over and over. any ideas?

I wouldn't think that libmad or
id3lib should have this effect,
not if you're not utilizing any
mp3/sound applications.

Did you upgrade any crucial system
libraries recently?

The blinking keyboard lights mean
that a kernel panic has happened.

You could try to boot into single user
mode after the next crash, and examine
the log-files in /var/log

Look at the most recent ones
You'll find the listed sorted by the most
recent at the bottom that way.

Good luck!
Tink

hey man thanks for replying. i checked my logs i have a ton of i8253 count too high! resetting.., altho these date back to way before i was having any problems. ive been logged in as root user for a while now with no problems, so i think its something specific to that account. the only other thing i did today is unmount cdrom1. i did recently try to upgrade my glib, altho this was a few days ago and i havent had problems till today, also this would affect all users not just my account right?

Odd ... Yes, glibc would screw up everything :)
The fact that it worked for a few days ... oh, well,
I'm at loss ... did you reboot after the install?

If it was something specific to that account that's
weird, too, because a user space application of
any kind shouldn't have the capabilities to crash
the machine. In this account, when you encounter
crashes, does this happen randomly or can you
see any patterns, like in "If I use xmms, it dies"?

Another thing to do would be to create another
normal user account and toy around in that one.

HIH.

Cheers,
Tink

i think it got it worked out. red hat 9 xmms doesnt come with mp3 coding support, so i installed an encoder so it would work. i think it was xmms causing the crash, the previously installed filter conflicting with libmap maybe? the funny thing is, if there is an audio cd mounted in my drive xmmx always pops up here and there trying to play it, which is annoying. anyway i def considered it could be part of the problem, so i killed it, but failed to realize it might pop up again in a while. i ran make uninstall on those libs reboot and ive ben running alright for a while. this is however just a theory, another one maybe being the source was labeled for i386, i run 686, i figure all x86 are the same, it usually doesnt matter, but in this case there was one specifically listed for 686, which i dont understand why i didnt just pick it in the first place. also, if it helps my log displayed this message several times which coincided with my crashes:
Nov 12 02:04:45 localhost kernel: ATAPI device hdb:
Nov 12 02:04:45 localhost kernel: Error: Illegal request -- (Sense key=0x05)
Nov 12 02:04:45 localhost kernel: Invalid command operation code -- (asc=0x20, ascq=0x00)
Nov 12 02:04:45 localhost kernel: The failed "Get Configuration" packet command was:
Nov 12 02:04:45 localhost kernel: "46 02 00 1e 00 00 00 00 08 00 00 00 "
Nov 12 02:04:49 localhost kernel: hdb: packet command error: status=0x51 { DriveReady SeekComplete Error }
Nov 12 02:04:49 localhost kernel: hdb: packet command error: error=0x54

to mee it looks like something with the cdrom? i dunno im such a noob.

I've seen errors like that on older
PII motherboards ... solution was
to turn of DMA for the CD-ROM.

Not sure whether that would fix
that issue for you ...

Cheers,
Tink