Date: Tue, 20 Mar 2001 20:04:41 +0100 (CET) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= <groudier@club-internet.fr> To: Jussi Reissell <reissell@cc.helsinki.fi> Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Booting problem Message-ID: <Pine.LNX.4.10.10103201930480.1462-100000@linux.local> In-Reply-To: <87itl4657l.fsf@mursu.pesa.fi>
next in thread | previous in thread | raw e-mail | index | archive | help
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 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 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 suggest you to configure it for some higher SCSI ID value and force the 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. > > 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. > > 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: > > sym0: <895> port 0x6c00-0x6cff mem 0xea000000-0xea000fff,0xea001000-0xea0010ff > irq 9 at device 11.0 on pci0 > sym0: Tekram NVRAM, ID 7, Fast-40, LVD, parity checking > > and the disk: > > <IBM DNES-318350W SA30> Fixed Direct Access SCSI-3 device > 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled > 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C) Everything looks fine here. :) Regards, Gérard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.LNX.4.10.10103201930480.1462-100000>