Could not fetch string descriptor pipe error

Forum rules Before you post please read how to get help. Topics in this forum are automatically closed 6 months after creation.

Forum rules
Before you post please read how to get help. Topics in this forum are automatically closed 6 months after creation.

User avatar

felemur

Level 5
Level 5
Posts: 537
Joined: Sun Sep 20, 2015 2:22 pm
Location: In the middle of 1000’s of acres of corn & soy fields in a house full of cats.

(Solved) Epson Scanner not usable since update to Mint 19 — Pipe error

I have a Epson Perfection V500 Photo Scanner GT-X770 that was working perfectly under Mint 17 & 18 series. I did a fresh install of Mint 19 Cinnamon, and all is good except for the scanner. Neither Image Scan or Simple Scan can «see» it.

I installed the correct Linux drivers from Epson, and tried both the Image Scan! app from Epson, and the Image Scan app from the repositories. All say there is no scanner. Yet, when I went to Terminal and did lsusb, I get this:

Code: Select all

david@david-OptiPlex-7010:~$ lsusb
Bus 002 Device 003: ID 051d:0002 American Power Conversion Uninterruptible Power Supply
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 020: ID 04b8:0130 Seiko Epson Corp. GT-X770 [Perfection V500]
Bus 001 Device 017: ID 05dc:a81d Lexar Media, Inc. 
Bus 003 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
david@david-OptiPlex-7010:~$ 

So, I know it is working, or it wouldn’t show up there. I’m stumped, so any ideas would be very welcome.
BTW, I did a restart after the installation of the drivers, and tried turning on and off the scanner. :) (as any previous Windows user would have).

My computer is a Dell Optiplex 7010 desktop, i7, 3770, and I’m running Mint Cinnamon 19 with all updates.

Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 3 times in total.

Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.

User avatar

felemur

Level 5
Level 5
Posts: 537
Joined: Sun Sep 20, 2015 2:22 pm
Location: In the middle of 1000’s of acres of corn & soy fields in a house full of cats.

Re: Epson Scanner not usable since update to Mint 19

Post

by felemur » Tue Jul 10, 2018 8:27 am

I don’t know if this helps, but even though the scanner is listed when doing: lsub, it gives this response when I enter: sudo scanimage -L

Code: Select all

david@david-OptiPlex-7010:~$ sudo scanimage -L
[sudo] password for david: 

No scanners were identified. If you were expecting something different,
check that the scanner is plugged in, turned on and detected by the
sane-find-scanner tool (if appropriate). Please read the documentation
which came with this software (README, FAQ, manpages).
david@david-OptiPlex-7010:~$ 

So, then I tried: sudo sane-find-scanner

Code: Select all

david@david-OptiPlex-7010:~$ sudo sane-find-scanner

  # sane-find-scanner will now attempt to detect your scanner. If the
  # result is different from what you expected, first make sure your
  # scanner is powered up and properly connected to your computer.

  # No SCSI scanners found. If you expected something different, make sure that
  # you have loaded a kernel SCSI driver for your SCSI adapter.

found USB scanner (vendor=0x04b8 [EPSON], product=0x0130 [EPSON Scanner]) at libusb:001:021
could not fetch string descriptor: Pipe error
could not fetch string descriptor: Pipe error
  # 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.

  # Most Scanners connected to the parallel port or other proprietary ports
  # can't be detected by this program.
david@david-OptiPlex-7010:~$ 

So what is a pipe error, and more to the point, what do I do to remedy this?

User avatar

felemur

Level 5
Level 5
Posts: 537
Joined: Sun Sep 20, 2015 2:22 pm
Location: In the middle of 1000’s of acres of corn & soy fields in a house full of cats.

ParaDice

Level 4
Level 4
Posts: 210
Joined: Sat Aug 27, 2016 6:38 am
Location: Germany

Re: Epson Scanner not usable since update to Mint 19 — Pipe error

Post

by ParaDice » Thu Jul 19, 2018 12:35 pm

I had similar issues with my Epson GT-S85 scanner under Linux Mint 19. The link above solved the problem for me, too. I’m quoting the solution here in case the link goes dead one day.

