Re: Zip Drive not Recognized as Block Device
-- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/f76a4226-161e-4dca-8374-d66811864...@yahoo.co.uk
Parallel port Iomega ZIP-drive, no imm or ppa module in Debian Jessie?
Hi guys!, I've found a printer port Iomega ZIP-drive a while ago and want to test if it's working. From want I've found out there's two modules required for the SCSI over Printer Port interface that Iomega used on these drives, imm and ppa. However I can't load these modules and they don't seem to be included in the Debian versions of the 3.12 kernel. I've checked the source listing of the kernel.org 3.12 kernel and there are indeed imm and ppa modules still in the kernel. So how do I build these?, do I have to build a new kernel from source or can I build just the modules somehow? Kind regards, Adrian. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAJYAQCDbvMM4G0njuqsn0TGxBrA=YNxVa=sm36yco5tpter...@mail.gmail.com
Re: Parallel port Iomega ZIP-drive, no imm or ppa module in Debian Jessie?
On Sun 20 Apr 2014 at 16:13:24 +0200, Adrian Christiansen wrote: I've found a printer port Iomega ZIP-drive a while ago and want to test if it's working. From want I've found out there's two modules required for the SCSI over Printer Port interface that Iomega used on these drives, imm and ppa. However I can't load these modules and they don't seem to be included in the Debian versions of the 3.12 kernel. I've checked the source listing of the kernel.org 3.12 kernel and there are indeed imm and ppa modules still in the kernel. So how do I build these?, do I have to build a new kernel from source or can I build just the modules somehow? If it helps: brian@desktop:~$ locate imm ppa | grep scsi /lib/modules/3.2.0-4-686-pae/kernel/drivers/scsi/imm.ko /lib/modules/3.2.0-4-686-pae/kernel/drivers/scsi/ppa.ko This is on stable and you might need a 3.12 kernel for other reasons. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20042014153118.387522d86...@desktop.copernicus.demon.co.uk
Resurrecting ancient IOMEGA ZIP drive
Hello folks, for one last time I wanted to set in motion my old, parallel-port IOMEGA Zip Drive to back up my stack of disks before I retire (read: dump in the trash) the whole shebang for good. I think the proper driver is ppa. I connected everything but nothing happens. Happens in the sense that anything gets added in the /dev/disks/ directory tree when I insert a disk in the drive. I tried rmmoding all parallel port-related modules and modprobing only ppa, but no change. The module loaded without error though. All this is sooo long ago, I really can't remember how it worked back in the days of the 1.xx.yy kernel which is probably the last time I used this thing. I know there were two versions of the parallel-port ZIP, and my drive is the older one. Here's some modprobe output, if it is of any interest: kir:/dev# modprobe -v ppa insmod /lib/modules/2.6.18-4-k7/kernel/drivers/parport/parport.ko insmod /lib/modules/2.6.18-4-k7/kernel/drivers/scsi/ppa.ko ppa: Version 2.07 (for Linux 2.4.x) pnp: Device 00:0a activated. parport: PnPBIOS parport detected. parport0: PC-style at 0x378 (0x778), irq 7, dma 3 [PCSPP,TRISTATE,COMPAT,EPP,ECP,DMA] kir:/dev# Thanks, --D. pgpBouCS4GVu8.pgp Description: PGP signature
Re: Resurrecting ancient IOMEGA ZIP drive
for one last time I wanted to set in motion my old, parallel-port IOMEGA Zip Drive to back up my stack of disks before I retire (read: dump in the trash) the whole shebang for good. Already solved -- I just had to kick the thing and the connectors a bit. Thanks to those thad would have helped me but don't nned to any more ;-) --D. pgpoTegcoQsIp.pgp Description: PGP signature
Re: Resurrecting ancient IOMEGA ZIP drive
On Wed, May 23, 2007 at 09:31:25AM +0200, Daniel Haude wrote: for one last time I wanted to set in motion my old, parallel-port IOMEGA Zip Drive to back up my stack of disks before I retire (read: dump in the trash) the whole shebang for good. I think the proper driver is ppa. I connected everything but nothing happens. Happens in the sense that anything gets added in the /dev/disks/ directory tree when I insert a disk in the drive. I tried rmmoding all parallel port-related modules and modprobing only ppa, but no change. The module loaded without error though. Here's some modprobe output, if it is of any interest: kir:/dev# modprobe -v ppa insmod /lib/modules/2.6.18-4-k7/kernel/drivers/parport/parport.ko insmod /lib/modules/2.6.18-4-k7/kernel/drivers/scsi/ppa.ko ppa: Version 2.07 (for Linux 2.4.x) pnp: Device 00:0a activated. parport: PnPBIOS parport detected. parport0: PC-style at 0x378 (0x778), irq 7, dma 3 [PCSPP,TRISTATE,COMPAT,EPP,ECP,DMA] I have an IDE zip on each of my boxes. It uses the ide-floppy module. Since I'm using Etch with udev it gets inserted automatically. What happens if you have the drive attached with a disk in it when you boot? Check the dmesg. AIUSI, the parport isn't necessarily hotplugging your Zip drive; udev isn't seeing the device. Doug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
probable zip drive and udev conflict
I think there may be a fight ongoing between udev and my parallel zip drive. does a way exist to have udev and the zip drive live happily together? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
re: zip drive and udev conflict
I managed to get the zip drive recognized in etch by rmmod imm followed by modprobe imm. I can adjust /etc/fstab but this is strange udev and imm didn't get this drive started earlier. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
impossible de faire fonctionner mon ZIP drive
Bonjour, je viens de remplacer mon ZIP drive (atapi 100M) pensant qu'l était mort. Ce n'est pas le cas, le zip ne veut pas se monter avec ma debian/sarge. Le noyau est configuré comme il se doit, par ailleurs cela fait des années que j'utilise un zip ( utilisait .. sans problèmes) (woody). Avec mes noyaux 2.6 plus possible de le monter. Le block device n'est pas reconnu. J'ai installé windooz, ça marche. Quesce'que j'ai fait de mal ? cordialement mess-mate -- You will always have good luck in your personal affairs.
Re: Problem with mounting sda zip drive
On 7/14/05, Benjamin Sher [EMAIL PROTECTED] wrote: L.V.Gandhi wrote: On 7/13/05, Benjamin Sher [EMAIL PROTECTED] wrote: Dear friends: Thanks to your help, I am making progress step by step. My next issue has to do with my zip drive. When I try to mount it, I am told that I need to supply the file system. Please see below. Would appreciate your help. First give command as root or using sudo 5 secs after inserting flash drive. tail -n 20 /var/log/message You will get something like this.(for me in my laptop it is like this) Jul 16 16:13:08 localhost kernel: usb 4-1: new high speed USB device using address 3 Jul 16 16:13:09 localhost kernel: SCSI subsystem initialized Jul 16 16:13:09 localhost kernel: Initializing USB Mass Storage driver... Jul 16 16:13:09 localhost kernel: scsi0 : SCSI emulation for USB Mass Storage devices Jul 16 16:13:09 localhost kernel: Vendor: JetFlash Model: TS128MJF2ARev: 1.00 Jul 16 16:13:09 localhost kernel: Type: Direct-Access ANSI SCSI revision: 02 Jul 16 16:13:09 localhost usb.agent[11700]: usb-storage: loaded successfully Jul 16 16:13:09 localhost kernel: usbcore: registered new driver usb-storage Jul 16 16:13:09 localhost kernel: USB Mass Storage support registered. Jul 16 16:13:09 localhost kernel: SCSI device sda: 256000 512-byte hdwr sectors (131 MB) Jul 16 16:13:09 localhost kernel: sda: assuming Write Enabled Jul 16 16:13:09 localhost scsi.agent[11755]: sd_mod: loaded sucessfully (for disk) Jul 16 16:13:09 localhost kernel: /dev/scsi/host0/bus0/target0/lun0: p1 Jul 16 16:13:09 localhost kernel: Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0 You also find ls -l /dev/sda* mount /dev/sda1 -t auto /media/usb0. See better http://www.debian-administration.org/topics/Debian/ for usb keys. Now if you have like mine as below lvgdell600m:~# ls -l /dev/sda* brw-r- 1 root hal 8, 0 Jul 16 16:13 /dev/sda brw-rw 1 root disk 8, 1 Jul 16 16:13 /dev/sda1 Then mount as -- L.V.Gandhi http://lvgandhi.tripod.com/ linux user No.205042
Re: Problem with mounting sda zip drive
On Saturday 16 July 2005 05:59 am, L.V.Gandhi wrote: On 7/14/05, Benjamin Sher [EMAIL PROTECTED] wrote: L.V.Gandhi wrote: On 7/13/05, Benjamin Sher [EMAIL PROTECTED] wrote: Dear friends: Thanks to your help, I am making progress step by step. My next issue has to do with my zip drive. When I try to mount it, I am told that I need to supply the file system. Please see below. Would appreciate your help. First give command as root or using sudo 5 secs after inserting flash drive. tail -n 20 /var/log/message You will get something like this.(for me in my laptop it is like this) Jul 16 16:13:08 localhost kernel: usb 4-1: new high speed USB device using address 3 Jul 16 16:13:09 localhost kernel: SCSI subsystem initialized Jul 16 16:13:09 localhost kernel: Initializing USB Mass Storage driver... Jul 16 16:13:09 localhost kernel: scsi0 : SCSI emulation for USB Mass Storage devices Jul 16 16:13:09 localhost kernel: Vendor: JetFlash Model: TS128MJF2ARev: 1.00 Jul 16 16:13:09 localhost kernel: Type: Direct-Access ANSI SCSI revision: 02 Jul 16 16:13:09 localhost usb.agent[11700]: usb-storage: loaded successfully Jul 16 16:13:09 localhost kernel: usbcore: registered new driver usb-storage Jul 16 16:13:09 localhost kernel: USB Mass Storage support registered. Jul 16 16:13:09 localhost kernel: SCSI device sda: 256000 512-byte hdwr sectors (131 MB) Jul 16 16:13:09 localhost kernel: sda: assuming Write Enabled Jul 16 16:13:09 localhost scsi.agent[11755]: sd_mod: loaded sucessfully (for disk) Jul 16 16:13:09 localhost kernel: /dev/scsi/host0/bus0/target0/lun0: p1 Jul 16 16:13:09 localhost kernel: Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0 You also find ls -l /dev/sda* mount /dev/sda1 -t auto /media/usb0. See better http://www.debian-administration.org/topics/Debian/ for usb keys. Now if you have like mine as below lvgdell600m:~# ls -l /dev/sda* brw-r- 1 root hal 8, 0 Jul 16 16:13 /dev/sda brw-rw 1 root disk 8, 1 Jul 16 16:13 /dev/sda1 Then mount as Dear L. Gandhi: Thank you for your kind help, but this issue has already been resolved: #mount /dev/sda4 -t vfat /media/usb0 (Note the 4 in sda4) Thank you. Benjamin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problem with mounting sda zip drive
L.V.Gandhi wrote: On 7/13/05, Benjamin Sher [EMAIL PROTECTED] wrote: Dear friends: Thanks to your help, I am making progress step by step. My next issue has to do with my zip drive. When I try to mount it, I am told that I need to supply the file system. Please see below. Would appreciate your help. localhost:/home/sher# mount /dev/sda -t auto /media/usb0 --- here use whether vfat or something else mount: you must specify the filesystem type Dear L.V. Gandhi: Thanks so much for the advice. I am not quite there yet, but we have made some real progress. Please see output below: localhost:/home/sher# mount /dev/sda -t vfat /media/usb0 mount: wrong fs type, bad option, bad superblock on /dev/sda, missing codepage or other error In some cases useful info is found in syslog - try dmesg | tail or so Here is the /etc/fstab output: localhost:/home/sher# cd /media/usb0 localhost:/media/usb0# ls localhost:/media/usb0# cat /etc/fstab # /etc/fstab: static file system information. # # file system mount point type options dump pass proc /proc proc defaults 0 0 /dev/hdb1 / ext3 defaults,errors=remount-ro 0 1 /dev/hdb5 none swap sw 0 0 /dev/hdc /media/cdrom0 iso9660 ro,user,noauto,unhide 0 0 /dev/hdd /media/cdrom1 iso9660 ro,user,noauto,unhide 0 0 /dev/fd0 /media/floppy0 auto rw,user,noauto 0 0 /dev/sda /media/usb0 auto rw,user,noauto 0 0 localhost:/media/usb0# Hope there is a solution. Benjamin
Re: Problem with mounting sda zip drive
L.V.Gandhi wrote: On 7/13/05, Benjamin Sher [EMAIL PROTECTED] wrote: Dear friends: Thanks to your help, I am making progress step by step. My next issue has to do with my zip drive. When I try to mount it, I am told that I need to supply the file system. Please see below. Would appreciate your help. localhost:/home/sher# mount /dev/sda -t auto /media/usb0 --- here use whether vfat or something else mount: you must specify the filesystem type Dear L. V. Gandhi and friends: Here is some more data: localhost:/media/usb0# dmesg |tail Error: Illegal request -- (Sense key=0x05) Invalid field in parameter list -- (asc=0x26, ascq=0x00) The failed "Mode Select 10" packet command was: "55 10 00 00 00 00 00 00 10 00 00 00 " FAT: bogus logical sector size 10240 VFS: Can't find a valid FAT filesystem on dev 08:00. FAT: bogus logical sector size 10240 VFS: Can't find a valid FAT filesystem on dev 08:00. FAT: bogus logical sector size 10240 VFS: Can't find a valid FAT filesystem on dev 08:00. localhost:/media/usb0# Benjamin
Re: Problem with mounting sda zip drive
Hi, I see you're trying to mount /dev/sda, please try /dev/sda4. I know it sounds daft, but somehow the people at Iomega decided to format their disks that way. Grx HdV P.S. This is from my experience with Zip drives a couple of years ago, so things might have changed between then and now... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Problem with mounting sda zip drive
Dear friends: Thanks to your help, I am making progress step by step. My next issue has to do with my zip drive. When I try to mount it, I am told that I need to supply the file system. Please see below. Would appreciate your help. Benjamin [EMAIL PROTECTED]:~$ cat /etc/fstab # /etc/fstab: static file system information. # # file system mount point type options dump pass proc/proc procdefaults0 0 /dev/hdb1 / ext3defaults,errors=remount-ro 0 1 /dev/hdb5 noneswapsw 0 0 /dev/hdc/media/cdrom0 iso9660 ro,user,noauto 0 0 /dev/hdd/media/cdrom1 iso9660 ro,user,noauto 0 0 /dev/fd0/media/floppy0 autorw,user,noauto 0 0 /dev/sda/media/usb0 autorw,user,noauto 0 0 [EMAIL PROTECTED]:~$ [EMAIL PROTECTED]:~$ su Password: localhost:/home/sher# mount /dev/sda -t auto /media/usb0 mount: you must specify the filesystem type localhost:/home/sher# -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
erro montando zip drive externo
Pessoal, Está acontecendo uma coisa intrigante aqui no meu Debian testing. Para fazer funcionar um zip drive externo (porta paralela) coloquei os módulos parport e ppa para carregar no boot. Porém todo dia ele teima em não montar na primeira tentativa. Vejam o que eu preciso fazer para montar: # mount -t vfat /dev/sda4 /media/zip mount: o dispositivo especial /dev/sda4 não existe # mount -t vfat /dev/sda /media/zip mount: wrong fs type, bad option, bad superblock on /dev/sda, missing codepage or other error # mount -t vfat /dev/sda4 /media/zip # Primeiro eu tenho de tentar montar com sda que eu sei que é errado, para só então ele aceitar o sda4... É bug ou eu estou fazendo algo errado? Agradeço a ajuda, Fábio. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: erro montando zip drive externo
Fabio Guerrazzi wrote: Pessoal, Está acontecendo uma coisa intrigante aqui no meu Debian testing. Para fazer funcionar um zip drive externo (porta paralela) coloquei os módulos parport e ppa para carregar no boot. Porém todo dia ele teima em não montar na primeira tentativa. Vejam o que eu preciso fazer para montar: # mount -t vfat /dev/sda4 /media/zip mount: o dispositivo especial /dev/sda4 não existe # mount -t vfat /dev/sda /media/zip mount: wrong fs type, bad option, bad superblock on /dev/sda, missing codepage or other error # mount -t vfat /dev/sda4 /media/zip # Primeiro eu tenho de tentar montar com sda que eu sei que é errado, para só então ele aceitar o sda4... É bug ou eu estou fazendo algo errado? Vc tem o udev instalado? Veja se o /dev/sda4 nao existe mesmo antes de vc monta-lo. Pode ser que ele seja criado sob demanda, e q algo não esteja ok... -- Marcos -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Help with Zip drive
Hi Jerry, maybe you should use the imm module rather than ppa. It depends on the type of drive, just try. On Fri, May 20, 2005 at 07:39:13AM -0700, Jerry Turba wrote: I just got a parallel port Zip 100 drive. I have the ppa module loaded, along with scsi support, scsi disk support. I do not have any scsi drives, only the zip on /dev/sda4. The zip is recognized during boot, and I can read it, format it with the iomegaware tool (iw), mount it, all without problem. I have problems when I try to write to it. After the cp command the system hangs for a while. When it comes back I have lost the use of the keyboard but not the mouse, and I have to reboot. (...) HTH -- Joachim Fahnenmüller All generalisations are dangerous, including this one. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Help with Zip drive
I just got a parallel port Zip 100 drive. I have the ppa module loaded, along with scsi support, scsi disk support. I do not have any scsi drives, only the zip on /dev/sda4. The zip is recognized during boot, and I can read it, format it with the iomegaware tool (iw), mount it, all without problem. I have problems when I try to write to it. After the cp command the system hangs for a while. When it comes back I have lost the use of the keyboard but not the mouse, and I have to reboot. Here is what seems to be the relevant part of /var/log/messages. Jan 2 10:09:21 main kernel: [worker_thread+0/702] worker_thread+0x0/0x2be Jan 2 10:09:21 main kernel: [kthread+183/189] kthread+0xb7/0xbd Jan 2 10:09:21 main kernel: [kthread+0/189] kthread+0x0/0xbd Jan 2 10:09:21 main kernel: [kernel_thread_helper+5/11] kernel_thread_helper+0 x5/0xb Jan 2 10:09:21 main kernel: Code: f3 6d 8d 5d 02 b9 2c 00 00 00 89 c8 89 da ee 8d 55 01 ec 89 Jan 2 10:10:01 main kernel: 6parport0: ppa already owner Jan 2 10:10:21 main kernel: scsi: Device offlined - not ready after error recov ery: host 0 channel 0 id 6 lun 0 Jan 2 10:10:21 main kernel: SCSI error : 0 0 6 0 return code = 0x7 Jan 2 10:10:21 main kernel: end_request: I/O error, dev sda, sector 554 Jan 2 10:11:24 main kernel: lost page write due to I/O error on sda4 How do I prevent the scsi device from going offline? Any help appreciated. Thanks Jerry -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Help with Zip drive
On Friday 20 May 2005 15:39, Jerry Turba wrote: I just got a parallel port Zip 100 drive [snip] I have problems when I try to write to it. After the cp command the system hangs for a while. When it comes back I have lost the use of the keyboard but not the mouse, and I have to reboot. Wild guess, but... are you sure the write protect tab on the actual ZIP disk is disabled? I think the option to detect write protected drives isn't enabled by default in Linux. That might be only with with USB devices, or something, though :) -- Lee. Please send replies to the list, not to my email address. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Help with Zip drive
On Fri, May 20, 2005 at 07:39:13AM -0700, Jerry Turba wrote: I just got a parallel port Zip 100 drive. I have the ppa module loaded, along with scsi support, scsi disk support. I do not have any scsi drives, only the zip on /dev/sda4. The zip is recognized during boot, and I can read it, format it with the iomegaware tool (iw), mount it, all without problem. I have problems when I try to write to it. After the cp command the system hangs for a while. When it comes back I have lost the use of the keyboard but not the mouse, and I have to reboot. Here is what seems to be the relevant part of /var/log/messages. This will not help probably. I had similar problems with my own parallel Zip 100 drive. At some point, I began getting 'input/output' errors when using cp. I never understood why. I had backup of everything on hard disk, so I eventually stopped using the zip drive. Victor -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Help with Zip Drive
I just got a parallel port Zip 100 drive. I have the ppa module loaded, along with scsi support, scsi disk support. I do not have any scsi drives, only the zip on /dev/sda4. The zip is recognized during boot, and I can read it, format it with the iomegaware tool (iw), mount it, all without problem. I have problems when I try to write to it. After the cp command the system hangs for a while. When it comes back I have lost the use of the keyboard but not the mouse, and I have to reboot. Here is what seems to be the relevant part of /var/log/messages. Jan 2 10:09:21 main kernel: [worker_thread+0/702] worker_thread+0x0/0x2be Jan 2 10:09:21 main kernel: [kthread+183/189] kthread+0xb7/0xbd Jan 2 10:09:21 main kernel: [kthread+0/189] kthread+0x0/0xbd Jan 2 10:09:21 main kernel: [kernel_thread_helper+5/11] kernel_thread_helper+0 x5/0xb Jan 2 10:09:21 main kernel: Code: f3 6d 8d 5d 02 b9 2c 00 00 00 89 c8 89 da ee 8d 55 01 ec 89 Jan 2 10:10:01 main kernel: 6parport0: ppa already owner Jan 2 10:10:21 main kernel: scsi: Device offlined - not ready after error recov ery: host 0 channel 0 id 6 lun 0 Jan 2 10:10:21 main kernel: SCSI error : 0 0 6 0 return code = 0x7 Jan 2 10:10:21 main kernel: end_request: I/O error, dev sda, sector 554 Jan 2 10:11:24 main kernel: lost page write due to I/O error on sda4 How do I prevent the scsi device from going offline? Any help appreciated. Thanks Jerry -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ZIP drive question (redu).
Hi; I'm not exactly sure what I did to make this (sort of) work; maybe downloading mtools did it (I could not get iwlcontainer-lnx-x86-10.tgz from Iomega (http://www.iomega.com/software/ ) to work). Anyway I can now mount, see and read data on the zip disk. However. When I tried to copy a directory onto the disk it sort of when berserk. I can hear it accessing repeatedly for 15 min. I could not kill -9 the cp command (!?!) . I finally rebooted to get the disk out. I put the disk in a windoz machine: some of the copying seemed to have worked but with shortened (8 character upper case) names (I don't know much about fat vs other format but this looks like the problem). I've put the disk back into the Linux box and on mount /mnt/zip (no cp command) it has gone back into this clicking/access mode. umount: /mnt/zip: device is busy So ... what now? kyle Subject: Re: ZIP drive question.. From: Jacob S. [EMAIL PROTECTED] Date: Wed, 21 Jul 2004 12:11:08 -0500 To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] On Wed, 21 Jul 2004 10:44:53 -0500 Forinash, Kyle [EMAIL PROTECTED] wrote: Hi; I'm having a problem mounting a 250Mb internal zip. a.dmesg shows me hdd:IOMEGA ZIP 250 ATAPI FLOPPY ^^^ b.standard mount procedures (edit '/dev/sda4 /mnt/zip auto user,noauto 0 0' into /etc/fstab followed by mount /mnt/zip) gives: the kernel does not recognize /dev/sda4 as a block device (maybe 'insmod driver'?) The dmesg output you pasted above shows the zip drive on hdd. As root try running mount /dev/hdd /mnt/zip. If that works, you'll need to change the sda4 in your fstab entry to hdd. If that doesn't work, you may want to run fdisk /dev/hdd as root to see if the disk is partitioned weird and then add the appropriate partition number to your mount command/fstab entry (hdd1, hdd2, etc.). I'm new to Debian (having just switched from Red Hat), this is a new install of Woody. An earlier message mentioned something about a ppa module but I can find no ref anywhere to that. If dmesg is showing that it's already been setup on /dev/hdd, you shouldn't need to load any more modules... except maybe fat or vfat, but that would be a totally different error from what you pasted above. HTH HAND, Jacob -- -- 'Violence is the last refuge of the incompetent.' Issac Asimov kyle forinash 812-941-2390 [EMAIL PROTECTED] http://Physics.ius.edu/ - -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ZIP drive question (redu).
On Fri, Aug 13, 2004 at 01:50:10PM -0400, kyle forinash wrote: Hi; I'm not exactly sure what I did to make this (sort of) work; maybe downloading mtools did it (I could not get iwlcontainer-lnx-x86-10.tgz from Iomega (http://www.iomega.com/software/ ) to work). Anyway I can now mount, see and read data on the zip disk. However. When I tried to copy a directory onto the disk it sort of when berserk. I can hear it accessing repeatedly for 15 min. I could not kill -9 the cp command (!?!) . I finally rebooted to get the disk out. I put the disk in a windoz machine: some of the copying seemed to have worked but with shortened (8 character upper case) names (I don't know much about fat vs other format but this looks like the problem). I've put the disk back into the Linux box and on mount /mnt/zip (no cp command) it has gone back into this clicking/access mode. umount: /mnt/zip: device is busy So ... what now? kyle I had a very similar problem. Only, it was a CD-ROM drive. The activity light was on, so I thought maybe it was like a floppy - if the drive doesn't get deactivated by the bootcode, it would keep spinning until first use. So, i did something like: dd if=/dev/hdc of=/dev/null bs=2k count=1 Instant hang. Ctl-C didn't work. kill -9 didn't work. Lots of something-bad-is-happening kernel messages. I had to reboot. A new cdrom drive fixed it for me... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: ZIP drive question
(reply at bottom) On Fri, 6 Aug 2004, Forinash, Kyle wrote: Thanks! I have not yet resolved the issue because I haven't been able to work on it (I've been out of town for two weeks). I'll check out the link next week and see if that helps. I'll post to the listserv if I figure it out. kyle -Original Message- From: Gayle Lee Fairless [mailto:[EMAIL PROTECTED] Sent: Sat 7/24/2004 4:23 PM To: Forinash, Kyle; [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: ZIP drive question Kyle, Did you ever solve your ZIP drive problem? I have a USB ZIP 250 drive on /dev /sda4. Since I am subscribling only to the digest to cut down on volume, I may have missed the resolution. I downloaded iwlcontainer-lnx-x86-10.tgz from Iomega. It appears to work for me. I have not finished working with it, though. http://www.iomega.com/software/ http://www.iomega.com/datahandler/servlet I included the URL's with Iomega that I used. It is possible to go to www.iomega.com and drill down to the download menu. Hope this helps! (Mr.) Gayle Lee Fairless Linux Gcomm 2.4.18-bf2.4 #1 Son Apr 14 09:53:28 CEST 2002 i686 unknown iwclcontainer-lnx-x86-10.tgz Kyle, I also set up sudo to let users on my system use the iw command to mount and umount the Zip cartridge. I'm using this with a USB Zip250 drive. There is a jazip package on woody stable that is supposed to work with other Zip drives, but it requires libform0.89 which is distributed only in binary form (since the source is not released to the public). I've downloaded the libform0.89 tarball file from Debian.org but haven't installed it. Even if I download the package I can't test since I don't have a SCSI connection on the Gateway 500 (I have a SCSI Zip 100 on my Amiga) and don't have ATAPI Zip drive. Sincerely, (Mr.) Gayle Lee Fairless Linux Gcomm 2.4.18-bf2.4 #1 Son Apr 14 09:53:28 CEST 2002 i686 unknown -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ZIP drive question
Kyle, Did you ever solve your ZIP drive problem? I have a USB ZIP 250 drive on /dev /sda4. Since I am subscribling only to the digest to cut down on volume, I may have missed the resolution. I downloaded iwlcontainer-lnx-x86-10.tgz from Iomega. It appears to work for me. I have not finished working with it, though. http://www.iomega.com/software/ http://www.iomega.com/datahandler/servlet I included the URL's with Iomega that I used. It is possible to go to www.iomega.com and drill down to the download menu. Hope this helps! (Mr.) Gayle Lee Fairless Linux Gcomm 2.4.18-bf2.4 #1 Son Apr 14 09:53:28 CEST 2002 i686 unknown iwclcontainer-lnx-x86-10.tgz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ZIP drive question.
On Thu, 22 Jul 2004 06:27:38 -0500 Forinash, Kyle [EMAIL PROTECTED] wrote: /home/kyle# /bin/mount /dev/hdd /mnt/zip mount: you must specify the filesystem type /home/kyle# /bin/mount -t vfat /dev/hdd /mnt/zip mount: wrong fs type, bad option, bad superblock on /dev/hdd, or too many mounted file systems /home/kyle# /sbin/fdisk /dev/hdd Command (m for help): p Disk /dev/hdd: 64 heads, 32 sectors, 239 cylinders Units = cylinders of 2048 * 512 bytes Device BootStart EndBlocks Id System /dev/hdd4 * 1 2392447206 FAT16 Command (m for help): q :/home/kyle# /bin/mount -t FAT16 /dev/hdd4 /mnt/zip mount: fs type FAT16 not supported by kernel -- You're on the right track. As root try mount -t vfat /dev/hdd4 /mnt/zip. HTH, Jacob - Nope I get: /home/kyle# /bin/mount -t vfat /dev/hdd4 /mnt/zip mount: wrong fs type, bad option, bad superblock on /dev/hdd4, or too many mounted file systems (could this be the IDE device where you in fact use ide-scsi so that sr0 or sda or so is needed?) I'm still stumped(but thanks for the help-at least I'm not being stupid) --- This zip disk is formatted, isn't it? Try one more mount command - mount -t msdos /dev/hdd4 /mnt/zip. HTH, Jacob Yes, this is a backup disk with stuff on it. :/home/kyle# mount -t msdos /dev/hdd4 /mnt/zip mount: wrong fs type, bad option, bad superblock on /dev/hdd4, or too many mounted file systems (could this be the IDE device where you in fact use ide-scsi so that sr0 or sda or so is needed?) The drive does react and sound like it tries to read the disk. I tired to new partition a different disk with fdisk but get the same thing. Having spent some time Googleing I have discovered what may be the problem (and I'm learning a lot!): vfat.o (msdos, FAT16 etc.) is NOT in /lib/modules/2.2.20-idepci/fs/ (in fact no where in the system- how I installed a clean system without it is beyond me, lots of other modules are there). I think maybe if I had version kernal version 2.2.20 of vfat I could insmod it (other versions of vfat will not fool insmod -I tried using a different version from an old RedHat system). I don't know any other way of getting around this, if that is the problem (except perhaps a kernel recompile, and I don't have time to learn how to do that right now). Thanks for the help, any suggestions? kyle
Re: ZIP drive question.
On Fri, 23 Jul 2004 09:58:15 -0500 Forinash, Kyle [EMAIL PROTECTED] wrote: On Thu, 22 Jul 2004 06:27:38 -0500 Forinash, Kyle [EMAIL PROTECTED] wrote: This zip disk is formatted, isn't it? Try one more mount command - mount -t msdos /dev/hdd4 /mnt/zip. HTH, Jacob Yes, this is a backup disk with stuff on it. :/home/kyle# mount -t msdos /dev/hdd4 /mnt/zip mount: wrong fs type, bad option, bad superblock on /dev/hdd4, or too many mounted file systems (could this be the IDE device where you in fact use ide-scsi so that sr0 or sda or so is needed?) The drive does react and sound like it tries to read the disk. I tired to new partition a different disk with fdisk but get the same thing. Having spent some time Googleing I have discovered what may be the problem (and I'm learning a lot!): vfat.o (msdos, FAT16 etc.) is NOT in /lib/modules/2.2.20-idepci/fs/ (in fact no where in the system- how I installed a clean system without it is beyond me, lots of other modules are there). I think maybe if I had version kernal version 2.2.20 of vfat I could insmod it (other versions of vfat will not fool insmod -I tried using a different version from an old RedHat system). I don't know any other way of getting around this, if that is the problem (except perhaps a kernel recompile, and I don't have time to learn how to do that right now). Now that I look, the 2.4.18-bf2.4 kernel in Woody comes with vfat compiled into the kernel instead of as a module. I'm not sure about 2.2.20-idepci, but I would suspect it's the same. grep for VFAT in /boot/config-2.2.20-idepci and see what it says. It should read 'y' for compiled into the kernel, 'm' for compiled as a module or 'n' for not compiled at all. On the off chance that 2.2.20-idepci doesn't have vfat support, apt-get install kernel-image-2.4.18-bf2.4 should install a newer kernel with vfat support compiled in - saving you the trouble of having to compile your own. Also, what version of Windows was used to write to this disk? Did you ever format it in Windows, or just used it with the format that Iomega puts on their PC zip disks? Sorry, it's been a little while since I've played with zip drives. Hopefully someone else will jump in here if they see me going wrong. HTH, Jacob -- GnuPG Key: 1024D/16377135 Random .signature #56: Windows hasn't increased computer literacy. It's just lowered the standard. pgpPOfcPtyyB7.pgp Description: PGP signature
Re: ZIP drive question.
Subject: Re: ZIP drive question.. From: Jacob S. [EMAIL PROTECTED] Date: Wed, 21 Jul 2004 15:53:37 -0500 To: [EMAIL PROTECTED] On Wed, 21 Jul 2004 15:20:22 -0500 Forinash, Kyle [EMAIL PROTECTED] wrote: Hi Jacob, thanks for trying to help me out. Here is what I tried (to no avail). How do I know what fs types are available (I tried repartitioning the zip as Extended but got the same not supported error)? Am I doing something stupid here? /home/kyle# /bin/mount /dev/hdd /mnt/zip mount: you must specify the filesystem type /home/kyle# /bin/mount -t vfat /dev/hdd /mnt/zip mount: wrong fs type, bad option, bad superblock on /dev/hdd, or too many mounted file systems /home/kyle# /sbin/fdisk /dev/hdd Command (m for help): p Disk /dev/hdd: 64 heads, 32 sectors, 239 cylinders Units = cylinders of 2048 * 512 bytes Device BootStart EndBlocks Id System /dev/hdd4 * 1 2392447206 FAT16 Command (m for help): q physics:/home/kyle# /bin/mount -t FAT16 /dev/hdd4 /mnt/zip mount: fs type FAT16 not supported by kernel -- You're on the right track. As root try mount -t vfat /dev/hdd4 /mnt/zip. HTH, Jacob - Nope I get: /home/kyle# /bin/mount -t vfat /dev/hdd4 /mnt/zip mount: wrong fs type, bad option, bad superblock on /dev/hdd4, or too many mounted file systems (could this be the IDE device where you in fact use ide-scsi so that sr0 or sda or so is needed?) I'm still stumped(but thanks for the help-at least I'm not being stupid) kyle
Re: ZIP drive question.
On Thu, 22 Jul 2004 06:27:38 -0500 Forinash, Kyle [EMAIL PROTECTED] wrote: /home/kyle# /bin/mount /dev/hdd /mnt/zip mount: you must specify the filesystem type /home/kyle# /bin/mount -t vfat /dev/hdd /mnt/zip mount: wrong fs type, bad option, bad superblock on /dev/hdd, or too many mounted file systems /home/kyle# /sbin/fdisk /dev/hdd Command (m for help): p Disk /dev/hdd: 64 heads, 32 sectors, 239 cylinders Units = cylinders of 2048 * 512 bytes Device BootStart EndBlocks Id System /dev/hdd4 * 1 2392447206 FAT16 Command (m for help): q physics:/home/kyle# /bin/mount -t FAT16 /dev/hdd4 /mnt/zip mount: fs type FAT16 not supported by kernel -- You're on the right track. As root try mount -t vfat /dev/hdd4 /mnt/zip. HTH, Jacob - Nope I get: /home/kyle# /bin/mount -t vfat /dev/hdd4 /mnt/zip mount: wrong fs type, bad option, bad superblock on /dev/hdd4, or too many mounted file systems (could this be the IDE device where you in fact use ide-scsi so that sr0 or sda or so is needed?) I'm still stumped(but thanks for the help-at least I'm not being stupid) This zip disk is formatted, isn't it? Try one more mount command - mount -t msdos /dev/hdd4 /mnt/zip. HTH, Jacob -- GnuPG Key: 1024D/16377135 Random .signature #33: Linux: transforms your microcomputer in a workstation. Windows NT: transforms your workstation in a microcomputer. pgpcZogZEf31I.pgp Description: PGP signature
Re: Re: ZIP drive question..
Hi;Im having a problem mounting a 250Mb internal zip.a. dmesg shows me hdd:IOMEGA ZIP 250 ATAPI FLOPPYb. standard mount procedures (edit /dev/sda4 /mnt/zip auto user,noauto 0 0 into /etc/fstab followed by mount /mnt/zip) gives: the kernel does not recognize /dev/sda4 as a block device (maybe insmod driver?)Im new to Debian (having just switched from Red Hat), this is a new install of Woody. An earlier message mentioned something about a ppa module but I can find no ref anywhere to that.Any suggestions?kyle
Re: ZIP drive question..
On Wed, 21 Jul 2004 10:44:53 -0500 Forinash, Kyle [EMAIL PROTECTED] wrote: Hi; I'm having a problem mounting a 250Mb internal zip. a.dmesg shows me hdd:IOMEGA ZIP 250 ATAPI FLOPPY ^^^ b.standard mount procedures (edit '/dev/sda4 /mnt/zip auto user,noauto 0 0' into /etc/fstab followed by mount /mnt/zip) gives: the kernel does not recognize /dev/sda4 as a block device (maybe 'insmod driver'?) The dmesg output you pasted above shows the zip drive on hdd. As root try running mount /dev/hdd /mnt/zip. If that works, you'll need to change the sda4 in your fstab entry to hdd. If that doesn't work, you may want to run fdisk /dev/hdd as root to see if the disk is partitioned weird and then add the appropriate partition number to your mount command/fstab entry (hdd1, hdd2, etc.). I'm new to Debian (having just switched from Red Hat), this is a new install of Woody. An earlier message mentioned something about a ppa module but I can find no ref anywhere to that. If dmesg is showing that it's already been setup on /dev/hdd, you shouldn't need to load any more modules... except maybe fat or vfat, but that would be a totally different error from what you pasted above. HTH HAND, Jacob -- GnuPG Key: 1024D/16377135 Random .signature #11: Linux -- Have you administered a real OS today? pgpl2CA6jCdXo.pgp Description: PGP signature
Re: ZIP drive question..
On 2004-07-21, Jacob S. penned: --Signature=_Wed__21_Jul_2004_12_11_08_-0500_wz0Lp0Pqv4IaNzYy Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Content-Transfer-Encoding: 7bit On Wed, 21 Jul 2004 10:44:53 -0500 Forinash, Kyle [EMAIL PROTECTED] wrote: Hi; I'm having a problem mounting a 250Mb internal zip. a.dmesg shows me hdd:IOMEGA ZIP 250 ATAPI FLOPPY ^^^ b.standard mount procedures (edit '/dev/sda4 /mnt/zip auto user,noauto 0 0' into /etc/fstab followed by mount /mnt/zip) gives: the kernel does not recognize /dev/sda4 as a block device (maybe 'insmod driver'?) The dmesg output you pasted above shows the zip drive on hdd. As root try running mount /dev/hdd /mnt/zip. If that works, you'll need to change the sda4 in your fstab entry to hdd. It will probably be /dev/hdd4 ... zip drives are weird that way. -- monique -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ZIP drive question..
On Wed, Jul 21, 2004 at 12:11:08PM -0500, Jacob S. wrote: On Wed, 21 Jul 2004 10:44:53 -0500 Forinash, Kyle [EMAIL PROTECTED] wrote: Hi; I'm having a problem mounting a 250Mb internal zip. a.dmesg shows me hdd:IOMEGA ZIP 250 ATAPI FLOPPY ^^^ b.standard mount procedures (edit '/dev/sda4 /mnt/zip auto user,noauto 0 0' into /etc/fstab followed by mount /mnt/zip) gives: the kernel does not recognize /dev/sda4 as a block device (maybe 'insmod driver'?) The dmesg output you pasted above shows the zip drive on hdd. As root try running mount /dev/hdd /mnt/zip. If that works, you'll need to change the sda4 in your fstab entry to hdd. If that doesn't work, you may want to run fdisk /dev/hdd as root to see if the disk is partitioned weird and then add the appropriate partition number to your mount command/fstab entry (hdd1, hdd2, etc.). I'm new to Debian (having just switched from Red Hat), this is a new install of Woody. An earlier message mentioned something about a ppa module but I can find no ref anywhere to that. If dmesg is showing that it's already been setup on /dev/hdd, you shouldn't need to load any more modules... except maybe fat or vfat, but that would be a totally different error from what you pasted above. IIRC the ppa module is for the parport version of the ZIP drive (and in that case it _is_ /dev/sda4 ), but for the internal drive it should be as Jacob wrote. HTH -- Joachim Fahnenmüller # Hi! I'm a .signature virus. Copy me into # your ~/.signature to help me spread! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: debian-user-digest Digest V2004 #653Subject: Re: ZIP drive question..
Hi Jacob, thanks for trying to help me out. Here is what I tried (to no avail). How do I know what fs types are available (I tried repartitioning the zip as Extended but got the same not supported error)? Am I doing something stupid here? /home/kyle# /bin/mount /dev/hdd /mnt/zip mount: you must specify the filesystem type /home/kyle# /bin/mount -t vfat /dev/hdd /mnt/zip mount: wrong fs type, bad option, bad superblock on /dev/hdd, or too many mounted file systems /home/kyle# /sbin/fdisk /dev/hdd Command (m for help): p Disk /dev/hdd: 64 heads, 32 sectors, 239 cylinders Units = cylinders of 2048 * 512 bytes Device BootStart EndBlocks Id System /dev/hdd4 * 1 2392447206 FAT16 Command (m for help): q physics:/home/kyle# /bin/mount -t FAT16 /dev/hdd4 /mnt/zip mount: fs type FAT16 not supported by kernel kyle Subject: Re: ZIP drive question.. From: Jacob S. [EMAIL PROTECTED] Date: Wed, 21 Jul 2004 12:11:08 -0500 To: [EMAIL PROTECTED] On Wed, 21 Jul 2004 10:44:53 -0500 Forinash, Kyle [EMAIL PROTECTED] wrote: Hi; I'm having a problem mounting a 250Mb internal zip. a.dmesg shows me hdd:IOMEGA ZIP 250 ATAPI FLOPPY ^^^ b.standard mount procedures (edit '/dev/sda4 /mnt/zip auto user,noauto 0 0' into /etc/fstab followed by mount /mnt/zip) gives: the kernel does not recognize /dev/sda4 as a block device (maybe 'insmod driver'?) The dmesg output you pasted above shows the zip drive on hdd. As root try running mount /dev/hdd /mnt/zip. If that works, you'll need to change the sda4 in your fstab entry to hdd If that doesn't work, you may want to run fdisk /dev/hdd as root to see if the disk is partitioned weird and then add the appropriate partition number to your mount command/fstab entry (hdd1, hdd2, etc.). I'm new to Debian (having just switched from Red Hat), this is a new install of Woody. An earlier message mentioned something about a ppa module but I can find no ref anywhere to that. If dmesg is showing that it's already been setup on /dev/hdd, you shouldn't need to load any more modules... except maybe fat or vfat, but that would be a totally different error from what you pasted above. HTH HAND, Jacob -- -- 'Violence is the last refuge of the incompetent.' Issac Asimov kyle forinash 812-941-2390 [EMAIL PROTECTED] http://Physics.ius.edu/ -
Re: ZIP drive question..
On Wed, 21 Jul 2004 15:20:22 -0500 Forinash, Kyle [EMAIL PROTECTED] wrote: Hi Jacob, thanks for trying to help me out. Here is what I tried (to no avail). How do I know what fs types are available (I tried repartitioning the zip as Extended but got the same not supported error)? Am I doing something stupid here? /home/kyle# /bin/mount /dev/hdd /mnt/zip mount: you must specify the filesystem type /home/kyle# /bin/mount -t vfat /dev/hdd /mnt/zip mount: wrong fs type, bad option, bad superblock on /dev/hdd, or too many mounted file systems /home/kyle# /sbin/fdisk /dev/hdd Command (m for help): p Disk /dev/hdd: 64 heads, 32 sectors, 239 cylinders Units = cylinders of 2048 * 512 bytes Device BootStart EndBlocks Id System /dev/hdd4 * 1 2392447206 FAT16 Command (m for help): q physics:/home/kyle# /bin/mount -t FAT16 /dev/hdd4 /mnt/zip mount: fs type FAT16 not supported by kernel You're on the right track. As root try mount -t vfat /dev/hdd4 /mnt/zip. HTH, Jacob -- GnuPG Key: 1024D/16377135 Random .signature #43: Q: How many Microsoft Programmers does it take to screw in a lightbulb? A: It cannot be done. You will need to upgrade your house. Q: How many Linux users does it take to change a lightbulb? A: Two. One to write the HOWTO-LIGHTBULB-CRONJOB, and another to read it. pgpdPPqlCC3Ii.pgp Description: PGP signature
adding a parallel zip drive
I have a working installation of sarge with v2.6 kernel. Considering the changes that took place on the EIDE and SCSI interfaces with respect to CD-RW's and that parallel zip drives also were SCSI emulated. How do I configure a zip disk under 2.6 today? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
ZIP drive question..
System is Debian testing (kernel 2.6.5) installed from Knoppix-3.4 The PC has a 100Mb ZIP drive in it. It is detected at boot time (dmesg - hdd). Lilo.conf has option hdd=scsi in it.. Attempt to mount the disks in it as # mount /dev/sda4 /mnt/test results in: mount: /dev/sda4 is not valid block device similar messge when /dev/hdd4 is mounted. Any pointers? -ishwar -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ZIP drive question..
On Tue, 2004-05-25 at 09:47, Ishwar Rattan wrote: System is Debian testing (kernel 2.6.5) installed from Knoppix-3.4 The PC has a 100Mb ZIP drive in it. It is detected at boot time (dmesg - hdd). Lilo.conf has option hdd=scsi in it.. Attempt to mount the disks in it as # mount /dev/sda4 /mnt/test results in: mount: /dev/sda4 is not valid block device similar messge when /dev/hdd4 is mounted. You didn't say what type of connection the drive is using, but judging by the fact that you said that the drive is 'in' the computer (and that it's being detected as hdd), I'm guessing that it's an internal IDE drive. If that's the case, why do you want to access it as a SCSI device? Have you tried taking out the hdd=scsi line in lilo.conf and accessing it directly as hdd? -- Alex Malinovich Support Free Software, delete your Windows partition TODAY! Encrypted mail preferred. You can get my public key from any of the pgp.net keyservers. Key ID: A6D24837 signature.asc Description: This is a digitally signed message part
Re: ZIP drive question..
It is an IDE internal 100Mb ZIP drive. (dmesg | grep ZIP displays- hdd: IOMEGA ZIP 100 ATAPI DRIVE, ATAPI FLOPPY drive) When hdd=scsi is removed, system still tries to access it as scsi drive. What is the option for this drive to be treated as ide/atapi drive? hdd=ide and hdd=atapi are treated as BAD options by the kernel. -ishwar On Tue, 25 May 2004, Alex Malinovich wrote: On Tue, 2004-05-25 at 09:47, Ishwar Rattan wrote: System is Debian testing (kernel 2.6.5) installed from Knoppix-3.4 The PC has a 100Mb ZIP drive in it. It is detected at boot time (dmesg - hdd). Lilo.conf has option hdd=scsi in it.. Attempt to mount the disks in it as # mount /dev/sda4 /mnt/test results in: mount: /dev/sda4 is not valid block device similar messge when /dev/hdd4 is mounted. You didn't say what type of connection the drive is using, but judging by the fact that you said that the drive is 'in' the computer (and that it's being detected as hdd), I'm guessing that it's an internal IDE drive. If that's the case, why do you want to access it as a SCSI device? Have you tried taking out the hdd=scsi line in lilo.conf and accessing it directly as hdd? -- Alex Malinovich Support Free Software, delete your Windows partition TODAY! Encrypted mail preferred. You can get my public key from any of the pgp.net keyservers. Key ID: A6D24837 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ZIP drive question..
On Tue, 2004-05-25 at 13:04, Ishwar Rattan wrote: It is an IDE internal 100Mb ZIP drive. (dmesg | grep ZIP displays- hdd: IOMEGA ZIP 100 ATAPI DRIVE, ATAPI FLOPPY drive) When hdd=scsi is removed, system still tries to access it as scsi drive. I'm not sure what you mean by this. Could you explain please? What is the option for this drive to be treated as ide/atapi drive? hdd=ide and hdd=atapi are treated as BAD options by the kernel. You don't need to pass any options. If it shows up as hdd the system already knows that it's an IDE device. -- Alex Malinovich Support Free Software, delete your Windows partition TODAY! Encrypted mail preferred. You can get my public key from any of the pgp.net keyservers. Key ID: A6D24837 signature.asc Description: This is a digitally signed message part
Re: ZIP drive question..
Here it is again. PC also has a CD-RW drive (internal ATAPI) and the install lilo.conf append line was: append=ramdisk_size=10 lang=en apm=power-off hda=scsi hdb=scsi \ hdc=scsi hdd=scsi hde=scsi hdf=scsi hdg=scsi hdh=scsi nomce and allowed CD-RW to work using ide-scsi interface?? So, on suggestion I tried the append options to: append=ramdisk_size=10 lang=en apm=power-off nomce and I have the samne problem (mount: /dev/hdd4 is not a valid block device) There seems to be an entry for /dev/hhd4 # /dev | grep hdd4 brw-rw1 root disk 22, 68 Apr 14 2001 hdd4 And also for /dev/sda4 (has no meaning here) # ll /dev | grep sda4 brw-rw1 root disk 8, 4 Apr 14 2001 sda4 I am unable to figure out the solution.. -ishwar On Tue, 25 May 2004, Alex Malinovich wrote: On Tue, 2004-05-25 at 13:04, Ishwar Rattan wrote: It is an IDE internal 100Mb ZIP drive. (dmesg | grep ZIP displays- hdd: IOMEGA ZIP 100 ATAPI DRIVE, ATAPI FLOPPY drive) When hdd=scsi is removed, system still tries to access it as scsi drive. I'm not sure what you mean by this. Could you explain please? What is the option for this drive to be treated as ide/atapi drive? hdd=ide and hdd=atapi are treated as BAD options by the kernel. You don't need to pass any options. If it shows up as hdd the system already knows that it's an IDE device. -- Alex Malinovich Support Free Software, delete your Windows partition TODAY! Encrypted mail preferred. You can get my public key from any of the pgp.net keyservers. Key ID: A6D24837 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ZIP drive question..
On Tue, 2004-05-25 at 15:18, Ishwar Rattan wrote: Here it is again. PC also has a CD-RW drive (internal ATAPI) and the install lilo.conf append line was: append=ramdisk_size=10 lang=en apm=power-off hda=scsi hdb=scsi \ hdc=scsi hdd=scsi hde=scsi hdf=scsi hdg=scsi hdh=scsi nomce and allowed CD-RW to work using ide-scsi interface?? These entries are for ide-scsi. ide-scsi is only used for CD/DVD drives and has no bearing on other IDE devices. There seems to be an entry for /dev/hhd4 # /dev | grep hdd4 brw-rw1 root disk 22, 68 Apr 14 2001 hdd4 And also for /dev/sda4 (has no meaning here) # ll /dev | grep sda4 brw-rw1 root disk 8, 4 Apr 14 2001 sda4 I am unable to figure out the solution.. Unless you're using udev with a 2.6 series kernel, the device entries will always be there, whether or not they actually exist on the system. This is a silly question, but you do of course have a disk in the drive, right? Also, if you're using hotplug, that might be affecting the drive as well. Something else that would help would be a list of your current modules (lsmod). -- Alex Malinovich Support Free Software, delete your Windows partition TODAY! Encrypted mail preferred. You can get my public key from any of the pgp.net keyservers. Key ID: A6D24837 signature.asc Description: This is a digitally signed message part
Re: how to mount a zip drive
On Fri, Nov 28, 2003 at 11:05:46AM -0600, wrote: | Hi All: | |how in praytell do you mount a zip drive is there a way to do it | without recompiling linux? # mount -t vfat /dev/hdd4 /mnt/zip Well, assuming you have my old Compaq micro-tower (which you don't, my dad does) then your zip drive is an internal IDE drive and is the secondary slave. If the details of my old system match yours, then the above command is exactly how to do it. If the details vary, then you'll have to adjust for that. -D -- One OS to rule them all, one OS to find them, One OS to bring them all and in the darkness bind them, In the Land of Redmond, where the Shadows lie. www: http://dman13.dyndns.org/~dman/jabber: [EMAIL PROTECTED] pgp0.pgp Description: PGP signature
Re: how to mount a zip drive
Paul Valley wrote: Hi All: how in praytell do you mount a zip drive is there a way to do it without recompiling linux? Paul You can just compile those necessary modules, and modprobe. no new kernel, no reboot. -- Yours sincerely,\|||/ (o o) +---ooO--(_)--Ooo+ | ZHANG Jiele | | [EMAIL PROTECTED].oooO| | http://www.jiele.net ( ) Oooo.| +\ (( )+ \_)) / -- (_/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: how to mount a zip drive
On Fri, 2003-11-28 at 11:05, Paul Valley wrote: Hi All: how in praytell do you mount a zip drive is there a way to do it without recompiling linux? Well, you need to give us more info first. What type of zip drive is it? Internal IDE, Parallel, SCSI, or USB? If you're using a stock Debian kernel you shouldn't need to do any recompiling. You'll just need to load the appropriate modules. Once you've got that done, you just need to mount partition 4 for the appropriate device. (i.e. if you're using an IDE zip drive, you'd mount /dev/hdc4, assuming that the drive is hdc of course.) -- Alex Malinovich Support Free Software, delete your Windows partition TODAY! Encrypted mail preferred. You can get my public key from any of the pgp.net keyservers. Key ID: A6D24837 signature.asc Description: This is a digitally signed message part
how to mount a zip drive
Hi All: how in praytell do you mount a zip drive is there a way to do it without recompiling linux? Paul -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: booting from a usb mass storage zip drive
Rob Benton wrote: PROCESSES: root15 0.0 0.0 00 ?SW 02:46 0:00 [usb-storage-0] root16 0.0 0.0 00 ?SW 02:46 0:00 [scsi_eh_1] These are kernel threads, that's why they're low-numbered processes just above 1 (init), have their name in brackets, and all the zeros for their used memory etc. These represent the parts of the kernel that deal with your usb device. LOOPING OUTPUT IN SYSLOG: -- Oct 21 22:44:22 wakizashi kernel: usb-storage: queuecommand() called Oct 21 22:44:22 wakizashi kernel: usb-storage: *** thread awakened. Oct 21 22:44:22 wakizashi kernel: usb-storage: Command READ_10 (10 bytes) Oct 21 22:44:22 wakizashi kernel: usb-storage: 28 00 00 03 aa 78 00 00 04 00 00 00 Oct 21 22:44:22 wakizashi kernel: usb-storage: Bulk command S 0x43425355 T 0x1516 Trg 0 LUN 0 L 2048 F 128 CL 10 Oct 21 22:44:22 wakizashi kernel: usb-storage: Bulk command transfer result=0 These are verbose USB debugging messages. Rebuild your kernel with CONFIG_USB_DEBUG turned off. -- see shy jo signature.asc Description: Digital signature
booting from a usb mass storage zip drive
I need some extra eyes and advice for this problem I'm having. I've got a usb 250 zip drive that I've installed debian on. I've been using an initrd ramdisk to boot from that uses kernel 2.4.20. The boot process goes fine. The problem is, there are 2 strange processes that continue after boot. One of them is writing to all the log files filling up the disk. Booting into another partition (on an ide drive) I can mount this drive and none of these problems occur. Does anyone know how to fix this or what that process is looking/waiting for? // logs and processes // PROCESSES: root15 0.0 0.0 00 ?SW 02:46 0:00 [usb-storage-0] root16 0.0 0.0 00 ?SW 02:46 0:00 [scsi_eh_1] USBFS IS MOUNTED /proc/bus/usb devices: *--snip--* C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=255ms T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 2 Spd=12 MxCh= 0 D: Ver= 1.10 Cls=00(ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=059b ProdID=0030 Rev= 1.00 S: Manufacturer=Iomega S: Product=USB Zip 250 S: SerialNumber=059B00300D006248 C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr= 0mA I: If#= 0 Alt= 0 #EPs= 3 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage E: Ad=01(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=83(I) Atr=03(Int.) MxPS= 2 Ivl=32ms drivers: usbdevfs hub 96-111: hiddev hid serial usb-storage LOOPING OUTPUT IN SYSLOG: -- Oct 21 22:44:22 wakizashi kernel: usb-storage: queuecommand() called Oct 21 22:44:22 wakizashi kernel: usb-storage: *** thread awakened. Oct 21 22:44:22 wakizashi kernel: usb-storage: Command READ_10 (10 bytes) Oct 21 22:44:22 wakizashi kernel: usb-storage: 28 00 00 03 aa 78 00 00 04 00 00 00 Oct 21 22:44:22 wakizashi kernel: usb-storage: Bulk command S 0x43425355 T 0x1516 Trg 0 LUN 0 L 2048 F 128 CL 10 Oct 21 22:44:22 wakizashi kernel: usb-storage: Bulk command transfer result=0 Oct 21 22:44:22 wakizashi kernel: usb-storage: usb_stor_transfer_partial(): xfer 2048 bytes Oct 21 22:44:22 wakizashi kernel: usb-storage: usb_stor_bulk_msg() returned 0 xferred 2048/2048 Oct 21 22:44:22 wakizashi kernel: usb-storage: usb_stor_transfer_partial(): transfer complete Oct 21 22:44:22 wakizashi kernel: usb-storage: Bulk data transfer result 0x0 Oct 21 22:44:22 wakizashi kernel: usb-storage: Attempting to get CSW... Oct 21 22:44:22 wakizashi kernel: usb-storage: Bulk status result = 0 Oct 21 22:44:22 wakizashi kernel: usb-storage: Bulk status Sig 0x53425355 T 0x1516 R 0 Stat 0x0 Oct 21 22:44:22 wakizashi kernel: usb-storage: scsi cmd done, result=0x0 Oct 21 22:44:22 wakizashi kernel: usb-storage: *** thread sleeping. Oct 21 22:44:22 wakizashi kernel: usb-storage: queuecommand() called Oct 21 22:44:22 wakizashi kernel: usb-storage: *** thread awakened. Oct 21 22:44:22 wakizashi kernel: usb-storage: Command READ_10 (10 bytes) Oct 21 22:44:22 wakizashi kernel: usb-storage: 28 00 00 03 aa 9c 00 00 02 00 00 00 Oct 21 22:44:22 wakizashi kernel: usb-storage: Bulk command S 0x43425355 T 0x1517 Trg 0 LUN 0 L 1024 F 128 CL 10 Oct 21 22:44:22 wakizashi kernel: usb-storage: Bulk command transfer result=0 Oct 21 22:44:22 wakizashi kernel: usb-storage: usb_stor_transfer_partial(): xfer 1024 bytes Oct 21 22:44:22 wakizashi kernel: usb-storage: usb_stor_bulk_msg() returned 0 xferred 1024/1024 Oct 21 22:44:22 wakizashi kernel: usb-storage: usb_stor_transfer_partial(): transfer complete Oct 21 22:44:22 wakizashi kernel: usb-storage: Bulk data transfer result 0x0 Oct 21 22:44:22 wakizashi kernel: usb-storage: Attempting to get CSW... Oct 21 22:44:22 wakizashi kernel: usb-storage: Bulk status result = 0 Oct 21 22:44:22 wakizashi kernel: usb-storage: Bulk status Sig 0x53425355 T 0x1517 R 0 Stat 0x0 Oct 21 22:44:22 wakizashi kernel: usb-storage: scsi cmd done, result=0x0 Oct 21 22:44:22 wakizashi kernel: usb-storage: *** thread sleeping. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
internal zip drive kernel option
Hi, People Please I would appreciate if someone can help me with this matter. I recompiled kernel to turn quotas on (configured using make config), but now cannot access internal zip drive through: mount /dev/hdd1 /zip as i did previusly. Which module I forget to turn on to get it ? Fernando Rowies Thanks Internet GRATIS es Yahoo! Conexión 4004-1010 desde Buenos Aires. Usuario: yahoo; contraseña: yahoo Más ciudades: http://conexion.yahoo.com.ar -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Getting a Zip Drive to Work
On Wed, 6 Aug 2003 [EMAIL PROTECTED] wrote: Having just installed Debian (as a new Linux user) I am having problems getting my internal zip-drive to work. Mainly as I cannot figure out which device it is and becuase I need to have the edits to the fstab I need to make explained. Any help explanations would be very much appreciated. As the ATAPI model seems to be the most popular I'll show you what you need to know for installing such a beast. For SCSI only the first step will differ. First find out which IDE channel you're using: grep ZIP /var/log/messages OK, in my case that gives hdd: IOMEGA ZIP 100 ATAPI, ATAPI FLOPPY drive However, this is not enough because for some never explained reason Iomega has formatted some ZIP disks with a filesystem on hdd4 some others just on hdd. Some you need to figure out what is applicable to your situation. Trial and error may be the fastest route in this case as there are only two options. Or you could just build your own filesystem on them with mke2fs. Here's what I have in my /etc/fstab for the ZIP drive: /dev/hdd4 /zipext2defaults,user,noauto0 0 #/dev/hdd4 /zipvfatdefaults,user,noauto,uid=1000,gid=1000 0 0 The first entry is the one I use normally, but sometimes I need to mount ZIP disks from friends that are using that other OS. That's what the second entry is for. HTH Grx HdV -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Getting a Zip Drive to Work
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, Aug 06, 2003 at 06:27:41AM -0400, [EMAIL PROTECTED] wrote: Having just installed Debian (as a new Linux user) I am having problems getting my internal zip-drive to work. Mainly as I cannot figure out which device it is and becuase I need to have the edits to the fstab I need to make explained. I think all zip drives are treated as SCSI, so it would be among /dev/sd*. The Zip Drive HOWTO may be helpful... http://ursine.ca/doc/HOWTO/en-html/ZIP-Drive.html - -- .''`. Paul Johnson [EMAIL PROTECTED] : :' :proud Debian admin and user `. `'` `- Debian - when you have better things to do than fix a system -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/MN9/sClmdIs2Ki8RAmMkAJ9Q/uNUMjx2Koo/bJhl2CiuKS5ZRwCfe7k3 oKjI9Unx2Fqk3vy0zhfEeCQ= =HTnj -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Getting a Zip Drive to Work
Nope - depends on the kind of zip drive. ATAPI zip is seen as /dev/hd* unless you use ide-scsi to explicitly reassign it. To the OP: There may be an easier way to do this, but the way I do it with my ATAPI (IDE) zip drive is to look in /proc/ide/hd*/model: perrin:~# cat /proc/ide/hdd/model IOMEGA ZIP 100 ATAPI that will tell you which device it is. Alternatively, if you load ide-scsi and sr_mod, you can use scsicheck to find it. Cheers, Andy Perrin -- Andrew J Perrin - http://www.unc.edu/~aperrin Assistant Professor of Sociology, U of North Carolina, Chapel Hill [EMAIL PROTECTED] * andrew_perrin (at) unc.edu On Wed, 6 Aug 2003, Paul Johnson wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, Aug 06, 2003 at 06:27:41AM -0400, [EMAIL PROTECTED] wrote: Having just installed Debian (as a new Linux user) I am having problems getting my internal zip-drive to work. Mainly as I cannot figure out which device it is and becuase I need to have the edits to the fstab I need to make explained. I think all zip drives are treated as SCSI, so it would be among /dev/sd*. The Zip Drive HOWTO may be helpful... http://ursine.ca/doc/HOWTO/en-html/ZIP-Drive.html - -- .''`. Paul Johnson [EMAIL PROTECTED] : :' :proud Debian admin and user `. `'` `- Debian - when you have better things to do than fix a system -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/MN9/sClmdIs2Ki8RAmMkAJ9Q/uNUMjx2Koo/bJhl2CiuKS5ZRwCfe7k3 oKjI9Unx2Fqk3vy0zhfEeCQ= =HTnj -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Getting a Zip Drive to Work
Having just installed Debian (as a new Linux user) I am having problems getting my internal zip-drive to work. Mainly as I cannot figure out which device it is and becuase I need to have the edits to the fstab I need to make explained. Any help explanations would be very much appreciated. Cheers, Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Mounting 250mb Zip Drive (Internel)
Howdy; Im trying to mount my Zip drive, but its just not working. Ive tried: mount /dev/hda2 /mnt/zip1/ mount /dev/ide/ /mnt/zip1/ mount /dev/scsi/ /mnt/zip1/ mount /dev/hdb /mnt/zip1/ I was looking in the archive and found a few posts, but the hdb4 dir was not in the dev dir which was recommended by a user to use to mount the zip drive from. Post can be found here (http://lists.debian.org/debian-user/2003/debian-user-200301/msg02811.html) Its just a basic 250mb zip drive which is on the same IDE ribbon cable as the cdrom. Can anyone suggest any ideas? Thank you! Alex Togstad Web Developer [EMAIL PROTECTED] --Custom Built Servers the way you want them. Ask me for a free quote!!
Re: Mounting 250mb Zip Drive (Internel)
Alex Togstad wrote: Howdy; Im trying to mount my Zip drive, but its just not working. Ive tried: mount /dev/hda2 /mnt/zip1/ mount /dev/ide/ /mnt/zip1/ mount /dev/scsi/ /mnt/zip1/ mount /dev/hdb /mnt/zip1/ I was looking in the archive and found a few posts, but the hdb4 dir was not in the dev dir which was recommended by a user to use to mount the zip drive from. Post can be found here (http://lists.debian.org/debian-user/2003/debian-user-200301/msg02811.html) Its just a basic 250mb zip drive which is on the same IDE ribbon cable as the cdrom. Can anyone suggest any ideas? Thank you! Alex Togstad Web Developer [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] --Custom Built Servers the way you want them. Ask me for a free quote!! try using the /dev/sda, usually sda4 for logical partition. take a look at http://www.linux-usb.org/ for more info. -- /ernst -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Mounting 250mb Zip Drive (Internel)
Its just a basic 250mb zip drive which is on the same IDE ribbon cable as the cdrom. Are you using scsi-emulation? If not, then your drive will be in /dev/hddevice_numberanother_number As you say it's on the same cable as the cdrom, it will be c or d If your cd-rom is /dev/hdc, your zip will be /dev/hdd Check for messages about those devices in `dmesg` or /var/log/kernel. You'll find the wanted info over there. Now, if you have scsi-emulation... how is your cdrom device called? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
[SOLVED]RE: Mounting 250mb Zip Drive (Internel)
Mark was right, it was in /dev/hdd. So I just had to mount /dev/hdd /mnt/zip1 And it worked like a charm!! Alex Togstad Web Developer [EMAIL PROTECTED] -Original Message- From: Mark Zimmerman [mailto:[EMAIL PROTECTED] Sent: Friday, March 21, 2003 5:59 AM To: [EMAIL PROTECTED] Subject: Re: Mounting 250mb Zip Drive (Internel) On Fri, Mar 21, 2003 at 05:03:23AM -0800, Alex Togstad wrote: Howdy; I'm trying to mount my Zip drive, but its just not working. I've tried: mount /dev/hda2 /mnt/zip1/ mount /dev/ide/ /mnt/zip1/ mount /dev/scsi/ /mnt/zip1/ mount /dev/hdb /mnt/zip1/ I was looking in the archive and found a few posts, but the 'hdb4' dir was not in the dev dir which was recommended by a user to use to mount the zip drive from. Post can be found here (http://lists.debian.org/debian-user/2003/debian-user-200301/msg02811.ht ml) It's just a basic 250mb zip drive which is on the same IDE ribbon cable as the cdrom. The device is probably /dev/hdd, then, so try /dev/hdd4. Also, to see the partition table, use 'fdisk /dev/hdd' and print the table. You should be able to see hdd somewhere in dmesg. If not, you may not have built the necessary kernel modules. -- Mark -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
CDRom and zip drive don't mount
Hi everybody, I've just found cdroms won't mount - and the zip drives don't work either. These are the drives, according to the kern.log : hda: IC35L040AVER07-0, ATA DISK Drive hdb: Maxtor 2F040J0, ATA DISK Drive hdc: CRD-8482B, ATAPI CDROM drive hdd: IOMEGA ZIP 250 ATAPI, ATAPI FLOPPY drive hda: the first hard disk - which is in use by windows hdb: the second hard disk - which is where Debian Linux lives hdc: the cdrom drive hdd: ? this should be the zip drive I don't know how to get them mounted; I included the /etc/fstab file maybe something is wrong Thanks in advance, Joris Huizer __ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com fstab Description: fstab
Re: CDRom and zip drive don't mount
Hi, On Friday 17 January 2003 01:19 am, Joris Huizer wrote: I've just found cdroms won't mount - and the zip drives don't work either. What exactly happens when you try to mount them? These are the drives, according to the kern.log : hda: IC35L040AVER07-0, ATA DISK Drive hdb: Maxtor 2F040J0, ATA DISK Drive hdc: CRD-8482B, ATAPI CDROM drive hdd: IOMEGA ZIP 250 ATAPI, ATAPI FLOPPY drive In your fstab you have /dev/cdrom listed instead of /dev/hdc, is cdrom a symlink to hdc? I don't know why the zip drive doesn't work... please be a little more specific about what happens when you try to mount Cam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: CDRom and zip drive don't mount
Joris Huizer wrote: I don't know how to get them mounted; I included the /etc/fstab file maybe something is wrong Your fstab file should contain: /dev/hdc /cdrom iso9660 ro,user,noauto 0 0 for the cdrom drive. Make sure that: -You dont have ide-scsi active (in lilo.conf: append= hdc=ide-scsi) - /cdrom is an existing directory -There's a cdrom in the drive :=) /dev/hdb4 /zip auto rw,user,noauto 0 0 for the zip drive. Make sure that: -You dont have ide-scsi active (in lilo.conf: append= hdd=ide-scsi) - /zip is an existing directory -There's a filesystem on the zip disk. Note that your mount points (/cdrom, /zip) might be different. Zip disks are usually partitioned (don't know why) so that there is one partition (number 4) with all space assigned. Any output from command would help. hth, /johan Thanks in advance, Joris Huizer -- Johan Ehnberg [EMAIL PROTECTED] Windows? No... I don't think so. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: CDRom and zip drive don't mount
--- Cameron Matheson [EMAIL PROTECTED] wrote: Hi, On Friday 17 January 2003 01:19 am, Joris Huizer wrote: I've just found cdroms won't mount - and the zip drives don't work either. What exactly happens when you try to mount them? These are the drives, according to the kern.log : hda: IC35L040AVER07-0, ATA DISK Drive hdb: Maxtor 2F040J0, ATA DISK Drive hdc: CRD-8482B, ATAPI CDROM drive hdd: IOMEGA ZIP 250 ATAPI, ATAPI FLOPPY drive In your fstab you have /dev/cdrom listed instead of /dev/hdc, is cdrom a symlink to hdc? I don't know why the zip drive doesn't work... please be a little more specific about what happens when you try to mount Cam Changin /dev/cdrom to /dev/hdc solved the prob for cdroms ! :-) When I say mount /zip I get the the message mount: mount point /zip does not exist Maybe it's important to know I added the line of /dev/hdd to get it to mount myself - debian didn't add it automatically so I thought I had to add myself - maybe I have to edit more ? Thanks in advance! __ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: CDRom and zip drive don't mount
--- Johan Ehnberg [EMAIL PROTECTED] wrote: Joris Huizer wrote: I don't know how to get them mounted; I included the /etc/fstab file maybe something is wrong Your fstab file should contain: /dev/hdc /cdrom iso9660 ro,user,noauto 0 0 for the cdrom drive. Make sure that: -You dont have ide-scsi active (in lilo.conf: append= hdc=ide-scsi) - /cdrom is an existing directory -There's a cdrom in the drive :=) /dev/hdb4 /zipautorw,user,noauto 0 0 for the zip drive. Make sure that: -You dont have ide-scsi active (in lilo.conf: append= hdd=ide-scsi) - /zip is an existing directory -There's a filesystem on the zip disk. Note that your mount points (/cdrom, /zip) might be different. Zip disks are usually partitioned (don't know why) so that there is one partition (number 4) with all space assigned. Any output from command would help. hth, /johan Thanks in advance, Joris Huizer -- Johan Ehnberg [EMAIL PROTECTED] Windows? No... I don't think so. -- Cool that did it - I only had to edit on the line and add the folder - hehe these days it feels like every gets hard - thank you for helping :-) __ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
AW: CDRom and zip drive don't mount
I'm a newbie and seem to be hooked on Linux I had exactly the same question come up last night on my newly installed system. My question is: how come is this all so complicated? When I shove a Knoppix CD into my system it mounts almost everything (except the zip drive) automatically. I don't think it would be unreasonable to expect a newly installed system to list all data devices it finds and ask me whether I want to mount them. Or not?? BTW try to find the line /dev/hdb4 /zipautorw,user,noauto 0 0 which I need to mount my zip drive in the documentation. I couldn't find it in the instalation manual, or was I looking in the wrong places? But I'm learning... Christof Dr.-Ing. Christof Hurschler (Ph.D.) Labor fur Biomechanik und Experimentelle Orthopadie Orthopadische Klinik der MHH Anna-von-Borries-Str. 1-7 D-30625 Hannover +49-0511-5354-647 Voice +49-0511-5354-343 Fax +49-172-5946-909 Mobile mailto:[EMAIL PROTECTED] -Ursprungliche Nachricht- Von: Johan Ehnberg [mailto:[EMAIL PROTECTED]] Gesendet: Freitag, 17. Januar 2003 10:34 An: Joris Huizer Cc: debian user Betreff: Re: CDRom and zip drive don't mount Joris Huizer wrote: I don't know how to get them mounted; I included the /etc/fstab file maybe something is wrong Your fstab file should contain: /dev/hdc /cdrom iso9660 ro,user,noauto 0 0 for the cdrom drive. Make sure that: -You dont have ide-scsi active (in lilo.conf: append= hdc=ide-scsi) - /cdrom is an existing directory -There's a cdrom in the drive :=) /dev/hdb4 /zipautorw,user,noauto 0 0 for the zip drive. Make sure that: -You dont have ide-scsi active (in lilo.conf: append= hdd=ide-scsi) - /zip is an existing directory -There's a filesystem on the zip disk. Note that your mount points (/cdrom, /zip) might be different. Zip disks are usually partitioned (don't know why) so that there is one partition (number 4) with all space assigned. Any output from command would help. hth, /johan Thanks in advance, Joris Huizer -- Johan Ehnberg [EMAIL PROTECTED] Windows? No... I don't think so. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: CDRom and zip drive don't mount
Joris == Joris Huizer [EMAIL PROTECTED] writes: Joris When I say mount /zip I get the the message mount: mount Joris point /zip does not exist Does 'ls /zip' say zip does not exist too? In that case, just create it. 'mkdir /zip' and go. Joris Maybe it's important to know I added the line of /dev/hdd Joris to get it to mount myself - debian didn't add it Joris automatically so I thought I had to add myself - maybe I Joris have to edit more ? The mount points must exist for you to mount a device. The device file must exist, and the device must be available, for you to mount a device to a mount point. Pretty simple once you get the hang of it ;-) Cheers! Shyamal -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: AW: CDRom and zip drive don't mount
Christof == hurschler [EMAIL PROTECTED] writes: Christof My question is: how come is this all so complicated? Christof When I shove a Knoppix CD into my system it mounts Christof almost everything (except the zip drive) automatically. Christof I don't think it would be unreasonable to expect a newly Christof installed system to list all data devices it finds and Christof ask me whether I want to mount them. Or not?? Yes and no. Some people like automatic detection, they chose distributions like Knoppix, Mandrake, Lindows etc. Some people prefer not to have the automatic detection because (a) it makes it impossible to install on some hardware and (b) it does not detect some hardware correctly. Debian seems designed to better support the second class of users. It is all about choices, and the observation that you can't keep all people happy all the time ;-) Cheers! Shyamal -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
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 ?
Iomega Zip drive USB
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. 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 ? -- Michel COURT LSIS Domaine Universitaire de Saint Jerome 13397 Marseille cedex 20 tel: +33 4 91 05 60 45 fax : +33 4 91 05 60 33 email : [EMAIL PROTECTED]
Re: kernel need to be reconfigured for Zip drive ?
O This is a weird behavior because I have another zip drive and it works without any addition work on another machine. Must be different models or soemthing. Do you have CD burner in this machine, but not in the other? Yes, both machines have exact same cdrw's . Just the zip drive are different models. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: kernel need to be reconfigured for Zip drive ?
On Tue, Oct 15, 2002 at 04:01:37PM -0400, ThanhVu Nguyen wrote: Hello, I just bought a Zip 100 IDE drive. I am running kernel 2.4.19 with scsi emulation support for cdrom. Just wondering if I need to turn on any options to have it support the Zip drive. dmesg says the zip is under hdd , I tried mount -t vfat -l /dev/hdd4 and mount -t vfat -l /dev/hdd have these messages I have a similar configuration (zip drive in hdd, and scsi emulation) add this to the boot command line: hdd=ide-floppy (this is to avoid the ide-scsi emulation reclaim the zip drive) and use hdd4 to mount the drive (e.g. mount /dev/hdd4 /zip) HTH -- German Garcia | Debian GNU/Linux [EMAIL PROTECTED] | vi - c - c++ Buenos Aires, Argentina | Barrio de Tango -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: kernel need to be reconfigured for Zip drive ?
Hello, I finally got it to work ... by enable SCSI disk support on the kernel (sr_mod), then the device becomes /dev/sda4. I never thought of this since the drive I have is not SCSI. I did try to recompile kernel with ide-floppy but same result, it doesn't work either. Now that it works .. I am happy. Thanks for all your inputs. This is a weird behavior because I have another zip drive and it works without any addition work on another machine. Must be different models or soemthing. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
kernel need to be reconfigured for Zip drive ?
Hello, I just bought a Zip 100 IDE drive. I am running kernel 2.4.19 with scsi emulation support for cdrom. Just wondering if I need to turn on any options to have it support the Zip drive. dmesg says the zip is under hdd , I tried mount -t vfat -l /dev/hdd4 and mount -t vfat -l /dev/hdd have these messages wrong fs type, bad option, bad superblock on /dev/hdd, or too many mounted file systems (could this be the IDE device where you in fact use ide-scsi so that sr0 or sda or so is needed?) in dmseg, my cdrw is under hdc but it is actually scd0. So could the zip drive has some other names under /dev ? -- ThanhVu Nguyen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: kernel need to be reconfigured for Zip drive ?
On Tue, 2002-10-15 at 15:01, ThanhVu Nguyen wrote: Hello, I just bought a Zip 100 IDE drive. I am running kernel 2.4.19 with scsi emulation support for cdrom. Just wondering if I need to turn on any options to have it support the Zip drive. dmesg says the zip is under hdd , I tried mount -t vfat -l /dev/hdd4 and mount -t vfat -l /dev/hdd have these messages wrong fs type, bad option, bad superblock on /dev/hdd, or too many mounted file systems (could this be the IDE device where you in fact use ide-scsi so that sr0 or sda or so is needed?) in dmseg, my cdrw is under hdc but it is actually scd0. So could the zip drive has some other names under /dev ? You shouldn't need to recompile anything. Just try: mount -t vfat /dev/hdd4 /mnt/zip substituting /mnt/zip for wherever you want to mount it of course. The 4 is the important part. -Alex signature.asc Description: This is a digitally signed message part
Re: kernel need to be reconfigured for Zip drive ?
On Tue, 15 Oct 2002 17:27:18 -0400 Bruce Best (CRO) [EMAIL PROTECTED] wrote: Did you try /dev/sdd?? Hello, I get ... # mount /dev/sdd /zip/ mount: /dev/sdd is not a valid block device Any ideas ? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: kernel need to be reconfigured for Zip drive ?
On 15 Oct 2002 16:27:18 -0500 Alex Malinovich [EMAIL PROTECTED] wrote: On Tue, 2002-10-15 at 15:01, ThanhVu Nguyen wrote: Hello, I just bought a Zip 100 IDE drive. I am running kernel 2.4.19 with scsi emulation support for cdrom. Just wondering if I need to turn on any options to have it support the Zip drive. dmesg says the zip is under hdd , I tried mount -t vfat -l /dev/hdd4 and mount -t vfat -l /dev/hdd have these messages wrong fs type, bad option, bad superblock on /dev/hdd, or too many mounted file systems (could this be the IDE device where you in fact use ide-scsi so that sr0 or sda or so is needed?) in dmseg, my cdrw is under hdc but it is actually scd0. So could the zip drive has some other names under /dev ? You shouldn't need to recompile anything. Just try: mount -t vfat /dev/hdd4 /mnt/zip substituting /mnt/zip for wherever you want to mount it of course. The 4 is the important part. -Alex Hello, it still gives the same msg . # mount -t vfat /dev/hdd4 /zip mount: wrong fs type, bad option, bad superblock on /dev/hdd4, or too many mounted file systems (could this be the IDE device where you in fact use ide-scsi so that sr0 or sda or so is needed?) Any other ideas ? -- ThanhVu Nguyen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: kernel need to be reconfigured for Zip drive ?
On Wed, 2002-10-16 at 03:17, ThanhVu Nguyen wrote: On Tue, 15 Oct 2002 17:27:18 -0400 Bruce Best (CRO) [EMAIL PROTECTED] wrote: Did you try /dev/sdd?? Hello, I get ... # mount /dev/sdd /zip/ mount: /dev/sdd is not a valid block device Any ideas ? Usually, only the 4th partition on a Zip disc is formatted. Try /dev/sd?4. Replace the ? with the appropriate letter. Just run 'fdisk -l /dev/sd?'. -- Claudio Bley ASCII ribbon campaign () Debian GNU/Linux advocate - against HTML email X http://www.cs.uni-magdeburg.de/~bley/ vCards / \ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: kernel need to be reconfigured for Zip drive ?
On Tue, 2002-10-15 at 18:18, ThanhVu Nguyen wrote: On 15 Oct 2002 16:27:18 -0500 Alex Malinovich [EMAIL PROTECTED] wrote: On Tue, 2002-10-15 at 15:01, ThanhVu Nguyen wrote: Hello, I just bought a Zip 100 IDE drive. I am running kernel 2.4.19 with scsi emulation support for cdrom. Just wondering if I need to turn on any options to have it support the Zip drive. dmesg says the zip is under hdd , I tried mount -t vfat -l /dev/hdd4 and mount -t vfat -l /dev/hdd have these messages wrong fs type, bad option, bad superblock on /dev/hdd, or too many mounted file systems (could this be the IDE device where you in fact use ide-scsi so that sr0 or sda or so is needed?) in dmseg, my cdrw is under hdc but it is actually scd0. So could the zip drive has some other names under /dev ? You shouldn't need to recompile anything. Just try: mount -t vfat /dev/hdd4 /mnt/zip substituting /mnt/zip for wherever you want to mount it of course. The 4 is the important part. -Alex Hello, it still gives the same msg . # mount -t vfat /dev/hdd4 /zip mount: wrong fs type, bad option, bad superblock on /dev/hdd4, or too many mounted file systems (could this be the IDE device where you in fact use ide-scsi so that sr0 or sda or so is needed?) I mount my Zip drive with mount -t vfat /dev/sda4 /mnt/zip Any other ideas ? -- ThanhVu Nguyen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Zip-Drive
Olá para todos, POssuo um Zip-drive interno IDE/ATApi...como eu faço para configura-lo no Linux, estou usando Woody. Tentei monta-lo como se fosse um dispositivo IDE normal e não funcionou. Utilizei o seguinte comando: mount -t vfat /dev/hdd /mnt/zip e apareceu a seguinte mensagem: mount: /dev/hdd4 is not a valid block device Alguém tem idéia do que esta ocorrendo??? Abraços a todos, Sergio
Re: Zip-Drive
Olá, On Fri, Aug 02, 2002 at 05:16:22PM -0300, Sergio Ricardo Milare wrote: Olá para todos, dispositivo IDE normal e não funcionou. Utilizei o seguinte comando: mount -t vfat /dev/hdd /mnt/zip e apareceu a seguinte mensagem: mount: /dev/hdd4 is not a valid block device Alguém tem idéia do que esta ocorrendo??? Possuo um destes; o único driver que tenho carregado é o ide-floppy. ~$ cat /proc/ide/hdd/driver ide-floppy version 0.97.sv Tente carregar este driver antes de mountar o zip. -- Mario O.de Menezes, Ph.D. Many are the plans in a man's heart, but IPEN-CNEN/SP is the Lord's purpose that prevails http://curiango.ipen.br/~mario Prov. 19.21
Re: iomega parallel port zip drive
On Saturday 08 June 2002 06:56 pm, robert jorgenson wrote: I tried it with the imm module but it did the same thing as the ppa module ... chimera:/home/bob# modprobe imm /lib/modules/2.4.18/kernel/drivers/scsi/imm.o: init_module: No such device Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters /lib/modules/2.4.18/kernel/drivers/scsi/imm.o: insmod /lib/modules/2.4.18/kernel/drivers/scsi/imm.o failed /lib/modules/2.4.18/kernel/drivers/scsi/imm.o: insmod imm failed chimera:/home/bob# I know i must be doing something wrong ... iv attatched the .config im using for my kernel in case anyone spots something i have done wrong try recompiling the kernel without the athlon optimimization, as a straight i386. ben -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: iomega parallel port zip drive
If i did this why not just get a kernel image from debian? Unless im really trying to keep my kernel footprint small which doesn't really matter much. I first wanted to compile just to know i could :) But now i want to get it to work :) i will try this though. On Sun, 9 Jun 2002 00:41:57 -0700 ben [EMAIL PROTECTED] wrote: On Saturday 08 June 2002 06:56 pm, robert jorgenson wrote: I tried it with the imm module but it did the same thing as the ppa module ... chimera:/home/bob# modprobe imm /lib/modules/2.4.18/kernel/drivers/scsi/imm.o: init_module: No such device Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters /lib/modules/2.4.18/kernel/drivers/scsi/imm.o: insmod /lib/modules/2.4.18/kernel/drivers/scsi/imm.o failed /lib/modules/2.4.18/kernel/drivers/scsi/imm.o: insmod imm failed chimera:/home/bob# I know i must be doing something wrong ... iv attatched the .config im using for my kernel in case anyone spots something i have done wrong try recompiling the kernel without the athlon optimimization, as a straight i386. ben -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: iomega parallel port zip drive
Nope compiling with i386 didn't work either, same error when i try and load the module On Sun, 9 Jun 2002 00:41:57 -0700 ben [EMAIL PROTECTED] wrote: On Saturday 08 June 2002 06:56 pm, robert jorgenson wrote: I tried it with the imm module but it did the same thing as the ppa module ... chimera:/home/bob# modprobe imm /lib/modules/2.4.18/kernel/drivers/scsi/imm.o: init_module: No such device Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters /lib/modules/2.4.18/kernel/drivers/scsi/imm.o: insmod /lib/modules/2.4.18/kernel/drivers/scsi/imm.o failed /lib/modules/2.4.18/kernel/drivers/scsi/imm.o: insmod imm failed chimera:/home/bob# I know i must be doing something wrong ... iv attatched the .config im using for my kernel in case anyone spots something i have done wrong try recompiling the kernel without the athlon optimimization, as a straight i386. ben -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [SOLVED]iomega parallel port zip drive
Okay i dont know EXACTLY what it was, but i went through EVERY SINGLE option and red almost every single help on each section and turned off a few things ... for some reason smp was enabled i turned that off, some random onboard ethernet driver was enabled. I cant remember everything cuz ive been up for about 36 hours working on this =/ but ill attatch the new .config if soemone realy wants to go through and find out what might have changed it have at it :) FYI it works just fine with /dev/sda4 /zip auto defaults,noauto 0 0 in my /etc/fstab so i dont have to pass -t vfat to it On Fri, 7 Jun 2002 21:13:53 -0700 robert jorgenson [EMAIL PROTECTED] wrote: Ok i had this working fine under my 2.2 distrobution kernel(debian) with modprobe ppa. i Decided to compile a 2.4 kernel and i an trying to get it to work correctly. Right now i have scsi support enabled, scsi disk support enabled, the ppa module compiled in as a module, and parallel printing enabled as a module(as per the zip drive mini-hwoto). When i try to mount /dev/sda4 it says that /dev/sda4 is not a valid block device. I have kernel compiled about 6 times tonight and i would really like next time to be last time, at least for tonight :) andone know what might be wrong? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] config Description: Binary data
Re: iomega parallel port zip drive
On Sunday 09 June 2002 07:12 am, robert jorgenson wrote: If i did this why not just get a kernel image from debian? Unless im really trying to keep my kernel footprint small which doesn't really matter much. I first wanted to compile just to know i could :) But now i want to get it to work :) i will try this though. i've found that the cpu optimization in kernels prior to 2.4.17 created a conflict that prevented usb ports being recognized. when i went with i386, the conflict disappeared. since the athlon optimization is relatively new, it's possible that it's contributing to the problem you're having--that's all. if you can't get the most basic cpu configuration to work, then it's more likely to be a device configuration problem. ben -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
iomega parallel port zip drive
Ok i had this working fine under my 2.2 distrobution kernel(debian) with modprobe ppa. i Decided to compile a 2.4 kernel and i an trying to get it to work correctly. Right now i have scsi support enabled, scsi disk support enabled, the ppa module compiled in as a module, and parallel printing enabled as a module(as per the zip drive mini-hwoto). When i try to mount /dev/sda4 it says that /dev/sda4 is not a valid block device. I have kernel compiled about 6 times tonight and i would really like next time to be last time, at least for tonight :) andone know what might be wrong? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: iomega parallel port zip drive
On Friday 07 June 2002 09:13 pm, robert jorgenson wrote: Ok i had this working fine under my 2.2 distrobution kernel(debian) with modprobe ppa. i Decided to compile a 2.4 kernel and i an trying to get it to work correctly. Right now i have scsi support enabled, scsi disk support enabled, the ppa module compiled in as a module, and parallel printing enabled as a module(as per the zip drive mini-hwoto). When i try to mount /dev/sda4 it says that /dev/sda4 is not a valid block device. I have kernel compiled about 6 times tonight and i would really like next time to be last time, at least for tonight :) andone know what might be wrong? i'm not sure if the situation is exactly the same as in my case, but since the switch from a 2.2 to the 2.4 kernel, i have to use a full mount command specifying the fstype to get the zip drive up, as in: mount -tfstype (e.g. vfat or ext2) /dev/sda4 /zip as opposed to previously using a simple mount /zip, even though the fstab entry for the /zip drive is auto /dev/sda4 /zipautodefaults,rw,users,noauto0 0 i have ppa support complied into the kernel. ben -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: iomega parallel port zip drive
On Fri, Jun 07, 2002 at 10:57:33PM -0700, ben wrote: On Friday 07 June 2002 09:13 pm, robert jorgenson wrote: HI, enabled as a module(as per the zip drive mini-hwoto). When i try to mount /dev/sda4 it says that /dev/sda4 is not a valid block device. I have kernel compiled about 6 times tonight and i would really like next time to be last time, at least for tonight :) andone know what might be wrong? i'm not sure if the situation is exactly the same as in my case, but since the switch from a 2.2 to the 2.4 kernel, i have to use a full mount command specifying the fstype to get the zip drive up, as in: mount -tfstype (e.g. vfat or ext2) /dev/sda4 /zip as opposed to previously using a simple mount /zip, even though the fstab entry for the /zip drive is auto /dev/sda4 /zipautodefaults,rw,users,noauto0 0 i have ppa support complied into the kernel. I don't know the source of the problem but if you load the ext2 or vfat module by hand or via /etc/modules you should be able to use a mount /zip command. Sven -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: iomega parallel port zip drive
I am also switching from 2.2 to 2.4 kernel but i cant mount it at all, even with the fstype. I have read almost eveything i could find and i cant get it to work =/ On Fri, 7 Jun 2002 22:57:33 -0700 ben [EMAIL PROTECTED] wrote: On Friday 07 June 2002 09:13 pm, robert jorgenson wrote: Ok i had this working fine under my 2.2 distrobution kernel(debian) with modprobe ppa. i Decided to compile a 2.4 kernel and i an trying to get it to work correctly. Right now i have scsi support enabled, scsi disk support enabled, the ppa module compiled in as a module, and parallel printing enabled as a module(as per the zip drive mini-hwoto). When i try to mount /dev/sda4 it says that /dev/sda4 is not a valid block device. I have kernel compiled about 6 times tonight and i would really like next time to be last time, at least for tonight :) andone know what might be wrong? i'm not sure if the situation is exactly the same as in my case, but since the switch from a 2.2 to the 2.4 kernel, i have to use a full mount command specifying the fstype to get the zip drive up, as in: mount -tfstype (e.g. vfat or ext2) /dev/sda4 /zip as opposed to previously using a simple mount /zip, even though the fstab entry for the /zip drive is auto /dev/sda4 /zipautodefaults,rw,users,noauto0 0 i have ppa support complied into the kernel. ben -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: iomega parallel port zip drive
On Saturday 08 June 2002 02:14 am, robert jorgenson wrote: I am also switching from 2.2 to 2.4 kernel but i cant mount it at all, even with the fstype. I have read almost eveything i could find and i cant get it to work =/ [snip] try this to see if the ppa module is doing what it should: $ dmesg | grep ppa i get the following: ppa: Version 2.07 (for Linux 2.4.x) ppa: Found device at ID 6, Attempting to use EPP 16 bit ppa: Found device at ID 6, Attempting to use SPP ppa: Communication established with ID 6 using SPP scsi1 : Iomega VPI0 (ppa) interface ben -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: iomega parallel port zip drive
i get ... ppa: Version 2.07 (for Linux 2.4.x) ppa: parport reports no devices. when i try and mobprobe ppa i get the following ... chimera:/usr/local# modprobe ppa /lib/modules/2.4.18/kernel/drivers/scsi/ppa.o: init_module: No such device Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters /lib/modules/2.4.18/kernel/drivers/scsi/ppa.o: insmod /lib/modules/2.4.18/kernel/drivers/scsi/ppa.o failed /lib/modules/2.4.18/kernel/drivers/scsi/ppa.o: insmod ppa failed chimera:/usr/local# Im assuming this is something i did wrong because ppa works perfectly with a stock kernel image from debian. Any ideas? On Sat, 8 Jun 2002 02:52:12 -0700 ben [EMAIL PROTECTED] wrote: On Saturday 08 June 2002 02:14 am, robert jorgenson wrote: I am also switching from 2.2 to 2.4 kernel but i cant mount it at all, even with the fstype. I have read almost eveything i could find and i cant get it to work =/ [snip] try this to see if the ppa module is doing what it should: $ dmesg | grep ppa i get the following: ppa: Version 2.07 (for Linux 2.4.x) ppa: Found device at ID 6, Attempting to use EPP 16 bit ppa: Found device at ID 6, Attempting to use SPP ppa: Communication established with ID 6 using SPP scsi1 : Iomega VPI0 (ppa) interface ben -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: iomega parallel port zip drive
On Saturday 08 June 2002 02:49 am, robert jorgenson wrote: i get ... ppa: Version 2.07 (for Linux 2.4.x) ppa: parport reports no devices. when i try and mobprobe ppa i get the following ... chimera:/usr/local# modprobe ppa /lib/modules/2.4.18/kernel/drivers/scsi/ppa.o: init_module: No such device Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters /lib/modules/2.4.18/kernel/drivers/scsi/ppa.o: insmod /lib/modules/2.4.18/kernel/drivers/scsi/ppa.o failed /lib/modules/2.4.18/kernel/drivers/scsi/ppa.o: insmod ppa failed chimera:/usr/local# Im assuming this is something i did wrong because ppa works perfectly with a stock kernel image from debian. Any ideas? how about recompiling the kernel so that ppa is configured into it, rather than run as a module? it has always worked for me and, personally, i think dealing with modules to configure a device that i make regular use of is an unecessary pain that i'd rather avoid. ben -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: iomega parallel port zip drive
I have tried it compiled in but i got the same invalid block device error, And the same message in dmesg finding no scsi hosts. And also before anyone asks everything is plugeed in right and there is a disk in there :) I cant imagine what is wrong ... On Sat, 8 Jun 2002 03:07:45 -0700 ben [EMAIL PROTECTED] wrote: On Saturday 08 June 2002 02:49 am, robert jorgenson wrote: i get ... ppa: Version 2.07 (for Linux 2.4.x) ppa: parport reports no devices. when i try and mobprobe ppa i get the following ... chimera:/usr/local# modprobe ppa /lib/modules/2.4.18/kernel/drivers/scsi/ppa.o: init_module: No such device Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters /lib/modules/2.4.18/kernel/drivers/scsi/ppa.o: insmod /lib/modules/2.4.18/kernel/drivers/scsi/ppa.o failed /lib/modules/2.4.18/kernel/drivers/scsi/ppa.o: insmod ppa failed chimera:/usr/local# Im assuming this is something i did wrong because ppa works perfectly with a stock kernel image from debian. Any ideas? how about recompiling the kernel so that ppa is configured into it, rather than run as a module? it has always worked for me and, personally, i think dealing with modules to configure a device that i make regular use of is an unecessary pain that i'd rather avoid. ben -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: iomega parallel port zip drive
On Saturday 08 June 2002 03:11 am, robert jorgenson wrote: I have tried it compiled in but i got the same invalid block device error, And the same message in dmesg finding no scsi hosts. And also before anyone asks everything is plugeed in right and there is a disk in there :) I cant imagine what is wrong ... you might want to study /var/log/kern.log to see if it gives any information about source compilation bugs that could cause the ppa error. ben -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: iomega parallel port zip drive
On Fri, Jun 07, 2002 at 09:13:53PM -0700, robert jorgenson wrote: Ok i had this working fine under my 2.2 distrobution kernel(debian) with modprobe ppa. i Decided to compile a 2.4 kernel and i an trying to get it to work correctly. Right now i have scsi support enabled, scsi disk support enabled, the ppa module compiled in as a module, and parallel printing enabled as a module(as per the zip drive mini-hwoto). When i try to mount /dev/sda4 it says that /dev/sda4 is not a valid block device. I have kernel compiled about 6 times tonight and i would really like next time to be last time, at least for tonight :) andone know what might be wrong? I had no trouble at all when I switched to 2.4 with a parallel port zip drive. However, I'm using the imm module instead of the ppa. Are you sure your drive is too old for imm? -- Mark pgp78abDgPNRX.pgp Description: PGP signature
Re: iomega parallel port zip drive
On Sat, Jun 08, 2002 at 03:11:25AM -0700, robert jorgenson wrote: I have tried it compiled in but i got the same invalid block device error, And the same message in dmesg finding no scsi hosts. And also before anyone asks everything is plugeed in right and there is a disk in there :) I cant imagine what is wrong ... On Sat, 8 Jun 2002 03:07:45 -0700 ben [EMAIL PROTECTED] wrote: On Saturday 08 June 2002 02:49 am, robert jorgenson wrote: i get ... ppa: Version 2.07 (for Linux 2.4.x) ppa: parport reports no devices. when i try and mobprobe ppa i get the following ... chimera:/usr/local# modprobe ppa /lib/modules/2.4.18/kernel/drivers/scsi/ppa.o: init_module: No such device Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters /lib/modules/2.4.18/kernel/drivers/scsi/ppa.o: insmod /lib/modules/2.4.18/kernel/drivers/scsi/ppa.o failed /lib/modules/2.4.18/kernel/drivers/scsi/ppa.o: insmod ppa failed chimera:/usr/local# Im assuming this is something i did wrong because ppa works perfectly with a stock kernel image from debian. Any ideas? Hi Robert, for me it works. It takes the following modules: parport, parport_pc, scsi_mod, sd_mod, imm. (It says that imm is for more recent drives, while ppa is for older ones.) On my system I can simply do: modprobe imm mount -t msdos /dev/sda4 /zip , but you can try to modprobe each module separately. BTW, what file system do you use on your ZIP? Regards, Joachim -- Joachim Fahnenmüller Lehrer für Mathematik und Physik Herder-Gymnasium Kattowitzer Straße 52 51065 Köln -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: iomega parallel port zip drive
I tried it with the imm module but it did the same thing as the ppa module ... chimera:/home/bob# modprobe imm /lib/modules/2.4.18/kernel/drivers/scsi/imm.o: init_module: No such device Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters /lib/modules/2.4.18/kernel/drivers/scsi/imm.o: insmod /lib/modules/2.4.18/kernel/drivers/scsi/imm.o failed /lib/modules/2.4.18/kernel/drivers/scsi/imm.o: insmod imm failed chimera:/home/bob# I know i must be doing something wrong ... iv attatched the .config im using for my kernel in case anyone spots something i have done wrong On Sat, 8 Jun 2002 23:25:35 +0200 Joachim Fahnenmueller [EMAIL PROTECTED] wrote: On Sat, Jun 08, 2002 at 03:11:25AM -0700, robert jorgenson wrote: I have tried it compiled in but i got the same invalid block device error, And the same message in dmesg finding no scsi hosts. And also before anyone asks everything is plugeed in right and there is a disk in there :) I cant imagine what is wrong ... On Sat, 8 Jun 2002 03:07:45 -0700 ben [EMAIL PROTECTED] wrote: On Saturday 08 June 2002 02:49 am, robert jorgenson wrote: i get ... ppa: Version 2.07 (for Linux 2.4.x) ppa: parport reports no devices. when i try and mobprobe ppa i get the following ... chimera:/usr/local# modprobe ppa /lib/modules/2.4.18/kernel/drivers/scsi/ppa.o: init_module: No such device Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters /lib/modules/2.4.18/kernel/drivers/scsi/ppa.o: insmod /lib/modules/2.4.18/kernel/drivers/scsi/ppa.o failed /lib/modules/2.4.18/kernel/drivers/scsi/ppa.o: insmod ppa failed chimera:/usr/local# Im assuming this is something i did wrong because ppa works perfectly with a stock kernel image from debian. Any ideas? Hi Robert, for me it works. It takes the following modules: parport, parport_pc, scsi_mod, sd_mod, imm. (It says that imm is for more recent drives, while ppa is for older ones.) On my system I can simply do: modprobe imm mount -t msdos /dev/sda4 /zip , but you can try to modprobe each module separately. BTW, what file system do you use on your ZIP? Regards, Joachim -- Joachim Fahnenmüller Lehrer für Mathematik und Physik Herder-Gymnasium Kattowitzer Straße 52 51065 Köln -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] config Description: Binary data
Re: IDE-SCSI, CD-RW, ZIP drive weirdness
On Thu, Apr 18, 2002 at 08:39:47PM -0700, Warren Dodge wrote: If you have another ATAPI CD-ROM, you would want to add this line to your /etc/modutils/aliases file and run update-modules: pre-install ide-scsi modprobe ide-cd This causes the IDE driver to load before ide-scsi. It then takes control of the ATAPID CD-ROM -- anything that it hasn't been told to ignore. That leaves just the ignored devices for ide-scsi to control. I'm not sure if it's the same thing for an ATAPI zip drive, but you might want to give it a shot. Thanks, that's a neat trick. -rob -- I did not vote for the Australian government. pgpVezUQqgmC6.pgp Description: PGP signature
Re: IDE-SCSI, CD-RW, ZIP drive weirdness
On Sun, Apr 14, 2002 at 08:14:54PM -0600, Troy Telford wrote: I have an ATAPI CD-RW installed as the second slave (/dev/hdd). According to the documentation I've read, to use the CD-RW in Linux, I have to use IDE-SCSI (kernel) and have 'hdd=scsi' in the boot parameters. I've done this, and I have no problems using the drive, but I have discovered somthing... odd. I have an ATAPI ZIP-100 on /dev/hdb (first slave). I am not telling the kernel to use IDE-SCSI for it (boot parameters), yet IDE-SCSI takes control of the ZIP-100. And, the ZIP-100 works great under the IDE-SCSI driver. (Since I run DevFS, it's interesting to note that this gets rid of any problems I've had and read about when using the ZIP-100 and DevFs). My only beef is that I don't believe I configured Linux to do this (although it was a pleasent surprise), and am wondering if this is a bug of some kind to be reported. (Or, if this is a little unknown workaround for ZIP drives DevFS). I have this exact same 'issue' with almost the same hardware. As far as I can tell, when the ide-scsi module is loaded, it takes control of all non-harddisk IDE devices on the system. I think there's a work around, but I can't for the life of me remember it. If it doesn't bother you, I'd just leave it. Oh yeah, there were a couple of other things, (all good:): * You can use tools like jazip (for your zip drive) that only understand SCSI. * Apparently some cd-rom drives can perform DAE (digital audio extraction, ie rip) cds quicker with ide-scsi enabled! -rob -- I did not vote for the Australian government. pgpJWQmW1qtiL.pgp Description: PGP signature
Re: IDE-SCSI, CD-RW, ZIP drive weirdness
If you have another ATAPI CD-ROM, you would want to add this line to your /etc/modutils/aliases file and run update-modules: pre-install ide-scsi modprobe ide-cd This causes the IDE driver to load before ide-scsi. It then takes control of the ATAPID CD-ROM -- anything that it hasn't been told to ignore. That leaves just the ignored devices for ide-scsi to control. I'm not sure if it's the same thing for an ATAPI zip drive, but you might want to give it a shot. Warren On Wednesday, April 17 2002 02:39, Rob Weir wrote: I have this exact same 'issue' with almost the same hardware. As far as I can tell, when the ide-scsi module is loaded, it takes control of all non-harddisk IDE devices on the system. I think there's a work around, but I can't for the life of me remember it. If it doesn't bother you, I'd just leave it. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
IDE-SCSI, CD-RW, ZIP drive weirdness
I have an ATAPI CD-RW installed as the second slave (/dev/hdd). According to the documentation I've read, to use the CD-RW in Linux, I have to use IDE-SCSI (kernel) and have 'hdd=scsi' in the boot parameters. I've done this, and I have no problems using the drive, but I have discovered somthing... odd. I have an ATAPI ZIP-100 on /dev/hdb (first slave). I am not telling the kernel to use IDE-SCSI for it (boot parameters), yet IDE-SCSI takes control of the ZIP-100. And, the ZIP-100 works great under the IDE-SCSI driver. (Since I run DevFS, it's interesting to note that this gets rid of any problems I've had and read about when using the ZIP-100 and DevFs). My only beef is that I don't believe I configured Linux to do this (although it was a pleasent surprise), and am wondering if this is a bug of some kind to be reported. (Or, if this is a little unknown workaround for ZIP drives DevFS). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
