-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hp scanner M148dw is detected after several minutes if not after reboot #108
Comments
Hi, Sorry for long delay with reply. Is this issue still relevant? |
HI, |
I am also using a HP LaserJet Pro M148dw, so I thought I'd add my two cents. My scanner HP LaserJet Pro M148dw
After reboot my scanner is almost instantly recognized (it takes a few seconds):
works fine. So does simple-scan. |
Hp scanner M148dw and Mint 20 64 bits
I have to wait several minutes after turning on the HP scanner for the scanner to be detected .
After a fresh install of Mint 20 the scanner was not detected at all .
Following suggestions of this topic https://forums.linuxmint.com/viewtopic.php?f=51&t=329760&sid=fbcc443cbc717890a971282644d7cb38&start=20
I did the following
After that, the scanner was discovered but the device found do not allows to scan with Simple scan.
I have to wait several minutes for finally having other devices found and pick the only one that works.
Command scanimage -L at first list only one device :
While after some minutes :
Only the one named "eSCL HP LaserjetPro M 148-m149" worked
Command $ airscan-discover do not return any device for about three minutes , then...
Following a suggestion I did this :
Edit /etc/sane.d/dll.conf and comment out all lines in the file.
Edit /etc/sane.d/dll.d/hplip and comment out hpaio.
After a reboot , it works fine, the scanner is seen immediately as "eSCL HP LaserjetPro M 148-m149" and woks correctly.
But if I turn off the scanner and then I turn it on again, the scanner is not seen anymore by the system, scanimage -L do not return any scanner.
I have to wait several minutes, sometimes 3, other times more than 5 to get the scanner detected again.
Update:
I found a turn around, adding manually the scanner to airscan.conf in /etc/sane.d
The text was updated successfully, but these errors were encountered: