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
Matthew Dillon wrote:
Again, in case the information got lost in the shuffle... before
messing with any DMA modes just try telling the BIOS to put the
disk in 'Large' mode.
The problem is that the BIOS misinterprets the slice table and
puts the disk into a strange mode that
On Sat, Jul 29, 2006 at 11:55:21PM -0700, Matthew Dillon wrote:
Again, in case the information got lost in the shuffle... before
messing with any DMA modes just try telling the BIOS to put the
disk in 'Large' mode.
The problem is that the BIOS misinterprets the slice table
:I was told on IRC yesterday that our fdisk has issues by setting the CHS =
:information to a wrapped value instead of just willing it with ones. Don=
:'t know if that is the culprit, though.
:
:cheers
: simon
I should be able to test it easily since I have to set my test machines
to
:FWIW, FreeBSD 6.0 has no trouble booting from the machine I had this
:problem on.
:
:--
:Francois Tigeot
With the disks set to 'Auto' mode instead of 'Large' mode?
There's no real difference between FreeBSD's slice table and ours. There
might be a difference with regards to the
::I was told on IRC yesterday that our fdisk has issues by setting the CHS =
::information to a wrapped value instead of just willing it with ones. Don=
::'t know if that is the culprit, though.
::
::cheers
:: simon
:
:I should be able to test it easily since I have to set my test machines
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.
On Fri, Jul 28, 2006 at 10:46:51AM -0400, Haidut wrote:
Yes, I followed this article and set everything to MAX PIO. It still
doesn't work and it's very annoying. BTW, to do give Dfly credit I
have to say that installing the latest FreeBSD version gives the same
error. This is a really
Yes, I followed this article and set everything to MAX PIO. It still
doesn't work and it's very annoying. BTW, to do give Dfly credit I
have to say that installing the latest FreeBSD version gives the same
error. This is a really embarassing bug for a modern operating system
to have. Of all
Haidut wrote:
Yes, I followed this article and set everything to MAX PIO. It still
doesn't work and it's very annoying. BTW, to do give Dfly credit I
have to say that installing the latest FreeBSD version gives the same
error.
Does FreeBSD-4 have the same issue?
This is a really embarassing
Yes, FreeBSD 4.x, 5.x and 6.x all produce the same error. NetBSD
installs fine and I haven't tried OpenBSD yet.
I'd gladly try to fix the bug but it's hard to begin when I don't even
know what's causing it. Obviously it's something special to the
Compaq/HP machines since Dfly installed fine on
Haidut wrote:
I installed Dfly on a Compaq Evo desktop and when I try to boot from
the HDD I get several lines of cryptic messages in hex and then a line
withe text BTX halted.
I found some posts on the Internet saying that *BSD have problem
booting on some Compaq machines but none of the posts
On Thu, Jul 27, 2006 at 07:42:32PM -0400, Haidut wrote:
Hi all,
I installed Dfly on a Compaq Evo desktop and when I try to boot from
the HDD I get several lines of cryptic messages in hex and then a line
withe text BTX halted.
I found some posts on the Internet saying that *BSD have problem
13 matches
Mail list logo
