zlacker

[parent] [thread] 4 comments
1. kamran+(OP)[view] [source] 2023-11-27 12:03:04
Mine constantly falls into some deep sleep state where it can’t be found on the network and I have to spend ~10 minutes coaxing it out of sleep using an unknown combination of random button jabs and test prints before it can be detected by my devices again and will print.

If anyone knows how to fix this please let me know, I want to love my printer as well.

replies(3): >>ourman+w4 >>JamesS+Uv >>adinis+T63
2. ourman+w4[view] [source] 2023-11-27 12:36:16
>>kamran+(OP)
Seconded. The 4 button, one line display interface is hopeless.

I print once a never, so the only answer I remember is to power cycle the little bastard.

And then I have to reboot my pc so windows 10 will find it.

There's probably a couple services I could restart instead, but reboot is fast enough I don't care.

replies(1): >>vel0ci+YU
3. JamesS+Uv[view] [source] 2023-11-27 15:22:17
>>kamran+(OP)
Ran into the same issue. I think using ethernet instead of wifi was the solution (and maybe something with disabling ipv6? been a long time since I looked into it).
◧◩
4. vel0ci+YU[view] [source] [discussion] 2023-11-27 17:03:41
>>ourman+w4
I used to have this issue on Windows. Enabling SNMP solved it. By default it checks SNMP to see the status of the printer, so if SNMP is off it'll eventually think the whole printer is offline.
5. adinis+T63[view] [source] 2023-11-28 07:12:09
>>kamran+(OP)
Mine used to have the problem. Upgrading the firmware and using Ethernet did not fix it.

Observation: disconnecting the printer from the network avoided the un-wake-able "deep sleep" state. Re-connecting the network made it susceptible again. I suspect it's particular network traffic that causes the printer to wedge into a sleep it cannot leave; possibly a Debian box that I've since de-commissioned. The problem no longer occurs despite having the same firmware as before and being connected to the network.

[go to top]