ZIP Drive on Parallel port in SuSE 10.0 Boxed Ed.
Hi, I used "modprobe ppa" and "dmesg" and fouind the following info for my Iomega ZIP100 parellel port drive: Vendor: IOMEGA Model: ZIP 100 Rev: P.05 Type: Direct-Access ANSI SCSI revision: 02 SCSI device sda: 196608 512-byte hdwr sectors (101 MB) sda: Write Protect is off sda: Mode Sense: 25 00 00 08 sda: cache data unavailable sda: assuming drive cache: write through SCSI device sda: 196608 512-byte hdwr sectors (101 MB) sda: Write Protect is off sda: Mode Sense: 25 00 00 08 sda: cache data unavailable sda: assuming drive cache: write through sda: sda4 Attached scsi removable disk sda at scsi0, channel 0, id 6, lun 0 Attached scsi generic sg0 at scsi0, channel 0, id 6, lun 0, type 0 Does anyone out there know the path I should set in Konqueror>Storage Media>Edit>Selection>Create New>Link to Device>Zip Device? My system did find it somehow after this as I was writing this...The device started blinking wildly for a moment, clicked, and then stopped. Some communicatiion took place. Thanks, -Joe G moment and the stopped.
It's communicating via the VP12 (imm) interface. Joe G wrote:
Hi,
I used "modprobe ppa" and "dmesg" and fouind the following info for my Iomega ZIP100 parellel port drive:
Vendor: IOMEGA Model: ZIP 100 Rev: P.05 Type: Direct-Access ANSI SCSI revision: 02 SCSI device sda: 196608 512-byte hdwr sectors (101 MB) sda: Write Protect is off sda: Mode Sense: 25 00 00 08 sda: cache data unavailable sda: assuming drive cache: write through SCSI device sda: 196608 512-byte hdwr sectors (101 MB) sda: Write Protect is off sda: Mode Sense: 25 00 00 08 sda: cache data unavailable sda: assuming drive cache: write through sda: sda4 Attached scsi removable disk sda at scsi0, channel 0, id 6, lun 0 Attached scsi generic sg0 at scsi0, channel 0, id 6, lun 0, type 0
Does anyone out there know the path I should set in Konqueror>Storage Media>Edit>Selection>Create New>Link to Device>Zip Device?
My system did find it somehow after this as I was writing this...The device started blinking wildly for a moment, clicked, and then stopped. Some communicatiion took place.
Thanks, -Joe G moment and the stopped.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Friday 2006-01-20 at 16:27 -0500, Joe G wrote:
sda: assuming drive cache: write through sda: sda4 Attached scsi removable disk sda at scsi0, channel 0, id 6, lun 0 Attached scsi generic sg0 at scsi0, channel 0, id 6, lun 0, type 0
Does anyone out there know the path I should set in Konqueror>Storage Media>Edit>Selection>Create New>Link to Device>Zip Device?
I don't know about konkeror, but it obviously is at /dev/sda4. You can define the traditional entry in fstab. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFD0aI+tTMYHG2NR9URAtqvAJ9cA8/aO+hVDe076VxDkk7AIpe72wCeKtdQ o6/8pXYeaHvQBki0967de7Y= =ZOud -----END PGP SIGNATURE-----
On Friday 20 January 2006 13:27, Joe G wrote:
Does anyone out there know the path I should set in Konqueror>Storage Media>Edit>Selection>Create New>Link to Device>Zip Device?
I'm not *positive* where you are talking about, but if you mean to create a new device link from the create new menu (that pops up on a right-click on the desktop or in Konqi in file manager mode at the Edit menu) Create New->Link to device->Zip Device... Then in the device tab, in the device drop-down list, you should have /dev/sda4 (in your case) HTH Mark
Mark A. Taff wrote:
On Friday 20 January 2006 13:27, Joe G wrote:
Does anyone out there know the path I should set in Konqueror>Storage Media>Edit>Selection>Create New>Link to Device>Zip Device?
I'm not *positive* where you are talking about, but if you mean to create a new device link from the create new menu (that pops up on a right-click on the desktop or in Konqi in file manager mode at the Edit menu) Create New->Link to device->Zip Device...
Then in the device tab, in the device drop-down list, you should have /dev/sda4 (in your case)
HTH
Mark
It's not there. Yes, it is definitely /dev/sda4, but /dev/sda4 is not on the drop down menu. I tried manually adding the path in the blank box at the top of the drop down list, but it still cannot access it. I even tried the following: "To use the ZIP drive with Linux, you must have a kernel configured with support for the SCSI system, support for SCSI disks, and support for the host adapter you are using. If you are not familiar with building a kernel, you should read up on the Linux Kernel HOWTO http://metalab.unc.edu/mdw/HOWTO/Kernel-HOWTO.html for information. You must begin the process of building a kernel with the configuration step. Here, you identify the specific kernel components that you need. First step | cd /usr/src/linux|. There are several ways to actually do the configuration. Under X windows I use *make xconfig*. There is also |make menuconfig| or |make config| for command line prompts. The easiest way is with xconfig. In the section *SCSI Support* set *SCSI support = Y*. Also set *SCSI disk support = Y*. In the section *SCSI low-level drivers* you want to set *IOMEGA Parallel Port ZIP drive SCSI support = M*. The M stands for modules. In the section *Character Devices* find and set *Parallell Printer support = M* If you are a bit unsure about any of this, use zdisk for the make step. This will build and install the kernel to floppy. If you screw it up somehow, you still have a good bootable system on the hard drive. Now build the kernel with these steps: * make dep * make clean * make zImage or zlilo or zdisk * make modules * make mdoules_install *hint* if you want to create an output log of the make zImage step you can use" I did try "Xconfig." I t brought me to a tree where I only had the options to either check or uncheck, not enter values. "Make config" brought me to a series of questions I really didn't feel comfortable answering... it seemed to want me to make changes to the kernel other than relating to the zip drive. I've strayed dangerously close to rewriting the whole kernel. The URL of what I've been trying to follow is: http://howtos.linux.com/howtos/ZIP-Drive-3.shtml I might just give this up before I invent a new, non-working variant of minix. -Joe ||
On Friday 20 January 2006 19:39, Joe G wrote:
I did try "Xconfig." I t brought me to a tree where I only had the options to either check or uncheck, not enter values. "Make config" brought me to a series of questions I really didn't feel comfortable answering... it seemed to want me to make changes to the kernel other than relating to the zip drive. I've strayed dangerously close to rewriting the whole kernel.
The URL of what I've been trying to follow is: http://howtos.linux.com/howtos/ZIP-Drive-3.shtml
I might just give this up before I invent a new, non-working variant of minix.
-Joe
You shouldn't have to do anything that drastic. That tutorial is almost four years old--things have gotten better since then. I am 99.999% sure that your stock kernel was compiled with SCSI support. Please post the contents of your /etc/fstab file. Mark
Mark A. Taff wrote:
You shouldn't have to do anything that drastic. That tutorial is almost four years old--things have gotten better since then. I am 99.999% sure that your stock kernel was compiled with SCSI support.
Please post the contents of your /etc/fstab file.
Mark
I tried the following and permission keeps getting denied: joegum@linux:~> su Password: linux:/home/joegum # /etc/fstab bash: /etc/fstab: Permission Denied linux:/home/joegum # cd /usr/src/linux linux :/etc/fstab: Permission Denied linux:/usr/src/linux # I also tried browsing with File Manager - Superuser Mode No luck. -Joe
Joe G wrote:
Mark A. Taff wrote:
You shouldn't have to do anything that drastic. That tutorial is almost four years old--things have gotten better since then. I am 99.999% sure that your stock kernel was compiled with SCSI support.
Please post the contents of your /etc/fstab file.
Mark
Oops! I found a way. Sorry 'bout that. Thanks, -Joe /dev/hda6 / reiserfs acl,user_xattr 1 1 /dev/hda1 /windows/C ntfs ro,users,gid=users,umask=0002,nls=utf8 0 0 /dev/hda5 swap swap defaults 0 0 proc /proc proc defaults 0 0 sysfs /sys sysfs noauto 0 0 usbfs /proc/bus/usb usbfs noauto 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 /dev/cdrecorder /media/cdrecorder subfs noauto,fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0 /dev/fd0 /media/floppy subfs noauto,fs=floppyfss,procuid,nodev,nosuid,sync 0 0 none /subdomain subdomainfs noauto 0 0
On Friday 20 January 2006 20:06, Joe G wrote:
Joe G wrote:
Mark A. Taff wrote:
You shouldn't have to do anything that drastic. That tutorial is almost four years old--things have gotten better since then. I am 99.999% sure that your stock kernel was compiled with SCSI support.
Please post the contents of your /etc/fstab file.
Mark
Oops! I found a way. Sorry 'bout that.
Thanks, -Joe
/dev/hda6 / reiserfs acl,user_xattr 1 1 /dev/hda1 /windows/C ntfs ro,users,gid=users,umask=0002,nls=utf8 0 0 /dev/hda5 swap swap defaults 0 0 proc /proc proc defaults 0 0 sysfs /sys sysfs noauto 0 0 usbfs /proc/bus/usb usbfs noauto 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 /dev/cdrecorder /media/cdrecorder subfs noauto,fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0 /dev/fd0 /media/floppy subfs noauto,fs=floppyfss,procuid,nodev,nosuid,sync 0 0 none /subdomain subdomainfs noauto 0 0
You need to add a line like so to your /etc/fstab: /dev/sda4 /media/zip auto noauto,user 0 0 To edit your /etc/fstab, I like to use `pico /etc/fstab` (not installed by default). Some others like `joe /etc/fstab` That will make mounting the zip drive easier. You need to make sure that the folder /media/zip actually exists, if nor make it. `ls /media` and make sure it shows the zip folder. If not, `mkdir /media/zip` Do all this as root. Then you should be able to mount the drive with something like `mount /dev/sda4 /media/zip` Literally, "mount the filesystem you the device sda4 so I can access it at /media/zip". There are shorter and longer invocations. See `man mount` and `man umount` for more info. HTH Mark
Mark A. Taff wrote:
You need to add a line like so to your /etc/fstab:
/dev/sda4 /media/zip auto noauto,user 0 0
To edit your /etc/fstab, I like to use `pico /etc/fstab` (not installed by default). Some others like `joe /etc/fstab`
That will make mounting the zip drive easier. You need to make sure that the folder /media/zip actually exists, if nor make it.
`ls /media` and make sure it shows the zip folder. If not, `mkdir /media/zip`
Do all this as root. Then you should be able to mount the drive with something like `mount /dev/sda4 /media/zip` Literally, "mount the filesystem you the device sda4 so I can access it at /media/zip".
There are shorter and longer invocations. See `man mount` and `man umount` for more info.
HTH
Mark
Ok Mark, I've entered the text (/dev/sda4...). How do I make it permanent? If I hitt ENTER, it just goes down a line. Sorry to be so dumb. -Joe
On Friday 20 January 2006 20:39, Joe G wrote:
Ok Mark, I've entered the text (/dev/sda4...). How do I make it permanent? If I hitt ENTER, it just goes down a line. Sorry to be so dumb.
-Joe
If you are in pico, CRTL + X will exit, promting to save the modified buffer. Say Y to save. CTRL + O will save with exiting pico. Mark
Mark A. Taff wrote:
If you are in pico, CRTL + X will exit, promting to save the modified buffer. Say Y to save. CTRL + O will save with exiting pico.
Mark
Hi Mark, I did exactly as you said, but there still seems to be a problem I verified (cat) that the line you wanted added to /etc/fstab was there. ls /media doesn't list it. I've included the output below. Thanks, -Joe joegum@linux:~> su Password: linux:/home/joegum # pico /etc/fstab linux:/home/joegum # ls /media . .. bmp_audio_cd cdrecorder floppy SU1000_001 xmms_audio_cd linux:/home/joegum # mkdir /media/zip linux:/home/joegum # mount /dev/sda4 /media/zip mount: special device /dev/sda4 does not exist linux:/home/joegum # pico /etc/fstab linux:/home/joegum # mount /dev/sda4 /media/zip mount: special device /dev/sda4 does not exist linux:/home/joegum #
On Friday 20 January 2006 21:13, Joe G wrote:
I did exactly as you said, but there still seems to be a problem I verified (cat) that the line you wanted added to /etc/fstab was there. ls /media doesn't list it. I've included the output below.
Thanks, -Joe
joegum@linux:~> su Password: linux:/home/joegum # pico /etc/fstab linux:/home/joegum # ls /media . .. bmp_audio_cd cdrecorder floppy SU1000_001 xmms_audio_cd linux:/home/joegum # mkdir /media/zip linux:/home/joegum # mount /dev/sda4 /media/zip mount: special device /dev/sda4 does not exist linux:/home/joegum # pico /etc/fstab linux:/home/joegum # mount /dev/sda4 /media/zip mount: special device /dev/sda4 does not exist linux:/home/joegum #
Make sure you have a formatted zip disk in the drive. As root, `cat /proc/diskstats` You should get lines like so: 8 1 sda1 44459 44781 0 0 8 2 sda2 643 2100 14 26 8 3 sda3 306 432 0 0 8 4 sda4 6 12 0 0 8 5 sda5 11390 135714 16218 129744 8 6 sda6 15558 248306 8625 69000 8 7 sda7 2809 110314 15318 122544 8 8 sda8 1088 9282 5918 47288 22 0 hdc 0 0 0 0 0 0 0 0 0 0 0 22 64 hdd 4 15 152 258 0 0 0 0 0 258 258 One of these should represent your zip disk, should be sda4. Your hard drive is hda, your cdrom is either hdb, hdc, or hdd (aka cdrecorder). If you peek through these, you should be able to determine for sure that your zip drive is sda4. Try mounting with `mount -t vfat /media/zip` Is the drive showing any signs of life? Mark
Mark A. Taff wrote:
Make sure you have a formatted zip disk in the drive.
As root, `cat /proc/diskstats`
You should get lines like so:
8 1 sda1 44459 44781 0 0 8 2 sda2 643 2100 14 26 8 3 sda3 306 432 0 0 8 4 sda4 6 12 0 0 8 5 sda5 11390 135714 16218 129744 8 6 sda6 15558 248306 8625 69000 8 7 sda7 2809 110314 15318 122544 8 8 sda8 1088 9282 5918 47288 22 0 hdc 0 0 0 0 0 0 0 0 0 0 0 22 64 hdd 4 15 152 258 0 0 0 0 0 258 258
One of these should represent your zip disk, should be sda4. Your hard drive is hda, your cdrom is either hdb, hdc, or hdd (aka cdrecorder). If you peek through these, you should be able to determine for sure that your zip drive is sda4.
Try mounting with `mount -t vfat /media/zip`
Is the drive showing any signs of life?
Mark
Hi Mark, I did as you said. The Zip seems dead. There is an almost full data disk in it. Thanks, -Joe Here's the output: Password: su: incorrect password joegum@linux:~> su Password: linux:/home/joegum # cat /proc/diskstats 2 0 fd0 16 0 32 492 0 0 0 0 0 492 492 1 0 ram0 0 0 0 0 0 0 0 0 0 0 0 1 1 ram1 0 0 0 0 0 0 0 0 0 0 0 1 2 ram2 0 0 0 0 0 0 0 0 0 0 0 1 3 ram3 0 0 0 0 0 0 0 0 0 0 0 1 4 ram4 0 0 0 0 0 0 0 0 0 0 0 1 5 ram5 0 0 0 0 0 0 0 0 0 0 0 1 6 ram6 0 0 0 0 0 0 0 0 0 0 0 1 7 ram7 0 0 0 0 0 0 0 0 0 0 0 1 8 ram8 0 0 0 0 0 0 0 0 0 0 0 1 9 ram9 0 0 0 0 0 0 0 0 0 0 0 1 10 ram10 0 0 0 0 0 0 0 0 0 0 0 1 11 ram11 0 0 0 0 0 0 0 0 0 0 0 1 12 ram12 0 0 0 0 0 0 0 0 0 0 0 1 13 ram13 0 0 0 0 0 0 0 0 0 0 0 1 14 ram14 0 0 0 0 0 0 0 0 0 0 0 1 15 ram15 0 0 0 0 0 0 0 0 0 0 0 7 0 loop0 0 0 0 0 0 0 0 0 0 0 0 7 1 loop1 0 0 0 0 0 0 0 0 0 0 0 7 2 loop2 0 0 0 0 0 0 0 0 0 0 0 7 3 loop3 0 0 0 0 0 0 0 0 0 0 0 7 4 loop4 0 0 0 0 0 0 0 0 0 0 0 7 5 loop5 0 0 0 0 0 0 0 0 0 0 0 7 6 loop6 0 0 0 0 0 0 0 0 0 0 0 7 7 loop7 0 0 0 0 0 0 0 0 0 0 0 3 0 hda 205268 185763 2950981 8689764 78065 96153 1393696 12280032 0 1390028 20970040 3 1 hda1 192410 192416 0 0 3 2 hda2 3 6 0 0 3 5 hda5 388 913 803 6424 3 6 hda6 198030 2755910 173423 1387272 22 0 hdc 963 150 4560 31112 0 0 0 0 0 27452 31112 9 0 md0 0 0 0 0 0 0 0 0 0 0 0 linux:/home/joegum # mount -t vfat /media/zip Usage: mount -V : print version mount -h : print this help mount : list mounted filesystems mount -l : idem, including volume labels So far the informational part. Next the mounting. The command is `mount [-t fstype] something somewhere'. Details found in /etc/fstab may be omitted. mount -a [-t|-O] ... : mount all stuff from /etc/fstab mount device : mount device at the known place mount directory : mount known device here mount -t type dev dir : ordinary mount command Note that one does not really mount a device, one mounts a filesystem (of the given type) found on the device. One can also mount an already visible directory tree elsewhere: mount --bind olddir newdir or move a subtree: mount --move olddir newdir A device can be given by name, say /dev/hda1 or /dev/cdrom, or by label, using -L label or by uuid, using -U uuid . Other options: [-nfFrsvw] [-o options] [-p passwdfd]. For many more details, say man 8 mount . linux:/home/joegum # mount /dev/hda6 on / type reiserfs (rw,acl,user_xattr) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) tmpfs on /dev/shm type tmpfs (rw) devpts on /dev/pts type devpts (rw,mode=0620,gid=5) /dev/hda1 on /windows/C type ntfs (ro,noexec,nosuid,nodev,gid=100,umask=0002,nls=utf8) none on /subdomain type subdomainfs (rw) usbfs on /proc/bus/usb type usbfs (rw) /dev/fd0 on /media/floppy type subfs (rw,nosuid,nodev,sync,fs=floppyfss,procuid) /dev/hdc on /media/cdrecorder type subfs (ro,nosuid,nodev,fs=cdfss,procuid,iocharset=utf8) linux:/home/joegum #
More info... My system was acting strangely while on line.... My pc and my AlphaShiled Firewall were both blinking furiouswly, even though I wasn't doing anything significant on line. So, I decided to run rkhunter. It found something that I think is relevant to this subject: * Filesystem checks Checking /dev for suspicious files... [ OK ] Scanning for hidden files... [ Warning! ] --------------- /dev/.udevdb /etc/.#fstab /etc/.pwd.lock --------------- Please inspect: /etc/.#fstab (broken symbolic link to `joegum@linux.13378') [Press <ENTER> to continue] I'm not sure what this means, but there seems to be a problem in fstab now. Thanks, -Joe
On Friday 20 January 2006 22:11, Joe G wrote:
Please inspect: /etc/.#fstab (broken symbolic link to `joegum@linux.13378')
I have never known a file like that to be created. The . will make it a hidden file, and the # makes me think it was just to uniquely identify the file. It looks the the file is a link to /home/joegum on a machine named linux.13378. I really don't have much idea about that??? Mark
Mark A. Taff wrote:
On Friday 20 January 2006 22:11, Joe G wrote:
Please inspect: /etc/.#fstab (broken symbolic link to `joegum@linux.13378')
I have never known a file like that to be created. The . will make it a hidden file, and the # makes me think it was just to uniquely identify the file. It looks the the file is a link to /home/joegum on a machine named linux.13378.
I really don't have much idea about that???
Mark
Oh well. I'll go back into fstab and undo what I've done. Thank you for trying. I guess the Zip drive on parallel port won't work on my pc in SuSe. It was very kind of you to try. Thank you, Mark. -Joe
Mark A. Taff wrote:
On Friday 20 January 2006 22:11, Joe G wrote:
Please inspect: /etc/.#fstab (broken symbolic link to `joegum@linux.13378')
I have never known a file like that to be created. The . will make it a hidden file, and the # makes me think it was just to uniquely identify the file. It looks the the file is a link to /home/joegum on a machine named linux.13378.
I really don't have much idea about that???
Mark
Oops, I almost forgot... You taught me alot tonight. Thanks, -Joe
On Friday 20 January 2006 22:33, Joe G wrote:
Oops, I almost forgot...
You taught me alot tonight.
You're welcome. I still think the issue can be fixed. The only reason I can think of for the kernel modules to be mixed up like that is something you did trying to fix the issue, and perhaps rebooting the machine will allow it to find the zip drive. Regards, Mark
On Fri, 2006-01-20 at 22:21 -0800, Mark A. Taff wrote:
On Friday 20 January 2006 22:11, Joe G wrote:
Please inspect: /etc/.#fstab (broken symbolic link to `joegum@linux.13378')
I have never known a file like that to be created. The . will make it a hidden file, and the # makes me think it was just to uniquely identify the file. It looks the the file is a link to /home/joegum on a machine named linux.13378.
I really don't have much idea about that???
Mark
Well, Joe was editing the file as you (Mark) asked him to. Joe seems to be really new to linux and may not have properly exited the editor and left a temp file behind or he is still editing the file. Take your pick. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
Ken Schneider wrote:
Well, Joe was editing the file as you (Mark) asked him to. Joe seems to be really new to linux and may not have properly exited the editor and left a temp file behind or he is still editing the file. Take your pick.
Actually, I came to Linux from MS Windows around 2.5 years ago. I started with Xandros and Knoppix, then played around with a bunch of different distros, but using all as a desktop... not a server. The GUIs have been for the most part adequate for me to do the things I needed to do. I switched to SuSE because there were certain apps that didn't seem to work well in the other distros I tried. I also wanted to explore the wide varietry of Desktop environments / managers that shipped with SuSE. But, I really haven't done much more in the command line other than running the occassional virus scan or rootkit check.... I haven't needed to. But, as you can see, I'll even tackle rewriting the kernel based on some ancient online tutorial. In other words, I'm not afraid to work and learn. -Joe
On Sat, 2006-01-21 at 08:41 -0500, Joe G wrote:
Ken Schneider wrote:
Well, Joe was editing the file as you (Mark) asked him to. Joe seems to be really new to linux and may not have properly exited the editor and left a temp file behind or he is still editing the file. Take your pick.
Actually, I came to Linux from MS Windows around 2.5 years ago. I started with Xandros and Knoppix, then played around with a bunch of different distros, but using all as a desktop... not a server. The GUIs have been for the most part adequate for me to do the things I needed to do. I switched to SuSE because there were certain apps that didn't seem to work well in the other distros I tried. I also wanted to explore the wide varietry of Desktop environments / managers that shipped with SuSE. But, I really haven't done much more in the command line other than running the occassional virus scan or rootkit check.... I haven't needed to. But, as you can see, I'll even tackle rewriting the kernel based on some ancient online tutorial. In other words, I'm not afraid to work and learn.
I think this is fantastic that you are trying to tackle the command line use of linux. Just be prepared for a system that does not boot if you start changing files in /etc and you enter something wrong, it happens to the best of us. I made the statement based on your very little knowledge of /etc/fstab and being able to determine if a drive/partition is available. Keep at it though trying to learn as much as you can, it doesn't all come easy and some of it is downright difficult. Anything is easy, once you know how. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
On Friday 20 January 2006 21:47, Joe G wrote:
I did as you said. The Zip seems dead. There is an almost full data disk in it.
Linux is not seeing the zip drive at all. Does it work when you are in windows? What kernel are you using ( `uname -a` )? What is the output of `lsmod`? Mark
Mark A. Taff wrote:
On Friday 20 January 2006 21:47, Joe G wrote:
I did as you said. The Zip seems dead. There is an almost full data disk in it.
Linux is not seeing the zip drive at all. Does it work when you are in windows? What kernel are you using ( `uname -a` )? What is the output of `lsmod`?
Mark
It works fine when I boot into Xp. The output is below. Btw, This is really nice of you, Mark. Thanks, -Joe Password: linux:/home/joegum # uname -a Linux linux 2.6.13-15.7-default #1 Tue Nov 29 14:32:29 UTC 2005 i686 i686 i386 GNU/Linux linux:/home/joegum # lsmod Module Size Used by parport_pc 38980 0 lp 11460 0 parport 33864 2 parport_pc,lp sg 35744 0 st 38944 0 sd_mod 18576 0 sr_mod 16420 0 scsi_mod 131304 4 sg,st,sd_mod,sr_mod ipt_pkttype 1664 1 ipt_LOG 6912 7 ipt_limit 2304 7 hfsplus 75140 0 vfat 12800 0 fat 49692 1 vfat subfs 7552 2 speedstep_lib 4228 0 freq_table 4612 0 button 7056 0 snd_pcm_oss 59168 0 battery 10244 0 snd_mixer_oss 18944 1 snd_pcm_oss snd_seq 51984 0 snd_seq_device 8588 1 snd_seq ac 5252 0 af_packet 21384 2 edd 9824 0 joydev 9408 0 usblp 12544 0 pcmcia 37176 0 firmware_class 9856 1 pcmcia ohci1394 32820 0 ieee1394 97208 1 ohci1394 ehci_hcd 32136 0 i2c_sis96x 5380 0 i2c_core 20368 1 i2c_sis96x yenta_socket 23820 1 rsrc_nonstatic 12800 1 yenta_socket pcmcia_core 39952 3 pcmcia,yenta_socket,rsrc_nonstatic 8139too 26112 0 snd_intel8x0 33504 1 mii 5504 1 8139too snd_ac97_codec 91004 1 snd_intel8x0 generic 4484 0 [permanent] subdomain 78872 1 snd_ac97_bus 2432 1 snd_ac97_codec ohci_hcd 20228 0 usbcore 112512 4 usblp,ehci_hcd,ohci_hcd snd_pcm 93064 3 snd_pcm_oss,snd_intel8x0,snd_ac97_codec snd_timer 24452 2 snd_seq,snd_pcm snd 60420 10 snd_pcm_oss,snd_mixer_oss,snd_seq,snd_seq_device,snd_intel8x0,snd_ac97_codec,snd_pcm,snd_timer soundcore 9184 1 snd snd_page_alloc 10632 2 snd_intel8x0,snd_pcm shpchp 88676 0 pci_hotplug 26164 1 shpchp sis_agp 8452 1 agpgart 33096 1 sis_agp ip6t_REJECT 5504 3 ipt_REJECT 5632 3 ipt_state 1920 12 iptable_mangle 2688 0 iptable_nat 22228 0 iptable_filter 2816 1 ip6table_mangle 2304 0 ip_conntrack 42168 2 ipt_state,iptable_nat ip_tables 19456 8 ipt_pkttype,ipt_LOG,ipt_limit,ipt_REJECT,ipt_state,iptable_mangle,iptable_nat,iptable_filter ip6table_filter 2688 1 ip6_tables 18176 3 ip6t_REJECT,ip6table_mangle,ip6table_filter ipv6 242752 11 ip6t_REJECT nls_utf8 2048 1 ntfs 182288 1 dm_mod 54972 0 reiserfs 250480 1 fan 4996 0 thermal 14472 0 ide_cd 39684 0 cdrom 36896 2 sr_mod,ide_cd processor 24380 1 thermal sis5513 15752 0 [permanent] ide_disk 17152 4 ide_core 122380 4 generic,ide_cd,sis5513,ide_disk linux:/home/joegum #
On Friday 20 January 2006 22:17, Joe G wrote:
linux:/home/joegum # lsmod Module Size Used by ... parport_pc 38980 0 lp 11460 0 parport 33864 2 parport_pc,lp ...
Something is wrong with your kernel modules. lsmod reports that module paraport_pc is used by no other modules, then it reports that parport actually *is* using paraport_pc (and lp). On my x86_64 machine: parport_pc 44912 1 lp 14336 0 parport 43532 2 parport_pc,lp Not knowing how to reload the kernel and all its modules with a reboot, I'll suggest a reboot here. Mark
Mark A. Taff wrote:
Something is wrong with your kernel modules. lsmod reports that module paraport_pc is used by no other modules, then it reports that parport actually *is* using paraport_pc (and lp).
On my x86_64 machine:
parport_pc 44912 1 lp 14336 0 parport 43532 2 parport_pc,lp
Not knowing how to reload the kernel and all its modules with a reboot, I'll suggest a reboot here.
Mark
I rebooted. I've included the output. Btw, I did go into fstsb and delete that line. I can put it back if you want. -Joe Password: linux:/home/joegum # lsmod Module Size Used by ipt_pkttype 1664 1 ipt_LOG 6912 7 ipt_limit 2304 7 hfsplus 75140 0 vfat 12800 0 fat 49692 1 vfat subfs 7552 2 speedstep_lib 4228 0 freq_table 4612 0 snd_pcm_oss 59168 0 snd_mixer_oss 18944 1 snd_pcm_oss snd_seq 51984 0 snd_seq_device 8588 1 snd_seq button 7056 0 battery 10244 0 ac 5252 0 af_packet 21384 2 edd 9824 0 joydev 9408 0 ip6t_REJECT 5504 3 ipt_REJECT 5632 3 ipt_state 1920 12 usblp 12544 0 iptable_mangle 2688 0 iptable_nat 22228 0 pcmcia 37176 0 firmware_class 9856 1 pcmcia iptable_filter 2816 1 ip6table_mangle 2304 0 ip_conntrack 42168 2 ipt_state,iptable_nat ip_tables 19456 8 ipt_pkttype,ipt_LOG,ipt_limit,ipt_REJECT,ipt_state,iptable_mangle,iptable_nat,iptable_filter ip6table_filter 2688 1 ip6_tables 18176 3 ip6t_REJECT,ip6table_mangle,ip6table_filter ehci_hcd 32136 0 ipv6 242752 11 ip6t_REJECT 8139too 26112 0 snd_intel8x0 33504 1 ohci_hcd 20228 0 usbcore 112512 4 usblp,ehci_hcd,ohci_hcd ohci1394 32820 0 ieee1394 97208 1 ohci1394 yenta_socket 23820 1 rsrc_nonstatic 12800 1 yenta_socket pcmcia_core 39952 3 pcmcia,yenta_socket,rsrc_nonstatic mii 5504 1 8139too snd_ac97_codec 91004 1 snd_intel8x0 snd_ac97_bus 2432 1 snd_ac97_codec i2c_sis96x 5380 0 i2c_core 20368 1 i2c_sis96x generic 4484 0 [permanent] snd_pcm 93064 3 snd_pcm_oss,snd_intel8x0,snd_ac97_codec sis_agp 8452 1 agpgart 33096 1 sis_agp shpchp 88676 0 pci_hotplug 26164 1 shpchp snd_timer 24452 2 snd_seq,snd_pcm snd 60420 10 snd_pcm_oss,snd_mixer_oss,snd_seq,snd_seq_device,snd_intel8x0,snd_ac97_codec,snd_pcm,snd_timer soundcore 9184 1 snd snd_page_alloc 10632 2 snd_intel8x0,snd_pcm subdomain 78872 1 parport_pc 38980 1 lp 11460 0 parport 33864 2 parport_pc,lp nls_utf8 2048 1 ntfs 182288 1 dm_mod 54972 0 reiserfs 250480 1 fan 4996 0 thermal 14472 0 ide_cd 39684 0 cdrom 36896 1 ide_cd processor 24380 1 thermal sis5513 15752 0 [permanent] ide_disk 17152 4 ide_core 122380 4 generic,ide_cd,sis5513,ide_disk linux:/home/joegum #
Mark, After rebooting, I went back into fstab and again added the lines you suggested. I then used the mount.... command. Same result. -Joe
On Friday 20 January 2006 22:57, Joe G wrote:
Mark,
After rebooting, I went back into fstab and again added the lines you suggested. I then used the mount.... command. Same result.
-Joe
And the output of `cat /proc/diskstats`? Mark
On Friday 20 January 2006 22:46, Joe G wrote:
I rebooted. I've included the output. Btw, I did go into fstsb and delete that line. I can put it back if you want.
The lsmod output looks OK now. The line in fstab is only needed to allow non-root users to mount the device, and to make it easier (less typing) to mount the device, as well as to specify other options (like mount read-only). Bottom line is we can get it working first, and then you can add that line back into fstab. So you know, /etc/mtab is like fstab, but it tracks *mounted* filesystems, where fstab holds configure info for filesystems. Also, *never* delete a line from a config file. A good practice is to first make a copy of the line you want to change, and comment it out. Then you make changes (change/delete) to the other line, while you still have a backup of the original line. In most linux config files, including fstab, any text that follows an # mark is a comment, and is skipped over. In pico ctrl+K will cut to clipboard, then crtl+U will paste the original back, and ctrl+U again will paste an extra copy of the line. Now then, `cat /proc/diskstats` to verify if we can now see sda4. You can also try to mount it with `mount /dev/sda4 /media/zip Mark
Mark A. Taff wrote:
On Friday 20 January 2006 22:46, Joe G wrote:
I rebooted. I've included the output. Btw, I did go into fstsb and delete that line. I can put it back if you want.
The lsmod output looks OK now. The line in fstab is only needed to allow non-root users to mount the device, and to make it easier (less typing) to mount the device, as well as to specify other options (like mount read-only).
Bottom line is we can get it working first, and then you can add that line back into fstab. So you know, /etc/mtab is like fstab, but it tracks *mounted* filesystems, where fstab holds configure info for filesystems.
Also, *never* delete a line from a config file. A good practice is to first make a copy of the line you want to change, and comment it out. Then you make changes (change/delete) to the other line, while you still have a backup of the original line. In most linux config files, including fstab, any text that follows an # mark is a comment, and is skipped over.
In pico ctrl+K will cut to clipboard, then crtl+U will paste the original back, and ctrl+U again will paste an extra copy of the line.
Now then, `cat /proc/diskstats` to verify if we can now see sda4.
You can also try to mount it with `mount /dev/sda4 /media/zip
Mark
Here's the output: -Joe Password: linux:/home/joegum # cat /proc/diskstats 2 0 fd0 20 0 40 528 0 0 0 0 0 528 528 1 0 ram0 0 0 0 0 0 0 0 0 0 0 0 1 1 ram1 0 0 0 0 0 0 0 0 0 0 0 1 2 ram2 0 0 0 0 0 0 0 0 0 0 0 1 3 ram3 0 0 0 0 0 0 0 0 0 0 0 1 4 ram4 0 0 0 0 0 0 0 0 0 0 0 1 5 ram5 0 0 0 0 0 0 0 0 0 0 0 1 6 ram6 0 0 0 0 0 0 0 0 0 0 0 1 7 ram7 0 0 0 0 0 0 0 0 0 0 0 1 8 ram8 0 0 0 0 0 0 0 0 0 0 0 1 9 ram9 0 0 0 0 0 0 0 0 0 0 0 1 10 ram10 0 0 0 0 0 0 0 0 0 0 0 1 11 ram11 0 0 0 0 0 0 0 0 0 0 0 1 12 ram12 0 0 0 0 0 0 0 0 0 0 0 1 13 ram13 0 0 0 0 0 0 0 0 0 0 0 1 14 ram14 0 0 0 0 0 0 0 0 0 0 0 1 15 ram15 0 0 0 0 0 0 0 0 0 0 0 7 0 loop0 0 0 0 0 0 0 0 0 0 0 0 7 1 loop1 0 0 0 0 0 0 0 0 0 0 0 7 2 loop2 0 0 0 0 0 0 0 0 0 0 0 7 3 loop3 0 0 0 0 0 0 0 0 0 0 0 7 4 loop4 0 0 0 0 0 0 0 0 0 0 0 7 5 loop5 0 0 0 0 0 0 0 0 0 0 0 7 6 loop6 0 0 0 0 0 0 0 0 0 0 0 7 7 loop7 0 0 0 0 0 0 0 0 0 0 0 3 0 hda 18175 31575 844130 3043760 8707 10929 156984 1625748 0 178412 4669508 3 1 hda1 838 844 0 0 3 2 hda2 3 6 0 0 3 5 hda5 340 514 0 0 3 6 hda6 48509 842286 19637 156984 22 0 hdc 22 11 216 6368 0 0 0 0 0 6292 6368 9 0 md0 0 0 0 0 0 0 0 0 0 0 0 linux:/home/joegum #
On Friday 20 January 2006 23:05, Joe G wrote:
Here's the output:
It still isn't finding your zip disk. I'm at a loss. You could try an internal zip drive; they are probably pretty cheap used at a local computer shop/ebay. Perhaps someone else here can get your machine to detect the zip drive. Once that is down, the rest is fairly trivial. Best of luck, Mark
Mark A. Taff wrote:
On Friday 20 January 2006 23:05, Joe G wrote:
Here's the output:
It still isn't finding your zip disk. I'm at a loss. You could try an internal zip drive; they are probably pretty cheap used at a local computer shop/ebay.
Perhaps someone else here can get your machine to detect the zip drive. Once that is down, the rest is fairly trivial.
Best of luck,
Mark
Thank you Mark for all your kind effort. -Joe
On 21/01/06, Joe G
Mark A. Taff wrote:
On Friday 20 January 2006 23:05, Joe G wrote:
Here's the output:
It still isn't finding your zip disk. I'm at a loss. You could try an internal zip drive; they are probably pretty cheap used at a local computer shop/ebay.
Perhaps someone else here can get your machine to detect the zip drive. Once that is down, the rest is fairly trivial.
Best of luck,
Mark
Thank you Mark for all your kind effort.
-Joe
Hi Joe. Shame I didn't see this last night... I have written a very simple HOW TO concerning the parallel port Zip drive. However this is meant for Ubuntu/Kubuntu. The good news is that it should work for SuSE 10 also. Well, it does in mine :-) First off, the standard SuSE 10 kernel will support both Zip 100 and Zip 250 drives out of the box - or from the iso if it's the open SuSE. You do not have to mess about recompiling or adding modules, they are already there. Here's how I did it all, bearing in mind that the modules file may be in a different location: Open up the /etc/modules file in your favourite text editor - I used Kate in Kubuntu - while logged in as either su or root. I've set up my system to log into root which is not default in Ubuntu/Kubuntu. for an Iomega 250 parallel drive add the line: imm for an older Iomega 100 parallel drive you will need to add the line: ppa save and close the file. You may need to enter your BIOS configuration and set the parallel port properties to SPP At this stage you need to create a mount point in order for Ubuntu/Kubuntu to know where to mount your Zip drive In a terminal (again as su or root) enter mkdir /mnt/zip100.0 (for a Zip 100 drive) or mkdir /mnt/zip250.0 (for a Zip 250 drive). Now, in your favourite text editor again, enter the following line for a Zip 100: /dev/sda4 /mnt/zip100.0 vfat noauto,user 0 0 or for a Zip 250: /dev/sda4 /mnt/zip250.0 vfat noauto,user 0 0 -- ============================================== I am only human, please forgive me if I make a mistake it is not deliberate. ============================================== Xmas may be over but, PLEASE DON'T drink and drive you'll make it to the next one that way. Kevan Farmer Linux user #373362 Cheslyn Hay Staffordshire WS6 7HR
Kevanf1 wrote:
Now, in your favourite text editor again, enter the following line for a Zip 100:
/dev/sda4 /mnt/zip100.0 vfat noauto,user 0 0
or for a Zip 250:
/dev/sda4 /mnt/zip250.0 vfat noauto,user 0 0
Hi Kevanf'l! Do I add these instructions to /etc/fstab or /mnt/zip100.0? Thank you, -Joe
On 21/01/06, Joe G
Kevanf1 wrote:
Now, in your favourite text editor again, enter the following line for a Zip 100:
/dev/sda4 /mnt/zip100.0 vfat noauto,user 0 0
or for a Zip 250:
/dev/sda4 /mnt/zip250.0 vfat noauto,user 0 0
Hi Kevanf'l!
Do I add these instructions to /etc/fstab or /mnt/zip100.0?
Thank you, -Joe
That particular line needs to be added to your fstab file. HTH -- ============================================== I am only human, please forgive me if I make a mistake it is not deliberate. ============================================== Xmas may be over but, PLEASE DON'T drink and drive you'll make it to the next one that way. Kevan Farmer Linux user #373362 Cheslyn Hay Staffordshire WS6 7HR
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Friday 2006-01-20 at 23:14 -0800, Mark A. Taff wrote:
It still isn't finding your zip disk. I'm at a loss. You could try an internal zip drive; they are probably pretty cheap used at a local computer shop/ebay.
Perhaps someone else here can get your machine to detect the zip drive. Once that is down, the rest is fairly trivial.
Does the file "/dev/sda4" exist? If not, I understand that udev should be creating on the fly, but I'm not familiar with udev yet, I'm using traditional dev files (9.3). - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFD0jZFtTMYHG2NR9URAn4FAJ0fOMBxyURl2bOG981JoDAfEC1SkACggJAq iOnuSh3IrFuPP4ELFWr2jSQ= =9Qhx -----END PGP SIGNATURE-----
On Sat, 2006-01-21 at 14:25 +0100, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Friday 2006-01-20 at 23:14 -0800, Mark A. Taff wrote:
It still isn't finding your zip disk. I'm at a loss. You could try an internal zip drive; they are probably pretty cheap used at a local computer shop/ebay.
Perhaps someone else here can get your machine to detect the zip drive. Once that is down, the rest is fairly trivial.
Does the file "/dev/sda4" exist?
If not, I understand that udev should be creating on the fly, but I'm not familiar with udev yet, I'm using traditional dev files (9.3).
udev will create the device file (on the fly) if the device is recognised. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Saturday 2006-01-21 at 08:57 -0500, Ken Schneider wrote:
Does the file "/dev/sda4" exist?
If not, I understand that udev should be creating on the fly, but I'm not familiar with udev yet, I'm using traditional dev files (9.3).
udev will create the device file (on the fly) if the device is recognised.
Based on some rules, I suppose; are they correct? According to the OP initial message, it is recognised: |> Attached scsi removable disk sda at scsi0, channel 0, id 6, lun 0 |> Attached scsi generic sg0 at scsi0, channel 0, id 6, lun 0, type 0 Perhaps the kernel log would say something. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFD0lWotTMYHG2NR9URAvRJAJ4tF3dFoYYxXUwEmKkBblxqPkPlowCfb6g7 AGiaKmZOoXm3rChNY7D7eZY= =no8C -----END PGP SIGNATURE-----
Carlos E. R. wrote:
Does the file "/dev/sda4" exist?
If not, I understand that udev should be creating on the fly, but I'm not familiar with udev yet, I'm using traditional dev files (9.3).
I used File Manager - Superuser Mode and checked the directories and sub-directories of /dev... /dev/sda4 doesn't seem to be there. I'm going to try reloading my whole system and see what happens. Maybe I messed something up. I just tried doing a search in YAST on the SuSE CD to see if there might be some package that could be loaded to provide /sda4 . It took nearly 45 minutes and it still wasn't finished. when I cancelled. All my critical data is backed up. It also seems that my pc is communicating wioth something online, even when I'm not doing anything. I hadrootkit obn here once before. I'll post again as to whether I can access my zip after the re-install. I also get weird messages when booting.... cannot find hda6....accessing hda6 -Joe -Joe
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Saturday 2006-01-21 at 10:16 -0500, Joe G wrote:
If not, I understand that udev should be creating on the fly, but I'm not familiar with udev yet, I'm using traditional dev files (9.3).
I used File Manager - Superuser Mode and checked the directories and sub-directories of /dev... /dev/sda4 doesn't seem to be there.
That's bad. It will not work till it appears.
I'm going to try reloading my whole system and see what happens. Maybe I messed something up. I just tried doing a search in YAST on the SuSE CD to see if there might be some package that could be loaded to provide /sda4 . It took nearly 45 minutes and it still wasn't finished. when I cancelled.
The program "pin filenametofind" will find you anything from the DVD, installed or not, in seconds.
All my critical data is backed up. It also seems that my pc is communicating wioth something online, even when I'm not doing anything.
Can't comment on that, little info.
I hadrootkit obn here once before. I'll post again as to whether I can access my zip after the re-install. I also get weird messages when booting.... cannot find hda6....accessing hda6
- -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFD0lTitTMYHG2NR9URAkKsAKCZFsnW+jilQLxGiqjDHPbkCV5vuACcDKmu VOtYfUr4ezbyO69EHFMyDog= =9PiH -----END PGP SIGNATURE-----
On Friday 20 January 2006 20:00, Joe G wrote:
I tried the following and permission keeps getting denied:
joegum@linux:~> su Password: linux:/home/joegum # /etc/fstab bash: /etc/fstab: Permission Denied linux:/home/joegum # cd /usr/src/linux linux :/etc/fstab: Permission Denied linux:/usr/src/linux #
I also tried browsing with File Manager - Superuser Mode
No luck.
-Joe
Sorry, `cat /etc/fstab` works well. Mark
participants (5)
-
Carlos E. R. -
Joe G -
Ken Schneider -
Kevanf1 -
Mark A. Taff