Thanks Mathias for your answer. But I think, I've performed your suggestion without much success.
Here after what I've tried ... - install dfbsd on partition3: no success - install dfbsd on partition1: no success within Grub, I've tried: - root (hd1,1): no success - rootnoverify (hd1,1,a): no success - rootnoverify (hd1,1): no success During the install, I've looked at the tty1 (kind of log file), and, amongst different messages, I see "raw partition offset != slice offset". Does this could be the cause of my problem ? If yes, how to solve ? (in the dfbsd mailing-list there is one person having the same error message, but no one has answered to him). An another strange error message I see ... after the command disklabel64 -B -r -w ad6s1 auto, I see "cannot find label (no disk label)". Does this is the cause of the problem ? (for this message, I've not yet googling) Thanks On Fri, Nov 11, 2011 at 4:25 PM, Matthias Rampke <matthias.ram...@googlemail.com> wrote: > Hello, > > I see two potential problems here: > > > On Freitag, 11. November 2011 at 07:36, william opensource4you wrote: > >> Disk 2 has >> pcbsd on primary partition (p1), and I've prepared a 15GB partition >> (p2) for dfbsd.. > > > I'm not sure about this, but do by any chance PC-BSD and DragonFly use the > same partition type? If so, something somewhere might get confused and look > for the DragonFly disklabel (= BSD subpartitioning) in the PC-BSD partition. > If so, I don't really know what to do about that. > >> >> In my grub (managed by my linux: last fedora) I've put (same as for >> netbsd and freebsd): >> Root (hd1,1,a) >> Makeactive >> Chainloader +1 > > > Maybe (but this is more of a blind guess either) try (hd1,1)? > > --matthiasr >
