Onstream DI-30 not responding 2.6
Hi
I'm trying to use my Onstream DI-30 (IDE) tape device with Kernel 2.6.0-test1. When trying to access the drive using the old 2.2 kernels and 2.4 these commands worked fine
bash-2.05# mt -f /dev/nht0 status/dev/nht0: No such device
bash-2.05# mt -f /dev/ht0 status/dev/ht0: No such device
bash-2.05# mt -f /dev/hdd status/dev/hdd: No such device or address
bash-2.05# mt -f /dev/hdc status/dev/hdc: No such device or address
While they now are showing ugly errors.
This is a part of the boot log
VP_IDE: IDE controller at PCI slot 0000:00:07.1VP_IDE: chipset revision 16VP_IDE: not 100% native mode: will probe irqs later
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xxVP_IDE: VIA vt82c686a (rev 22) IDE UDMA66 controller on pci0000:00:07.1
ide0: BM-DMA at 0xc000-0xc007, BIOS settings: hda:DMA, hdb:DMA
ide1: BM-DMA at 0xc008-0xc00f, BIOS settings: hdc:pio, hdd:DMA
hda: WDC WD205BA, ATA DISK drive
anticipatory scheduling elevator
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hdd: OnStream DI-30, ATAPI TAPE drive
Thanks in advance for any tips on a solution for this problem.
Stef
Hi,
ide-tape driver is broken right now in 2.6.
Config option for it is commented out because
it even doesn't compile (easy to fix).
I can help a bit if somebody wants to fix this driver. --
Bartlomiej
Quoted 36 lines · Stef van der Made
Hi
I'm trying to use my Onstream DI-30 (IDE) tape device with Kernel 2.6.0-test1. When trying to access the drive using the old 2.2 kernels and 2.4 these commands worked fine
bash-2.05# mt -f
/dev/nht0status/dev/nht0: No such device
bash-2.05# mt -f/dev/ht0status/dev/ht0: No such device
bash-2.05# mt -f/dev/hddstatus/dev/hdd: No such device or address
bash-2.05# mt -f/dev/hdcstatus/dev/hdc: No such device or addressWhile they now are showing ugly errors.
This is a part of the boot log
VP_IDE: IDE controller at PCI slot 0000:00:07.1VP_IDE: chipset revision 16VP_IDE: not 100% native mode: will probe irqs later
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xxVP_IDE: VIA vt82c686a (rev 22) IDE UDMA66 controller on pci0000:00:07.1ide0: BM-DMA at 0xc000-0xc007, BIOS settings: hda:DMA, hdb:DMA ide1: BM-DMA at 0xc008-0xc00f, BIOS settings: hdc:pio, hdd:DMAhda: WDC WD205BA, ATA DISK drive
anticipatory scheduling elevator
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hdd: OnStream DI-30, ATAPI TAPE driveThanks in advance for any tips on a solution for this problem.
Stef
Would help but my DI-30 is deadlocked and will not function regardless :-( It is nothing but a paperweight now.
Andre Hedrick
LAD Storage Consulting Group
Quoted 55 lines · Bartlomiej Zolnierkiewicz
Hi,
ide-tape driver is broken right now in 2.6.
Config option for it is commented out because
it even doesn't compile (easy to fix).I can help a bit if somebody wants to fix this driver. --
BartlomiejQuoted 33 lines · Stef van der Made
Hi
I'm trying to use my Onstream DI-30 (IDE) tape device with Kernel 2.6.0-test1. When trying to access the drive using the old 2.2 kernels and 2.4 these commands worked fine
bash-2.05# mt -f
/dev/nht0status/dev/nht0: No such device
bash-2.05# mt -f/dev/ht0status/dev/ht0: No such device
bash-2.05# mt -f/dev/hddstatus/dev/hdd: No such device or address
bash-2.05# mt -f/dev/hdcstatus/dev/hdc: No such device or addressWhile they now are showing ugly errors.
This is a part of the boot log
VP_IDE: IDE controller at PCI slot 0000:00:07.1VP_IDE: chipset revision 16VP_IDE: not 100% native mode: will probe irqs later
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xxVP_IDE: VIA vt82c686a (rev 22) IDE UDMA66 controller on pci0000:00:07.1ide0: BM-DMA at 0xc000-0xc007, BIOS settings: hda:DMA, hdb:DMA ide1: BM-DMA at 0xc008-0xc00f, BIOS settings: hdc:pio, hdd:DMAhda: WDC WD205BA, ATA DISK drive
anticipatory scheduling elevator
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hdd: OnStream DI-30, ATAPI TAPE driveQuoted 3 lines
Thanks in advance for any tips on a solution for this problem.
Stef
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/