Date: Fri, 20 May 2005 07:42:25 +0200 From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= <sos@deepcore.dk> To: "Kevin Oberman" <oberman@es.net> Cc: current@freebsd.org Subject: Re: Still at least one ATA problem Message-ID: <78B88E32-9A95-4E0D-AAD0-26DAF7EE893C@deepcore.dk> In-Reply-To: <20050519215648.C1E0A5D07@ptavv.es.net> References: <20050519215648.C1E0A5D07@ptavv.es.net>
index | next in thread | previous in thread | raw e-mail
On 19/05/2005, at 23.56, Kevin Oberman wrote: > Søren, > > I have to take back my "everything works" message. :-( > > With a kernel built on 5/17 I can no longer detach my second ATA > channel. > # atacontrol list > ATA channel 0: > Master: ad0 <IC25N040ATCS05-0/CS4OA61A> ATA/ATAPI revision 5 > Slave: no device present > ATA channel 1: > Master: no device present > Slave: no device present > # atacontrol detach 1 > atacontrol: Invalid channel (null) > > It's not limited to the primary channel, either. > # atacontrol info 0 > atacontrol: Invalid channel (null) It still works, you need to type "atacontrol detach ata1" as the parsing is more tight now, and channel are "ataN" disks are "adN" etc, just as one would think if its wasn't for the old ways of no parsing at all (blaim POLA :) ) - Sørenhelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?78B88E32-9A95-4E0D-AAD0-26DAF7EE893C>