I tried both with packet mode enabled and disabled with the same results. I will try changing the disk settings to Large or Auto as others have suggested. BTW, I used the latest versions of PC-BSD and DesktopBSD and both produced the same results as Dfly. Since they are nothing more than cosmetic enhancements to FreeBSD I guess it's safe to say that FreeBSD has the same problem. Of course, no offense meant here. They did a great job in making it easy to install. I am just trying to point out that they are still FreeBSD systems so if they hang on the machine as well then it's not just a bug in Dfly.
On 7/30/06, Francois Tigeot <[EMAIL PROTECTED]> wrote:
On Sun, Jul 30, 2006 at 11:24:17AM -0700, Matthew Dillon wrote: > :FWIW, FreeBSD 6.0 has no trouble booting from the machine I had this > :problem on. > > With the disks set to 'Auto' mode instead of 'Large' mode? Yes. > There's no real difference between FreeBSD's slice table and ours. There > might be a difference with regards to the boot code using packet mode > or not (configurable with boot0cfg), but generally speaking we want to > use packet mode for the greatest compatibility with BIOSes. I also used different disks for both OSes; this may have had an effect. FreeBSD: 120 GB PATA Dragonfly: 74 GB SATA -- Francois Tigeot