a) ‘sudo ln -sfr /usr/lib/sane/libsane-epkowa* /usr/lib/x86_64-linux-gnu/sane’
b) generate ‘/etc/udev/rules.d/79-udev-epson.rules’
content:
# chmod device EPSON group
ATTRS{manufacturer}==»EPSON», DRIVERS==»usb», SUBSYSTEMS==»usb», ATTRS{idVendor}==»04b8″, ATTRS{idProduct}==»*», MODE=»0777″

To get help, always post your system configuration. Open a terminal (Ctrl + Alt + T), type the following command and copy its output: inxi -Fxxxrz. To preserve formatting, please make sure to post it inside [ code] [/ code] blocks.

lostjohnny

Re: (Solved) Epson Scanner not usable since update to Mint 19 — Pipe error

Post

by lostjohnny » Sat Jul 28, 2018 5:49 am

Worked for me on my Epson Perfection V39 — eventually.

After following the advice above I had to reinstall the Iscan bundle (I’m fairly sure I’d installed it previously) and then re-enter the command at «a)» (there were also several reboots — just in case.)

Thank you very much.

ParaDice

Level 4
Level 4
Posts: 210
Joined: Sat Aug 27, 2016 6:38 am
Location: Germany

Re: (Solved) Epson Scanner not usable since update to Mint 19 — Pipe error

Post

by ParaDice » Thu Sep 13, 2018 2:50 pm

I’m coming back to correct myself. Unfortunately, the problem isn’t fixed entirely by the above solution.

While the scanner is recognised by the system and can be used for scanning, duplex scanning doesn’t seem to work. The problem occurs with scanning software of all kinds, both SimpleScan and gscan2pdf (my weapon of choice) will only scan one side of the page.

At least gscan2pdf with its more sophisticated options gives me a clue of what the problem could be. During device detection, some of the settings disappear, and these are the very settings responsible for enabling single- or dual-page-scanning.

Screenshot from 2018-09-13 20-39-20.png
Screenshot from 2018-09-13 20-39-38.png

I’m not sure how to fix this, though. I’ve looked through the settings. They allow me to switch from libimage-sane-perl (which is used by default) to scanadf (which sounds about right, after all ADF is responsible for duplex scanning, isn’t it?). If I select scanadf, however, gscan2pdf tells me that it is «updating options» during device detection, but never finishes doing so.

To get help, always post your system configuration. Open a terminal (Ctrl + Alt + T), type the following command and copy its output: inxi -Fxxxrz. To preserve formatting, please make sure to post it inside [ code] [/ code] blocks.

ParaDice

Level 4
Level 4
Posts: 210
Joined: Sat Aug 27, 2016 6:38 am
Location: Germany

Re: (Solved) Epson Scanner not usable since update to Mint 19 — Pipe error

Post

by ParaDice » Thu Sep 13, 2018 5:34 pm

I am aware of the fact that I need the appropriate drivers for this to run, and I have them installed. They used to work properly under Mint 18.3 (Ubuntu 16.04 basis), and since pretty much everything except for duplex works as it should, I was hoping this might be a minor settings or config issue, not a driver problem.

To get help, always post your system configuration. Open a terminal (Ctrl + Alt + T), type the following command and copy its output: inxi -Fxxxrz. To preserve formatting, please make sure to post it inside [ code] [/ code] blocks.

ParaDice

Level 4
Level 4
Posts: 210
Joined: Sat Aug 27, 2016 6:38 am
Location: Germany

Re: (Solved) Epson Scanner not usable since update to Mint 19 — Pipe error

Post

by ParaDice » Sat Sep 15, 2018 9:56 am

I appreciate that you’re trying to help anyway, felemur. Thanks! :)

I’ve solved the problem in meantime. While SimpleScan still won’t do duplex for some reason, I’ve managed to get gscan2pdf to do it. Turns out it had the «Preview» scanning option enabled, which does not work with ADF / duplex scanning. Disabling it did the trick for me.

Screenshot from 2018-09-15 15-53-02.png

Best wishes,
yet another happy customer. :lol:

To get help, always post your system configuration. Open a terminal (Ctrl + Alt + T), type the following command and copy its output: inxi -Fxxxrz. To preserve formatting, please make sure to post it inside [ code] [/ code] blocks.

User avatar

phd21

Level 20
Level 20
Posts: 10100
Joined: Thu Jan 09, 2014 9:42 pm
Location: Florida

