"Søren Schmidt" wrote:
>
> It seems Daniel C. Sobral wrote:
> > "Søren Schmidt" wrote:
> > >
> > > Well, that breaks somewhere else, as the mount code is clever enough
> > > 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 mount
> > > 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)
d...@newsguy.com
d...@freebsd.org
"What happened?"
"It moved, sir!"
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
