Am Freitag 24 August 2007 schrieb Niels Larsen:
On Friday 24 August 2007 02:35:29 Chris Ahlstrom wrote:
At last I installed a driver direct from nvidia's site, following their
instructions:
http://www.nvidia.com/object/linux_display_amd64_100.14.11.html
It worked, and I got kde up and
On Fri, Aug 24, 2007 at 12:48:29AM +0200, Michael wrote:
I just tweaked all ext3 partitions to something like
/dev/sda10 / ext3noatime,nodiratime,errors=remount-ro 0 1
to see what will happen. (The option data=writeback caused boot trouble)
So far, anything unchanged but
On 08/23/07 04:07:46PM -0700, [EMAIL PROTECTED] wrote:
Quoting Jim Crilly [EMAIL PROTECTED]:
On 08/23/07 10:03:24AM -0700, [EMAIL PROTECTED] wrote:
The problem of zeroing files of XFS still exists, however its not some
mythical type of corruption. You'll only see it on files recently
On Thu, Aug 23, 2007 at 09:47:13PM -0500, Neil Gunton wrote:
Eh? I've been using replication for years now. It works out of the box,
rock solid, and nothing special on the backend at all. Master produces
binary log, which is replayed on the slave(s). Nothing questionable
about it, it's used
On Fri, Aug 24, 2007 at 01:04:16AM +0200, Michael wrote:
Do you know if the kernel tries to balance load really equally ?
For my 2core AMD64 it seems cpu0 has to be about 70% before cpu1 gets
involved.
Another idea is, i always see cpu0 is the most busy one. But wouldn't
switching the
On 08/24/07 01:04:16AM +0200, Michael wrote:
Lennart,
probably don't have any good reason to. The scheduler does a great job
Do you know if the kernel tries to balance load really equally ?
For my 2core AMD64 it seems cpu0 has to be about 70% before cpu1 gets
involved.
Another idea
On Fri, Aug 24, 2007 at 02:53:49AM +0200, Niels Larsen wrote:
On Friday 24 August 2007 02:35:29 Chris Ahlstrom wrote:
At last I installed a driver direct from nvidia's site, following their
instructions:
http://www.nvidia.com/object/linux_display_amd64_100.14.11.html
You really don't
* Lennart Sorensen [EMAIL PROTECTED] [2007-08-24 09:33:27 -0400]:
On Fri, Aug 24, 2007 at 02:53:49AM +0200, Niels Larsen wrote:
On Friday 24 August 2007 02:35:29 Chris Ahlstrom wrote:
At last I installed a driver direct from nvidia's site, following their
instructions:
* Lennart Sorensen [EMAIL PROTECTED] [2007-08-24 09:27:34 -0400]:
In fact if you have three processes to run and in total they need 90% of
one cpu, then it is better to run it all on one cpu and let the other
one go to power saving mode rather than running half the load on each.
That does
* Hans-J. Ullrich [EMAIL PROTECTED] [2007-08-24 08:27:20 +0200]:
Am Freitag 24 August 2007 schrieb Niels Larsen:
On Friday 24 August 2007 02:35:29 Chris Ahlstrom wrote:
At last I installed a driver direct from nvidia's site, following their
instructions:
On Fri, Aug 24, 2007 at 10:14:13AM -0400, Chris Ahlstrom wrote:
The one or two times I've tried to use Debian procedures to update the
kernel, it worked okay. But I've also had trouble with it, especially
when adding drivers to the mix. I much prefer doing it all myself and
understanding
* Lennart Sorensen [EMAIL PROTECTED] [2007-08-24 10:20:13 -0400]:
On Fri, Aug 24, 2007 at 10:14:13AM -0400, Chris Ahlstrom wrote:
I much prefer doing it all myself and
understanding where to put every file.
I used to do my own kernels. I stopped bothering around 2.6.0 since
debian's
Quoting Jim Crilly [EMAIL PROTECTED]:
I tested the exact same thing again but waited 60 seconds after saving
the file, and then yanked the power out. Upon a boot up, the file was
intact and the save worked. So you still have about a 60 second window
of newly written files and a power loss for
Hi michael (2007.08.24_17:10:24_+0200)
limited of its mechanics, but since XFS will never journal data, only
meta-data, then won't there always be the chance that a file can get
corrupted on a timely power loss?
A file can get corrupted, but hopefully not the file metadata (i.e. the
On Fri, 2007-08-24 at 08:10 -0700, [EMAIL PROTECTED] wrote:
Quoting Jim Crilly [EMAIL PROTECTED]:
I tested the exact same thing again but waited 60 seconds after saving
the file, and then yanked the power out. Upon a boot up, the file was
intact and the save worked. So you still have
On 08/24/07 08:10:24AM -0700, [EMAIL PROTECTED] wrote:
Quoting Jim Crilly [EMAIL PROTECTED]:
I tested the exact same thing again but waited 60 seconds after saving
the file, and then yanked the power out. Upon a boot up, the file was
intact and the save worked. So you still have about a 60
I've installed a amd64 lenny system, and installed just afterwards the
nvidia 100 driver directly from the nvidia installer, with the
2.6.21-2-amd64 kernel. Not a single glitch, everything working fine...
and lightning fast!
Ivan
2007/8/24, Chris Ahlstrom [EMAIL PROTECTED]:
* Lennart Sorensen
On Fri, 2007-08-24 at 17:09 -0300, Ivan Paganini wrote:
I've installed a amd64 lenny system, and installed just afterwards the
nvidia 100 driver directly from the nvidia installer, with the
2.6.21-2-amd64 kernel. Not a single glitch, everything working fine...
and lightning fast!
It works
18 matches
Mail list logo
