Mayuresh | 2 Jun 10:09 2012
Picon

cdrecord DMA speed too slow error on 6.0 BETA2

When trying to burn a DVD with cdrecord I get the following error:

cdrecord: DMA speed too slow (OK for 1x). Cannot write at speed 16x.
cdrecord: Max DMA data speed is 1.
cdrecord: Try to use 'driveropts=burnfree'.

With the same hardware burning of same iso on same dvd worked on Linux.

I also tried burnfree option, though that resulted in a coaster.

Note: I have not burned a DVD using previous NetBSD versions on this
hardware. So not sure whether this is specific to 6.0 BETA or not.

Mayuresh

Dave Huang | 2 Jun 18:56 2012

Re: cdrecord DMA speed too slow error on 6.0 BETA2


On Jun 2, 2012, at 3:09 AM, Mayuresh wrote:

> When trying to burn a DVD with cdrecord I get the following error:
> 
> cdrecord: DMA speed too slow (OK for 1x). Cannot write at speed 16x.
> cdrecord: Max DMA data speed is 1.
> cdrecord: Try to use 'driveropts=burnfree'.

What do the kernel boot messages (i.e., dmesg) have to say about your IDE controller and DVD drive?

--

-- 
Name: Dave Huang         |  Mammal, mammal / their names are called /
INet: khym <at> azeotrope.org |  they raise a paw / the bat, the cat /
FurryMUCK: Dahan         |  dolphin and dog / koala bear and hog -- TMBG
Dahan: Hani G Y+C 36 Y++ L+++ W- C++ T++ A+ E+ S++ V++ F- Q+++ P+ B+ PA+ PL++

Mayuresh | 2 Jun 19:23 2012
Picon

Re: cdrecord DMA speed too slow error on 6.0 BETA2

On Sat, Jun 02, 2012 at 11:56:26AM -0500, Dave Huang wrote:
> > When trying to burn a DVD with cdrecord I get the following error:
> > 
> > cdrecord: DMA speed too slow (OK for 1x). Cannot write at speed 16x.
> > cdrecord: Max DMA data speed is 1.
> > cdrecord: Try to use 'driveropts=burnfree'.
> 
> What do the kernel boot messages (i.e., dmesg) have to say about your IDE controller and DVD drive?

# dmesg | grep  -e IDE -e DVD
piixide0 at pci0 dev 31 function 1: Intel 82801HBM IDE Controller (ICH8M)
(rev. 0x02)
cd0 at atapibus0 drive 0: <HL-DT-STCD-RW/DVD-ROM GCC-T10N, , A100> cdrom
removable

Mayuresh

Dave Huang | 2 Jun 19:32 2012

Re: cdrecord DMA speed too slow error on 6.0 BETA2


On Jun 2, 2012, at 12:23 PM, Mayuresh wrote:

> On Sat, Jun 02, 2012 at 11:56:26AM -0500, Dave Huang wrote:
>> What do the kernel boot messages (i.e., dmesg) have to say about your IDE controller and DVD drive?
> 
> # dmesg | grep  -e IDE -e DVD
> piixide0 at pci0 dev 31 function 1: Intel 82801HBM IDE Controller (ICH8M)
> (rev. 0x02)
> cd0 at atapibus0 drive 0: <HL-DT-STCD-RW/DVD-ROM GCC-T10N, , A100> cdrom
> removable

There should be multiple lines about both of those... try grepping for piixide0 and cd0 instead.
--

-- 
Name: Dave Huang         |  Mammal, mammal / their names are called /
INet: khym <at> azeotrope.org |  they raise a paw / the bat, the cat /
FurryMUCK: Dahan         |  dolphin and dog / koala bear and hog -- TMBG
Dahan: Hani G Y+C 36 Y++ L+++ W- C++ T++ A+ E+ S++ V++ F- Q+++ P+ B+ PA+ PL++

Mayuresh | 2 Jun 19:36 2012
Picon

Re: cdrecord DMA speed too slow error on 6.0 BETA2

On Sat, Jun 02, 2012 at 12:32:20PM -0500, Dave Huang wrote:
> >> What do the kernel boot messages (i.e., dmesg) have to say about your IDE controller and DVD drive?
> There should be multiple lines about both of those... try grepping for piixide0 and cd0 instead.

