Re: Trouble mounting Zip drive (solved!)
[snip] Hi and thanks for all help! Seems like I have found a sollution (thanks to this excellent tutorial http://freebsd.peon.net/tutorials/10/ and the help from the mailinglist members): One thing: I still don't understand how I should know that the device is rda0 or rda0c or even da0 sometimes in the example below. If someone could explain I'd be happy :-) # dd if=/dev/zero of=/dev/rda0 count=2 2+0 records in 2+0 records out 1024 bytes transferred in 0.040405 secs (25343 bytes/sec) # disklabel -Brw da0 auto # newfs /dev/rda0c Warning: Block size restricts cylinders per group to 97. /dev/rda0c: 196608 sectors in 48 cylinders of 1 tracks, 4096 sectors 96.0MB in 1 cyl groups (97 c/g, 194.00MB/g, 12288 i/g) super-block backups (for fsck -b #) at: 32 # mount /dev/da0c /zip # df -h FilesystemSize Used Avail Capacity Mounted on /dev/ad0s1a 126M35M81M30%/ /dev/ad0s1f 252M22K 232M 0%/tmp /dev/ad0s1g 5.1G 760M 3.9G16%/usr /dev/ad0s1e 252M 2.9M 229M 1%/var /dev/ad1s1e 3.0G 405M 2.3G14%/backup procfs4.0K 4.0K 0B 100%/proc /dev/da0c 94M 2.0K87M 0%/zip Best regards, Andreas --- Andreas Wideroe Andersen [EMAIL PROTECTED] Mobile: (+47) 90 92 61 21 http://www.filmshooting.com Norsk Smalfilm AS http://www.smalfilm.no ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Trouble mounting Zip drive (solved!)
* Andreas Widerøe Andersen [2005-07-06 10:42 +0200] Hi and thanks for all help! Seems like I have found a sollution (thanks to this excellent tutorial http://freebsd.peon.net/tutorials/10/ and the help from the mailinglist members): I didn't follow this thread from the beginning, so I'm not sure if this was ever an issue, or if it has been discussed. But when I used ZIP disks some two to three years ago, I had some issues with password-protected and read-only disks. I found a solution for that sending raw commands to the device using camcontrol. If you're interested, I could try to dig up my notes on the matter. At that time there was no command line utilities I could find that would set these bits on the disks. Regadrs, Svein Halvor ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Trouble mounting Zip drive
Hi, I'm having problems mounting a SCSI Iomega 100 Zip drive on my 4.11 RELEASE system: - From boot, this is what I see: da0 at ncr0 bus 0 target 5 lun 0 da0: IOMEGA ZIP 100 E.08 Removable Direct Access SCSI-2 device da0: 3.300MB/s transfers da0: 96MB (196608 512 byte sectors: 64H 32S/T 96C) - In my /etc/fstab i have this line: /dev/da0s4 /zipufs rw,noauto 0 0 I have mkdir a /zip directory This is the problem: $ mount /zip mount: /dev/da0s4: Operation not permitted I have tried many things now, but can't make things work. Any suggestion to what I do wrong? Thanks! Andreas --- Andreas Wideroe Andersen [EMAIL PROTECTED] Mobile: (+47) 90 92 61 21 http://www.filmshooting.com Norsk Smalfilm AS http://www.smalfilm.no ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Trouble mounting Zip drive
On Tue, 05 Jul 2005 17:14:50 +0200 Andreas Widerøe Andersen [EMAIL PROTECTED] wrote: Hi, I'm having problems mounting a SCSI Iomega 100 Zip drive on my 4.11 RELEASE system: - From boot, this is what I see: da0 at ncr0 bus 0 target 5 lun 0 da0: IOMEGA ZIP 100 E.08 Removable Direct Access SCSI-2 device da0: 3.300MB/s transfers da0: 96MB (196608 512 byte sectors: 64H 32S/T 96C) - In my /etc/fstab i have this line: /dev/da0s4 /zipufs rw,noauto 0 0 I have mkdir a /zip directory This is the problem: $ mount /zip mount: /dev/da0s4: Operation not permitted did you try mounting it as root ? (and what does /var/log/messages /var/log/dmesg say about it ?) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Trouble mounting Zip drive
At 17:19 05.07.2005, [EMAIL PROTECTED] wrote: On Tue, 05 Jul 2005 17:14:50 +0200 Andreas Widerøe Andersen [EMAIL PROTECTED] wrote: Hi, I'm having problems mounting a SCSI Iomega 100 Zip drive on my 4.11 RELEASE system: - From boot, this is what I see: da0 at ncr0 bus 0 target 5 lun 0 da0: IOMEGA ZIP 100 E.08 Removable Direct Access SCSI-2 device da0: 3.300MB/s transfers da0: 96MB (196608 512 byte sectors: 64H 32S/T 96C) - In my /etc/fstab i have this line: /dev/da0s4 /zipufs rw,noauto 0 0 I have mkdir a /zip directory This is the problem: $ mount /zip mount: /dev/da0s4: Operation not permitted did you try mounting it as root ? (and what does /var/log/messages /var/log/dmesg say about it ?) Uhh.. embarrasing :-O (yes, I was not root! Well, still have a problem as root (I've had this problem from the start when I WAS logged in as root): # mount /zip mount: /dev/da0s4 on /zip: incorrect super block /Andreas --- Andreas Wideroe Andersen [EMAIL PROTECTED] Mobile: (+47) 90 92 61 21 http://www.filmshooting.com Norsk Smalfilm AS http://www.smalfilm.no ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Trouble mounting Zip drive
Andreas Widerøe Andersen wrote: At 17:19 05.07.2005, [EMAIL PROTECTED] wrote: On Tue, 05 Jul 2005 17:14:50 +0200 Andreas Widerøe Andersen [EMAIL PROTECTED] wrote: Hi, I'm having problems mounting a SCSI Iomega 100 Zip drive on my 4.11 RELEASE system: snip did you try mounting it as root ? (and what does /var/log/messages /var/log/dmesg say about it ?) Uhh.. embarrasing :-O (yes, I was not root! Well, still have a problem as root (I've had this problem from the start when I WAS logged in as root): # mount /zip mount: /dev/da0s4 on /zip: incorrect super block /Andreas Is the filesystem really ufs as noted in /etc/fstab? IIRC, trying to mount a non-ufs filesystem as ufs will give this error. Other possibilities include a bad disk ... :-( HTH, Kevin Kinsey ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Trouble mounting Zip drive
On Tue, Jul 05, 2005 at 05:44:17PM +0200, Andreas Wider?e Andersen wrote: [...] # mount /zip mount: /dev/da0s4 on /zip: incorrect super block Your ZIP disk hasn't been formatted as UFS, I would try `msdos' instead. -- Jonathan Chen [EMAIL PROTECTED]Once is dumb luck. Twice is coincidence. Three times and Somebody Is Trying To Tell You Something. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Trouble mounting Zip drive
On Tue, 2005-07-05 at 15:35, Jonathan Chen wrote: On Tue, Jul 05, 2005 at 05:44:17PM +0200, Andreas Wider?e Andersen wrote: [...] # mount /zip mount: /dev/da0s4 on /zip: incorrect super block Your ZIP disk hasn't been formatted as UFS, I would try `msdos' instead. Try mount -t msdos /dev/da0s4 /zip on the command line If that doesn't work, try da0s1 instead. fstab should say: ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Device not automatically created for IDE Zip drive
Hello, I'm trying to use the automounter on an internal IDE Zip drive on 5-STABLE. The problem I'm having is the device /dev/afd0s1 is not automatically created. The device /dev/afd0 is there, but not the slice. Is there a way to force that device name to be created on reboot? -- Regards, Doug ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
SCSI Zip drive questions
Hello. I've got a SCSI Zip drive which I'd like to use on a 5.4 box. So far it works with two minor problems: a) I'd like to be able to mount it as my day-to-day user. So I put myself in the operator group; added the following to /etc/devfs.conf: own /dev/da1root:operator perm/dev/da10660 own /dev/da1s4 root:operator perm/dev/da1s4 0660 Then the following to /etc/fstab: /dev/da1s4 /mnt/zipmsdos rw,noauto 0 0 The issue here is that mount /mnt/zip will fail because /dev/da1s4 does not yet exist. First I need to try and mount /dev/da1, then da1s4 will be created. Is there a way to automate this? b) It's *slow*! The same hardware with a different operating system (OS/2) gave almost twofold performances! Copying a 90MB file to a zip drive takes more than 10 minutes and it didn't with the old software. Is there a way to improve this? Here's the relevant dmesg: sym0: 895 port 0xd800-0xd8ff mem 0xd5201000-0xd5201fff,0xd5202000-0xd52020ff irq 15 at device 10.0 on pci0 sym0: Tekram NVRAM, ID 7, Fast-40, LVD, parity checking ... (probe5:sym0:0:5:0): phase change 6-7 [EMAIL PROTECTED] resid=4. da0 at sym0 bus 0 target 0 lun 0 da0: SEAGATE ST39205LW 0105 Fixed Direct Access SCSI-3 device da0: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled da0: 8750MB (17921835 512 byte sectors: 255H 63S/T 1115C) da1 at sym0 bus 0 target 5 lun 0 da1: IOMEGA ZIP 100 E.08 Removable Direct Access SCSI-2 device da1: 3.300MB/s transfers da1: Attempt to query device size failed: NOT READY, Medium not present cd0 at sym0 bus 0 target 4 lun 0 cd0: PLEXTOR CD-ROM PX-40TS 1.12 Removable CD-ROM SCSI-2 device cd0: 20.000MB/s transfers (20.000MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed cd1 at sym0 bus 0 target 6 lun 0 cd1: YAMAHA CRW8824S 1.0a Removable CD-ROM SCSI-2 device cd1: 20.000MB/s transfers (20.000MHz, offset 15) cd1: cd present [1 x 2048 byte records] (da1:sym0:0:5:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da1:sym0:0:5:0): CAM Status: SCSI Status Error (da1:sym0:0:5:0): SCSI Status: Check Condition (da1:sym0:0:5:0): NOT READY asc:3a,0 (da1:sym0:0:5:0): Medium not present (da1:sym0:0:5:0): Unretryable error Opened disk da1 - 6 (da1:sym0:0:5:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da1:sym0:0:5:0): CAM Status: SCSI Status Error (da1:sym0:0:5:0): SCSI Status: Check Condition (da1:sym0:0:5:0): NOT READY asc:3a,0 (da1:sym0:0:5:0): Medium not present (da1:sym0:0:5:0): Unretryable error Opened disk da1 - 6 The errors should be normal, since the drive was empty on boot. bye Thanks av. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Mounting iomega zip drive
--- Mike Jeays [EMAIL PROTECTED] wrote: On Sun, 2005-03-06 at 17:16, E. J. Cerejo wrote: --- Mike Jeays [EMAIL PROTECTED] escreveu: On Mon, 2005-02-21 at 19:34, E. J. Cerejo wrote: I use to be able to mount my paralell zip drive with the following command under Fbsd 4.x: mount -t msdos /dev/da0s4 /zip now I'm running 5.3 I can't, what changed? I noticed that there is only da0 in my /dev directory, I have this in my kernel: # SCSI peripherals device scbus # SCSI bus (required for SCSI) #device ch # SCSI media changers device da # Direct Access (disks) #device sa # Sequential Access (tape etc) device atapicam# emulate ATAPI devices as SCSI ditto via CAM device cd # CD device pass# Passthrough device (direct SCSI access) #device ses # SCSI Environmental Services (and SAF-TE) do I need anything else? __ Converse com seus amigos em tempo real com o Yahoo! Messenger http://br.download.yahoo.com/messenger/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Try running cdrecord -scanbus, and see if the device number is different. This sounds somewhat similar to a problem I was having with a flash drive and DVD-burner. scsibus0: 0,0,0 0) * 0,1,0 1) * 0,2,0 2) * 0,3,0 3) * 0,4,0 4) * 0,5,0 5) * 0,6,0 6) 'IOMEGA ' 'ZIP 100 ' 'K.05' Removable Disk 0,7,0 7) * scsibus2: 2,0,0 200) 'JLMS' 'DVD-ROM LTD-166S' 'DS0E' Removable CD-ROM 2,1,0 201) 'LITE-ON ' 'LTR-40125S ' 'ZS0K' Removable CD-ROM 2,2,0 202) * 2,3,0 203) * 2,4,0 204) * 2,5,0 205) * 2,6,0 206) * 2,7,0 207) * Aparently it's there on device 0. Any ideas? ___ Yahoo! Acesso Grátis - Instale o discador do Yahoo! agora. http://br.acesso.yahoo.com/ - Internet rápida e grátis Not many. I would try to muddle my way through, with attempts like: mount -t msdos /dev/da0 /zip mount -t msdos /dev/da0sx /zip, for x=1 to 4 (the 4 you have already tried) Then in desperation: mount -t msdos /dev/da6 /zip mount -t msdos /dev/da6sx /zip for x=1 to 4 mount -t msdos /dev/afd0 /zip Maybe someone else will have a better understanding of the device number mappings. I clearly don't. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Weird! Tried with mount -t msdos /dev/da0s4 /zip and it worked, I can see that da0s4 got created in /dev, before wasn't there. Could cdrecord -scanbus command have created it? __ Converse com seus amigos em tempo real com o Yahoo! Messenger http://br.download.yahoo.com/messenger/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Mounting iomega zip drive
On Wed, 2005-03-09 at 22:44, E. J. Cerejo wrote: --- Mike Jeays [EMAIL PROTECTED] wrote: On Sun, 2005-03-06 at 17:16, E. J. Cerejo wrote: --- Mike Jeays [EMAIL PROTECTED] escreveu: On Mon, 2005-02-21 at 19:34, E. J. Cerejo wrote: I use to be able to mount my paralell zip drive with the following command under Fbsd 4.x: mount -t msdos /dev/da0s4 /zip now I'm running 5.3 I can't, what changed? I noticed that there is only da0 in my /dev directory, I have this in my kernel: # SCSI peripherals devicescbus # SCSI bus (required for SCSI) #device ch # SCSI media changers deviceda # Direct Access (disks) #device sa # Sequential Access (tape etc) deviceatapicam# emulate ATAPI devices as SCSI ditto via CAM devicecd # CD devicepass# Passthrough device (direct SCSI access) #device ses # SCSI Environmental Services (and SAF-TE) do I need anything else? __ Converse com seus amigos em tempo real com o Yahoo! Messenger http://br.download.yahoo.com/messenger/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Try running cdrecord -scanbus, and see if the device number is different. This sounds somewhat similar to a problem I was having with a flash drive and DVD-burner. scsibus0: 0,0,0 0) * 0,1,0 1) * 0,2,0 2) * 0,3,0 3) * 0,4,0 4) * 0,5,0 5) * 0,6,0 6) 'IOMEGA ' 'ZIP 100 ' 'K.05' Removable Disk 0,7,0 7) * scsibus2: 2,0,0 200) 'JLMS' 'DVD-ROM LTD-166S' 'DS0E' Removable CD-ROM 2,1,0 201) 'LITE-ON ' 'LTR-40125S ' 'ZS0K' Removable CD-ROM 2,2,0 202) * 2,3,0 203) * 2,4,0 204) * 2,5,0 205) * 2,6,0 206) * 2,7,0 207) * Aparently it's there on device 0. Any ideas? ___ Yahoo! Acesso Grátis - Instale o discador do Yahoo! agora. http://br.acesso.yahoo.com/ - Internet rápida e grátis Not many. I would try to muddle my way through, with attempts like: mount -t msdos /dev/da0 /zip mount -t msdos /dev/da0sx /zip, for x=1 to 4 (the 4 you have already tried) Then in desperation: mount -t msdos /dev/da6 /zip mount -t msdos /dev/da6sx /zip for x=1 to 4 mount -t msdos /dev/afd0 /zip Maybe someone else will have a better understanding of the device number mappings. I clearly don't. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Weird! Tried with mount -t msdos /dev/da0s4 /zip and it worked, I can see that da0s4 got created in /dev, before wasn't there. Could cdrecord -scanbus command have created it? __ Converse com seus amigos em tempo real com o Yahoo! Messenger http://br.download.yahoo.com/messenger/ Glad it helped - muddling through does work sometimes! I don't think cdrecord would create the device - FreeBSD 5.x seems to create them automatically in the right circumstances. If you look at your Zip disk with fdisk (fdisk /dev/da0), you will see the four partitions. I had some where #4 was the partition with the data. Here is the result on a USB flash drive: it shows that partition 1 has the data, and I must address it as /dev/da0s1 501 ~ # fdisk /dev/da0 *** Working on device /dev/da0 *** parameters extracted from in-core disklabel are: cylinders=62 heads=64 sectors/track=32 (2048 blks/cyl) parameters to be used for BIOS calculations are: cylinders=62 heads=64 sectors/track=32 (2048 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 6 (0x06),(Primary 'big' DOS (= 32MB)) start 32, size 127712 (62 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 498/ head 7/ sector 32 The data for partition 2 is: UNUSED The data for partition 3 is: UNUSED The data for partition 4 is: UNUSED I can't experiment any more, because my IDE Zip drive died, and it is not worth replacing since CD burners reached a reasonable
Re: Mounting iomega zip drive
--- Mike Jeays [EMAIL PROTECTED] escreveu: On Mon, 2005-02-21 at 19:34, E. J. Cerejo wrote: I use to be able to mount my paralell zip drive with the following command under Fbsd 4.x: mount -t msdos /dev/da0s4 /zip now I'm running 5.3 I can't, what changed? I noticed that there is only da0 in my /dev directory, I have this in my kernel: # SCSI peripherals device scbus # SCSI bus (required for SCSI) #device ch # SCSI media changers device da # Direct Access (disks) #device sa # Sequential Access (tape etc) device atapicam# emulate ATAPI devices as SCSI ditto via CAM device cd # CD device pass# Passthrough device (direct SCSI access) #device ses # SCSI Environmental Services (and SAF-TE) do I need anything else? __ Converse com seus amigos em tempo real com o Yahoo! Messenger http://br.download.yahoo.com/messenger/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Try running cdrecord -scanbus, and see if the device number is different. This sounds somewhat similar to a problem I was having with a flash drive and DVD-burner. scsibus0: 0,0,0 0) * 0,1,0 1) * 0,2,0 2) * 0,3,0 3) * 0,4,0 4) * 0,5,0 5) * 0,6,0 6) 'IOMEGA ' 'ZIP 100 ' 'K.05' Removable Disk 0,7,0 7) * scsibus2: 2,0,0 200) 'JLMS' 'DVD-ROM LTD-166S' 'DS0E' Removable CD-ROM 2,1,0 201) 'LITE-ON ' 'LTR-40125S ' 'ZS0K' Removable CD-ROM 2,2,0 202) * 2,3,0 203) * 2,4,0 204) * 2,5,0 205) * 2,6,0 206) * 2,7,0 207) * Aparently it's there on device 0. Any ideas? ___ Yahoo! Acesso Grátis - Instale o discador do Yahoo! agora. http://br.acesso.yahoo.com/ - Internet rápida e grátis ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Mounting iomega zip drive
On Sun, 2005-03-06 at 17:16, E. J. Cerejo wrote: --- Mike Jeays [EMAIL PROTECTED] escreveu: On Mon, 2005-02-21 at 19:34, E. J. Cerejo wrote: I use to be able to mount my paralell zip drive with the following command under Fbsd 4.x: mount -t msdos /dev/da0s4 /zip now I'm running 5.3 I can't, what changed? I noticed that there is only da0 in my /dev directory, I have this in my kernel: # SCSI peripherals devicescbus # SCSI bus (required for SCSI) #device ch # SCSI media changers deviceda # Direct Access (disks) #device sa # Sequential Access (tape etc) deviceatapicam# emulate ATAPI devices as SCSI ditto via CAM devicecd # CD devicepass# Passthrough device (direct SCSI access) #device ses # SCSI Environmental Services (and SAF-TE) do I need anything else? __ Converse com seus amigos em tempo real com o Yahoo! Messenger http://br.download.yahoo.com/messenger/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Try running cdrecord -scanbus, and see if the device number is different. This sounds somewhat similar to a problem I was having with a flash drive and DVD-burner. scsibus0: 0,0,0 0) * 0,1,0 1) * 0,2,0 2) * 0,3,0 3) * 0,4,0 4) * 0,5,0 5) * 0,6,0 6) 'IOMEGA ' 'ZIP 100 ' 'K.05' Removable Disk 0,7,0 7) * scsibus2: 2,0,0 200) 'JLMS' 'DVD-ROM LTD-166S' 'DS0E' Removable CD-ROM 2,1,0 201) 'LITE-ON ' 'LTR-40125S ' 'ZS0K' Removable CD-ROM 2,2,0 202) * 2,3,0 203) * 2,4,0 204) * 2,5,0 205) * 2,6,0 206) * 2,7,0 207) * Aparently it's there on device 0. Any ideas? ___ Yahoo! Acesso Grátis - Instale o discador do Yahoo! agora. http://br.acesso.yahoo.com/ - Internet rápida e grátis Not many. I would try to muddle my way through, with attempts like: mount -t msdos /dev/da0 /zip mount -t msdos /dev/da0sx /zip, for x=1 to 4 (the 4 you have already tried) Then in desperation: mount -t msdos /dev/da6 /zip mount -t msdos /dev/da6sx /zip for x=1 to 4 mount -t msdos /dev/afd0 /zip Maybe someone else will have a better understanding of the device number mappings. I clearly don't. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Mounting iomega zip drive
On Sun, 06 Mar 2005 22:51:49 -0500, Mike Jeays [EMAIL PROTECTED] wrote: On Sun, 2005-03-06 at 17:16, E. J. Cerejo wrote: --- Mike Jeays [EMAIL PROTECTED] escreveu: On Mon, 2005-02-21 at 19:34, E. J. Cerejo wrote: I use to be able to mount my paralell zip drive with the following command under Fbsd 4.x: mount -t msdos /dev/da0s4 /zip now I'm running 5.3 I can't, what changed? I noticed that there is only da0 in my /dev directory, if da0 is the only entry in /dev then you might have missed something in the kernel configuration. AFAIK device vpo is reguired for Iomega Parallel Zip Drive. and device umass is required for Iomega USB Zip Drive. Note that device vpo is disabled by default in the GENERIC configuration file. I wonder why?! PS: Secure Kernel Levels might also prevent mounting devices. (not very sure about this)! I have this in my kernel: # SCSI peripherals devicescbus # SCSI bus (required for SCSI) #device ch # SCSI media changers deviceda # Direct Access (disks) #device sa # Sequential Access (tape etc) deviceatapicam# emulate ATAPI devices as SCSI ditto via CAM devicecd # CD devicepass# Passthrough device (direct SCSI access) #device ses # SCSI Environmental Services (and SAF-TE) do I need anything else? __ Converse com seus amigos em tempo real com o Yahoo! Messenger http://br.download.yahoo.com/messenger/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Try running cdrecord -scanbus, and see if the device number is different. This sounds somewhat similar to a problem I was having with a flash drive and DVD-burner. scsibus0: 0,0,0 0) * 0,1,0 1) * 0,2,0 2) * 0,3,0 3) * 0,4,0 4) * 0,5,0 5) * 0,6,0 6) 'IOMEGA ' 'ZIP 100 ' 'K.05' Removable Disk 0,7,0 7) * scsibus2: 2,0,0 200) 'JLMS' 'DVD-ROM LTD-166S' 'DS0E' Removable CD-ROM 2,1,0 201) 'LITE-ON ' 'LTR-40125S ' 'ZS0K' Removable CD-ROM 2,2,0 202) * 2,3,0 203) * 2,4,0 204) * 2,5,0 205) * 2,6,0 206) * 2,7,0 207) * Aparently it's there on device 0. Any ideas? ___ Yahoo! Acesso Grátis - Instale o discador do Yahoo! agora. http://br.acesso.yahoo.com/ - Internet rápida e grátis Not many. I would try to muddle my way through, with attempts like: mount -t msdos /dev/da0 /zip mount -t msdos /dev/da0sx /zip, for x=1 to 4 (the 4 you have already tried) Then in desperation: mount -t msdos /dev/da6 /zip mount -t msdos /dev/da6sx /zip for x=1 to 4 mount -t msdos /dev/afd0 /zip Maybe someone else will have a better understanding of the device number mappings. I clearly don't. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Mounting iomega zip drive
On Mon, 21 Feb 2005, E. J. Cerejo wrote: I use to be able to mount my paralell zip drive with the following command under Fbsd 4.x: mount -t msdos /dev/da0s4 /zip now I'm running 5.3 I can't, what changed? I noticed that there is only da0 in my /dev directory, I have this in my kernel: # SCSI peripherals device scbus # SCSI bus (required for SCSI) #device ch # SCSI media changers device da # Direct Access (disks) #device sa # Sequential Access (tape etc) device atapicam# emulate ATAPI devices as SCSI ditto via CAM device cd # CD device pass# Passthrough device (direct SCSI access) #device ses # SCSI Environmental Services (and SAF-TE) do I need anything else? I've got a parellel port zip drive running on a 5.3 system at home. From memory, I think what you need is: device vpo ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Mounting iomega zip drive
I use to be able to mount my paralell zip drive with the following command under Fbsd 4.x: mount -t msdos /dev/da0s4 /zip now I'm running 5.3 I can't, what changed? I noticed that there is only da0 in my /dev directory, I have this in my kernel: # SCSI peripherals device scbus # SCSI bus (required for SCSI) #device ch # SCSI media changers device da # Direct Access (disks) #device sa # Sequential Access (tape etc) device atapicam# emulate ATAPI devices as SCSI ditto via CAM device cd # CD device pass# Passthrough device (direct SCSI access) #device ses # SCSI Environmental Services (and SAF-TE) do I need anything else? __ Converse com seus amigos em tempo real com o Yahoo! Messenger http://br.download.yahoo.com/messenger/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Mounting iomega zip drive
On Mon, 2005-02-21 at 19:34, E. J. Cerejo wrote: I use to be able to mount my paralell zip drive with the following command under Fbsd 4.x: mount -t msdos /dev/da0s4 /zip now I'm running 5.3 I can't, what changed? I noticed that there is only da0 in my /dev directory, I have this in my kernel: # SCSI peripherals devicescbus # SCSI bus (required for SCSI) #device ch # SCSI media changers deviceda # Direct Access (disks) #device sa # Sequential Access (tape etc) deviceatapicam# emulate ATAPI devices as SCSI ditto via CAM devicecd # CD devicepass# Passthrough device (direct SCSI access) #device ses # SCSI Environmental Services (and SAF-TE) do I need anything else? __ Converse com seus amigos em tempo real com o Yahoo! Messenger http://br.download.yahoo.com/messenger/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Try running cdrecord -scanbus, and see if the device number is different. This sounds somewhat similar to a problem I was having with a flash drive and DVD-burner. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Connecting a USB Zip drive -- whatever am I doing wrong?
On Sun, 11 Jul 2004 16:04:10 +0100 John Murphy [EMAIL PROTECTED] wrote: epilogue [EMAIL PROTECTED] wrote: ### uname -a FreeBSD 4.10-RELEASE-p1 i386 ### relevant lines from kernel device vpo device scbus device da device umass device uhci# uhci related entries show up in dmesg device usb device ugen Do you have 'device pass'? Just a guess, sorry if it doesn't help. regrettably, this did not do the trick. i see precisely the same behaviour as outlined in my earlier messages. sigh. thanks for your suggestion, john. -- John. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Connecting a USB Zip drive -- whatever am I doing wrong?
epilogue [EMAIL PROTECTED] wrote: ### uname -a FreeBSD 4.10-RELEASE-p1 i386 ### relevant lines from kernel device vpo device scbus device da device umass device uhci# uhci related entries show up in dmesg device usb device ugen Do you have 'device pass'? Just a guess, sorry if it doesn't help. -- John. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Connecting a USB Zip drive -- whatever am I doing wrong?
hey hey, anyone else willing to take a stab at this? fwiw, i am fairly certain that the problem resides somewhere between the keyboard and the chair, however i would appreciate confirmation (i think :) before i do something silly like submitting a pr or sending this off to another list. (note that i had two very right suggestions to add the umass device, however that didn't solve the problem, because i already had it compiled into my kernel. i simply forgot to include it in this message. this has been corrected below...) apologies for the lengthy message. really wanted to provide as much useful info as i could. thanks to all who suffer through the verbiage, yet resolutely give it a go. hello all, for many moons now, i'll occasionally dedicate a dark day to getting my USB Zip drive to work. i've been through the handbook, faq, relevant man pages, mailing lists and across the colossal googlesphere collecting bits and pieces, none of which seem to get me the desired result. i'm obviously missing something. i'm writing with the hope that, what i have managed to overlook will be so obvious and straighforward, some kind reader will take 2 seconds to point it out, so that i may zip off on my merry way. ### uname -a FreeBSD 4.10-RELEASE-p1 i386 ### relevant lines from kernel device vpo device scbus device da device umass device uhci# uhci related entries show up in dmesg device usb device ugen i have also tried with the ohci device added, but it never generates any dmesg entries. from what i gather, uhci and ohci have an 'either - or' kind of relationship. i'm supposing that uhci is the right device for my system. now, when i boot with the zip device plugged in (whether or not there is a disk loaded), the system will hang until i unplug the usb cable. ### dmesg snip atapci0: Intel PIIX4 ATA33 controller port 0x1050-0x105f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: Intel 82371AB/EB (PIIX4) USB controller port 0x1060-0x107f irq 5 at device 7.2 on pci0 usb0: Intel 82371AB/EB (PIIX4) USB controller on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered ##-- hangs here for about 30 seconds, then chugs on happily --## chip0: Intel 82371AB Power management controller port 0x1040-0x104f at device 7.3 on pci0 pcm0: ESS Technology Maestro-2E port 0x1400-0x14ff irq 5 at device 8.0 on pci0 snip pccard: card inserted, slot 1 ad0: 17301MB TOSHIBA MK1814GAV [35152/16/63] at ata0-master UDMA33 acd0: CDROM TOSHIBA CD-ROM XM-7002B at ata1-master UDMA33 ##-- hangs here *until* i pull the usb plug. after i do, i get the following error messages but the boot finishes nicely. --## umass0: BBB reset failed, IOERROR umass0: BBB reset failed, STALLED umass0: BBB bulk-in clear stall failed, STALLED umass0: BBB bulk-out clear stall failed, STALLED umass0: BBB reset failed, STALLED umass0: BBB bulk-in clear stall failed, STALLED umass0: BBB bulk-out clear stall failed, STALLED umass0: BBB reset failed, STALLED umass0: BBB bulk-in clear stall failed, STALLED umass0: BBB bulk-out clear stall failed, STALLED Mounting root from ufs:/dev/ad0s2a umass0: at uhub0 port 1 (addr 2) disconnected umass0: detached snip ### /var/log/messages Jul 4 21:47:04 /kernel: umass0: Iomega USB Zip 100, rev 1.00/1.00, addr 2 Jul 4 21:47:04 /kernel: umass0: Get Max Lun not supported (STALLED) Jul 4 21:48:09 /kernel: umass0: BBB reset failed, IOERROR ### after booting, i plug the usb cable back in and usbdevs -v: Controller /dev/usb0: addr 1: full speed, self powered, config 1, UHCI root hub(0x), Intel(0x), rev 1.00 port 1 addr 2: full speed, self powered, config 1, Zip 100(0x0001), Iomega(0x059b), rev 1.00 port 2 powered ### ps auxw | grep -i usb root 99 0.0 0.2 940 604 ?? Is 9:42PM 0:00.00 /usr/sbin/usbd root 4 0.0 0.0 00 ?? DL5:42PM 0:00.00 (usbtask) root 3 0.0 0.0 00 ?? DL5:42PM 0:00.00 (usb0) looks good (i think). ### mounting i'm not sure that i 'get' which device the zip maps to nor how to determine this. i have tried about 40 different combinations of mount (mostly gleaned from my research), but i have yet to hit upon the right command. # mount -t msdos /dev/da* /mnt # * = practically every single one msdos: /dev/da0s4: Device not configured ...with the same results for /dev/sa* devices. of the many combinations tried, /dev/usb0 has provided the most promising error message (i think). # mount -t msdos /dev/usb0 /mnt msdos: /dev/usb0: Block device required ### final notes 1) not the drive - it works on several other non-*nix systems 2) not the usb port itself - boot to another OS and it works. 2) not the zip disks - have tried different disks all known to be good if there is any further testing i can do or details i can provide, please let me
Re: Connecting a USB Zip drive -- whatever am I doing wrong?
epilogue wrote: ### relevant lines from kernel device vpo device scbus device da device uhci# uhci related entries show up in dmesg device usb device ugen Don't forget umass. Try adding sa. My USB HDD comes up as /dev/sa0. Your ZIP drive might need sa, too. [dmesg snipped] [various messages snipped] ### /var/log/messages Jul 4 21:47:04 /kernel: umass0: Iomega USB Zip 100, rev 1.00/1.00, addr 2 Jul 4 21:47:04 /kernel: umass0: Get Max Lun not supported (STALLED) Jul 4 21:48:09 /kernel: umass0: BBB reset failed, IOERROR I guess if you posted these to stable@ you might get more attention. ### mounting i'm not sure that i 'get' which device the zip maps to nor how to determine this. i have tried about 40 different combinations of mount (mostly gleaned from my research), but i have yet to hit upon the right command. # mount -t msdos /dev/da* /mnt # * = practically every single one msdos: /dev/da0s4: Device not configured See above. I think USB mass storage devices require sa to work, therefore you would need sth like mount -t msdos /dev/sa* /mnt -- Don't know what * should be out of my head now. Hope this helps. Phil. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Connecting a USB Zip drive -- whatever am I doing wrong?
On Mon, 05 Jul 2004 13:36:20 +0200 Phil Schulz [EMAIL PROTECTED] wrote: epilogue wrote: ### relevant lines from kernel device vpo device scbus device da device uhci# uhci related entries show up in dmesg device usb device ugen Don't forget umass. Try adding sa. My USB HDD comes up as /dev/sa0. Your ZIP drive might need sa, too. hello phil, actually, i have 'umass' enabled. i simply missed including it, when i cut and pasted all this together. i added 'sa'. the boot time freeze still occurs, but when i unplug, i see a few new messages in dmesg and /var/log/messages. before sa: snip umass0: Iomega USB Zip 100, rev 1.00/1.00, addr 2 umass0: Get Max Lun not supported (STALLED) umass0: BBB reset failed, IOERROR with sa: snip umass0: Iomega USB Zip 100, rev 1.00/1.00, addr 2 umass0: Get Max Lun not supported (STALLED) umass0: Invalid CSW: status 4 2 (da0:umass-sim0:0:0:0): got CAM status 0x4 (da0:umass-sim0:0:0:0): fatal error, failed to attach to device (da0:umass-sim0:0:0:0): lost device (da0:umass-sim0:0:0:0): removing device entry [dmesg snipped] [various messages snipped] ### /var/log/messages Jul 4 21:47:04 /kernel: umass0: Iomega USB Zip 100, rev 1.00/1.00, addr 2 Jul 4 21:47:04 /kernel: umass0: Get Max Lun not supported (STALLED) Jul 4 21:48:09 /kernel: umass0: BBB reset failed, IOERROR I guess if you posted these to stable@ you might get more attention. ### mounting i'm not sure that i 'get' which device the zip maps to nor how to determine this. i have tried about 40 different combinations of mount (mostly gleaned from my research), but i have yet to hit upon the right command. # mount -t msdos /dev/da* /mnt # * = practically every single one msdos: /dev/da0s4: Device not configured See above. I think USB mass storage devices require sa to work, therefore you would need sth like mount -t msdos /dev/sa* /mnt -- Don't know what * should be out of my head now. # cd /dev; sh MAKEDEV all # just to be sure. # ls -al sa* crw-rw 4 root operator 14, 0 Jul 5 09:56 sa0 crw-rw 4 root operator 14, 0 Jul 5 09:56 sa0.0 crw-rw 2 root operator 14, 4 Jul 5 09:56 sa0.1 crw-rw 2 root operator 14, 8 Jul 5 09:56 sa0.2 crw-rw 2 root operator 14, 12 Jul 5 09:56 sa0.3 crw-rw 2 root wheel 14, 0x2000 Jul 5 09:56 sa0.ctl # mount -t msdos /dev/sa0.0 /mnt msdos: /dev/sa0.0: Device not configured unfortunately, i'm getting the same error for each of these devices. nevertheless, many thanks for your suggestions. epi Hope this helps. Phil. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Connecting a USB Zip drive -- whatever am I doing wrong?
hello all, for many moons now, i'll occasionally dedicate a dark day to getting my USB Zip drive to work. i've been through the handbook, faq, relevant man pages, mailing lists and across the colossal googlesphere collecting bits and pieces, none of which seem to get me the desired result. i'm obviously missing something. i'm writing with the hope that, what i have managed to overlook will be so obvious and straighforward, some kind reader will take 2 seconds to point it out, so that i may zip off on my merry way. ### uname -a FreeBSD 4.10-RELEASE-p1 i386 ### relevant lines from kernel device vpo device scbus device da device uhci# uhci related entries show up in dmesg device usb device ugen i have also tried with the ohci device added, but it never generates any dmesg entries. from what i gather, uhci and ohci have an 'either - or' kind of relationship. i'm supposing that uhci is the right device for my system. now, when i boot with the zip device plugged in (whether or not there is a disk loaded), the system will hang until i unplug the usb cable. ### dmesg snip atapci0: Intel PIIX4 ATA33 controller port 0x1050-0x105f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: Intel 82371AB/EB (PIIX4) USB controller port 0x1060-0x107f irq 5 at device 7.2 on pci0 usb0: Intel 82371AB/EB (PIIX4) USB controller on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered ##-- hangs about 30 seconds here, but chugs on happily after --## chip0: Intel 82371AB Power management controller port 0x1040-0x104f at device 7.3 on pci0 pcm0: ESS Technology Maestro-2E port 0x1400-0x14ff irq 5 at device 8.0 on pci0 snip pccard: card inserted, slot 1 ad0: 17301MB TOSHIBA MK1814GAV [35152/16/63] at ata0-master UDMA33 acd0: CDROM TOSHIBA CD-ROM XM-7002B at ata1-master UDMA33 ##-- hangs here *until* i pull the usb plug. after i do, i get the following error messages but the boot finishes nicely. --## umass0: BBB reset failed, IOERROR umass0: BBB reset failed, STALLED umass0: BBB bulk-in clear stall failed, STALLED umass0: BBB bulk-out clear stall failed, STALLED umass0: BBB reset failed, STALLED umass0: BBB bulk-in clear stall failed, STALLED umass0: BBB bulk-out clear stall failed, STALLED umass0: BBB reset failed, STALLED umass0: BBB bulk-in clear stall failed, STALLED umass0: BBB bulk-out clear stall failed, STALLED Mounting root from ufs:/dev/ad0s2a umass0: at uhub0 port 1 (addr 2) disconnected umass0: detached ltmdm0: Lucent Winmodem port 0x1800-0x18ff,0x1080-0x1087 mem 0xfc00-0xfcff irq 5 at device 16.0 on pci0 ltmdm0: type Virtual 16550A umass0: Iomega USB Zip 100, rev 1.00/1.00, addr 2 umass0: Get Max Lun not supported (STALLED) umass0: BBB reset failed, IOERROR ### after booting. i plug the usb cable back in and usbdevs -v Controller /dev/usb0: addr 1: full speed, self powered, config 1, UHCI root hub(0x), Intel(0x), rev 1.00 port 1 addr 2: full speed, self powered, config 1, Zip 100(0x0001), Iomega(0x059b), rev 1.00 port 2 powered ### ps auxw | grep -i usb root 99 0.0 0.2 940 604 ?? Is 9:42PM 0:00.00 /usr/sbin/usbd root 4 0.0 0.0 00 ?? DL5:42PM 0:00.00 (usbtask) root 3 0.0 0.0 00 ?? DL5:42PM 0:00.00 (usb0) looks good (i think). ### /var/log/messages Jul 4 21:47:04 /kernel: umass0: Iomega USB Zip 100, rev 1.00/1.00, addr 2 Jul 4 21:47:04 /kernel: umass0: Get Max Lun not supported (STALLED) Jul 4 21:48:09 /kernel: umass0: BBB reset failed, IOERROR ### mounting i'm not sure that i 'get' which device the zip maps to nor how to determine this. i have tried about 40 different combinations of mount (mostly gleaned from my research), but i have yet to hit upon the right command. # mount -t msdos /dev/da* /mnt # * = practically every single one msdos: /dev/da0s4: Device not configured of the many combinations tried, /dev/usb0 has provided the most promising error message (i think). # mount -t msdos /dev/usb0 /mnt msdos: /dev/usb0: Block device required ### final notes 1) the Zip drive works on several other non-*nix systems 2) i *have* tried with more than just one disk. i'm guessing that the problem is that i'm just not mounting correctly, but hey, that's just a guess. :) -- my apologies for the lengthy message. hopefully, it provided some useful troubleshooting info. please let me know if there are any further details i can provide. many thanks, epi ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Connecting a USB Zip drive -- whatever am I doing wrong?
On Sunday 04 July 2004 07:28 pm, epilogue wrote: hello all, for many moons now, i'll occasionally dedicate a dark day to getting my USB Zip drive to work. i've been through the handbook, faq, relevant man pages, mailing lists and across the colossal googlesphere collecting bits and pieces, none of which seem to get me the desired result. i'm obviously missing something. i'm writing with the hope that, what i have managed to overlook will be so obvious and straighforward, some kind reader will take 2 seconds to point it out, so that i may zip off on my merry way. ### uname -a FreeBSD 4.10-RELEASE-p1 i386 ### relevant lines from kernel device vpo device scbus device da device uhci# uhci related entries show up in dmesg deviceusb deviceugen What about device umass # Disks/Mass storage - Requires scbus and da Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Connecting a USB Zip drive -- whatever am I doing wrong?
On Sun, 4 Jul 2004 20:04:06 -0700 Kent Stewart [EMAIL PROTECTED] wrote: On Sunday 04 July 2004 07:28 pm, epilogue wrote: hello all, for many moons now, i'll occasionally dedicate a dark day to getting my USB Zip drive to work. i've been through the handbook, faq, relevant man pages, mailing lists and across the colossal googlesphere collecting bits and pieces, none of which seem to get me the desired result. i'm obviously missing something. i'm writing with the hope that, what i have managed to overlook will be so obvious and straighforward, some kind reader will take 2 seconds to point it out, so that i may zip off on my merry way. ### uname -a FreeBSD 4.10-RELEASE-p1 i386 ### relevant lines from kernel device vpo device scbus device da device uhci# uhci related entries show up in dmesg device usb device ugen What about device umass # Disks/Mass storage - Requires scbus and da hello kent, it's already in there. sigh. i just missed it, when i pasted all this info together. sorry for the oversight. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD and Internal IDE 100M ZIP drive
Shawn Guillemette wrote: Looking to eject my 100M iomega ZIP deive from with in my shell script. URL's, Pasted examples, anything.. Im searching the net too... not much luck yet... Shawn There is no place like 127.0.0.1 There is an eject utility in ports that purports to be able to eject removable media, but so far I have not been able to convince it to eject my internal IDE Zip media. Works fine on the IDE CD-ROM drive tho. Dave ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD and Internal IDE 100M ZIP drive
On Wed, 24 Mar 2004, Shawn Guillemette wrote: Looking to eject my 100M iomega ZIP deive from with in my shell script. URL's, Pasted examples, anything.. Im searching the net too... not much luck yet... I haven't found anything that will eject the disk for FreeBSD. I had a binary tool like that back when I had a SuSE system, though. 'ziptool', or something like that. Perhaps it will work under Linux emulation... though I tend to be pessimistic. -- David Fleck [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD and Internal IDE 100M ZIP drive
Looking to eject my 100M iomega ZIP deive from with in my shell script. URL's, Pasted examples, anything.. Im searching the net too... not much luck yet... Shawn There is no place like 127.0.0.1 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
ZIP DRIVE
I have a 100M zip drive in my machine and want to start using it for some backups. I have a script working (always looking for more if you have urls) so it will erase the data on the zip disk using rm and then write some tar'ed files to the disk. I cant seem to get the drive to release the disk though. Id like to have the script release the tape for me so I know when it has completed. Also wondering if there is another way to remove the files from the destination media.. I know with tapes you can use erase, rewind, so on .. are there similar commands for the zip drive? Thanks, Shawn Guillemette There is no place like 127.0.0.1 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
ZIP DRIVE
I have a 100M zip drive in my machine and want to start using it for some backups. I have a script working (always looking for more if you have urls) so it will erase the data on the zip disk using rm and then write some tar'ed files to the disk. I cant seem to get the drive to release the disk though. Id like to have the script release the tape for me so I know when it has completed. Also wondering if there is another way to remove the files from the destination media.. I know with tapes you can use erase, rewind, so on .. are there similar commands for the zip drive? Thanks, Shawn Guillemette There is no place like 127.0.0.1 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Solution to Zip drive failed to install.
Solution to failed ZIP drive install The BIOs setting was the fault. I cleared it by disabling the BIOs internal motherboard settings and installing a printer card that I set to run at IRQ 7 - 0278 . This brought up the zip drive with no problem. Then I removed the card and reset the internal motherboard back to IRQ 7 and 0378. This brought up the zip drive with no problem. I did set also the BIOs to EPP. My original problem. I have a FreeBSD 4.4 box that works fine with Zip drives. I have another 4.4 that I can't get to configure the /zip drive. I am now building another box using 4.9 and can't get the zip drive to work on it either. snd module installs and works fine BTW on all three boxes. The error messages I get are /dev/da0s4 Device not configured. and trying to unload the kernel module to reload it gives the same message. I am doing this vpo install from old notes and I can't figure out what's causing the configuration failure. I also tried entering /etc/fstab parameters same as the other box that works. /dev/da0s4 /zip msdos rw,noauto 0 0 Suggestions appreciated or point me clearer to a How To. I looked on the FreeBSD.org and that section is what I follow. Thanks. -- Aloha! Al Plant - Webmaster http://hawaiidakine.com Providing FAST DSL Service for $28.00 /mo. Member Small Business Hawaii. Running FreeBSD 4.5 UNIX Caldera Linux 2.4 RedHat 7.2 Support OPEN SOURCE in Business Computing. Phone 808-622-0043 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Formatting Zip Drive Disks
On Thursday, January 22, 2004 2:34:32 AM you wrote: I am attempting to format a 100 mb. ZIP disk, but am getting nowhere. The ZIP drive worked fine under Windows. The disk is presently formatted as NTFS, if that makes any difference. Nothing I try seems to work . Since I am new to BSD, I assume that I am using the wrong commands. I am presently using version 5.2 of BSD. Can anyone assist me.? Zip-drives and FreeBSD: http://www.freebsd.org/doc/en_US.ISO8859-1/articles/zip-drive/index.html and to some extent Formatting media on FreeBSD http://www.freebsd.org/doc/en_US.ISO8859-1/articles/formatting-media/index.html ** Reply Separator ** Thursday, January 22, 2004 5:37:52 AM I have went that route. It seems that no matter what I do, I receive the following error message when attempting to mount the disk: Incorrect Super block Do you have any suggestions? I have tried mounting in various ways, but they all fail. Formatting via /stand/sysinstall has not corrected the problem. Gerard Seibert [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Formatting Zip Drive Disks
On Thu, 22 Jan 2004, Gerard Seibert wrote: Do you have any suggestions? I have tried mounting in various ways, but they all fail. Formatting via /stand/sysinstall has not corrected the problem. have you considered making a filesystem on the zip disk ? Regards, /\_/\ All dogs go to heaven. [EMAIL PROTECTED](0 0)http://www.alphaque.com/ +==oOO--(_)--OOo==+ | for a in past present future; do| | for b in clients employers associates relatives neighbours pets; do | | echo The opinions here in no way reflect the opinions of my $a $b. | | done; done | +=+ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD zip drive install
Configuring a zip drive. I have a FreeBSD 4.4 box that works fine with Zip drives. I have another 4.4 that I can't get to configure the /zip drive. I am now building the box using 4.9 and can't get the zip drive to work on it either. snd module installs and works fine BTW on all three boxes. The error messages I get are /dev/da0s4 Device not configured. and trying to unload the kernel module to reload it gives the same message. da0* shows up under /dev when you cd /dev Is there another way to assure that the detection is being made? I see an error under dmesg now: vpo0 IOMEGA drive Parallel to SCSI is detected on ppbus0 vpo0 EPP mode (seems OK.) BUT: vpo0: VPO error/time out (5) shows just before the last line of the dmesg file. Any idea what I should be looking for? I am doing this vpo install from old notes and I can't figure out what's causing the configuration failure. I also tried entering /etc/fstab parameters same as the other box that works. /dev/da0s4 /zip msdos rw,noauto 0 0 This IS the problem. The 3 da0 entries that show up on the 4.4 box dmesg that works do not show up on the other 2 boxes. da0 at vpo0 bus0 target6 lun0 da0 : (iomega zip) da0 : 96mb Any of you FreeBSD guys know how to cure this? Aloha! Al Plant - Webmaster http://hawaiidakine.com Providing FAST DSL Service for $28.00 /mo. Member Small Business Hawaii. Running FreeBSD 4.5 UNIX Caldera Linux 2.4 RedHat 7.2 Support OPEN SOURCE in Business Computing. Phone 808-622-0043 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD zip drive install
On Wed, 21 Jan 2004, al plant wrote: I have a FreeBSD 4.4 box that works fine with Zip drives. I have another 4.4 that I can't get to configure the /zip drive. I am now building the box using 4.9 and can't get the zip drive to work on it either. first, what kind of zip drive? USB? paralell port? SCSI? snd module installs and works fine BTW on all three boxes. i don't know what this has to do with a zip drive. The error messages I get are /dev/da0s4 Device not configured. and trying to unload the kernel module to reload it gives the same message. generally, that means you might not have the right FS or not have a disk in it. da0* shows up under /dev unless you're using devfs, it'll always be there. Is there another way to assure that the detection is being made? I see an error under dmesg now: vpo0 IOMEGA drive Parallel to SCSI is detected on ppbus0 vpo0 EPP mode (seems OK.) BUT: vpo0: VPO error/time out (5) shows just before the last line of the dmesg file. Any idea what I should be looking for? that seems like it may be a paralell port issue. i'd suggest trying to swap your zip drives between the working and non-working machines to make sure the hardware isn't bad. I am doing this vpo install from old notes and I can't figure out what's causing the configuration failure. it could well be a hardware problem, although generally it's a driver or kernel configuration problem. I also tried entering /etc/fstab parameters same as the other box that works. /dev/da0s4 /zip msdos rw,noauto 0 0 this won't do you much good until the hardware is working. keep it in though, no reason to delete it just yet. The 3 da0 entries that show up on the 4.4 box dmesg that works do not show up on the other 2 boxes. da0 at vpo0 bus0 target6 lun0 da0 : (iomega zip) da0 : 96mb well, do you have scsi devices compiled in to the kernel? how about the scsi kernel module? it'll be needed to handle any da device Any of you FreeBSD guys know how to cure this? not really, no. i can just suggest places to start looking. ---/ f. johan beisser /--+ The other day I asked former Yankees pitcher Jim Bouton what he thought of our great victory over Iraq, and he said, Mohammed Ali versus Mr. Rogers. -- kurt vonnegut, 5.9.03 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: trouble mounting a zip drive on parallel port
On Fri, 16 Jan 2004, Alex Walker wrote: I'm trying to mount a parallel zip drive on FreeBSD 4.8. I did re-configure my kernel to include the vpo driver and I get the following message on dmesg: vpo0: Iomega VPI0 Parallel to SCSI interface on ppbus0 vpo0: EPP mode vpo0: VP0 error/timeout (5) vpo0: VP0 error/timeout (5) The errors are a little worrying, but it does seem to be seeing the drive. Don't be too sure about that. From my experience, what you're seeing here is acknowledgement that the ppbus recognizes the existence of the vpo driver, and that it's set for EPP mode. This is prior to any attempt to communicate with the zip drive itself. I got the same error messages when my parallel cable came loose and the zip was no longer communicating with the driver at all. Do you get any messages like the following? (I'm guessing not): Creating DISK da0 da0 at vpo0 bus 0 target 6 lun 0 da0: IOMEGA ZIP 100 J.03 Removable Direct Access SCSI-2 device da0: 96MB (196608 512 byte sectors: 64H 32S/T 96C) If not, there's no device to mount. Sorry, I'm no expert on debugging this, I can just tell you my experience. -- David Fleck [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: trouble mounting a zip drive on parallel port
Alas, I got no message about Creating DISK da0. I have double checked all of the connections (my machine is set to dual boot with another OS, and everything works fine there), so I know it's not a connection issue. Still it just refuses to find the drive even though I have set everything up in my kernel exactly as it says in the handbook. Any chance someone else out there might have run into this? I hate to sound overly desperate, but as I stare down at the little green light on my zip drive while it stubbornly refuses to work, I'm beginning to hear a voice in my head that sounds suspiciously like John Cleese when he screamed you vicious bastard! at his car in the gourmet night episode of Fawlty Towers. Someone please help me before I start whacking the thing with a plant. Thanks, Alex On Saturday 17 January 2004 07:13 am, David Fleck wrote: Creating DISK da0 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: trouble mounting a zip drive on parallel port
On Saturday 17 January 2004 07:55 pm, Alex Walker wrote: Alas, I got no message about Creating DISK da0. I have double checked all of the connections (my machine is set to dual boot with another OS, and everything works fine there), so I know it's not a connection issue. Still it just refuses to find the drive even though I have set everything up in my kernel exactly as it says in the handbook. Any chance someone else out there might have run into this? I hate to sound overly desperate, but as I stare down at the little green light on my zip drive while it stubbornly refuses to work, I'm beginning to hear a voice in my head that sounds suspiciously like John Cleese when he screamed you vicious bastard! at his car in the gourmet night episode of Fawlty Towers. Someone please help me before I start whacking the thing with a plant. Thanks, Alex On Saturday 17 January 2004 07:13 am, David Fleck wrote: Creating DISK da0 Have you tried mounting various /dev/da0* devices? To get a list of them, execute: ls -al /dev/da0* Best of luck, Andrew Gould ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
trouble mounting a zip drive on parallel port
Here's on of those things that should be simple but is giving me a surprising number of headachs... I'm trying to mount a parallel zip drive on FreeBSD 4.8. I did re-configure my kernel to include the vpo driver and I get the following message on dmesg: vpo0: Iomega VPI0 Parallel to SCSI interface on ppbus0 vpo0: EPP mode vpo0: VP0 error/timeout (5) vpo0: VP0 error/timeout (5) The errors are a little worrying, but it does seem to be seeing the drive. Then, when trying to mount it, I get this error: mount_msdos: /dev/da0s4: Device not configured I'm sure there's something very small and simple that I'm doing wrong, and I'd be grateful if someone would kindly point it out. Thanks a lot, Alex ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: trouble mounting a zip drive on parallel port
Alex Walker asked on Saturday January 17, 2004: Here's on of those things that should be simple but is giving me a surprising number of headachs... I'm trying to mount a parallel zip drive on FreeBSD 4.8. I did re-configure my kernel to include the vpo driver and I get the following message on dmesg: vpo0: Iomega VPI0 Parallel to SCSI interface on ppbus0 vpo0: EPP mode vpo0: VP0 error/timeout (5) vpo0: VP0 error/timeout (5) The errors are a little worrying, but it does seem to be seeing the drive. Then, when trying to mount it, I get this error: mount_msdos: /dev/da0s4: Device not configured I'm sure there's something very small and simple that I'm doing wrong, and I'd be grateful if someone would kindly point it out. Thanks a lot, Alex Just a stab in the dark, because I haven't used this device - can you mount da0s4a or da0s4c ? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
trouble mounting a zip drive on parallel port
Here's on of those things that should be simple but is giving me a surprising number of headachs... I'm trying to mount a parallel zip drive on FreeBSD 4.8. I did re-configure my kernel to include the vpo driver and I get the following message on dmesg: vpo0: Iomega VPI0 Parallel to SCSI interface on ppbus0 vpo0: EPP mode vpo0: VP0 error/timeout (5) vpo0: VP0 error/timeout (5) The errors are a little worrying, but it does seem to be seeing the drive. Then, when trying to mount it, I get this error: mount_msdos: /dev/da0s4: Device not configured I'm sure there's something very small and simple that I'm doing wrong, and I'd be grateful if someone would kindly point it out. Thanks a lot, Alex __ Do you Yahoo!? Yahoo! Hotjobs: Enter the Signing Bonus Sweepstakes http://hotjobs.sweepstakes.yahoo.com/signingbonus ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
zip drive problem
I have one zip250 disk that is not mounting. It gives the error: dev/afd0: Operation not permitted All the rest of my disks mount properly, and work fine. I need to recover data from this disk. Any ideas? -- Kirk R. Wythers Department of Forest Resources Tel: 612.625.2261 University of Minnesota Fax: 612.625.5211530 Cleveland Ave. N Email: [EMAIL PROTECTED]Saint Paul, MN 55108 USA ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
problem with parallel port ZIP drive (100MB)
Help! I can't use my parallel port iomega ZIP drive on FreeBSD. I think that I followed all the instructions (from the ZIP drive article under /usr/share/doc/en/articles) correctly, but obviously I missed something :-( What I did was: 1. Configure the kernel: the (as far as I have understood) important lines of my kernel configuration PCKERNEL were: # SCSI peripherals # the next two are required by vpo device (Iomega ZIP drive) device scbus # SCSI bus (required) device da # Direct Access (disks) # the rest is not necessary #device sa # Sequential Access (tape etc) #device cd # CD #device pass# Passthrough device (direct SCSI access) # Parallel port device ppc0at isa? irq 7 device ppbus # Parallel port bus (required) #device lpt # Printer #device plip# TCP/IP over parallel device ppi # Parallel port interface device device vpo # Requires scbus and da 1a. Compile the kernel with: cd /usr/src; make buildkernel KERNCONF=PCKERNEL 1b. Install it: make installkernel KERNCONF=PCKERNEL 2. Reboot: During boot, the system hung for a few seconds and some timeout messages from vpo appeared on the screen. The last lines of dmesg output are: ppc0: Parallel port at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode ppi0: Parallel I/O on ppbus0 vpo0: Iomega VPI0 Parallel to SCSI interface on ppbus0 vpo0: EPP mode ad0: 38166MB WDC WD400BB-00DEA0 [77545/16/63] at ata0-master UDMA33 ad1: 12416MB QUANTUM FIREBALL CX13.0A [25228/16/63] at ata0-slave UDMA33 acd0: CDROM FX4820T at ata1-master PIO4 acd1: CD-RW AOPEN CD-RW CRW4048 1.05 20020605 at ata1-slave PIO4 vpo0: VP0 error/timeout (5) vpo0: VP0 error/timeout (5) vpo0: VP0 error/timeout (2) vpo0: VP0 error/timeout (5) vpo0: VP0 error/timeout (5) vpo0: VP0 error/timeout (5) vpo0: VP0 error/timeout (5) vpo0: VP0 error/timeout (5) vpo0: VP0 error/timeout (5) vpo0: VP0 error/timeout (2) vpo0: VP0 error/timeout (5) vpo0: VP0 error/timeout (5) vpo0: VP0 error/timeout (5) Mounting root from ufs:/dev/ad0s1a That is, something went wrong here already?! 3. When I tried to mount, the mount was unsuccessful, of course :-( # mount_msdos /dev/da1s4 /mnt mount_msdos: /dev/da1s4: Device not configured Any hint highly appreciated! Thanks, Vivenzio Pagliari ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
USB zip drive problems continued
Hello- i am having problems getting my usb zip drive working on freebsd 4.7. so far i have created these devices cd /dev sh MAKEDEV usb1 usb2 this is the error that i get at boot time... --- dmesg | grep umass umass0: Iomega USB Zip 100, rev 1.00/1.00, addr 3 umass0: Get Max Lun not supported (STALLED) umass0: BBB reset failed, IOERROR camcontrol devlist -v at scbus-1 target -1 lun -1 (xpt0) usbdevs -v Controller /dev/usb0: addr 1: I/O error addr 2: I/O error addr 3: I/O error addr 4: I/O error addr 5: I/O error addr 6: I/O error addr 7: I/O error addr 8: I/O error addr 9: I/O error addr 10: I/O error addr 11: I/O error addr 12: I/O error addr 13: I/O error addr 14: I/O error addr 15: I/O error addr 16: I/O error addr 17: I/O error addr 18: I/O error addr 19: I/O error addr 20: I/O error addr 21: I/O error addr 22: I/O error addr 23: I/O error addr 24: I/O error addr 25: I/O error addr 26: I/O error addr 27: I/O error addr 28: I/O error addr 29: I/O error addr 30: I/O error addr 31: I/O error addr 32: I/O error addr 33: I/O error addr 34: I/O error addr 35: I/O error addr 36: I/O error addr 37: I/O error addr 38: I/O error addr 39: I/O error addr 40: I/O error addr 41: I/O error addr 42: I/O error addr 43: I/O error addr 44: I/O error addr 45: I/O error addr 46: I/O error addr 47: I/O error addr 48: I/O error addr 49: I/O error addr 50: I/O error addr 51: I/O error addr 52: I/O error addr 53: I/O error addr 54: I/O error addr 55: I/O error addr 56: I/O error addr 57: I/O error addr 58: I/O error addr 59: I/O error addr 60: I/O error addr 61: I/O error addr 62: I/O error addr 63: I/O error addr 64: I/O error addr 65: I/O error addr 66: I/O error addr 67: I/O error addr 68: I/O error addr 69: I/O error addr 70: I/O error addr 71: I/O error addr 72: I/O error addr 73: I/O error addr 74: I/O error addr 75: I/O error addr 76: I/O error addr 77: I/O error addr 78: I/O error addr 79: I/O error addr 80: I/O error addr 81: I/O error addr 82: I/O error addr 83: I/O error addr 84: I/O error addr 85: I/O error addr 86: I/O error addr 87: I/O error addr 88: I/O error addr 89: I/O error addr 90: I/O error addr 91: I/O error addr 92: I/O error addr 93: I/O error addr 94: I/O error addr 95: I/O error addr 96: I/O error addr 97: I/O error addr 98: I/O error addr 99: I/O error addr 100: I/O error addr 101: I/O error addr 102: I/O error addr 103: I/O error addr 104: I/O error addr 105: I/O error addr 106: I/O error addr 107: I/O error addr 108: I/O error addr 109: I/O error addr 110: I/O error addr 111: I/O error addr 112: I/O error addr 113: I/O error addr 114: I/O error addr 115: I/O error addr 116: I/O error addr 117: I/O error addr 118: I/O error addr 119: I/O error addr 120: I/O error addr 121: I/O error addr 122: I/O error addr 123: I/O error addr 124: I/O error addr 125: I/O error addr 126: I/O error addr 127: I/O error any suggestions? thanks, brian To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
usb zip drive
after i boot my machine i would like to attatch a usb zip drive. does freebsd scan for new hardware when it is plugged in or is this a manual process? if so what tools are out there to perform these tasks? cheers, b To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: usb zip drive
Your drive should be recognized by umass, you'll be able to view the device name it is assigned in the output form dmesg. All you should need to do is create an entry for it in /etc/fstab On Wednesday 19 February 2003 18:36, Brian Henning wrote: after i boot my machine i would like to attatch a usb zip drive. does freebsd scan for new hardware when it is plugged in or is this a manual process? if so what tools are out there to perform these tasks? cheers, b To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message -- Willie Viljoen Freelance IT Consultant 214 Paul Kruger Avenue, Universitas Bloemfontein 9321 South Africa +27 51 522 15 60 +27 51 522 44 36 (after hours) +27 82 404 03 27 (mobile) [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: usb zip drive
i am not sure it will be in my dmesg if the device doesn't exist on boot.. or will dmesg hold info about devices loaded after boot? -Original Message- From: Willie Viljoen [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 19, 2003 10:41 AM To: Brian Henning Cc: [EMAIL PROTECTED] Subject: Re: usb zip drive Your drive should be recognized by umass, you'll be able to view the device name it is assigned in the output form dmesg. All you should need to do is create an entry for it in /etc/fstab On Wednesday 19 February 2003 18:36, Brian Henning wrote: after i boot my machine i would like to attatch a usb zip drive. does freebsd scan for new hardware when it is plugged in or is this a manual process? if so what tools are out there to perform these tasks? cheers, b To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message -- Willie Viljoen Freelance IT Consultant 214 Paul Kruger Avenue, Universitas Bloemfontein 9321 South Africa +27 51 522 15 60 +27 51 522 44 36 (after hours) +27 82 404 03 27 (mobile) [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: usb zip drive
On Wed, Feb 19, 2003 at 10:46:20AM -0600, Brian Henning wrote: i am not sure it will be in my dmesg if the device doesn't exist on boot.. or will dmesg hold info about devices loaded after boot? dmesg will show you the most recent kernel messages, which can appear at any poing during operation, not just at boot. So basically, yes. Hope this helps. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
ZIP Drive
I'm looking for help with mounting a zip drive under FreeBSD. I have Googled around on this but haven't found anyone with the same problem or even better a solution. I leave the ZIP disk in the drive before booting the kernel like all the help files say and it picks it up: da0 at vpo0 bus 0 target 6 lun 0 da0: IOMEGA ZIP 100 J.03 Removable Direct Access SCSI-2 device da0: 96MB (196608 512 byte sectors: 64H 32S/T 96C) But when I try to mount it: mount -t msdos /dev/da0 /mnt it gives me : msdos: /dev/da0: Invalid argument Why does this keep happening?? What am I doing wrong? -- It takes two to lie Marge, one to lie and one to listen. PGP Public Key: http://konundrum.org/schrodinger.asc To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: ZIP Drive
Read... http://www.freebsd.org/doc/en_US.ISO8859-1/articles/zip-drive/x86.html On Fri, 17 Jan 2003, Schrodinger wrote: I'm looking for help with mounting a zip drive under FreeBSD. I have Googled around on this but haven't found anyone with the same problem or even better a solution. I leave the ZIP disk in the drive before booting the kernel like all the help files say and it picks it up: da0 at vpo0 bus 0 target 6 lun 0 da0: IOMEGA ZIP 100 J.03 Removable Direct Access SCSI-2 device da0: 96MB (196608 512 byte sectors: 64H 32S/T 96C) But when I try to mount it: mount -t msdos /dev/da0 /mnt it gives me : msdos: /dev/da0: Invalid argument Why does this keep happening?? What am I doing wrong? -- It takes two to lie Marge, one to lie and one to listen. PGP Public Key: http://konundrum.org/schrodinger.asc To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: ZIP Drive
mount -t msdos /dev/da0 /mnt msdos: /dev/da0: Invalid argument Why does this keep happening?? What am I doing wrong? In the past I found that the zip disks had some odd partitioning. I often found the primary partition to be the 4th partition on the disk (the first three being empty/non-existant/zero-size). The first thing that sticks out to me above though is that you are not attempting to mount a partition, but the raw disk. Try mounting one of: da0s1 da0s2 da0s3 da0s4 -- I think it is probably this one. - Mike To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
mount usb zip drive
Dear FreeBSD Support, I've got FBD v. 4.6.2 and upon boot see that the usb drivers load and that Iomega Zip 100 loads. But how do I mount the usb zip drive? I've tried mount /dev/usb0 as well as mount /dev/umass0 but get messages stating to the effect of not a device or file. Thank you, Ted 17 Dec. 2002 __ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
[Fwd: Re: ATAPI Zip Drive. Please Help!]
I'm running 3.5-STABLE, and have the Zip Drive working fine: wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): ST36540A wd0: 6204MB (12706470 sectors), 13446 cyls, 15 heads, 63 S/T, 512 B/S wdc0: unit 1 (wd1): FUJITSU M1638TAU wd1: 2452MB (5021856 sectors), 4982 cyls, 16 heads, 63 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 1 (wd3): IOMEGA ZIP 100 wd3: 96MB (196608 sectors), 512 cyls, 12 heads, 32 S/T, 512 B/S wdc1: unit 0 (atapi): SAMSUNG DVD-ROM SD-604/FT10, removable, accel, dma, iordis My /etc/fstab: # DeviceMountpoint FStype Options Dump Pass# /dev/wd1s1b none swap sw 00 /dev/wd1s1a / ufsrw 11 /dev/wd1s1f /usr ufsrw 22 /dev/wd1s1e /var ufsrw 22 /dev/wcd0c /cdrom cd9660 ro,noauto 00 /dev/wd3s1 /zip msdos ro,noauto 22 proc/proc procfs rw 00 Sorry if the output is all over the screen. You might need to cd /dev and do sh MAKEDEV afd0s and then trying the /dev/afd0s1 thru s4. I dont know.. I dont run 4.6 with a zip drive so I cant give ya an exact device. Good Luck! Mohsin AbdulRahman [EMAIL PROTECTED] Brian M. Kincaid said: Hi, 1) Google search iomega zip freebsd 2) pick SCSI Iomega ZIP drives under FreeBSD link 3) read page 4) use slice 4 as indicated Good luck, Brian In message [EMAIL PROTECTED], Bryan Cassidy wr ites: OK This is really annoying.. I know I've already asked this questions before but got nothing and really want to get this working so maybe someone could help me out here. I am trying to mount my zip drive in FreeBSD 4.6.2 I am having NO luck what so ever. Here is the output from dmesg about my Zip Drive afd0: 239MB IOMEGA ZIP 250 ATAPI [239/64/32] at ata1-slave PIO3 I have tried almost everything I can think of off the top of my head to mount this damn thing but get this error everytime mount_msdos: /dev/afd0: Invalid argument YES! I have tried /dev/afd0a b c d e f and so on. I get nothing.lol. Well, maybe someone wouldn't mind helping me out here cause so far this is the only hardware problem I am having. - E-Mail: Bryan Cassidy [EMAIL PROTECTED] Gaim: bsdsys Yahoo Messenger: bsdsys Screenshot ~~~ http://deskmod.org/?state=viewskin_id=18160 I have put alot of time in setting up my mail filters. Please do not simply Reply-To: Bryan Cassidy [EMAIL PROTECTED] unless stated to do so. Please reply to my e-mails using the appropriate mailing lists. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message -- Brian M. Kincaid PGP Key: http://wwwkeys.pgp.net:11371/pks/lookup?op=getsearch=0x33656401 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hardware in the body of the message Mohsin AbdulRahman [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
ATAPI Zip Drive. Please Help!
OK This is really annoying.. I know I've already asked this questions before but got nothing and really want to get this working so maybe someone could help me out here. I am trying to mount my zip drive in FreeBSD 4.6.2 I am having NO luck what so ever. Here is the output from dmesg about my Zip Drive afd0: 239MB IOMEGA ZIP 250 ATAPI [239/64/32] at ata1-slave PIO3 I have tried almost everything I can think of off the top of my head to mount this damn thing but get this error everytime mount_msdos: /dev/afd0: Invalid argument YES! I have tried /dev/afd0a b c d e f and so on. I get nothing.lol. Well, maybe someone wouldn't mind helping me out here cause so far this is the only hardware problem I am having. - E-Mail: Bryan Cassidy [EMAIL PROTECTED] Gaim: bsdsys Yahoo Messenger: bsdsys Screenshot ~~~ http://deskmod.org/?state=viewskin_id=18160 I have put alot of time in setting up my mail filters. Please do not simply Reply-To: Bryan Cassidy [EMAIL PROTECTED] unless stated to do so. Please reply to my e-mails using the appropriate mailing lists. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: ATAPI Zip Drive. Please Help!
Hi,
1) Google search iomega zip freebsd
2) pick SCSI Iomega ZIP drives under FreeBSD link
3) read page
4) use slice 4 as indicated
Good luck,
Brian
In message [EMAIL PROTECTED], Bryan Cassidy wr
ites:
OK This is really annoying.. I know I've already asked this questions
before but got nothing and really want to get this working so maybe
someone could help me out here. I am trying to mount my zip drive in
FreeBSD 4.6.2 I am having NO luck what so ever. Here is the output
from dmesg about my Zip Drive
afd0: 239MB IOMEGA ZIP 250 ATAPI [239/64/32] at ata1-slave PIO3
I have tried almost everything I can think of off the top of my head
to mount this damn thing but get this error everytime
mount_msdos: /dev/afd0: Invalid argument
YES! I have tried /dev/afd0a b c d e f and so on. I get
nothing.lol. Well, maybe someone wouldn't mind helping me out here
cause so far this is the only hardware problem I am having.
-
E-Mail: Bryan Cassidy [EMAIL PROTECTED]
Gaim: bsdsys
Yahoo Messenger: bsdsys
Screenshot ~~~
http://deskmod.org/?state=viewskin_id=18160
I have put alot of time in setting up my mail filters. Please do not
simply Reply-To: Bryan Cassidy [EMAIL PROTECTED] unless
stated to do so. Please reply to my e-mails using the appropriate
mailing lists.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message
--
Brian M. Kincaid
PGP Key: http://wwwkeys.pgp.net:11371/pks/lookup?op=getsearch=0x33656401
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message
Re: My Zip Drive
On Mon, 14 Oct 2002 11:47:50 -0700 (PDT) Linh Pham [EMAIL PROTECTED] wrote: On 2002-10-14, Bryan Cassidy scribbled: # I am using FreeBSD 4.6.2 I have a Zip Drive on my machine. I try using # mount_msdos /dev/afd0 /mnt as root and I hear it trying to mount it # but get a error saying Invalid argument. You may need to add the slice moniker to the device, i.e.: mount_msdos /dev/afd0a /mnt -- Linh Pham [EMAIL PROTECTED] Webmaster and FreeBSD Geekhttp://closedsrc.org closedsrc.org Every solution breeds new problems Well, I did what you said do and tried mount_msdos /dev/afd0a /mnt and still getthis [bryanc2000@insightbb]/home/bryanc2000# mount_msdos /dev/afd0a /mnt/ mount_msdos: /dev/afd0a: Invalid argument To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: My Zip Drive
On Mon, 14 Oct 2002 14:12:29 -0700 (PDT) Linh Pham [EMAIL PROTECTED] wrote: Based on the example from that page, replace afd0a with afd0s4 and see if it works for you or not. It's been a while since I've had to mount a Zip disk on FreeBSD... OK i did that and I get a new error from that. [bryanc2000@insightbb]/home/bryanc2000# mount_msdos /dev/afd0s4 /mnt/ mount_msdos: /dev/afd0s4: Device not configured [bryanc2000@insightbb]/home/bryanc2000# I dont know what else to do but it would be nice to get it working and get some more zip disks instead of these damn floppies. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Iomega Zip Drive...
Hello, I have an Iomega Zip Drive (100) that I would like to get running with FreeBSD. I have the devices 'umass', 'uhci', and 'usb' specified in my kernel config; however, I am getting these errors on boot: /kernel: umass0: Iomega USB Zip 100, rev 1.00/1.00, addr 2 /kernel: umass0: Get Max Lun not supported (STALLED) /kernel: umass0: BBB reset failed, TIMEOUT /kernel: umass0: BBB bulk-in clear stall failed, TIMEOUT /kernel: umass0: BBB bulk-out clear stall failed, TIMEOUT /kernel: umass0: BBB reset failed, TIMEOUT /kernel: umass0: BBB bulk-in clear stall failed, TIMEOUT /kernel: umass0: BBB bulk-out clear stall failed, TIMEOUT /kernel: umass0: BBB reset failed, TIMEOUT /kernel: umass0: BBB bulk-in clear stall failed, TIMEOUT /kernel: umass0: BBB bulk-out clear stall failed, TIMEOUT /kernel: umass0: BBB reset failed, TIMEOUT /kernel: umass0: BBB bulk-in clear stall failed, TIMEOUT /kernel: umass0: BBB bulk-out clear stall failed, TIMEOUT /kernel: umass0: BBB reset failed, TIMEOUT /kernel: umass0: BBB bulk-in clear stall failed, TIMEOUT /kernel: umass0: BBB bulk-out clear stall failed, TIMEOUT This was from a single boot, and, as you can imagine, all of those TIMEOUTS get a little annoying and take a great deal of time. Anyway, I've checked through my boot messages and nothing else seems to be going wrong. Any suggestions? Thanks, Jason To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
