| 1 |
Christian Parpart wrote: |
| 2 |
|
| 3 |
>On Monday 16 May 2005 3:49 pm, Christian Parpart wrote: |
| 4 |
> |
| 5 |
> |
| 6 |
>>On Monday 16 May 2005 3:29 pm, Eric Thibodeau wrote: |
| 7 |
>> |
| 8 |
>> |
| 9 |
>>>Hi Chrisitian, |
| 10 |
>>> |
| 11 |
>>> You might want to take a look at the Linux kernel amilling list. One of |
| 12 |
>>>my friends had issues with his dual Xeon and 4Gigs of RAM. In his case, |
| 13 |
>>>Windows would claim to see the 4Gigs but would actually crassh when he |
| 14 |
>>>actually came to use more than 3...sounds fammiliar? |
| 15 |
>>> |
| 16 |
>>> In Linux, he'd get a kernel panic on boot (2.6.x kernels)...after over 6 |
| 17 |
>>>months of poking at forums and the LKML, his bug was officially received |
| 18 |
>>>as valid from the kernel gurus and eventually fixed.... |
| 19 |
>>> |
| 20 |
>>>hope this helps a little in your investigation... |
| 21 |
>>> |
| 22 |
>>> |
| 23 |
>>Aiiii! doesn't sound that good, however, better having a bug from blocking |
| 24 |
>>me my 4th GB than a statement like "just just can't" :) |
| 25 |
>> |
| 26 |
>>I'm following the LKML not that long yet to have cought up your friends |
| 27 |
>>message, but I'll try a new thread then. |
| 28 |
>> |
| 29 |
>> |
| 30 |
> |
| 31 |
>THANKS ALL! |
| 32 |
> |
| 33 |
>The problem has been a misconfigured BIOS setup. Well, It was already |
| 34 |
>misconfigured as I received the machine by my local shop. However, setting |
| 35 |
>Memhole to "Software" has fixed this issue for good :-D |
| 36 |
> |
| 37 |
>(Now I can start coding mem-eating apps ^o^) |
| 38 |
> |
| 39 |
> |
| 40 |
cool. for this reason I always load the defaults of the bios of each |
| 41 |
system I build (and I usually flash to the latest stable bios too). |
| 42 |
|
| 43 |
hope it all goes well for you :) |
| 44 |
|
| 45 |
>Thanks, |
| 46 |
>Christian Parpart. |
| 47 |
> |
| 48 |
> |
| 49 |
> |
| 50 |
-- |
| 51 |
gentoo-server@g.o mailing list |
Archives