Here's the thing; I never had trouble suspending the console, but I also
never tracked stable or current with that r128 card in. I only ran releases
with updated ports trees. Last time I ran that card was under 4.6-RELEASE
and my experience was that I could suspend on the console or another VT but
Steve Bertrand <[EMAIL PROTECTED]> writes:
> I'm from fbsd-questions, and was advised to post this one here. Please Cc
> me as I'm not yet a member of this list. Thank-you.
>
> I am trying to installworld after a successful cvsup of RELENG_4 and
> buildworld from 4.6. I continuously get:
>
> ins
On Thu, 2003-04-03 at 12:31, Welch, Sean M. wrote:
> I'm familiar with this one -- it isn't agp, it is DRI. DRI depends on AGP
> so you are disabling both when you disable
> AGP. This issue has to do with the DRI module "losing track" of what is
> going on in the usage of main memory
> (through
On Thu, 2003-04-03 at 11:14, David Gilbert wrote:
> I don't know the exact nature of the bug, but compiling in the agp
> driver on my laptop locks up the unit on resume. Runing without agp
> compiled in is fine. The lockup isn't every time ... and it isn't
> solved by suspending and resuming with
No, not at all. Disable DRI in your XF86Config file. One work
around I have used with good success is to start up the server
without DRI enabled (using one XF86Config)and then after that
start up another server (with DRI) for JUST 3D work on another
VT. This is easy enough to do from the comm
> "Sean" == Sean M Welch writes:
Sean> I'm familiar with this one -- it isn't agp, it is DRI. DRI
Sean> depends on AGP so you are disabling both when you disable AGP.
Sean> This issue has to do with the DRI module "losing track" of what
Sean> is going on in the usage of main memory (through
I'm familiar with this one -- it isn't agp, it is DRI. DRI depends on AGP
so you are disabling both when you disable
AGP. This issue has to do with the DRI module "losing track" of what is
going on in the usage of main memory
(through AGP) when you do a suspend resume -- it gets stuck trying to
Yes, and it also says 4.8 was released on 30 Mar 2003. We all know the
schedule always goes through changes. It would be nice if
http://www.freebsd.org/ports/ had a little Status: frozen|unfrozen display.
I guess ill have to make due with this though.
Thanks.
-Original Message-
From: Fran
On Thu, Apr 03, 2003 at 01:38:11PM -0500, Mike Jakubik wrote:
> Hello,
>
> Is there a way to check the status of the ports tree without having to
> subscribe to the ports mailing lists? I'm not interested in all the ports
> chatter, just looking for a way to check if the tree is frozen, etc.
On Thu, Apr 03, 2003 at 01:38:11PM -0500, Mike Jakubik wrote:
> Is there a way to check the status of the ports tree without having to
> subscribe to the ports mailing lists? I'm not interested in all the ports
> chatter, just looking for a way to check if the tree is frozen, etc.
You can c
I don't know the exact nature of the bug, but compiling in the agp
driver on my laptop locks up the unit on resume. Runing without agp
compiled in is fine. The lockup isn't every time ... and it isn't
solved by suspending and resuming with the console active. The
relavant probes are:
apm0: on
Hello,
Is there a way to check the status of the ports tree without having to
subscribe to the ports mailing lists? I'm not interested in all the ports
chatter, just looking for a way to check if the tree is frozen, etc.
Thanks.
___
[EMAIL PROT
n0n4m3 wrote:
current stable ver. is 4.7-STABLE or 4.8-STABLE ?
my version is 4.8-RC there is 4.8 stable yet ?
thx
Kris
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL
On Thu, 3 Apr 2003 00:44:32 -0500
Jean-Daniel <[EMAIL PROTECTED]> wrote:
> Hi everyone, recently I was told on this mailing list that to avoid
> the kde/nvidia bug when closing apps I had to recompile qt with the
> OPENGL=NO option.
>
> I was wondering if there was maybe a little hwoto somewhere
14 matches
Mail list logo
