Author Topic: Linux error (Read 756 times)

bigguy · « **on:** November 06, 2011, 10:18:29 PM »

I was just using my laptop and Kontact program in Ubuntu Linux. All of a sudden the screen goes black and all these numbers come up. The last line reads something like this:

[1586.396010] CR2: 00000000fffffffc

There is way to much info to post. Tried to take a pic and my phone camera is not working now, damn it. Any help with this or is there an error log I can look at some where.

Nesa · « **Reply #1 on:** November 07, 2011, 01:04:26 AM »

/var/log/messages logs everything on the system, or you can look at the xorg log. should be in var/log as well

bigguy · « **Reply #2 on:** November 07, 2011, 01:17:37 AM »

Ok, will check that tomorrow. not sure why it happened. The screen turned black and it started to scroll a huge list of code and then that line at the bottom. I would think this is hardware related wouldn't you say.

Nesa · « **Reply #3 on:** November 07, 2011, 01:29:57 AM »

I don't know it could be, or it could be a bug in the software.

bigguy · « **Reply #4 on:** November 07, 2011, 01:33:14 AM »

I'll post back when I find that log. Thanks Nesa.

bigguy · « **Reply #5 on:** November 07, 2011, 09:55:47 AM »

There is no messages folder. There was a crash folder but nothing in it.

bigguy · « **Reply #6 on:** November 07, 2011, 05:19:17 PM »

In Var/Logs there are a lot of files and folders. WOuld it be in there and what am I looking for.

Nesa · « **Reply #7 on:** November 07, 2011, 05:35:44 PM »

Its called messages with no file extension its a big file.

bigguy · « **Reply #8 on:** November 07, 2011, 05:47:53 PM »

Ok, will look here in a minute. trying to install a program called preload I think it is to speed things up a bit.

bigguy · « **Reply #9 on:** November 17, 2011, 09:35:29 AM »

There is no file or folder called messages under Var/Logs. Could it be somewhere else.

Nesa · « **Reply #10 on:** November 17, 2011, 06:20:02 PM »

It should be in there, I'll install ubuntu and check.

bigguy · « **Reply #11 on:** November 17, 2011, 07:44:04 PM »

K, that would be cool.

Nesa · « **Reply #12 on:** November 22, 2011, 06:14:52 PM »

Look at syslog and Xlog might have a number for Xlog like Xlog.0.log
Also run a system update.

bigguy · « **Reply #13 on:** November 22, 2011, 06:27:55 PM »

will do that now and see what shows up. Thanks again Nesa.

bigguy · « **Reply #14 on:** November 22, 2011, 06:34:29 PM »

Xorg.0.log and .old...syslog syslog.1 and so on are here as well. What program do I open these with.

Nesa · « **Reply #15 on:** November 22, 2011, 09:37:27 PM »

A text viewer

bigguy · « **Reply #16 on:** November 22, 2011, 11:23:08 PM »

lol, any text viewer that works with linux...sorry may seem like a dumb question but I clicked on one and it asked me what to open it with. Didn't know if there was another way to do it in linux.

Nesa · « **Reply #17 on:** November 23, 2011, 01:12:23 AM »

On mine text viewer was the default option

bigguy · « **Reply #18 on:** November 23, 2011, 09:06:01 AM »

Ok, I got syslog open, what am I looking for.

Nesa · « **Reply #19 on:** November 24, 2011, 05:53:43 AM »

It should be time stamped look at any errors around the time of the crash.

bigguy · « **Reply #20 on:** November 24, 2011, 05:44:28 PM »

Ok, I will look closer at it and see what I can find.

Nesa · « **Reply #21 on:** November 25, 2011, 05:03:17 AM »

Do a update the fix most of the bugs quick in *buntu releases

bigguy · « **Reply #22 on:** November 25, 2011, 06:07:32 PM »

I did an update and so far things are all good.

Still will be checking the log files though to see if I can run this down.

Nesa · « **Reply #23 on:** November 25, 2011, 08:18:15 PM »

Good luck