On Mon, Mar 12, 2007 at 11:25:13PM -0700, Steve Langasek wrote: > So regrettably, this bug went more or less unnoticed on the 'kernel' > pseudopackage until now, and it does appear (based on the upstream > discussion) to affect the etch kernels. And in addition to it being noticed > after the upload of 2.6.18.dfsg.1-11, there also doesn't seem to be a real > upstream fix available for the problem yet. > > There does seem to be a workaround available though, which is iommu=soft. > At the moment, I'm doubtful that we could change the kernel to force this > setting on only the nvidia chipsets in time for etch. Should we instead tag > this bug etch-ignore, and refer the iommu=soft workaround to the release > notes?
Could this also be related to my #414580 problems ? Will try the iommu=soft option now. Mmm, ... No, iommu=soft doesn't seem to help there. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
