From owner-freebsd-arch@FreeBSD.ORG Mon Aug 10 16:38:33 2009 Return-Path: Delivered-To: freebsd-arch@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3AE341065674; Mon, 10 Aug 2009 16:38:33 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from tower.berklix.org (tower.berklix.org [83.236.223.114]) by mx1.freebsd.org (Postfix) with ESMTP id 9BFE78FC33; Mon, 10 Aug 2009 16:38:32 +0000 (UTC) Received: from park.js.berklix.net (p549A30CD.dip.t-dialin.net [84.154.48.205]) (authenticated bits=0) by tower.berklix.org (8.14.2/8.14.2) with ESMTP id n7AGcuup078141; Mon, 10 Aug 2009 16:38:57 GMT (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by park.js.berklix.net (8.13.8/8.13.8) with ESMTP id n7AGcL4a080340; Mon, 10 Aug 2009 18:38:21 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.14.3/8.14.3) with ESMTP id n7AGeYH0054650; Mon, 10 Aug 2009 18:40:39 +0200 (CEST) (envelope-from jhs@fire.js.berklix.net) Message-Id: <200908101640.n7AGeYH0054650@fire.js.berklix.net> To: Alexander Motin From: "Julian H. Stacey" Organization: http://www.berklix.com BSD Unix Linux Consultancy, Munich Germany User-agent: EXMH on FreeBSD http://www.berklix.com/free/ X-URL: http://www.berklix.com In-reply-to: Your message "Mon, 10 Aug 2009 12:42:58 +0300." <4A7FEBA2.5090106@FreeBSD.org> Date: Mon, 10 Aug 2009 18:40:34 +0200 Sender: jhs@berklix.com Cc: freebsd-hardware@FreeBSD.org, freebsd-arch@FreeBSD.org Subject: Re: Do we still need ATA disk CHS addressing? X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Aug 2009 16:38:33 -0000 Hi Alexander, > Julian H. Stacey wrote: > >> Have anybody seen ATA drive without LBA support in last years? > > Yes > What it is? Some ancient HDD or flash card? Sorry my first reply was short, a holding reply, ( A server died, & 2nd reserve needed time, still does ) I run 20+ assorted hosts from 4.11 to 7.2 Uni & Dual proc, i386 (real 386!) to 686 & amd64, so I guess I'm A) Pretty vulnerable to legacy scare. B) A litmus tesst for a wider community of others, some with older kit, not on lists or with bleeding edge latest hardware, but will get hit when stuff eg HCS gets declared legacy=dumped. (hardware@ & arch@ are more likely mostly high enders, lower percentage of legacy hardware users I guess) If I have to pull the lid on 20/25 hosts, to check disk sticky labels, I will if I must, but could you please reccomend people syntax to run on 4 5 6 7 RELEASES to check if a host is susceptible ? (Yes I know 4 is declares dead, but I still have lots of hosts with it & I suspect quite a lot of others do, be nice to know if any of those boxes are doomed to only upgarde to 7 not 8 ) BTW My configs & dmesg extract: http://berklix.com/~jhs/src/bsd/fixes/FreeBSD/src/jhs/sys/i386/conf/HOLZ The genuine 386 host uses config name MINI. The config name SCAN represents a class of scanners with embedded FreeBSD inside that a bunch of people have http://berklix.com/scanjet/ I will turn on more verbose boot to increase http://berklix.com/scanjet/dmesg/4.11/ from its too minimal current ata0 at port 0x1f0-0x1f7,0x3f6 irq 14 on isa0 Cheers, Julian -- Julian Stacey: BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Mail ASCII plain text not HTML & Base64. http://asciiribbon.org Virused Microsoft PCs cause spam. http://berklix.com/free/