Date: Sun, 09 Jan 2000 10:43:24 +0100 From: sthaug@nethelp.no To: jedgar@fxp.org Cc: obrien@NUXI.com, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/i386/conf GENERIC LINT Message-ID: <5523.947411004@verdi.nethelp.no> In-Reply-To: Your message of "Sat, 8 Jan 2000 21:56:24 -0500 (EST)" References: <Pine.BSF.4.10.10001082154210.20985-100000@pawn.primelocation.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> > > FWIW, with both > > > controller ncr0 > > > controller sym0 > > > in the kernel config, the machine boots successfully, attaching: > > > > Are you able to test this kernel in a machine with a SCSI card that only > > `ncr' supports? > > > > Unfortunately, no. The only ncr-supported chipset here is the 875 as > shown. I just tried 3.4-STABLE here on an older machine with an 810 card. With controller ncr0 controller sym0 in the kernel, it attaches ncr0 and everything works normally: ncr0: <ncr 53c810 fast10 scsi> rev 0x02 int a irq 10 on pci0.17.0 ... da0 at ncr0 bus 0 target 2 lun 0 da0: <IBM DCAS-34330 S61A> Fixed Direct Access SCSI-2 device da0: 10.000MB/s transfers (10.000MHz, offset 8) da0: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C) As a check, I removed the ncr0 line, leaving only the sym driver in the kernel. The machine then panics when booting, as expected (nowhere to mount root from). Running a buildworld now, with both drivers in the kernel. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5523.947411004>