Hmph. Not because Adam was right but because I have been trying to change permissions for this scanner (I need root permish) and it isn't playing ball. Nautilus claims I already have it. Terminal won't let me. (I've tried chmod) The scanner itself does work, btw but only when I fire up VueScan. Help, please. TIA.
Bev.
On 08 Oct 10:05, Bev Nicolson wrote:
Hmph. Not because Adam was right but because I have been trying to change permissions for this scanner (I need root permish) and it isn't playing ball. Nautilus claims I already have it. Terminal won't let me. (I've tried chmod) The scanner itself does work, btw but only when I fire up VueScan. Help, please. TIA.
Please include the output of the following so that we might stand a chance of working out what's going on: lsusb -v sudo ls -laR /dev/bus/usb id
Thanks,
Here it is:
Bus 001 Device 001: ID 0000:0000 Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 9 Hub bDeviceSubClass 0 Unused bDeviceProtocol 0 Full speed (or root) hub bMaxPacketSize0 64 idVendor 0x0000 idProduct 0x0000 bcdDevice 2.06 iManufacturer 3 iProduct 2 iSerial 1 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 25 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 Unused bInterfaceProtocol 0 Full speed (or root) hub iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0002 1x 2 bytes bInterval 255 can't get hub descriptor: Operation not permitted cannot read device status, Operation not permitted (1)
Then:
/dev/bus/usb: total 0 drwxr-xr-x 3 root root 60 2010-10-08 16:42 . drwxr-xr-x 3 root root 60 2010-10-08 16:42 .. drwxr-xr-x 2 root root 60 2010-10-08 16:42 001
/dev/bus/usb/001: total 0 drwxr-xr-x 2 root root 60 2010-10-08 16:42 . drwxr-xr-x 3 root root 60 2010-10-08 16:42 .. crw-rw-r-- 1 root root 189, 0 2010-10-08 16:42 001
Bev.
On 08 Oct 16:54, Bev Nicolson wrote:
Here it is:
Bus 001 Device 001: ID 0000:0000 Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 9 Hub bDeviceSubClass 0 Unused bDeviceProtocol 0 Full speed (or root) hub bMaxPacketSize0 64 idVendor 0x0000 idProduct 0x0000 bcdDevice 2.06 iManufacturer 3 iProduct 2 iSerial 1 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 25 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 Unused bInterfaceProtocol 0 Full speed (or root) hub iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0002 1x 2 bytes bInterval 255 can't get hub descriptor: Operation not permitted cannot read device status, Operation not permitted (1)
Then:
/dev/bus/usb: total 0 drwxr-xr-x 3 root root 60 2010-10-08 16:42 . drwxr-xr-x 3 root root 60 2010-10-08 16:42 .. drwxr-xr-x 2 root root 60 2010-10-08 16:42 001
/dev/bus/usb/001: total 0 drwxr-xr-x 2 root root 60 2010-10-08 16:42 . drwxr-xr-x 3 root root 60 2010-10-08 16:42 .. crw-rw-r-- 1 root root 189, 0 2010-10-08 16:42 001
Erm... and with the scanner plugged in... :)
(also, try the lsusb -v sudo'd too).
And again, plugged in. I don't think I've missed anything out.
Bev.
Bus 001 Device 002: ID 06bd:2061 AGFA-Gevaert NV SnapScan 1212U (?) Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.00 bDeviceClass 255 Vendor Specific Class bDeviceSubClass 255 Vendor Specific Subclass bDeviceProtocol 255 Vendor Specific Protocol bMaxPacketSize0 8 idVendor 0x06bd AGFA-Gevaert NV idProduct 0x2061 SnapScan 1212U (?) bcdDevice 1.00 iManufacturer 1 AGFA iProduct 2 SNAPSCAN iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 39 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x40 (Missing must-be-set bit!) Self Powered MaxPower 100mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 255 Vendor Specific Subclass bInterfaceProtocol 255 Vendor Specific Protocol iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 16 Device Status: 0x0001 Self Powered
Bus 001 Device 001: ID 0000:0000 Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 9 Hub bDeviceSubClass 0 Unused bDeviceProtocol 0 Full speed (or root) hub bMaxPacketSize0 64 idVendor 0x0000 idProduct 0x0000 bcdDevice 2.06 iManufacturer 3 iProduct 2 iSerial 1 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 25 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 Unused bInterfaceProtocol 0 Full speed (or root) hub iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0002 1x 2 bytes bInterval 255 can't get hub descriptor: Operation not permitted cannot read device status, Operation not permitted (1)
sudo ls -laR /dev/bus/usb
/dev/bus/usb: total 0 drwxr-xr-x 3 root root 60 2010-10-08 16:42 . drwxr-xr-x 3 root root 60 2010-10-08 16:42 .. drwxr-xr-x 2 root root 80 2010-10-08 17:19 001
/dev/bus/usb/001: total 0 drwxr-xr-x 2 root root 80 2010-10-08 17:19 . drwxr-xr-x 3 root root 60 2010-10-08 16:42 .. crw-rw-r-- 1 root root 189, 0 2010-10-08 16:42 001 crw-rw-r--+ 1 root root 189, 1 2010-10-08 17:20 002
On 08 Oct 17:24, Bev Nicolson wrote:
And again, plugged in. I don't think I've missed anything out.
Bev.
Bus 001 Device 002: ID 06bd:2061 AGFA-Gevaert NV SnapScan 1212U (?) Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.00 bDeviceClass 255 Vendor Specific Class bDeviceSubClass 255 Vendor Specific Subclass bDeviceProtocol 255 Vendor Specific Protocol bMaxPacketSize0 8 idVendor 0x06bd AGFA-Gevaert NV idProduct 0x2061 SnapScan 1212U (?) bcdDevice 1.00 iManufacturer 1 AGFA iProduct 2 SNAPSCAN iSerial 0 bNumConfigurations 1
<snippage class="mass" />
/dev/bus/usb/001: total 0 drwxr-xr-x 2 root root 80 2010-10-08 17:19 . drwxr-xr-x 3 root root 60 2010-10-08 16:42 .. crw-rw-r-- 1 root root 189, 0 2010-10-08 16:42 001 crw-rw-r--+ 1 root root 189, 1 2010-10-08 17:20 002
OK - so this shows us that the scanner device is owned by root:root, this is where the problem is...
So, what you need to do is add a udev rule that does the right thing for you.
So create a file in /etc/udev/rules.d called 025_agfa-snapscan.rules and put the following as the content:
--- FILE CONTENT START --- SUBSYSTEM!="usb|usb_device", GOTO="agfa_snapscan_rules_end" ACTION!="add", GOTO="agfa_snapscan_rules_end"
ATTRS{idVendor}=="06bd", ATTRS{idProduct}=="2061", MODE="0660", GROUP="scanner"
LABEL="agfa_snapscan_rules_end" --- FILE CONTENT END ---
Then unplug and plug back in the scanner. The device should then be in the scanner group instead of root, and assuming that you are in the scanner group, you'll have access to it. If you're not in the scanner group, but are in plugdev, then just change the GROUP setting above.
Thanks,
On 09 Oct 18:30, Bev Nicolson wrote:
Thanks Brett but I have what may be a silly question. How do log in as root to do this? (Or at least, once I've typed in sudo su then what would I do?) Bev.
Well, I'd personally do:
sudo vim /etc/udev/rules.d/025_agfa-snapscan.rules
To edit the file, put the content in and save it...
Otherwise, create the file in your home directory as you using your favourite text editor, then copy it using: sudo cp ~/025_agfa-snapscan.rules /etc/udev/rules.d/
Once the file is place, unplugging and plugging in the scanner will mean that it has the right properties and you can use it as yourself.
Thanks,
On 09/10/10 18:43, Brett Parker wrote:
Well, I'd personally do:
sudo vim /etc/udev/rules.d/025_agfa-snapscan.rules
Personally I wouldn't suggest vim as I think it's about as user friendly as being mugged, but YMMV.
A friendlier version if you're using ubuntu would be to type this in a terminal
gksu gedit /etc/udev/rules.d/025_agfa-snapscan.rules
Of course, this....
To edit the file, put the content in and save it...
Otherwise, create the file in your home directory as you using your favourite text editor, then copy it using: sudo cp ~/025_agfa-snapscan.rules /etc/udev/rules.d/
Once the file is place, unplugging and plugging in the scanner will mean that it has the right properties and you can use it as yourself.
...should work OK too! :-)
Steve
On 9 October 2010 18:30, Bev Nicolson lumos60@gmail.com wrote:
Thanks Brett but I have what may be a silly question. How do log in as root to do this? (Or at least, once I've typed in sudo su then what would I do?) Bev.
Hi Bev,
Just in case you're not sure on this: If you execute a command as yourself but using 'sudo' before it, it means you are being given root privilege to execute said command. It avoids the need to log in to a shell as root.
Typing 'sudo su' is akin to saying 'Let me switch to being root - look,I have root privilege to allow me to do this'. Because executing a command using sudo allows you to execute a command without having to log in as root, you won't need to do this.
Hope I've put that sensibly.
Jenny
On Sat, Oct 09, 2010 at 08:23:51PM +0100, Jenny Hopkins wrote:
Typing 'sudo su' is akin to saying 'Let me switch to being root - look,I have root privilege to allow me to do this'. Because executing a command using sudo allows you to execute a command without having to log in as root, you won't need to do this.
If you want a root shell and have sudo then you can use sudo -i to get your root shell.
Adam
I've got the text file in the right folder but XSane refuse to open it. Here's what it says if it helps anyone diagnose the issue. (Well, I guess the issue is, it still thinks it's in root and won't let it near my grubby paws.) How do I knock some sense into it?
can't get hub descriptor: Operation not permitted cannot read device status, Operation not permitted (1) sudo ls -laR /dev/bus/usb
/dev/bus/usb: total 0 drwxr-xr-x 3 root root 60 2010-10-10 15:49 . drwxr-xr-x 3 root root 60 2010-10-10 15:49 .. drwxr-xr-x 2 root root 80 2010-10-10 17:14 001
/dev/bus/usb/001: total 0 drwxr-xr-x 2 root root 80 2010-10-10 17:14 . drwxr-xr-x 3 root root 60 2010-10-10 15:49 .. crw-rw-r-- 1 root root 189, 0 2010-10-10 15:49 001 crw-rw-r--+ 1 root scanner 189, 4 2010-10-10 17:22 005
Bev.
On 10 Oct 17:30, Bev Nicolson wrote:
I've got the text file in the right folder but XSane refuse to open it. Here's what it says if it helps anyone diagnose the issue. (Well, I guess the issue is, it still thinks it's in root and won't let it near my grubby paws.) How do I knock some sense into it?
can't get hub descriptor: Operation not permitted cannot read device status, Operation not permitted (1) sudo ls -laR /dev/bus/usb
/dev/bus/usb: total 0 drwxr-xr-x 3 root root 60 2010-10-10 15:49 . drwxr-xr-x 3 root root 60 2010-10-10 15:49 .. drwxr-xr-x 2 root root 80 2010-10-10 17:14 001
/dev/bus/usb/001: total 0 drwxr-xr-x 2 root root 80 2010-10-10 17:14 . drwxr-xr-x 3 root root 60 2010-10-10 15:49 .. crw-rw-r-- 1 root root 189, 0 2010-10-10 15:49 001 crw-rw-r--+ 1 root scanner 189, 4 2010-10-10 17:22 005
That looks right - what does xsane say? Are you in the scanner group? Can we have the output of the command "id"?
The id command will list the groups you're in, if you're not in the scanner group you wont have permissions.
If it turns out that you're not in the scanner group then do: sudo adduser yourusername scanner
Obviously replacing yourusername with, erm, your username...
Then logout and back in again.
Thanks,
id /says/ I'm in the scanner group. Hmm. XSane says 'Failed to open device snapscan:libusb:001:002 invalid argument' . Beats head against brick wall.
Bev.
If it turns out that you're not in the scanner group then do: sudo adduser yourusername scanner
Obviously replacing yourusername with, erm, your username...
Just in case it helps (or I've misinterpreted it) here's id (edited.)
uid=1000(myusername) gid=1000(myusername) groups=4(adm),20(dialout),21(fax),24(cdrom),25(floppy),29(audio),30(dip),44(video),46(plugdev),100(users),106(lpadmin),110(scanner),112(admin),1000(myusername)
Bev.
On 11 October 2010 09:51, Bev Nicolson lumos60@gmail.com wrote:
id /says/ I'm in the scanner group. Hmm. XSane says 'Failed to open device snapscan:libusb:001:002 invalid argument' . Beats head against brick wall.
Bev.
On Monday 11 October 2010 09:51:50 Bev Nicolson wrote:
id /says/ I'm in the scanner group. Hmm. XSane says 'Failed to open device snapscan:libusb:001:002 invalid argument' . Beats head against brick wall.
Bev.
If it turns out that you're not in the scanner group then do: sudo adduser yourusername scanner
Obviously replacing yourusername with, erm, your username...
OK, now try using vuescan again. Now it may work on xsane after you have got it working with that once. it does with me anyway, and no I have no idea why, so all this discussion has been most interesting.
But you know, at some point discretion is the better part of valor, and it is probably easiest to just buy vuescan, which is pretty decent package.
Peter
[Big Snip]
OK, I've vaguely recalled having to upload a firmware file to the scanner to make it work. I googled it before but failed to find anything. When you've read this, have a google yourself and see if you can find more info.
Anyway, I've just found a result, but it's in French of which I parlez rein.
See: http://www.queret.net/blog/post/2007/10/02/103-linux-debian-scanner-usb-agfa...
Scroll down to "Commentaires" "1 Le jeudi, 13 décembre 2007"
This mentions a config file /etc/sane.d/snapscan.conf, which I have. It says <Quote> # Change to the fully qualified filename of your firmware file, if # firmware upload is needed by the scanner #firmware /usr/share/sane/snapscan/your-firmwarefile.bin firmware /usr/share/sane/snapscan/SnapScan_1212U_2.bin </Quote>
And this is how my config file reads, and I have the bin file present. If you/anyone finds English instructions on this, please share them with me via the list, so if I need to rebuild my machine I've got a clue! :-)
I will email Bev the bin file direct.
An Explanation: I think this scanner is quite "dumb". It can do things, process stuff etc, but it doesn't have any firmware, i.e. instructions on how to do stuff. It relies on the operating system to transfer the firmware to it before it does anything. That is what the .bin file is, and I recall finding it inside the windows setup file or package for the scanner. XSane can upload the info to the scanner, if it's been told what to do, and where the file is. The reason why it works after using the other scanner program, is because presumably that uploads some firmware to the scanner, and it stays there until the scanner's switched off.
I hope that makes sense!
Regards Steve
On 11-Oct-10 09:53:36, steve-ALUG@hst.me.uk wrote:
[Big Snip]
OK, I've vaguely recalled having to upload a firmware file to the scanner to make it work. I googled it before but failed to find anything. When you've read this, have a google yourself and see if you can find more info.
Anyway, I've just found a result, but it's in French of which I parlez rein.
Ah, you speak Kidney! See below.
See: http://www.queret.net/blog/post/2007/10/02/103-linux-debian-scanner-usb- agfa-snapscan-1212u
Scroll down to "Commentaires" "1 Le jeudi, 13 décembre 2007"
This mentions a config file /etc/sane.d/snapscan.conf, which I have. It says
<Quote> # Change to the fully qualified filename of your firmware file, if # firmware upload is needed by the scanner #firmware /usr/share/sane/snapscan/your-firmwarefile.bin firmware /usr/share/sane/snapscan/SnapScan_1212U_2.bin </Quote>
And this is how my config file reads, and I have the bin file present. If you/anyone finds English instructions on this, please share them with me via the list, so if I need to rebuild my machine I've got a clue! :-)
I will email Bev the bin file direct.
An Explanation: I think this scanner is quite "dumb". It can do things, process stuff etc, but it doesn't have any firmware, i.e. instructions on how to do stuff. It relies on the operating system to transfer the firmware to it before it does anything. That is what the .bin file is, and I recall finding it inside the windows setup file or package for the scanner. XSane can upload the info to the scanner, if it's been told what to do, and where the file is. The reason why it works after using the other scanner program, is because presumably that uploads some firmware to the scanner, and it stays there until the scanner's switched off.
I hope that makes sense!
Regards Steve
For what it's worth, below is a translation of the French original, including the two commments made later by others. Ted.
########################################################### Linux Debian : Scanner USB AGFA SnapScan 1212u By Yoann Tuesday, 2 October 2007, 12:20
I have just picked up an AGFA SnapScan 1212u scanner.
While this is immediately recognised by Ubuntu, that is not the case for Debian Etch. Whether using Gimp or Xsane, the message "No peripheral recognised" comes up.
I shall explain the very simple procedure for installing and configuring an AGFA SnapScan 1212u scanner on Debian Etch.
Prerequisites: The packages xsane and gimp must already be present at the time of installation.
Before you do anything else, install missing packages:
apt-get install sane xsane sane-utils libsane libsane-extras
Scanner detection:
sane-find-scanner
# No SCSI scanners found. If you expected something different, # make sure that you have loaded a kernel SCSI driver for your # SCSI adapter. # Also you need support for SCSI Generic (sg) in your operating system. # If using Linux, try "modprobe sg".
found USB scanner (vendor=0x06bd AGFA, product=0x0001 SNAPSCAN 1212U) at libusb:001:002
# Your USB scanner was (probably) detected. It may or may not be # supported by SANE. Try scanimage -L and read the backend's manpage.
# Not checking for parallel port scanners.
Now check that the file /etc/sane.d/snapscan.conf contains the two lines which correspond to the AGFA 1212U scanners (of which there are in fact two models):
cat /etc/sane.d/snapscan.conf
# Agfa 1212U usb 0x06bd 0x0001 usb 0x06bd 0x2061
Now check that the scanner is properly detected:
scanimage -L
device `snapscan:libusb:001:002' is a AGFA SNAPSCAN 1212U flatbed scanner
Next, you must add your username to group 'scanner':
adduser <username> scanner
Now check that you are indeed in group 'scanner' using the command 'groups'. If you are not, re-start your session to endure that the changes are registered.
Now Xsane and Gimp should be able to access the scanner.
Comments:
1. Tuesday , 13 Décember 2007, 10:40 by jbemond You have to choose the snapscan type in /etc/sane.d/snapscan.conf In my case it is USB... Then you have to put the driver[? Fr = "pilote"] (firmware) for this scanner in: /usr/share/sane/snapscan/SnapScan_1212U_2.bin
# Change to the fully qualified filename of your firmware file, if # firmware upload is needed by the scanner # firmware /usr/share/sane/snapscan/your-firmwarefile.bin # firmware /usr/share/sane/snapscan/SnapScan_1212U_2.bin
# If not automatically found you may manually specify a device name.
# For USB scanners also specify bus=usb, e.g. /dev/usb/scanner0 bus=usb
# For SCSI scanners specify the generic device, e.g. /dev/sg0 on Linux. # /dev/sg0
2. Wednesday, 27 February 2008, 10:39 by sinbad83 Despite an intensive Internet search, including the manufacturer's website, I have not been able to find the Linux (Ubuntu) driver for an HP4600 scanner. Might there be some generic Sane driver that one could use?
-------------------------------------------------------------------- E-Mail: (Ted Harding) ted.harding@wlandres.net Fax-to-email: +44 (0)870 094 0861 Date: 11-Oct-10 Time: 12:21:42 ------------------------------ XFMail ------------------------------
Yes, that makes sense Steve. But I have another question. How do I cp over the bin file to the bin folder? I've just tried something and nowt happened. And no it won't let me drag and drop it. Oh no.
Bev.
An Explanation: I think this scanner is quite "dumb". It can do things, process stuff etc, but it doesn't have any firmware, i.e. instructions on how to do stuff. It relies on the operating system to transfer the firmware to it before it does anything. That is what the .bin file is, and I recall finding it inside the windows setup file or package for the scanner. XSane can upload the info to the scanner, if it's been told what to do, and where the file is. The reason why it works after using the other scanner program, is because presumably that uploads some firmware to the scanner, and it stays there until the scanner's switched off.
I hope that makes sense!
Regards Steve
main@lists.alug.org.uk http://www.alug.org.uk/ http://lists.alug.org.uk/mailman/listinfo/main Unsubscribe? See message headers or the web site above!
On 11/10/10 17:04, Bev Nicolson wrote:
Yes, that makes sense Steve. But I have another question. How do I cp over the bin file to the bin folder? I've just tried something and nowt happened. And no it won't let me drag and drop it. Oh no.
Bev.
Drag and drop the file to your desktop, or save it on your desktop.
Open Nautilus (the file manager) and see if the directory /usr/share/sane/snapscan exists.
If it doesn't, then open a terminal and type
sudo mkdir /usr/share/sane/snapscan
If you've done that, or the directory exists, type this in a terminal NB it's all on one line. Replace YOUR_USER_NAME with the name of your Home folder's name.
sudo cp /home/YOUR_USER_NAME/Desktop/SnapScan_1212U_2.bin /usr/share/sane/snapscan/
The above copies the file. Then type
sudo chown root:root /usr/share/sane/snapscan/SnapScan_1212U_2.bin
That should make sure the file is owned by the root user.
Then start xsane and see what happens. Perhaps if you try starting it from a terminal by typing xsane, you'll see any error messages that come up.
Hope this helps.
Regards Steve
I get this Steve:
ls: cannot access /usr/share/sane/snapscan/SnapScan1212U_2.bin: No such file or directory
Which is less than helpful, imo.
However this is more promising:
[snapscan] Cannot open firmware file /usr/share/sane/snapscan/your-firmwarefile.bin. [snapscan] Edit the firmware file entry in snapscan.conf.
How do I do this?
Bev.
On 12 Oct 09:45, Bev Nicolson wrote:
I get this Steve:
ls: cannot access /usr/share/sane/snapscan/SnapScan1212U_2.bin: No such file or directory
Which is less than helpful, imo.
However this is more promising:
[snapscan] Cannot open firmware file /usr/share/sane/snapscan/your-firmwarefile.bin. [snapscan] Edit the firmware file entry in snapscan.conf.
OK - attached is the firmware file that you're looking for...
Copy that in to /usr/share/sane/snapscan as root:
sudo cp SnapScan1212U_2.bin /usr/share/sane/snapscan/SnapScan1212U_2.bin
In the directory you saved it to.
Then: sudo jedit /etc/sane.d/snapscan.conf
Change the firmware line to: firmware /usr/share/sane/snapscan/SnapScan1212U_2.bin
and save the file.
Now you should be fully functional!
Probably.
Thanks,
On 12 Oct 10:44, Brett Parker wrote:
On 12 Oct 09:45, Bev Nicolson wrote:
I get this Steve:
ls: cannot access /usr/share/sane/snapscan/SnapScan1212U_2.bin: No such file or directory
Which is less than helpful, imo.
However this is more promising:
[snapscan] Cannot open firmware file /usr/share/sane/snapscan/your-firmwarefile.bin. [snapscan] Edit the firmware file entry in snapscan.conf.
OK - attached is the firmware file that you're looking for...
Except, user error was involved, and I failed at attaching the file, have sent it off list though :)
Right. Guess what? Terminal says no. Like this:
cp: cannot create regular file `/usr/share/sane/snapscan/SnapScan1212U_2.bin': No such file or directory
We know it /can/ do this so how do we get it to?
Bev.
On 12 Oct 16:41, Bev Nicolson wrote:
Right. Guess what? Terminal says no. Like this:
cp: cannot create regular file `/usr/share/sane/snapscan/SnapScan1212U_2.bin': No such file or directory
sudo mkdir -p /usr/share/sane/snapscan sudo cp SnapScan1212U_2.bin /usr/share/sane/snapscan
Hope that helps,
It's as well I'm determined and I quite like Bash. Here's what I've done so far (edited.) Have I gone wrong somewhere?
sudo cp SnapScan1212U_2.bin /usr/share/sane/snapscan/SnapScan1212U_2.bin cp: cannot stat `SnapScan1212U_2.bin': No such file or directory sudo cp SnapScan1212U_2.bin /usr/share/sane/snapscan cp: cannot stat `SnapScan1212U_2.bin': No such file or directory
sudo mkdir -p SnapScan1212U_2.bin cp SnapScan1212U_2.bin /usr/share/sane/snapscan cp: omitting directory `SnapScan1212U_2.bin' sudo cp SnapScan1212U_2.bin /usr/share/sane/snapscan cp: omitting directory `SnapScan1212U_2.bin' firmware /usr/share/sane/snapscan/SnapScan1212U_2.bin bash: firmware: command not found sudo jedit /etc/sane.d/snapscan.conf sudo: jedit: command not found sudo edit /etc/sane.d/snapscan.conf Warning: unknown mime-type for "/etc/sane.d/snapscan.conf" -- using "application/*" Error: no "edit" mailcap rules found for type "application/*"
P.S. Edited the firmware line in gedit. Still refusing to open. Grr. Is there any thing else I can do?
Bev.
sudo cp SnapScan1212U_2.bin /usr/share/sane/snapscan/SnapScan1212U_2.bin cp: cannot stat `SnapScan1212U_2.bin': No such file or directory sudo cp SnapScan1212U_2.bin /usr/share/sane/snapscan cp: cannot stat `SnapScan1212U_2.bin': No such file or directory
sudo mkdir -p SnapScan1212U_2.bin
On 13 Oct 09:58, Bev Nicolson wrote:
It's as well I'm determined and I quite like Bash. Here's what I've done so far (edited.) Have I gone wrong somewhere?
sudo cp SnapScan1212U_2.bin /usr/share/sane/snapscan/SnapScan1212U_2.bin
That should have been run in the directory that you'd saved SnapScan1212U_2.bin into, then it should have worked.
cp: cannot stat `SnapScan1212U_2.bin': No such file or directory sudo cp SnapScan1212U_2.bin /usr/share/sane/snapscan cp: cannot stat `SnapScan1212U_2.bin': No such file or directory
sudo mkdir -p SnapScan1212U_2.bin cp SnapScan1212U_2.bin /usr/share/sane/snapscan cp: omitting directory `SnapScan1212U_2.bin' sudo cp SnapScan1212U_2.bin /usr/share/sane/snapscan cp: omitting directory `SnapScan1212U_2.bin' firmware /usr/share/sane/snapscan/SnapScan1212U_2.bin
That line was to go in to the text file that is in /etc/sane.d/snapscan.conf, not at a bash prompt.
bash: firmware: command not found sudo jedit /etc/sane.d/snapscan.conf
OK - so you haven't got jedit installed :) Use: sudo editor /etc/sane.d/snapscan.conf
edit the line, save the file, and bob should be your uncle. Probably.
sudo: jedit: command not found sudo edit /etc/sane.d/snapscan.conf Warning: unknown mime-type for "/etc/sane.d/snapscan.conf" -- using "application/*" Error: no "edit" mailcap rules found for type "application/*"
Umm, this is fairly tentative but I /think/ it's worked. (Thudding noise as several luggers fall to a faint from shock.) Either way I just fired it up in Terminal and there it was. If I ever meet Brett or Steve I shall buy you both a beer or other drink of your choice. Thank you.
Bev.
On 13/10/10 10:43, Brett Parker wrote:
On 13 Oct 09:58, Bev Nicolson wrote:
sudo jedit /etc/sane.d/snapscan.conf
OK - so you haven't got jedit installed :) Use: sudo editor /etc/sane.d/snapscan.conf
edit the line, save the file, and bob should be your uncle. Probably.
sudo: jedit: command not found
I think that should have been sudo gedit .... not sudo jedit ....
Sorry I've been absent from this thread for a while - I've been busy with "Real Life". Glad it seems to be working now :-)
Steve
It's still moaning about the firmware needing editing, though it has been. Should I just give up with it?
Bev.
Me again. Investigating where the two bin files have /actually/ got to, I see one is my home folder (locked) and the other is in the file system but not in the bin folder or the usr bin folder. (I thought I'd been careful here) Is this likely to be part of the problem? I'm determined to get Brett's instructions thoroughly implemented (as it were) before I give up. TIA.
Bev.
Bev Nicolson wrote:
Me again. Investigating where the two bin files have /actually/ got to, I see one is my home folder (locked) and the other is in the file system but not in the bin folder or the usr bin folder. (I thought I'd been careful here) Is this likely to be part of the problem? I'm determined to get Brett's instructions thoroughly implemented (as it were) before I give up. TIA.
Yes that is absolutely likely to be the problem.
Try this (adapted from a previous post)
Open a terminal and type
sudo mkdir /usr/share/sane/snapscan
Then type this in a terminal NB it's all on one line.
sudo cp ~/SnapScan_1212U_2.bin /usr/share/sane/snapscan/
The above should copy one file. Then type
sudo chown root:root /usr/share/sane/snapscan/SnapScan_1212U_2.bin
That should make sure the file is owned by the root user.
Then start xsane and see what happens. Perhaps if you try starting it from a terminal by typing xsane, you'll see any error messages that come up.
Hope this helps.
Regards
Steve
Ha. I surprise myself. It is in there. But this pesky scanner is still not opening. I have by the by, done what Brett suggested too. Bev.
On 11 October 2010 17:04, Bev Nicolson lumos60@gmail.com wrote:
Yes, that makes sense Steve. But I have another question. How do I cp over the bin file to the bin folder? I've just tried something and nowt happened. And no it won't let me drag and drop it. Oh no.
On 11/10/10 18:31, Bev Nicolson wrote:
Ha. I surprise myself. It is in there. But this pesky scanner is still not opening. I have by the by, done what Brett suggested too. Bev.
Bev, I don't have the answers, but out of interest, what does this say?
ls -al /usr/share/sane/snapscan/SnapScan1212U_2.bin
is it owned by Root Root? If not try the chown line from my last message.
And what (if any) error messages do you get if you start xsane from a terminal prompt?
Regards Steve
[Resent as original didn't appear on the list]
On 11/10/10 17:04, Bev Nicolson wrote:
Yes, that makes sense Steve. But I have another question. How do I cp over the bin file to the bin folder? I've just tried something and nowt happened. And no it won't let me drag and drop it. Oh no.
Bev.
Drag and drop the file to your desktop, or save it on your desktop.
Open Nautilus (the file manager) and see if the directory /usr/share/sane/snapscan exists.
If it doesn't, then open a terminal and type
sudo mkdir /usr/share/sane/snapscan
If you've done that, or the directory exists, type this in a terminal NB it's all on one line. Replace YOUR_USER_NAME with the name of your Home folder's name.
sudo cp /home/YOUR_USER_NAME/Desktop/SnapScan_1212U_2.bin /usr/share/sane/snapscan/
The above copies the file. Then type
sudo chown root:root /usr/share/sane/snapscan/SnapScan_1212U_2.bin
That should make sure the file is owned by the root user.
Then start xsane and see what happens. Perhaps if you try starting it from a terminal by typing xsane, you'll see any error messages that come up.
Hope this helps.
Regards Steve
I am really enjoying this thread, Its great to have finally learned why it is that vuescan should get my scanner going. And its also very nice to see people diving in and helping like this: its what Linux is all about. Or part of what its about.
Peter
On 11 Oct 10:32, Peter Alcibiades wrote:
On Monday 11 October 2010 09:51:50 Bev Nicolson wrote:
id /says/ I'm in the scanner group. Hmm. XSane says 'Failed to open device snapscan:libusb:001:002 invalid argument' . Beats head against brick wall.
Bev.
If it turns out that you're not in the scanner group then do: sudo adduser yourusername scanner
Obviously replacing yourusername with, erm, your username...
OK, now try using vuescan again. Now it may work on xsane after you have got it working with that once. it does with me anyway, and no I have no idea why, so all this discussion has been most interesting.
But you know, at some point discretion is the better part of valor, and it is probably easiest to just buy vuescan, which is pretty decent package.
At a guess I'd say there's some missing firmware, but I'd need to look up the scanner, which I haven't had a chance to do yet... If it is that then there's some more things that we can probably do!
Reading around, there's a known bug, and the suggested workaround is to: sudo apt-get install scanbuttond
Thanks,
-
Adam Bower -
Bev Nicolson -
Brett Parker -
Jenny Hopkins -
Peter Alcibiades -
steve-ALUG＠hst.me.uk -
ted.harding＠wlandres.net