From owner-freebsd-hardware@FreeBSD.ORG Mon Feb 19 11:00:59 2007 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id ECB4216A402 for ; Mon, 19 Feb 2007 11:00:59 +0000 (UTC) (envelope-from achilov-rn@askd.ru) Received: from to-495.askd.ru (master.askd.ru [80.242.75.6]) by mx1.freebsd.org (Postfix) with ESMTP id 57C0113C4AA for ; Mon, 19 Feb 2007 11:00:58 +0000 (UTC) (envelope-from achilov-rn@askd.ru) Received: from to-495.askd.ru (IDENT:shelton@localhost.askd.ru [127.0.0.1]) by to-495.askd.ru (8.13.8/8.13.6) with ESMTP id l1JB0voj032885 for ; Mon, 19 Feb 2007 17:00:57 +0600 (NOVT) (envelope-from achilov-rn@askd.ru) Received: from localhost (localhost [[UNIX: localhost]]) by to-495.askd.ru (8.13.8/8.13.6/Submit) id l1JB0tC3032884 for freebsd-hardware@freebsd.org; Mon, 19 Feb 2007 17:00:55 +0600 (NOVT) (envelope-from achilov-rn@askd.ru) X-Authentication-Warning: to-495.askd.ru: shelton set sender to achilov-rn@askd.ru using -f From: "Rashid N. Achilov" Organization: =?koi8-r?b?7+/v?= "=?koi8-r?b?4fMt88nT1MXNwQ==?= =?koi8-r?b?IOvPzdDMxcvT?=" To: freebsd-hardware@freebsd.org Date: Mon, 19 Feb 2007 17:00:55 +0600 User-Agent: KMail/1.9.5 MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200702191700.55722.achilov-rn@askd.ru> Subject: Floppy drive on Intel m/b X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "Achilov, Rashid" List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Feb 2007 11:01:00 -0000 I had have catched by very strange and frustrating bug, which appeared only (at least by me) on Intel motherboards - D945GNT, DQ965GF. When I try to load GENERIC kernel, system stops sometime after detecting all HDD's, when probed FDD. When I try to load customized kernel, system stops here - it infinitely doing "FDD status" from SECOND FDD, which for ages switched off. I think some "more stupid" BIOS simply reported "no second FDD", but Intel hadn't these in their BIOS and kernel INFINITELY does request FDD status and boot stops here! I think, when doing probe (at least FDD's), unavailability status info sholud be equal "no device" That was a very simply solution: echo "hint.fd.1.disabled=\"1\"" >> /boot/device.hints But I think, here is invalid policy - boot MUST NOT stopped, even status info about some devices unavailable. -- With Best Regards. Rashid N. Achilov (RNA1-RIPE), Web: http://www.askd.ru/~shelton OOO "ACK" telecommunications administrator, e-mail: achilov-rn [at] askd.ru PGP: 83 CD E2 A7 37 4A D5 81 D6 D6 52 BF C9 2F 85 AF 97 BE CB 0A