Re: How's the nforce4 support in Linux?

Re: How's the nforce4 support in Linux?

[Julien Wajsberg]

[-- Attachment #1: Type: text/plain, Size: 1508 bytes --]

Hi

Just to answer some questions :

- USB works ok since 2.6.11
- audio works too. The only problem is that two applications can't
open /dev/dsp in the same time.
- network works

I own an Asus A8N-Sli motherboard with the Nforce4-Sli chipset, and I
experiment the following problem :

Mar 25 22:42:55 evenflow kernel: hda: dma_timer_expiry: dma status == 0x60
Mar 25 22:42:55 evenflow kernel: hda: DMA timeout retry
Mar 25 22:42:55 evenflow kernel: hda: timeout waiting for DMA
Mar 25 22:42:55 evenflow kernel: hda: status error: status=0x58 {
DriveReady SeekComplete DataRequest }
Mar 25 22:42:55 evenflow kernel: 
Mar 25 22:42:55 evenflow kernel: ide: failed opcode was: unknown
Mar 25 22:42:55 evenflow kernel: hda: drive not ready for command
Mar 25 22:42:55 evenflow kernel: hda: status timeout: status=0xd0 { Busy }
Mar 25 22:42:55 evenflow kernel: 
Mar 25 22:42:55 evenflow kernel: ide: failed opcode was: unknown
Mar 25 22:42:55 evenflow kernel: hdb: DMA disabled
Mar 25 22:42:55 evenflow kernel: hda: drive not ready for command


Of course, if I disable DMA with hdparm, this problem disappear.. but
it isn't a long-term solution ;-)

Using vanilla 2.6.11.5 kernel. I attached the config file.

I also experiment sometimes a complete hang of the system. But I
didn't find how to reproduce the bug yet, especially because it seems
to happen when I do nothing (when I'm sleeping or am at work ;), and I
can't get a Oops because I don't have any serial console...

Kind regards,
-- 
Julien Wajsberg

[-- Attachment #2: config-2.6.11.5 --]
[-- Type: application/octet-stream, Size: 33107 bytes --]

#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.11.5
# Fri Mar 25 22:26:14 2005
#
CONFIG_X86=y
CONFIG_MMU=y
CONFIG_UID16=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y

#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
CONFIG_CLEAN_COMPILE=y
CONFIG_BROKEN_ON_SMP=y
CONFIG_LOCK_KERNEL=y

#
# General setup
#
CONFIG_LOCALVERSION=""
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
# CONFIG_POSIX_MQUEUE is not set
CONFIG_BSD_PROCESS_ACCT=y
# CONFIG_BSD_PROCESS_ACCT_V3 is not set
CONFIG_SYSCTL=y
# CONFIG_AUDIT is not set
CONFIG_LOG_BUF_SHIFT=14
CONFIG_HOTPLUG=y
CONFIG_KOBJECT_UEVENT=y
# CONFIG_IKCONFIG is not set
# CONFIG_EMBEDDED is not set
CONFIG_KALLSYMS=y
# CONFIG_KALLSYMS_ALL is not set
# CONFIG_KALLSYMS_EXTRA_PASS is not set
CONFIG_FUTEX=y
CONFIG_EPOLL=y
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set
CONFIG_SHMEM=y
CONFIG_CC_ALIGN_FUNCTIONS=0
CONFIG_CC_ALIGN_LABELS=0
CONFIG_CC_ALIGN_LOOPS=0
CONFIG_CC_ALIGN_JUMPS=0
# CONFIG_TINY_SHMEM is not set

#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
CONFIG_MODULE_FORCE_UNLOAD=y
CONFIG_OBSOLETE_MODPARM=y
# CONFIG_MODVERSIONS is not set
# CONFIG_MODULE_SRCVERSION_ALL is not set
CONFIG_KMOD=y

#
# Processor type and features
#
CONFIG_X86_PC=y
# CONFIG_X86_ELAN is not set
# CONFIG_X86_VOYAGER is not set
# CONFIG_X86_NUMAQ is not set
# CONFIG_X86_SUMMIT is not set
# CONFIG_X86_BIGSMP is not set
# CONFIG_X86_VISWS is not set
# CONFIG_X86_GENERICARCH is not set
# CONFIG_X86_ES7000 is not set
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
# CONFIG_MPENTIUMII is not set
# CONFIG_MPENTIUMIII is not set
# CONFIG_MPENTIUMM is not set
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
CONFIG_MK8=y
# CONFIG_MCRUSOE is not set
# CONFIG_MEFFICEON is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MCYRIXIII is not set
# CONFIG_MVIAC3_2 is not set
# CONFIG_X86_GENERIC is not set
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_L1_CACHE_SHIFT=6
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_INTEL_USERCOPY=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_HPET_TIMER=y
CONFIG_HPET_EMULATE_RTC=y
# CONFIG_SMP is not set
CONFIG_PREEMPT=y
CONFIG_PREEMPT_BKL=y
# CONFIG_X86_UP_APIC is not set
CONFIG_X86_TSC=y
# CONFIG_X86_MCE is not set
# CONFIG_TOSHIBA is not set
# CONFIG_I8K is not set
# CONFIG_MICROCODE is not set
# CONFIG_X86_MSR is not set
CONFIG_X86_CPUID=m

#
# Firmware Drivers
#
# CONFIG_EDD is not set
CONFIG_NOHIGHMEM=y
# CONFIG_HIGHMEM4G is not set
# CONFIG_HIGHMEM64G is not set
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y
# CONFIG_EFI is not set
CONFIG_HAVE_DEC_LOCK=y
# CONFIG_REGPARM is not set

#
# Power management options (ACPI, APM)
#
# CONFIG_PM is not set

#
# ACPI (Advanced Configuration and Power Interface) Support
#
CONFIG_ACPI=y
CONFIG_ACPI_BOOT=y
CONFIG_ACPI_INTERPRETER=y
# CONFIG_ACPI_AC is not set
# CONFIG_ACPI_BATTERY is not set
# CONFIG_ACPI_BUTTON is not set
# CONFIG_ACPI_VIDEO is not set
# CONFIG_ACPI_FAN is not set
# CONFIG_ACPI_PROCESSOR is not set
# CONFIG_ACPI_ASUS is not set
# CONFIG_ACPI_IBM is not set
# CONFIG_ACPI_TOSHIBA is not set
CONFIG_ACPI_BLACKLIST_YEAR=0
# CONFIG_ACPI_DEBUG is not set
CONFIG_ACPI_BUS=y
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_PCI=y
CONFIG_ACPI_SYSTEM=y
# CONFIG_X86_PM_TIMER is not set
# CONFIG_ACPI_CONTAINER is not set

#
# CPU Frequency scaling
#
# CONFIG_CPU_FREQ is not set

#
# Bus options (PCI, PCMCIA, EISA, MCA, ISA)
#
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GOMMCONFIG is not set
# CONFIG_PCI_GODIRECT is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_MMCONFIG=y
CONFIG_PCIEPORTBUS=y
# CONFIG_PCI_LEGACY_PROC is not set
CONFIG_PCI_NAMES=y
# CONFIG_ISA is not set
# CONFIG_MCA is not set
# CONFIG_SCx200 is not set

#
# PCCARD (PCMCIA/CardBus) support
#
# CONFIG_PCCARD is not set

#
# PC-card bridges
#

#
# PCI Hotplug Support
#
# CONFIG_HOTPLUG_PCI is not set

#
# Executable file formats
#
CONFIG_BINFMT_ELF=y
# CONFIG_BINFMT_AOUT is not set
CONFIG_BINFMT_MISC=m

#
# Device Drivers
#

#
# Generic Driver Options
#
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y
# CONFIG_FW_LOADER is not set
# CONFIG_DEBUG_DRIVER is not set

#
# Memory Technology Devices (MTD)
#
# CONFIG_MTD is not set

#
# Parallel port support
#
CONFIG_PARPORT=m
CONFIG_PARPORT_PC=m
CONFIG_PARPORT_PC_CML1=m
# CONFIG_PARPORT_SERIAL is not set
CONFIG_PARPORT_PC_FIFO=y
CONFIG_PARPORT_PC_SUPERIO=y
# CONFIG_PARPORT_OTHER is not set
CONFIG_PARPORT_1284=y

#
# Plug and Play support
#
CONFIG_PNP=y
# CONFIG_PNP_DEBUG is not set

#
# Protocols
#
CONFIG_PNPACPI=y

#
# Block devices
#
CONFIG_BLK_DEV_FD=y
# CONFIG_PARIDE is not set
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_UMEM is not set
# CONFIG_BLK_DEV_COW_COMMON is not set
CONFIG_BLK_DEV_LOOP=y
# CONFIG_BLK_DEV_CRYPTOLOOP is not set
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_SX8 is not set
# CONFIG_BLK_DEV_UB is not set
# CONFIG_BLK_DEV_RAM is not set
CONFIG_BLK_DEV_RAM_COUNT=16
CONFIG_INITRAMFS_SOURCE=""
# CONFIG_LBD is not set
CONFIG_CDROM_PKTCDVD=m
CONFIG_CDROM_PKTCDVD_BUFFERS=8
# CONFIG_CDROM_PKTCDVD_WCACHE is not set

#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
# CONFIG_ATA_OVER_ETH is not set

#
# ATA/ATAPI/MFM/RLL support
#
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 is not set
CONFIG_BLK_DEV_IDECD=y
# CONFIG_BLK_DEV_IDETAPE is not set
# CONFIG_BLK_DEV_IDEFLOPPY is not set
CONFIG_BLK_DEV_IDESCSI=m
# CONFIG_IDE_TASK_IOCTL is not set

#
# IDE chipset support/bugfixes
#
CONFIG_IDE_GENERIC=y
# CONFIG_BLK_DEV_CMD640 is not set
# CONFIG_BLK_DEV_IDEPNP is not set
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
# CONFIG_BLK_DEV_OFFBOARD is not set
# CONFIG_BLK_DEV_GENERIC is not set
# CONFIG_BLK_DEV_OPTI621 is not set
# CONFIG_BLK_DEV_RZ1000 is not set
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 is not set
# CONFIG_BLK_DEV_ALI15X3 is not set
CONFIG_BLK_DEV_AMD74XX=y
# CONFIG_BLK_DEV_ATIIXP is not set
# CONFIG_BLK_DEV_CMD64X is not set
# CONFIG_BLK_DEV_TRIFLEX is not set
# CONFIG_BLK_DEV_CY82C693 is not set
# CONFIG_BLK_DEV_CS5520 is not set
# CONFIG_BLK_DEV_CS5530 is not set
# CONFIG_BLK_DEV_HPT34X is not set
# CONFIG_BLK_DEV_HPT366 is not set
# CONFIG_BLK_DEV_SC1200 is not set
# CONFIG_BLK_DEV_PIIX is not set
# CONFIG_BLK_DEV_NS87415 is not set
# CONFIG_BLK_DEV_PDC202XX_OLD is not set
# CONFIG_BLK_DEV_PDC202XX_NEW is not set
# CONFIG_BLK_DEV_SVWKS is not set
# CONFIG_BLK_DEV_SIIMAGE is not set
# CONFIG_BLK_DEV_SIS5513 is not set
# CONFIG_BLK_DEV_SLC90E66 is not set
# CONFIG_BLK_DEV_TRM290 is not set
# CONFIG_BLK_DEV_VIA82CXXX is not set
# CONFIG_IDE_ARM is not set
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_IDEDMA_IVB is not set
CONFIG_IDEDMA_AUTO=y
# CONFIG_BLK_DEV_HD is not set

#
# SCSI device support
#
CONFIG_SCSI=m
CONFIG_SCSI_PROC_FS=y

#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=m
# CONFIG_CHR_DEV_ST is not set
# CONFIG_CHR_DEV_OSST is not set
CONFIG_BLK_DEV_SR=m
CONFIG_BLK_DEV_SR_VENDOR=y
CONFIG_CHR_DEV_SG=m

#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
# CONFIG_SCSI_MULTI_LUN is not set
# CONFIG_SCSI_CONSTANTS is not set
# CONFIG_SCSI_LOGGING is not set

#
# SCSI Transport Attributes
#
# CONFIG_SCSI_SPI_ATTRS is not set
# CONFIG_SCSI_FC_ATTRS is not set
# CONFIG_SCSI_ISCSI_ATTRS is not set

#
# SCSI low-level drivers
#
# CONFIG_BLK_DEV_3W_XXXX_RAID is not set
# CONFIG_SCSI_3W_9XXX is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AACRAID is not set
# CONFIG_SCSI_AIC7XXX is not set
# CONFIG_SCSI_AIC7XXX_OLD is not set
# CONFIG_SCSI_AIC79XX is not set
# CONFIG_SCSI_DPT_I2O is not set
# CONFIG_MEGARAID_NEWGEN is not set
# CONFIG_MEGARAID_LEGACY is not set
CONFIG_SCSI_SATA=y
# CONFIG_SCSI_SATA_AHCI is not set
# CONFIG_SCSI_SATA_SVW is not set
# CONFIG_SCSI_ATA_PIIX is not set
CONFIG_SCSI_SATA_NV=y
# CONFIG_SCSI_SATA_PROMISE is not set
# CONFIG_SCSI_SATA_QSTOR is not set
# CONFIG_SCSI_SATA_SX4 is not set
# CONFIG_SCSI_SATA_SIL is not set
# CONFIG_SCSI_SATA_SIS is not set
# CONFIG_SCSI_SATA_ULI is not set
# CONFIG_SCSI_SATA_VIA is not set
# CONFIG_SCSI_SATA_VITESSE is not set
# CONFIG_SCSI_BUSLOGIC is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_EATA is not set
# CONFIG_SCSI_EATA_PIO is not set
# CONFIG_SCSI_FUTURE_DOMAIN is not set
# CONFIG_SCSI_GDTH is not set
# CONFIG_SCSI_IPS is not set
# CONFIG_SCSI_INITIO is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_PPA is not set
# CONFIG_SCSI_IMM is not set
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_IPR is not set
# CONFIG_SCSI_QLOGIC_ISP is not set
# CONFIG_SCSI_QLOGIC_FC is not set
# CONFIG_SCSI_QLOGIC_1280 is not set
CONFIG_SCSI_QLA2XXX=m
# CONFIG_SCSI_QLA21XX is not set
# CONFIG_SCSI_QLA22XX is not set
# CONFIG_SCSI_QLA2300 is not set
# CONFIG_SCSI_QLA2322 is not set
# CONFIG_SCSI_QLA6312 is not set
# CONFIG_SCSI_DC395x is not set
CONFIG_SCSI_DC390T=m
# CONFIG_SCSI_NSP32 is not set
# CONFIG_SCSI_DEBUG is not set

#
# Multi-device support (RAID and LVM)
#
CONFIG_MD=y
# CONFIG_BLK_DEV_MD is not set
CONFIG_BLK_DEV_DM=m
CONFIG_DM_CRYPT=m
CONFIG_DM_SNAPSHOT=m
CONFIG_DM_MIRROR=m
CONFIG_DM_ZERO=m

#
# Fusion MPT device support
#
# CONFIG_FUSION is not set

#
# IEEE 1394 (FireWire) support
#
CONFIG_IEEE1394=m

#
# Subsystem Options
#
# CONFIG_IEEE1394_VERBOSEDEBUG is not set
# CONFIG_IEEE1394_OUI_DB is not set
# CONFIG_IEEE1394_EXTRA_CONFIG_ROMS is not set

#
# Device Drivers
#
# CONFIG_IEEE1394_PCILYNX is not set
CONFIG_IEEE1394_OHCI1394=m

#
# Protocol Drivers
#
CONFIG_IEEE1394_VIDEO1394=m
CONFIG_IEEE1394_SBP2=m
# CONFIG_IEEE1394_SBP2_PHYS_DMA is not set
# CONFIG_IEEE1394_ETH1394 is not set
# CONFIG_IEEE1394_DV1394 is not set
CONFIG_IEEE1394_RAWIO=m
# CONFIG_IEEE1394_CMP is not set

#
# I2O device support
#
# CONFIG_I2O is not set

#
# Networking support
#
CONFIG_NET=y

#
# Networking options
#
CONFIG_PACKET=y
CONFIG_PACKET_MMAP=y
CONFIG_NETLINK_DEV=m
CONFIG_UNIX=y
# CONFIG_NET_KEY is not set
CONFIG_INET=y
# CONFIG_IP_MULTICAST is not set
# CONFIG_IP_ADVANCED_ROUTER is not set
# CONFIG_IP_PNP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_ARPD is not set
CONFIG_SYN_COOKIES=y
# CONFIG_INET_AH is not set
# CONFIG_INET_ESP is not set
# CONFIG_INET_IPCOMP is not set
# CONFIG_INET_TUNNEL is not set
CONFIG_IP_TCPDIAG=m
CONFIG_IP_TCPDIAG_IPV6=y

#
# IP: Virtual Server Configuration
#
# CONFIG_IP_VS is not set
CONFIG_IPV6=m
# CONFIG_IPV6_PRIVACY is not set
# CONFIG_INET6_AH is not set
# CONFIG_INET6_ESP is not set
# CONFIG_INET6_IPCOMP is not set
# CONFIG_INET6_TUNNEL is not set
# CONFIG_IPV6_TUNNEL is not set
CONFIG_NETFILTER=y
# CONFIG_NETFILTER_DEBUG is not set

#
# IP: Netfilter Configuration
#
CONFIG_IP_NF_CONNTRACK=m
CONFIG_IP_NF_CT_ACCT=y
CONFIG_IP_NF_CONNTRACK_MARK=y
# CONFIG_IP_NF_CT_PROTO_SCTP is not set
CONFIG_IP_NF_FTP=m
CONFIG_IP_NF_IRC=m
# CONFIG_IP_NF_TFTP is not set
# CONFIG_IP_NF_AMANDA is not set
# CONFIG_IP_NF_QUEUE is not set
CONFIG_IP_NF_IPTABLES=m
CONFIG_IP_NF_MATCH_LIMIT=m
CONFIG_IP_NF_MATCH_IPRANGE=m
CONFIG_IP_NF_MATCH_MAC=m
CONFIG_IP_NF_MATCH_PKTTYPE=m
CONFIG_IP_NF_MATCH_MARK=m
CONFIG_IP_NF_MATCH_MULTIPORT=m
CONFIG_IP_NF_MATCH_TOS=m
CONFIG_IP_NF_MATCH_RECENT=m
CONFIG_IP_NF_MATCH_ECN=m
CONFIG_IP_NF_MATCH_DSCP=m
CONFIG_IP_NF_MATCH_AH_ESP=m
CONFIG_IP_NF_MATCH_LENGTH=m
CONFIG_IP_NF_MATCH_TTL=m
CONFIG_IP_NF_MATCH_TCPMSS=m
CONFIG_IP_NF_MATCH_HELPER=m
CONFIG_IP_NF_MATCH_STATE=m
CONFIG_IP_NF_MATCH_CONNTRACK=m
CONFIG_IP_NF_MATCH_OWNER=m
CONFIG_IP_NF_MATCH_ADDRTYPE=m
CONFIG_IP_NF_MATCH_REALM=m
# CONFIG_IP_NF_MATCH_SCTP is not set
# CONFIG_IP_NF_MATCH_COMMENT is not set
CONFIG_IP_NF_MATCH_CONNMARK=m
CONFIG_IP_NF_MATCH_HASHLIMIT=m
CONFIG_IP_NF_FILTER=m
CONFIG_IP_NF_TARGET_REJECT=m
CONFIG_IP_NF_TARGET_LOG=m
CONFIG_IP_NF_TARGET_ULOG=m
CONFIG_IP_NF_TARGET_TCPMSS=m
CONFIG_IP_NF_NAT=m
CONFIG_IP_NF_NAT_NEEDED=y
CONFIG_IP_NF_TARGET_MASQUERADE=m
CONFIG_IP_NF_TARGET_REDIRECT=m
# CONFIG_IP_NF_TARGET_NETMAP is not set
# CONFIG_IP_NF_TARGET_SAME is not set
CONFIG_IP_NF_NAT_SNMP_BASIC=m
CONFIG_IP_NF_NAT_IRC=m
CONFIG_IP_NF_NAT_FTP=m
CONFIG_IP_NF_MANGLE=m
CONFIG_IP_NF_TARGET_TOS=m
CONFIG_IP_NF_TARGET_ECN=m
CONFIG_IP_NF_TARGET_DSCP=m
CONFIG_IP_NF_TARGET_MARK=m
CONFIG_IP_NF_TARGET_CLASSIFY=m
CONFIG_IP_NF_TARGET_CONNMARK=m
# CONFIG_IP_NF_TARGET_CLUSTERIP is not set
# CONFIG_IP_NF_RAW is not set
# CONFIG_IP_NF_ARPTABLES is not set

#
# IPv6: Netfilter Configuration
#
# CONFIG_IP6_NF_QUEUE is not set
# CONFIG_IP6_NF_IPTABLES is not set

#
# SCTP Configuration (EXPERIMENTAL)
#
# CONFIG_IP_SCTP is not set
# CONFIG_ATM is not set
# CONFIG_BRIDGE is not set
# CONFIG_VLAN_8021Q is not set
# CONFIG_DECNET is not set
# CONFIG_LLC2 is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_NET_DIVERT is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set

#
# QoS and/or fair queueing
#
CONFIG_NET_SCHED=y
# CONFIG_NET_SCH_CLK_JIFFIES is not set
CONFIG_NET_SCH_CLK_GETTIMEOFDAY=y
# CONFIG_NET_SCH_CLK_CPU is not set
CONFIG_NET_SCH_CBQ=m
CONFIG_NET_SCH_HTB=m
CONFIG_NET_SCH_HFSC=m
CONFIG_NET_SCH_PRIO=m
CONFIG_NET_SCH_RED=m
CONFIG_NET_SCH_SFQ=m
CONFIG_NET_SCH_TEQL=m
CONFIG_NET_SCH_TBF=m
CONFIG_NET_SCH_GRED=m
CONFIG_NET_SCH_DSMARK=m
# CONFIG_NET_SCH_NETEM is not set
CONFIG_NET_SCH_INGRESS=m
CONFIG_NET_QOS=y
CONFIG_NET_ESTIMATOR=y
CONFIG_NET_CLS=y
CONFIG_NET_CLS_TCINDEX=m
CONFIG_NET_CLS_ROUTE4=m
CONFIG_NET_CLS_ROUTE=y
CONFIG_NET_CLS_FW=m
CONFIG_NET_CLS_U32=m
# CONFIG_CLS_U32_PERF is not set
# CONFIG_NET_CLS_IND is not set
# CONFIG_CLS_U32_MARK is not set
CONFIG_NET_CLS_RSVP=m
# CONFIG_NET_CLS_RSVP6 is not set
# CONFIG_NET_CLS_ACT is not set
CONFIG_NET_CLS_POLICE=y

#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
# CONFIG_NETPOLL is not set
# CONFIG_NET_POLL_CONTROLLER is not set
# CONFIG_HAMRADIO is not set
# CONFIG_IRDA is not set
# CONFIG_BT is not set
CONFIG_NETDEVICES=y
# CONFIG_DUMMY is not set
# CONFIG_BONDING is not set
# CONFIG_EQUALIZER is not set
CONFIG_TUN=m
# CONFIG_ETHERTAP is not set
# CONFIG_NET_SB1000 is not set

#
# ARCnet devices
#
CONFIG_ARCNET=m
# CONFIG_ARCNET_1201 is not set
CONFIG_ARCNET_1051=m
# CONFIG_ARCNET_RAW is not set
# CONFIG_ARCNET_CAP is not set
CONFIG_ARCNET_COM90xx=m
CONFIG_ARCNET_COM90xxIO=m
CONFIG_ARCNET_RIM_I=m
CONFIG_ARCNET_COM20020=m
CONFIG_ARCNET_COM20020_PCI=m

#
# Ethernet (10 or 100Mbit)
#
CONFIG_NET_ETHERNET=y
CONFIG_MII=m
# CONFIG_HAPPYMEAL is not set
# CONFIG_SUNGEM is not set
CONFIG_NET_VENDOR_3COM=y
CONFIG_VORTEX=m
# CONFIG_TYPHOON is not set

#
# Tulip family network device support
#
# CONFIG_NET_TULIP is not set
# CONFIG_HP100 is not set
CONFIG_NET_PCI=y
# CONFIG_PCNET32 is not set
# CONFIG_AMD8111_ETH is not set
# CONFIG_ADAPTEC_STARFIRE is not set
# CONFIG_B44 is not set
CONFIG_FORCEDETH=m
# CONFIG_DGRS is not set
CONFIG_EEPRO100=m
CONFIG_E100=m
# CONFIG_E100_NAPI is not set
# CONFIG_FEALNX is not set
# CONFIG_NATSEMI is not set
CONFIG_NE2K_PCI=m
CONFIG_8139CP=m
CONFIG_8139TOO=m
# CONFIG_8139TOO_PIO is not set
# CONFIG_8139TOO_TUNE_TWISTER is not set
CONFIG_8139TOO_8129=y
# CONFIG_8139_OLD_RX_RESET is not set
# CONFIG_SIS900 is not set
# CONFIG_EPIC100 is not set
# CONFIG_SUNDANCE is not set
# CONFIG_TLAN is not set
CONFIG_VIA_RHINE=m
CONFIG_VIA_RHINE_MMIO=y

#
# Ethernet (1000 Mbit)
#
# CONFIG_ACENIC is not set
# CONFIG_DL2K is not set
CONFIG_E1000=m
# CONFIG_E1000_NAPI is not set
# CONFIG_NS83820 is not set
# CONFIG_HAMACHI is not set
# CONFIG_YELLOWFIN is not set
# CONFIG_R8169 is not set
CONFIG_SK98LIN=m
# CONFIG_VIA_VELOCITY is not set
# CONFIG_TIGON3 is not set

#
# Ethernet (10000 Mbit)
#
# CONFIG_IXGB is not set
# CONFIG_S2IO is not set

#
# Token Ring devices
#
# CONFIG_TR is not set

#
# Wireless LAN (non-hamradio)
#
# CONFIG_NET_RADIO is not set

#
# Wan interfaces
#
# CONFIG_WAN is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
# CONFIG_PLIP is not set
# CONFIG_PPP is not set
# CONFIG_SLIP is not set
# CONFIG_NET_FC is not set
# CONFIG_SHAPER is not set
# CONFIG_NETCONSOLE is not set

#
# ISDN subsystem
#
# CONFIG_ISDN is not set

#
# Telephony Support
#
# CONFIG_PHONE is not set

#
# Input device support
#
CONFIG_INPUT=y

#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
# CONFIG_INPUT_MOUSEDEV_PSAUX is not set
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1280
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=1024
CONFIG_INPUT_JOYDEV=m
# CONFIG_INPUT_TSDEV is not set
CONFIG_INPUT_EVDEV=m
# CONFIG_INPUT_EVBUG is not set

#
# Input I/O drivers
#
CONFIG_GAMEPORT=m
CONFIG_SOUND_GAMEPORT=m
CONFIG_GAMEPORT_NS558=m
# CONFIG_GAMEPORT_L4 is not set
CONFIG_GAMEPORT_EMU10K1=m
# CONFIG_GAMEPORT_VORTEX is not set
# CONFIG_GAMEPORT_FM801 is not set
# CONFIG_GAMEPORT_CS461X is not set
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
CONFIG_SERIO_SERPORT=y
# CONFIG_SERIO_CT82C710 is not set
# CONFIG_SERIO_PARKBD is not set
# CONFIG_SERIO_PCIPS2 is not set
CONFIG_SERIO_LIBPS2=y
# CONFIG_SERIO_RAW is not set

#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_LKKBD is not set
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_KEYBOARD_NEWTON is not set
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=m
CONFIG_MOUSE_SERIAL=m
# CONFIG_MOUSE_VSXXXAA is not set
CONFIG_INPUT_JOYSTICK=y
# CONFIG_JOYSTICK_ANALOG is not set
# CONFIG_JOYSTICK_A3D is not set
# CONFIG_JOYSTICK_ADI is not set
# CONFIG_JOYSTICK_COBRA is not set
# CONFIG_JOYSTICK_GF2K is not set
# CONFIG_JOYSTICK_GRIP is not set
# CONFIG_JOYSTICK_GRIP_MP is not set
# CONFIG_JOYSTICK_GUILLEMOT is not set
# CONFIG_JOYSTICK_INTERACT is not set
CONFIG_JOYSTICK_SIDEWINDER=m
# CONFIG_JOYSTICK_TMDC is not set
# CONFIG_JOYSTICK_IFORCE is not set
# CONFIG_JOYSTICK_WARRIOR is not set
# CONFIG_JOYSTICK_MAGELLAN is not set
# CONFIG_JOYSTICK_SPACEORB is not set
# CONFIG_JOYSTICK_SPACEBALL is not set
# CONFIG_JOYSTICK_STINGER is not set
# CONFIG_JOYSTICK_TWIDDLER is not set
# CONFIG_JOYSTICK_DB9 is not set
# CONFIG_JOYSTICK_GAMECON is not set
# CONFIG_JOYSTICK_TURBOGRAFX is not set
# CONFIG_JOYSTICK_JOYDUMP is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
# CONFIG_INPUT_MISC is not set

#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
CONFIG_SERIAL_NONSTANDARD=y
# CONFIG_COMPUTONE is not set
# CONFIG_ROCKETPORT is not set
# CONFIG_CYCLADES is not set
# CONFIG_DIGIEPCA is not set
# CONFIG_DIGI is not set
# CONFIG_MOXA_INTELLIO is not set
# CONFIG_MOXA_SMARTIO is not set
# CONFIG_ISI is not set
# CONFIG_SYNCLINK is not set
# CONFIG_SYNCLINKMP is not set
CONFIG_N_HDLC=m
# CONFIG_RISCOM8 is not set
# CONFIG_SPECIALIX is not set
# CONFIG_SX is not set
# CONFIG_RIO is not set
# CONFIG_STALDRV is not set

#
# Serial drivers
#
CONFIG_SERIAL_8250=m
# CONFIG_SERIAL_8250_ACPI is not set
CONFIG_SERIAL_8250_NR_UARTS=4
CONFIG_SERIAL_8250_EXTENDED=y
# CONFIG_SERIAL_8250_MANY_PORTS is not set
CONFIG_SERIAL_8250_SHARE_IRQ=y
# CONFIG_SERIAL_8250_DETECT_IRQ is not set
# CONFIG_SERIAL_8250_MULTIPORT is not set
# CONFIG_SERIAL_8250_RSA is not set

#
# Non-8250 serial port support
#
CONFIG_SERIAL_CORE=m
CONFIG_UNIX98_PTYS=y
# CONFIG_LEGACY_PTYS is not set
# CONFIG_PRINTER is not set
# CONFIG_PPDEV is not set
# CONFIG_TIPAR is not set

#
# IPMI
#
# CONFIG_IPMI_HANDLER is not set

#
# Watchdog Cards
#
# CONFIG_WATCHDOG is not set
CONFIG_HW_RANDOM=m
CONFIG_NVRAM=m
CONFIG_RTC=y
# CONFIG_DTLK is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
# CONFIG_SONYPI is not set

#
# Ftape, the floppy tape device driver
#
# CONFIG_FTAPE is not set
CONFIG_AGP=y
# CONFIG_AGP_ALI is not set
# CONFIG_AGP_ATI is not set
# CONFIG_AGP_AMD is not set
# CONFIG_AGP_AMD64 is not set
# CONFIG_AGP_INTEL is not set
# CONFIG_AGP_INTEL_MCH is not set
CONFIG_AGP_NVIDIA=y
# CONFIG_AGP_SIS is not set
# CONFIG_AGP_SWORKS is not set
# CONFIG_AGP_VIA is not set
# CONFIG_AGP_EFFICEON is not set
# CONFIG_DRM is not set
# CONFIG_MWAVE is not set
# CONFIG_RAW_DRIVER is not set
# CONFIG_HPET is not set
# CONFIG_HANGCHECK_TIMER is not set

#
# I2C support
#
CONFIG_I2C=m
CONFIG_I2C_CHARDEV=m

#
# I2C Algorithms
#
CONFIG_I2C_ALGOBIT=m
CONFIG_I2C_ALGOPCF=m
CONFIG_I2C_ALGOPCA=m

#
# I2C Hardware Bus support
#
# CONFIG_I2C_ALI1535 is not set
# CONFIG_I2C_ALI1563 is not set
# CONFIG_I2C_ALI15X3 is not set
CONFIG_I2C_AMD756=m
# CONFIG_I2C_AMD756_S4882 is not set
# CONFIG_I2C_AMD8111 is not set
# CONFIG_I2C_I801 is not set
# CONFIG_I2C_I810 is not set
# CONFIG_I2C_ISA is not set
CONFIG_I2C_NFORCE2=m
# CONFIG_I2C_PARPORT is not set
# CONFIG_I2C_PARPORT_LIGHT is not set
# CONFIG_I2C_PIIX4 is not set
# CONFIG_I2C_PROSAVAGE is not set
# CONFIG_I2C_SAVAGE4 is not set
# CONFIG_SCx200_ACB is not set
# CONFIG_I2C_SIS5595 is not set
# CONFIG_I2C_SIS630 is not set
# CONFIG_I2C_SIS96X is not set
# CONFIG_I2C_STUB is not set
# CONFIG_I2C_VIA is not set
# CONFIG_I2C_VIAPRO is not set
# CONFIG_I2C_VOODOO3 is not set
# CONFIG_I2C_PCA_ISA is not set

#
# Hardware Sensors Chip support
#
CONFIG_I2C_SENSOR=m
# CONFIG_SENSORS_ADM1021 is not set
# CONFIG_SENSORS_ADM1025 is not set
# CONFIG_SENSORS_ADM1026 is not set
# CONFIG_SENSORS_ADM1031 is not set
# CONFIG_SENSORS_ASB100 is not set
# CONFIG_SENSORS_DS1621 is not set
# CONFIG_SENSORS_FSCHER is not set
# CONFIG_SENSORS_GL518SM is not set
# CONFIG_SENSORS_IT87 is not set
# CONFIG_SENSORS_LM63 is not set
# CONFIG_SENSORS_LM75 is not set
# CONFIG_SENSORS_LM77 is not set
# CONFIG_SENSORS_LM78 is not set
# CONFIG_SENSORS_LM80 is not set
# CONFIG_SENSORS_LM83 is not set
# CONFIG_SENSORS_LM85 is not set
# CONFIG_SENSORS_LM87 is not set
# CONFIG_SENSORS_LM90 is not set
# CONFIG_SENSORS_MAX1619 is not set
# CONFIG_SENSORS_PC87360 is not set
# CONFIG_SENSORS_SMSC47B397 is not set
# CONFIG_SENSORS_SMSC47M1 is not set
# CONFIG_SENSORS_VIA686A is not set
CONFIG_SENSORS_W83781D=m
CONFIG_SENSORS_W83L785TS=m
CONFIG_SENSORS_W83627HF=m

#
# Other I2C Chip support
#
# CONFIG_SENSORS_EEPROM is not set
# CONFIG_SENSORS_PCF8574 is not set
# CONFIG_SENSORS_PCF8591 is not set
# CONFIG_SENSORS_RTC8564 is not set
# CONFIG_I2C_DEBUG_CORE is not set
# CONFIG_I2C_DEBUG_ALGO is not set
# CONFIG_I2C_DEBUG_BUS is not set
# CONFIG_I2C_DEBUG_CHIP is not set

#
# Dallas's 1-wire bus
#
# CONFIG_W1 is not set

#
# Misc devices
#
# CONFIG_IBM_ASM is not set

#
# Multimedia devices
#
# CONFIG_VIDEO_DEV is not set

#
# Digital Video Broadcasting Devices
#
# CONFIG_DVB is not set

#
# Graphics support
#
# CONFIG_FB is not set
CONFIG_VIDEO_SELECT=y

#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
CONFIG_DUMMY_CONSOLE=y

#
# Sound
#
CONFIG_SOUND=m

#
# Advanced Linux Sound Architecture
#
CONFIG_SND=m
CONFIG_SND_TIMER=m
CONFIG_SND_PCM=m
CONFIG_SND_HWDEP=m
CONFIG_SND_RAWMIDI=m
CONFIG_SND_SEQUENCER=m
# CONFIG_SND_SEQ_DUMMY is not set
CONFIG_SND_OSSEMUL=y
CONFIG_SND_MIXER_OSS=m
CONFIG_SND_PCM_OSS=m
CONFIG_SND_SEQUENCER_OSS=y
CONFIG_SND_RTCTIMER=m
# CONFIG_SND_VERBOSE_PRINTK is not set
# CONFIG_SND_DEBUG is not set

#
# Generic devices
#
CONFIG_SND_MPU401_UART=m
# CONFIG_SND_DUMMY is not set
# CONFIG_SND_VIRMIDI is not set
# CONFIG_SND_MTPAV is not set
# CONFIG_SND_SERIAL_U16550 is not set
CONFIG_SND_MPU401=m

#
# PCI devices
#
CONFIG_SND_AC97_CODEC=m
# CONFIG_SND_ALI5451 is not set
# CONFIG_SND_ATIIXP is not set
# CONFIG_SND_ATIIXP_MODEM is not set
# CONFIG_SND_AU8810 is not set
# CONFIG_SND_AU8820 is not set
# CONFIG_SND_AU8830 is not set
# CONFIG_SND_AZT3328 is not set
# CONFIG_SND_BT87X is not set
# CONFIG_SND_CS46XX is not set
# CONFIG_SND_CS4281 is not set
CONFIG_SND_EMU10K1=m
# CONFIG_SND_EMU10K1X is not set
# CONFIG_SND_CA0106 is not set
# CONFIG_SND_KORG1212 is not set
# CONFIG_SND_MIXART is not set
# CONFIG_SND_NM256 is not set
# CONFIG_SND_RME32 is not set
# CONFIG_SND_RME96 is not set
# CONFIG_SND_RME9652 is not set
# CONFIG_SND_HDSP is not set
# CONFIG_SND_TRIDENT is not set
# CONFIG_SND_YMFPCI is not set
# CONFIG_SND_ALS4000 is not set
# CONFIG_SND_CMIPCI is not set
# CONFIG_SND_ENS1370 is not set
# CONFIG_SND_ENS1371 is not set
# CONFIG_SND_ES1938 is not set
# CONFIG_SND_ES1968 is not set
# CONFIG_SND_MAESTRO3 is not set
# CONFIG_SND_FM801 is not set
# CONFIG_SND_ICE1712 is not set
# CONFIG_SND_ICE1724 is not set
CONFIG_SND_INTEL8X0=m
# CONFIG_SND_INTEL8X0M is not set
# CONFIG_SND_SONICVIBES is not set
# CONFIG_SND_VIA82XX is not set
# CONFIG_SND_VIA82XX_MODEM is not set
# CONFIG_SND_VX222 is not set

#
# USB devices
#
# CONFIG_SND_USB_AUDIO is not set
# CONFIG_SND_USB_USX2Y is not set

#
# Open Sound System
#
# CONFIG_SOUND_PRIME is not set

#
# USB support
#
CONFIG_USB=m
# CONFIG_USB_DEBUG is not set

#
# Miscellaneous USB options
#
CONFIG_USB_DEVICEFS=y
CONFIG_USB_BANDWIDTH=y
# CONFIG_USB_DYNAMIC_MINORS is not set
# CONFIG_USB_OTG is not set
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB_ARCH_HAS_OHCI=y

#
# USB Host Controller Drivers
#
CONFIG_USB_EHCI_HCD=m
# CONFIG_USB_EHCI_SPLIT_ISO is not set
# CONFIG_USB_EHCI_ROOT_HUB_TT is not set
CONFIG_USB_OHCI_HCD=m
# CONFIG_USB_UHCI_HCD is not set
# CONFIG_USB_SL811_HCD is not set

#
# USB Device Class drivers
#
# CONFIG_USB_AUDIO is not set
# CONFIG_USB_BLUETOOTH_TTY is not set
# CONFIG_USB_MIDI is not set
# CONFIG_USB_ACM is not set
# CONFIG_USB_PRINTER is not set

#
# NOTE: USB_STORAGE enables SCSI, and 'SCSI disk support' may also be needed; see USB_STORAGE Help for more information
#
CONFIG_USB_STORAGE=m
# CONFIG_USB_STORAGE_DEBUG is not set
# CONFIG_USB_STORAGE_RW_DETECT is not set
# CONFIG_USB_STORAGE_DATAFAB is not set
# CONFIG_USB_STORAGE_FREECOM is not set
# CONFIG_USB_STORAGE_ISD200 is not set
# CONFIG_USB_STORAGE_DPCM is not set
# CONFIG_USB_STORAGE_HP8200e is not set
# CONFIG_USB_STORAGE_SDDR09 is not set
# CONFIG_USB_STORAGE_SDDR55 is not set
# CONFIG_USB_STORAGE_JUMPSHOT is not set

#
# USB Input Devices
#
CONFIG_USB_HID=m
CONFIG_USB_HIDINPUT=y
# CONFIG_HID_FF is not set
# CONFIG_USB_HIDDEV is not set

#
# USB HID Boot Protocol drivers
#
# CONFIG_USB_KBD is not set
# CONFIG_USB_MOUSE is not set
# CONFIG_USB_AIPTEK is not set
# CONFIG_USB_WACOM is not set
# CONFIG_USB_KBTAB is not set
# CONFIG_USB_POWERMATE is not set
# CONFIG_USB_MTOUCH is not set
# CONFIG_USB_EGALAX is not set
# CONFIG_USB_XPAD is not set
# CONFIG_USB_ATI_REMOTE is not set

#
# USB Imaging devices
#
# CONFIG_USB_MDC800 is not set
# CONFIG_USB_MICROTEK is not set

#
# USB Multimedia devices
#
# CONFIG_USB_DABUSB is not set

#
# Video4Linux support is needed for USB Multimedia device support
#

#
# USB Network Adapters
#
# CONFIG_USB_CATC is not set
# CONFIG_USB_KAWETH is not set
# CONFIG_USB_PEGASUS is not set
# CONFIG_USB_RTL8150 is not set
# CONFIG_USB_USBNET is not set

#
# USB port drivers
#
# CONFIG_USB_USS720 is not set

#
# USB Serial Converter support
#
# CONFIG_USB_SERIAL is not set

#
# USB Miscellaneous drivers
#
# CONFIG_USB_EMI62 is not set
# CONFIG_USB_EMI26 is not set
# CONFIG_USB_AUERSWALD is not set
# CONFIG_USB_RIO500 is not set
# CONFIG_USB_LEGOTOWER is not set
# CONFIG_USB_LCD is not set
# CONFIG_USB_LED is not set
# CONFIG_USB_CYTHERM is not set
# CONFIG_USB_PHIDGETKIT is not set
# CONFIG_USB_PHIDGETSERVO is not set
# CONFIG_USB_IDMOUSE is not set
# CONFIG_USB_TEST is not set

#
# USB ATM/DSL drivers
#

#
# USB Gadget Support
#
# CONFIG_USB_GADGET is not set

#
# MMC/SD Card support
#
# CONFIG_MMC is not set

#
# InfiniBand support
#
# CONFIG_INFINIBAND is not set

#
# File systems
#
CONFIG_EXT2_FS=y
# CONFIG_EXT2_FS_XATTR is not set
CONFIG_EXT3_FS=y
# CONFIG_EXT3_FS_XATTR is not set
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
CONFIG_REISERFS_FS=y
# CONFIG_REISERFS_CHECK is not set
# CONFIG_REISERFS_PROC_INFO is not set
# CONFIG_REISERFS_FS_XATTR is not set
# CONFIG_JFS_FS is not set

#
# XFS support
#
# CONFIG_XFS_FS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_ROMFS_FS is not set
# CONFIG_QUOTA is not set
CONFIG_DNOTIFY=y
# CONFIG_AUTOFS_FS is not set
# CONFIG_AUTOFS4_FS is not set

#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=m
CONFIG_JOLIET=y
CONFIG_ZISOFS=y
CONFIG_ZISOFS_FS=m
CONFIG_UDF_FS=m
CONFIG_UDF_NLS=y

#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=m
CONFIG_MSDOS_FS=m
CONFIG_VFAT_FS=m
CONFIG_FAT_DEFAULT_CODEPAGE=850
CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-15"
CONFIG_NTFS_FS=m
# CONFIG_NTFS_DEBUG is not set
# CONFIG_NTFS_RW is not set

#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
# CONFIG_PROC_KCORE is not set
CONFIG_SYSFS=y
# CONFIG_DEVFS_FS is not set
# CONFIG_DEVPTS_FS_XATTR is not set
CONFIG_TMPFS=y
# CONFIG_TMPFS_XATTR is not set
# CONFIG_HUGETLBFS is not set
# CONFIG_HUGETLB_PAGE is not set
CONFIG_RAMFS=y

#
# Miscellaneous filesystems
#
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
CONFIG_HFS_FS=m
CONFIG_HFSPLUS_FS=m
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EFS_FS is not set
# CONFIG_CRAMFS is not set
# CONFIG_VXFS_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set

#
# Network File Systems
#
# CONFIG_NFS_FS is not set
# CONFIG_NFSD is not set
CONFIG_SMB_FS=m
CONFIG_SMB_NLS_DEFAULT=y
CONFIG_SMB_NLS_REMOTE="cp850"
CONFIG_CIFS=m
# CONFIG_CIFS_STATS is not set
# CONFIG_CIFS_XATTR is not set
# CONFIG_CIFS_EXPERIMENTAL is not set
# CONFIG_NCP_FS is not set
# CONFIG_CODA_FS is not set
# CONFIG_AFS_FS is not set

#
# Partition Types
#
# CONFIG_PARTITION_ADVANCED is not set
CONFIG_MSDOS_PARTITION=y

#
# Native Language Support
#
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="cp850"
CONFIG_NLS_CODEPAGE_437=m
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
CONFIG_NLS_CODEPAGE_850=m
# CONFIG_NLS_CODEPAGE_852 is not set
# CONFIG_NLS_CODEPAGE_855 is not set
# CONFIG_NLS_CODEPAGE_857 is not set
# CONFIG_NLS_CODEPAGE_860 is not set
# CONFIG_NLS_CODEPAGE_861 is not set
# CONFIG_NLS_CODEPAGE_862 is not set
# CONFIG_NLS_CODEPAGE_863 is not set
# CONFIG_NLS_CODEPAGE_864 is not set
# CONFIG_NLS_CODEPAGE_865 is not set
# CONFIG_NLS_CODEPAGE_866 is not set
# CONFIG_NLS_CODEPAGE_869 is not set
# CONFIG_NLS_CODEPAGE_936 is not set
# CONFIG_NLS_CODEPAGE_950 is not set
# CONFIG_NLS_CODEPAGE_932 is not set
# CONFIG_NLS_CODEPAGE_949 is not set
# CONFIG_NLS_CODEPAGE_874 is not set
# CONFIG_NLS_ISO8859_8 is not set
# CONFIG_NLS_CODEPAGE_1250 is not set
# CONFIG_NLS_CODEPAGE_1251 is not set
# CONFIG_NLS_ASCII is not set
CONFIG_NLS_ISO8859_1=m
# CONFIG_NLS_ISO8859_2 is not set
# CONFIG_NLS_ISO8859_3 is not set
# CONFIG_NLS_ISO8859_4 is not set
# CONFIG_NLS_ISO8859_5 is not set
# CONFIG_NLS_ISO8859_6 is not set
# CONFIG_NLS_ISO8859_7 is not set
# CONFIG_NLS_ISO8859_9 is not set
# CONFIG_NLS_ISO8859_13 is not set
# CONFIG_NLS_ISO8859_14 is not set
CONFIG_NLS_ISO8859_15=m
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
CONFIG_NLS_UTF8=m

#
# Profiling support
#
# CONFIG_PROFILING is not set

#
# Kernel hacking
#
CONFIG_DEBUG_KERNEL=y
CONFIG_MAGIC_SYSRQ=y
# CONFIG_SCHEDSTATS is not set
# CONFIG_DEBUG_SLAB is not set
CONFIG_DEBUG_PREEMPT=y
# CONFIG_DEBUG_SPINLOCK is not set
# CONFIG_DEBUG_SPINLOCK_SLEEP is not set
# CONFIG_DEBUG_KOBJECT is not set
CONFIG_DEBUG_BUGVERBOSE=y
# CONFIG_DEBUG_INFO is not set
# CONFIG_DEBUG_FS is not set
# CONFIG_FRAME_POINTER is not set
CONFIG_EARLY_PRINTK=y
# CONFIG_DEBUG_STACKOVERFLOW is not set
# CONFIG_KPROBES is not set
# CONFIG_DEBUG_STACK_USAGE is not set
# CONFIG_DEBUG_PAGEALLOC is not set
# CONFIG_4KSTACKS is not set

#
# Security options
#
# CONFIG_KEYS is not set
# CONFIG_SECURITY is not set

#
# Cryptographic options
#
CONFIG_CRYPTO=y
# CONFIG_CRYPTO_HMAC is not set
# CONFIG_CRYPTO_NULL is not set
# CONFIG_CRYPTO_MD4 is not set
# CONFIG_CRYPTO_MD5 is not set
# CONFIG_CRYPTO_SHA1 is not set
# CONFIG_CRYPTO_SHA256 is not set
# CONFIG_CRYPTO_SHA512 is not set
# CONFIG_CRYPTO_WP512 is not set
# CONFIG_CRYPTO_DES is not set
# CONFIG_CRYPTO_BLOWFISH is not set
# CONFIG_CRYPTO_TWOFISH is not set
# CONFIG_CRYPTO_SERPENT is not set
# CONFIG_CRYPTO_AES_586 is not set
# CONFIG_CRYPTO_CAST5 is not set
# CONFIG_CRYPTO_CAST6 is not set
# CONFIG_CRYPTO_TEA is not set
# CONFIG_CRYPTO_ARC4 is not set
# CONFIG_CRYPTO_KHAZAD is not set
# CONFIG_CRYPTO_ANUBIS is not set
# CONFIG_CRYPTO_DEFLATE is not set
# CONFIG_CRYPTO_MICHAEL_MIC is not set
# CONFIG_CRYPTO_CRC32C is not set
# CONFIG_CRYPTO_TEST is not set

#
# Hardware crypto devices
#
# CONFIG_CRYPTO_DEV_PADLOCK is not set

#
# Library routines
#
# CONFIG_CRC_CCITT is not set
CONFIG_CRC32=y
# CONFIG_LIBCRC32C is not set
CONFIG_ZLIB_INFLATE=m
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_X86_BIOS_REBOOT=y
CONFIG_PC=y

Re: How's the nforce4 support in Linux?

[Lee Revell]

On Fri, 2005-03-25 at 23:59 +0100, Julien Wajsberg wrote:
> - audio works too. The only problem is that two applications can't
> open /dev/dsp in the same time.

Not a problem.  ALSA does software mixing for chipsets that can't do it
in hardware.  Google for dmix.

However this doesn't (and can't be made to) work with the in-kernel OSS
emulation (it works fine with the alsa-lib/libaoss emulation).  So you
are technically correct in that two OSS apps can't open /dev/dsp at the
same time, but there is no problem with multiple apps sharing the sound
device, as long as they use the ALSA API (which they should be using
anyway).

Lee

Re: How's the nforce4 support in Linux?

[Julien Wajsberg]

On Fri, 25 Mar 2005 18:14:22 -0500, Lee Revell <rlrevell@joe-job.com> wrote:
> On Fri, 2005-03-25 at 23:59 +0100, Julien Wajsberg wrote:
> > - audio works too. The only problem is that two applications can't
> > open /dev/dsp in the same time.
> 
> Not a problem.  ALSA does software mixing for chipsets that can't do it
> in hardware.  Google for dmix.
> 
> However this doesn't (and can't be made to) work with the in-kernel OSS
> emulation (it works fine with the alsa-lib/libaoss emulation).  So you
> are technically correct in that two OSS apps can't open /dev/dsp at the
> same time, but there is no problem with multiple apps sharing the sound
> device, as long as they use the ALSA API (which they should be using
> anyway).

Okay, good to know. Then I'll have to find out why beep-media-player
doesn't work with alsa :-)

-- 
Julien

Re: How's the nforce4 support in Linux?

[Lee Revell]

On Sat, 2005-03-26 at 01:38 +0100, Julien Wajsberg wrote:
> On Fri, 25 Mar 2005 18:14:22 -0500, Lee Revell <rlrevell@joe-job.com> wrote:
> > On Fri, 2005-03-25 at 23:59 +0100, Julien Wajsberg wrote:
> > > - audio works too. The only problem is that two applications can't
> > > open /dev/dsp in the same time.
> > 
> > Not a problem.  ALSA does software mixing for chipsets that can't do it
> > in hardware.  Google for dmix.
> > 
> > However this doesn't (and can't be made to) work with the in-kernel OSS
> > emulation (it works fine with the alsa-lib/libaoss emulation).  So you
> > are technically correct in that two OSS apps can't open /dev/dsp at the
> > same time, but there is no problem with multiple apps sharing the sound
> > device, as long as they use the ALSA API (which they should be using
> > anyway).
> 
> Okay, good to know. Then I'll have to find out why beep-media-player
> doesn't work with alsa :-)
> 

