SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hello all,
few days back i found DMA issue in my 10.0. As i had to upgrade to 10.2, so without finding the solution for that i installed 10.2.
But still facing the DMA error reports during boot up.
root@bond:/boot# /sbin/lspci | grep -i ide
00:1f.1 IDE interface: Intel Corporation 82801AA IDE (rev 02)
Quote:
root@bond:/boot# cat config | grep DMA
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_IDEDMA_FORCED is not set
CONFIG_IDEDMA_PCI_AUTO=y
# CONFIG_IDEDMA_ONLYDISK is not set
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_IDEDMA_PCI_WIP is not set
CONFIG_BLK_DEV_ADMA100=y
# CONFIG_HPT34X_AUTODMA is not set
CONFIG_IDEDMA_AUTO=y
# CONFIG_IDEDMA_IVB is not set
# CONFIG_DMA_NONPCI is not set
CONFIG_SCSI_EATA_DMA=m
CONFIG_SCSI_SYM53C8XX_DMA_ADDRESSING_MODE=1
# CONFIG_IEEE1394_SBP2_PHYS_DMA is not set
CONFIG_DMASCC=m
CONFIG_SOUND_ALI5455_CODECSPDIFOUT_CODECINDEPENDENTDMA=y
CONFIG_SOUND_ALI5455_CONTROLLERSPDIFOUT_CONTROLLERINDEPENDENTDMA=y
# CONFIG_SOUND_DMAP is not set
i haven't compiled the kernel. Its the default one 2.4.31.
What shoud i do now ??? Actually the picture is still not clear to me that whats going on.
Thats a strange issue, usually you should not have to recompile your stock kernel for DMA, it should already be enabled by DEFAULT.
Edit
I just missed your attempt at enabling dma already, thats my own fault sorry....now I am racking my own brain as to what could be the issue. Still, you should not have to recompile your kernel, it probably is something with your bios settings maybe?
Thats a strange issue, usually you should not have to recompile your stock kernel for DMA, it should already be enabled by DEFAULT.
Edit
I just missed your attempt at enabling dma already, thats my own fault sorry....now I am racking my own brain as to what could be the issue. Still, you should not have to recompile your kernel, it probably is something with your bios settings maybe?
ya, it seems to be something with bios. B'coz my XP too is running slow.
I tried looking for DMA in bios but didn't find as i haven't faced such problem earlier.
Let me check it again.
Those are different than having to do with your hard drives. What you're looking at is to with PnP. I'll explain what that is and why there are those settings. A bit of history first.
Way back before Plug and Play for the PC you used to have set what resources an expansion card used by setting jumpers on them. Those were the old days of legacy ISA cards.
Take for example Sound Blaster 16 sound cards. The usual configuration for them was to use a 220 Base Memory address, IRQ 5, high DMA 5 and low DMA 1. This was determined by the jumper settings on the SB16 card. They came by default with the above settings. Sometimes you would have to change those jumpers settings if you had another expansion card that required the any of those resources. Say you had another card that required IRQ 5. You would then set the SB16 to use IRQ7 by changing what jumpers you had set for setting it's IRQ, or you would change the other cards jumpers. The point was that you couldn't have two pieces of hardware using the same IRQ or there would be conflict if you tried to use them at the same time.
Later on in time through the course of the PC's development came the early Plug and Play cards that used the ISA bus. Then even later on came PCI cards (which are plug and play also). The reason you have those setting, that you're talking about, was so that you could reserve those resources to prevent a conflict in a case where you had a mixture of PnP and non-PnP cards. So for instance, say you had an old legacy non-PnP SB16 in your system along with a bunch of other PnP cards. You would reserve those settings (eg IRQ 5, Base 220, DMA 1, and DMA 5) in the BIOS where you are looking at. That way the BIOS know not to assign those to your PnP cards and possibly create a conflict.
Earlier BIOS didn't have those settings that you're talking about unfortunately. It wasn't uncommon to get migrains when it came you had a mixture of PnP and non-PnP cards in the same system back then and didn't have a BIOS with such handy settings. That's how it Plug Play adopted the nick name Plug and Pray. Because of the configuration hell you had to go through back then.
You're probably now wondering what a person did if they had the scenario where they had a mixture of PnP and non-PnP cards but had a BIOS that didn't have setting to reserves resources. That's where ICU/ICM came in. Stands for Intel Configuration Utility/Intel Configuration Manager (or was it's ISA configuration. I could swear mine was name the former back then). That a was a nice little program that used was very terse and confusing and very poorly documented. Basically you would load it up and create hardware profiles to store setting for reserving the configuration resources. Then after you saved it, it would keep the settings in file that would be read at boot time as an extension to the BIOS.
I believe with Linux that isapnptools is to do the equivilent of what ICU/ICM used to be used for. Except, I'm sure isapnptools is much more flexible and featureful.
Moral of the story is that if you're using strictly PnP cards only, or stickly non-PnP cards, you shouldn't need to worry about those settings. The setting "PnP" means that the BIOS can go ahead and allocate them to PnP cards. In otherwords you want them all PnP in most cases if all of your cards are PnP cards. Most systems don't have non-PnP cards. Non-PnP cards pretty much died off around 10 years ago.
In Slackware I do not set hdparm to configure the drive for DMA.
There is a utility for Windows NT4 called dmacheck.exe to ensure Windows is using DMA. As far as I know, you can use this utility in XP to verify the DMA status. Essentially the utility sets some registry settings. I am not familiar with XP as I am with NT4, so ask around if there are other XP built-in tools to configure DMA.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.