On 08/21/12 10:22, Ian Smith wrote:
> Those guys were losing 768MB or more, but had plenty to spare. You?
16G so not a big problem, but that doesn't mean I like giving it away...
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/m
On Tue, 21 Aug 2012 09:54:14 -0600, Gary Aitken wrote:
> Having run for a couple of days now without problems,
> I'm guardedly optimistic I've solved this problem.
> It appears the problem had nothing to do with screen blanking.
> The solution was to disable memory mapping in BIOS,
> whose pu
Having run for a couple of days now without problems,
I'm guardedly optimistic I've solved this problem.
It appears the problem had nothing to do with screen blanking.
The solution was to disable memory mapping in BIOS,
whose purpose is to recover the memory addresses reserved for hardware
in old
On 08/19/12 10:11, Ian Smith wrote:
> In freebsd-questions Digest, Vol 428, Issue 7, Message: 4
> On Fri, 17 Aug 2012 13:51:07 -0600 Gary Aitken
> wrote:
> > On 08/16/12 00:04, Matthew Seaman wrote:
> > > On 16/08/2012 05:45, Gary Aitken wrote:
> > ...
> > >> Running 9.0 release on an amd
In freebsd-questions Digest, Vol 428, Issue 7, Message: 4
On Fri, 17 Aug 2012 13:51:07 -0600 Gary Aitken wrote:
> On 08/16/12 00:04, Matthew Seaman wrote:
> > On 16/08/2012 05:45, Gary Aitken wrote:
> ...
> >> Running 9.0 release on an amd 64 box, standard kernel, 16GB, SSD (/,
> >> /usr, /va
On 08/17/12 20:29, Matthew Navarre wrote:
>
>
> On Aug 17, 2012, at 7:00 PM, Warren Block wrote:
>
>> On Fri, 17 Aug 2012, Gary Aitken wrote:
>>
>>> On 08/17/12 14:44, Warren Block wrote:
>>>
If that stops the lockups, then you could try setting each in turn to a
non-zero value (minu
On Aug 17, 2012, at 7:00 PM, Warren Block wrote:
> On Fri, 17 Aug 2012, Gary Aitken wrote:
>
>> On 08/17/12 14:44, Warren Block wrote:
>>
>>> If that stops the lockups, then you could try setting each in turn to a
>>> non-zero value (minutes). Leave everything at zero except for the one
>>
On Fri, 17 Aug 2012, Gary Aitken wrote:
On 08/17/12 14:44, Warren Block wrote:
If that stops the lockups, then you could try setting each in turn to
a non-zero value (minutes). Leave everything at zero except for the
one being tested. But these also seem unlikely, as it's a hardware
signal
On 08/17/12 14:44, Warren Block wrote:
> If that stops the lockups, then you could try setting each in turn to a
> non-zero value (minutes). Leave everything at zero except for the one being
> tested. But these also seem unlikely, as it's a hardware signal from the
> video board to the monito
On Fri, 17 Aug 2012, Gary Aitken wrote:
On 08/16/12 00:04, Matthew Seaman wrote:
On 16/08/2012 05:45, Gary Aitken wrote:
...
Running 9.0 release on an amd 64 box, standard kernel, 16GB, SSD (/,
/usr, /var, /tmp) + HDDs, visiontek 900331 graphics card (ati radeon
hd5550).
As long as I am usin
On 08/16/12 00:04, Matthew Seaman wrote:
> On 16/08/2012 05:45, Gary Aitken wrote:
...
>> Running 9.0 release on an amd 64 box, standard kernel, 16GB, SSD (/,
>> /usr, /var, /tmp) + HDDs, visiontek 900331 graphics card (ati radeon
>> hd5550).
>>
>> As long as I am using the system, things seem to b
On Wed, 15 Aug 2012 22:45:47 -0600
Gary Aitken wrote:
> I've been struggling trying to ignore something and it refuses to go
> away :-(.
>
> Running 9.0 release on an amd 64 box, standard kernel, 16GB, SSD
> (/, /usr, /var, /tmp) + HDDs, visiontek 900331 graphics card (ati radeon
> hd5550).
>
On 16/08/2012 05:45, Gary Aitken wrote:
> I've been struggling trying to ignore something and it refuses to go
> away :-(.
>
> Running 9.0 release on an amd 64 box, standard kernel, 16GB, SSD (/,
> /usr, /var, /tmp) + HDDs, visiontek 900331 graphics card (ati radeon
> hd5550).
>
> As long as I am
I've been struggling trying to ignore something and it refuses to go away :-(.
Running 9.0 release on an amd 64 box, standard kernel, 16GB, SSD (/, /usr,
/var, /tmp) + HDDs, visiontek 900331 graphics card (ati radeon hd5550).
As long as I am using the system, things seem to be fine. However,
14 matches
Mail list logo