Without knowing anything about it, I'm willing to guess "programmer
laziness/lack of time" (depending on your perspective).  As long as ALSA
continues to provide OSS emulation, lazy developers will not update
their apps to the (superior) ALSA API.

I just upgraded all my home machines to a Gnome 2.10 based distro and
way shocked to find that it still uses esd via OSS emulation for system
sounds.  So the endless user complaints about "wtf, esd is blocking my
sound device, on windows my apps can share it" will not be going away in
the forseeable future.

Ugh.  dmix has only been available for, oh, 18 months, and the apps
still have not caught up.

Lee

Re: How's the nforce4 support in Linux?

[Tomasz Torcz]

On Fri, Mar 25, 2005 at 06:14:22PM -0500, Lee Revell wrote:
> On Fri, 2005-03-25 at 23:59 +0100, Julien Wajsberg wrote:
> > - audio works too. The only problem is that two applications can't
> > open /dev/dsp in the same time.
> 
> Not a problem.  ALSA does software mixing for chipsets that can't do it
> in hardware.  Google for dmix.
> 
> However this doesn't (and can't be made to) work with the in-kernel OSS
> emulation (it works fine with the alsa-lib/libaoss emulation).  So you

 quake3 still segfaults when run through "aoss". And can't be fixed, as
it's closed source still.