# dmesg | grep -e cd0 -e piixide0
piixide0 at pci0 dev 31 function 1: Intel 82801HBM IDE Controller (ICH8M)
(rev. 0x02)
piixide0: bus-master DMA support present
piixide0: primary channel configured to compatibility mode
piixide0: primary channel interrupting at ioapic0 pin 14
atabus0 at piixide0 channel 0
piixide0: secondary channel configured to compatibility mode
piixide0: secondary channel ignored (disabled)
cd0 at atapibus0 drive 0: <HL-DT-STCD-RW/DVD-ROM GCC-T10N, , A100> cdrom
removable
cd0: 32-bit data port
cd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 2 (Ultra/33)
cd0(piixide0:0:0): using PIO mode 4, Ultra-DMA mode 2 (Ultra/33) (using
DMA)

Mayuresh

Mayuresh | 2 Jun 19:42 2012
Picon

Re: cdrecord DMA speed too slow error on 6.0 BETA2

On Sat, Jun 02, 2012 at 11:06:18PM +0530, Mayuresh wrote:
> On Sat, Jun 02, 2012 at 12:32:20PM -0500, Dave Huang wrote:
> > >> What do the kernel boot messages (i.e., dmesg) have to say about your IDE controller and DVD drive?
> > There should be multiple lines about both of those... try grepping for piixide0 and cd0 instead.
> 

I am extremely sorry about my last two dmesg excerpts. I accidentally took
them from a different machine.

Here is from the machine where I face problem:

$ dmesg | grep -e cd0 -e atapibus0
atapibus0 at atabus0: 2 targets
cd0 at atapibus0 drive 1: <HL-DT-ST DVDRAM GSA-H10N, K25E57N4416, JL10>
cdrom removable
cd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 2 (Ultra/33)

