[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
ZIP drive problems with kernel.
Hi.
I just compiled my 2.2.7 kernel, and I'm having problems using my zip
drive.
The last kernel i compiled before it had the problem too,
and before that i used the generic RedHat kernel (which had no problem).
I have read the howtos and selected scsi and parport inside the kernel
(I selected them as modules before and the howto recommended for using
them not as modules)
When I boot to the old generic kernel i don't have the problem.
I need to compile the zip driver (ppa) as module, since i dont want it
connected all the time, and i do want to be able to use a printer.
It seems that the problem is somehow connected to the parport,
and thought about testing my printer with it to see if it works,
but unfortunatly my printer is broken beyond repair.
(so it woudnt respond anyway)
This is the output of insmod ppa:
/lib/modules/2.2.7/scsi/ppa.o: unresolved symbol
parport_unregister_device
/lib/modules/2.2.7/scsi/ppa.o: unresolved symbol parport_enumerate
/lib/modules/2.2.7/scsi/ppa.o: unresolved symbol parport_register_device
/lib/modules/2.2.7/scsi/ppa.o: unresolved symbol parport_claim
/lib/modules/2.2.7/scsi/ppa.o: unresolved symbol parport_release
This is the output of modprobe ppa:
/lib/modules/2.2.7/scsi/ppa.o: init_module: Device or resource busy
(when parport was a module it stated that no device could be found on
parallel port or something similar. though it was connected, and the old
kernel could use it)
Also, if that's any help, I don't use kerneld, I use kmod instead.
Is there anything i forgot to compile?
Thanks,
Yoni.
--
The day Microsoft makes something that doesn't suck,
is probably the day they start making vacuum cleaners...