-- 
Tomasz Torcz               "Never underestimate the bandwidth of a station
zdzichu@irc.-nie.spam-.pl    wagon filled with backup tapes." -- Jim Gray

Re: How's the nforce4 support in Linux?

[Lee Revell]

On Tue, 2005-03-29 at 20:58 +0200, Tomasz Torcz wrote:
> On Fri, Mar 25, 2005 at 06:14:22PM -0500, Lee Revell wrote:
> > On Fri, 2005-03-25 at 23:59 +0100, Julien Wajsberg wrote:
> > > - audio works too. The only problem is that two applications can't
> > > open /dev/dsp in the same time.
> > 
> > Not a problem.  ALSA does software mixing for chipsets that can't do it
> > in hardware.  Google for dmix.
> > 
> > However this doesn't (and can't be made to) work with the in-kernel OSS
> > emulation (it works fine with the alsa-lib/libaoss emulation).  So you
> 
>  quake3 still segfaults when run through "aoss". And can't be fixed, as
> it's closed source still.
> 

I guess that's Quake3's problem...

Lee

Re: How's the nforce4 support in Linux?

[Tomasz Torcz]

On Tue, Mar 29, 2005 at 03:40:07PM -0500, Lee Revell wrote:
> On Tue, 2005-03-29 at 20:58 +0200, Tomasz Torcz wrote:
> > On Fri, Mar 25, 2005 at 06:14:22PM -0500, Lee Revell wrote:
> > > On Fri, 2005-03-25 at 23:59 +0100, Julien Wajsberg wrote:
> > > > - audio works too. The only problem is that two applications can't
> > > > open /dev/dsp in the same time.
> > > 
> > > Not a problem.  ALSA does software mixing for chipsets that can't do it
> > > in hardware.  Google for dmix.
> > > 
> > > However this doesn't (and can't be made to) work with the in-kernel OSS
> > > emulation (it works fine with the alsa-lib/libaoss emulation).  So you
> > 
> >  quake3 still segfaults when run through "aoss". And can't be fixed, as
> > it's closed source still.
> > 
> I guess that's Quake3's problem...

 It an glaring example, dmix is unsufficient in one third of my sound
