| View previous topic :: View next topic |
| Author |
Message |
ColdPack
n00b
Joined: 19 Jun 2002
Posts: 60
Location: Madison, WI
|
 Posted: Fri Jul 05, 2002 5:19 pm Post subject: Added question about mounting... ZIP |
 |
|
I have a SCSI zip drive. I can mount it without any problems provided a zip disk was in the drive when I booted up.
I cannot put a disk in the drive after Gentoo is already up and running and mount it. It says "special device sda4 does not exist".
I don't have this problem in Debian or Slackware and I use the same kernel config between them. Is there something happening in the boot-up process that causes this? I figured if it sees the scsi card and shows that an IOMEGA disk drive is attached, it would be assigned as /dev/sda4... but not at the moment. Only if a zip disk is in there at bootup.
Any zippy ideas?
Thanks!
CP |
|
| Back to top |
|
 |
delta407
Bodhisattva
Joined: 23 Apr 2002
Posts: 2876
Location: Chicago, IL
|
| Posted: Fri Jul 05, 2002 5:26 pm Post subject: |
|
|
Moved this post from this thread into its own because it is a completely separate issue.
_________________
I don't believe in witty sigs. |
|
| Back to top |
|
|
kaplan
n00b
Joined: 05 Jul 2002
Posts: 12
Location: Canada
|
| Posted: Fri Jul 05, 2002 9:15 pm Post subject: |
|
|
I had the same problem with an ATAPI zip drive. My work around was, when compiling the kernel, to compile ide-floppy as a module. Hence whenever I need to use the zip drive I do the following (with a zip-disk in the drive of course):
| Code: |
$ su -
$ modprobe ide-floppy
$ exit
$ mount /mnt/zip
|
Anyways, this is just a work around and not a solution. I think the problem has something to do with devfs. Anyone familiar with devfs configuration?
hope this helps.
Sam |
|
| Back to top |
|
|
delta407
Bodhisattva
Joined: 23 Apr 2002
Posts: 2876
Location: Chicago, IL
|
| Posted: Sat Jul 06, 2002 12:33 am Post subject: |
|
|
| kaplan wrote: | | I think the problem has something to do with devfs. |
Bingo; way back in the day (a few weeks ago) I had this post.
_________________
I don't believe in witty sigs. |
|
| Back to top |
|
|
wilbertnl
Tux's lil' helper
Joined: 01 Jul 2002
Posts: 89
Location: Tulsa, OK, USA
|
| Posted: Sun Jul 28, 2002 3:19 am Post subject: Iomega and devfs |
|
|
The debian/slackware way to solve this problem is disabling devfs with "gentoo=nodevfs" as kernel parameter. But the following solution works for me too:
I added the following lines in /etc/devfs.conf
# Create /dev/hde
LOOKUP ^hde$ CFUNCTION GLOBAL mksymlink ide/host2/bus0/target0/lun0/disc hde
REGISTER ^ide/host2/bus0/target0/lun0/disc$ CFUNCTION GLOBAL mksymlink $devname hde
UNREGISTER ^ide/host2/bus0/target0/lun0/disc$ CFUNCTION GLOBAL unlink $devname hde
# Create /dev/hde1
LOOKUP ^hde1$ CFUNCTION GLOBAL mksymlink ide/host2/bus0/target0/lun0/part1 hde1
REGISTER ^ide/host2/bus0/target0/lun0/part1$ CFUNCTION GLOBAL mksymlink $devname hde1
UNREGISTER ^ide/host2/bus0/target0/lun0/part1$ CFUNCTION GLOBAL unlink $devname hde1
# Create /dev/hde4
LOOKUP ^hde4$ CFUNCTION GLOBAL mksymlink ide/host2/bus0/target0/lun0/part4 hde4
REGISTER ^ide/host2/bus0/target0/lun0/part4$ CFUNCTION GLOBAL mksymlink $devname hde4
UNREGISTER ^ide/host2/bus0/target0/lun0/part4$ CFUNCTION GLOBAL unlink $devname hde4
I have an additional Promise Ultra66 pci-card, that explains host2.
Now I can use devfs AND my Iomega zip drive without any trick!
You need to find your own host and lun, but I guess that you will figure that. For me there was no need to do anything else than these lines in /etc/devfs.
My kernels are 2.4.19-rc3/gentoo-r7
_________________
Wilbert van Bakel
Strive for excellence, not perfection |
|
| Back to top |
|
|
|
Other Things Gentoo
