On Mon 16 Aug 2021 at 19:55:49 +0100, Brian wrote:
> On Mon 16 Aug 2021 at 19:51:50 +0200, Nicolas George wrote:
>
> > Brian (12021-08-02):
> > > My thinking is that a USB printer uses libusb, just as a scanner does.
> > > No kernel driver involved. The printer drivers are "internal" to CUPS.
> >
On Mon 16 Aug 2021 at 19:51:50 +0200, Nicolas George wrote:
> Brian (12021-08-02):
> > My thinking is that a USB printer uses libusb, just as a scanner does.
> > No kernel driver involved. The printer drivers are "internal" to CUPS.
>
> The output of `/sbin/modinfo usblp` confirms there is a kern
Brian (12021-08-02):
> My thinking is that a USB printer uses libusb, just as a scanner does.
> No kernel driver involved. The printer drivers are "internal" to CUPS.
The output of `/sbin/modinfo usblp` confirms there is a kernel driver
for USB printers.
filename: /lib/modules/5.10.0-8-amd6
On Mon 02 Aug 2021 at 17:35:46 +0200, Nicolas George wrote:
> Brian (12021-08-02):
> > Helpful remarks, but I did not think printers used kernel drivers.
>
> AFAIR, USB printers appear as a special device, unlike generic USB
> devices, that makes one layer of drivers, but then you need an userlan
Brian (12021-08-02):
> Helpful remarks, but I did not think printers used kernel drivers.
AFAIR, USB printers appear as a special device, unlike generic USB
devices, that makes one layer of drivers, but then you need an userland
driver, probably GhostScript, to talk the proper language to that
dev
On Mon 02 Aug 2021 at 10:36:22 +0200, Nicolas George wrote:
> Thomas Schmitt (12021-08-02):
> > Do you have any sg device left as suspect for the scanner's device file,
> > after you subtracted one for each hard disk and each optical drive ?
> > (I.e. are there two hard disks to occupy sg0 and sg1
On Mon 02 Aug 2021 at 13:21:22 +0200, Thomas Schmitt wrote:
> Hi,
>
> Brian wrote:
> > Isn't /dev/sg0 the block device?
>
> /dev/sgX are character devices.
>
> https://tldp.org/HOWTO/SCSI-Generic-HOWTO/intro.html
> says
> "The driver's purpose is to allow SCSI commands to be sent directly t
Hi,
Brian wrote:
> Isn't /dev/sg0 the block device?
/dev/sgX are character devices.
https://tldp.org/HOWTO/SCSI-Generic-HOWTO/intro.html
says
"The driver's purpose is to allow SCSI commands to be sent directly to
SCSI devices. [...] Various specialized applications for writing
CD-Rs an
On Mon 02 Aug 2021 at 09:55:17 +0200, Thomas Schmitt wrote:
> Hi,
>
> i wrote:
> > > /dev/sg2 might be the generic SCSI device to which /dev/sr0 is connected.
>
> mick crane wrote:
> > Drive type : vendor 'PLDS' product 'DVD+-RW DS-8A9SH' revision 'ED11'
>
> So it's clearly the DVD burner whi
Thomas Schmitt (12021-08-02):
> Do you have any sg device left as suspect for the scanner's device file,
> after you subtracted one for each hard disk and each optical drive ?
> (I.e. are there two hard disks to occupy sg0 and sg1 and no other sgX left ?)
Have SCSI scanners been spotted since the
On 2021-08-02 08:55, Thomas Schmitt wrote:
Hi,
i wrote:
> /dev/sg2 might be the generic SCSI device to which /dev/sr0 is connected.
mick crane wrote:
Drive type : vendor 'PLDS' product 'DVD+-RW DS-8A9SH' revision
'ED11'
So it's clearly the DVD burner which is at sg2.
Do you have any sg
Hi,
i wrote:
> > /dev/sg2 might be the generic SCSI device to which /dev/sr0 is connected.
mick crane wrote:
> Drive type : vendor 'PLDS' product 'DVD+-RW DS-8A9SH' revision 'ED11'
So it's clearly the DVD burner which is at sg2.
Do you have any sg device left as suspect for the scanner's devi
On 2021-07-31 12:11, Thomas Schmitt wrote:
Hi,
mick crane wrote:
looking at those informative pages I think /dev/sg2 is the scanner
should that not be in group scanner ?
lrwxrwxrwx 1 root root 3 Jul 30 17:36 cdrom -> sr0
crw-rw+ 1 root cdrom21, 2 Jul 30 17:36 sg2
brw-rw
Greg Wooledge wrote:
> On Sun, Aug 01, 2021 at 10:41:13AM -0400, songbird wrote:
> > mick crane wrote:
> > > Doh! discovered have to restart scanbd.service after changing config
> > > file.
> > > You'd have thought I would know that.
> >
> > some will restart automatically when their config fi
On Sun, Aug 01, 2021 at 10:41:13AM -0400, songbird wrote:
> mick crane wrote:
> > Doh! discovered have to restart scanbd.service after changing config
> > file.
> > You'd have thought I would know that.
>
> some will restart automatically when their config file changes
> and others don't. you
mick crane wrote:
> On 2021-07-31 17:40, Brian wrote:
><...>
> Doh! discovered have to restart scanbd.service after changing config
> file.
> You'd have thought I would know that.
> changing group to scanner of directory want to save to seems to have
> fixed permission issue.
> mick
some will
On 2021-07-31 17:40, Brian wrote:
<...>
Doh! discovered have to restart scanbd.service after changing config
file.
You'd have thought I would know that.
changing group to scanner of directory want to save to seems to have
fixed permission issue.
mick
--
Key ID4BFEBB31
On Sat 31 Jul 2021 at 17:17:29 +0100, mick crane wrote:
> On 2021-07-31 16:32, Brian wrote:
>
> > grep scanner /etc/groups
> > cat /etc/default/saned
> >
> I keep thinking it should be groups and not group as well.
An embarassing typo :).
> me and saned are in scanner group
> /etc/default/
On Sat 31 Jul 2021 at 16:57:53 +0100, mick crane wrote:
> On 2021-07-31 14:37, mick crane wrote:
> when I say Xsane works fine.
> All I've deleted as far as I know are the .conf files for scanners I don't
> have.
>
> In /etc/sane.d/dll.conf
> I removed all scanner names except
> net
> fujitsu
> #
On 2021-07-31 16:32, Brian wrote:
grep scanner /etc/groups
cat /etc/default/saned
I keep thinking it should be groups and not group as well.
me and saned are in scanner group
/etc/default/saned
RUN_AS_USER=saned
How to find which is the scanner in /dev if it is supposed to be
there?
Xsa
On 2021-07-31 14:37, mick crane wrote:
when I say Xsane works fine.
All I've deleted as far as I know are the .conf files for scanners I
don't have.
In /etc/sane.d/dll.conf
I removed all scanner names except
net
fujitsu
#escl
running Xsane I get to select
fujitsu or net:localhost.. both of whi
On Sat 31 Jul 2021 at 14:37:49 +0100, mick crane wrote:
> On 2021-07-31 13:18, Brian wrote:
> > On Sat 31 Jul 2021 at 10:20:43 +0100, mick crane wrote:
> >
> > > On 2021-07-30 18:30, Brian wrote:
> > > <...>
> > > > https://wiki.debian.org/SaneOverNetwork#escl
> > > looking at those informative
On 2021-07-31 13:18, Brian wrote:
On Sat 31 Jul 2021 at 10:20:43 +0100, mick crane wrote:
On 2021-07-30 18:30, Brian wrote:
<...>
> https://wiki.debian.org/SaneOverNetwork#escl
looking at those informative pages I think /dev/sg2 is the scanner
should that not be in group scanner ?
root@pumpk
On Sat 31 Jul 2021 at 10:20:43 +0100, mick crane wrote:
> On 2021-07-30 18:30, Brian wrote:
> <...>
> > https://wiki.debian.org/SaneOverNetwork#escl
> looking at those informative pages I think /dev/sg2 is the scanner
> should that not be in group scanner ?
>
> root@pumpkin:/# ls -l /dev |grep
Hi,
mick crane wrote:
> looking at those informative pages I think /dev/sg2 is the scanner
> should that not be in group scanner ?
> lrwxrwxrwx 1 root root 3 Jul 30 17:36 cdrom -> sr0
> crw-rw+ 1 root cdrom21, 2 Jul 30 17:36 sg2
> brw-rw+ 1 root cdrom11, 0 Jul 30 17:
On 2021-07-30 18:30, Brian wrote:
<...>
https://wiki.debian.org/SaneOverNetwork#escl
looking at those informative pages I think /dev/sg2 is the scanner
should that not be in group scanner ?
root@pumpkin:/# ls -l /dev |grep cdrom
lrwxrwxrwx 1 root root 3 Jul 30 17:36 cdrom -> sr0
cr
On 2021-07-30 18:30, Brian wrote:
I like things to work but I'm quite capable of breaking things on my
own.
A sound principal for anyone to take note of.
=O)
--
Key ID4BFEBB31
On Fri 30 Jul 2021 at 17:47:50 +0100, mick crane wrote:
> On 2021-07-30 15:36, to...@tuxteam.de wrote:
> > On Fri, Jul 30, 2021 at 03:21:47PM +0100, mick crane wrote:
> > > >>> > Can I assume there is something else binding to the scanner address
> > > >>> > ?
> >
> > [...]
> >
> > > >>it's ine
On 2021-07-30 15:36, to...@tuxteam.de wrote:
On Fri, Jul 30, 2021 at 03:21:47PM +0100, mick crane wrote:
>>> > Can I assume there is something else binding to the scanner address ?
[...]
>>it's inetd
>>tcp0 0 0.0.0.0:sane-port 0.0.0.0:*
>>LISTEN
>>869/inetd
[...]
The o
On Fri, Jul 30, 2021 at 03:21:47PM +0100, mick crane wrote:
> >>> > Can I assume there is something else binding to the scanner address ?
[...]
> >>it's inetd
> >>tcp0 0 0.0.0.0:sane-port 0.0.0.0:*
> >>LISTEN
> >>869/inetd
[...]
> The only thing not commented out is
> sane-po
On 2021-07-30 12:45, Greg Wooledge wrote:
On Fri, Jul 30, 2021 at 12:37:40PM +0100, mick crane wrote:
On 2021-07-30 11:59, Dan Ritter wrote:
> mick crane wrote:
> > Can I assume there is something else binding to the scanner address ?
> > How to find out what that might be ?
>
>
> sudo netstat -
>
> > $ sudo ss -l4pon | grep [port]
>
> That grep command is wrong in a couple ways.
>
> First, the unquoted [port] is a live glob pattern for the shell.
I meant port number here, i.e.:
$ sudo ss -l4pon | grep 80
> Finally, you added the -n option to ss, which means it no longer prints
> servi
On Fri, Jul 30, 2021 at 02:27:19PM +0300, IL Ka wrote:
> >
> > sudo netstat -ltp|grep sane-port
> >
>
> or
>
> $ sudo ss -l4pon | grep [port]
That grep command is wrong in a couple ways.
First, the unquoted [port] is a live glob pattern for the shell. The
shell will look for files in the curre
On Fri, Jul 30, 2021 at 12:37:40PM +0100, mick crane wrote:
> On 2021-07-30 11:59, Dan Ritter wrote:
> > mick crane wrote:
> > > Can I assume there is something else binding to the scanner address ?
> > > How to find out what that might be ?
> >
> >
> > sudo netstat -ltp|grep sane-port
> >
> > s
On 2021-07-30 11:59, Dan Ritter wrote:
mick crane wrote:
Can I assume there is something else binding to the scanner address ?
How to find out what that might be ?
sudo netstat -ltp|grep sane-port
should tell you the PID and name of the process.
it's inetd
tcp0 0 0.0.0.0:sane-
>
> sudo netstat -ltp|grep sane-port
>
or
$ sudo ss -l4pon | grep [port]
mick crane wrote:
> Can I assume there is something else binding to the scanner address ?
> How to find out what that might be ?
sudo netstat -ltp|grep sane-port
should tell you the PID and name of the process.
-dsr-
sorry to be a nuisance but I don't know what I'm doing and I don't know
anybody even likes computers.
I try to get the scanner to scan by pressing the button so I don't have
to keep moving between scanner and computer.
root@pumpkin:~# pidof scanbd && SANE_CONFIG_DIR=/etc/sane.d scanimage -L
627
38 matches
Mail list logo
