View previous topic :: View next topic |
Author |
Message |
eviltang n00b
Joined: 08 Sep 2005 Posts: 18 Location: United States
|
Posted: Tue Sep 13, 2005 8:04 pm Post subject: Enable DMA [SOLVED] |
|
|
I cannot get DMA enabled on my Tyan Tiger MP MOBO. The chipset is AMD-766 [ViperPlus]. I have disabled APIC and APM in the BIOS. I have removed APIC and APM in the kernel. I am using one Western Digital HD as /dev/hda.
Here is the error that I am getting (very common):
Code: |
mookee ~ # hdparm -d1 /dev/hda
/dev/hda:
setting using_dma to 1 (on)
HDIO_SET_DMA failed: Operation not permitted
using_dma = 0 (off)
mookee ~ #
|
Here is some of the information that may help you determin my issue:
Code: |
lspci -v information about the IDE controller
0000:00:07.1 IDE interface: Advanced Micro Devices [AMD] AMD-766 [ViperPlus] IDE
(rev 01) (prog-if 8a [Master SecP PriP])
Flags: bus master, medium devsel, latency 64
I/O ports at f000 [size=16]
|
Here is my IDE section in my kernel config:
Code: |
# CONFIG_PARIDE is not set
CONFIG_IDE=y
CONFIG_BLK_DEV_IDE=y
# Please see Documentation/ide.txt for help/info on IDE drives
# CONFIG_BLK_DEV_IDE_SATA is not set
# CONFIG_BLK_DEV_HD_IDE is not set
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_IDEDISK_MULTI_MODE=y
CONFIG_BLK_DEV_IDECD=y
# CONFIG_BLK_DEV_IDETAPE is not set
# CONFIG_BLK_DEV_IDEFLOPPY is not set
# CONFIG_BLK_DEV_IDESCSI is not set
CONFIG_IDE_TASK_IOCTL=y
# IDE chipset support/bugfixes
CONFIG_IDE_GENERIC=y
# CONFIG_BLK_DEV_IDEPNP is not set
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_IDEDMA_FORCED is not set
CONFIG_IDEDMA_PCI_AUTO=y
CONFIG_IDEDMA_ONLYDISK=y
# CONFIG_IDE_ARM is not set
# CONFIG_IDE_CHIPSETS is not set
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_IDEDMA_IVB is not set
CONFIG_IDEDMA_AUTO=y
# Old CD-ROM drivers (not SCSI, not IDE)
# CONFIG_CD_NO_IDESCSI is not set
# CONFIG_IEEE1394_VIDEO1394 is not set
# CONFIG_VIDEO_DEV is not set
# CONFIG_VIDEO_SELECT is not set
|
I have tried disabling generic dma support and building my chipset driver (AMD/nVidia) into the kernel and I get a kernel panic at boot. I've compiled as a module and inserted the module after boot but I get the same error. I think this is becuase the generic chipset takes precidence. but like I said if I build it into the kernel it panics and gives me a VFS error (i think that was it).
Here are my kernel options at boot: kernel-2.6.12-gentoo-r10 noapic nolapic acpi=off elevator=deadline
Thank you in advance for any help you can provide.
Respectfully,
EvilTang _________________ EvilTang
Last edited by eviltang on Wed Sep 14, 2005 3:44 pm; edited 1 time in total |
|
Back to top |
|
|
hw-tph l33t
Joined: 08 Jan 2004 Posts: 768 Location: Uppsala, Sweden
|
Posted: Tue Sep 13, 2005 9:11 pm Post subject: |
|
|
You probably want CONFIG_BLK_DEV_AMD74XX support:
Code: | This driver adds explicit support for AMD-7xx and AMD-8111 chips
and also for the nVidia nForce chip. This allows the kernel to
change PIO, DMA and UDMA speeds and to configure the chip to
optimum performance.
Symbol: BLK_DEV_AMD74XX [=y]
Prompt: AMD and nVidia IDE support
Defined at drivers/ide/Kconfig:485
Depends on: IDE && BLK_DEV_IDE && BLK_DEV_IDEDMA_PCI
Location:
-> Device Drivers
-> ATA/ATAPI/MFM/RLL support
-> ATA/ATAPI/MFM/RLL support (IDE [=y])
-> Enhanced IDE/MFM/RLL disk/cdrom/tape/floppy support (BLK_D
-> PCI IDE chipset support (BLK_DEV_IDEPCI [=y])
-> Generic PCI bus-master DMA support (BLK_DEV_IDEDMA_PCI |
CONFIG_IDE_GENERIC and CONFIG_BLK_DEV_GENERIC shouldn't be a problem.
Håkan _________________ Self-admitted computer fetishist |
|
Back to top |
|
|
eviltang n00b
Joined: 08 Sep 2005 Posts: 18 Location: United States
|
Posted: Tue Sep 13, 2005 9:21 pm Post subject: Tried That. |
|
|
Thank you for the post. However, that is the chipset that I am compiling into the kernel when I get the kernel panic. Any other ideas?
Thanks! _________________ EvilTang |
|
Back to top |
|
|
doro1211 Guru
Joined: 06 Jun 2004 Posts: 312
|
Posted: Wed Sep 14, 2005 2:52 am Post subject: |
|
|
That is typically the error one gets when the correct IDE driver is not compiled into your kernel. I would google around for that mb and linux and see what driver others are using. |
|
Back to top |
|
|
eviltang n00b
Joined: 08 Sep 2005 Posts: 18 Location: United States
|
Posted: Wed Sep 14, 2005 3:45 pm Post subject: Not really Resolved |
|
|
This issue is not resolved, I am going to try some other hardware configurations for my primary gentoo box. Thanks for the support anyways. _________________ EvilTang |
|
Back to top |
|
|
Neil Nelson n00b
Joined: 15 Sep 2005 Posts: 2
|
Posted: Thu Sep 15, 2005 11:13 pm Post subject: Possible Solution |
|
|
I have been working with Gentoo for just a week and noticed I was having the same DMA problem with my Tyan MPX board this morning
Code: | 0000:00:07.1 IDE interface: Advanced Micro Devices [AMD] AMD-768 [Opus] IDE (rev 04) |
and tried some of the items in this post without success. From my installation experience it seemed as though the installation disk easily recognized several items that took me awhile to get into my current installation and so I loaded that disk and ran
Code: | hdparm -d1 /dev/hda |
and obtained the desired result
Code: | /dev/hda:
setting using_dma to 1 (on)
using_dma = 1 (on) |
Clearly the following flyswatter step can be greatly improved upon, but I just copied the ide lines from the install disk config overwritting those in /usr/src/linux.config, recompiled the kernel and rebooted with a solution.
Code: | #
# IDE chipset support/bugfixes
#
CONFIG_IDE_GENERIC=y
CONFIG_BLK_DEV_CMD640=y
CONFIG_BLK_DEV_CMD640_ENHANCED=y
CONFIG_BLK_DEV_IDEPNP=y
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
# CONFIG_BLK_DEV_OFFBOARD is not set
CONFIG_BLK_DEV_GENERIC=y
CONFIG_BLK_DEV_OPTI621=y
CONFIG_BLK_DEV_RZ1000=y
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_AEC62XX=y
CONFIG_BLK_DEV_ALI15X3=y
# CONFIG_WDC_ALI15X3 is not set
CONFIG_BLK_DEV_AMD74XX=y
CONFIG_BLK_DEV_ATIIXP=y
CONFIG_BLK_DEV_CMD64X=y
CONFIG_BLK_DEV_TRIFLEX=y
CONFIG_BLK_DEV_CY82C693=y
CONFIG_BLK_DEV_CS5520=y
CONFIG_BLK_DEV_CS5530=y
CONFIG_BLK_DEV_HPT34X=y
# CONFIG_HPT34X_AUTODMA is not set
CONFIG_BLK_DEV_HPT366=y
CONFIG_BLK_DEV_SC1200=y
CONFIG_BLK_DEV_PIIX=y
CONFIG_BLK_DEV_IT821X=y
CONFIG_BLK_DEV_NS87415=y
CONFIG_BLK_DEV_PDC202XX_OLD=y
# CONFIG_PDC202XX_BURST is not set
CONFIG_BLK_DEV_PDC202XX_NEW=y
CONFIG_PDC202XX_FORCE=y
CONFIG_BLK_DEV_SVWKS=y
CONFIG_BLK_DEV_SIIMAGE=m
CONFIG_BLK_DEV_SIS5513=y
CONFIG_BLK_DEV_SLC90E66=y
CONFIG_BLK_DEV_TRM290=y
CONFIG_BLK_DEV_VIA82CXXX=y
# CONFIG_IDE_ARM is not set
CONFIG_IDE_CHIPSETS=y
#
# Note: most of these also require special kernel boot parameters
#
CONFIG_BLK_DEV_4DRIVES=y
CONFIG_BLK_DEV_ALI14XX=y
CONFIG_BLK_DEV_DTC2278=y
CONFIG_BLK_DEV_HT6560B=y
CONFIG_BLK_DEV_QD65XX=y
CONFIG_BLK_DEV_UMC8672=y
CONFIG_BLK_DEV_IDEDMA=y
CONFIG_IDEDMA_IVB=y
CONFIG_IDEDMA_AUTO=y
# CONFIG_BLK_DEV_HD is not set
|
From here it would be good to know exacly which changed .config lines are required and which kernel boot parameters, if any, might be used. But these issues are beyond my initial experience. |
|
Back to top |
|
|
|