search for: udma2

...-ROM is going to look like to the program, is >that it looks like an additional hard disk which a very high drive >number (typically 9Fh or so); MS-DOS will normally ignore this since it >asks the BIOS how many drives there are and ignores the rest. >Does the error message come from UDMA2.SYS or...? > -hpa yes, it comes from UDMA2.SYS, it does a series of initialisation tests (read spead for example, and VDS). I don't know behaviour when booting to MSDOS on harddisk, only Isolinux --> A: and Isolinux --> Memdisk --> Disk image Bernd http://fdos.org/ripcord/beta9...

...I can't spread/provide that disk image. I'll manage, though. It's just making my testing a tiny bit more difficult (hit ESC each time the machine boots, then select floppy, instead of let isolinux boot and then select 'A' for localboot 0x80 as defined in my isolinux.cfg file) UDMA2 author mailed this: ------------ and avoids addressing over 20 bits. Re: the "Int 13h" function codes used by UDMA2, they are (A) 41h to see if an EDD BIOS is present, 48h to request EDD parameters for every disk and 08h to request CHS values for every disk. All are "basic" fu...

...Shop kernel: ata1: FAILURE - zero length DMA transfer attempted Dec 10 07:54:31 Shop kernel: ata1: setting up DMA failed cat /var/log/messages | grep ata1: cd0 at ata1 bus 0 scbus3 target 0 lun 0 cd0: <TSSTcorp DVD-ROM TS-H352C DE02> Removable CD-ROM SCSI-0 device cd0: 33.300MB/s transfers (UDMA2, ATAPI 12bytes, PIO 65534bytes) cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed cd1 at ata1 bus 0 scbus3 target 1 lun 0 cd1: <PHILIPS DVD+-RW DVD8701 5D24> Removable CD-ROM SCSI-0 device cd1: Serial Number MY0P92257015956T02SA cd1: 33.300MB/s transfers (U...

>information a bit closer; it'd find that it's marked accordingly. UDMA2.SYS author now worked around it, it seems you do something with "DPTE" in isolinux.asm but not using it (probably for memdisk or direct floppy/harddisk emulation?). also something about EDD v1.1 and v3.0 specifications and setting bits to 1. Anyway, the driver works now on: BIOS -> cd...

We run several RH7.2/7.3 servers & recently 2 of them, although still working fine, have started to show kjournald as generally using over 50% cpu% on 'top' - virtually continuously. Free cpu% generally less than 25% now! Both machines are also using software RAID5 EIDE ....... otherwise are standard server installs. Any info on what kjournald is & why it should have recently

...nd it would seem that my disk access is extremely slow. I have the latest updated kernel from RedHat 8.0 kernel 2.4.18-27.8.0. Somehow I think it is related to the UDMA stuff (shows my level of understanding). I have run hdparm and although I think I should at least udma level 5, I have at most udma2 listed. Is this a kernel option/update problem? The first question is whether my disk is really not optimum. Any help or help would be appreciated Or if you need more info just ask. ned blurock Here is some less vague info: ---------------------------------------------------------------- hdp...

Hello Folks, We have 2 (identical hardware) busy public 2U rack servers, both have several hundred users & peak email (for example) deliveries at 300/5min during the daytime. Both servers run RAID1 over 2 EIDE disk drives. One server is fine - it never has problems - it is running RH7.3 and CPU loads are normal. The other server has constant disk activity & kjournald at CPU load of

...solinux (with either loading an image directly through MEMDISK, or booting to A:), and not when using a bootdisk directly or booting a bootdisk directly which has SYSLINUX on it. configuration: bootable cdrom with Isolinux 2.11/2.12pre9 as bootloader. 1.44MB bootdisk with MSDOS.SYS/IO.SYS and the UDMA2 dos driver, http://fdos.org/ripcord/beta9sr1/other/misc/Udma2_16.zip (sourcecode included) DEVICE=UDMA2.SYS SHELL=A:\COMMAND.COM A:\ /D /P Doesn't Isolinux clear everything before a localboot 0x00 ? I guess not, as sometimes the eltorito.sys driver from www.nu2.nu also still loads, which mean...

...CCbytes=4 BuffType=unknown, BuffSize=0kB, 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=no WriteCache=enabled Drive conforms to: unknown: * signifies the current active mode So from recommendation on website I did this to match MaxMultiSect: hdparm -m16 /dev/hda then tried this to turn MultSect off: hdparm -m0 /dev/hda Still getting error. The Supermicro MBD-X7SBL...

...e size with M = 1024*1024: 27199 MBytes Capabilities: LBA, IORDY(can be disabled) Buffer size: 512.0kB Queue depth: 1 Standby timer values: spec'd by Standard R/W multiple sector transfer: Max = 16 Current = 16 DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 *udma4 Cycle time: min=120ns recommended=120ns PIO: pio0 pio1 pio2 pio3 pio4 Cycle time: no flow control=240ns IORDY flow control=120ns Commands/features: Enabled Supported: * READ BUFFER cmd * WRITE BUFFER cmd...

...e=0, ECCbytes=34 BuffType=DualPortCache, BuffSize=1961kB, MaxMultSect=16, MultSect=16 CurCHS=16383/16/63, CurSects=-66060037, LBA=yes, LBAsects=40088160 IORDY=on/off, tPIO={min:240,w/IORDY:120}, tDMA={min:120,rec:120} PIO modes: pio0 pio1 pio2 pio3 pio4 DMA modes: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 *udma4 AdvancedPM=no Drive Supports : ATA/ATAPI-4 T13 1153D revision 17 : ATA-1 ATA-2 ATA-3 ATA-4 DMA modes: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 *udma5 4:15pm up 14 days, 23:58, 2 users, load average: 10.72, 7.41, 6.20 vmstat 5 procs memory...

...BuffType=DualPortCache, BuffSize=256kB, MaxMultSect=16, MultSect=16 CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=73400320 IORDY=yes, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120} PIO modes: pio0 pio1 pio2 DMA modes: sdma0 sdma1 sdma2 mdma0 mdma1 mdma2 UDMA modes: udma0 udma1 udma2 udma3 udma4 *udma5 AdvancedPM=no Drive conforms to: ATA/ATAPI-5 published, ANSI NCITS 340-2000: * signifies the current active mode The bonnie numbers show for sequential output: Good Machine Host: 76,857K/Sec My Machine Host: 72,561K/Sec Good Machine Centos 5.7 Guest: 66,266K/sec My Machine...

