SuSE doesn't config Epson perfection 2450 PHOTO scanner
gracia@Vigor10:~> /usr/sbin/lsusb Bus 003 Device 003: ID 04b8:0112 Seiko Epson Cor p. Perfection 2450 Bus 003 Device 001: ID 0000:0000 Bus 002 Device 001: ID 0000:0000 Bus 001 Device 004: ID 05e3:0700 Genesys Logic, Inc. SIIG US2256 CompactFlash Card Reader Bus 001 Device 001: ID 0000:0000 -- Gracia...Cooleemee, NC Registered Linux user #263390 - SuSE 10 Pro My country, right or wrong. If right, to be kept right, if wrong, to be
I'm using suseSUSE 10. It 'sees' it but comes up with 'not configured' & epkowa says 'no active scanner for this driver. I have had no trouble using it in SUSE 9.3 Any ideas?? put right.
Hello, On Jan 11 21:15 Gracia M. Littauer wrote (shortened):
I'm using suseSUSE 10. It 'sees' it but comes up with 'not configured' & epkowa says 'no active scanner for this driver.
The reason is that any USB device can be identified on the USB (there are USB strandards which are used to do this). The driver "epkowa" was successfully activated but this driver cannot find your scanner and therefore your scanner is still not ready to be used. Normally, a driver automatically detects the USB scanners it supports. As the driver "epkowa" supports your scanner but as it cannot detect it, this indicates that the USB communication fails on your system (except the lowest-level USB device identification).
I have had no trouble using it in SUSE 9.3
gracia@Vigor10:~> /usr/sbin/lsusb Bus 003 Device 003: ID 04b8:0112 Seiko Epson Corp. Perfection 2450
I know that the following may not directly help you to get your scanner working, nevertheless it should help you to understand where you can search for the problem: For example my Epson Perfection 2480 works o.k. with Suse Linux 10.0 using the epkowa backend. "Works o.k." means that it works except some USB problems which happen from time to time: For unknown reason (there is no USB error message in dmesg) it happens from time to time that USB communication is no longer possible. Sometimes it works again by unknown magic after waiting a bit. Sometimes it works again after re-loading USB kernel modules. Always it works again after re-booting the system. Perhaps the USB hardware on my workstation is a bit unstable, see what I wrote about my Epson Stylus Photo RX420 and about "If a USB scanner is not detected by YaST" at http://portal.suse.com/sdb/en/2005/09/jsmeix_scanner-setup-100.html In general regarding "USB, hotplug, udev, HAL, ...", see http://portal.suse.com/sdb/en/2004/10/jsmeix_scanner-setup-92.html and note that "the details change from version to version. Additionally there will be further enhancements (e.g. "udev", "HAL", ...). An article regarding scanner setup cannot describe all the details about USB, hotplug, udev, HAL, resmgr, PAM, and so on. Refer to the appropriate specific documentation if there are problems in one of these areas." In general regarding "Trouble-Shooting (Debugging)" see http://portal.suse.com/sdb/en/2004/10/jsmeix_scanner-setup-92.html Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5 Mail: jsmeix@suse.de 90409 Nuernberg, Germany WWW: http://www.suse.de/
Hello, FYI: Regarding the troubles with the Epson Perfection 2450 PHOTO see the "Epson 2450" thread on the sane-devel mailing list: http://lists.alioth.debian.org/pipermail/sane-devel/2006-January/015980.html It shows that it is very likely no problem in the SANE software but in the low-level device access layers. Perhaps with USB 1.x it might work? Perhaps with firewire it might work? Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5 Mail: jsmeix@suse.de 90409 Nuernberg, Germany WWW: http://www.suse.de/
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Thursday 2006-01-12 at 10:17 +0100, Johannes Meixner wrote: ...
For example my Epson Perfection 2480 works o.k. with Suse Linux 10.0 using the epkowa backend.
"Works o.k." means that it works except some USB problems which happen from time to time: For unknown reason (there is no USB error message in dmesg) it happens from time to time that USB communication is no longer possible. Sometimes it works again by unknown magic after waiting a bit. Sometimes it works again after re-loading USB kernel modules. Always it works again after re-booting the system.
Sounds familiar... See if this rings a bell. Instead of halting/booting my system every day, I prefer to suspend it to disk. Sometimes it happens, perhaps after a month without problems, that one day the scanner (epson 1650 via usb) is no longer there. I can not list it with lsusb. Gone. The only solution seems to be to reboot - down the flush goes my uptime! ;-) This is with SuSE 9.3. Time ago, there was "rchotplug restart" that would force the usb bus to work again, but the script has disappeared. I tried reloading usb kernel modules, but it did not work; perhaps I did it wrong. It seems the usb init script is now inside "/etc/init.d/kbd". I will try the method there next time it happens. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFD2A1wtTMYHG2NR9URAsJYAJ9d+lR3mbtb+mE80Vx0enL8dHPOfwCfVvl7 VlqTXyEvKnN7JXosfV2EL3s= =Eoql -----END PGP SIGNATURE-----
Carlos E. R. said:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Thursday 2006-01-12 at 10:17 +0100, Johannes Meixner wrote:
...
For example my Epson Perfection 2480 works o.k. with Suse Linux 10.0 using the epkowa backend.
"Works o.k." means that it works except some USB problems which happen from time to time: For unknown reason (there is no USB error message in dmesg) it happens from time to time that USB communication is no longer possible. Sometimes it works again by unknown magic after waiting a bit. Sometimes it works again after re-loading USB kernel modules. Always it works again after re-booting the system.
Sounds familiar...
See if this rings a bell. Instead of halting/booting my system every day, I prefer to suspend it to disk. Sometimes it happens, perhaps after a month without problems, that one day the scanner (epson 1650 via usb) is no longer there. I can not list it with lsusb. Gone. The only solution seems to be to reboot - down the flush goes my uptime! ;-)
This is with SuSE 9.3. Time ago, there was "rchotplug restart" that would force the usb bus to work again, but the script has disappeared. I tried reloading usb kernel modules, but it did not work; perhaps I did it wrong.
It seems the usb init script is now inside "/etc/init.d/kbd". I will try the method there next time it happens.
A colleague has been having similar problems with a different model of Epson scanner. He found that connecting the scanner directly to the PC rather through a hub fixed his problem. -- David Bottrill david@bottrill.org www.bottrill.org Registered Linux user number 330730 Internet Free World Dialup: 683864
On Thu, 26 Jan 2006 10:56:54 -0000 (UTC) "David Bottrill" <david@bottrill.org> wrote:
Carlos E. R. said:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Thursday 2006-01-12 at 10:17 +0100, Johannes Meixner wrote:
...
For example my Epson Perfection 2480 works o.k. with Suse Linux 10.0 > using the epkowa backend.
"Works o.k." means that it works except some USB problems which happen from time to time: For unknown reason (there is no USB error message in dmesg) it happens from time to time that USB communication is no longer possible. Sometimes it works again by unknown magic after waiting a bit. Sometimes it works again after re-loading USB kernel modules. Always it works again after re-booting the system.
Sounds familiar...
See if this rings a bell. Instead of halting/booting my system every day, I prefer to suspend it to disk. Sometimes it happens, perhaps after a month without problems, that one day the scanner (epson 1650 via usb) is no longer there. I can not list it with lsusb. Gone. The only solution seems to be to reboot - down the flush goes my uptime! ;-)
This is with SuSE 9.3. Time ago, there was "rchotplug restart" that would force the usb bus to work again, but the script has disappeared. I tried reloading usb kernel modules, but it did not work; perhaps I did it wrong.
I'm using 9.3 and there's no rchotplug on my system. Okay... you mean that it was part of some Suse prior to 9.3...
It seems the usb init script is now inside "/etc/init.d/kbd". I will try the method there next time it happens.
....
Looking at that script, there's comments which say: # [bugzilla #46113] # we come here although heading for runlevel 5. # I'll comment out diabling hotplug for now. jw. # test -f /proc/sys/kernel/hotplug && echo /bin/true > \ /proc/sys/kernel/hotplug 2>/dev/null (note wrap crap) I just found this, so haven't had a hard look at this code or at bug #46113. Seems curious though. -- "This world ain't big enough for the both of us," said the big noema to the little noema.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Thursday 2006-01-26 at 07:39 -0500, ken wrote:
Carlos E. R. said:
This is with SuSE 9.3. Time ago, there was "rchotplug restart" that would force the usb bus to work again, but the script has disappeared. I tried reloading usb kernel modules, but it did not work; perhaps I did it wrong.
I'm using 9.3 and there's no rchotplug on my system. Okay... you mean that it was part of some Suse prior to 9.3...
Exactly. Perhaps it was with 9.1 or 8.2, I don't remember.
It seems the usb init script is now inside "/etc/init.d/kbd". I will try the method there next time it happens.
....
Looking at that script, there's comments which say:
# [bugzilla #46113] # we come here although heading for runlevel 5. # I'll comment out diabling hotplug for now. jw. # test -f /proc/sys/kernel/hotplug && echo /bin/true > \ /proc/sys/kernel/hotplug 2>/dev/null
(note wrap crap)
I just found this, so haven't had a hard look at this code or at bug #46113. Seems curious though.
Same as I thought. I suppose that the usb setup code has gone to the kbd init script because usb keyboards are now common; I remember seeing posts here of people having problems during start up which they could do nothing about because the keyboard was not functional yet. I wonder what "diabling" means :-? The webster seems to relate it to the devil, I hope they meant something else ;-) I think I'll create a usbreinit script from that; I suppose I'll have to remove modules in reverse order, perhaps with force. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFD2OKItTMYHG2NR9URAhxbAJ4yjjkLxaUfaDeYcJX6R/EWf9Vp7gCfa/zK BuI4Bog2TbVNyYdNwsR2tic= =LVjq -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Thursday 2006-01-26 at 10:56 -0000, David Bottrill wrote:
A colleague has been having similar problems with a different model of Epson scanner. He found that connecting the scanner directly to the PC rather through a hub fixed his problem.
It is not the scanner, but anything: the joystick also disapears. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFD2M4YtTMYHG2NR9URAiRrAJ9rrszfUAE+vpysbP60WX//halUUACgjGL/ fKWCt09KeAhpsHBDm0fXx0A= =fHQH -----END PGP SIGNATURE-----
On Thu, 2006-01-26 at 10:56 +0000, David Bottrill wrote:
Carlos E. R. said:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Thursday 2006-01-12 at 10:17 +0100, Johannes Meixner wrote:
...
Sounds familiar...
See if this rings a bell. Instead of halting/booting my system every day, I prefer to suspend it to disk. Sometimes it happens, perhaps after a month without problems, that one day the scanner (epson 1650 via usb) is no longer there. I can not list it with lsusb. Gone. The only solution seems to be to reboot - down the flush goes my uptime! ;-)
This is with SuSE 9.3. Time ago, there was "rchotplug restart" that would force the usb bus to work again, but the script has disappeared. I tried reloading usb kernel modules, but it did not work; perhaps I did it wrong.
It seems the usb init script is now inside "/etc/init.d/kbd". I will try the method there next time it happens.
A colleague has been having similar problems with a different model of Epson scanner. He found that connecting the scanner directly to the PC rather through a hub fixed his problem.
I had a problem with some devices I had connected to a non-powered USB hub. Replaced the USB hub with a powered one and all of the problems went away. The one that had the most problems was a scanner. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
Hello, On Jan 26 08:32 Ken Schneider wrote (shortened):
I had a problem with some devices I had connected to a non-powered USB hub. Replaced the USB hub with a powered one and all of the problems went away. The one that had the most problems was a scanner.
Which is described at http://portal.suse.com/sdb/en/2004/10/jsmeix_scanner-setup-92.html "USB Cable Connection and Additional USB Hubs" Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5 Mail: jsmeix@suse.de 90409 Nuernberg, Germany WWW: http://www.suse.de/
On Thu, 26 Jan 2006 08:32:04 -0500 Ken Schneider <suse-list@bout-tyme.net> wrote:
On Thu, 2006-01-26 at 10:56 +0000, David Bottrill wrote:
Carlos E. R. said:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
....
A colleague has been having similar problems with a different model of Epson scanner. He found that connecting the scanner directly to the PC rather through a hub fixed his problem.
I had a problem with some devices I had connected to a non-powered USB hub. Replaced the USB hub with a powered one and all of the problems went away. The one that had the most problems was a scanner.
I might be really reaching, but could it be the case that the problem I'm having connecting a USB scanner to my laptop (Dell Inspiron 600m) is that the USB port isn't powered? -- "This world ain't big enough for the both of us," said the big noema to the little noema.
* Carlos E. R. <robin1.listas@tiscali.es> [01-25-06 19:19]:
This is with SuSE 9.3. Time ago, there was "rchotplug restart" that would force the usb bus to work again, but the script has disappeared. I tried reloading usb kernel modules, but it did not work; perhaps I did it wrong.
Next time, try powering down the scanner and disconnecting the usb lead. Repower the scanner and (wait for completion of the power up cycle) reconnect the usb lead. I have an Epson 2400 which has reappeared using the above sequence. -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/gallery2
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Friday 2006-01-27 at 10:33 -0500, Patrick Shanahan wrote:
* Carlos E. R. <robin1.listas@tiscali.es> [01-25-06 19:19]:
This is with SuSE 9.3. Time ago, there was "rchotplug restart" that would force the usb bus to work again, but the script has disappeared. I tried reloading usb kernel modules, but it did not work; perhaps I did it wrong.
Next time, try powering down the scanner and disconnecting the usb lead. Repower the scanner and (wait for completion of the power up cycle) reconnect the usb lead.
I tried that already, no difference. Even un-powering the computer (suspend to disk) doesn't work, I have to really reboot.
I have an Epson 2400 which has reappeared using the above sequence.
It is not really a problem with the scanner, but with the usb bus itself. I tried pluggin what I had available, a joystick, and nothing: lsusb did not see it. Fortunately, it is rare: once every 20..30 days. But it means I can not get a big uptime to be proud off! ;-) - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFD2mbbtTMYHG2NR9URAlo5AJ0U/nwXXp4pexLxziK2zY3UWNUI5wCeJhGF WFuwWrV4Iw6T45nUi0GdvRQ= =dvIt -----END PGP SIGNATURE-----
On Thursday 12 January 2006 02:15, Gracia M. Littauer wrote:
I'm using suseSUSE 10. It 'sees' it but comes up with 'not configured' & epkowa says 'no active scanner for this driver. I have had no trouble using it in SUSE 9.3
I have this scanner and couldn't get working properly with 9.3 or 10, though it worked perfectly with 9.0 and 9.1. Something isn't right about the changes that were made to scanner handling, which went backwards as far as I'm concerned. By all means go over the files and resources Johannes suggests to see if you can get it working, and if you can please post your fix. If you can't get it running and it matters to you enough, though, I would try the trial version of Vuescan from www.hamrick.com and consider buying it if it works for you. It solved all my scanner problems, but you have to pay for the non-trial version. Whatever oddities are said to exist in our various USB setups that prevent the standard SuSE tools working with this scanner, Vuescan seems to be able to overcome them without difficulty. Good luck Fergus
Any ideas??
gracia@Vigor10:~> /usr/sbin/lsusb Bus 003 Device 003: ID 04b8:0112 Seiko Epson Cor p. Perfection 2450 Bus 003 Device 001: ID 0000:0000 Bus 002 Device 001: ID 0000:0000 Bus 001 Device 004: ID 05e3:0700 Genesys Logic, Inc. SIIG US2256 CompactFlash Card Reader Bus 001 Device 001: ID 0000:0000
-- Gracia...Cooleemee, NC Registered Linux user #263390 - SuSE 10 Pro My country, right or wrong. If right, to be kept right, if wrong, to be put right.
-- Fergus Wilde Chetham's Library Long Millgate Manchester M3 1SB Tel: 0161 834 7961 Fax: 0161 839 5797 http://www.chethams.org.uk
participants (8)
-
Carlos E. R. -
David Bottrill -
Fergus Wilde -
Gracia M. Littauer -
Johannes Meixner -
ken -
Ken Schneider -
Patrick Shanahan