On Wednesday 14 March 2007, Stanislav Brabec wrote:
Bartlomiej Zolnierkiewicz wrote:
On Wednesday 14 March 2007, Stanislav Brabec wrote:
Albert Lee wrote:
Tejun Heo wrote:
Hmmm... weird. Your drive bears the same model name as Stanislav's.
I
don't think the low
Jeff Garzik wrote:
Tejun Heo wrote:
[libata]
And, as the device requires custom high level driver, libata fails
miserably. Would it be worth to try support these devices? Or are
they just too outdated to put the effort in?
What SCSI peripheral device type does it report, when booted
Tejun Heo wrote:
Hmmm... weird. Your drive bears the same model name as Stanislav's. I
don't think the low level driver is causing the difference. They both
use the standard libata HSM implementation. Any ideas? Stanislav, can
you try to connect that zip drive to another IDE
Albert Lee wrote:
Tejun Heo wrote:
Hmmm... weird. Your drive bears the same model name as Stanislav's. I
don't think the low level driver is causing the difference. They both
use the standard libata HSM implementation. Any ideas? Stanislav, can
you try to connect that zip drive to
Stanislav Brabec wrote:
Looking at the syslog in Novell bug 232086 in detail, following line may
indicate hardware failure:
usb 5-1: string descriptor 0 read error: -22
I don't think usb 5-1 is related to ide-floppy problem.
My drive is a slave on bus, where master is a modern Seagate
Tejun wrote:
If that's the case, libata should work too as long as the HSM problem is
fixed.
Really? I didn't notice when libata gained ATAPI-disk support.
Are you *sure* about that??
Cool.
-
To unsubscribe from this list: send the line unsubscribe linux-ide in
the body of a message to
On Wednesday 14 March 2007, Stanislav Brabec wrote:
Albert Lee wrote:
Tejun Heo wrote:
Hmmm... weird. Your drive bears the same model name as Stanislav's. I
don't think the low level driver is causing the difference. They both
use the standard libata HSM implementation. Any
Bartlomiej Zolnierkiewicz wrote:
My drive is a slave on bus, where master is a modern Seagate ST3160812A.
On my system I see two regressions:
- One between year 2002 kernels and SuSE Linux 10.0:
Delay with packet command initiated yet DRQ isn't asserted before
first read access, then the
Mark Lord wrote:
Tejun wrote:
If that's the case, libata should work too as long as the HSM problem is
fixed.
Really? I didn't notice when libata gained ATAPI-disk support.
Are you *sure* about that??
Not sure sure but almost sure. :-) What ide-scsi does is borrowing
SCSI mid and high
Mark Lord wrote:
Tejun Heo wrote:
Yeap, agreed but I think getting more info on the libata HSM violation
can help diagnosing ide problem too. Anyways, Stanislav, can you bisect
as Bartlomiej requested?
Tejun, do you have a Zip100 (ATAPI) drive to play with there?
Nope. Do you happen to
Stanislav Brabec wrote:
Bartlomiej Zolnierkiewicz wrote:
On Wednesday 14 March 2007, Stanislav Brabec wrote:
Albert Lee wrote:
Tejun Heo wrote:
Hmmm... weird. Your drive bears the same model name as Stanislav's. I
don't think the low level driver is causing the difference. They both
use
Hi,
On Monday 12 March 2007, Sergei Shtylyov wrote:
Hello.
Tejun Heo wrote:
Stanislav Brabec reported that IOMEGA IDE ZIP drive doesn't work with
recent kernels. Low level driver is via82cxxx. Relevant part of
2.6.20.1 boot message follows.
VP_IDE: IDE controller at PCI slot
Jeff Garzik wrote:
Tejun Heo wrote:
[libata]
And, as the device requires custom high level driver, libata fails
miserably. Would it be worth to try support these devices? Or are
they just too outdated to put the effort in?
What SCSI peripheral device type does it report, when booted
It seems ide-floppy needs some special handlings in interrupt handling
too like delaying data transfer by several ticks after device indicates
readiness. Apart from separate high level driver, we might have to
modify libata HSM implementation if we're gonna support these devices.
The data
Alan Cox wrote:
It seems ide-floppy needs some special handlings in interrupt handling
too like delaying data transfer by several ticks after device indicates
readiness. Apart from separate high level driver, we might have to
modify libata HSM implementation if we're gonna support these
Hello, all.
Stanislav Brabec reported that IOMEGA IDE ZIP drive doesn't work with
recent kernels. Low level driver is via82cxxx. Relevant part of
2.6.20.1 boot message follows.
VP_IDE: IDE controller at PCI slot :00:11.1
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will
Hello.
Tejun Heo wrote:
Stanislav Brabec reported that IOMEGA IDE ZIP drive doesn't work with
recent kernels. Low level driver is via82cxxx. Relevant part of
2.6.20.1 boot message follows.
VP_IDE: IDE controller at PCI slot :00:11.1
VP_IDE: chipset revision 6
VP_IDE: not 100%
Tejun Heo wrote:
[libata]
And, as the device requires custom high level driver, libata fails
miserably. Would it be worth to try support these devices? Or are
they just too outdated to put the effort in?
What SCSI peripheral device type does it report, when booted under libata?
Jeff
18 matches
Mail list logo
