I am trying to configure a dual parallel port after installation of SuSE 8.2. I am following instructions from the chip maker (MosNet). The important part is using insmod to modify the parport. But when I try to run "insmod parport.o" at root directory in bash I get the message "no such file or directory." I used the -v switch and it told me it was using parport.o. I then did the next command (something like "insmod parport_pc.o io... -v") command and it said "using parport_pc.o" and then "no such file or directory" Where can I get info on insmod? Any help would be greatly appreciated.
mark bannister wrote:
I am trying to configure a dual parallel port after installation of SuSE 8.2. I am following instructions from the chip maker (MosNet). The important part is using insmod to modify the parport. But when I try to run "insmod parport.o" at root directory in bash I get the message "no such file or directory." I used the -v switch and it told me it was using parport.o. I then did the next command (something like "insmod parport_pc.o io... -v") command and it said "using parport_pc.o" and then "no such file or directory"
Try first a "depmod -a". If this doesn't work, try to use the full path to the module after insmod. # insmod -v /lib/modules/2.xxxx/.../parport.o
Where can I get info on insmod?
# man insmod
Any help would be greatly appreciated.
-- Andreas
<snip>
Try first a "depmod -a". If this doesn't work, try to use the full path to the module after insmod.
# insmod -v /lib/modules/2.xxxx/.../parport.o
Thanks -a doesn't seem to be a valid option. I tried the full path. It gave me an error. I think it told me that it was in using it. I did look over the man pages, but wasn't able to get much out of them.
Where can I get info on insmod?
# man insmod
Any help would be greatly appreciated.
-- Thanks Mark B.
mark bannister wrote:
<snip>
Try first a "depmod -a". If this doesn't work, try to use the full path to the module after insmod.
# insmod -v /lib/modules/2.xxxx/.../parport.o
Thanks -a doesn't seem to be a valid option.
# depmod -a ???
I tried the full path. It gave me an error. I think it told me that it was in using it. I did look over the man pages, but wasn't able to get much out of them.
The error? -- Andreas
Andreas Winkelmann wrote:
mark bannister wrote:
<snip>
Try first a "depmod -a". If this doesn't work, try to use the full path to the module after insmod.
# insmod -v /lib/modules/2.xxxx/.../parport.o
Thanks -a doesn't seem to be a valid option.
# depmod -a
???
<snip> Err...ok I can't read.. OK, did depmod -a then insmod with full path to parport.o and -v. It returned : Symbol version prefix '' Insmod: a module named parport already exists
mark bannister wrote:
Try first a "depmod -a". If this doesn't work, try to use the full path to the module after insmod.
# insmod -v /lib/modules/2.xxxx/.../parport.o
Thanks -a doesn't seem to be a valid option.
# depmod -a
???
<snip> Err...ok I can't read.. OK, did depmod -a then insmod with full path to parport.o and -v. It returned : Symbol version prefix '' Insmod: a module named parport already exists
Look with # lsmod if it is already loaded. Maybe it is the old Module, You can unload Modules with rmmod # rmmod module -- Andreas
Andreas Winkelmann wrote:
mark bannister wrote: <snip> Look with
# lsmod
if it is already loaded. Maybe it is the old Module, You can unload Modules with rmmod
# rmmod module
Thanks, now I see progress <g> Parport and parport_pc are in use, each three times. rmmod parport reports "device or resource is busy." I assume I need to start shutting things down but I'm not sure of the best way to do that.
mark bannister wrote:
mark bannister wrote: <snip> Look with
# lsmod
if it is already loaded. Maybe it is the old Module, You can unload Modules with rmmod
# rmmod module
Thanks, now I see progress <g> Parport and parport_pc are in use, each three times. rmmod parport reports "device or resource is busy." I assume I need to start shutting things down but I'm not sure of the best way to do that.
With lsmod you see a column which says by which module this one is used, maybe parport is used by parport_pc. So you have to "rmmod parport_pc" before "rmmod parport". -- Andreas
<snip> Thanks so much! I did need to rmmod in the correct order. I also had to use the full path to parport and parport_pc I still could not get it working until I called Netmos directly and talk to a real human who knew linux. I was leaving off the IRQ's as instructed by the SuSE documents, but this card requires them. So the steps to install were: rmmod lp rmmod parport_pc rmmod parport lspci -vv ;gives a listing of all pci devices #use the first and third address (they are paired) and the IRQ given #modify the modules.conf parport section insmod /path/to/parport/parport.o insmod /path/to/parport/parport_pc.o io=0x378,0xeff0,0xefa8 irq=7,11,11 modprobe /path/to/parport/parport modprobe /path/to/parport/parport_pc modprobe lp #check status with lpstat -t
participants (2)
-
Andreas Winkelmann -
mark bannister