uses (other two beeing movie and music playback)
 But you advertise dmix like it was silver bullet.

-- 
Tomasz Torcz               "Never underestimate the bandwidth of a station
zdzichu@irc.-nie.spam-.pl    wagon filled with backup tapes." -- Jim Gray

Re: How's the nforce4 support in Linux?

[Lennart Sorensen]

On Wed, Mar 30, 2005 at 05:00:23PM +0200, Tomasz Torcz wrote:
>  It an glaring example, dmix is unsufficient in one third of my sound
> uses (other two beeing movie and music playback)
>  But you advertise dmix like it was silver bullet.

An emu10k1 is a silver bullet. :)

Len Sorensen

Re: How's the nforce4 support in Linux?

[Martin Schlemmer]

[-- Attachment #1: Type: text/plain, Size: 1233 bytes --]

On Wed, 2005-03-30 at 17:00 +0200, Tomasz Torcz wrote:
> On Tue, Mar 29, 2005 at 03:40:07PM -0500, Lee Revell wrote:
> > On Tue, 2005-03-29 at 20:58 +0200, Tomasz Torcz wrote:
> > > On Fri, Mar 25, 2005 at 06:14:22PM -0500, Lee Revell wrote:
> > > > On Fri, 2005-03-25 at 23:59 +0100, Julien Wajsberg wrote:
> > > > > - audio works too. The only problem is that two applications can't
> > > > > open /dev/dsp in the same time.
> > > > 
> > > > Not a problem.  ALSA does software mixing for chipsets that can't do it
> > > > in hardware.  Google for dmix.
> > > > 
> > > > However this doesn't (and can't be made to) work with the in-kernel OSS
> > > > emulation (it works fine with the alsa-lib/libaoss emulation).  So you
> > > 
> > >  quake3 still segfaults when run through "aoss". And can't be fixed, as
> > > it's closed source still.
> > > 
> > I guess that's Quake3's problem...
> 
>  It an glaring example, dmix is unsufficient in one third of my sound
> uses (other two beeing movie and music playback)
>  But you advertise dmix like it was silver bullet.
> 

