Hello... As I've reported in another post, my system is locking sometimes. I couldn't yet determine what is the problem, but something strange happened today:
To see what could be the problem, I left the system with xmms running while I was out for 4 hours. When I came back, the keyboard was non-functionl, and nothing worked... Since it's a standalone box, I hadto reset it. I was sort of expecting this (I was actually trying to rule out some applications that could be locking the system) But at startup, it now makes strange complaints, like: modprobe: can't locate module # modprobe: can't locate module are modprobe: can't locate module with But these are parts of commented lines in /etc/modules!!! # /etc/modules: kernel modules to load at boot time. # # This file should contain the names of kernel modules that are # to be loaded at boot time, one per line. Comments begin with # a `#', and everything on the line after them are ignored. (Lines 2, 3 and 4 end with #, are, and with) Later, it will complain about an open " ` " which was not closed. But this is because of the open " ` " in line 5! What could be happening? (I mean, why would it just ignore the comments and treat them like listed modules to be loaded?) It happens no matter which kernel I boot. Anyway, since no modules were being loaded there, that wasn't much of a problem... But I did get also a "can't find modules.dep" mesage later (this is fixed already) I really don't understand what's going on... I suspected that my memory could be bad, but I've compiled lots of big packages (including several kernels, sometimes every two days), for months and never got a sig11. I'm beginning to suspect this may be: - PS/2 mouse (these locks began to happen after I got a new mouse) - X 3.3.6 (no problems happened with X 4) - video card (SiS 6326 AGP) This system (woody) worked fine for months... Could one single package that I've upgraded lock X? (well X itself was upgraded recently...) (It locked with kernels 2.4.0-test5, 2.2.16 and some other that I don't remember...) Not that I didn't expect to have crashes running woody, but... Locks like this? Is this common? Next thing I'll do is to compile X 4.0.1 and see if the problem goes away. If it does, then (and I'd be surprised) it'd be an X-3.3.6 problem... I have to confess I am confused... Thanks for any ideas. J. -- Jeronimo Pellegrini Institute of Computing - Unicamp - Brazil http://www.ic.unicamp.br/~jeronimo mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
