Date: Thu, 18 Mar 1999 04:21:25 +0900 From: "Daniel C. Sobral" <dcs@newsguy.com> To: =?iso-8859-1?Q?S=F8ren?= Schmidt <sos@freebsd.dk> Cc: rnordier@nordier.com, current@FreeBSD.ORG Subject: Re: How to add a new bootdevice to the new boot code ??? Message-ID: <36F000B5.E87D2BF3@newsguy.com> References: <199903171913.UAA26701@freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
"S=F8ren Schmidt" wrote: > = > It seems Daniel C. Sobral wrote: > > "S=F8ren Schmidt" wrote: > > > > > > Well, that breaks somewhere else, as the mount code is clever enoug= h > > > to look at the name of the driver in this case "ad" which doesn't > > > match the specified #0 ie "wd". > > > I kindof tried this by having my driver put itself in both the > > > wd & ad majors in the table, but that doesn't work, because the mou= nt > > > stuff gets confused on the root name somehow, and fails to mount > > > root because the names dont match... > > > > I know you most certainly could not possibly have forgotten that, > > but it's the kind of thing that just *must* be mentioned... > > /etc/fstab? > = > Nope thats not it, been there too :) Ok, I have a clue... bootdev can be different from rootdev. I don't know where this makes a difference, but it makes... :-) Meanwhile, edit sys/boot/i386/libi386/biosdisk.c and change WDMAJOR to 30. If that doesn't help, the problem must be elsewhere. Also, make sure you don't have any root_disk_unit or num_ide_disks set. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "What happened?" "It moved, sir!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?36F000B5.E87D2BF3>