Re: (Solved) Epson Scanner not usable since update to Mint 19 — Pipe error

Post

by phd21 » Sat Sep 15, 2018 10:37 am

Hi felemur, ParaDice, & Anyone Else Interested in this,

I just read your post and the good replies to it. Here are my thoughts on this as well.

+1 for using the excellent «gscan2pdf» application.

FYI: In case you did not know, there are updated versions of «gscan2pdf» and the «sane» scanner libraries that may not be in the Mint repositories but are available in their respective PPA’s. I recommend restarting computers after installing these before trying them.

Previous post with the scanning related PPA’s and installation instructions.
Simple scan in mint 19 — Linux Mint Forums
viewtopic.php?f=47&t=274108&hilit=gscan2pdf

Hope this helps …

Phd21: Mint 20 Cinnamon & xKDE (Mint Xfce + Kubuntu KDE) & KDE Neon 64-bit (new based on Ubuntu 20.04) Awesome OS’s, Dell Inspiron I5 7000 (7573) 2 in 1 touch screen, Dell OptiPlex 780 Core2Duo E8400 3GHz,4gb Ram, Intel 4 Graphics.

ParaDice

Level 4
Level 4
Posts: 210
Joined: Sat Aug 27, 2016 6:38 am
Location: Germany

Re: (Solved) Epson Scanner not usable since update to Mint 19 — Pipe error

Post

by ParaDice » Sat Sep 15, 2018 1:21 pm

Hi phd21,

thank you ever so much for pointing me to the PPAs! I have updated gscan2pdf through the PPA. Now even I can even save scanning profiles again (which hadn’t been working in the version I got from from the official repos).

Another thumbs up from me! :)

To get help, always post your system configuration. Open a terminal (Ctrl + Alt + T), type the following command and copy its output: inxi -Fxxxrz. To preserve formatting, please make sure to post it inside [ code] [/ code] blocks.

Odinista

Re: Epson Scanner not usable since update to Mint 19 — Pipe error

Post

by Odinista » Fri Oct 05, 2018 4:03 pm

ParaDice wrote: ↑

Thu Jul 19, 2018 12:35 pm

I had similar issues with my Epson GT-S85 scanner under Linux Mint 19. The link above solved the problem for me, too. I’m quoting the solution here in case the link goes dead one day.

a) ‘sudo ln -sfr /usr/lib/sane/libsane-epkowa* /usr/lib/x86_64-linux-gnu/sane’
b) generate ‘/etc/udev/rules.d/79-udev-epson.rules’
content:
# chmod device EPSON group
ATTRS{manufacturer}==»EPSON», DRIVERS==»usb», SUBSYSTEMS==»usb», ATTRS{idVendor}==»04b8″, ATTRS{idProduct}==»*», MODE=»0777″

Can someone help me? I tryied to follow these steps but with no success.
Linux mint 19
Epson L395 (printing but not scanning)

When I try to use «IScan» the response is «iScan — could not send command to scanner — check the scanner status».
When I type «sane-find-scanner» the response:
«could not fetch string descriptor: Pipe error
could not fetch string descriptor: Pipe error
found USB scanner (vendor=0x04b8, product=0x1122) at libusb:002:005
could not fetch string descriptor: Pipe error
could not fetch string descriptor: Pipe error
# 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.

# Most Scanners connected to the parallel port or other proprietary ports
# can’t be detected by this program.»

