search for: udma33

...did not receive any answers the first time. I have P4P800-VM motherboard with serial ata controlers (ICH5) and serial ata discs. I managed to install FreeBSD 4.9-STABLE on this box when setting the IDE controller in legacy mode. Everything works normal except when booting, the drives are set into UDMA33 mode: atapci0: <Intel ICH5 SATA150 controller> port 0xfc00-0xfc0f,0-0x3,0-0x7,0-0x3,0- 0x7 irq 0 at device 31.2 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 ad0: DMA limited to UDMA33, non-ATA66 cable or device ad0: 76319MB <ST380013AS> [155061/16/63] at a...

...a few SCSI disks. I recently upgraded from FreeBSD 4.5 to 4.7 then almost immediately to 4.8. I'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. (P...

...instead of 9.76Gb that it really is. I found the HD model number with Google on someone elses dmesg and got the correct CHS: ad0: 28615MB <IC25N030ATDA04-0> [58140/16/63] This is what is shown before sysinstall launches, with the stuff in parentheses as ASCII characters: ad0: dma limited to UDMA33, non-ATA66 cable or device ad0: 692MB <(smiley face black)C 5(smiley face white)0(heart)0(smiley face black)T@A 4!0> [1407/16/63] at ata0-master UDMA33 Thanks, Brad Davis

...e: 37529472 1572864 4.2BSD 2048 16384 94 # (Cyl. 1560*- 38791*) **************************************************************** I have that (to me) crypted errore message.. can anybody tell me what does that UDMA ICRC error means? May 24 19:58:30 saturn /kernel: ad0: DMA limited to UDMA33, non-ATA66 cable or device May 24 19:58:30 saturn /kernel: ad0: 9770MB <Maxtor 91021U2> [19852/16/63] at ata0-master UDMA33 May 24 19:58:30 saturn /kernel: ad1: 19092MB <Maxtor 2B020H1> [38792/16/63] at ata1-master UDMA33 May 24 19:58:30 saturn /kernel: Mounting root from ufs:/dev/ad...

...the other day. I was given this system, and I have only run FreeBSD-STABLE on it. The motherboard is a Supermicro370SWD with an Intel 810 "Whitney" chipset (82810DC100 GMCH + 82801AA ICH). The docs say that there is support for UDMA66, but FreeBSD reports that the drive is being set to UDMA33. I booted in verbose mode, and here are the relevant parts from dmesg. atapci0: <Intel ICH ATA66 controller> port 0xffa0-0xffaf at device 31.1 on pci0 ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0xffa0 ata0: mask=03 ostat0=50 ostat2=50 ata0-master: ATAPI 00 00 ata0-slave: ATAPI 14 eb ata0:...

...th Intel 865P chipset. Attempt to install both 5.1-R and 4.8-20030810 snap have failed. I've turned off every onboard device in the BIOS that is possible. During the install of 5.1 the system hangs at acpi_cpu0: throttling enabled: 8 steps (100% to 12.5%), currently 100%. ad4: DMA limited to UDMA33, non ATA66 cable or device ad4: 156334MB (Maxtor 6Y160L0) [3912632/16/63] at ata2-master UDMA33 acd0: DVD-ROM () at ata3-master UDMA33 Mounting root from UFS:/dev/md0 (at this point the system just sits here) This drive has been tested in another system and does come up as UDMA100 on this cable....

I have a couple of DVD drives (one drive, one burner) that used to play DVDs quite fine from 5.3 to somewhere in the 6.x branch. Nowadays I have to send them to PIO4 to play DVDs, because they'll just throw DMA not aligned errors around in UDMA33 or WDMA2 mode. Should someone be interested in this I'm willing to supply all necessary information, such as the exact drives, firmware versions, kernel traces... whatever comes to your mind. I'm also willing to test patches.

