Re: observations with the ata-driver (hd and zip drive)
more observations to the zip-drive problem: First the relevant dmesg-line: atapi: MODE_SENSE_BIG - UNIT ATTENTION skey=6 asc=29 ascq=00 error=00 afd0: IOMEGA ZIP 100 ATAPI/23.D rewriteable drive at ata0 as master afd0: 96MB (196608 sectors), 32 cyls, 64 heads, 96 S/T, 512 B/S afd0: 4096KB/s, transfer limit 64 blks, PIO afd0: Medium: Unknown media (0x0) second : the first 512 bytes of /dev/rfd* are identical, here are checksums: 61088 1 rafd0.txt 61088 1 rafd0s4.txt here are some lines of the files in emacs hexl-mode: : eb2e 4950 4152 5420 636f 6465 2030 3039 ..IPART code 009 0010: 202d 2049 6f6d 6567 6120 436f 7270 6f72 - Iomega Corpor 0020: 6174 696f 6e20 2d20 3131 2f32 332f 3930 ation - 11/23/90 0030: fafc 8cc8 8ed0 bc00 7c8e d88e c0b9 0002 |... the zip disks where formatted under windows, of course. trying to mount the zip-drive gives: msdos: /dev/afd0s4: Invalid argument -- Fritz Heinrichmeyer mailto:[EMAIL PROTECTED] FernUniversitaet Hagen, LG ES, 58084 Hagen (Germany) tel:+49 2331/987-1166 fax:987-355 http://ES-i2.fernuni-hagen.de/~jfh To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: observations with the ata-driver (hd and zip drive)
It seems F. Heinrichmeyer wrote: more observations to the zip-drive problem: First the relevant dmesg-line: atapi: MODE_SENSE_BIG - UNIT ATTENTION skey=6 asc=29 ascq=00 error=00 afd0: IOMEGA ZIP 100 ATAPI/23.D rewriteable drive at ata0 as master afd0: 96MB (196608 sectors), 32 cyls, 64 heads, 96 S/T, 512 B/S afd0: 4096KB/s, transfer limit 64 blks, PIO afd0: Medium: Unknown media (0x0) That looks like it should... second : the first 512 bytes of /dev/rfd* are identical, here are checksums: 61088 1 rafd0.txt 61088 1 rafd0s4.txt here are some lines of the files in emacs hexl-mode: : eb2e 4950 4152 5420 636f 6465 2030 3039 ..IPART code 009 0010: 202d 2049 6f6d 6567 6120 436f 7270 6f72 - Iomega Corpor 0020: 6174 696f 6e20 2d20 3131 2f32 332f 3930 ation - 11/23/90 0030: fafc 8cc8 8ed0 bc00 7c8e d88e c0b9 0002 |... the zip disks where formatted under windows, of course. trying to mount the zip-drive gives: msdos: /dev/afd0s4: Invalid argument This has appeared before IIRC, I've no idea why this doesn't work, but I can rig up my ZIP drive, but I dont have DOS nor WINDOWS, do it fail also if the disk is formatted under FreeBSD ?? -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: observations with the ata-driver (hd and zip drive)
On Fri, 26 Nov 1999, Soren Schmidt wrote: It seems F. Heinrichmeyer wrote: more observations to the zip-drive problem: First the relevant dmesg-line: I'm also still having a small problem with the ata driver and my HP Colorado 8G. I have it hanging off an ATAPI CDROM as a slave. The dmesg says: ata-pci1: AcerLabs Aladdin IDE controller irq 0 at device 11.0 on pci0 ata-pci1: Busmastering DMA supported ata0: iobase=0x01f0 altiobase=0x03f6 ata0: mask=03 status0=00 status1=00 ata0: mask=03 status0=00 status1=00 ata0: devices = 0xc ata0 at 0x01f0 irq 14 on ata-pci1 This indicates that it sees two ATAPI devices. But when the system starts up, all I get is: ata0-master: piomode=4 dmamode=2 udmamode=2 dmaflag=1 atapi: MODE_SENSE_BIG - UNIT ATTENTION skey=6 asc=29 ascq=00 error=00 acd0: DELTA OPC-K101/ST1 F/W by OIPD/VER-3.40 CDROM drive at ata0 as master acd0: read 687KB/s (6875KB/s), 128KB buffer, PIO acd0: supported read types: CD-R, CD-RW, CD-DA, packet acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked No tape drive is found. All worked well with the old drivers. == = Bryan D. Liesner LeezSoft Communications, Inc. = = A subsidiary of LeezSoft Inc. = = [EMAIL PROTECTED] Home of the Gipper= == To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: observations with the ata-driver (hd and zip drive)
It seems Bryan Liesner wrote: On Fri, 26 Nov 1999, Soren Schmidt wrote: It seems F. Heinrichmeyer wrote: more observations to the zip-drive problem: First the relevant dmesg-line: I'm also still having a small problem with the ata driver and my HP Colorado 8G. I have it hanging off an ATAPI CDROM as a slave. The dmesg says: ata-pci1: AcerLabs Aladdin IDE controller irq 0 at device 11.0 on pci0 ata-pci1: Busmastering DMA supported ata0: iobase=0x01f0 altiobase=0x03f6 ata0: mask=03 status0=00 status1=00 ata0: mask=03 status0=00 status1=00 ata0: devices = 0xc ata0 at 0x01f0 irq 14 on ata-pci1 This indicates that it sees two ATAPI devices. But when the system starts up, all I get is: ata0-master: piomode=4 dmamode=2 udmamode=2 dmaflag=1 atapi: MODE_SENSE_BIG - UNIT ATTENTION skey=6 asc=29 ascq=00 error=00 acd0: DELTA OPC-K101/ST1 F/W by OIPD/VER-3.40 CDROM drive at ata0 as master acd0: read 687KB/s (6875KB/s), 128KB buffer, PIO acd0: supported read types: CD-R, CD-RW, CD-DA, packet acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked No tape drive is found. All worked well with the old drivers. Hmm, what can I say, I use a simlar setup, just with either a Seagate or an Onstream tape, both work well. You should probably sprinkle a couple of printf's in the atapi probe code and the tape driver an see where it fails... -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: observations with the ata-driver (hd and zip drive)
On 26 Nov, Soren Schmidt wrote: trying to mount the zip-drive gives: msdos: /dev/afd0s4: Invalid argument This has appeared before IIRC, I've no idea why this doesn't work, but I can rig up my ZIP drive, but I dont have DOS nor WINDOWS, do it fail also if the disk is formatted under FreeBSD ?? I didn´t tried to reproduce this recently, but you could try to format the ZIP-disc with mtools: mformat -t 96 -h 64 -s 32 -H 32 z: Fritz: could you post the output of "minfo z:" (ata-controller)? Here´s the one with wd (perhaps a diff between them gives someone a hint): ---snip--- (101) netchild@ttyp2 minfo z: device information: === filename="/dev/rwfd0s4" sectors per track: 32 heads: 64 cylinders: 96 mformat command line: mformat -t 96 -h 64 -s 32 -H 32 z: bootsector information == banner:"(?6;1IHC" sector size: 512 bytes cluster size: 4 sectors reserved (boot) sectors: 1 fats: 2 max available root directory slots: 512 small size: 0 sectors media descriptor byte: 0xf8 sectors per fat: 192 sectors per track: 32 heads: 64 hidden sectors: 32 big size: 196576 sectors physical drive id: 0x80 reserved=0x0 dos4=0x29 serial number: 39BC1102 disk label="ZIP-100" disk type="FAT16 " ---snip--- And here the boot-message: ---snip--- wdc0: unit 1 (atapi): IOMEGA ZIP 100 ATAPI/23.D, removable, intr, iordis wfd0: medium type unknown (no disk) wfd0: buggy Zip drive, 64-block transfer limit set ---snip--- Søren, I assume the ata-controller knows about the last line, right? Bye, Alexander. -- I'll be damned if I can't win when I'm keeping score. http://netchild.home.pages.de Alexander+Home @ Leidinger.net Key fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: observations with the ata-driver (hd and zip drive)
It seems Alexander Leidinger wrote: I didn´t tried to reproduce this recently, but you could try to format the ZIP-disc with mtools: mformat -t 96 -h 64 -s 32 -H 32 z: I'll dig out my ZIP drive tonight a do some testing... ---snip--- wdc0: unit 1 (atapi): IOMEGA ZIP 100 ATAPI/23.D, removable, intr, iordis wfd0: medium type unknown (no disk) wfd0: buggy Zip drive, 64-block transfer limit set ---snip--- Søren, I assume the ata-controller knows about the last line, right? It does, and it also says so in the probe... -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
