https://bugzilla.novell.com/show_bug.cgi?id=180390#c77
--- Comment #77 from Henryk Hecht 2007-11-12 18:19:57 MST ---
I do not believe that to be the issue, at least in my case. Older SuSE kernels
(9.x?) worked fine with ECP. Somewhere around 10.0, it would work with ECP
unless the modules were reloaded (which the yast2 printer module apparently
does, among other things), at which point it would cease to function until
reboot. Sometime later (not sure when, I had to switch to EPP and there was no
progress on the bug) it has apparently stopped working even right after boot if
ECP is enabled. The only other data point I can offer is that NT OSs don't
seem to have a problem with ECP (at least not NT 5.0 or 5.1).
Given this, it seems unlikely that DMA simply doesn't work for the port.
Certainly it would be hard to reconcile this with the works-until-reloaded
behavior in early 10.x. Is there a way to reliably tell if DMA is being used
in Windows (I know it will sometimes lie about IDE DMA status, so...)?
Alternatively, would it be helpful or possible to directly compare the pnpbios
and pnpacpi information? Generally, before I start lobbying the upstream
kernel, is there a way to be sure I'm blaming the right thing?
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.