Or goes limbo randomly and no mailing to lists seems to result in a
reply (from the alsa peeps at least) ...


-- 
Martin Schlemmer


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: How's the nforce4 support in Linux?

[Lee Revell]

On Wed, 2005-03-30 at 21:19 +0200, Martin Schlemmer wrote:
> On Wed, 2005-03-30 at 17:00 +0200, Tomasz Torcz wrote:
> > > >  quake3 still segfaults when run through "aoss". And can't be fixed, as
> > > > it's closed source still.
> > > > 
> > > I guess that's Quake3's problem...
> > 
> >  It an glaring example, dmix is unsufficient in one third of my sound
> > uses (other two beeing movie and music playback)
> >  But you advertise dmix like it was silver bullet.
> > 
> 
> Or goes limbo randomly and no mailing to lists seems to result in a
> reply (from the alsa peeps at least) ...
> 

Because no one has ever produced a simple test program with source code
that demonstrates the problem.  You really expect the ALSA developers to
go chasing bugs in closed source apps?

Anyway, do you really need to hear your system sounds and MP3s while
playing Q3?  This is hardly a fatal problem.

Lee

Re: How's the nforce4 support in Linux?

[Martin Schlemmer]

[-- Attachment #1: Type: text/plain, Size: 1148 bytes --]

On Wed, 2005-03-30 at 16:01 -0500, Lee Revell wrote:
> On Wed, 2005-03-30 at 21:19 +0200, Martin Schlemmer wrote:
> > On Wed, 2005-03-30 at 17:00 +0200, Tomasz Torcz wrote:
> > > > >  quake3 still segfaults when run through "aoss". And can't be fixed, as
> > > > > it's closed source still.
> > > > > 
> > > > I guess that's Quake3's problem...
> > > 
> > >  It an glaring example, dmix is unsufficient in one third of my sound
> > > uses (other two beeing movie and music playback)
> > >  But you advertise dmix like it was silver bullet.
> > > 
> > 
> > Or goes limbo randomly and no mailing to lists seems to result in a
> > reply (from the alsa peeps at least) ...
> > 
> 
> Because no one has ever produced a simple test program with source code
> that demonstrates the problem.  You really expect the ALSA developers to
> go chasing bugs in closed source apps?
> 
> Anyway, do you really need to hear your system sounds and MP3s while
> playing Q3?  This is hardly a fatal problem.
> 

It never involved Q3 - what makes you assume this?  I just chipped in
due to your dmix advertising.


-- 
Martin Schlemmer


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: How's the nforce4 support in Linux?

[Lee Revell]

On Fri, 2005-03-25 at 23:59 +0100, Julien Wajsberg wrote:
> I also experiment sometimes a complete hang of the system. But I
> didn't find how to reproduce the bug yet, especially because it seems
> to happen when I do nothing (when I'm sleeping or am at work ;), and I
> can't get a Oops because I don't have any serial console...

You could try netconsole...

Lee

Re: How's the nforce4 support in Linux?

[Julien Wajsberg]

On Fri, 25 Mar 2005 18:20:54 -0500, Lee Revell <rlrevell@joe-job.com> wrote:
> On Fri, 2005-03-25 at 23:59 +0100, Julien Wajsberg wrote:
> > I also experiment sometimes a complete hang of the system. But I
> > didn't find how to reproduce the bug yet, especially because it seems
> > to happen when I do nothing (when I'm sleeping or am at work ;), and I
> > can't get a Oops because I don't have any serial console...
> 
> You could try netconsole...

Good point... I just tried, but forcedeth doesn't support netpoll. If
you have a pointer, I could try to implement it ;-)

-- 
Julien

Re: How's the nforce4 support in Linux?

[Michal Schmidt]

[-- Attachment #1: Type: text/plain, Size: 269 bytes --]

Julien Wajsberg wrote:
> Good point... I just tried, but forcedeth doesn't support netpoll. If
> you have a pointer, I could try to implement it ;-)

Can you try the attached patch for forcedeth?
It compiles for me, but I don't have nForce hardware to test it.

Michal

[-- Attachment #2: forcedeth-netpoll.patch --]
[-- Type: text/plain, Size: 895 bytes --]

--- linux-2.6.12-rc1/drivers/net/forcedeth.c.orig	2005-03-26 15:00:12.000000000 +0100
+++ linux-2.6.12-rc1/drivers/net/forcedeth.c	2005-03-26 15:08:56.000000000 +0100
@@ -1480,6 +1480,13 @@ static void nv_do_nic_poll(unsigned long
 	enable_irq(dev->irq);
 }
 
+#ifdef CONFIG_NET_POLL_CONTROLLER
+static void nv_poll_controller(struct net_device *dev)
+{
+	nv_do_nic_poll((long) dev);
+}
+#endif
+
 static void nv_get_drvinfo(struct net_device *dev, struct ethtool_drvinfo *info)
 {
 	struct fe_priv *np = get_nvpriv(dev);
@@ -1962,6 +1969,9 @@ static int __devinit nv_probe(struct pci
 	dev->get_stats = nv_get_stats;
 	dev->change_mtu = nv_change_mtu;
 	dev->set_multicast_list = nv_set_multicast;
+#ifdef CONFIG_NET_POLL_CONTROLLER
+	dev->poll_controller = nv_poll_controller;
+#endif
 	SET_ETHTOOL_OPS(dev, &ops);
 	dev->tx_timeout = nv_tx_timeout;
 	dev->watchdog_timeo = NV_WATCHDOG_TIMEO;

Re: How's the nforce4 support in Linux?

[Julien Wajsberg]

On Sat, 26 Mar 2005 15:13:47 +0100, Michal Schmidt
<xschmi00@stud.feec.vutbr.cz> wrote:
> Julien Wajsberg wrote:
> > Good point... I just tried, but forcedeth doesn't support netpoll. If
> > you have a pointer, I could try to implement it ;-)
> 
> Can you try the attached patch for forcedeth?
> It compiles for me, but I don't have nForce hardware to test it.

Okay, it works :)
maybe I'll have something for you to debug at the next crash...

-- 
Julien


> --- linux-2.6.12-rc1/drivers/net/forcedeth.c.orig       2005-03-26 15:00:12.000000000 +0100
> +++ linux-2.6.12-rc1/drivers/net/forcedeth.c    2005-03-26 15:08:56.000000000 +0100
> @@ -1480,6 +1480,13 @@ static void nv_do_nic_poll(unsigned long
>         enable_irq(dev->irq);
>  }
> 
> +#ifdef CONFIG_NET_POLL_CONTROLLER
> +static void nv_poll_controller(struct net_device *dev)
> +{
> +       nv_do_nic_poll((long) dev);
> +}
> +#endif
> +
>  static void nv_get_drvinfo(struct net_device *dev, struct ethtool_drvinfo *info)
>  {
>         struct fe_priv *np = get_nvpriv(dev);
> @@ -1962,6 +1969,9 @@ static int __devinit nv_probe(struct pci
>         dev->get_stats = nv_get_stats;
>         dev->change_mtu = nv_change_mtu;
>         dev->set_multicast_list = nv_set_multicast;
> +#ifdef CONFIG_NET_POLL_CONTROLLER
> +       dev->poll_controller = nv_poll_controller;
> +#endif
>         SET_ETHTOOL_OPS(dev, &ops);
>         dev->tx_timeout = nv_tx_timeout;
>         dev->watchdog_timeo = NV_WATCHDOG_TIMEO;
> 
> 
>

Re: How's the nforce4 support in Linux?

[Lee Revell]

On Fri, 2005-03-25 at 23:59 +0100, Julien Wajsberg wrote:
> Mar 25 22:42:55 evenflow kernel: hda: dma_timer_expiry: dma status == 0x60
> Mar 25 22:42:55 evenflow kernel: hda: DMA timeout retry
> Mar 25 22:42:55 evenflow kernel: hda: timeout waiting for DMA
> Mar 25 22:42:55 evenflow kernel: hda: status error: status=0x58 {
> DriveReady SeekComplete DataRequest }
> Mar 25 22:42:55 evenflow kernel: 
> Mar 25 22:42:55 evenflow kernel: ide: failed opcode was: unknown
> Mar 25 22:42:55 evenflow kernel: hda: drive not ready for command
> Mar 25 22:42:55 evenflow kernel: hda: status timeout: status=0xd0 { Busy }
> Mar 25 22:42:55 evenflow kernel: 
> Mar 25 22:42:55 evenflow kernel: ide: failed opcode was: unknown
> Mar 25 22:42:55 evenflow kernel: hdb: DMA disabled
> Mar 25 22:42:55 evenflow kernel: hda: drive not ready for command

Are you sure the drive is OK?  Those messages are the classic signs of a
failing drive...

Lee

Re: How's the nforce4 support in Linux?

[Julien Wajsberg]

On Fri, 25 Mar 2005 18:21:42 -0500, Lee Revell <rlrevell@joe-job.com> wrote:
> On Fri, 2005-03-25 at 23:59 +0100, Julien Wajsberg wrote:
> > Mar 25 22:42:55 evenflow kernel: hda: dma_timer_expiry: dma status == 0x60
> > Mar 25 22:42:55 evenflow kernel: hda: DMA timeout retry
> > Mar 25 22:42:55 evenflow kernel: hda: timeout waiting for DMA
> > Mar 25 22:42:55 evenflow kernel: hda: status error: status=0x58 {
> > DriveReady SeekComplete DataRequest }
> > Mar 25 22:42:55 evenflow kernel:
> > Mar 25 22:42:55 evenflow kernel: ide: failed opcode was: unknown
> > Mar 25 22:42:55 evenflow kernel: hda: drive not ready for command
> > Mar 25 22:42:55 evenflow kernel: hda: status timeout: status=0xd0 { Busy }
> > Mar 25 22:42:55 evenflow kernel:
> > Mar 25 22:42:55 evenflow kernel: ide: failed opcode was: unknown
> > Mar 25 22:42:55 evenflow kernel: hdb: DMA disabled
> > Mar 25 22:42:55 evenflow kernel: hda: drive not ready for command
> 
> Are you sure the drive is OK?  Those messages are the classic signs of a
> failing drive...

It's nearly new, and it was ok in my last computer (an old P3-500 with
PIIX4, IIRC).
BTW I did a complete badblocks check on it, and it found nothing.

-- 
Julien

Re: How's the nforce4 support in Linux?

[Julien Wajsberg]

On Mar 26, 2005 12:59 AM, Julien Wajsberg <julien.wajsberg@gmail.com> wrote:
> I own an Asus A8N-Sli motherboard with the Nforce4-Sli chipset, and I
> experiment the following problem :
> 
> Mar 25 22:42:55 evenflow kernel: hda: dma_timer_expiry: dma status == 0x60
> Mar 25 22:42:55 evenflow kernel: hda: DMA timeout retry
> Mar 25 22:42:55 evenflow kernel: hda: timeout waiting for DMA
> Mar 25 22:42:55 evenflow kernel: hda: status error: status=0x58 {
> DriveReady SeekComplete DataRequest }
> Mar 25 22:42:55 evenflow kernel:
> Mar 25 22:42:55 evenflow kernel: ide: failed opcode was: unknown
> Mar 25 22:42:55 evenflow kernel: hda: drive not ready for command
> Mar 25 22:42:55 evenflow kernel: hda: status timeout: status=0xd0 { Busy }
> Mar 25 22:42:55 evenflow kernel:
> Mar 25 22:42:55 evenflow kernel: ide: failed opcode was: unknown
> Mar 25 22:42:55 evenflow kernel: hdb: DMA disabled
> Mar 25 22:42:55 evenflow kernel: hda: drive not ready for command
> 
> Of course, if I disable DMA with hdparm, this problem disappear.. but
> it isn't a long-term solution ;-)
> 
> Using vanilla 2.6.11.5 kernel. I attached the config file.

I tried the multidma mode (as opposed to ultradma), and the system
hanged immediately. (Thanks to the patched-for-netpoll forcedeth
driver), I got the following message:

Unknown interrupt or fault at EIP 00000206 00000060 c0247a3a

There's definitely something wrong here...
I'm still using the same setup as in my first mail.

-- 
Julien

Re: How's the nforce4 support in Linux?

[Richard B. Johnson]

On Tue, 5 Apr 2005, Julien Wajsberg wrote:

> On Mar 26, 2005 12:59 AM, Julien Wajsberg <julien.wajsberg@gmail.com> wrote:
>> I own an Asus A8N-Sli motherboard with the Nforce4-Sli chipset, and I
>> experiment the following problem :
>>
>> Mar 25 22:42:55 evenflow kernel: hda: dma_timer_expiry: dma status == 0x60
>> Mar 25 22:42:55 evenflow kernel: hda: DMA timeout retry
>> Mar 25 22:42:55 evenflow kernel: hda: timeout waiting for DMA
>> Mar 25 22:42:55 evenflow kernel: hda: status error: status=0x58 {
>> DriveReady SeekComplete DataRequest }
>> Mar 25 22:42:55 evenflow kernel:
>> Mar 25 22:42:55 evenflow kernel: ide: failed opcode was: unknown
>> Mar 25 22:42:55 evenflow kernel: hda: drive not ready for command
>> Mar 25 22:42:55 evenflow kernel: hda: status timeout: status=0xd0 { Busy }
>> Mar 25 22:42:55 evenflow kernel:
>> Mar 25 22:42:55 evenflow kernel: ide: failed opcode was: unknown
>> Mar 25 22:42:55 evenflow kernel: hdb: DMA disabled
                                      ^^^^^^^^^^^^^^^^^
>> Mar 25 22:42:55 evenflow kernel: hda: drive not ready for command
>>
>> Of course, if I disable DMA with hdparm, this problem disappear.. but
>> it isn't a long-term solution ;-)
>>

The long-term solution is to replace either the drive, cable, or the
motherboard that can't do DMA. A bad DMA operation can write data
anywhere (right into the middle of the kernel). There isn't
anything software can do about it. Software sets up the
controller for a DMA operation, then waits for an interrupt
that tells it has completed or failed. Software can retry failed
operations until software gets destroyed by the hardware, but
there isn't anything else that can be done.

The fact that disabling DMA makes the problem(s) go away is
proof that it isn't a software problem. There are flash-RAM
devices that emulate IDE drives. Most of these can't do DMA
and the IDE driver doesn't accept that fact. That is a known
bug. One needs to use hdparm to tell it to stop trying to
use DMA. In your case, the driver stopped using DMA when
it found out that it didn't work. There is no bug.

Cheers,
Dick Johnson
Penguin : Linux version 2.6.11 on an i686 machine (5537.79 BogoMips).
  Notice : All mail here is now cached for review by Dictator Bush.
                  98.36% of all statistics are fiction.

Re: How's the nforce4 support in Linux?

[Julien Wajsberg]

On Apr 5, 2005 4:10 PM, Richard B. Johnson <linux-os@analogic.com> wrote:
> On Tue, 5 Apr 2005, Julien Wajsberg wrote:
> 
> > On Mar 26, 2005 12:59 AM, Julien Wajsberg <julien.wajsberg@gmail.com> wrote:
> >> I own an Asus A8N-Sli motherboard with the Nforce4-Sli chipset, and I
> >> experiment the following problem :
> >>
> >> Mar 25 22:42:55 evenflow kernel: hda: dma_timer_expiry: dma status == 0x60
> >> Mar 25 22:42:55 evenflow kernel: hda: DMA timeout retry
> >> Mar 25 22:42:55 evenflow kernel: hda: timeout waiting for DMA
> >> Mar 25 22:42:55 evenflow kernel: hda: status error: status=0x58 {
> >> DriveReady SeekComplete DataRequest }
> >> Mar 25 22:42:55 evenflow kernel:
> >> Mar 25 22:42:55 evenflow kernel: ide: failed opcode was: unknown
> >> Mar 25 22:42:55 evenflow kernel: hda: drive not ready for command
> >> Mar 25 22:42:55 evenflow kernel: hda: status timeout: status=0xd0 { Busy }
> >> Mar 25 22:42:55 evenflow kernel:
> >> Mar 25 22:42:55 evenflow kernel: ide: failed opcode was: unknown
> >> Mar 25 22:42:55 evenflow kernel: hdb: DMA disabled
>                                       ^^^^^^^^^^^^^^^^^
> >> Mar 25 22:42:55 evenflow kernel: hda: drive not ready for command
> >>
> >> Of course, if I disable DMA with hdparm, this problem disappear.. but
> >> it isn't a long-term solution ;-)
> >>
> 
> The long-term solution is to replace either the drive, cable, or the
> motherboard that can't do DMA.
It's a recent drive that did ultra DMA on another motherboard, and a
recent motherboard with a cable that did ultra DMA before.It was ultra
DMA2 on this old motherboard, but it still was ultra DMA.

> A bad DMA operation can write data
> anywhere (right into the middle of the kernel). There isn't
> anything software can do about it. Software sets up the
> controller for a DMA operation, then waits for an interrupt
> that tells it has completed or failed. Software can retry failed
> operations until software gets destroyed by the hardware, but
> there isn't anything else that can be done.
> 
> The fact that disabling DMA makes the problem(s) go away is
> proof that it isn't a software problem. There are flash-RAM
> devices that emulate IDE drives. Most of these can't do DMA
> and the IDE driver doesn't accept that fact. That is a known
> bug. One needs to use hdparm to tell it to stop trying to
> use DMA. In your case, the driver stopped using DMA when
> it found out that it didn't work. There is no bug.

In my case, the driver stopped for hdb, that is my dvd-burner/player.
It did nothing for hda or hdc, I had to disable DMA myself.


Will I have to install Windows XP to prove ultra DMA works correctly
on this setup ? I really don't hope...

-- 
Julien

Re: How's the nforce4 support in Linux?

[Richard B. Johnson]

On Tue, 5 Apr 2005, Julien Wajsberg wrote:

> On Apr 5, 2005 4:10 PM, Richard B. Johnson <linux-os@analogic.com> wrote:
>> On Tue, 5 Apr 2005, Julien Wajsberg wrote:
>>
>>> On Mar 26, 2005 12:59 AM, Julien Wajsberg <julien.wajsberg@gmail.com> wrote:
>>>> I own an Asus A8N-Sli motherboard with the Nforce4-Sli chipset, and I
>>>> experiment the following problem :
>>>>
>>>> Mar 25 22:42:55 evenflow kernel: hda: dma_timer_expiry: dma status == 0x60
>>>> Mar 25 22:42:55 evenflow kernel: hda: DMA timeout retry
>>>> Mar 25 22:42:55 evenflow kernel: hda: timeout waiting for DMA
>>>> Mar 25 22:42:55 evenflow kernel: hda: status error: status=0x58 {
>>>> DriveReady SeekComplete DataRequest }
>>>> Mar 25 22:42:55 evenflow kernel:
>>>> Mar 25 22:42:55 evenflow kernel: ide: failed opcode was: unknown
>>>> Mar 25 22:42:55 evenflow kernel: hda: drive not ready for command
>>>> Mar 25 22:42:55 evenflow kernel: hda: status timeout: status=0xd0 { Busy }
>>>> Mar 25 22:42:55 evenflow kernel:
>>>> Mar 25 22:42:55 evenflow kernel: ide: failed opcode was: unknown
>>>> Mar 25 22:42:55 evenflow kernel: hdb: DMA disabled
>>                                       ^^^^^^^^^^^^^^^^^
>>>> Mar 25 22:42:55 evenflow kernel: hda: drive not ready for command
>>>>
>>>> Of course, if I disable DMA with hdparm, this problem disappear.. but
>>>> it isn't a long-term solution ;-)
>>>>
>>
>> The long-term solution is to replace either the drive, cable, or the
>> motherboard that can't do DMA.
> It's a recent drive that did ultra DMA on another motherboard, and a
> recent motherboard with a cable that did ultra DMA before.It was ultra
> DMA2 on this old motherboard, but it still was ultra DMA.
>
>> A bad DMA operation can write data
>> anywhere (right into the middle of the kernel). There isn't
>> anything software can do about it. Software sets up the
>> controller for a DMA operation, then waits for an interrupt
>> that tells it has completed or failed. Software can retry failed
>> operations until software gets destroyed by the hardware, but
>> there isn't anything else that can be done.
>>
>> The fact that disabling DMA makes the problem(s) go away is
>> proof that it isn't a software problem. There are flash-RAM
>> devices that emulate IDE drives. Most of these can't do DMA
>> and the IDE driver doesn't accept that fact. That is a known
>> bug. One needs to use hdparm to tell it to stop trying to
>> use DMA. In your case, the driver stopped using DMA when
>> it found out that it didn't work. There is no bug.
>
> In my case, the driver stopped for hdb, that is my dvd-burner/player.
> It did nothing for hda or hdc, I had to disable DMA myself.
>
> Will I have to install Windows XP to prove ultra DMA works correctly
> on this setup ? I really don't hope...

How would you know?  Windows will just run it as PIOW and be done
with it. Did you ever try to copy a large file in XP? Try it.
Try the same thing in linux on the same hardware. You don't need
a stop-watch. On Win-XP, a 10 megabyte file (hardly large) takes
about 10 seconds. That's 1 megabyte/second. Linux tries to be
a bit faster.

>
> -- 
> Julien
>

Cheers,
Dick Johnson
Penguin : Linux version 2.6.11 on an i686 machine (5537.79 BogoMips).
  Notice : All mail here is now cached for review by Dictator Bush.
                  98.36% of all statistics are fiction.

Re: How's the nforce4 support in Linux?

[Bartlomiej Zolnierkiewicz]

On Apr 6, 2005 1:41 PM, Richard B. Johnson <linux-os@analogic.com> wrote:
> On Tue, 5 Apr 2005, Julien Wajsberg wrote:
> 
> > On Apr 5, 2005 4:10 PM, Richard B. Johnson <linux-os@analogic.com> wrote:
> >> On Tue, 5 Apr 2005, Julien Wajsberg wrote:
> >>
> >>> On Mar 26, 2005 12:59 AM, Julien Wajsberg <julien.wajsberg@gmail.com> wrote:
> >>>> I own an Asus A8N-Sli motherboard with the Nforce4-Sli chipset, and I
> >>>> experiment the following problem :
> >>>>
> >>>> Mar 25 22:42:55 evenflow kernel: hda: dma_timer_expiry: dma status == 0x60
> >>>> Mar 25 22:42:55 evenflow kernel: hda: DMA timeout retry
> >>>> Mar 25 22:42:55 evenflow kernel: hda: timeout waiting for DMA
> >>>> Mar 25 22:42:55 evenflow kernel: hda: status error: status=0x58 {
> >>>> DriveReady SeekComplete DataRequest }
> >>>> Mar 25 22:42:55 evenflow kernel:
> >>>> Mar 25 22:42:55 evenflow kernel: ide: failed opcode was: unknown
> >>>> Mar 25 22:42:55 evenflow kernel: hda: drive not ready for command
> >>>> Mar 25 22:42:55 evenflow kernel: hda: status timeout: status=0xd0 { Busy }
> >>>> Mar 25 22:42:55 evenflow kernel:
> >>>> Mar 25 22:42:55 evenflow kernel: ide: failed opcode was: unknown
> >>>> Mar 25 22:42:55 evenflow kernel: hdb: DMA disabled
> >>                                       ^^^^^^^^^^^^^^^^^
> >>>> Mar 25 22:42:55 evenflow kernel: hda: drive not ready for command
> >>>>
> >>>> Of course, if I disable DMA with hdparm, this problem disappear.. but
> >>>> it isn't a long-term solution ;-)
> >>>>
> >>
> >> The long-term solution is to replace either the drive, cable, or the
> >> motherboard that can't do DMA.
> > It's a recent drive that did ultra DMA on another motherboard, and a
> > recent motherboard with a cable that did ultra DMA before.It was ultra
> > DMA2 on this old motherboard, but it still was ultra DMA.
> >
> >> A bad DMA operation can write data
> >> anywhere (right into the middle of the kernel). There isn't
> >> anything software can do about it. Software sets up the
> >> controller for a DMA operation, then waits for an interrupt
> >> that tells it has completed or failed. Software can retry failed
> >> operations until software gets destroyed by the hardware, but
> >> there isn't anything else that can be done.
> >>
> >> The fact that disabling DMA makes the problem(s) go away is
> >> proof that it isn't a software problem. There are flash-RAM
> >> devices that emulate IDE drives. Most of these can't do DMA
> >> and the IDE driver doesn't accept that fact. That is a known
> >> bug. One needs to use hdparm to tell it to stop trying to
> >> use DMA. In your case, the driver stopped using DMA when
> >> it found out that it didn't work. There is no bug.

There still can be a bug in setting up DMA timings etc.

It is hard to even guess as you haven't given any details about your
system: dmesg/hdparm/lspci/config... (or I overlooked it somehow).

> > In my case, the driver stopped for hdb, that is my dvd-burner/player.
> > It did nothing for hda or hdc, I had to disable DMA myself.
> >
> > Will I have to install Windows XP to prove ultra DMA works correctly
> > on this setup ? I really don't hope...

That would be very helpful.

Another useful thing would be to try non-nVidia motherboard
(if you have one handy) without changing anything else.

Bartlomiej

Re: How's the nforce4 support in Linux?

[Julien Wajsberg]

On Apr 6, 2005 6:02 PM, Bartlomiej Zolnierkiewicz <bzolnier@gmail.com> wrote:
> 
> There still can be a bug in setting up DMA timings etc.
> 
> It is hard to even guess as you haven't given any details about your
> system: dmesg/hdparm/lspci/config... (or I overlooked it somehow).

I sent the related dmesg lines, and my .config.
for dmesg and .config :
http://marc.theaimsgroup.com/?l=linux-kernel&m=111179215521092&w=2

what part of lspci would you need ?

hdparm :

flash@evenflow:~$ sudo hdparm -i /dev/hda

/dev/hda:

 Model=Maxtor 6Y160P0, FwRev=YAR41BW0, SerialNo=Y47J8CRE
 Config={ Fixed }
 RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=57
 BuffType=DualPortCache, BuffSize=7936kB, MaxMultSect=16, MultSect=off
 CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=268435455
 IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
 PIO modes:  pio0 pio1 pio2 pio3 pio4 
 DMA modes:  mdma0 mdma1 mdma2 
 UDMA modes: udma0 udma1 udma2 
 AdvancedPM=yes: disabled (255) WriteCache=enabled
 Drive conforms to: (null): 

 * signifies the current active mode

(it shows no mode... it's strange, because this drive should be nearly
the same as the following)

flash@evenflow:~$ sudo hdparm -i /dev/hdc

/dev/hdc:

 Model=Maxtor 6Y120L0, FwRev=YAR41BW0, SerialNo=Y31LWCXE
 Config={ Fixed }
 RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=57
 BuffType=DualPortCache, BuffSize=2048kB, MaxMultSect=16, MultSect=off
 CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=240121728
 IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
 PIO modes:  pio0 pio1 pio2 pio3 pio4 
 DMA modes:  mdma0 mdma1 mdma2 
 UDMA modes: udma0 udma1 udma2 udma3 udma4 udma5 *udma6 
 AdvancedPM=yes: disabled (255) WriteCache=enabled
 Drive conforms to: (null): 

 * signifies the current active mode

flash@evenflow:~$ sudo hdparm -d /dev/hdc

/dev/hdc:
 using_dma    =  0 (off)

(Note : hdparm -i says 'udma6', and hdparm -d says 'no dma'...
Strange, isn't it ?)

> > > In my case, the driver stopped for hdb, that is my dvd-burner/player.
> > > It did nothing for hda or hdc, I had to disable DMA myself.
> > >
> > > Will I have to install Windows XP to prove ultra DMA works correctly
> > > on this setup ? I really don't hope...
> 
> That would be very helpful.

I'll try that...

> Another useful thing would be to try non-nVidia motherboard
> (if you have one handy) without changing anything else.

I succesfully used these drives with another motherboard (PIIX4)
before, in udma2 mode, for years...

But first thing : I have to check if the cables are correctly plugged
in (I mean in the correct order)... I didn't have the time to do that
yet.

Thanks for your answer.
-- 
Julien

Re: How's the nforce4 support in Linux?

[Julien Wajsberg]

On Apr 6, 2005 1:41 PM, Richard B. Johnson <linux-os@analogic.com> wrote:
>
> How would you know?  Windows will just run it as PIOW and be done
> with it.
Yes, but there's a way to know which mode you're using (maybe not
precisely, but at least PIO vs DMA).

> Did you ever try to copy a large file in XP? Try it.
> Try the same thing in linux on the same hardware. You don't need
> a stop-watch. On Win-XP, a 10 megabyte file (hardly large) takes
> about 10 seconds. That's 1 megabyte/second. Linux tries to be
> a bit faster.

Usually, I only have Linux on any hardware I have ;) And there is no
point comparing these things here...

--
Julien

PS: Sorry Richard, I forgot my "reply to all" button...

Re: How's the nforce4 support in Linux?

[Chuck]

On Fri, 2005-03-25 at 23:59 +0100, Julien Wajsberg wrote:
> Mar 25 22:42:55 evenflow kernel: hda: dma_timer_expiry: dma status == 0x60
> Mar 25 22:42:55 evenflow kernel: hda: DMA timeout retry
> Mar 25 22:42:55 evenflow kernel: hda: timeout waiting for DMA
> Mar 25 22:42:55 evenflow kernel: hda: status error: status=0x58 {
> DriveReady SeekComplete DataRequest }
> Mar 25 22:42:55 evenflow kernel:
> Mar 25 22:42:55 evenflow kernel: ide: failed opcode was: unknown
> Mar 25 22:42:55 evenflow kernel: hda: drive not ready for command
> Mar 25 22:42:55 evenflow kernel: hda: status timeout: status=0xd0 { Busy }
> Mar 25 22:42:55 evenflow kernel:
> Mar 25 22:42:55 evenflow kernel: ide: failed opcode was: unknown
> Mar 25 22:42:55 evenflow kernel: hdb: DMA disabled
> Mar 25 22:42:55 evenflow kernel: hda: drive not ready for command

(something) like the same problem here:  

I get lots of:

hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown


The disk (WDC WD800JB) is about 1/2 year old. 
I've checked the drive in my old system... nothing!
Also WD's diagnostic kit doesn't report any problems like bad sectors,
or other troubles...  

(Please CC me, I'm not on the list)

Re: How's the nforce4 support in Linux?

[Arjan van de Ven]

`
> hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> hda: dma_intr: error=0x84 { DriveStatusError BadCRC 

BadCRC is 99% sure a cabling issue; either a bad/overheated cable or a
cable used at too high a speed for the cable.

Re: How's the nforce4 support in Linux?

[Marcin Dalecki]

On 2005-03-26, at 16:19, Arjan van de Ven wrote:

> `
>> hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
>> hda: dma_intr: error=0x84 { DriveStatusError BadCRC
>
> BadCRC is 99% sure a cabling issue; either a bad/overheated cable or a
> cable used at too high a speed for the cable.

No. It is more likely that the timing programming between the disk and 
host controller
are in a miss-match state. UDMA mode detection can come in to mind too.
It makes sense to experiment with hdparm to see if the problem goes 
away in non
Ultra DMA modes.

Re: How's the nforce4 support in Linux?

[Chuck]

On Saturday, 26. March 2005 18:32, Marcin Dalecki wrote:
> On 2005-03-26, at 16:19, Arjan van de Ven wrote:
> > `
> >
> >> hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> >> hda: dma_intr: error=0x84 { DriveStatusError BadCRC
> >
> > BadCRC is 99% sure a cabling issue; either a bad/overheated cable or a
> > cable used at too high a speed for the cable.
>
> No. It is more likely that the timing programming between the disk and
> host controller
> are in a miss-match state. UDMA mode detection can come in to mind too.
> It makes sense to experiment with hdparm to see if the problem goes
> away in non
> Ultra DMA modes.

Thanks, I tried the cable that came with the drive  (it was still sealed) and 
experimented a little bit with hdparm...
Now, the problem seems to be gone...  

Re: How's the nforce4 support in Linux?

[Julien Wajsberg]

On Mar 26, 2005 7:32 PM, Marcin Dalecki <martin@dalecki.de> wrote:
> 
> On 2005-03-26, at 16:19, Arjan van de Ven wrote:
> 
> > `
> >> hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> >> hda: dma_intr: error=0x84 { DriveStatusError BadCRC
> >
> > BadCRC is 99% sure a cabling issue; either a bad/overheated cable or a
> > cable used at too high a speed for the cable.
> 
> No. It is more likely that the timing programming between the disk and
> host controller
> are in a miss-match state. UDMA mode detection can come in to mind too.
> It makes sense to experiment with hdparm to see if the problem goes
> away in non
> Ultra DMA modes.

Do you mean "multiword dma modes" or "pio modes" ?

-- 
Julien

Re: How's the nforce4 support in Linux?

[Chuck Ebbert]

On Thu, 24 Mar 2005 at 10:34:12 +0100, Arjan van de Ven wrote:

> probably just one of those things implemented in the binary drivers in
> software, just like the "hardware" IDE raid is most of the time (3ware
> being the positive exception there)

 IT8212 is a real hardware ATA RAID controller.  Too bad it will never get
merged from -ac into mainline with the HW RAID support intact...

--
Chuck
http://www.counterfeitmini.org

Re: How's the nforce4 support in Linux?

[Asfand Yar Qazi]

Arjan van de Ven wrote:
>>* "hardware firewall" -- sounds silly.  Pretty sure Linux doesn't support
>>it in any case.
>>
> 
> 
> probably just one of those things implemented in the binary drivers in
> software, just like the "hardware" IDE raid is most of the time (3ware
> being the positive exception there)
> 

http://www.neoseeker.com/Articles/Hardware/Previews/nvnforce4/3.html

You're right there - some semi-hardware support combined with drivers 
apparently result in lower CPU usage that software firewalls.  Apparently.

Actually, these people like it:
http://www.bjorn3d.com/read.php?cID=712&pageID=1096

However one feature that you can't laugh at is the fact that it can be 
made to block packets in the span of time between the OS being loaded 
up, and the "real" firewall coming up.  This small time span 
theoretically leaves the PC vulnerable, so I think this is the only 
use for "ActiveAmor Firewall".

However, this doesn't answer my original question (which I suppose I 
should have made clearer): can I get SATA II NCQ support in Linux with 
an nForce 4 chipset?

Re: How's the nforce4 support in Linux?

[Arjan van de Ven]

On Thu, 2005-03-24 at 10:00 +0000, Asfand Yar Qazi wrote:
> Arjan van de Ven wrote:
> >>* "hardware firewall" -- sounds silly.  Pretty sure Linux doesn't support
> >>it in any case.
> >>
> > 
> > 
> > probably just one of those things implemented in the binary drivers in
> > software, just like the "hardware" IDE raid is most of the time (3ware
> > being the positive exception there)
> > 
> 
> http://www.neoseeker.com/Articles/Hardware/Previews/nvnforce4/3.html
> 
> You're right there - some semi-hardware support combined with drivers 
> apparently result in lower CPU usage that software firewalls.  Apparently.

lower CPU usage than the *windows* firewall.
While there is a potential gain from a firewall function on the other
side of the PCI bus, this gain is when you reject most packets. Eg you
save "bad" packets from going over the bus. Now the question is how many
bad packets do you get per second...

> However one feature that you can't laugh at is the fact that it can be 
> made to block packets in the span of time between the OS being loaded 
> up, and the "real" firewall coming up.  This small time span 
> theoretically leaves the PC vulnerable, so I think this is the only 
> use for "ActiveAmor Firewall".

This is a joke right? In linux at least, the OS doesn't get packets
unless it asks for it; I can't imagine any other OS doing that
differently (since most are somewhat based on the same model). And all
linux distros I know of first install the firewall rules and then tell
the NIC to start receiving packets. In that order. I don't know how
windows does it (and I don't care), but if it gets this wrong it would
be a really bad bug in windows. But I guess it'd give the chipset
marketing people something to boast about ;)

Re: How's the nforce4 support in Linux?

[Lennart Sorensen]

On Thu, Mar 24, 2005 at 10:00:46AM +0000, Asfand Yar Qazi wrote:
> http://www.neoseeker.com/Articles/Hardware/Previews/nvnforce4/3.html
> 
> You're right there - some semi-hardware support combined with drivers 
> apparently result in lower CPU usage that software firewalls.  Apparently.
> 
> Actually, these people like it:
> http://www.bjorn3d.com/read.php?cID=712&pageID=1096
> 
> However one feature that you can't laugh at is the fact that it can be 
> made to block packets in the span of time between the OS being loaded 
> up, and the "real" firewall coming up.  This small time span 
> theoretically leaves the PC vulnerable, so I think this is the only 
> use for "ActiveAmor Firewall".

Until the OS loads network drivers AND configures IP support AND starts
accepting packets in, there is nothing for the firewall to do.
Certainly on Linux I can make sure iptables is populated (or least has a
sane policy set) before I bring up networking.  In other words: "Who
cares".

> However, this doesn't answer my original question (which I suppose I 
> should have made clearer): can I get SATA II NCQ support in Linux with 
> an nForce 4 chipset?

Don't know.  I think 3ware's controllers do their own NCQ, which is
pretty neat.

Len Sorensen

Re: How's the nforce4 support in Linux?

[Raphael Jacquot]

Lennart Sorensen wrote:

> Until the OS loads network drivers AND configures IP support AND starts
> accepting packets in, there is nothing for the firewall to do.
> Certainly on Linux I can make sure iptables is populated (or least has a
> sane policy set) before I bring up networking.  In other words: "Who
> cares".

guess that's a windows thing...

Re: How's the nforce4 support in Linux?

[Jeff Garzik]

Asfand Yar Qazi wrote:
> However, this doesn't answer my original question (which I suppose I 
> should have made clearer): can I get SATA II NCQ support in Linux with 
> an nForce 4 chipset?

I answered this question already.  The answer is no.

	Jeff

Re: How's the nforce4 support in Linux?

[Robert Hancock]

Asfand Yar Qazi wrote:
> NForce4 Ultra is brilliant - in many ways.  Except it requires binary 
> drivers, which I really don't want to use.  And apparently, the hardware 
> firewall seems to restrict bandwidth a bit.  And even when its off, 
> external chips that end up being faster (http://tinyurl.com/4zssp)
> 
> So, I'm wondering, are my assumptions correct?  Do I have to use binary 
> drivers to make absolutely full use of the Nforce4 chipset?  Or is there 
> sufficient support for me to make use of the features on it without 
> using binary drivers?
> 
> Sorry for asking something that may have been asked before, but I've 
> tried searching several times through the mailing list and on a search 
> engine, but have had little luck.
> 
> Thanks,
>     Asfand Yar

There is no need to use any binary drivers on the nForce4 - the only 
ones even available are for the network and audio. The network works 
fine with the forcedeth driver included in the kernel - I don't know 
about the audio, I'm not using the onboard sound.

Some wrinkles with Linux support are that you may need to update the X 
server (ex: X.org) as there are some bugs with PCI Express video on 
x86_64 that were fixed somewhat recently - as well there was a bug with 
USB port detection that cropped up in kernel 2.6.10 and I believe is 
fixed in 2.6.11.

The nForce4 chipset supports NCQ on the SATA interface, however this is 
not supported in Linux yet. It seems like the SATA controller has some 
similarity or is based on the ADMA architecture (the Windows driver is 
called "NVIDIA nForce4 ADMA Controller", so using it with the ADMA 
driver might be doable at some point, though I haven't heard of any 
hardware specs being released..

-- 
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/

Re: How's the nforce4 support in Linux?

[Lee Revell]

On Thu, 2005-03-24 at 20:15 -0600, Robert Hancock wrote:
> There is no need to use any binary drivers on the nForce4 - the only 
> ones even available are for the network and audio. The network works 
> fine with the forcedeth driver included in the kernel - I don't know 
> about the audio, I'm not using the onboard sound.

Your statement is self contradictory.  How can you say there's no need
to use binary drivers if you don't know anything about the audio
support?  Many users consider sound a critical feature.

As a matter of fact there are a few quirks with the audio on Nvidia
chipsets, due to (surprise) lack of documentation.

Lee

Re: How's the nforce4 support in Linux?

[Asfand Yar Qazi]

Asfand Yar Qazi wrote:
> Arjan van de Ven wrote:
> 
>>> * "hardware firewall" -- sounds silly.  Pretty sure Linux doesn't 
>>> support
>>> it in any case.
>>>
>>
>>
>> probably just one of those things implemented in the binary drivers in
>> software, just like the "hardware" IDE raid is most of the time (3ware
>> being the positive exception there)
>>
> 
> http://www.neoseeker.com/Articles/Hardware/Previews/nvnforce4/3.html
> 
> You're right there - some semi-hardware support combined with drivers 
> apparently result in lower CPU usage that software firewalls.  Apparently.
> 
> Actually, these people like it:
> http://www.bjorn3d.com/read.php?cID=712&pageID=1096
> 
> However one feature that you can't laugh at is the fact that it can be 
> made to block packets in the span of time between the OS being loaded 
> up, and the "real" firewall coming up.  This small time span 
> theoretically leaves the PC vulnerable, so I think this is the only use 
> for "ActiveAmor Firewall".
> 
> However, this doesn't answer my original question (which I suppose I 
> should have made clearer): can I get SATA II NCQ support in Linux with 
> an nForce 4 chipset?
> 
> 

Argh already been answered.  Another question: which add-in SATA RAID 
boards (preferably in PCI Express flavour) support NCQ fully and will 
be fully supported in Linux?

How's the nforce4 support in Linux?

[Asfand Yar Qazi]

Hi,

I'm currently contemplating going for an Athlon 64 system.  However, 
I'll primarily be using a Linux-based OS (Gentoo, namely), so I need 
to know how well the chipsets are supported currently.

I'd really like to go Via - but the crummy KT890 / VT8237 combo sucks 
- mainly due to the lack of SATA II with NCQ.  I share the sentiments 
of the person in a post in the AnandTech forums 
(http://tinyurl.com/6d9bx) who says:

"The feature set on the K8T890 sucks. It was supposed to use the 
VT8251 southbridge, bringing SATA-II/NCQ, HD Audio, etc. 
Unfortunately, this southbridge has since dissappeared off the face of 
the earth, and all the current K8T890 boards use the old VT8237. 
nForce4, on the other hand, has SATA-II/NCQ, hardware firewall, nice 
software overclocking/monitoring tools (ntune), gigabit lan, etc. On 
top of that, performance and overclocking is pretty damn good. I was 
at one point looking forward to the K8T890, but considering how much 
of a joke the whole product line has been (lacking features, months of 
delays with no explanation, lack of any variety of retail boards), I 
have to say I'd avoid it like the plague."

NForce4 Ultra is brilliant - in many ways.  Except it requires binary 
drivers, which I really don't want to use.  And apparently, the 
hardware firewall seems to restrict bandwidth a bit.  And even when 
its off, external chips that end up being faster 
(http://tinyurl.com/4zssp)

So, I'm wondering, are my assumptions correct?  Do I have to use 
binary drivers to make absolutely full use of the Nforce4 chipset?  Or 
is there sufficient support for me to make use of the features on it 
without using binary drivers?

Sorry for asking something that may have been asked before, but I've 
tried searching several times through the mailing list and on a search 
engine, but have had little luck.

Thanks,
	Asfand Yar

p.s. Here's something for the search engines to latch on to, so this 
post and any repies are easier to find: via nvidia nforce4 nforce 4 
kt890 kt 890 vt8237 comparison feature set supported compatibility 
binary drivers

Re: How's the nforce4 support in Linux?

[Jeff Garzik]

On Thu, Mar 24, 2005 at 09:20:29AM +0000, Asfand Yar Qazi wrote:
> Hi,
> 
> I'm currently contemplating going for an Athlon 64 system.  However, 
> I'll primarily be using a Linux-based OS (Gentoo, namely), so I need 
> to know how well the chipsets are supported currently.
> 
> I'd really like to go Via - but the crummy KT890 / VT8237 combo sucks 
> - mainly due to the lack of SATA II with NCQ.  I share the sentiments 
> of the person in a post in the AnandTech forums 
> (http://tinyurl.com/6d9bx) who says:
> 
> "The feature set on the K8T890 sucks. It was supposed to use the 
> VT8251 southbridge, bringing SATA-II/NCQ, HD Audio, etc. 
> Unfortunately, this southbridge has since dissappeared off the face of 
> the earth, and all the current K8T890 boards use the old VT8237. 
> nForce4, on the other hand, has SATA-II/NCQ, hardware firewall, nice 
> software overclocking/monitoring tools (ntune), gigabit lan, etc. On 
> top of that, performance and overclocking is pretty damn good. I was 
> at one point looking forward to the K8T890, but considering how much 
> of a joke the whole product line has been (lacking features, months of 
> delays with no explanation, lack of any variety of retail boards), I 
> have to say I'd avoid it like the plague."

Well, let's cut through the B.S. ;-)

* Even when the SATA core is updated to support NCQ, nForce will not
support it under Linux.  No hardware info.

* "hardware firewall" -- sounds silly.  Pretty sure Linux doesn't support
it in any case.

* overclocking -- overclockers are always playing with fire.  any
overclocked hardware is suspect and unsupportable.

* via comes with gigabit lan these days.  My own VIA-based Athlon64
system comes with r8169 gigabit.

	Jeff

Re: How's the nforce4 support in Linux?

[Arjan van de Ven]

> 
> * "hardware firewall" -- sounds silly.  Pretty sure Linux doesn't support
> it in any case.
> 

probably just one of those things implemented in the binary drivers in
software, just like the "hardware" IDE raid is most of the time (3ware
being the positive exception there)

Re: How's the nforce4 support in Linux?

[Tupshin Harper]

Arjan van de Ven wrote:

>>* "hardware firewall" -- sounds silly.  Pretty sure Linux doesn't support
>>it in any case.
>>
>>    
>>
>
>probably just one of those things implemented in the binary drivers in
>software, just like the "hardware" IDE raid is most of the time (3ware
>being the positive exception there)
>
Incorrect. While the logic is is almost certainly implemented in the 
drivers, there is silicon acceleration of the functionality built into 
the Nforce4 chipset (unlike the nforce3), and requires almost no CPU 
time to do its job. Nvidia calls this chipset support ActiveArmor.

-Tupshin

Re: How's the nforce4 support in Linux?

[Lennart Sorensen]

On Thu, Mar 24, 2005 at 04:30:32AM -0500, Jeff Garzik wrote:
> Well, let's cut through the B.S. ;-)
> 
> * Even when the SATA core is updated to support NCQ, nForce will not
> support it under Linux.  No hardware info.

Hmm, either that or someone will figure it out anyhow, like they did
with forcedeth.  Would be nice if nvidia would realize just how dumb not
releasing programing specs is.  How can that be considered a secret.
Maybe they just have a company wide policy of "release nothing" rather
than "don't release the clever 3D acceleration in our drivers that ATI
can't have".  Some comapnies just don't seem to realize they are in the
business of _selling_ hardware, not hardware interface specifications.

> * "hardware firewall" -- sounds silly.  Pretty sure Linux doesn't support
> it in any case.
> 
> * overclocking -- overclockers are always playing with fire.  any
> overclocked hardware is suspect and unsupportable.
> 
> * via comes with gigabit lan these days.  My own VIA-based Athlon64
> system comes with r8169 gigabit.

I think the r8139 has ruined realtek for me forever.  I like the Marvell
Yukon chip Asus includes on many boards (although some people have
reported problems with some Asus boards using them with Linux).

Len Sorensen

Re: How's the nforce4 support in Linux?

[Jeff Garzik]

Lennart Sorensen wrote:
> I think the r8139 has ruined realtek for me forever.  I like the Marvell
> Yukon chip Asus includes on many boards (although some people have
> reported problems with some Asus boards using them with Linux).


I won't disagree with your experiences.  For me, outside of one brief 
moment when the r8169 driver didn't work on Athlon64, it has worked 
flawlessly for me.

RealTek 8169 is currently my favorite gigabit chip.

WRT Marvell Yukon, make sure it is not the Yukon2.  Yukon2 isn't 
supported by any driver in the kernel, presently.

	Jeff

Re: How's the nforce4 support in Linux?

[Andi Kleen]

Jeff Garzik <jgarzik@pobox.com> writes:
>
> I won't disagree with your experiences.  For me, outside of one brief
> moment when the r8169 driver didn't work on Athlon64, it has worked
> flawlessly for me.
>
> RealTek 8169 is currently my favorite gigabit chip.

It does not seem to support DAC (or rather it breaks with DAC enabled), 
which makes it not very useful on any machine with >3GB of memory.

-Andi

Re: How's the nforce4 support in Linux?

[Jeff Garzik]

Andi Kleen wrote:
> Jeff Garzik <jgarzik@pobox.com> writes:
> 
>>I won't disagree with your experiences.  For me, outside of one brief
>>moment when the r8169 driver didn't work on Athlon64, it has worked
>>flawlessly for me.
>>
>>RealTek 8169 is currently my favorite gigabit chip.
> 
> 
> It does not seem to support DAC (or rather it breaks with DAC enabled), 
> which makes it not very useful on any machine with >3GB of memory.

Driver bug.  I can futz with it and get it to do 64-bit on my Athlon64.

	Jeff

Re: How's the nforce4 support in Linux?

[Indrek Kruusa]

Jeff Garzik wrote:

> Andi Kleen wrote:
>
>> Jeff Garzik <jgarzik@pobox.com> writes:
>>
>>> I won't disagree with your experiences.  For me, outside of one brief
>>> moment when the r8169 driver didn't work on Athlon64, it has worked
>>> flawlessly for me.
>>>
>>> RealTek 8169 is currently my favorite gigabit chip.
>>
>>
>>
>> It does not seem to support DAC (or rather it breaks with DAC 
>> enabled), which makes it not very useful on any machine with >3GB of 
>> memory.
>
>
> Driver bug.  I can futz with it and get it to do 64-bit on my Athlon64.


Continuing with off-topic questions: is this "checksum off-load" usable 
with r8169? Is there any other reason (performance?) to use hardware 
TCP/IP checksumming than just "cool, a little chunk of software is 
hardwired again"?
I have seen you mentioned that this causes mainly troubles if you try to 
set it with ethtool. Is it still true?

Indrek

Re: How's the nforce4 support in Linux?

[Jeff Garzik]

Indrek Kruusa wrote:
> Jeff Garzik wrote:
> 
>> Andi Kleen wrote:
>>
>>> Jeff Garzik <jgarzik@pobox.com> writes:
>>>
>>>> I won't disagree with your experiences.  For me, outside of one brief
>>>> moment when the r8169 driver didn't work on Athlon64, it has worked
>>>> flawlessly for me.
>>>>
>>>> RealTek 8169 is currently my favorite gigabit chip.
>>>
>>>
>>>
>>>
>>> It does not seem to support DAC (or rather it breaks with DAC 
>>> enabled), which makes it not very useful on any machine with >3GB of 
>>> memory.
>>
>>
>>
>> Driver bug.  I can futz with it and get it to do 64-bit on my Athlon64.
> 
> 
> 
> Continuing with off-topic questions: is this "checksum off-load" usable 
> with r8169? Is there any other reason (performance?) to use hardware 
> TCP/IP checksumming than just "cool, a little chunk of software is 
> hardwired again"?

It's usable, and enables "zero copy" feature.


> I have seen you mentioned that this causes mainly troubles if you try to 
> set it with ethtool. Is it still true?

Not sure what you are referring to.

	Jeff

Re: How's the nforce4 support in Linux?

[Indrek Kruusa]

Jeff Garzik wrote:

> Indrek Kruusa wrote:
>
>> Jeff Garzik wrote:
>>
>>> Andi Kleen wrote:
>>>
>>>> Jeff Garzik <jgarzik@pobox.com> writes:
>>>>
>>>>> I won't disagree with your experiences.  For me, outside of one brief
>>>>> moment when the r8169 driver didn't work on Athlon64, it has worked
>>>>> flawlessly for me.
>>>>>
>>>>> RealTek 8169 is currently my favorite gigabit chip.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> It does not seem to support DAC (or rather it breaks with DAC 
>>>> enabled), which makes it not very useful on any machine with >3GB 
>>>> of memory.
>>>
>>>
>>>
>>>
>>> Driver bug.  I can futz with it and get it to do 64-bit on my Athlon64.
>>
>>
>>
>>
>> Continuing with off-topic questions: is this "checksum off-load" 
>> usable with r8169? Is there any other reason (performance?) to use 
>> hardware TCP/IP checksumming than just "cool, a little chunk of 
>> software is hardwired again"?
>
>
> It's usable, and enables "zero copy" feature.
>
>
>> I have seen you mentioned that this causes mainly troubles if you try 
>> to set it with ethtool. Is it still true?
>
>
> Not sure what you are referring to.




Sorry  - my brains interpretation was classic rumor case: discussion I 
remembered was about broken NIC not about enabling hw checksum. I 
referred to this one:

http://www.ussg.iu.edu/hypermail/linux/kernel/0503.3/0369.html


Jeff Garzik wrote:

> Evgeniy Polyakov wrote:
>
>> Noone will complain on Linux if NIC is broken and produces wrong
>> checksum
>> and HW checksum offloading is enabled using ethtools.
>
>
>
> Actually, that is a problem and people have definitely complained 
> about it in the past.

Re: How's the nforce4 support in Linux?

[Francois Romieu]

Jeff Garzik <jgarzik@pobox.com> :
> Andi Kleen wrote:
[r8169 driver]
> >It does not seem to support DAC (or rather it breaks with DAC enabled), 
> >which makes it not very useful on any machine with >3GB of memory.
> 
> Driver bug.  I can futz with it and get it to do 64-bit on my Athlon64.

Care to send a patch ?

--
Ueimor

Re: How's the nforce4 support in Linux?

[Jeff Garzik]

Francois Romieu wrote:
> Jeff Garzik <jgarzik@pobox.com> :
> 
>>Andi Kleen wrote:
> 
> [r8169 driver]
> 
>>>It does not seem to support DAC (or rather it breaks with DAC enabled), 
>>>which makes it not very useful on any machine with >3GB of memory.
>>
>>Driver bug.  I can futz with it and get it to do 64-bit on my Athlon64.
> 
> 
> Care to send a patch ?

Not globally applicable, judging from the reports :(

	Jeff