Cannot Start Scanner - Device busy
 

Hi

I have Mustek Scanexpress 1200 UB Plus scanner and my OS is Mepis 6.0. I finally managed to get Xsane and Kooka to load and recognise my scanner. I say recognise but they see it as Mustek Bearpaw 1200 CU scanner. Now don't mind what they call it unless this is the reason for my problem.

Neither Kooka or Xsane will scan and I get he fault "Cannot Start Scanner - Device busy". Now as far as I can determine from this cryptic message either the the software is seeing he scanner already on when it isn't or the it is seeing the usb port occupied by something else.

I've looked in all my log files to see if there are any clues to what is going on but no success.

Has anyone any idea what I must do to resolve his?

Thank

grabro
:cry:

Did you ever get this to work?
I got my Mustek 600 III ep working after a bunch of messing around, and during the process, I received a lot of the same message, and it was due to incorrectly specifying the scanner's device name when trying to access it. Instead of telling me 'device not found' or something useful like that, it told me 'Device Busy'.
By using the 'scanimage -L' command as root, and a few other things, I was finally able to specify the correct device. Now, the fastest way for me to scan a basic image is like:
and if you run this command as root at the command line, and it works, then all is likely set up just fine.
One thing I DID have to do, in order to use for example GIMP to scan images, was run GIMP as root, because by default the scanner device/device node is owned by root. Rather than change the permissions, I just made a desktop link like 'kdesu gimp-command' and problem solved. You may choose togo the permissions route.
And btw, GIMP has an awesome scanner interface which works 110% great with my scanner!
For more info on my exact course of action, search LQ for posts by me, containing the words 'mustek 600 scanner' and I'm sure you'll find it easily.
SV

usb scanner - Device Busy
 

GrapefruiTgirl

Hi sorry for the delay in acknowledging your input but have been busy.

Have changed PC and upgraded OS to Mepis 6.5 but still the same problem with the scanner. I have of course been trying to resolve this as it is now the only problem I have on the PC. Incidentally this scanner worked fine when I had Suse as the OS.

I tried your advice but it did not work. I also had some other advice which I tried at the command line as user.

grabro@1[~]$ sane_debug_Mustek=255 scanimage -d gt68xx >image.pnm
scanimage: sane_start: Device busy

Now it takes about 60 seconds for it to tell me the "device Busy" so during this time I ran "dmesg | tail" in another terminal and this was the result.

[17191925.488000] ppdev0: registered pardevice
[17191925.508000] ppdev0: negotiated back to compatibility mode because user-space forgot
[17191925.508000] ppdev0: unregistered pardevice
[17193536.316000] ppdev0: registered pardevice
[17193536.316000] ppdev0: unregistered pardevice
[17193536.332000] ppdev0: registered pardevice
[17193536.332000] ppdev0: unregistered pardevice
[17193536.332000] ppdev0: registered pardevice
[17193536.356000] ppdev0: negotiated back to compatibility mode because user-space forgot
[17193536.356000] ppdev0: unregistered pardevice

Do You have any idea what this means? What on earth is "user-space forgot"!!

Thanks for your interest

grabro