Ubuntu Server 6.06.2 was the last server build I could install on that
Sun Blade 100 (sparc64). All attempts at getting the IDE subsystem to
disable DMA with kernels 2.6.24 and newer failed. As I mentioned above,
I tried an exhaustive list of [kernel/IDE] options to disable DMA but
was never able t
I'll be happy to test out the Alpha5 build after it is released, but can
you tell me precisely what kernel option or options I should provide to
disable DMA? I understand ide=nodma is deprecated and may even be
removed at this point. And its never been clear exactly what the new
option to disable D
Despite all my efforts I could not get DMA disabled on Ubuntu 8.04 using
kernel 2.6.24 and a sparc processor. I tried all the options listed
above (hda=nodma, the obsolete ide=nodma, ide_core.options=nodma, etc.
etc. etc.) and all indications in logs and such were that DMA was
disabled as desired,
Just want to add that reverting to the older 6.06.2 Ubuntu distro with
the 2.6.15 kernel worked fine.
--
Sparc64 Gutsy Kernel not recognizing ide=nodma
https://bugs.launchpad.net/bugs/159152
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Good news. Mr. Zolnierkiewicz, maintainer of the Linux kernel IDE
subsystem got back to me very quickly, and I quote -- "hdx=nodma" should
work fine with kernels >= 2.6.24 -- thank you very much!!
I have no experience installing Ubuntu yet. I have some experience with
other distributions, but this
I see Hardy Heron Alpha 3 (release 8.04) is bundling kernel 2.6.24. I
will contact the author of the above patches to confirm if his patches
fix this issue in post 2.6.23.x kernels and will post back here.
--
Sparc64 Gutsy Kernel not recognizing ide=nodma
https://bugs.launchpad.net/bugs/159152
Yo
Found this post, not sure of its relevance to the Ubuntu kernel
http://lkml.org/lkml/2007/3/15/293
"...However the code responsible for manually
enabling DMA ("hdparm -d 1") has a bug which results in DMA being erroneously
enabled - ide_set_dma() incorrectly passes "0" return value to
set_using_d
Any chance this issue will be resolved in the next release (8.x / Hardy
Heron)? I have an old Sun Blade 100 with Solaris 10 installed. I was
hoping to install the Ubuntu [LAMP] server until I read of this problem
in kernel bundled with 7.10. It apparently affects all platforms that
cannot support D