(It doesn't seem IDE.)

Mayuresh.

Dave Huang | 2 Jun 19:58 2012

Re: cdrecord DMA speed too slow error on 6.0 BETA2

On Sat, Jun 02, 2012 at 11:12:10PM +0530, Mayuresh wrote:
> Here is from the machine where I face problem:
> 
> $ dmesg | grep -e cd0 -e atapibus0
> atapibus0 at atabus0: 2 targets
> cd0 at atapibus0 drive 1: <HL-DT-ST DVDRAM GSA-H10N, K25E57N4416, JL10>
> cdrom removable
> cd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 2 (Ultra/33)
> 
> (It doesn't seem IDE.)

That drive seems to be an IDE drive... interesting that there's no
line like the

cd0(piixide0:0:0): using PIO mode 4, Ultra-DMA mode 2 (Ultra/33) (using
DMA)

from your other machine. If it's not using DMA, that would probably
explain your burning problem. Information about your IDE controller
must be somewhere in the dmesg... atapibus0 is attached to atabus0, so
grep for atabus0 and see where that's attached. That should be your
IDE controller, so grep for that.

E.g., on one of my machines, I have:
atapibus0 at atabus2: 2 targets

and then:
atabus2 at cmdide0 channel 0

and finally:
(Continue reading)

Mayuresh | 2 Jun 20:08 2012
Picon

Re: cdrecord DMA speed too slow error on 6.0 BETA2

On Sat, Jun 02, 2012 at 12:58:27PM -0500, Dave Huang wrote:
> from your other machine. If it's not using DMA, that would probably
> explain your burning problem. Information about your IDE controller
> must be somewhere in the dmesg... atapibus0 is attached to atabus0, so
> grep for atabus0 and see where that's attached. That should be your
> IDE controller, so grep for that.

I saw it says - no driver support. I am using GENERIC kernel. Do I require
compiling it in?

$ dmesg | grep pciide
pciide0 at pci2 dev 0 function 0: vendor 0x11ab product 0x6101 (rev. 0xb1)
pciide0: bus-master DMA support present, but unused (no driver support)
pciide0: primary channel configured to native-PCI mode
pciide0: using ioapic0 pin 17 for native-PCI interrupt
atabus0 at pciide0 channel 0
pciide0: secondary channel configured to native-PCI mode
atabus1 at pciide0 channel 1

Mayuresh

Dave Huang | 2 Jun 20:19 2012

Re: cdrecord DMA speed too slow error on 6.0 BETA2

On Sat, Jun 02, 2012 at 11:38:33PM +0530, Mayuresh wrote:
> I saw it says - no driver support. I am using GENERIC kernel. Do I require
> compiling it in?
> 
> $ dmesg | grep pciide
> pciide0 at pci2 dev 0 function 0: vendor 0x11ab product 0x6101 (rev. 0xb1)
> pciide0: bus-master DMA support present, but unused (no driver support)

That seems to be a "Marvell 88SE6101 Single Port PATA133 Controller".
I don't see any support in NetBSD for that, but I'm no expert on it.
Hopefully someone else will know what it will take to get DMA enabled
for that controller.
--

-- 
Name: Dave Huang         |  Mammal, mammal / their names are called /
INet: khym <at> azeotrope.org |  they raise a paw / the bat, the cat /
FurryMUCK: Dahan         |  dolphin and dog / koala bear and hog -- TMBG
Dahan: Hani G Y+C 34 Y++ L+++ W- C++ T++ A+ E+ S++ V++ F- Q+++ P+ B+ PA+ PL++

Christos Zoulas | 3 Jun 02:58 2012

Re: cdrecord DMA speed too slow error on 6.0 BETA2

In article <20120602181953.GB1107 <at> azeotrope.org>,
Dave Huang  <khym <at> azeotrope.org> wrote:
>On Sat, Jun 02, 2012 at 11:38:33PM +0530, Mayuresh wrote:
>> I saw it says - no driver support. I am using GENERIC kernel. Do I require
>> compiling it in?
>> 
>> $ dmesg | grep pciide
>> pciide0 at pci2 dev 0 function 0: vendor 0x11ab product 0x6101 (rev. 0xb1)
>> pciide0: bus-master DMA support present, but unused (no driver support)
>
>That seems to be a "Marvell 88SE6101 Single Port PATA133 Controller".
>I don't see any support in NetBSD for that, but I'm no expert on it.
>Hopefully someone else will know what it will take to get DMA enabled
>for that controller.

I think FreeBSD has support for it, so it should not be too hard.

christos

Thor Lancelot Simon | 2 Jun 20:25 2012
Picon

Re: cdrecord DMA speed too slow error on 6.0 BETA2

On Sat, Jun 02, 2012 at 11:38:33PM +0530, Mayuresh wrote:
> On Sat, Jun 02, 2012 at 12:58:27PM -0500, Dave Huang wrote:
> > from your other machine. If it's not using DMA, that would probably
> > explain your burning problem. Information about your IDE controller
> > must be somewhere in the dmesg... atapibus0 is attached to atabus0, so
> > grep for atabus0 and see where that's attached. That should be your
> > IDE controller, so grep for that.
> 
> I saw it says - no driver support. I am using GENERIC kernel. Do I require
> compiling it in?

Instead of posting tiny little snippets, could you please just post the
entire dmesg output?

Thanks!

Matthew Mondor | 3 Jun 09:56 2012
Picon

Re: cdrecord DMA speed too slow error on 6.0 BETA2

On Sat, 2 Jun 2012 23:38:33 +0530
Mayuresh <mayuresh <at> acm.org> wrote:

> On Sat, Jun 02, 2012 at 12:58:27PM -0500, Dave Huang wrote:
> > from your other machine. If it's not using DMA, that would probably
> > explain your burning problem. Information about your IDE controller
> > must be somewhere in the dmesg... atapibus0 is attached to atabus0, so
> > grep for atabus0 and see where that's attached. That should be your
> > IDE controller, so grep for that.
> 
> I saw it says - no driver support. I am using GENERIC kernel. Do I require
> compiling it in?
> 
> $ dmesg | grep pciide
> pciide0 at pci2 dev 0 function 0: vendor 0x11ab product 0x6101 (rev. 0xb1)
> pciide0: bus-master DMA support present, but unused (no driver support)
> pciide0: primary channel configured to native-PCI mode
> pciide0: using ioapic0 pin 17 for native-PCI interrupt
> atabus0 at pciide0 channel 0
> pciide0: secondary channel configured to native-PCI mode
> atabus1 at pciide0 channel 1

It's not guaranteed to work (it could freeze the machine at boot if it
doesn't), but if you haven't tried yet, you could attempt to set the
force-DMA flag 0x0001, i.e.:

pciide* at pci? dev ? function ? flags 0x0001   # GENERIC pciide driver

I have to do this for an unsupported chip (VT6415, kern/45917), but it
fortunately works fine for me.
(Continue reading)


Gmane