Is it time to retire the scanner ?

[Warren Block]

On Sat, 22 Oct 2016, Manish Jain wrote:

> (ada0:ata0:0:1:0): READ_DMA48. ACB: 25 00 df ea ff 40 33 00 00 00 01 00
> (ada0:ata0:0:1:0): CAM status: Command timeout
> (ada0:ata0:0:1:0): Retrying command
>
> I have no idea what the above means, but it does suggest to me that the
> scanner cannot be blamed if it is still powered off.
>
> The newest things in the system are the PSU, cabinet, RAM, and DVD drive
> - all swapped just yesterday. Could the DVD drive be the source ?

Possibly, they do return noisy errors when no media is loaded.  There 
was talk of silencing some of those lately.

> Returning to the scanner, I have been running 'scanimage -L' as root.
> Between 0 and 4 times in succession, the command reports normal output :
>
> <output>
> /root <<: scanimage -L
> device `pixma:04A9176C_43130B' is a CANON Canon PIXMA MG2400 Series
> multi-function peripheral
> </output
>
> And then suddenly, it goes dead
> /root <<: scanimage -L
> #does not return now

This might be correctable with a USB quirk, or it might need 
modification of the FreeBSD USB code.  Best to ask on the 
freebsd-usb at FreeBSD.org mailing list.

>> If the scanner works on XP, the hardware is fine.  This is more likely a
>> problem with USB and multifunction devices on FreeBSD.  It could be
>> solvable.
>
> Thanks for lending me hope. I am really struggling - just invested
> something like USD 600 on a total system upgrade to make this superslick
> machine. But it's all turning to ashes if the hardware starts going
> bonkers already.
>
> Would you suggest I wait a while for some further proof to accumulate;
> or I should try making a fresh install of FreeBSD 10.2/11 (my current
> system 10.3).

Post on the USB mailing list.  They will probably ask for usbconfig 
output.

Personally, I avoid multifunction devices.  My Epson 1640SU scanner is 
old and large but worked fine on 10-STABLE (and long before) and 
continues to work in 12-CURRENT without any changes.  It's noticeably 
faster than some new scanners.

> Unrelated to this, there is a bug in 10.3 amd64 install - most of the
> times I have set up 10.3, the installer forgets to put the boot code in
> the MBR. So immediately after install, I have to run a live shell and
> run boot0cfg to get the boot code there.

This should be a separate thread.