On Mon, Apr 22, 2002 at 02:52:03PM -0700, Peter Jay Salzman wrote:
> begin Richard S. Crawford <[EMAIL PROTECTED]>
> >
> > Thanks for the tip. I'll remember that. As it is, I'm unable to ping,
> > browse to, ssh to, tel-net to, telepathically link to, or otherwise
> > communicate with the ma
On Mon, 22 Apr 2002, Richard S. Crawford wrote:
> GeForce 2, I believe. I'll check on X when I get home, but I believe it's
> a pretty recent version.
A side check. If you have installed the nvidia modules/drivers for X with
GLX/DR support, under the right conditions in X, you can actually kill
At 03:06 PM 4/22/02 -0700, you wrote:
> > Hrmmm The only thing I can think of are some RH7.2 packages that I
> > installed through Red Carpet the other night.
>
>if we were betting, i would put my money here. what got installed?
Off the top of my head, I don't actually know (blame years of
begin Richard S. Crawford <[EMAIL PROTECTED]>
> At 02:52 PM 4/22/02 -0700, you wrote:
> >begin Richard S. Crawford <[EMAIL PROTECTED]>
> >>
> >> Thanks for the tip. I'll remember that. As it is, I'm unable to ping,
> >> browse to, ssh to, tel-net to, telepathically link to, or otherwise
> >> co
At 02:52 PM 4/22/02 -0700, you wrote:
>begin Richard S. Crawford <[EMAIL PROTECTED]>
> >
> > Thanks for the tip. I'll remember that. As it is, I'm unable to ping,
> > browse to, ssh to, tel-net to, telepathically link to, or otherwise
> > communicate with the machine. I'll try smoke signals nex
begin Richard S. Crawford <[EMAIL PROTECTED]>
>
> Thanks for the tip. I'll remember that. As it is, I'm unable to ping,
> browse to, ssh to, tel-net to, telepathically link to, or otherwise
> communicate with the machine. I'll try smoke signals next.
this is a good indication that the kern
At 11:55 AM 4/22/02 -0700, you wrote:
>Again, by "froze up" you probably mean that the graphical interface was
>unresponsive. There are other things one needs to do to know for sure
>that the kernel has crashed. Often, X will crash, giving a user at the
>console the impression that the machine h
On Monday 22 April 2002 10:53 am, you wrote:
> I'm also not at home with the box right now. I'm trying to log in
> remotely, and unable to do so (though I was able to just an hour ago)...
> there is simply no response from my computer.
As has been discussed, it's good to clarify this. Based on
begin Richard S. Crawford <[EMAIL PROTECTED]>
> At 11:15 AM 4/22/02 -0700, you wrote:
>
> >ok, this might be an indication of a bona-fide kernel crash. that's
> >when linux "stops running". the kernel stops responding to any event.
> >may be a ram problem. doubt it's hard drive related. a u
At 11:15 AM 4/22/02 -0700, you wrote:
>and my response was to tell him how to run a program (type the name in
>at a prompt, possibly prepending a "./" in front of the name). i then
>suggested that he read a general book on using linux.
>
>he basically had a cow. a ... mad ... cow.
Hee hee! I
begin Richard S. Crawford <[EMAIL PROTECTED]>
> At 10:20 AM 4/22/02 -0700, you wrote:
> >richard, at the risk of starting another "tom the bicyclist" thread, i
> >would say that you need to pick up a general book on linux.
> Oh, and who the heck was Tom the Bicyclist?
don't ask -- it was proba
At 10:36 AM 4/22/02 -0700, you wrote:
>begin Peter Jay Salzman <[EMAIL PROTECTED]>
> > richard, at the risk of starting another "tom the bicyclist" thread, i
> > would say that you need to pick up a general book on linux.
Oh, and who the heck was Tom the Bicyclist?
__
At 10:20 AM 4/22/02 -0700, you wrote:
>richard, at the risk of starting another "tom the bicyclist" thread, i
>would say that you need to pick up a general book on linux.
Hee hee. I admit that I kind of panicked on this one. I've heard that:
a. The most common cause of a Linux crash is a
begin Peter Jay Salzman <[EMAIL PROTECTED]>
> richard, at the risk of starting another "tom the bicyclist" thread, i
> would say that you need to pick up a general book on linux.
>
> at a *bare minimum* you need to know how to get information about your
> system. i would say that knowing how to
begin Robert G. Scofield <[EMAIL PROTECTED]>
> On Monday 22 April 2002 09:50 am, you wrote:
> >
> > Rod suggess checking the filesystems to make sure they are not full (good
> > idea too)
>
> When you guys talk about the filesytems being full, do you mean that the hard
> disk is full? I once
richard, at the risk of starting another "tom the bicyclist" thread, i
would say that you need to pick up a general book on linux.
at a *bare minimum* you need to know how to get information about your
system. i would say that knowing how to get basic info about your
system is MORE crucial than,
On Mon, 22 Apr 2002, Robert G. Scofield wrote:
> When you guys talk about the filesytems being full, do you mean that the hard
> disk is full? I once completely filled up a Red Hat system to the point
> where I'd get error messages that it could not write my files because there
> was no room.
If, as Robert suggested, this means roughly the same as a full disk, then
that shouldn't be a problem. Since I had problems with that a couple of
months ago, I'm pretty vigilant on that point.
INSTALLFEST, huh? When's the next one? Didn't I just miss one? ;-)
At 10:04 AM 4/22/02 -0700, you
On Mon, 22 Apr 2002, Richard S. Crawford wrote:
> I know it's not much to go on, but when it comes to this area, that's about
> the limit of my expertise. In all honesty, I'm not even entirely sure
> which system logs to check, or how to check them.
Isolating the problems and establishing what
Richard demonstrates woeful ignorance by saying, "What?"
At 09:13 AM 4/22/02 -0700, you wrote:
>That's not much to go on, but make sure you don't have a
>full filesystem.
___
vox-tech mailing list
[EMAIL PROTECTED]
http://lists.lugod.org/mailman/list
On Monday 22 April 2002 09:50 am, you wrote:
>
> Rod suggess checking the filesystems to make sure they are not full (good
> idea too)
When you guys talk about the filesytems being full, do you mean that the hard
disk is full? I once completely filled up a Red Hat system to the point
where I'
This looks like a job for INSTALLFEST!!
- Original Message -
From: "Richard S. Crawford" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, April 22, 2002 9:20 AM
Subject: Re: [vox-tech] RH keeps crashing
> I know it's not much to go on,
On Mon, 22 Apr 2002, Richard S. Crawford wrote:
> My RH 7.2 box has crashed three times in the past 24 hours. Each time I've
> rebooted, I've run fsck / and gone through the entire check and repair
> process, but I'm obviously missing something.
>
> What else should I be checking?
As Pete sug
I know it's not much to go on, but when it comes to this area, that's about
the limit of my expertise. In all honesty, I'm not even entirely sure
which system logs to check, or how to check them.
I'm just hoping it isn't hardware... I'm not all that keen on replacing my
hard drive. ;-)
At
That's not much to go on, but make sure you don't have a
full filesystem. Otherwise it's most likely hardware.
-- Rod
http://www.sunsetsystems.com/
On Monday 22 April 2002 09:06, Richard S. Crawford wrote:
> My RH 7.2 box has crashed three times in the past 24 hours. Each
> time I've reboot
i dunno. maybe the system logs?
pete
ps- try memtest too.
begin Richard S. Crawford <[EMAIL PROTECTED]>
> My RH 7.2 box has crashed three times in the past 24 hours. Each time I've
> rebooted, I've run fsck / and gone through the entire check and repair
> process, but I'm obviously missing
My RH 7.2 box has crashed three times in the past 24 hours. Each time I've
rebooted, I've run fsck / and gone through the entire check and repair
process, but I'm obviously missing something.
What else should I be checking?
___
vox-tech mailing list
27 matches
Mail list logo