...g 3 sub-systems[2] at my system, are these numbers resonsable[3]?? [1] - From dmesg (FreeBSD 6.1-RELEASE): AMD Sempron(tm) Processor 3000+ (1808.33-MHz K8-class CPU) real memory = 2080309248 (1983 MB) avail memory = 1997869056 (1905 MB) ad0: 76350MB <SAMSUNG SP0802N TK200-04> at ata0-master UDMA33 [2] The sub-systems are: 1 - A server giving adreesses of documents to be indexed 2 - A server receiving these documents and replacing (I don't add, just replaces) 3 - The indexer/parser of documents send all them to "2" after X documents [3] - With 500K documents the flush (automat...

...zation) stops. Referring to this portion of the dmesg -v output, of a successful boot, where i have marked ">>>HERE<<<" is where the boot freezes on an unsuccessful boot. This is a constnat problem, on 6.2 as well as 6.3 unchanged. ata0-master: pio=PIO4 wdma=WDMA2 udma=UDMA33 cable=40 wire acd0: setting PIO4 on 63XXESB2 chip acd0: setting UDMA33 on 63XXESB2 chip acd0: <TSSTcorpCD-RW/DVD-ROM TSL462D/DE01> CDRW drive at ata0 as master acd0: read 4134KB/s (4134KB/s) write 4134KB/s (4134KB/s), 1536KB buffer, UDMA33 acd0: Reads: CDR, CDRW, CDDA stream, DVDROM, DVDR, pa...

Hi, I have a server (Dell PowerEdge SC1435, ServerWorks HT1000) on which I'd like to try installing FreeBSD. I've already failed to make 7.0 work on this box and was wondering if you have information about the behavior of the upcoming 7.1 on this hardware. I've been following the "HT1000 chipset errata saga" thread, and the commits by sos@ to CVS (around Jan 2008), but have

...): Invalid argument On the other hand, DVD's play fine, for example with either ''vlc dvd:///dev/acd0@2'' or ''mplayer dvd://2'' I wonder whether the problem is related to the FAILURE line in dmesg: acd0: DVDR <MATSHITADVD-RAM UJ-852S/1.01> at ata0-master UDMA33 acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 cd0 at ata0 bus 0 target 0 lun 0 cd0: <MATSHITA DVD-RAM UJ-852S 1.01> Removable CD-ROM SCSI-0 device cd0: 33.000MB/s transfers cd0: Attempt to query device size failed: NOT...

...lsb=0x00 msb=0x00 Apr 29 01:07:45 udns kernel: ata0: stat1=0x00 err=0x01 lsb=0x14 msb=0xeb Apr 29 01:07:45 udns kernel: ata0: reset tp2 stat0=50 stat1=00 devices=0x9<ATAPI_SLAVE,ATA_MASTER> Apr 29 01:07:45 udns kernel: ad0: setting PIO4 on ROSB4 chip Apr 29 01:07:45 udns kernel: ad0: setting UDMA33 on ROSB4 chip Apr 29 01:07:45 udns kernel: acd0: setting PIO4 on ROSB4 chip Apr 29 01:07:45 udns kernel: ata0: reinit done .. Apr 29 01:07:45 udns kernel: ad0: TIMEOUT - READ_DMA retrying (1 retry left) LBA=18520542 Apr 29 01:07:45 udns kernel: Apr 29 01:07:50 udns kernel: ata0: reiniting channel...

...eebsd.computerhouseprato.com 4.9-PRERELEASE FreeBSD 4.9-PRERELEASE #0: Mon Sep 8 18:14:24 CEST 2003 gmarco@freebsd.computerhouseprato.com:/usr/obj/usr/src/sys/FREEBSD i386 Sep 16 07:55:07 freebsd /kernel: DUMMYNET initialized (011031) Sep 16 07:55:07 freebsd /kernel: ad0: DMA limited to UDMA33, non-ATA66 cable or device Sep 16 07:55:07 freebsd /kernel: ad0: 19464MB <SAMSUNG SV2044D> [39546/16/63] at ata0-master UDMA33 Sep 16 07:55:07 freebsd /kernel: acd0: CDROM <FX4820T> at ata0-slave PIO4 Sep 16 07:55:07 freebsd /kernel: Mounting root from ufs:/dev/ad0s1a Sep 16 07:55:07...

