Very Computer

I have a HP 7200e Parallel-port CD-writer and a Linux SuSE 6.2 kernel
2.2.10 System. Before i upgradet my system from 6.1 (kernel 2.2.7)
everything was working fine. Since the upgrate, the modules won't load
any more !!
I could load all the modules which were needet ,mount the cd-writer and
read/write to it.
The writer is Supportet and actually everything has been done as these
URL-HOWTO-Sites inform:
http://www.guug.de/~winni/linux/cdr/html/CD-Writing.html
http://www.torque.net/parport/paride.html

I use this Kernel Konfigurations:
BLOCK  Loopback device                          loop    M
PARIDE CONFIG_PARIDE(Parallel-port support)     paride  Y
PARIDE CONFIG_PARIDE_PCD(for CD-R)              pcd     M
PARIDE CONFIG_PARIDE_PG(for CD-W)               pg      M
PARIDE CONFIG_PARIDE_EPAT(Lowlevel Driver)      epat    M

FS     ISO 9660 CDROM filesystem   iso9660     Y
FS     Microsoft Joliet cdrom...   joliet      Y

(My actions analytical):
412-marinos:/ # cat /proc/modules
412-marinos:/ # modprobe epat
412-marinos:/ # cat /proc/modules
epat                    5840   0 (unused)
paride                  3116   1 [epat]
parport                 6476   0 [paride]
412-marinos:/ # modprobe pcd
/lib/modules/2.2.10/misc/pcd.o: init_module: Device or resource busy
/lib/modules/2.2.10/misc/pcd.o: insmod /lib/modules/2.2.10/misc/pcd.o
failed
/lib/modules/2.2.10/misc/pcd.o: insmod pcd failed
412-marinos:/ # modprobe pg
/lib/modules/2.2.10/misc/pg.o: init_module: Device or resource busy
/lib/modules/2.2.10/misc/pg.o: insmod /lib/modules/2.2.10/misc/pg.o
failed
/lib/modules/2.2.10/misc/pg.o: insmod pg failed
412-marinos:/ # modprobe loop
412-marinos:/ # cat /proc/modules
loop                    7264   0 (unused)
parport_probe           2916   0 (autoclean) (unused)
epat                    5840   0
paride                  3116   1 [epat]
parport                 6476   0 [parport_probe paride]
412-marinos:/ #

One thing i thing that might be reason may be thep paride.o module
should not be loaded before the pcd.o module. It seems that the the
paride module and the paraport.o modules are loaded automaticly when the
epat.o module is loaded.
If this is the reason i dont't know how to prevent that and if not is
there something else what i should look at ??

I would appreciate any hind's or solution's you have !!  

Thank you,
Marinos Shanios

This is the script I used to load/unload the modules
------------------- modprobe.cd --------------------
#!/bin/bash
case "$1" in
mod)
        modprobe epat
        modprobe pcd  
        modprobe paride      
        modprobe pg  
        modprobe loop
        ;;
umod)
        rmmod loop
        rmmod pg
        rmmod pcd
        rmmod epat
        rmmod paride
        ;;
*)
        echo "Usage: $0 [{mod|umod}]"
esac
cat /proc/modules
-----------------------------------------------------

The solution has been found !! The reason was the Order of callings !!
Modprobe has checks for any other needed modules and loads them
automaticly!
So if we did modprobe epad instead of insmod epad we would get with
automaticly epat,paride,parport loaded.
There is nothing wrong with the paride module,but there is one with the
parport modul. The pcd module should be loaded before the paraport
module.

Many thanks again !!

Marinos Shanios

The modified Script (now working)
---------modprobe.cd----------------
#!/bin/bash
case "$1" in
mod)    
        insmod paride
        insmod epat
        insmod pcd
        insmod pg
        insmod loop
        ;;
umod)
        rmmod loop
        rmmod pg
        rmmod pcd
        rmmod epat
        rmmod paride
        ;;
*)
        echo "Usage: $0 [{mod|umod}]"
esac
cat /proc/modules
-----------------------------------------------