Parallel port Zip drive problem after 7.3/kernel/2.4.18-20030812 update
All, I applied the 7.3/kernel/2.4.18-20030812 update (and everything else) to my 7.3 systems and I noticed on the one with a parallel port Zip drive that it no longer works. I assumed it was a parallel port card problem but it isn't, since I've replaced the card and there was no change. This is the error I get: $ mount /media/zip /dev/sda4: Invalid argument mount: I could not determine the filesystem type, and none was specified The fstab entry looks like: /dev/sda4 /media/zip auto noauto,user,exec 0 0 Specifying the fstype doesn't seem to help. It accesses the drive, and the drive is ejectable via software. Since there isn't a newer kernel RPM for download, is there something else I can do to get this to work again. It's a major pain not having the Zip drive available. Thanks. Tom. ------------------------------------------------------------------------------- Tom Maszerowski - tommasz@frontiernet.net -------------------------------------------------------------------------------
The Wednesday 2003-11-26 at 17:33 -0500, Tom Maszerowski wrote:
This is the error I get:
$ mount /media/zip /dev/sda4: Invalid argument mount: I could not determine the filesystem type, and none was specified
No sda, I think. Try "modprobe imm". -- Cheers, Carlos Robinson
Here's what I got:
# modprobe imm
/lib/modules/2.4.18-4GB/kernel/drivers/scsi/imm.o: init_module: No such device
Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters
/lib/modules/2.4.18-4GB/kernel/drivers/scsi/imm.o: insmod /lib/modules/2.4.18-4GB/kernel/drivers/scsi/imm.o failed
/lib/modules/2.4.18-4GB/kernel/drivers/scsi/imm.o: insmod imm failed
How do I update imm.o?
Tom.
On Thu, 27 Nov 2003 00:07:05 +0100 (CET)
"Carlos E. R."
The Wednesday 2003-11-26 at 17:33 -0500, Tom Maszerowski wrote:
This is the error I get:
$ mount /media/zip /dev/sda4: Invalid argument mount: I could not determine the filesystem type, and none was specified
No sda, I think. Try "modprobe imm".
-- Cheers, Carlos Robinson
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
------------------------------------------------------------------------------- Tom Maszerowski - http://www.frontiernet.net/~tommasz Geek - Exploring alternative OS's since 1985! Guitar Player - Heritage H575 and '37(ish) Epiphone Triumph BMW Rider - 1987 BMW K75s (gone), President IBMWR, LPR #44, DoD #1957 -------------------------------------------------------------------------------
The Wednesday 2003-11-26 at 21:49 -0500, Tom Maszerowski wrote:
# modprobe imm /lib/modules/2.4.18-4GB/kernel/drivers/scsi/imm.o: init_module: No such device Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters /lib/modules/2.4.18-4GB/kernel/drivers/scsi/imm.o: insmod /lib/modules/2.4.18-4GB/kernel/drivers/scsi/imm.o failed /lib/modules/2.4.18-4GB/kernel/drivers/scsi/imm.o: insmod imm failed
You will get that exact message if the drive is not properly connected: I have just tried (SuSE 8.2) and got that message with the unit disconnected.
How do I update imm.o?
You should make sure the hardware is really working, maybe trying another OS. It should have been updated with the kernel. I can only suggest going in to the kernel config and check and recompile. Otherwise, report to SuSE feedback (web page) - but only after making sure there is no hardware problem. I have a SuSE 7.3 nearby, but I don't know if the kernel was updated or not. I might try my ZIP there, but I can't assure you when I will try. -- Cheers, Carlos Robinson
participants (2)
-
Carlos E. R. -
Tom Maszerowski