Enable DMA???

[Kamikaze78]

I found this fix and applied it some months ago.

http://forum.fedoraforum.org/forum/showthread.php?t=114586

Now that worked. I had full use of my drives and they burnt at the proper speeds. Then one day after some updates, I get the following messages at boot.

ata2.00 tag 0 cmd 0xa0 emask 0x4 stat 0x40 err 0x0 (timeout)
ata2.00 exception emask 0x0 sact 0x0 serr 0x0 action 0x2 frozen
ata2.00 (BMDMA stat 0x65)
ata2.00 tag 0 cmd 0xa0 emask 0x4 stat 0x40 err 0x0 (timeout)
ata2.00 exception emask 0x0 sact 0x0 serr 0x0 action 0x2 frozen
ata2.00 (BMDMA stat 0x65)
ata2.00 tag 0 cmd 0xa0 emask 0x4 stat 0x40 err 0x0 (timeout)
ata2.00 exception emask 0x0 sact 0x0 serr 0x0 action 0x2 frozen
ata2.00 (BMDMA stat 0x65)
ata2.00 tag 0 cmd 0xa0 emask 0x4 stat 0x40 err 0x0 (timeout)
ata2.00 exception emask 0x0 sact 0x0 serr 0x0 action 0x2 frozen
ata2.00 (BMDMA stat 0x65)
ata2.00 tag 0 cmd 0xa0 emask 0x4 stat 0x40 err 0x0 (timeout)
ata2.00 exception emask 0x0 sact 0x0 serr 0x0 action 0x2 frozen
ata2.01 (BMDMA stat 0x65)
ata2.00 tag 0 cmd 0xa0 emask 0x4 stat 0x40 err 0x0 (timeout)
ata2.00 exception emask 0x0 sact 0x0 serr 0x0 action 0x2 frozen
ata2.01 (BMDMA stat 0x65)
ata2.00 tag 0 cmd 0xa0 emask 0x4 stat 0x40 err 0x0 (timeout)
ata2.00 exception emask 0x0 sact 0x0 serr 0x0 action 0x2 frozen
ata2.01 (BMDMA stat 0x65)
ata2.00 tag 0 cmd 0xa0 emask 0x4 stat 0x40 err 0x0 (timeout)
ata2.00 exception emask 0x0 sact 0x0 serr 0x0 action 0x2 frozen
ata2.01 (BMDMA stat 0x65)

Or something to that effect... I never counted how many times it came accross the screen. But I found out that it was caused by the fix that I applied. I reverted to defaults and the errors went away.

From what I have found on the net, there were some updates to hal and the way it handles things that they changed. And with this change stopped the fix from working. My question is, is there another fix for this that would allow me to have my drive on scd0 instead of hdc. I really dont care if its proper or not. Its alot less problems if I have it that way.

So hopefully the smarter linux users can figure something out so this will start working again. Thanks for your time.

[Kamikaze78]

Still no ideas on this issue?

[gala_dragos]

Are u sure u need scsi emulation for the drive? I mean the new kernels support direct ATA/ATAPI drives with no problem. About the speed I don't know if fast writing speeds improves data readability, I think it degrades it couse u can't read it on other drives (especialy older ones). Use K3B or get Nero Linux if you want professional burning software that can handle the speed better. I have a CD-R/RW and I never had speed problems under linux and it is not SCSI emulated. It can write at 52X under linux with no problem, but if I try this speed under windows it chokes (I'm lucky that I have Buffer underrun protection).

[Kamikaze78]

Are u sure u need scsi emulation for the drive? I mean the new kernels support direct ATA/ATAPI drives with no problem. About the speed I don't know if fast writing speeds improves data readability, I think it degrades it couse u can't read it on other drives (especialy older ones). Use K3B or get Nero Linux if you want professional burning software that can handle the speed better. I have a CD-R/RW and I never had speed problems under linux and it is not SCSI emulated. It can write at 52X under linux with no problem, but if I try this speed under windows it chokes (I'm lucky that I have Buffer underrun protection).

Ok, this is where my problem lies. I Have nero linux but cant use it. I need to enable dma on a drive that dma cannot be enabled on. So nero linux is out of the question. I try to use DVD Shrink though wine and DVD Shrink sees the drive, it just cant read from it. With scsi emulation all my problems go away and I burn faster.

[gala_dragos]

Did you checked the BIOS on your system? Some BIOSes disable ATAPI DMA by default. Also you could try recompiling the kernel with scsi emulation enabled (not sure if it works). Good luck !

[Kamikaze78]

Did you checked the BIOS on your system? Some BIOSes disable ATAPI DMA by default. Also you could try recompiling the kernel with scsi emulation enabled (not sure if it works). Good luck !

It is enabled. Also note. That I had the scsi emulation enabled before, my burner worked just fine. But with the new hal, it dont have the same support. I just would like to know how to make the same fix I applied before work with my linux again.