From owner-freebsd-scsi Tue Feb 19 5:26:59 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from rigel.grass.st (rigel.grass.st [195.197.32.30]) by hub.freebsd.org (Postfix) with ESMTP id 20E1B37B416 for ; Tue, 19 Feb 2002 05:26:54 -0800 (PST) Received: (from bsdscsi@localhost) by rigel.grass.st (8.9.3/8.9.3) id PAA25410 for scsi@freebsd.org; Tue, 19 Feb 2002 15:26:52 +0200 (EET) (envelope-from bsdscsi) Date: Tue, 19 Feb 2002 15:26:52 +0200 From: mika ruohotie To: scsi@freebsd.org Subject: ASUS P2B-DS unable to boot 4.5 or 5.0-20020218 from floppies Message-ID: <20020219152652.A25402@rigel.grass.st> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org as the subject says... i have the said motherboard and i am totally unable to boot either one of those operating systems (from floppies) on that hardware. it doesnt matter if i leave the onboard scsi unused, it's still unable to boot. i also tested the USB behaviour suggested on some mailing list (i forgot which one, i searched the keywords from many lists). anyone with suggestions, or preferably idea what's broken. yes, the said hardware used to run freebsd, at least current from early summer works, also possibly 4.2 (someone else said 4.2 would work, on some mailinglist). what i understand, it's some kind of scsi hang, caused by ahc, since it's looping and tells me someone reset the scsi-bus (which is sitting without disks, with disks it just hangs, no difference if i have just terminators on it or not) i'll mail this to scsi, since it's more about scsi than hardware. mickey -- mika ruohotie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message