Exploring CPUs, motherboards, overclocking, building your own PC, case mods, PC brands, handhelds, peripherals of all types, DVDs, CD burners, hardware-specific software, device drivers, and anything else related to hardware.
The The Restaurant at the Edge of the Universe, previously known as The Water Cooler, is a place to post stuff that has absolutely nothing at all to do with computers, broadband, Scot's Newsletter, or anything that's "supposed" to be here.
I read all that and still don't understand it. REFInd found and booted my newly restored (from the original no longer connected drive) Debian system on a brand new drive even though there was no entry in ESP as that was fresh from a new Win 10 install. If it was finding it via NVRAM entries, why didn't it find the other 3 Linux systems that existed as multiboot before I changed the system drive? 🤔
Okay, there appears to be nothing wrong with the scanner portion of the printer. I decided to start from scratch on my backup laptop, which I don't use too often and which usually doesn't have a printer connected. The system auto-configured the printer when it was detected and I decided to see what that got me. Scanimage -L found the scanner, and when I scanned a document from CLI I was able to do six(!) consecutive scans without an issue. I haven't been able to get more than two with the printer connected to the main laptop, and that was rare as it was usually only one.
When I have a few minutes I'm going to delete all the printer/scanner definitions from my main laptop and see if the process that worked on the backup laptop gives the same results on the main laptop. I did see something briefly when I was searching for info on the error message about certain motherboards having some difficulty with something to do with the error message, but I can't remember any details unfortunately. I'll be interested to see if I can get a working scan setup on the main laptop.
It's some progress anyway. Thanks for your input, Eric.