Printer only after restart detected

Help for Current Versions of MX
When asking for help, use Quick System Info from MX Tools. It will be properly formatted using the following steps.
1. Click on Quick System Info in MX Tools
2. Right click in your post and paste.
Message
Author
bench
Posts: 9
Joined: Tue Aug 15, 2023 5:30 am

Printer only after restart detected

#1 Post by bench »

Hallo my printer is only detected, when starting the printer before the computer or when restarting the computer after printer switched on. I already had this problem with MX-21. I hoped the update to MX-23 would fix this, but did not. Any work around?

Code: Select all

System:
  Kernel: 6.1.0-11-amd64 [6.1.38-4] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/vmlinuz-6.1.0-11-amd64 root=UUID=<filter> ro quiet splash
  Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 info: xfce4-panel wm: xfwm v: 4.18.0 vt: 7
    dm: LightDM v: 1.26.0 Distro: MX-23_x64 Libretto July 31  2023 base: Debian GNU/Linux 12
    (bookworm)
Machine:
  Type: Desktop Mobo: ASRock model: H110TM-ITX R2.0 serial: <superuser required>
    UEFI-[Legacy]: American Megatrends v: P7.30 date: 01/22/2018
CPU:
  Info: model: Intel Pentium G4600 bits: 64 type: MT MCP arch: Kaby Lake level: v2 built: 2018
    process: Intel 14nm family: 6 model-id: 0x9E (158) stepping: 9 microcode: 0xF4
  Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled cache: L1: 128 KiB
    desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB L3: 3 MiB desc: 1x3 MiB
  Speed (MHz): avg: 2200 high: 3600 min/max: 800/3600 scaling: driver: intel_pstate
    governor: powersave cores: 1: 800 2: 800 3: 3600 4: 3600 bogomips: 28800
  Flags: ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
  Type: retbleed mitigation: IBRS
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: IBRS, IBPB: conditional, STIBP: conditional, RSB filling,
    PBRSB-eIBRS: Not affected
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel arch: Gen-9.5
    process: Intel 14nm built: 2016-20 ports: active: HDMI-A-2 empty: DP-1,DP-2,HDMI-A-1
    bus-ID: 00:02.0 chip-ID: 8086:5912 class-ID: 0300
  Device-2: Logitech Logitech Webcam C925e type: USB driver: snd-usb-audio,uvcvideo bus-ID: 1-2:3
    chip-ID: 046d:085b class-ID: 0102 serial: <filter>
  Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X:
    loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915 display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22") s-diag: 582mm (22.93")
  Monitor-1: HDMI-A-2 mapped: HDMI-2 model: ViewSonic XG2401 SERIES serial: <filter> built: 2017
    res: 1920x1080 hz: 60 dpi: 92 gamma: 1.2 size: 531x299mm (20.91x11.77") diag: 609mm (24")
    ratio: 16:9 modes: max: 1920x1080 min: 720x400
  API: OpenGL v: 4.6 Mesa 22.3.6 renderer: Mesa Intel HD Graphics 630 (KBL GT2)
    direct-render: Yes
