replaced the SATA cable as well. My plan is to revert
the ATA drivers to two weeks ago, and see if the problem persists.
Failing that, I will test to see if this is a cooling problem. Failing
that, I will replace the SATA controller. However, I wanted to know if
I'm barking up the wrong tree
-master UDMA133
Nothing else was changed in the machine except the specific version of
-CURRENT since the time things worked and now. In addition to replacing
the drive, I have replaced the SATA cable as well. My plan is to revert
the ATA drivers to two weeks ago, and see if the problem persists
the ATA drivers to two weeks ago, and see if the problem persists.
Failing that, I will test to see if this is a cooling problem. Failing
that, I will replace the SATA controller. However, I wanted to know if
I'm barking up the wrong tree, and perhaps this is a software issue.
There are some
the ATA drivers to two weeks ago, and see if the problem persists.
Failing that, I will test to see if this is a cooling problem. Failing
that, I will replace the SATA controller. However, I wanted to know if
I'm barking up the wrong tree, and perhaps this is a software issue.
There are some
It seems Joe Marcus Clarke wrote:
There are some early issues of the SiI3112 chips that has problems that
can cause datacorruption etc etc..
You can try the following patch (which btw re@ has for approval),
otherwise I'd try another controller as there seem to be no end of the
troubles
' and rebuild everything twice (using and old backup kernel from
Current of a month or so ago) and go the same kind of 'panic' as described
earlier. I read the thread on the problem, and finally commented out the
'ATA' Drivers in the Kernel config file and rebooted and had no problems at
all
Are there any plans to support the buggy CMD640 interface in the future
now that 4.0-RELEASE has come and gone? I have a box that is running 3.4
happily, and it has this interface. I really would like the chance to use
some of the 4.0 features, but I can not while support for this interface
, but I can not while support for this interface
lacks.
The old wd driver is still present in 4.0, it just isn't the default.
You can build a custom kernel with it rather than the new ata drivers and
you are able to get all of the other benefits of 4.0 despite your buggy
CMD640 controller
It seems Thomas Veldhouse wrote:
Are there any plans to support the buggy CMD640 interface in the future
now that 4.0-RELEASE has come and gone? I have a box that is running 3.4
happily, and it has this interface. I really would like the chance to use
some of the 4.0 features, but I can not
And I have three machines which I was trying to use for testing -current and my
firewall. These machines all have either a CMD640 or an RZ100 controller on the
motherboard. (They seemed to be popular with the early Pentium machines.) The
controllers seem reliable enough to use for extended
On Tue, 14 Mar 2000, Soren Schmidt wrote:
It worked until the latest newbus changes, I'm looking at it, but havn't
found anything obvious yet.
But seriously you want to get another ATA interface, the CMD640 is
_broken_ and no software can help that, you are playing russian
roulette with
Hi folks,
I am having problems again with the ata drivers on my old Pentium 66
system.
With a kernel built from sources cvsupped today, I get he following
messages when booting:
...
pcib0: Host to PCI bridge on motherboard
pci0: PCI bus on pcib0
atapci0: RZ 100? ATA controller !WARNING! buggy
On Tue, 15 Feb 2000, Thomas T. Veldhouse wrote:
Soren, do you have any idea what might be the problem? Is there anything I
can do to give you more information? I have 3.4-STABLE installed on the box
presently - it is serving as my gateway/firewall, so it really can't afford
much downtime
At 11:38 AM 2/15/00 -0600, Thomas Veldhouse wrote:
Great. Well, I am down too! I don't see any mention of this in any of
the newsgroups (via Yahoo). I can not find a single reference. I don't
remember seeing such a thing stated either.
Look through the mailing lists on www.dejanews.com. Do
in the kernel config. Is there an option for the new ATA
drivers? If so, are they in the GENERIC kernel (for use with boot disks)?
I didn't see any mention of the workaround while booting the install disks
(kern.flp and mfsroot.flp).
Tom Veldhouse
[EMAIL PROTECTED]
On Tue, 15 Feb 2000, Ilmar S
] work around for. In the old wd drivers, you had to declare the
work around in the kernel config. Is there an option for the new ATA
drivers? If so, are they in the GENERIC kernel (for use with boot disks)?
I didn't see any mention of the workaround while booting the install disks
(kern.flp
, I might look at the IDE contoller. There is a
known bug in CMD640(B) that the old drivers and the Linux drivers have a
[verbose] work around for. In the old wd drivers, you had to declare the
work around in the kernel config. Is there an option for the new ATA
drivers? If so
I have an older Pentium box that has a MATSHITA CR-581/1.04 (as seen from
3.4-STABLE) CD drive (4x) on the fourth IDE interface (second IDE controller
slave). The IDE controller is the buggy CMD640B. I have been trying to
install 4.0-CURRENT-2214 to no avail. I get the following errors (I
"Dave J. Boers" wrote:
On Tue, Dec 21, 1999 at 11:22:12PM +0100, Thierry Herbelot wrote:
Let's start a thread on the BP6 ? (the release of the board was
carefully synchronized with stable SMP releases of FreeBSD : kudos to
the FreeBSD release engineering team ;-))
I second that!
I know your talking SMP but thought you'd like to know some temps for UP
systems as well...
I have a Celeron 300a that I overclock to 464 MHz (100 MHz FSB + extra
turbo frequency boost) running at 2.1 v and it runs at about 30 degrees
celcius when idle and at 52 degrees when running setiathome
[snip]
What is the rating of your Power supply ?
Not quite high enough :-(
It's a 300 Watt power supply.
Hehe - I'm running dual 540's (2.2V) on a BP6 (I'm guessing around 30 Watts
per CPU), extra case fan, big CPU fans, CD, TNT and an IDE drive (I've had
three hooked up once) - on a 235W
On Tue, Dec 21, 1999 at 11:22:12PM +0100, Thierry Herbelot wrote:
Let's start a thread on the BP6 ? (the release of the board was
carefully synchronized with stable SMP releases of FreeBSD : kudos to
the FreeBSD release engineering team ;-))
I second that! Running -current since October and
On Sat, Dec 18, 1999 at 07:27:16AM +0100, Thierry Herbelot wrote:
Do you boot from the UDMA66 drive ?
Yes. Bios boot sequence is EXT,C,A; where EXT is set to UDMA66, not SCSI.
The SCSI disk is a 4.3 Gb WD Enterprise on an Adaptec 2940AU board.
What is your BIOS revision ?
Award Bios v.
Hi all,
I just wanted to let you know that I enabled UDMA66 (by plugging in an 80
conductor cable) on my WDC AC418000D today. The mainboard is an ABit BP6
with builtin Highpoint HPT366 ATA controller.
The system works very nicely. I did some heavy testing in single user mode
by moving several
On 18-Dec-99 Dave J. Boers wrote:
The system works very nicely. I did some heavy testing in single user mode
by moving several 300 Mb files around between the IDE disk and my other
SCSI disk (which got me a sustained transfer rate of over 10 Mb/sec). Then
I made world. Everything works great
"Dave J. Boers" wrote:
Hi all,
I just wanted to let you know that I enabled UDMA66 (by plugging in an 80
conductor cable) on my WDC AC418000D today. The mainboard is an ABit BP6
with builtin Highpoint HPT366 ATA controller.
The system works very nicely. I did some heavy testing in
Hello,
I have noticed over time that many people are test driving the new
ATA
Drivers. I attempted to do it a while back but I couldn't boot because of
the device name changes. I did not know what the new device names were.
Anyway - is there a simple HOWTO for using these drivers
It seems Thomas Veldhouse wrote:
Hello,
I have noticed over time that many people are test driving the new
ATA
Drivers. I attempted to do it a while back but I couldn't boot because of
the device name changes. I did not know what the new device names were.
Anyway
On Tue, 21 Sep 1999, David Krinsky wrote:
On Mon, Sep 20, 1999 at 12:05:38AM +, Gary Hampton ([EMAIL PROTECTED])
wrote:
On Mon, 20 Sep 1999, Adam Strohl wrote:
Remake your acd device, I think you may need a patch to do it. I had the
same problem, until I rm-ed the device and
On Mon, Sep 20, 1999 at 12:05:38AM +, Gary Hampton ([EMAIL PROTECTED])
wrote:
On Mon, 20 Sep 1999, Adam Strohl wrote:
Remake your acd device, I think you may need a patch to do it. I had the
same problem, until I rm-ed the device and remade it.
- ( Adam Strohl
I have been trying to get the ata drivers to work on my system for a
a while now but can't seem to mount my cdrom drives. This is what I get on
boot up:
ata-pci0: Intel PIIX4 IDE controller at device 7.1 on pci0
ata-pci0: Busmastering DMA supported
atapi: piomode=4, dmamode=2, udmamode=-1
ata0
Hampton wrote:
I have been trying to get the ata drivers to work on my system for a
a while now but can't seem to mount my cdrom drives. This is what I get on
boot up:
ata-pci0: Intel PIIX4 IDE controller at device 7.1 on pci0
ata-pci0: Busmastering DMA supported
atapi: piomode=4
It seems Stephen Hocking-Senior Programmer PGS Tensor Perth wrote:
Soren, I did a bit of experimenting with my CVS archive and found that
version
1.8 of ata-all.c was the last one that worked on my problem box. 1.9 spewed
out errors about unexpected interrupts whilst probing and eventually
Soren, I did a bit of experimenting with my CVS archive and found that version
1.8 of ata-all.c was the last one that worked on my problem box. 1.9 spewed
out errors about unexpected interrupts whilst probing and eventually hung, and
1.10 gave the unable to mount wd0s2a errors we all love.
I have been unable to use my Ultra DMA ATAPI CD-ROM since version 4
of Soren's ATAPI driver.
Version 4 worked fine but since then (since at least version 6
I didn't try version 5) The system wont boot if I have my secondary
IDE controller enabled.
The system never completes its kernel
On Thu, 29 Apr 1999, Soren Schmidt wrote:
It seems Brian Feldman wrote:
Ever going to help with my atapi-fd problems? I found examples of the
corruptions, including lots of NULLs...
Well, so long as I cannot get my hands on the problem, its real hard
to solve it. I'm trying to get ahold
It seems Andrzej Bialecki wrote:
Ever going to help with my atapi-fd problems? I found examples of the
corruptions, including lots of NULLs...
Well, so long as I cannot get my hands on the problem, its real hard
to solve it. I'm trying to get ahold of the same LS120 drive here
but so
It seems Soren Schmidt wrote:
As I said before, I can make some tests, but unfortunately my machine
doesn't want to mount disks at all with the new ATA code... Please take a
look at the message I sent about a week ago.
Unfortunately they dont tell me much :(
I'll have to rearrange
(trimmed spaghetti CC: list...)
On Fri, 30 Apr 1999, Soren Schmidt wrote:
Unfortunately they dont tell me much :(
I'll have to rearrange some disks here and try to make some new installs
see if I can get the problem to appear then..
Is there any info I can dig out for you? Some useful
It seems Brian Feldman wrote:
Ever going to help with my atapi-fd problems? I found examples of the
corruptions, including lots of NULLs...
Well, so long as I cannot get my hands on the problem, its real hard
to solve it. I'm trying to get ahold of the same LS120 drive here
but so far I havn't
On Thu, 29 Apr 1999, Soren Schmidt wrote:
It seems Brian Feldman wrote:
Ever going to help with my atapi-fd problems? I found examples of the
corruptions, including lots of NULLs...
Well, so long as I cannot get my hands on the problem, its real hard
to solve it. I'm trying to get ahold
Hi,
In the great new ATA device driver framework (thanks Soren) there seems
to be a problem reported before by Stephen:
Stephen Hocking-Senior Programmer PGS Tensor Perth wrote:
On my machine, a kernel newer than one built on the 22nd will not complete
booting, panicing about not being
Hi,
I have three hosts with -current, all with the new ATA in function.
Booting the same kernel produces different results on all of them wrt
root file system mounting:
- one reports 'changing root device to wd0s3a'
- one reports 'changing root device to wd0s3a' followed by 'changing
root
Soren Schmidt wrote:
Hmm, could you mail me the output of fdisk disklabel from those tree
machines, with indication of how they behave ??
I'm unable to reproduce those errors here, but this might bring the
details I need to figure it out...
Certainly. First the working machine (reports
On Wed, 28 Apr 1999, Soren Schmidt wrote:
Hi,
I have three hosts with -current, all with the new ATA in function.
Booting the same kernel produces different results on all of them wrt
root file system mounting:
- one reports 'changing root device to wd0s3a'
- one reports 'changing
45 matches
Mail list logo
