Date: Fri, 10 Dec 1999 17:41:01 +0100 (CET) From: Alexander Leidinger <Alexander@Leidinger.net> To: msmith@freebsd.org Cc: current@freebsd.org Subject: Re: HEADSUP: wd driver will be retired! Message-ID: <199912101641.RAA01801@Magelan.Leidinger.net> In-Reply-To: <199912092157.NAA01406@mass.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 9 Dec, Mike Smith wrote: >> There also exist cases where the chipset is supported but a particular >> functionality isn´t supported yet (in my case it´s the possibility to >> access MS-DOS formated ZIP-disks, harddisk access works well, and I´m >> not the only one with this problem (not counting the people which have >> not tried to use the ata driver but need to access MS-DOS-ZIPs too)). > > I'm completely at a loss as to how the ata driver could be responsible > for your inability to read these disks. I don't have a copy of your > original problem report to hand, but since I have all the hardware here > I'd appreciate it if you could be a little more explicit about your > problem. > > The ata driver just moves bytes; it doesn't give a damn what they are. Try to mount a MS-DOS formatted ZIP-disk (or to access it with mtools). With wfd I´m able to access it, with afd I can´t access it. - Yes, I´m used the right /dev entries and remade them with the newest MAKEDEV, everytime I tested it. - Yes, I´m used the right fstab/mtools.conf entries ({,r}{a,w}fd0s4). If you need more info (dmesg of boot -v with ata and/or wd driver, {g,b}zipped image of an empty, unaccessible ZIP-disk, ...) just ask. Bye, Alexander. -- The best things in life are free, but the expensive ones are still worth a look. 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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199912101641.RAA01801>