From owner-freebsd-current Sat Mar 21 19:35:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA26619 for freebsd-current-outgoing; Sat, 21 Mar 1998 19:35:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA26611 for ; Sat, 21 Mar 1998 19:35:54 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id TAA07597; Sat, 21 Mar 1998 19:31:37 -0800 (PST) Message-Id: <199803220331.TAA07597@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Cory Kempf cc: Mike Smith , freebsd-current@FreeBSD.ORG Subject: Re: Today's kernel doesn't work on (my) DK440LX In-reply-to: Your message of "Mon, 16 Mar 1998 21:44:33 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 21 Mar 1998 19:31:35 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > At 23:48 -0500 98.03.14, Mike Smith wrote: > >> My system seems to be dependent on the line: > >> > >> config kernel root on da0 swap on generic > > > >The 'generic' keyword causes a search for suitable devices. Because > >the bootstrap doesn't recognise the 'da' device, it passes 0 in as the > >boot major. > > So, what should I use for the device? And (more importantly) where do I > find this stuff out? You shouldn't care, especially if you just use config kernel on wd0 > If I try sd0 as the device, config returns that it is unrecognized. > > After booting, / is mounted on /dev/da0a, which has a major device number > of 4 and a minor device number of 0. Perhaps da4a will work... It sounds like the CAM code replaces "sd" everywhere with "da". Maybe you haven't updated config? > >The kernel recently started trusting this value; you will need to extend > >the bootstrap so that it supplies it correctly. > > Uh, how do I do that? For that matter, what does that mean? You can ignore the advice; the bootstrap will believe that it is booting from a SCSI disk, but now SCSI disks are called 'da'. > >> In my kernel config file. Especially the 'swap on generic' part. If I > >> take it out, or replace it with anything I have tried so far, my kernel > >> doesn't work at all. If I attempt to boot, the system attempts to change > >> root to wd0s2b, and I get a Fatal Trap 12. Doing a trace says that it is > >> happening in _ffs_mount(). > > > >This is probably because the disk type on your disk is incorrect. What > >does 'disklabel' say about your boot disk? > > # /dev/rda0a: > type: ESDI ... > It lies: The disk is a SCSI device and the RPM is 10,000. You should use 'disklabel -e' to correct ESDI->SCSI. The rpm value is ignored, but you can change it anyway if it offends your sensibilities. 8) The missing SCSI value is the problem here; because the disk is mislabelled, the bootstrap is passing the wrong value in to the kernel, and the kernel is trying to mount the wrong device. Because you have no 'wd' code in your kernel, the attempt to use that driver fails more spectacularly. Sorry for the delay in the response to your problem. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message