Using «scanimage -L» the response: «No scanners were identified. If you were expecting something different,
check that the scanner is plugged in, turned on and detected by the
sane-find-scanner tool (if appropriate). Please read the documentation
which came with this software (README, FAQ, manpages).»

  1. I have Ubu 14.04 on one partition and I just updated from Ubu 15.10 to Ubu 16.04 on another partition. In 14.04, xsane works fine. In 15.10, I could not get xsane to find the scanner. Now I upgraded to 16.04 and xsane still finds no device.

    The scanner works fine in 14.04. Never worked in 15.10, won’t work now in 16.04. The scanner is part of an all in one scanner printer Epson L351. It works fine in 14.04.

    This is the output of sane-find-scanner and scanimage -L

    pedro@pedro-275E4E-275E5E:~$ sudo sane-find-scanner

    # sane-find-scanner will now attempt to detect your scanner. If the
    # result is different from what you expected, first make sure your
    # scanner is powered up and properly connected to your computer.

    # No SCSI scanners found. If you expected something different, make sure that
    # you have loaded a kernel SCSI driver for your SCSI adapter.

    could not fetch string descriptor: Pipe error
    could not fetch string descriptor: Pipe error
    found USB scanner (vendor=0x04b8 [EPSON], product=0x08a1 [EPSON L350 Series]) at libusb:004:005
    # 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.

    # Most Scanners connected to the parallel port or other proprietary ports
    # can’t be detected by this program.
    pedro@pedro-275E4E-275E5E:~$

    Don’t know what a pipe error is. but the scanner is detected.

    pedro@pedro-275E4E-275E5E:~$ sudo scanimage -L
    [sudo] password for pedro:

    No scanners were identified. If you were expecting something different,
    check that the scanner is plugged in, turned on and detected by the
    sane-find-scanner tool (if appropriate). Please read the documentation
    which came with this software (README, FAQ, manpages).
    pedro@pedro-275E4E-275E5E:~$

    I have the correct settings in /etc/sane.d/epson.conf

    # usb 0x4b8 0x110
    #[EPSON L350 Series]) at libusb:004:003

    usb 0x04b8 0x08A1

    # And for the scanner module, use the following configuration:
    usb /dev/usbscanner0

    usb /dev/usb/scanner0

    This has gone on a long time now. Any tips out there please? Permissions??

    I tried running xsane as root, got danger warnings, went ahead, but still no devices found.

    I borrowed a simple canon flatbed usb powered scanner. Xsane finds it and it works. I did not have to set anything at all. Just works, as does my Epson in 14.04.

    What is wrong here? I was hoping the upgrade would solve the problem, then I could move to 16.04 completely.


  2. Re: scanner problem

    I went to the Epson webpage, downloaded and installed epkowa, which installs iscan, which is like their spin of xsane I suppose.

    I noticed in /etc/epkowa/epkowa.conf that it said:

    # For any USB scanner not known to the backend (yet), you may, at your
    # own peril(!!), force the backend to recognise and use it via libusb.
    # You can do so by the following configuration command:
    #
    usb 04b8 08a1
    #
    # SEIKO EPSON’s USB vendor ID is ‘0x04b8’ (without quotes). In order
    # to find the USB product ID, use lsusb(1).
    # A sample configuration for the Epson Perfection 1650 (Epson GT-8200),
    # which has a product ID of 0x0110, would look as follows:
    #
    #usb 0x04b8 0x0110

    «at your peril» gave me the idea to mask this line in epson.conf and epson2.conf so I wrote a few ###

    Long story short, now it works!!

    Problem may have been multiple .conf files in /etc/sane.de pointing at the same machine! No idea, but it works! Took me a year!


  3. Re: scanner problem

    Thanks for showing how you solved the problem. Please mark this thread as [SOLVED], using Thread Tools at the top right.


    I drink my Ubuntu black, no sugar.
    Ubuntu user 28819


  4. Re: scanner problem

    Hi There,

    I am facing same issue with my pixma MG3640 while trying to configure with 14.04.

    Usb is detecting as scanner(came to know this through sane-find-scanner)

    But scanimage -L is empty.

    Seemingly canon is not providing any linux drivers for this at the moment. If you have any suggestion please let me know.

    Thanks,


  5. Re: scanner problem

    It’s frustrating isn’t it? Drove me crazy for a year!

    Try setting the values of the Vendor ID and Product number from sane-find-scanner in /etc/sane.d/pixma.conf

    You can get the Vendor ID and Product Number by entering lsusb in a termminal too! If it sees your scanner, they should show up!

    You need to be root to do this. In a terminal

    sudo gedit

    You will have to enter your admin password, that will open gedit as root. Open /etc/sane.d/pixma.conf or whatever .conf is for your scanner,then just enter this line anywhere. (All the other lines will be commented out with #). At the bottom is good.

    You need this format: usb YourVendorID YourProductNumber The example below is mine:

    usb 04b8 08a1

    Of course, replace the 2 hexadecimal numbers with your Vendor ID and product number. See if xsane finds your scanner then.

    This worked for me in 14.04, but not in 15.10 or 16.04. In 16.04, I put hash tags in front of everything, and it works! Figure that out!

    Last edited by pedro_rodriguez2; May 1st, 2016 at 01:00 AM.


  6. Re: scanner problem

    Wow i’m impressed with how you got it to work.
    I have a hardware scanner too (forget which brand) and it works in v14.04 without issues.
    I’m afraid to try it in v16 after experiencing and reading about some of these types of issues.

    There’s no printer drivers for my hardware except for one crazy old long script written and it edits a lot of system folders so I never ran it.

    I just put stuff on flash drive and print from Windows at my local library.

    May Peace Prevail for Life in all Realms of Creation —Masahisa Goi


  7. Re: scanner problem

    I borrowed a friend’s little Canon scanner, it’s a flatbed usb powered scanner. Works in Ubuntu without any problem, no configuration at all. Plug it in, scan. They only cost about 300 RMB now here in China, say $ 50. My Epson multi machine was more sensitive, but it works now! I think these scanner printer machines can confuse the system.

    Printer and scanner are not the same.

    What does

    lsusb

    show on your system?

    I have the old version of Ubu on 1 partition and the newer version on another partition. When I get 16.04 working correctly, I’ll move to it completely.


  8. Re: scanner problem

    Hello pedro_rodriguez2,

    Thanks for your detailed explanation and time taken to review this.

    The same steps I tried here, pixma.conf is having same entries as there in lsusb.

    ========
    root@SydLap:~# scanimage -V
    scanimage (sane-backends) 1.0.26git; backend version 1.0.26

    root@SydLap:~# sane-find-scanner

    # sane-find-scanner will now attempt to detect your scanner. If the
    # result is different from what you expected, first make sure your
    # scanner is powered up and properly connected to your computer.

    # No SCSI scanners found. If you expected something different, make sure that
    # you have loaded a kernel SCSI driver for your SCSI adapter.

    found USB scanner (vendor=0x04a9 [Canon], product=0x178a [MG3600 series]) at libusb:002:005
    found USB scanner (vendor=0x0bda [Generic], product=0x0129 [USB2.0-CRW]) at libusb:002:002

    root@SydLap:~# scanimage -L

    No scanners were identified. If you were expecting something different….
    ===============================================

    Dont know where I am doing wrong, this is 14.04 version and I dont see much help specific to my problem in common forums out there.

    If anyone got a clue here on how to proceed, this would be appreciated deeply.

    Thanks,


  9. Re: scanner problem

    OK, try this, it can’t do any harm:

    In /etc/sane.d I have a file

    canon_dr.conf

    It lists a lot of canon scanners. I don’t see your one, but you can append it. Use gedit as root.

    at the bottom, just add the data from sane-find-scanner:

    # my crazy Canon scanner
    usb 0x04a9 0x178a

    See if that works!


  10. Re: scanner problem

    Hi,

    Seems like I am unlucky, my crazy scanner is not at all detecting.

    Funny part is I can see two lines with sane-find-scanner, the second one stays there evenif the scanner is not connected(as a history: I got sane-find-scanner catch my MG3640 only after a manual sane update using git)
    ======
    found USB scanner (vendor=0x04a9 [Canon], product=0x178a [MG3600 series]) at libusb:002:005
    found USB scanner (vendor=0x0bda [Generic], product=0x0129 [USB2.0-CRW]) at libusb:002:002

    They say no driver roll out for linux, too bad if it is true. My customer has got a bad impression with linux already lol..
    http://www.canon-europe.com/support/…20%2832-bit%29

    Anyway, thanks for your time, if you got anything further please post here. Meanwhile I will try other tips and will surely update here if I manage to get this working.

    Thanks,

    Last edited by syd2; May 4th, 2016 at 11:55 AM.


  • Печать

Страницы: [1] 2  Все   Вниз

Тема: Не работает МФУ EPSON SX535WD  (Прочитано 4760 раз)

0 Пользователей и 1 Гость просматривают эту тему.

Оффлайн
Remark3

« Последнее редактирование: 21 Июля 2014, 21:33:05 от Remark3 »


chemtech

sudo scanimage -L


Пользователь решил продолжить мысль 21 Июля 2014, 07:09:16:


ls /etc/sane.d/


Оффлайн
Remark3

В зависимости от настроения и положения звёзд на небе sudo scanimage -L может выдавать либо:
device `epkowa:usb:003:007′ is a Epson Stylus NX530/NX635/SX535WD/Stylus Office BX535WD Series flatbed scanner
либо:
device `epkowa:usb:003:007′ is a Epson (unknown model) flatbed scanner

ls /etc/sane.d/

Соответственно сканер может иногда даже определяться в simple-scan и image-scan и даже сканировать, но продолжается это недолго, так же внезапно он перестаёт определяться.

« Последнее редактирование: 21 Июля 2014, 21:27:47 от Remark3 »


chemtech

Что изменяли в dll.conf?


Пользователь решил продолжить мысль 22 Июля 2014, 07:10:36:


cat /etc/udev/rules.d/45-libsane.rules

cat /etc/sane.d/dll.conf

« Последнее редактирование: 22 Июля 2014, 07:10:36 от chemtech »


Оффлайн
Remark3

cat /etc/udev/rules.d/45-libsane.rules выдаёт:
cat: /etc/udev/rules.d/45-libsane.rules: Нет такого файла или каталога

cat /etc/sane.d/dll.conf выдаёт:

В dll.conf я, как и писал в первом посте, менял только то, что советовали сделать здесь:

т.е. закомментировал (поставил перед ними #) 2 строчки: epson2 и v4l. Раскомментировать epkowa не получилось, т.к. в этом файле нет такой строчки. После получения некорректного выхлопа sudo sane-find-scanner -q был возвращён на место старый файл dll.conf (откорректированный файл был перезаписан предварительно сохранённым старым файлом). dll.conf~, вероятно получился при автосохранении dll.conf. Т.к. файлы dll.conf и dll.conf~ оказались идентичными, то dll.conf~ удалил.


chemtech

Remark3,
Попробуйте что написано в «4. Решение возможных проблем»


Пользователь решил продолжить мысль 22 Июля 2014, 12:22:15:


chemtech,
вот тут еще почитайте
Установка сканеров, принтеров и МФУ Epson
epkowa должен же быть где-то
Сделайте

sudo updatedb
locate epkowa

« Последнее редактирование: 22 Июля 2014, 12:22:15 от chemtech »


Оффлайн
Remark3

epkowa то есть конечно.
locate epkowa выдаёт:

Кроме этого, cat /etc/sane.d/dll.d/iscan выдаёт:


chemtech


Оффлайн
Remark3

Пробовал редактировать dll.conf:
1) закомментировать строки epson2 и v4l
2) то же + добавить в файл строку epkowa
3) то же + закомментировать все строки, кроме epkowa
Ни один вариант не прошёл. Итоговый файл dll.conf:

