Re: Iomega Zip drive USB
Michel Court wrote: Bonjour, je viens d'acquérir un Zip Drive 250 usb autoalimenté et je souhaiterais le mettre en place sur une debian Woody. J'ai compilé un noyau avec le support USB et le supprot de /proc. moi aussi j'ai un zip 250 usb autoalimenté ! et il marche bien sur ma Sarge et ma Woody ! Alors pour le faire marcher, il m'a fallut ajouter le module 'usb-storage' et 'usb-uhci' chez toi je pense que ce seré plutot 'uhci' vu ton dmesg donc moi je te conseil de faire un : $ lsmod et regarde si les modules 'uhci' et 'usb-storage' sont chargé. si tu ne les a pa : $ modprobe uhci # ajoute le module uhci $ modprobe usb-storage # ajoute le module usb-storage retape pour voir si tou sé bien passé : $ lsmod Normalement en ajoutant le module 'usb-storage' ton zip doit se mettre en route ! (enfinje crois ! ;-)) il te reste plus qu'a le monter : $ mount -t vfat /dev/sda4 /mnt/zip voila et maintenant tu pe voir le contenu de ton zip dans le dossier /mnt/zip (il fo bien sur que celui soit créer : $ mkdir /mnt/zip) voila j'espere pour toi que ca marchera et pi si ca ne marche pa n'hesite pas à renvoyer tes erreurs ! ciao !! Mathieu Il semblerait que le noyau reconnaisse le drive puisque un extrait de dmesg me donne : uhci.c: bf80: wakeup_hc uhci.c: root-hub INT complete: port1: 93 port2: 80 data: 2 hub.c: port 1 connection change hub.c: port 1, portstatus 101, change 1, 12 Mb/s hub.c: port 1, portstatus 103, change 0, 12 Mb/s hub.c: USB new device connect on bus1/1, assigned device number 2 usb.c: kmalloc IF dad4a280, numif 1 usb.c: new device strings: Mfr=1, Product=2, SerialNumber=5 usb.c: USB device number 2 default language ID 0x409 Manufacturer: Iomega Product: USB Zip 250 SerialNumber: 0032484D89050828 usb.c: unhandled interfaces on device usb.c: USB device 2 (vend/prod 0x59b/0x32) is not claimed by any active driver. Length = 18 DescriptorType = 01 USB version = 1.10 Vendor:Product = 059b:0032 MaxPacketSize0 = 64 NumConfigurations = 1 Device version = 4.00 Device Class:SubClass:Protocol = 00:00:00 Per-interface classes Configuration: bLength =9 bDescriptorType = 02 wTotalLength= 0027 bNumInterfaces = 01 bConfigurationValue = 01 iConfiguration = 03 bmAttributes= 80 MaxPower= 498mA Interface: 0 Alternate Setting: 0 bLength =9 bDescriptorType = 04 bInterfaceNumber= 00 bAlternateSetting = 00 bNumEndpoints = 03 bInterface Class:SubClass:Protocol = 08:06:50 iInterface = 04 Endpoint: bLength =7 bDescriptorType = 05 bEndpointAddress= 01 (out) bmAttributes= 02 (Bulk) wMaxPacketSize = 0040 bInterval = 00 Endpoint: bLength =7 bDescriptorType = 05 bEndpointAddress= 82 (in) bmAttributes= 02 (Bulk) wMaxPacketSize = 0040 bInterval = 00 Endpoint: bLength =7 bDescriptorType = 05 bEndpointAddress= 83 (in) bmAttributes= 03 (Interrupt) wMaxPacketSize = 0002 bInterval = 20 Mais je n'ai rien dans /proc/bus/usb ! Quelqun a-t-il deja tenté cette manip ?
Re: Iomega zip drive
On Tue, Mar 16, 1999 at 08:29:38AM -0800, Alessandro Z wrote: I'm trying to have my Iomega zip drive working under Linux. I previously successfully compiled the kernel to support the zip drive with a SuSE distro, now I'm trying with Debian and Red Hat on different PC. In both cases there's something wrong. After compiling the kernel including: -- scsi support=yes scsi disk support=yes Iomega Zip support as a module parallel printer as module and running lilo to use the new kernel I get an error when trying to install ppa: If your zip drive is quite new, then Iomega have started using a new protocol, so a different driver is needed. It's in Linux 2.2; I don't know if you can get it for 2.0. Hamish -- Hamish Moffatt VK3TYD [EMAIL PROTECTED], [EMAIL PROTECTED] Latest Debian packages at ftp://ftp.rising.com.au/pub/hamish. PGP#EFA6B9D5 CCs of replies from mailing lists are welcome. http://hamish.home.ml.org
Re: Iomega zip drive
Alessandro Z wrote: After compiling the kernel including: -- scsi support=yes scsi disk support=yes Iomega Zip support as a module parallel printer as module and running lilo to use the new kernel I get an error when trying to install ppa: What about rebooting after running lilo? insmod ppa I also get error messages with insmod because ppa depends on modules that could not be installed in the kernel. The file /lib/modules/2.2.1/modules.dep says that ppa depends on scsi_mod, and parport. But when I modprobe ppa I get no error messages if the ZIP drive is connected. Now it is not here, and so I get: /lib/modules/2.2.1/scsi/ppa.o: init_module: Device or resource busy parport: Device or resource busy -- PPA: unable to initialise controller at 0x378, error 1 scsi: 0 hosts /lib/modules/2.0.xx/scsi/ppa.o: init_module: Device or resource busy I see that you use kernel 2.0.xx. I didn't know that kernel in the 2.0 series supported ZIP drives. I think that my last 2.0.35 didn't included ZIP drives. Nevertheless, I include below some of the critical CONFIG's in file /usr/src/kernel-source-2.2.1/.config after running make menuconfig for paralel port ZIP drive, in case you want to compile kernel 2.2.1: # Loadable module support CONFIG_MODULES=y CONFIG_MODVERSIONS=y CONFIG_KMOD=y # General setup CONFIG_PARPORT=m CONFIG_PARPORT_PC=m # CONFIG_PARPORT_OTHER is not set # Plug and Play support CONFIG_PNP=y CONFIG_PNP_PARPORT=m # Additional Block Devices CONFIG_PARIDE_PARPORT=m # CONFIG_PARIDE is not set # SCSI support CONFIG_SCSI=m # SCSI support type (disk, tape, CD-ROM) CONFIG_BLK_DEV_SD=m # SCSI low-level drivers CONFIG_SCSI_PPA=m # CONFIG_SCSI_IMM is not set CONFIG_SCSI_IZIP_EPP16=y # CONFIG_SCSI_IZIP_SLOW_CTR is not set # Character devices CONFIG_PRINTER=m CONFIG_PRINTER_READBACK=y -- Conrado Badenas (Assistant Lecturer) Department of Thermodynamics. University of Valencia c/. Doctor Moliner, 50 | e-m: [EMAIL PROTECTED] 46100 Burjassot (Valencia) | Phn: +34-63864350 SPAIN| Fax: +34-63983385
Re: Iomega ZIP Drive(100Meg)
On Wed, Jul 01, 1998 at 11:38:06AM -0700, Syed Huq wrote: I have a Iomega ZIP Drive(100Meg, parallel port). How do I make Linux see all the files there ? Do I need to mount that drive somehow ? Can you tell me the commands to use ? This really belongs in debian-user, so the To: header has been altered accordingly. You have to mount the thing, yes. You need a kernel with the zip parallel module in it. Agh, where's a 2.0.x source tree when I need one? (I run 2.1.x myself) The driver is under the SCSI options, it's the ppa driver. According to the old unmaintained Zip howto, you couldn't have the ppa driver and the parport driver installed at the same time. I'm certain this has changed now, so you'll have to play with it. Note that the Zip disks are formatted with one partition on /dev/sda4 (assuming you don't have another SCSI card else you'd be using it now and you'd not be asking about the ppa driver..) however most people just mke2fs /dev/sda and call it good. The DOS driver will thereafter probably not like the disk, but. You can repartition the disk with [c]fdisk if you wish, but I don't know what that would do to the DOS driver either. (Though I'm eager to try it when I get a new SCSI cable--thanks bdale!) Upon getting this thing working again, I am looking at putting together a Zip rescue disk and package to create same probably from both a group of .debs and an installed system and a few other things.. There are holes still in doing it, sooo... I'm also considering other Zip-related packages and an update of the howto as soon as I can get current information to update it with... g pgpAFStKTsbpX.pgp Description: PGP signature
