On Sat, 13 Dec 2003, Michel [ISO-8859-1] Dnzer wrote:
On Sat, 2003-12-13 at 23:04, Fred Heitkamp wrote:
Can someone explain why the business is in the source file?
It's a merge conflict. (It's a good idea to check the output of cvs up
for lines starting with a capital C for conflict)
I
On Tue, 9 Dec 2003, Michel [ISO-8859-1] Dnzer wrote:
On Fri, 2003-12-05 at 13:11, Fred Heitkamp wrote:
I set the AGP mode to 2. Setting the mode to 2 seemed to allow X to run
continuously the longest without locking up. In fact I used mode 2 all
day and I don't believe X11 ever locked
On Wed, 3 Dec 2003, Andrew P. Lentvorski, Jr. wrote:
On Wed, 3 Dec 2003, Alexander Stohr wrote:
I tried just leaving the display running without doing anything
interactive with the interface and X ran for several hours before
freezing. All that was running was Xscreensaver. I then
maybe there is just a power save flaw,
ACPI has been significantly reworked, and I think it's on by default
now. ACPI BIOS implementations are also notoriously buggy. ACPI can also
affect your IRQ routing etc, so if you're using it you might want to try
turning it off and seeing what happens.
I suppose I could have a hardware problem, since my PC is a
couple years
old now. However, I can leave the same computer just running a 2.4.x
kernel for days with no problems. Would the redesigned kernel
2.6.x bang the hardware so much more; going beyond that of
kernel 2.4.x?
It can be
On Wed, 3 Dec 2003, Alexander Stohr wrote:
I tried just leaving the display running without doing anything
interactive with the interface and X ran for several hours before
freezing. All that was running was Xscreensaver. I then tried
again using
X normally but with a different window
FH I suppose I could have a hardware problem, since my PC is a couple years
FH old now. However, I can leave the same computer just running a 2.4.x
FH kernel for days with no problems.
HZ is 1000 by default in 2.6; the different scheduling might perhaps
cause a deadlock somewhere. Can you try
I tried just leaving the display running without doing anything
interactive with the interface and X ran for several hours before
freezing. All that was running was Xscreensaver. I then tried
again using
X normally but with a different window manager (XFCE 4) and
it worked for
about an
On Wed, 3 Dec 2003, Alexander Stohr wrote:
I tried just leaving the display running without doing anything
interactive with the interface and X ran for several hours before
freezing. All that was running was Xscreensaver. I then tried
again using
X normally but with a different window
On Sat, 2003-11-29 at 21:03, Fred Heitkamp wrote:
On Sat, 29 Nov 2003, Michel [ISO-8859-1] Dnzer wrote:
On Fri, 2003-11-28 at 19:27, Fred Heitkamp wrote:
name of display: :0.0
display: :0 screen: 0
direct rendering: No
server glx vendor string: Brian Paul
server glx version
On Sat, 29 Nov 2003, Michel [ISO-8859-1] Dnzer wrote:
On Fri, 2003-11-28 at 19:27, Fred Heitkamp wrote:
name of display: :0.0
display: :0 screen: 0
direct rendering: No
server glx vendor string: Brian Paul
server glx version string: 1.4 Mesa 4.0.4
Current XFree86 CVS is based on
On Fri, 2003-11-28 at 19:27, Fred Heitkamp wrote:
name of display: :0.0
display: :0 screen: 0
direct rendering: No
server glx vendor string: Brian Paul
server glx version string: 1.4 Mesa 4.0.4
Current XFree86 CVS is based on Mesa 5.0.x, it seems to be picking up
the wrong libGL?
(**)
12 matches
Mail list logo
