Hi,
I have two PCs, with apparently a somewhat old
motherboard, since there's a maximum support for
UDMA66 by the harddisk controller.
The attached harddisks are newer and allow a
higher speed of UDMA100.
This combination of older motherboard and newer
harddisk causes great problems with 5.X
Important:
Don't write to the drive after changing bios settings.
Just see if it works.
When I installed 5.3 on another machine w/ a Maxtor 40GB HDD, FBSD
complained about the drive geometry settings. It seems the
defaults use CHS regardless of how the bios is set. I had to
change geometry
--- Mars Trading [EMAIL PROTECTED] wrote:
This idea may seem useless but what have you got to
lose?
Have you tried changing bios setting for hard drive
mode to auto or
something other than LBA? Maybe LARGE or CHS?
Is there a risk that I lose all data on my disk, when
changing this in
At 08:47 2/16/2005, Rob wrote:
--- Mars Trading [EMAIL PROTECTED] wrote:
This idea may seem useless but what have you got to
lose?
Have you tried changing bios setting for hard drive
mode to auto or
something other than LBA? Maybe LARGE or CHS?
Is there a risk that I lose all data on my
Rob wrote:
In this case there's only one harddisk and when I do
# atacontrol mode 0 UDMA66 BIOSPIO
I get lots of such lines:
ad0: WARNING - WRITE_DMA UDMA ICRC error (retrying
request) LBA=20185375
ad0: WARNING - WRITE_DMA UDMA ICRC error (retrying
request) LBA=20185375
ad0: FAILURE - WRITE_DMA
--- Mark Kirkwood [EMAIL PROTECTED] wrote:
Rob wrote:
What does that mean? UDMA66 and hw.ata.ata_dma=0 ?
Hmmm, that is interesting, 2 suggestion to determine
what is going on:
- run diskinfo -t on your disks and let us know the
results
Motherboard: LG, type LGM-VBX6
atapci0: VIA
Mark Kirkwood wrote:
Rob,
I am currently running 5.3 Release on a Tyan
Trinity 400 (VIA 82C596B
UDMA66) with 2 x Seagate Barracude IV (UDMA100)
and have no stability issues. e.g from dmesg:
atapci0: VIA 82C596B UDMA66 controller port
0xe000-0xe00f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7
Rob wrote:
What does that mean? UDMA66 and hw.ata.ata_dma=0 ?
Hmmm, that is interesting, 2 suggestion to determine what is going on:
- run diskinfo -t on your disks and let us know the results
- use sysctl to set hw.ata.ata_dma=1 and see what happens
And why then is UDMA66 not automatically
--- Mark Kirkwood [EMAIL PROTECTED] wrote:
Rob wrote:
What does that mean? UDMA66 and hw.ata.ata_dma=0 ?
Hmmm, that is interesting, 2 suggestion to determine
what is going on:
- run diskinfo -t on your disks and let us know the
results
- use sysctl to set hw.ata.ata_dma=1 and see what
Rob wrote:
Sorry, I don't understand your last question in
the brackets. What does 'they' refer to? The
motherboard(s), the type of dma, or what?
I was cryptically asking for the model numbers of your motherboard(s),
e.g. mine is a Tyan Trinity 400 S1854
regards
Mark
Hey Rob,
I'm on the same hardware - 82C596B (UDMA66) - but using a Seagate 20GB
UDMA100 Drive. Relevant info from dmesg:
atapci0: VIA 82C596B UDMA66 controller port
0xd000-0xd00f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 7.1 on pci0
ata0: channel #0 on atapci0
ad0: 19092MB ST320014A/3.07
Hi,
I have two PCs, with apparently a somewhat old
motherboard, since there's a maximum support for
UDMA66 by the harddisk controller.
The attached harddisks are newer and allow a
higher speed of UDMA100.
This combination of older motherboard and newer
harddisk causes great problems with 5.X
Rob,
I am currently running 5.3 Release on a Tyan Trinity 400 (VIA 82C596B
UDMA66) with 2 x Seagate Barracude IV (UDMA100) and have no stability
issues. e.g from dmesg:
atapci0: VIA 82C596B UDMA66 controller port
0xe000-0xe00f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 7.1 on pci0
ata0:
13 matches
Mail list logo