Добавил пользователя в группу saned.
Пробовал разные варианты 45-libsane.rules:
1)SYSFS{idVendor}==»0x04b8″, SYSFS{idProduct}==»0x0891″, MODE=»664″, GROUP=»saned», ENV{libsane_matched}=»yes»
2)SYSFS{idVendor}==»04b8″, SYSFS{idProduct}==»0891″, MODE=»664″, GROUP=»saned», ENV{libsane_matched}=»yes»
3)SUBSYSTEMS==»usb», ATTRS{idVendor}==»04b8″, ATTRS{idProduct}==»0891″, ENV{libsane_matched}=»yes», GROUP=»scanner»
Тоже ни один вариант не прошёл.

Что в итоге имеем:
1)вызываем Image-scan, он не срабатывает
2)вызываем Image-scan ещё раз, он выдаёт сообщение «Could not send command to scanner. Check the scanner’s status.»
3)через ~1,5 минуты открывается окно Image-scan и можно сканировать
Simple-scan и xsane сканируют с задержкой ~1,5 минуты.
Gscan2pdf определяет неизвестную модель Epson и вылетает с ошибкой.
Из-под Gimp вообще не сканирует.

В общем 3 программы как-то худо бедно что-то сканируют, но чувствуется, что настроено всё кривовато.
Как я понял от настроек здесь ничего не зависит. Единственное, что приходит в голову так это попробовать загрузить бинарный файл, как советуют здесь:
http://www.vasilevsky.net/epson-perfection-2480-ubuntu

