Re: Loadable kernel modules not unloadable

["hillbilly" <bennitech@bluep.com.au>]

Just a further note to Adam Porter in addition to my response on the
why and wherefore above, I discovered that the wierd behaviour with not
being able to access the status port appears to be specific to the
combination of Debian Sarge with the particular PC I was using.  The
difficulty does not appear on other machines with Sarge loaded and
running and funnier still, it's not failed hardware because when I
prevent parport from loading at all, my custom module works just fine!
Hmmm, very odd indeed!  Maybe a quirky peripheral chip not in common
use.  Anyway, /etc/modprobe.conf/local seems to be a good solution.

Cheers to all.

;-]