Yeah, I tried the mini-HOWTO for the zip drive a couple of months ago when I was
trying to get my parallel port zip going, and I found that the mini-HOWTO is
OUTDATED.  I spent several days trying to do exactly what it said, trying to
recompile the kernel, reinstalling the whole system (mdk 6.1)...over and over
and over.

Then the tip came from this forum that it's no longer 'insmod' but now
'modprobe'.
Then the tip came, just do 'modprobe ppa', stick in a disk and mount it, so I
tried it and it worked!
All that time, all that frustration, and it could have been so simple!

The problem these guys all seem to be writing about appears TO ME to have more
to do with Mdk 7 than anything else. A bug? Another change of some sort? Who
knows?  Seems like Jon demonstrated this by getting his old zip out and trying
it with mdk7 -- works for him under the older versions, but not under 7 ... hmmm
... what's the difference between the earlier versions and mdk7?  This seems to
be the question.

So, anyone out there have the answer? Anyone have a parallel port zip running
w/mdk7? If you do, seems like there's a lot of people needing your help!
Lance

Bruce Hilliker wrote:
> 
> Jon wrote:
> 
> > Mani Abreu wrote:
> >
> > > Nope. Just tried that, here's the result:
> > >     mount: the kernel does not recognize /dev/sda4 as a block device
> > >         (maybe 'insmod driver'?)
> > >
> > > I read that the problem may be that the kernel is loading the drivers for
> > > the line printer first, before parport/ppa driver. How do I change the
> > > order around?
> > >
> > > Mani
> > >
> > >     forstfed wrote:
> > >
> > > > On Sun, 02 Apr 2000, you wrote:
> > > >
> > > > Well, try just doing the mount now.  See if that does anything.
> > > >
> > > > > Well, I tried that. Here's what I got after typing "insmod ppa":
> > > > >     /lib/modules/2.2.14-15mdk/scsi/ppa.o: init_module: Device or resource
> > > > busy
> > > > >
> > > > > Any ideas? I really want to get this thing resolved.....
> > > > >
> > > > > Mani
> > > > >
> > > > >
> > > > > forstfed wrote:
> > > > >
> > > > > > On Fri, 31 Mar 2000, you wrote:
> > > > > >
> > > > > > This is what worked for me:
> > > > > >
> > > > > > As su in a terminal window:
> > > > > >
> > > > > > mkdir /mnt/zip
> > > > > >
> > > > > > insmod parport
> > > > > >
> > > > > > insmod ppa
> > > > > >
> > > > > > mount -t msdos /dev/sda4 /mnt/zip
> > > > > >
> > > > > > make sure there is a disk in.  You have to umount -t msdos /dev/sda4
> > > > /mnt/zip
> > > > > > to eject the disk, then  mount -t msdos /dev/sda4 /mnt/zip again when you
> > > > > > insert another disk.
> > > > > >
> > > > > > Ed
> >
> > Geez, You guys made me dig my old zip drive out of the closet to test this problem
> > and you know, it didn't work either.  Tried it on a RedHat 6.1 and a Mandrake
> > 7.0-2 machine.  Hardware works as I made a DOS boot disk with guest.exe on it.
> > Worked fine with Redhat 5.2 and Slackware 3.6 some time ago with the commands
> > listed above.  I also looked at modules loaded and tried it without any modules
> > and in init 1 hand loading modules.  Since the kernel for Mandrake 7.0 came from
> > Redhat 6.1 (Recompiled) I wonder if perhaps lp (or another parallel port using
> > service)  support was built into the kernel instead of as a mod.
> >
> > Question!  Does anyone out there have a parallel port ZIP working on Mandrake
> > 7.0-2 or RedHat 6.1?  If so, can you please tell us how you did it?  Give out with
> > the port setting in the BIOS, Kernel you used and anything else you think might
> > help.  I am going to try recompiling a kernel to see if I can get it working.
> 
> I don't really know if this will help; but check out the attached "text" file.  I
> come from
> the Linux Gazette.
> 
> Bruce :-)
> 
>   --------------------------------------------------------------------------------
>   Zip Drive Mini-HOWTO
>   Kyle Dansie,   [EMAIL PROTECTED]
>   v2.4, 10 January 1999
> 
>   This Document provides a quick reference quide on setting up and using
>   the Iomega ZIP drive with Linux.
>   ______________________________________________________________________
> ...[snip]...


Reply via email to