« Последнее редактирование: 23 Июля 2014, 02:04:23 от Remark3 »


chemtech

Remark3,

sudo adduser "ваш пользователь" sanedсделали?


Пользователь решил продолжить мысль 23 Июля 2014, 07:18:00:


выключаем сканер, перезагружаем компьютер


Оффлайн
Remark3

Пользователя добавил, вот cat /etc/group:

После каждого изменения так и делал: выключал сканер, перезагружал компьютер, включал сканер.


chemtech


Оффлайн
Remark3

Кабель не менял, т.к. не вижу смысла. По этому же кабелю как принтер устройство работает нормально, да и как сканер в общем работает, только определяется 1,5 минуты и sane-find-scanner его не видит в упор. Если бы что-то было с кабелем, то ни принтер, ни сканер не работали бы вообще.

« Последнее редактирование: 24 Июля 2014, 07:15:48 от Remark3 »


chemtech

Remark3,

cat /var/log/syslog | egrep -i "(error|fail|warning)"


Оффлайн
Remark3

cat /var/log/syslog | egrep -i «(error|fail|warning)»


  • Печать

Страницы: [1] 2  Все   Вверх

Hey,

I am trying to get the Ricoh SP 150SU to work. There are drivers/packages for almost all other Linux distributions, just not Arch. I already got it to print, by just copying the files from the provided .deb-package to their destinations, but now I’m stuck with the scanning function of the device. There even is an install.sh inside the SANE-package, which doesn’t work out of the box in Arch. I had a look into it, read some SANE documentation and tried a few steps.

