Re: Probleme mit DMA
>
> Was für einen Chipsatz hast du denn (lspci -v hilft dir da). Und dann
> einfach mal unter /lib/modules/$kernelversion/kernel/drivers/ide
> schauen ob es da ein Modul gibt. Wenn nicht mal unter
> /boot/config-$kernelversion gucken, obs fest im Kernel ist (was ich
> aber nicht glaube, sonst würds ja gehen). Wenn beides nicht zum Erfolg
> führt, besorg dir die Kernelquellen und bau dir selbst einen Kernel.
>
lspci -v sagt:
00:00.0 Host bridge: VIA Technologies, Inc.: Unknown device 3116
Subsystem: Unknown device 1849:3156
Flags: bus master, 66Mhz, medium devsel, latency 8
Memory at e0000000 (32-bit, prefetchable) [size=64M]
Capabilities: <available only to root>
00:01.0 PCI bridge: VIA Technologies, Inc. VT8633 [Apollo Pro266 AGP]
(prog-if 00 [Normal decode]) Flags: bus master, 66Mhz, medium
devsel, latency 0 Bus: primary=00, secondary=01, subordinate=01,
sec-latency=0 Memory behind bridge: dfd00000-dfefffff
Prefetchable memory behind bridge: cfc00000-dfbfffff
Capabilities: <available only to root>
00:10.0 USB Controller: VIA Technologies, Inc. UHCI USB (rev 80)
(prog-if 00 [UHCI]) Subsystem: VIA Technologies, Inc. UHCI USB
Flags: bus master, medium devsel, latency 32, IRQ 11
I/O ports at e400 [size=32]
Capabilities: <available only to root>
00:10.1 USB Controller: VIA Technologies, Inc. UHCI USB (rev 80)
(prog-if 00 [UHCI]) Subsystem: VIA Technologies, Inc. UHCI USB
Flags: bus master, medium devsel, latency 32, IRQ 10
I/O ports at e800 [size=32]
Capabilities: <available only to root>
00:10.2 USB Controller: VIA Technologies, Inc. UHCI USB (rev 80)
(prog-if 00 [UHCI]) Subsystem: VIA Technologies, Inc. UHCI USB
Flags: bus master, medium devsel, latency 32, IRQ 10
I/O ports at ec00 [size=32]
Capabilities: <available only to root>
00:10.3 USB Controller: VIA Technologies, Inc.: Unknown device 3104 (rev
82) (prog-if 20) Subsystem: VIA Technologies, Inc.: Unknown
device 3104 Flags: bus master, medium devsel, latency 32, IRQ 10
Memory at dfffff00 (32-bit, non-prefetchable) [size=256]
Capabilities: <available only to root>
00:11.0 ISA bridge: VIA Technologies, Inc.: Unknown device 3177
Subsystem: Unknown device 1849:3177
Flags: bus master, stepping, medium devsel, latency 0
Capabilities: <available only to root>
00:11.1 IDE interface: VIA Technologies, Inc. Bus Master IDE (rev 06)
(prog-if 8a [Master SecP PriP]) Subsystem: Unknown device
1849:0571 Flags: bus master, medium devsel, latency 32, IRQ 14
I/O ports at fc00 [size=16]
Capabilities: <available only to root>
00:11.5 Multimedia audio controller: VIA Technologies, Inc. AC97 Audio
Controller (rev 50) Subsystem: VIA Technologies, Inc.: Unknown
device 4161 Flags: medium devsel, IRQ 10
I/O ports at e000 [size=256]
Capabilities: <available only to root>
00:12.0 Ethernet controller: VIA Technologies, Inc. Ethernet Controller
(rev 74) Subsystem: Unknown device 1849:3065 Flags: bus
master, medium devsel, latency 32, IRQ 11 I/O ports at dc00
[size=256] Memory at dffffe00 (32-bit, non-prefetchable)
[size=256] Capabilities: <available only to root>
01:00.0 VGA compatible controller: S3 Inc.: Unknown device 8d04 (prog-if
00 [VGA]) Subsystem: S3 Inc.: Unknown device 8d04
Flags: bus master, 66Mhz, medium devsel, latency 32, IRQ 11
Memory at dfe80000 (32-bit, non-prefetchable) [size=512K]
Memory at d0000000 (32-bit, prefetchable) [size=128M]
Expansion ROM at dfe70000 [disabled] [size=64K]
Capabilities: <available only to root>
Unter /lib ..../drivers/ide/ steht:
ataraid.o
hptraid.o
ide-cd.o
ide-disk.o
ide-floppy.o
ide-mod.o
ide-probe-mod.o
ide-tape.o
inhalt.txt
pdcraid.o
Da finde ich jetzt nichts was konkret auf einen Chipsatz von VIA
hinweist.
In der config-Datei fuer den Kernel steht folgendes:
# IDE chipset support/bugfixes
#
CONFIG_BLK_DEV_CMD640=y
# CONFIG_BLK_DEV_CMD640_ENHANCED is not set
# CONFIG_BLK_DEV_ISAPNP is not set
CONFIG_BLK_DEV_RZ1000=y
CONFIG_BLK_DEV_IDEPCI=y
# CONFIG_IDEPCI_SHARE_IRQ is not set
CONFIG_BLK_DEV_IDEDMA_PCI=y
CONFIG_BLK_DEV_ADMA=y
# CONFIG_BLK_DEV_OFFBOARD is not set
# CONFIG_IDEDMA_PCI_AUTO is not set
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_IDEDMA_PCI_WIP is not set
# CONFIG_IDEDMA_NEW_DRIVE_LISTINGS is not set
CONFIG_BLK_DEV_AEC62XX=y
# CONFIG_AEC62XX_TUNING is not set
CONFIG_BLK_DEV_ALI15X3=y
# CONFIG_WDC_ALI15X3 is not set
CONFIG_BLK_DEV_AMD74XX=y
# CONFIG_AMD74XX_OVERRIDE is not set
CONFIG_BLK_DEV_CMD64X=y
CONFIG_BLK_DEV_CY82C693=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_PIIX=y
# CONFIG_PIIX_TUNING is not set
CONFIG_BLK_DEV_NS87415=y
CONFIG_BLK_DEV_OPTI621=y
CONFIG_BLK_DEV_PDC202XX=y
CONFIG_PDC202XX_BURST=y
# CONFIG_PDC202XX_FORCE is not set
CONFIG_BLK_DEV_SVWKS=y
CONFIG_BLK_DEV_SIS5513=y
CONFIG_BLK_DEV_SLC90E66=y
CONFIG_BLK_DEV_TRM290=y
CONFIG_BLK_DEV_VIA82CXXX=y
# CONFIG_IDE_CHIPSETS is not set
# CONFIG_IDEDMA_AUTO is not set
# CONFIG_IDEDMA_IVB is not set
# CONFIG_DMA_NONPCI is not set
CONFIG_BLK_DEV_IDE_MODES=y
CONFIG_BLK_DEV_ATARAID=m
CONFIG_BLK_DEV_ATARAID_PDC=m
CONFIG_BLK_DEV_ATARAID_HPT=m
Mir sagt das jetzt ersteinmal nicht viel.
Gruss
Kai
Reply to: