Re: AIC7XXX + v2.4.18 problems?

[Doug Ledford]

On Wed, Jun 19, 2002 at 11:49:25PM +0200, J.A. Magallon wrote:
> You are hangin things on the 50pin connector, which is SE, so you could never
> get 160Mb/s (LVD, transmit on up and down), you could at most go at 80Mb/s.

80MB/s is also LVD.  The fastest you can go on a SE narrow chain is in 
fact 20MB/s.

> >
> >Channel A Target 0 Negotiation Settings
> >        User: 40.000MB/s transfers (40.000MHz DT, offset 255)
> >        Goal: 20.000MB/s transfers (20.000MHz, offset 31)
> >        Curr: 20.000MB/s transfers (20.000MHz, offset 31)
> 
> Hardware thinks the disk just can do Goal=20Mb/s. Why ?

The 29160 card detects which cable a device is hooked to and the driver 
then sets the maximum allowed speed according to that.  When you plug a 
drive into a SE cable, the driver knows it and sets the maximum speed to 
SE speeds.

> It says nothing about 16 bits... Are you forcing it to narrow
> with a jumper ??

16bit is off in the BIOS settings, so it wouldn't get used regardless.

> >Channel A Target 2 Negotiation Settings
> >        User: 160.000MB/s transfers (80.000MHz DT, offset 255, 16bit)
> >        Goal: 20.000MB/s transfers (20.000MHz, offset 15)
> >        Curr: 20.000MB/s transfers (20.000MHz, offset 15)
> 
> It recognizes the drive can do wide, but as the first device in the
> chain forced narrow, goal is narrow.

No, the order of devices has no impact on this.  No device has any impact 
on any other device's speed settings unless they are both connected to the 
same physical cable and one of the devices is forcing a cable that *could* 
be in LVD mode into SE mode instead.  Short of that, all device 
negotiations are 100% independant of each other.

-- 
  Doug Ledford <[e-mail]>     919-754-3700 x44233
         Red Hat, Inc. 
         1801 Varsity Dr.
         Raleigh, NC 27606