What I did so far is:

  • Copy the .so-Files to /usr/lib/sane (script works until here)

  • Add «alto» to /etc/sane.d/dll.conf

  • Create file /etc/sane.d/alto.conf

  • Add lines to /usr/lib/udev/rules.d/49-sane.rules

  • Added my user to group «scanner» (also tried running all commands with sudo)

  • Reboot

cat /etc/sane.d/alto.conf:

usb # tried without this, too
usb 0x05ca 0x0454
scsi RICOH IS60

cat /usr/lib/udev/rules.d/49-sane.rules:

[...]
# RICOH SP 150SU Scanner
ATTRS{idVendor}=="05ca", ATTRS{idProduct}=="0454", MODE="0664", GROUP="scanner", ENV{libsane_matched}="yes"
# RICOH SP 150SUw Scanner
ATTRS{idVendor}=="05ca", ATTRS{idProduct}=="0456", MODE="0664", GROUP="scanner", ENV{libsane_matched}="yes"
[...]

sane-find-scanner:

# sane-find-scanner will now attempt to detect your scanner. If the
# result is different from what you expected, first make sure your
# scanner is powered up and properly connected to your computer.

# 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".

could not fetch string descriptor: Pipe error
could not fetch string descriptor: Pipe error
found USB scanner (vendor=0x05ca [RICOH], product=0x0454 [SP 150SU]) at libusb:001:004
could not fetch string descriptor: Pipe error

# 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.

# Most Scanners connected to the parallel port or other proprietary ports
# can't be detected by this program.

scanimage -L

No scanners were identified. If you were expecting something different,
check that the scanner is plugged in, turned on and detected by the
sane-find-scanner tool (if appropriate). Please read the documentation
which came with this software (README, FAQ, manpages).

You can see the full downloads page here.

Can someone please guide me to the right direction? I am not totally new to Arch or Linux in general, but it is my first time trying to install a device without just installing a package (which I would do if there was one, of course) smile

Thank you in advance, BlkChockr

Last edited by BlkChockr (2019-07-16 18:08:36)

ALT LINUX 8.0
xsane не видит

[root@a151f1 ~]# lsusb | grep ’04a9′
Bus 001 Device 008: ID 04a9:1912 Canon, Inc.
[root@a151f1 ~]# getfacl /dev/bus/usb/001/008
getfacl: Removing leading ‘/’ from absolute path names
# file: dev/bus/usb/001/008
# owner: root
# group: lp
user::rw-
group::rw-
other::r—
================================

root@a151f1 ~]# sane-find-scanner

  # sane-find-scanner will now attempt to detect your scanner. If the
  # result is different from what you expected, first make sure your
  # scanner is powered up and properly connected to your computer.

  # 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=0x0924 [Xerox], product=0x42e2 [WorkCentre 3335]) at libusb:001:004
