On Tue, 3 Jun 2003, Shaun Jurrens wrote:
> I hate to say it, but I've had these for months starting at 4.6-stable
> and continuing up to at least the latest 4.7-RRELEASE-p* . I have one
> dual -current box that has exibited the same behaviour as well.
FWIW, I had similar issues (similar messages,
On Thu, Jun 05, 2003 at 10:54:14AM -0600, Justin T. Gibbs wrote:
#> After that the box didn't find 3 of the 5 fxp nic's until a new
#> >boot and a cleared ESCD. Not sure why an fxp card should bitch
#> >about SCB's anyway.
#>
#> Perhaps because fxp devices have SCBs too? Not the sam
On Thu, 5 Jun 2003, Shaun Jurrens wrote:
> On Wed, Jun 04, 2003 at 06:32:46PM +0200, Palle Girgensohn wrote:
> #> Hi Shaun,
> #>
> #> Thanks for the input! Glad to hear I'm not the only one
> #>
> #> In my case, both the SCSI and NIC are integrated on the motherboard, so I
> #> cannot really move t
After that the box didn't find 3 of the 5 fxp nic's until a new
> boot and a cleared ESCD. Not sure why an fxp card should bitch
> about SCB's anyway.
Perhaps because fxp devices have SCBs too? Not the same SCBs that
the Adaptec SCSI controllers have, but a different data str
On Wed, Jun 04, 2003 at 06:32:46PM +0200, Palle Girgensohn wrote:
#> Hi Shaun,
#>
#> Thanks for the input! Glad to hear I'm not the only one
#>
#> In my case, both the SCSI and NIC are integrated on the motherboard, so I
#> cannot really move them around... :)
#>
#> Also, as I mentioned, I trie
Hi Shaun,
Thanks for the input! Glad to hear I'm not the only one
In my case, both the SCSI and NIC are integrated on the motherboard, so I
cannot really move them around... :)
Also, as I mentioned, I tried a de0 (PCI card, not onboard, and it
literally stopped the machine). Is the de0 driver
I hate to say it, but I've had these for months starting at 4.6-stable
and continuing up to at least the latest 4.7-RRELEASE-p* . I have one
dual -current box that has exibited the same behaviour as well.
The boxes work just fine with the xl0 driver. Lots of different motherboards
and processors
