From owner-freebsd-stable@FreeBSD.ORG Sat Nov 12 17:59:27 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A55EA16A41F for ; Sat, 12 Nov 2005 17:59:27 +0000 (GMT) (envelope-from rsmith@xs4all.nl) Received: from smtp-vbr8.xs4all.nl (smtp-vbr8.xs4all.nl [194.109.24.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id F1F5C43D53 for ; Sat, 12 Nov 2005 17:59:26 +0000 (GMT) (envelope-from rsmith@xs4all.nl) Received: from slackbox.xs4all.nl (slackbox.xs4all.nl [213.84.242.160]) by smtp-vbr8.xs4all.nl (8.13.3/8.13.3) with ESMTP id jACHxOY1067126; Sat, 12 Nov 2005 18:59:25 +0100 (CET) (envelope-from rsmith@xs4all.nl) Received: by slackbox.xs4all.nl (Postfix, from userid 1001) id BD2B3B822; Sat, 12 Nov 2005 18:59:24 +0100 (CET) Date: Sat, 12 Nov 2005 18:59:24 +0100 From: Roland Smith To: Timm Florian Gloger Message-ID: <20051112175924.GA46385@slackbox.xs4all.nl> Mail-Followup-To: Timm Florian Gloger , freebsd-stable@freebsd.org References: <4375E87D.6070008@web.de> <20051112134735.GA39705@slackbox.xs4all.nl> <4376038B.7070801@gmail.com> <20051112155055.GA42074@slackbox.xs4all.nl> <437626AE.1060303@gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="9jxsPFA5p3P2qPhR" Content-Disposition: inline In-Reply-To: <437626AE.1060303@gmail.com> User-Agent: Mutt/1.4.2.1i X-GPG-Fingerprint: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 X-GPG-Key: http://www.xs4all.nl/~rsmith/pubkey.txt X-GPG-Notice: If this message is not signed, don't assume I sent it! X-Virus-Scanned: by XS4ALL Virus Scanner Cc: freebsd-stable@freebsd.org Subject: Re: FreeBsd 6.0 i386 freezes after ata initialization X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Nov 2005 17:59:27 -0000 --9jxsPFA5p3P2qPhR Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Nov 12, 2005 at 06:30:22PM +0100, Timm Florian Gloger wrote: > Disabling firewire did very well. Installation continues now. > Are there known fixes how to get firewire running after installing or is= =20 > this just a "installation-kernel" problem? The firewire driver is part of the GENERIC kernel. But AFAICT your chipset doesn't seem to be on the list of supported devices in fwohci(4). If you get the system up and running, try enabling firewire in the BIOS again, and see if the system boots. If the system boots, but there is no firewire device, check the output of 'pciconf -lv' to see what kind of chip it is. Have a look at the archives for the freebsd-firewire list. (http://lists.freebsd.org/pipermail/freebsd-firewire/) Maybe your problem has been handled there. If not, post a message to that list. > Thanks for your help Roland You're welcome! Roland --=20 R.F.Smith (http://www.xs4all.nl/~rsmith/) Please send e-mail as plain text. public key: http://www.xs4all.nl/~rsmith/pubkey.txt --9jxsPFA5p3P2qPhR Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDdi18EnfvsMMhpyURApL4AJ9MwGOw3EaGBqEjW9aHN/r6krULrQCgnf2y wTmRM1yehaErx32Pk8RZvpE= =rMMP -----END PGP SIGNATURE----- --9jxsPFA5p3P2qPhR--