...work interface> on ppbus0 lpt0: <Printer> on ppbus0 lpt0: Interrupt-driven port ppi0: <Parallel I/O> on ppbus0 APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via IOAPIC #0 intpin 2 SMP: AP CPU #1 Launched! ad0: 9671MB <WDC AC310100B> [19650/16/63] at ata0-master UDMA33 ad1: 39082MB <Maxtor 54098U8> [79406/16/63] at ata1-master UDMA33 Waiting 15 seconds for SCSI devices to settle Mounting root from ufs:/dev/da0s1a da0 at ahc0 bus 0 target 0 lun 0 da0: <WDIGTL WD91 ULTRA2 1.00> Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offs...

Hi there, System is FreeBSD 4.9 Stable Had a problem during a portupgrade that when portupgrade did some cleaning a directory could not be deleted because it were not empty. However, it was empty. rm -rf didn't help either. Because I didn't know what to do I decided to boot. At system startup fsck was started which produced the message: unexpected softupdate inconsistency and also that

...s the machine worked fine again for maybe 12 hours but then encountered the same type of errors which start with stuff along the lines of: Sep 26 05:59:35 www /kernel: ad0: READ command timeout tag=0 serv=0 - resetting Sep 26 05:59:35 www /kernel: ata0: resetting devices .. ad0: DMA limited to UDMA33, non-ATA66 cable or device After a few of these the machine stops being able to access its drives and eventually either reboots or hangs. After searching for a bit I saw that disabling DMA access altogether might help the situation out so I have done that at startup which now gives me the foll...

I'm running: localhost(6.1-P)[21] uname -a FreeBSD localhost 6.1-PRERELEASE FreeBSD 6.1-PRERELEASE #19: Wed Mar 15 07:15:25 PST 2006 root@g1-18.catwhisker.org.:/common/S2/obj/usr/src/sys/LAPTOP_30W i386 localhost(6.1-P)[22] I figured I'd grab a copy of the recent 6.1-BETA4 (disc1) ISO to try it out & hand it out to folks.... It seems to have worked, but I got a bit of a whine

...rface> on ppbus0 lpt0: <Printer> on ppbus0 lpt0: Interrupt-driven port ppi0: <Parallel I/O> on ppbus0 APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via IOAPIC #0 intpin 2 SMP: AP CPU #1 Launched! ad0: 29314MB <IBM-DTLA-307030> [59560/16/63] at ata0-master using UDMA33 ad1: 29314MB <IBM-DTLA-307030> [59560/16/63] at ata0-slave using UDMA33 ad2: 29314MB <IBM-DTLA-307030> [59560/16/63] at ata1-master using UDMA33 ad3: 29314MB <IBM-DTLA-307030> [59560/16/63] at ata1-slave using UDMA33 Waiting 15 seconds for SCSI devices to settle sa0 at ahc0 bus 0...

If you start to experience problems with ata devices, please direct your report this way. Thanks -lq

...sio1: type 16550A ppc0: <Parallel port> at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode plip0: <PLIP network interface> on ppbus0 lpt0: <Printer> on ppbus0 lpt0: Interrupt-driven port ppi0: <Parallel I/O> on ppbus0 ad0: DMA limited to UDMA33, non-ATA66 cable or device ad0: 38166MB <ST340014A> [77545/16/63] at ata0-master UDMA33 acd0: DVD-ROM <DVD-ROM DDU1621> at ata1-slave PIO4 Mounting root from ufs:/dev/ad0s1a ---------------------------------------------------------------------------- -------------- I just wonder whethe...