From owner-freebsd-scsi Tue Mar 20 13:17:36 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from front1m.grolier.fr (front1m.grolier.fr [195.36.216.51]) by hub.freebsd.org (Postfix) with ESMTP id C64BA37B71A for ; Tue, 20 Mar 2001 13:17:32 -0800 (PST) (envelope-from groudier@club-internet.fr) Received: from nas2-169.mea.club-internet.fr (nas2-169.mea.club-internet.fr [195.36.200.169]) by front1m.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with ESMTP id WAA05949; Tue, 20 Mar 2001 22:15:18 +0100 (MET) Date: Tue, 20 Mar 2001 20:04:41 +0100 (CET) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= X-Sender: groudier@linux.local To: Jussi Reissell Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Booting problem In-Reply-To: <87itl4657l.fsf@mursu.pesa.fi> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 20 Mar 2001, Jussi Reissell wrote: > Sorry folks, this probably isn't a FBSD topic as such, more of a > generic hw problem, I guess ... but maybe some tekram owner is able to > give me advice. I never heared of this problem, neither am a Tekram owner. So, I shouldn't have replied to your mail. :) I would suggest you to report the problem to Tekram support, and why not=20 upgrade the BIOS of the board if some new version is available. > I'm having a bit of a problem booting from an IBM disk hooked up to a > Tekram 390u2w controller. At boot-time the controller refuses to load > the BIOS and hence boot from the SCSI disk. The 390 spits out a: "No > BIOS disk found! SCSI BIOS not installed" At least by default, the controller BIOS scans SCSI devices by ascending SCSI ID number. If it is some timing problem, using a different SCSI ID=20 for your disk can make difference. It is just guessing... If, for example, your disk is configured for a very low SCSI ID, I would=20 suggest you to configure it for some higher SCSI ID value and force the=20 BIOS to scan some (non existing) SCSI IDs before this one. Each SCSI ID scanned is about 250 ms elapsed. I haven't any better idea. May-be you already tried it. > According to the Tekram manual, this is normal if only a CD-ROM is > installed. I get this behaviour with only the IBM disk on board. >=20 > The strange thing is that the controller occasionally is able to find > the disk allright and boot from it but most of the time is not. >=20 > What should I look for? I took out all the other SCSI devices, so as > far as I can tell, the problem should be in the controller, cabling or > the disk itself. Maybe termination? If the SCSI hard disk is working reliably (you may exercise the drive after boot from IDE), then the SCSI BUS is likely correct. > If I boot off of an IDE disk, the sym driver finds the disk ok and > although performance isn't stellar, things function as > expected. Here's what dmesg says about the controller: >=20 > sym0: <895> port 0x6c00-0x6cff mem 0xea000000-0xea000fff,0xea001000-0xea0= 010ff > irq 9 at device 11.0 on pci0 > sym0: Tekram NVRAM, ID 7, Fast-40, LVD, parity checking >=20 > and the disk: >=20 > Fixed Direct Access SCSI-3 device=20 > 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabl= ed > 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C) Everything looks fine here. :) Regards, G=E9rard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message