Audio:
  Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: ASRock driver: snd_hda_intel
    v: kernel bus-ID: 1-2:3 bus-ID: 00:1f.3 chip-ID: 046d:085b chip-ID: 8086:a170 class-ID: 0102
    class-ID: 0403 serial: <filter>
  Device-2: Logitech Logitech Webcam C925e type: USB driver: snd-usb-audio,uvcvideo
  API: ALSA v: k6.1.0-11-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 0.3.65 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: kernel port: N/A bus-ID: 00:1f.6
    chip-ID: 8086:15b8 class-ID: 0200
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:
  Local Storage: total: 931.51 GiB used: 232.97 GiB (25.0%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Crucial model: CT1000MX500SSD1 size: 931.51 GiB block-size:
    physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 032 scheme: MBR
Partition:
  ID-1: / raw-size: 930.5 GiB size: 914.82 GiB (98.32%) used: 232.78 GiB (25.4%) fs: ext4
    dev: /dev/dm-0 maj-min: 253:0 mapped: root.fsm
  ID-2: /boot raw-size: 1024 MiB size: 973.4 MiB (95.06%) used: 190.8 MiB (19.6%) fs: ext4
    dev: /dev/sda1 maj-min: 8:1
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: file size: 4 GiB used: 0 KiB (0.0%) priority: -2 file: /swap/swap
Sensors:
  System Temperatures: cpu: 51.0 C pch: 54.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Repos:
  Packages: pm: dpkg pkgs: 2396 libs: 1296 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
    pkgs: 0 pm: flatpak pkgs: 0
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
    1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
    2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/librewolf.list
    1: deb [arch=amd64] http://deb.librewolf.net bullseye main
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb http://ftp.halifax.rwth-aachen.de/mxlinux/packages/mx/repo/ bookworm main non-free
  Active apt repos in: /etc/apt/sources.list.d/resilio-sync.list
    1: deb http://linux-packages.resilio.com/resilio-sync/deb resilio-sync non-free
Info:
  Processes: 234 Uptime: 31m wakeups: 1 Memory: 15.33 GiB used: 5.39 GiB (35.2%) Init: SysVinit
  v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12 Client: shell wrapper
  v: 5.2.15-release inxi: 3.3.26
Boot Mode: BIOS (legacy, CSM, MBR)
You do not have the required permissions to view the files attached to this post.
Last edited by bench on Tue Aug 15, 2023 6:59 am, edited 2 times in total.

User avatar
Eadwine Rose
Administrator
Posts: 14462
Joined: Wed Jul 12, 2006 2:10 am

Re: Printer only after restart detected

#2 Post by Eadwine Rose »

Oh I had this as well on 21, haven't tried on 23 yet. I have gotten in the habit of just starting the printer (HP) before the computer, always.
MX-23.6_x64 July 31 2023 * 6.1.0-34amd64 ext4 Xfce 4.20.0 * 8-core AMD Ryzen 7 2700
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 535.216.01 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 870EVO * Samsung S24D330 & P2250 * HP Envy 5030

User avatar
CharlesV
Global Moderator
Posts: 7089
Joined: Sun Jul 07, 2019 5:11 pm

Re: Printer only after restart detected

#3 Post by CharlesV »

@bench Welcome in!

What model of printer and what connection type?
*QSI = Quick System Info from menu (Copy for Forum)
*MXPI = MX Package Installer
*Please check the solved checkbox on the post that solved it.
*Linux -This is the way!

User avatar
gimcrack
Posts: 288
Joined: Fri Dec 02, 2011 5:17 pm

Re: Printer only after restart detected

#4 Post by gimcrack »

My works just fine. Samsung Xpress M2070FW USB connection.

Try looking at logs for debugging and troubleshooter guide.

https://wiki.ubuntu.com/DebuggingPrintingProblems

User avatar
j2mcgreg
Global Moderator
Posts: 6606
Joined: Tue Oct 23, 2007 12:04 pm

Re: Printer only after restart detected

#5 Post by j2mcgreg »

CharlesV wrote: Tue Aug 15, 2023 10:03 am @bench Welcome in!

What model of printer and what connection type?
It's identified in the attachment as an Epson ET 2850. It's their latest Eco tank model and it is advertised as being wireless. Assuming he is using a wireless connection, I think that he should turn the printer on and leave it on 24/7 (if he can). The constant wireless polling by the printer should be enough for it to be discovered at boot.
HP 15; ryzen 3 5300U APU; 500 Gb SSD; 8GB ram
HP 17; ryzen 3 3200; 500 GB SSD; 12 GB ram
Idea Center 3; 12 gen i5; 256 GB ssd;

In Linux, newer isn't always better. The best solution is the one that works.

User avatar
CharlesV
Global Moderator
Posts: 7089
Joined: Sun Jul 07, 2019 5:11 pm

Re: Printer only after restart detected

#6 Post by CharlesV »

j2mcgreg wrote: Tue Aug 15, 2023 10:45 am

It's identified in the attachment as an Epson ET 2850. It's their latest Eco tank model and it is advertised as being wireless. Assuming he is using a wireless connection, I think that he should turn the printer on and leave it on 24/7 (if he can). The constant wireless polling by the printer should be enough for it to be discovered at boot.
Thanks! I totally missed that! ( I am going to HAVE to have more coffee before I post anything ;-/ )

Yes, I would agree with that if he is using it as wireless. I have not seen any issues with the Eco Tank's, once the printer is added to cups. (But I also *always* set them up on a static ip too! )
*QSI = Quick System Info from menu (Copy for Forum)
*MXPI = MX Package Installer
*Please check the solved checkbox on the post that solved it.
*Linux -This is the way!

bench
Posts: 9
Joined: Tue Aug 15, 2023 5:30 am

Re: Printer only after restart detected

#7 Post by bench »

Hallo, long term MX-user (2019), finally registered in the forum.

I am using Epson ET 2850 with USB connection. Is there a script to reload anything, I don't need to restart the whole system?

User avatar
Eadwine Rose
Administrator
Posts: 14462
Joined: Wed Jul 12, 2006 2:10 am

Re: Printer only after restart detected

#8 Post by Eadwine Rose »

@bench I don't think you meant to mark this thread as solved, did you?


Unmarked the thread.
MX-23.6_x64 July 31 2023 * 6.1.0-34amd64 ext4 Xfce 4.20.0 * 8-core AMD Ryzen 7 2700
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 535.216.01 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 870EVO * Samsung S24D330 & P2250 * HP Envy 5030

User avatar
l0dr3
Posts: 463
Joined: Wed Jun 28, 2023 11:06 am

Re: Printer only after restart detected

#9 Post by l0dr3 »

bench wrote: Tue Aug 15, 2023 5:39 am Hallo my printer is only detected, when starting the printer before the computer or when restarting the computer after printer switched on. I already had this problem with MX-21. I hoped the update to MX-23 would fix this, but did not. Any work around?
Hi, your attachment shows that you are trying to use the 'generic' epson ESC driver.

This is, afaik, and as i experienced today with my 'Epson WF-7220' device, no longer supported in MX23/BOOKWORM by cups v2.4.2.

My recommendation: try to use 'ipp/ipps' printing with the default-provided 'driverless' or 'IPP Everywhere' driver ...

greetz

l0dr3
Last edited by l0dr3 on Tue Aug 15, 2023 3:24 pm, edited 2 times in total.

User avatar
Eadwine Rose
Administrator
Posts: 14462
Joined: Wed Jul 12, 2006 2:10 am

Re: Printer only after restart detected

#10 Post by Eadwine Rose »

@l0dr3 Where is your reply? It went missing ;)
MX-23.6_x64 July 31 2023 * 6.1.0-34amd64 ext4 Xfce 4.20.0 * 8-core AMD Ryzen 7 2700
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 535.216.01 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 870EVO * Samsung S24D330 & P2250 * HP Envy 5030

Post Reply

Return to “MX Help”