Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 22 Mar 2005 12:43:30 -0600
From:      Vulpes Velox <v.velox@vvelox.net>
To:        Harry Coin <harrycoin@qconline.com>
Cc:        freebsd-current@freebsd.org
Subject:   Re: ATAPICAM?
Message-ID:  <20050322124330.105d3811@vixen42.local.lan>
In-Reply-To: <4.3.2.7.2.20050322071722.038787d0@mail.qconline.com>
References:  <20050322120017.6E90816A4EC@hub.freebsd.org> <4.3.2.7.2.20050322071722.038787d0@mail.qconline.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 22 Mar 2005 07:23:44 -0600
Harry Coin <harrycoin@qconline.com> wrote:

> Gary Jennejohn <garyj@jennejohn.org wrote:
> 
>  >What's with ATAPICAM?
> 
> I'm not sure what the issue is with the new ata drivers, but I know 
> Atapicam in the context of USB memory chip solid state disk readers
> and an  ata DVD burner hangs the bootup process with an interrupt
> storm right after  the hard disks are enumerated and just before the
> SMP message announcing  the launch of the second processor would
> have been displayed.
> 
> I hope the new attention due to the updated ata drivers fixes it, as
> the  system just hangs.  It's an unusable showstopper on all 5.x. 
> Same system  works with the various Redmond, WA based commercial
> products.
> 
> Comment atapicam out of the kernel, all is well.

Works fine with my DVD burner here. There is a issue with some
chipsets, but not all. Last I checked, many months ago, it acted wierd
on my promise card. No problems with it and my nforce chipset.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050322124330.105d3811>