search for: atapi_dma

I sent a note about this a couple of weeks ago, but have not heard anything. I'm really getting a bit desperate. I have a system that I am trying to upgrade from 8.2 to 9.0. I have built it and installed the kernel, but it fails to boot. The boot freezes after probing for my hard drives during the probe of the CDROM. It just sits there, seemingly forever, though I have never waited longer

I'm trying to install 4.8 from cdrom. I get to the kernel config menu, select the first option, install without configuring a kernel, and the boot process hangs accessing the cdrom. ad0 (the hard drive) is recognized fine. The cdrom does: acd0: MODE_SENSE_BIG command timeout - resetting ata1: resetting devices .. done over and over. Finally I get to the screen "Probing devices, please

...'ve had trouble with the burner since. With FreeBSD 4.5, I used "sysctl hw.atamodes=---,---,dma,---" to set the burner to DMA. Everything then worked fine. As far as I know it was using UDMA33. That's what the BIOS said it was using anyway. With FreeBSD 4.8 I use "hw.ata.atapi_dma=1" at boot. This then tells me it is using UDMA33. Unfortunately, I then often get this: acd0: READ_BIG - HARDWARE ERROR asc=0x08 ascq=0x03 error=0x00 I think this means a DMA error. (PS why not say what it is?) If I use atacontrol to downgrade to WDMA2, it works flawlessly (though s...

...llo, I'm building a new system for a friend and I bought a Pioneer DVD-120s drive for him because it was a newer version of the drive I use (DVD-116) and my friend uses (DVD-106s) with FreeBSD. The problem is that FreeBSD cannot probe the drive for some reason. I've tried twiddling the ATAPI_DMA bit, rescanned the drive, and toyed with the cable, but nothing seems to work. The BIOS can see the drive, in fact I can boot FreeBSD using the El-Torrito boot sector on the drive, but I cannot use the CD as the distribution in the installer. FreeBSD 4.8-RELEASE boots all the way up to the poi...

These are new boxes. http://www.supermicro.com/products/system/1U/5015/SYS-5015B-MT.cfm core 2 Q6600 CPU 8Gb 667 RAM Boxes were memtested from Fri-Mon okay. 6.3-RELEASE (amd64) installs fine. Build cycle okay. Running (no load) for a week or so. However, when I try to configure gmirror they hang on boot. After some fiddling it appears issuing #kldload geom_mirror hangs the boxes very hard.

FreeBSD wahoo.prodigy.net 4.9-PRERELEASE FreeBSD 4.9-PRERELEASE #0: Tue Sep 23 10:13:51 CDT 2003 jbryant@wahoo.prodigy.net:/usr/obj/usr/src/sys/WAHOO.SMP i386 Dual Pentium II 333 MHz on Tyan Thunder-2 Motherboard. Anyone else seeing this? jim -- "Religious fundamentalism is the biggest threat to international security that exists today." United Nations Secretary

...imeout. There aren't dumps, all CPU is freezed, state of leds in kayboard doesn't change, only leds of wireless card (D-Link G520) are blinking. Some times is printed on console DMA erros of ad0 before system to freeze. We have already tried to disable ATA DMA (hw.ata.ata_dma=0, hw.ata.atapi_dma=0, hw.ata.wc=0), but system freezes yet. This bridge is runnig on motherboard MSI VIAK8M with 03 Atheros board (D-Link G520), but this problem happens using other motherboards and CPUs. Is there anyway to force dumps? Is there any watchdog hardware for FreeBSD 6.X? All sounds like when we were...

...34 hw.physmem: 2138202112 hw.usermem: 2118488064 hw.pagesize: 4096 hw.floatingpoint: 1 hw.machine_arch: i386 hw.realmem: 2147155968 hw.aac.iosize_max: 65536 hw.amr.force_sg32: 0 hw.an.an_dump: off hw.an.an_cache_mode: dbm hw.an.an_cache_mcastonly: 0 hw.an.an_cache_iponly: 1 hw.ata.ata_dma: 1 hw.ata.atapi_dma: 1 hw.ata.wc: 1 hw.cardbus.debug: 0 hw.cardbus.cis_debug: 0 hw.cs.debug: 0 hw.cs.ignore_checksum_failure: 0 hw.cs.recv_delay: 570 hw.firewire.try_bmr: 1 hw.firewire.hold_count: 3 hw.firewire.fwmem.eui64_hi: 0 hw.firewire.fwmem.eui64_lo: 0 hw.firewire.fwmem.speed: 2 hw.firewire.fwe.stream_ch: 1 hw.f...