I have just released SYSLINUX 3.00-pre9. The only change versus 3.00-pre8 is that the MEMDISK query API now reports the boot loader ID byte, per Bernd's suggestion. This is a release candidate, and I plan to release it as 3.00 *tomorrow*, unless I hear back anything bad. -hpa

...en (not only asterisk) and the only way to recover is a full reboot. Not sure how or if this is related to the new harddisk settings but we made the changes last friday and this (seriuos) problem happened tuesday and thursday (today) this week. The settings we have now in our harddisks is using udma2 with the following settings as show with hdparm: dev/hda: multcount = 16 (on) IO_support = 3 (32-bit w/sync) unmaskirq = 0 (off) using_dma = 1 (on) keepsettings = 0 (off) readonly = 0 (off) readahead = 8 (on) geometry = 4865/255/63, sectors = 78165360, start =...

...fa0-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: mask=03 stat0=50 stat1=10 ata0-master: ATA 01 a5 ata0: devices=09 ata0: at 0x1f0 irq 14 on atapci0 ... ad0: success setting UDMA2 on Intel chip Creating DISK ad0 ar: FreeBSD check1 failed ad0: <Maxtor 4D040H2/DAH017K0> ATA-6 disk at ata0-master ad0: 38146MB (78125000 sectors), 77504 C, 16 H, 63 S, 512 B ad0: 16 secs/int, 1 depth queue, UDMA33 ad0: piomode=4 dmamode=2 udmamode=5 cblid=1 My question is, why did the kerne...

...BuffType=DualPortCache, BuffSize=8192kB, MaxMultSect=16, MultSect=16 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 udma3 udma4 *udma5 AdvancedPM=no WriteCache=enabled Drive conforms to: Unspecified: ATA/ATAPI-1 ATA/ATAPI-2 ATA/ATAPI-3 ATA/ATAPI-4 ATA/ATAPI-5 ATA/ATAPI-6 * signifies the current active mode Any suggestions welcomed. Thanks! --Chris

My apologies in advance for asking such an elementary question. I called myself searching the Installation Guide and Deployment Guide, with no success. The situation is that I bought a Lite-On ATAPI iHAP122 that will not burn DVDs unless I use hdparm to turn dma off. I bought that drive because it was a rare beige drive. Until I can find a decent DVD burner and/or get a Windows machine put

...e=0, ECCbytes=52 BuffType=DualPortCache, BuffSize=1821kB, MaxMultSect=16, MultSect=16 CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=66055248 IORDY=on/off, tPIO={min:240,w/IORDY:120}, tDMA={min:120,rec:120} PIO modes: pio0 pio1 pio2 pio3 pio4 DMA modes: mdma0 mdma1 mdma2 udma0 udma1 udma2 AdvancedPM=yes: disabled (255) WriteCache=enabled Drive Supports : Reserved : Reserved : Reserved : ATA/ATAPI-6 T13 1410D revision 1 : Reserved : Reserved : Reserved : ATA-2 ATA-3 ATA-4 ATA-5 ATA-6 ----------------- The initial problem I encountered with the drive is the I was able to see only...

...=40 BuffType=DualPortCache, BuffSize=512kB, MaxMultSect=16, MultSect=16 CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=20044080 IORDY=on/off, tPIO={min:160,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 AdvancedPM=no WriteCache=enabled Drive conforms to: device does not report version: 1 2 3 4 /sbin/lspci= 00:00.0 Host bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133] (rev 02) 00:01.0 PCI bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133 AGP] 00:07.0 ISA bridge:...

Hello, I've got a (P)ATA disk in a special frame. The disk itself supports UDMA-100 (and has an 80-ribbon cable), but the frame isn't compatible with that. By default, FreeBSD negotiates UDMA-100, and the console starts to fill with ICRC errors. In the past, I used a patch to ata-all.c that enabled the following entry in loader.conf to force the disk to UDMA-33, so it worked fine: