On Apr 6, 2005 6:02 PM, Bartlomiej Zolnierkiewicz <[EMAIL PROTECTED]> wrote:
>
> There still can be a bug in setting up DMA timings etc.
>
> It is hard to even guess as you haven't given any details about your
> system: dmesg/hdparm/lspci/config... (or I overlooked it somehow).
I sent the
On Apr 6, 2005 1:41 PM, Richard B. Johnson <[EMAIL PROTECTED]> wrote:
>
> How would you know? Windows will just run it as PIOW and be done
> with it.
Yes, but there's a way to know which mode you're using (maybe not
precisely, but at least PIO vs DMA).
> Did you ever try to copy a large file in
On Apr 6, 2005 1:41 PM, Richard B. Johnson [EMAIL PROTECTED] wrote:
How would you know? Windows will just run it as PIOW and be done
with it.
Yes, but there's a way to know which mode you're using (maybe not
precisely, but at least PIO vs DMA).
Did you ever try to copy a large file in XP?
On Apr 6, 2005 6:02 PM, Bartlomiej Zolnierkiewicz [EMAIL PROTECTED] wrote:
There still can be a bug in setting up DMA timings etc.
It is hard to even guess as you haven't given any details about your
system: dmesg/hdparm/lspci/config... (or I overlooked it somehow).
I sent the related
On Apr 6, 2005 1:41 PM, Richard B. Johnson <[EMAIL PROTECTED]> wrote:
> On Tue, 5 Apr 2005, Julien Wajsberg wrote:
>
> > On Apr 5, 2005 4:10 PM, Richard B. Johnson <[EMAIL PROTECTED]> wrote:
> >> On Tue, 5 Apr 2005, Julien Wajsberg wrote:
> >>
> >>> On Mar 26, 2005 12:59 AM, Julien Wajsberg
On Tue, 5 Apr 2005, Julien Wajsberg wrote:
On Apr 5, 2005 4:10 PM, Richard B. Johnson <[EMAIL PROTECTED]> wrote:
On Tue, 5 Apr 2005, Julien Wajsberg wrote:
On Mar 26, 2005 12:59 AM, Julien Wajsberg <[EMAIL PROTECTED]> wrote:
I own an Asus A8N-Sli motherboard with the Nforce4-Sli chipset, and I
On Tue, 5 Apr 2005, Julien Wajsberg wrote:
On Apr 5, 2005 4:10 PM, Richard B. Johnson [EMAIL PROTECTED] wrote:
On Tue, 5 Apr 2005, Julien Wajsberg wrote:
On Mar 26, 2005 12:59 AM, Julien Wajsberg [EMAIL PROTECTED] wrote:
I own an Asus A8N-Sli motherboard with the Nforce4-Sli chipset, and I
On Apr 6, 2005 1:41 PM, Richard B. Johnson [EMAIL PROTECTED] wrote:
On Tue, 5 Apr 2005, Julien Wajsberg wrote:
On Apr 5, 2005 4:10 PM, Richard B. Johnson [EMAIL PROTECTED] wrote:
On Tue, 5 Apr 2005, Julien Wajsberg wrote:
On Mar 26, 2005 12:59 AM, Julien Wajsberg [EMAIL PROTECTED]
On Apr 5, 2005 4:10 PM, Richard B. Johnson <[EMAIL PROTECTED]> wrote:
> On Tue, 5 Apr 2005, Julien Wajsberg wrote:
>
> > On Mar 26, 2005 12:59 AM, Julien Wajsberg <[EMAIL PROTECTED]> wrote:
> >> I own an Asus A8N-Sli motherboard with the Nforce4-Sli chipset, and I
> >> experiment the following
On Tue, 5 Apr 2005, Julien Wajsberg wrote:
On Mar 26, 2005 12:59 AM, Julien Wajsberg <[EMAIL PROTECTED]> wrote:
I own an Asus A8N-Sli motherboard with the Nforce4-Sli chipset, and I
experiment the following problem :
Mar 25 22:42:55 evenflow kernel: hda: dma_timer_expiry: dma status == 0x60
Mar 25
On Mar 26, 2005 12:59 AM, Julien Wajsberg <[EMAIL PROTECTED]> wrote:
> I own an Asus A8N-Sli motherboard with the Nforce4-Sli chipset, and I
> experiment the following problem :
>
> Mar 25 22:42:55 evenflow kernel: hda: dma_timer_expiry: dma status == 0x60
> Mar 25 22:42:55 evenflow kernel: hda:
On Apr 5, 2005 4:10 PM, Richard B. Johnson [EMAIL PROTECTED] wrote:
On Tue, 5 Apr 2005, Julien Wajsberg wrote:
On Mar 26, 2005 12:59 AM, Julien Wajsberg [EMAIL PROTECTED] wrote:
I own an Asus A8N-Sli motherboard with the Nforce4-Sli chipset, and I
experiment the following problem :
On Mar 26, 2005 12:59 AM, Julien Wajsberg [EMAIL PROTECTED] wrote:
I own an Asus A8N-Sli motherboard with the Nforce4-Sli chipset, and I
experiment the following problem :
Mar 25 22:42:55 evenflow kernel: hda: dma_timer_expiry: dma status == 0x60
Mar 25 22:42:55 evenflow kernel: hda: DMA
On Tue, 5 Apr 2005, Julien Wajsberg wrote:
On Mar 26, 2005 12:59 AM, Julien Wajsberg [EMAIL PROTECTED] wrote:
I own an Asus A8N-Sli motherboard with the Nforce4-Sli chipset, and I
experiment the following problem :
Mar 25 22:42:55 evenflow kernel: hda: dma_timer_expiry: dma status == 0x60
Mar 25
On Mar 26, 2005 7:32 PM, Marcin Dalecki <[EMAIL PROTECTED]> wrote:
>
> On 2005-03-26, at 16:19, Arjan van de Ven wrote:
>
> > `
> >> hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> >> hda: dma_intr: error=0x84 { DriveStatusError BadCRC
> >
> > BadCRC is 99% sure a cabling issue;
On Mar 26, 2005 7:32 PM, Marcin Dalecki [EMAIL PROTECTED] wrote:
On 2005-03-26, at 16:19, Arjan van de Ven wrote:
`
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC
BadCRC is 99% sure a cabling issue; either a
On Wed, 2005-03-30 at 16:01 -0500, Lee Revell wrote:
> On Wed, 2005-03-30 at 21:19 +0200, Martin Schlemmer wrote:
> > On Wed, 2005-03-30 at 17:00 +0200, Tomasz Torcz wrote:
> > > > > quake3 still segfaults when run through "aoss". And can't be fixed,
> > > > > as
> > > > > it's closed source
Francois Romieu wrote:
Jeff Garzik <[EMAIL PROTECTED]> :
Andi Kleen wrote:
[r8169 driver]
It does not seem to support DAC (or rather it breaks with DAC enabled),
which makes it not very useful on any machine with >3GB of memory.
Driver bug. I can futz with it and get it to do 64-bit on my
Jeff Garzik <[EMAIL PROTECTED]> :
> Andi Kleen wrote:
[r8169 driver]
> >It does not seem to support DAC (or rather it breaks with DAC enabled),
> >which makes it not very useful on any machine with >3GB of memory.
>
> Driver bug. I can futz with it and get it to do 64-bit on my Athlon64.
Care
On Wed, 2005-03-30 at 21:19 +0200, Martin Schlemmer wrote:
> On Wed, 2005-03-30 at 17:00 +0200, Tomasz Torcz wrote:
> > > > quake3 still segfaults when run through "aoss". And can't be fixed, as
> > > > it's closed source still.
> > > >
> > > I guess that's Quake3's problem...
> >
> > It an
Jeff Garzik wrote:
Indrek Kruusa wrote:
Jeff Garzik wrote:
Andi Kleen wrote:
Jeff Garzik <[EMAIL PROTECTED]> writes:
I won't disagree with your experiences. For me, outside of one brief
moment when the r8169 driver didn't work on Athlon64, it has worked
flawlessly for me.
RealTek 8169 is
Indrek Kruusa wrote:
Jeff Garzik wrote:
Andi Kleen wrote:
Jeff Garzik <[EMAIL PROTECTED]> writes:
I won't disagree with your experiences. For me, outside of one brief
moment when the r8169 driver didn't work on Athlon64, it has worked
flawlessly for me.
RealTek 8169 is currently my favorite
Jeff Garzik wrote:
Andi Kleen wrote:
Jeff Garzik <[EMAIL PROTECTED]> writes:
I won't disagree with your experiences. For me, outside of one brief
moment when the r8169 driver didn't work on Athlon64, it has worked
flawlessly for me.
RealTek 8169 is currently my favorite gigabit chip.
It does not
Andi Kleen wrote:
Jeff Garzik <[EMAIL PROTECTED]> writes:
I won't disagree with your experiences. For me, outside of one brief
moment when the r8169 driver didn't work on Athlon64, it has worked
flawlessly for me.
RealTek 8169 is currently my favorite gigabit chip.
It does not seem to support
On Wed, 2005-03-30 at 17:00 +0200, Tomasz Torcz wrote:
> On Tue, Mar 29, 2005 at 03:40:07PM -0500, Lee Revell wrote:
> > On Tue, 2005-03-29 at 20:58 +0200, Tomasz Torcz wrote:
> > > On Fri, Mar 25, 2005 at 06:14:22PM -0500, Lee Revell wrote:
> > > > On Fri, 2005-03-25 at 23:59 +0100, Julien
On Wed, Mar 30, 2005 at 05:00:23PM +0200, Tomasz Torcz wrote:
> It an glaring example, dmix is unsufficient in one third of my sound
> uses (other two beeing movie and music playback)
> But you advertise dmix like it was silver bullet.
An emu10k1 is a silver bullet. :)
Len Sorensen
-
To
On Tue, Mar 29, 2005 at 03:40:07PM -0500, Lee Revell wrote:
> On Tue, 2005-03-29 at 20:58 +0200, Tomasz Torcz wrote:
> > On Fri, Mar 25, 2005 at 06:14:22PM -0500, Lee Revell wrote:
> > > On Fri, 2005-03-25 at 23:59 +0100, Julien Wajsberg wrote:
> > > > - audio works too. The only problem is that
On Tue, Mar 29, 2005 at 03:40:07PM -0500, Lee Revell wrote:
On Tue, 2005-03-29 at 20:58 +0200, Tomasz Torcz wrote:
On Fri, Mar 25, 2005 at 06:14:22PM -0500, Lee Revell wrote:
On Fri, 2005-03-25 at 23:59 +0100, Julien Wajsberg wrote:
- audio works too. The only problem is that two
On Wed, Mar 30, 2005 at 05:00:23PM +0200, Tomasz Torcz wrote:
It an glaring example, dmix is unsufficient in one third of my sound
uses (other two beeing movie and music playback)
But you advertise dmix like it was silver bullet.
An emu10k1 is a silver bullet. :)
Len Sorensen
-
To
On Wed, 2005-03-30 at 17:00 +0200, Tomasz Torcz wrote:
On Tue, Mar 29, 2005 at 03:40:07PM -0500, Lee Revell wrote:
On Tue, 2005-03-29 at 20:58 +0200, Tomasz Torcz wrote:
On Fri, Mar 25, 2005 at 06:14:22PM -0500, Lee Revell wrote:
On Fri, 2005-03-25 at 23:59 +0100, Julien Wajsberg wrote:
Andi Kleen wrote:
Jeff Garzik [EMAIL PROTECTED] writes:
I won't disagree with your experiences. For me, outside of one brief
moment when the r8169 driver didn't work on Athlon64, it has worked
flawlessly for me.
RealTek 8169 is currently my favorite gigabit chip.
It does not seem to support DAC
Jeff Garzik wrote:
Andi Kleen wrote:
Jeff Garzik [EMAIL PROTECTED] writes:
I won't disagree with your experiences. For me, outside of one brief
moment when the r8169 driver didn't work on Athlon64, it has worked
flawlessly for me.
RealTek 8169 is currently my favorite gigabit chip.
It does not
Indrek Kruusa wrote:
Jeff Garzik wrote:
Andi Kleen wrote:
Jeff Garzik [EMAIL PROTECTED] writes:
I won't disagree with your experiences. For me, outside of one brief
moment when the r8169 driver didn't work on Athlon64, it has worked
flawlessly for me.
RealTek 8169 is currently my favorite gigabit
Jeff Garzik wrote:
Indrek Kruusa wrote:
Jeff Garzik wrote:
Andi Kleen wrote:
Jeff Garzik [EMAIL PROTECTED] writes:
I won't disagree with your experiences. For me, outside of one brief
moment when the r8169 driver didn't work on Athlon64, it has worked
flawlessly for me.
RealTek 8169 is currently
On Wed, 2005-03-30 at 21:19 +0200, Martin Schlemmer wrote:
On Wed, 2005-03-30 at 17:00 +0200, Tomasz Torcz wrote:
quake3 still segfaults when run through aoss. And can't be fixed, as
it's closed source still.
I guess that's Quake3's problem...
It an glaring example, dmix is
Jeff Garzik [EMAIL PROTECTED] :
Andi Kleen wrote:
[r8169 driver]
It does not seem to support DAC (or rather it breaks with DAC enabled),
which makes it not very useful on any machine with 3GB of memory.
Driver bug. I can futz with it and get it to do 64-bit on my Athlon64.
Care to send a
Francois Romieu wrote:
Jeff Garzik [EMAIL PROTECTED] :
Andi Kleen wrote:
[r8169 driver]
It does not seem to support DAC (or rather it breaks with DAC enabled),
which makes it not very useful on any machine with 3GB of memory.
Driver bug. I can futz with it and get it to do 64-bit on my Athlon64.
On Wed, 2005-03-30 at 16:01 -0500, Lee Revell wrote:
On Wed, 2005-03-30 at 21:19 +0200, Martin Schlemmer wrote:
On Wed, 2005-03-30 at 17:00 +0200, Tomasz Torcz wrote:
quake3 still segfaults when run through aoss. And can't be fixed,
as
it's closed source still.
I
On Tue, 2005-03-29 at 20:58 +0200, Tomasz Torcz wrote:
> On Fri, Mar 25, 2005 at 06:14:22PM -0500, Lee Revell wrote:
> > On Fri, 2005-03-25 at 23:59 +0100, Julien Wajsberg wrote:
> > > - audio works too. The only problem is that two applications can't
> > > open /dev/dsp in the same time.
> >
> >
On Fri, Mar 25, 2005 at 06:14:22PM -0500, Lee Revell wrote:
> On Fri, 2005-03-25 at 23:59 +0100, Julien Wajsberg wrote:
> > - audio works too. The only problem is that two applications can't
> > open /dev/dsp in the same time.
>
> Not a problem. ALSA does software mixing for chipsets that can't
On Fri, Mar 25, 2005 at 06:14:22PM -0500, Lee Revell wrote:
On Fri, 2005-03-25 at 23:59 +0100, Julien Wajsberg wrote:
- audio works too. The only problem is that two applications can't
open /dev/dsp in the same time.
Not a problem. ALSA does software mixing for chipsets that can't do it
On Tue, 2005-03-29 at 20:58 +0200, Tomasz Torcz wrote:
On Fri, Mar 25, 2005 at 06:14:22PM -0500, Lee Revell wrote:
On Fri, 2005-03-25 at 23:59 +0100, Julien Wajsberg wrote:
- audio works too. The only problem is that two applications can't
open /dev/dsp in the same time.
Not a
On Sat, 26 Mar 2005 15:13:47 +0100, Michal Schmidt
<[EMAIL PROTECTED]> wrote:
> Julien Wajsberg wrote:
> > Good point... I just tried, but forcedeth doesn't support netpoll. If
> > you have a pointer, I could try to implement it ;-)
>
> Can you try the attached patch for forcedeth?
> It compiles
Jeff Garzik <[EMAIL PROTECTED]> writes:
>
> I won't disagree with your experiences. For me, outside of one brief
> moment when the r8169 driver didn't work on Athlon64, it has worked
> flawlessly for me.
>
> RealTek 8169 is currently my favorite gigabit chip.
It does not seem to support DAC (or
Jeff Garzik [EMAIL PROTECTED] writes:
I won't disagree with your experiences. For me, outside of one brief
moment when the r8169 driver didn't work on Athlon64, it has worked
flawlessly for me.
RealTek 8169 is currently my favorite gigabit chip.
It does not seem to support DAC (or rather
On Sat, 26 Mar 2005 15:13:47 +0100, Michal Schmidt
[EMAIL PROTECTED] wrote:
Julien Wajsberg wrote:
Good point... I just tried, but forcedeth doesn't support netpoll. If
you have a pointer, I could try to implement it ;-)
Can you try the attached patch for forcedeth?
It compiles for me,
On Saturday, 26. March 2005 18:32, Marcin Dalecki wrote:
> On 2005-03-26, at 16:19, Arjan van de Ven wrote:
> > `
> >
> >> hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> >> hda: dma_intr: error=0x84 { DriveStatusError BadCRC
> >
> > BadCRC is 99% sure a cabling issue; either a
On Saturday, 26. March 2005 18:32, Marcin Dalecki wrote:
On 2005-03-26, at 16:19, Arjan van de Ven wrote:
`
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC
BadCRC is 99% sure a cabling issue; either a bad/overheated
On 2005-03-26, at 16:19, Arjan van de Ven wrote:
`
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC
BadCRC is 99% sure a cabling issue; either a bad/overheated cable or a
cable used at too high a speed for the cable.
No. It is more
`
> hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> hda: dma_intr: error=0x84 { DriveStatusError BadCRC
BadCRC is 99% sure a cabling issue; either a bad/overheated cable or a
cable used at too high a speed for the cable.
-
To unsubscribe from this list: send the line
On Fri, 2005-03-25 at 23:59 +0100, Julien Wajsberg wrote:
> Mar 25 22:42:55 evenflow kernel: hda: dma_timer_expiry: dma status == 0x60
> Mar 25 22:42:55 evenflow kernel: hda: DMA timeout retry
> Mar 25 22:42:55 evenflow kernel: hda: timeout waiting for DMA
> Mar 25 22:42:55 evenflow kernel: hda:
Julien Wajsberg wrote:
Good point... I just tried, but forcedeth doesn't support netpoll. If
you have a pointer, I could try to implement it ;-)
Can you try the attached patch for forcedeth?
It compiles for me, but I don't have nForce hardware to test it.
Michal
---
Julien Wajsberg wrote:
Good point... I just tried, but forcedeth doesn't support netpoll. If
you have a pointer, I could try to implement it ;-)
Can you try the attached patch for forcedeth?
It compiles for me, but I don't have nForce hardware to test it.
Michal
---
On Fri, 2005-03-25 at 23:59 +0100, Julien Wajsberg wrote:
Mar 25 22:42:55 evenflow kernel: hda: dma_timer_expiry: dma status == 0x60
Mar 25 22:42:55 evenflow kernel: hda: DMA timeout retry
Mar 25 22:42:55 evenflow kernel: hda: timeout waiting for DMA
Mar 25 22:42:55 evenflow kernel: hda:
`
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC
BadCRC is 99% sure a cabling issue; either a bad/overheated cable or a
cable used at too high a speed for the cable.
-
To unsubscribe from this list: send the line unsubscribe
On 2005-03-26, at 16:19, Arjan van de Ven wrote:
`
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC
BadCRC is 99% sure a cabling issue; either a bad/overheated cable or a
cable used at too high a speed for the cable.
No. It is more
On Sat, 2005-03-26 at 01:38 +0100, Julien Wajsberg wrote:
> On Fri, 25 Mar 2005 18:14:22 -0500, Lee Revell <[EMAIL PROTECTED]> wrote:
> > On Fri, 2005-03-25 at 23:59 +0100, Julien Wajsberg wrote:
> > > - audio works too. The only problem is that two applications can't
> > > open /dev/dsp in the
On Fri, 25 Mar 2005 18:14:22 -0500, Lee Revell <[EMAIL PROTECTED]> wrote:
> On Fri, 2005-03-25 at 23:59 +0100, Julien Wajsberg wrote:
> > - audio works too. The only problem is that two applications can't
> > open /dev/dsp in the same time.
>
> Not a problem. ALSA does software mixing for
On Fri, 25 Mar 2005 18:20:54 -0500, Lee Revell <[EMAIL PROTECTED]> wrote:
> On Fri, 2005-03-25 at 23:59 +0100, Julien Wajsberg wrote:
> > I also experiment sometimes a complete hang of the system. But I
> > didn't find how to reproduce the bug yet, especially because it seems
> > to happen when I
On Fri, 25 Mar 2005 18:21:42 -0500, Lee Revell <[EMAIL PROTECTED]> wrote:
> On Fri, 2005-03-25 at 23:59 +0100, Julien Wajsberg wrote:
> > Mar 25 22:42:55 evenflow kernel: hda: dma_timer_expiry: dma status == 0x60
> > Mar 25 22:42:55 evenflow kernel: hda: DMA timeout retry
> > Mar 25 22:42:55
On Fri, 2005-03-25 at 23:59 +0100, Julien Wajsberg wrote:
> Mar 25 22:42:55 evenflow kernel: hda: dma_timer_expiry: dma status == 0x60
> Mar 25 22:42:55 evenflow kernel: hda: DMA timeout retry
> Mar 25 22:42:55 evenflow kernel: hda: timeout waiting for DMA
> Mar 25 22:42:55 evenflow kernel: hda:
On Fri, 2005-03-25 at 23:59 +0100, Julien Wajsberg wrote:
> I also experiment sometimes a complete hang of the system. But I
> didn't find how to reproduce the bug yet, especially because it seems
> to happen when I do nothing (when I'm sleeping or am at work ;), and I
> can't get a Oops because I
On Fri, 2005-03-25 at 23:59 +0100, Julien Wajsberg wrote:
> - audio works too. The only problem is that two applications can't
> open /dev/dsp in the same time.
Not a problem. ALSA does software mixing for chipsets that can't do it
in hardware. Google for dmix.
However this doesn't (and can't
Hi
Just to answer some questions :
- USB works ok since 2.6.11
- audio works too. The only problem is that two applications can't
open /dev/dsp in the same time.
- network works
I own an Asus A8N-Sli motherboard with the Nforce4-Sli chipset, and I
experiment the following problem :
Mar 25
On Thu, 24 Mar 2005 at 10:34:12 +0100, Arjan van de Ven wrote:
> probably just one of those things implemented in the binary drivers in
> software, just like the "hardware" IDE raid is most of the time (3ware
> being the positive exception there)
IT8212 is a real hardware ATA RAID controller.
On Thu, 24 Mar 2005 at 10:34:12 +0100, Arjan van de Ven wrote:
probably just one of those things implemented in the binary drivers in
software, just like the hardware IDE raid is most of the time (3ware
being the positive exception there)
IT8212 is a real hardware ATA RAID controller. Too
Hi
Just to answer some questions :
- USB works ok since 2.6.11
- audio works too. The only problem is that two applications can't
open /dev/dsp in the same time.
- network works
I own an Asus A8N-Sli motherboard with the Nforce4-Sli chipset, and I
experiment the following problem :
Mar 25
On Fri, 2005-03-25 at 23:59 +0100, Julien Wajsberg wrote:
- audio works too. The only problem is that two applications can't
open /dev/dsp in the same time.
Not a problem. ALSA does software mixing for chipsets that can't do it
in hardware. Google for dmix.
However this doesn't (and can't be
On Fri, 2005-03-25 at 23:59 +0100, Julien Wajsberg wrote:
I also experiment sometimes a complete hang of the system. But I
didn't find how to reproduce the bug yet, especially because it seems
to happen when I do nothing (when I'm sleeping or am at work ;), and I
can't get a Oops because I
On Fri, 2005-03-25 at 23:59 +0100, Julien Wajsberg wrote:
Mar 25 22:42:55 evenflow kernel: hda: dma_timer_expiry: dma status == 0x60
Mar 25 22:42:55 evenflow kernel: hda: DMA timeout retry
Mar 25 22:42:55 evenflow kernel: hda: timeout waiting for DMA
Mar 25 22:42:55 evenflow kernel: hda:
On Fri, 25 Mar 2005 18:21:42 -0500, Lee Revell [EMAIL PROTECTED] wrote:
On Fri, 2005-03-25 at 23:59 +0100, Julien Wajsberg wrote:
Mar 25 22:42:55 evenflow kernel: hda: dma_timer_expiry: dma status == 0x60
Mar 25 22:42:55 evenflow kernel: hda: DMA timeout retry
Mar 25 22:42:55 evenflow
On Fri, 25 Mar 2005 18:20:54 -0500, Lee Revell [EMAIL PROTECTED] wrote:
On Fri, 2005-03-25 at 23:59 +0100, Julien Wajsberg wrote:
I also experiment sometimes a complete hang of the system. But I
didn't find how to reproduce the bug yet, especially because it seems
to happen when I do
On Fri, 25 Mar 2005 18:14:22 -0500, Lee Revell [EMAIL PROTECTED] wrote:
On Fri, 2005-03-25 at 23:59 +0100, Julien Wajsberg wrote:
- audio works too. The only problem is that two applications can't
open /dev/dsp in the same time.
Not a problem. ALSA does software mixing for chipsets that
On Sat, 2005-03-26 at 01:38 +0100, Julien Wajsberg wrote:
On Fri, 25 Mar 2005 18:14:22 -0500, Lee Revell [EMAIL PROTECTED] wrote:
On Fri, 2005-03-25 at 23:59 +0100, Julien Wajsberg wrote:
- audio works too. The only problem is that two applications can't
open /dev/dsp in the same time.
On Thu, 2005-03-24 at 20:15 -0600, Robert Hancock wrote:
> There is no need to use any binary drivers on the nForce4 - the only
> ones even available are for the network and audio. The network works
> fine with the forcedeth driver included in the kernel - I don't know
> about the audio, I'm
Asfand Yar Qazi wrote:
NForce4 Ultra is brilliant - in many ways. Except it requires binary
drivers, which I really don't want to use. And apparently, the hardware
firewall seems to restrict bandwidth a bit. And even when its off,
external chips that end up being faster
Lennart Sorensen wrote:
I think the r8139 has ruined realtek for me forever. I like the Marvell
Yukon chip Asus includes on many boards (although some people have
reported problems with some Asus boards using them with Linux).
I won't disagree with your experiences. For me, outside of one brief
Asfand Yar Qazi wrote:
However, this doesn't answer my original question (which I suppose I
should have made clearer): can I get SATA II NCQ support in Linux with
an nForce 4 chipset?
I answered this question already. The answer is no.
Jeff
-
To unsubscribe from this list: send the line
Lennart Sorensen wrote:
On Thu, Mar 24, 2005 at 10:33:03AM +, Asfand Yar Qazi wrote:
No, but I do need NCQ
Perhaps a stupid question... but: Why do you _need_ NCQ? If you need it
that badly (not sure why anyone would), you could always get SCSI or a
3ware controller.
For the novelty value.
On Thu, Mar 24, 2005 at 10:33:03AM +, Asfand Yar Qazi wrote:
> No, but I do need NCQ
Perhaps a stupid question... but: Why do you _need_ NCQ? If you need it
that badly (not sure why anyone would), you could always get SCSI or a
3ware controller.
NCQ is a nice feature, but hardly essential.
Lennart Sorensen wrote:
Until the OS loads network drivers AND configures IP support AND starts
accepting packets in, there is nothing for the firewall to do.
Certainly on Linux I can make sure iptables is populated (or least has a
sane policy set) before I bring up networking. In other words:
On Thu, Mar 24, 2005 at 10:00:46AM +, Asfand Yar Qazi wrote:
> http://www.neoseeker.com/Articles/Hardware/Previews/nvnforce4/3.html
>
> You're right there - some semi-hardware support combined with drivers
> apparently result in lower CPU usage that software firewalls. Apparently.
>
>
On Thu, Mar 24, 2005 at 04:30:32AM -0500, Jeff Garzik wrote:
> Well, let's cut through the B.S. ;-)
>
> * Even when the SATA core is updated to support NCQ, nForce will not
> support it under Linux. No hardware info.
Hmm, either that or someone will figure it out anyhow, like they did
with
Pawel Sikora wrote:
Do You really need nforce4?
Maybe sis76[01]GX will be enough? :-)
http://www.sis.com/products/sis760gx.htm
http://www.sis.com/pressroom/pressrelease_000184.htm
No, but I do need NCQ
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
On Thu, 2005-03-24 at 10:00 +, Asfand Yar Qazi wrote:
> Arjan van de Ven wrote:
> >>* "hardware firewall" -- sounds silly. Pretty sure Linux doesn't support
> >>it in any case.
> >>
> >
> >
> > probably just one of those things implemented in the binary drivers in
> > software, just like
Do You really need nforce4?
Maybe sis76[01]GX will be enough? :-)
http://www.sis.com/products/sis760gx.htm
http://www.sis.com/pressroom/pressrelease_000184.htm
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More
Asfand Yar Qazi wrote:
Arjan van de Ven wrote:
* "hardware firewall" -- sounds silly. Pretty sure Linux doesn't
support
it in any case.
probably just one of those things implemented in the binary drivers in
software, just like the "hardware" IDE raid is most of the time (3ware
being the
Arjan van de Ven wrote:
* "hardware firewall" -- sounds silly. Pretty sure Linux doesn't support
it in any case.
probably just one of those things implemented in the binary drivers in
software, just like the "hardware" IDE raid is most of the time (3ware
being the positive exception there)
Arjan van de Ven wrote:
* "hardware firewall" -- sounds silly. Pretty sure Linux doesn't support
it in any case.
probably just one of those things implemented in the binary drivers in
software, just like the "hardware" IDE raid is most of the time (3ware
being the positive exception there)
>
> * "hardware firewall" -- sounds silly. Pretty sure Linux doesn't support
> it in any case.
>
probably just one of those things implemented in the binary drivers in
software, just like the "hardware" IDE raid is most of the time (3ware
being the positive exception there)
-
To unsubscribe
On Thu, Mar 24, 2005 at 09:20:29AM +, Asfand Yar Qazi wrote:
> Hi,
>
> I'm currently contemplating going for an Athlon 64 system. However,
> I'll primarily be using a Linux-based OS (Gentoo, namely), so I need
> to know how well the chipsets are supported currently.
>
> I'd really like to
Hi,
I'm currently contemplating going for an Athlon 64 system. However,
I'll primarily be using a Linux-based OS (Gentoo, namely), so I need
to know how well the chipsets are supported currently.
I'd really like to go Via - but the crummy KT890 / VT8237 combo sucks
- mainly due to the lack of
Hi,
I'm currently contemplating going for an Athlon 64 system. However,
I'll primarily be using a Linux-based OS (Gentoo, namely), so I need
to know how well the chipsets are supported currently.
I'd really like to go Via - but the crummy KT890 / VT8237 combo sucks
- mainly due to the lack of
On Thu, Mar 24, 2005 at 09:20:29AM +, Asfand Yar Qazi wrote:
Hi,
I'm currently contemplating going for an Athlon 64 system. However,
I'll primarily be using a Linux-based OS (Gentoo, namely), so I need
to know how well the chipsets are supported currently.
I'd really like to go Via
* hardware firewall -- sounds silly. Pretty sure Linux doesn't support
it in any case.
probably just one of those things implemented in the binary drivers in
software, just like the hardware IDE raid is most of the time (3ware
being the positive exception there)
-
To unsubscribe from
Arjan van de Ven wrote:
* hardware firewall -- sounds silly. Pretty sure Linux doesn't support
it in any case.
probably just one of those things implemented in the binary drivers in
software, just like the hardware IDE raid is most of the time (3ware
being the positive exception there)
Arjan van de Ven wrote:
* hardware firewall -- sounds silly. Pretty sure Linux doesn't support
it in any case.
probably just one of those things implemented in the binary drivers in
software, just like the hardware IDE raid is most of the time (3ware
being the positive exception there)
Asfand Yar Qazi wrote:
Arjan van de Ven wrote:
* hardware firewall -- sounds silly. Pretty sure Linux doesn't
support
it in any case.
probably just one of those things implemented in the binary drivers in
software, just like the hardware IDE raid is most of the time (3ware
being the positive
OT
Do You really need nforce4?
Maybe sis76[01]GX will be enough? :-)
http://www.sis.com/products/sis760gx.htm
http://www.sis.com/pressroom/pressrelease_000184.htm
/OT
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More
On Thu, 2005-03-24 at 10:00 +, Asfand Yar Qazi wrote:
Arjan van de Ven wrote:
* hardware firewall -- sounds silly. Pretty sure Linux doesn't support
it in any case.
probably just one of those things implemented in the binary drivers in
software, just like the hardware IDE raid
1 - 100 of 109 matches
Mail list logo
