1 |
The problem is the following, that the same crap happen on Windows as |
2 |
well. I got there bluescreen after a while. |
3 |
|
4 |
I made a memory test, and let it run over 50% of over all tests, and no |
5 |
error displayed (perhaps I let it go more then hours). |
6 |
|
7 |
|
8 |
However, I don't really believe that it is a memory issue.... |
9 |
|
10 |
Next month I get myself a new machine.... |
11 |
|
12 |
|
13 |
Long time thought to get rid of my old Core2Duo which I am using now |
14 |
more then 6 years. |
15 |
|
16 |
|
17 |
Cheers |
18 |
|
19 |
|
20 |
Tamer |
21 |
|
22 |
|
23 |
Am 27.05.2013 17:38, schrieb Fast Turtle: |
24 |
> On Sun, 26 May 2013 18:36:55 -0500 |
25 |
> Dale <rdalek1967@×××××.com> wrote: |
26 |
> |
27 |
>> |
28 |
>> |
29 |
> All of these are good general diagnostic suggestions but from what was said, I suspect it's the kernel radeon driver as I've had the same problem. If he's got a radeon card, then he needs at least the linux-firmware and change the krenel setting to build the radoeon as a module/rebuild kernel and modules. Problem solved - I'm not sure what's borked in the kernel module but it affects all versions in portage |
30 |
> |