Kooka or Xsane won't run

[Mike Reinehr]

On Thursday 05 October 2006 15:32, Harry G wrote:
> On Thursday 05 October 2006 1:24 pm, Mike Reinehr wrote:
> > On Thursday 05 October 2006 11:57, Harry G wrote:
> > > On Wednesday 04 October 2006 4:43 pm, Net Llama! wrote:
> > > > On Wed, 4 Oct 2006, Harry G wrote:
> > > > > When run from a terminal, I get the error:
> > > > > insmod: can't
> > > > > read
> > > > > '/lib/modules/2.6.15-26-386/kernel/drivers/mfpportctrl/mfpport.ko':
> > > > > No such file or directory
> > > > >
> > > > > Did I muck up the kernel somehow?
> > > >
> > > > Looks that way.  Does the mfpport modules exist?
> > >
> > > No the file doesn't exit.
> > >
> > >   But if I try to run either as root (yes, I know you should not run
> > > Xsane as root) both work fine.
> > >
> > > Weird, huh?
> > >
> > > Harry G
> >
> > Harry,
> >
> > This sounds like a plain, old permissions problem. I think the mfpport
> > module message is a red herring. I use xsane regularly & I don't have any
> > such module.
> >
> > Have you checked the permissions & group ownership of the device node of
> > your scanner?
> >
> > cmr
>
> How would I determine which node it is using?
>
> Harry G

That would depend upon what type of interface you're using. Here, I'm using a 
SCSI interface and the device nodes are: 
	$ ls -l scanner sg1
	lrwxrwxrwx 1 root root        8 Aug 30  2003 scanner -> /dev/sg1
	crw-rw---- 1 root scanner 21, 1 Mar 14  2002 sg1
Note that the group owner is "scanner", and any users (me!) who wish to use 
the scanner must be a member of that group.

Your device nodes would be different if you are using USB or a parallel port, 
but the permissions & group memberships sould be similar. You could start by 
reviewing your dmesg output at boot, look at the output of `lsusb` and/or 
check /proc/bus. (I'm not sure where a parallel port would show up.)

HTH!

cmr

-- 
Debian 'Etch': Registered Linux User #241964

"More laws, less justice." -- Marcus Tullius Ciceroca, 42 BC