Mailinglist Archive: opensuse (3513 mails)

< Previous Next >
Re: [opensuse] SCSI-scanners on openSUSE 11.1
  • From: Philippe Andersson <pan@xxxxxxxxxxxxx>
  • Date: Tue, 06 Jan 2009 18:07:24 +0100
  • Message-id: <49638FCC.9020608@xxxxxxxxxxxxx>
Hello Dieter,

I recently installed an HP ScanJet 5p on my father's computer (OpenSuSE
11.0). It's also a SCSI model.

I don't have the lshal output at hand (but I could get it by next week,
if you're still interested).

This being said, I do remember that this scanner also identified itself
as a "processor" (not specifically in the lshal output, though).

Now, I could get this scanner to work perfectly by simply following the
good advice given by Yast, i.e. to enable "network scan" and to create a
"localhost configuration" (all of this is done through Yast | Hardware |
Scanner, then click the "Other" button in the lower right corner).

Once done, Kooka saw the scanner and used it without problem.


Cheers. Bye.

Ph. A.

Dieter Jurzitza wrote:
Dear listmembers,
currently I am trying to force openSUSE 11.1 to cooperate again correctly

Therefore my call:
whoever is willing and whoever owns a SCSI scanner / is using a SCSI scanner
(even better if you own different ones) please:

lshal > out

and send that to me. Whoever thinks he is supplying too much private
information (_seriously_ I am not planning anything bad :-) ) may delete
everything what has nothing to do with a scanner. I am really only interested
in the scanner as such. The corresponding part of "out" looks as follows on
my side:

= '/org/freedesktop/Hal/devices/pci_9004_8178_scsi_host_scsi_device_lun0_0'
info.parent = '/org/freedesktop/Hal/devices/pci_9004_8178_scsi_host'
info.product = 'SCSI Device' (string)
info.subsystem = 'scsi' (string)
= '/org/freedesktop/Hal/devices/pci_9004_8178_scsi_host_scsi_device_lun0_0'
linux.hotplug_type = 2 (0x2) (int)
linux.subsystem = 'scsi' (string)

scsi.bus = 0 (0x0) (int) = 6 (0x6) (int)
scsi.lun = 0 (0x0) (int)
scsi.model = 'C7670A' (string) = 6 (0x6) (int)
scsi.type = 'processor' (string)
scsi.vendor = 'HP' (string)

access_control.file = '/dev/sg2' (string)
access_control.type = 'scanner' (string)
info.callouts.add = {'hal-acl-tool --add-device'} (string list)
info.callouts.remove = {'hal-acl-tool --remove-device'} (string list)
info.capabilities = {'scsi_generic', 'scanner', 'access_control'} (string
info.category = 'scsi_generic' (string)
= '/org/freedesktop/Hal/devices/pci_9004_8178_scsi_host_scsi_device_lun0_0'
info.product = 'SCSI Generic Interface' (string)
info.subsystem = 'scsi_generic' (string)

linux.device_file = '/dev/sg2' (string)
linux.hotplug_type = 2 (0x2) (int)
linux.subsystem = 'scsi_generic' (string)

scsi_generic.device = '/dev/sg2' (string)

Of real interest for me are only two lines here: "scsi.type", on my side the
entry "processor", I expect to see "scanner" in most cases.
Whoever finds another "processor" with a model name that differs from mine
(scsi.model) or who owns a scanner that announces himself neither as
nor as "processor" is of greatest interest for me. For those specific devices
exceptions have to be inserted into the corresponding file.

Thank you very much in advance,
please send the data via email to dieter<dot>jurzitza<at>t<dash>online<dot>de

P.S. Nothing to be gained here, I've got nothing to offer but a thank you :-)
Till then,



*Philippe Andersson*
Unix System Administrator
IBA Particle Therapy |
Tel: +32-10-475.983
Fax: +32-10-487.707
eMail: pan@xxxxxxxxxxxxx

The contents of this e-mail message and any attachments are intended solely for
the recipient (s) named above. This communication is intended to be and to
remain confidential and may be protected by intellectual property rights. Any
use of the information contained herein (including but not limited to, total or
partial reproduction, communication or distribution of any form) by persons
other than the designated recipient(s) is prohibited. Please notify the sender
immediately by e-mail if you have received this e-mail by mistake and delete
this e-mail from your system. E-mail transmission cannot be guaranteed to be
secure or error-free. Ion Beam Applications does not accept liability for any
such errors. Thank you for your cooperation.
< Previous Next >