Hello folks,
following up to this bugreport as I experience similar problems...
I have an ASUS P2B-S mainboard featuring an Adaptec AIC-7890 Ultra2
chipset with a single device connected, a TEAC CD-R55S cd-writer,
both working reliably ever since I bought them in 1998. The transport
setting are a
James Bottomley <[EMAIL PROTECTED]> wrote:
> OK, try the attached. If it works out, I'll soak it in -mm for
> a while and then try to put it in as a bug fix for 2.6.15.
This works for me. The DV write tests are skipped and the system boots
cleanly. The boot messages are the same as when we ifde
James Bottomley wrote:
On Sun, 2005-11-20 at 21:21 -0500, Graham Knap wrote:
Sure enough, the kernel now boots. I'll attach the "dmesg" output here.
Do you guys have a "final" patch in mind?
Let me know if there are other tests you'd like me to run. Now that I
know how to do this, I should be
On Sun, 2005-11-20 at 21:21 -0500, Graham Knap wrote:
> Sure enough, the kernel now boots. I'll attach the "dmesg" output here.
>
> Do you guys have a "final" patch in mind?
>
> Let me know if there are other tests you'd like me to run. Now that I
> know how to do this, I should be able to turn a
Processing commands for [EMAIL PROTECTED]:
> reassign 338089 linux-2.6
Bug#338089: New aic7xxx driver fails spectacularly on 2940UW
Warning: Unknown package 'linux-image-2.6.14-1-686'
Bug reassigned from package `linux-image-2.6.14-1-686' to `linux-2.6'.
> --
Stoppin
On Mon, Nov 14, 2005 at 07:45:20PM -0500, Graham Knap wrote:
> James Bottomley <[EMAIL PROTECTED]> wrote:
> > Can you try with the attached patch, which will force DV to ignore
> > the echo buffer write tests?
>
> I'll certainly try.
>
> The kernel I was using was a prebuilt Debian kernel. I'm no
James Bottomley <[EMAIL PROTECTED]> wrote:
> Can you try with the attached patch, which will force DV to ignore
> the echo buffer write tests?
I'll certainly try.
The kernel I was using was a prebuilt Debian kernel. I'm not sure how
to rebuild it from source. Horms, if you could point me in the r
On Sun, 2005-11-13 at 14:42 -0500, Doug Ledford wrote:
> The device is on a non-LVD bus. Certain devices were created back when
> the spec still stated that using PPR negotiation messages on a non-LVD
> bus was a no-no. As the echo buffer was an addition to support DV, and
> originally DV wasn
James Bottomley wrote:
On Sun, 2005-11-13 at 13:03 -0500, Graham Knap wrote:
Doug Ledford <[EMAIL PROTECTED]> wrote:
You already said it didn't help with the problem,
I meant that I don't think I successfully disabled DV, because the boot
messages were *identical*, except for the line where
On Sun, 2005-11-13 at 13:03 -0500, Graham Knap wrote:
> Doug Ledford <[EMAIL PROTECTED]> wrote:
> > You already said it didn't help with the problem,
>
> I meant that I don't think I successfully disabled DV, because the boot
> messages were *identical*, except for the line where the kernel shows
Doug Ledford <[EMAIL PROTECTED]> wrote:
> If the drive is unaccessible after the DV failure, even on a warm
> reboot (which includes a SCSI bus reset), then the drive is flat
> hung. Something done in the current code is breaking it.
Ah. I had wondered if that was possible.
> Can you get a boot
On Sun, 2005-11-13 at 12:41 -0500, Doug Ledford wrote:
> If the drive is unaccessible after the DV failure, even on a warm reboot
> (which includes a SCSI bus reset), then the drive is flat hung.
> Something done in the current code is breaking it. Can you get a boot
> with DV turned off and ca
Graham Knap wrote:
James Bottomley <[EMAIL PROTECTED]> wrote:
My best guess would be that the bus is slightly marginal. The
aic7xxx drivers are notoriously sensitive to bus problems. Could you
try lowering the bus speed to 10MHz in the aic7xxx bios and see if
that helps?
Sure. I changed th
James Bottomley <[EMAIL PROTECTED]> wrote:
> My best guess would be that the bus is slightly marginal. The
> aic7xxx drivers are notoriously sensitive to bus problems. Could you
> try lowering the bus speed to 10MHz in the aic7xxx bios and see if
> that helps?
Sure. I changed the device to 20MBy
On Tue, 2005-11-08 at 20:47 -0500, Graham Knap wrote:
> Target 0 Negotiation Settings
> User: 40.000MB/s transfers (20.000MHz, offset 127, 16bit)
> Goal: 40.000MB/s transfers (20.000MHz, offset 8, 16bit)
> Curr: 40.000MB/s transfers (20.000MHz, offset 8, 16bit)
That's a bit
Graham Knap <[EMAIL PROTECTED]> wrote:
> Recent versions of the aic7xxx driver will not boot on my secondary
> PC. The 2.6.8 kernel shipped with sarge works, but neither the 2.6.12
> kernel in testing nor the 2.6.14 kernel in unstable will boot.
> This is an older system:
> Asus P2L-B, Celeron 500
On Tue, 2005-11-08 at 12:31 +0900, Horms wrote:
> On Mon, Nov 07, 2005 at 09:45:23PM -0500, Graham Knap wrote:
> > Package: linux-image-2.6.14-1-686
> > Version: 2.6.14-2
> >
> > Recent versions of the aic7xxx driver will not boot on my secondary PC.
> > The 2.6.8 kernel shipped with sarge works p
On Mon, Nov 07, 2005 at 09:45:23PM -0500, Graham Knap wrote:
> Package: linux-image-2.6.14-1-686
> Version: 2.6.14-2
>
> Recent versions of the aic7xxx driver will not boot on my secondary PC.
> The 2.6.8 kernel shipped with sarge works perfectly, but neither the
> 2.6.12 kernel in testing nor the
Package: linux-image-2.6.14-1-686
Version: 2.6.14-2
Recent versions of the aic7xxx driver will not boot on my secondary PC.
The 2.6.8 kernel shipped with sarge works perfectly, but neither the
2.6.12 kernel in testing nor the 2.6.14 kernel in unstable will boot.
This is an older system:
Asus P2L
19 matches
Mail list logo
