Previously, Joel Hammer chose to write: > I am puzzled that your are talking about /dev/hdc4 /mnt/floppy when you > are saying that your network card is not working. >
Well, to attempt to clarify: The network card works when I boot the normall kernel that I use day-to-day, but the ZIP won't. The example mount command I referenced was with that kernel. I can mount the ZIP just fine with the alternate kernel, but the network card gets lost. > As I recall, the trick with the IOMega zip drive was to configure printer > support as a module (lp), since that has to be loaded after the modules > for the zip drive. > This would make sense for a parallel port ZIP, I can't see where printer support as a module would affect communications with an IDE device. (of course, I don't know why my network card won't work when I boot with the kernel from which I CAN access my ZIP drive). > That was the only trick as far at the kernel, I believe. I don't see > how that will interfere with your floppy drive or your network card. > Me either. > The CONFIG_DEV_IDEFLOPPY is not required for floppies. Maybe unset that and > your floppy will work. > No, it's not required for access to std floppies, but it can be used to access an IDE ZIP (at least according to the help text associated with it). That why I compiled it into the one kernel version I've tried. And that's the kernel that works. Don't be confused by my attempting to mount the device onto /mnt/floppy. I'm trying to troubleshoot an IDE ZIP drive. Trying to mount it on /mnt/floppy had no more significance than any oher mount point I would've tried. I'm gonna test appending the line "hdc=ide-floppy" to my kernel line for my normal kernel and see if that changes anything. I believe that would be equivalent to CONFIG_DEV_IDEFLOPPY=y when compiling a kernel. Thanks, Tim _______________________________________________ Linux-users mailing list Archives, Digests, etc at http://linux.nf/mailman/listinfo/linux-users