found USB scanner (vendor=0x04a9 [Canon], product=0x1912 [LiDE 400]) at libusb:001:008
could not fetch string descriptor: Pipe error
could not fetch string descriptor: Pipe error
  # 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.

  # Most Scanners connected to the parallel port or other proprietary ports
  # can’t be detected by this program.
================================================

[root@a151f1 ~]# scanimage -L
MIB search path: /usr/share/snmp/mibs:/usr/share/mibs/net-snmp:/usr/share/mibs/iana:/usr/share/mibs/ietf:/usr/share/mibs/tubs:/usr/share/mibs/cisco:/usr/share/pibs/ietf:/usr/share/pibs/tubs:
Cannot find module (NET-SNMP-AGENT-MIB): At line 0 in (none)
Cannot find module (SNMPv2-MIB): At line 0 in (none)
Cannot find module (IF-MIB): At line 0 in (none)
Cannot find module (IP-MIB): At line 0 in (none)
Cannot find module (TCP-MIB): At line 0 in (none)
Cannot find module (UDP-MIB): At line 0 in (none)
Cannot find module (HOST-RESOURCES-MIB): At line 0 in (none)
Cannot find module (NOTIFICATION-LOG-MIB): At line 0 in (none)
Cannot find module (DISMAN-EVENT-MIB): At line 0 in (none)
Cannot find module (DISMAN-SCHEDULE-MIB): At line 0 in (none)
Cannot find module (EtherLike-MIB): At line 0 in (none)
Cannot find module (HOST-RESOURCES-TYPES): At line 0 in (none)
Cannot find module (IPV6-ICMP-MIB): At line 0 in (none)
Cannot find module (IPV6-MIB): At line 0 in (none)
Cannot find module (IPV6-TCP-MIB): At line 0 in (none)
Cannot find module (IPV6-UDP-MIB): At line 0 in (none)
Cannot find module (UCD-IPFWACC-MIB): At line 0 in (none)
Cannot find module (SNMP-TARGET-MIB): At line 0 in (none)
Cannot find module (TUNNEL-MIB): At line 0 in (none)
Cannot find module (IPV6-FLOW-LABEL-MIB): At line 0 in (none)
Cannot find module (UCD-DISKIO-MIB): At line 0 in (none)
Cannot find module (LM-SENSORS-MIB): At line 0 in (none)
Cannot find module (UCD-SNMP-MIB): At line 0 in (none)
Cannot find module (UCD-DEMO-MIB): At line 0 in (none)
Cannot find module (NET-SNMP-VACM-MIB): At line 0 in (none)
Cannot find module (SNMP-VIEW-BASED-ACM-MIB): At line 0 in (none)
Cannot find module (SNMP-COMMUNITY-MIB): At line 0 in (none)
Cannot find module (IP-FORWARD-MIB): At line 0 in (none)
Cannot find module (SNMP-NOTIFICATION-MIB): At line 0 in (none)
Cannot find module (SNMP-MPD-MIB): At line 0 in (none)
Cannot find module (SNMP-USER-BASED-SM-MIB): At line 0 in (none)
Cannot find module (SNMP-FRAMEWORK-MIB): At line 0 in (none)
Cannot find module (SNMPv2-TM): At line 0 in (none)
Cannot find module (NET-SNMP-PASS-MIB): At line 0 in (none)
Cannot find module (NET-SNMP-EXTEND-MIB): At line 0 in (none)
Cannot find module (UCD-DLMOD-MIB): At line 0 in (none)

No scanners were identified. If you were expecting something different,
check that the scanner is plugged in, turned on and detected by the
sane-find-scanner tool (if appropriate). Please read the documentation
which came with this software (README, FAQ, manpages).

В Linux’е полный ноль…

Понравилась статья? Поделить с друзьями:

Читайте также:

  • Could not enter matchmaking valorant error
  • Could not enter match inprogress pubg ошибка
  • Could not do normal boot invalid kernel length как исправить
  • Could not determine default pdf printer как исправить
  • Could not determine a temp directory name try running setup exe t path как исправить

  • 0 0 голоса
    Рейтинг статьи
    Подписаться
    Уведомить о
    guest

    0 комментариев
    Старые
    Новые Популярные
    Межтекстовые Отзывы
    Посмотреть все комментарии