Brother USB Scanner is recognised but not working

[Barneyonfire]

The other day I updated Ubuntu and when I tried to scan something, it would not work. Both gscan2pdf an Xsane brought out this:

scanimage: open of device brother2:bus4;dev1 failed: Error during device I/O

I spent some hours googling and looking for help, but nothing got my Scanner working again.
What I did:
- I reinstalled all packages of sane and the brother driver
- I tried another USB-Port
- I tried it with the Live-CD of Ubuntu 8.10 (32 Bit)
- with Windows Xp Pro the scanner works fine
- stopping ehci

Further Information:
- Scanner is a Brother MFC 465 CN connected via USB 2.0 cabel
- I am Using Ubuntu 8.10 32 Bit

It seems that one of the updates caused all that trouble, but using the (older) Livecd didn't work ether, so I suppose it is a Problem that is not yet fixed. While googling I found some other guys with the same problem, but none of their workarounds could help, so I would be happy, if this could be fixed in 9.04 :)

As requested:
pascal@pascal-desktop:~$ uname -a
Linux pascal-desktop 2.6.27-11-generic #1 SMP Thu Jan 29 19:24:39 UTC 2009 i686 GNU/Linux
Added attachments.

WORKAROUND:
use 'sudo xsane'

[Michele Mangili (mangilimic)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it without more information.

Please include the following additional information, if you have not already done so (pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" after a fresh boot and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.

For your reference, the full description of procedures for kernel-related bug reports is available at https://wiki.ubuntu.com/KernelTeamBugPolicies Thanks in advance!

[Barneyonfire (ikearegal)]

Thank you so far for your quick reaction!
Hope this helps.

[Michele Mangili (mangilimic)]

Hello!

I apologize for the inconvenience but I forgot to ask you the last log (which is probably the most useful!):
please run command "lsusb > lsusb.log" and attach the resulting file "lsusb.log" to this bug report.

However I found that your problem has already been reported to Brother (see this page : http://solutions.brother.com/linux/en_us/faq_scn.html#101 ). Have you already tried to run "sudo xsane"?

Thank you!

[Barneyonfire (ikearegal)]

He!
In the attachment is the log file you need. I also tried 'sudo xsane' and that did the trick! Thank you very much for that hint!
But when I startet Xsane there was a warning about how dangerous this is and so on, so this can't be a long term solution. At least we now know where to look :)
I knew the Brother link you posted, but I did not see a relation between this error and mine.
I hopse this helps you fixing the problem. If any other issues occur, don't hesitate to contact me. I am happy, if I could help.

[Barneyonfire (ikearegal)]

I forgot to make this clear: The workaround by Brother didn't help, because the suggested changes were already done.
That is what it looked like right from the start.
    # USB devices (usbfs replacement)
    SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", MODE="0666"
    SUBSYSTEM=="usb_device", MODE="0666"

[Michele Mangili (mangilimic)]

Hi!

I'm going to close this report since it is a duplicate of bug #217571 . To solve your issue you can try to follow the instructions posted here: http://solutions.brother.com/linux/sol/printer/linux/linux_faq.html#9 , additionally any further discussion regarding the bug should occur in the other report. Anyway I think that this issue doesn't belong to Ubuntu developers, but it should be handled by Brother. In fact the driver provided for your scanner are not released under the GPL licence (as you can see from bug #72321), so it is almost impossible for Ubuntu developers to solve this kind of problems!

Feel free to continue to report any other bugs you may find.

[Michele Mangili (mangilimic)]

Barneyonfire wrote:
> I forgot to make this clear: The workaround by Brother didn't help, because the suggested changes were already done.
> That is what it looked like right from the start.
> # USB devices (usbfs replacement)
> SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", MODE="0666"
> SUBSYSTEM=="usb_device", MODE="0666"
>

Sorry! I haven't read this reply before posting my previous comment! I
read from Brother website that this workaround is for Ubuntu 8.04 , not
Intrepid.

Could you please write a comment in bug #217571 , and make clear that
this workaround doesn't solve the problem in Ubuntu 8.10 ?

In my opinion, the best choice is to contact Brother support and point
out the problem.

Thank you!

[penalvch (penalvch)]

Barneyonfire, thank you for reporting this and helping make Ubuntu better.

As per https://wiki.ubuntu.com/Releases your release is EOL.

If you have an issue in a supported release (ex. 16.04) please file a new report, and feel free to subscribe me to it.