http://bugzilla.opensuse.org/show_bug.cgi?id=916781 Johannes Meixner changed: What |Removed |Added ---------------------------------------------------------------------------- Component|AutoYaST |Basesystem Found By|--- |Community User Assignee|jsmeix@suse.com |bnc-team-screening@forge.pr | |ovo.novell.com Summary|Cannot integrate HP |"Read-only file system" |LaserJet 5MP on Direct |while printing to HP |Connection via Yast2 |LaserJet 5MP --- Comment #1 from Johannes Meixner --- "Read-only file system" issues are no actual printing issues. The printing system requires a normal usable (file)system. Therefore I am the wrong assignee here. Only a blind guess: Do you perhaps use btrfs as filesystem and did you perhaps not boot your normal system but insteda you booted from a btrfs snapshot? As far as I know in this case the filesystem is read-only and you have to do some manual steps to get from the booted snapshot to a normal usable system again. But I am not at all an expert here, therefore only a guess. FYI: Regarding the parallel port: Nowadays printing via the parallel port does no longer work out of the box which means you have to do some manual setup to make it work. Basically as root "modprobe lp" should be enough to make printing via the parallel port working again, see "Parallel port printers do no longer work out of the box" at https://en.opensuse.org/Archive:Printing_News -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=916781 Johannes Meixner changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lee4home@btinternet.com Flags| |needinfo?(lee4home@btintern | |et.com) --- Comment #3 from Johannes Meixner --- Anthony Lee, Do you use btrfs as filesystem and did you boot from a btrfs snapshot? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=916781 --- Comment #5 from Anthony Lee --- Created attachment 622476 --> http://bugzilla.opensuse.org/attachment.cgi?id=622476&action=edit Snapper information -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=916781 --- Comment #14 from Johannes Meixner --- The "Bad Driver Information File '/usr/share/cups/drv/sample.drv'" error message in your /var/log/cups/error_log has nothing to do with whether or not printing via parallel port works for your HP LaserJet 5MP. That error message comes from cups-driverd that is run by the cupsd e.g. when lpinfo -m" is run to list all available printer drivers (PPDs) and then cups-driverd complains about some issues but cups-driverd is not involved when something is actually printed. In short: You can ignore messages from cups-driverd here. In general a single line from /var/log/cups/error_log is basically meaningless for me because I need more context to have at least a chance to help, see https://en.opensuse.org/SDB:How_to_Report_a_Printing_Issue In particular I need the whole CUPS debug messages for exactly one single failed print job. Regarding basic tests whether or not the printer is accessible via the parallel port see https://en.opensuse.org/SDB:Installing_a_Printer When you run as root echo -en "\rHello\r\f" >/dev/lp0 does your HP LaserJet 5MP print one sheet with the word Hello on it? If not, when you run as root rmmod lp rmmod ppdev rmmod parport_pc rmmod parport modprobe parport modprobe parport_pc modprobe ppdev modprobe lp echo -en "\rHello\r\f" >/dev/lp0 does it now print one sheet with the word Hello on it? If not, when you run as root rmmod lp rmmod ppdev rmmod parport_pc rmmod parport rm /dev/lp* systemd-tmpfiles --create /usr/lib/tmpfiles.d/parallel-printer.conf modprobe parport modprobe parport_pc modprobe ppdev modprobe lp echo -en "\rHello\r\f" >/dev/lp0 does it now print one sheet with the word Hello on it? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=916781 --- Comment #17 from Anthony Lee --- (In reply to Arvin Schnell from comment #15)

So the "filesystem read-only" issue is solved?

I guess so. Many thanks. However, I still have the printer problem. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=916781 --- Comment #19 from Anthony Lee --- This dammed system seems to have lost my attempt to respond earlier. Try again: vivaldi:/home/wendy # lpinfo -v network ipp network ipps network https network http network lpd network socket network smb Other responses interspersed, below: (In reply to Johannes Meixner from comment #14)

The "Bad Driver Information File '/usr/share/cups/drv/sample.drv'" error message in your /var/log/cups/error_log has nothing to do with whether or not printing via parallel port works for your HP LaserJet 5MP.

That error message comes from cups-driverd that is run by the cupsd e.g. when lpinfo -m" is run to list all available printer drivers (PPDs) and then cups-driverd complains about some issues but cups-driverd is not involved when something is actually printed.

In short: You can ignore messages from cups-driverd here.

In general a single line from /var/log/cups/error_log is basically meaningless for me because I need more context to have at least a chance to help, see https://en.opensuse.org/SDB:How_to_Report_a_Printing_Issue In particular I need the whole CUPS debug messages for exactly one single failed print job.

Regarding basic tests whether or not the printer is accessible via the parallel port see https://en.opensuse.org/SDB:Installing_a_Printer

When you run as root

echo -en "\rHello\r\f" >/dev/lp0

does your HP LaserJet 5MP print one sheet with the word Hello on it?

vivaldi:/home/wendy # echo -en "\rHello\r\f" >/dev/lp0 bash: /dev/lp0: Device or resource busy No printing!

If not, when you run as root

rmmod lp rmmod ppdev rmmod parport_pc rmmod parport modprobe parport modprobe parport_pc modprobe ppdev modprobe lp echo -en "\rHello\r\f" >/dev/lp0

does it now print one sheet with the word Hello on it?

vivaldi:/home/wendy # rmmod lp rmmod: ERROR: Module lp is in use vivaldi:/home/wendy # rmmod ppdev vivaldi:/home/wendy # rmmod parport_pc rmmod: ERROR: Module parport_pc is in use vivaldi:/home/wendy # rmmod parport rmmod: ERROR: Module parport is in use by: lp parport_pc vivaldi:/home/wendy # modprobe parport vivaldi:/home/wendy # modprobe parport_pc vivaldi:/home/wendy # modprobe ppdev vivaldi:/home/wendy # modprobe lp vivaldi:/home/wendy # echo -en "\rHello\r\f" >/dev/lp0 bash: /dev/lp0: Device or resource busy No printing!

If not, when you run as root

rmmod lp rmmod ppdev rmmod parport_pc rmmod parport rm /dev/lp* systemd-tmpfiles --create /usr/lib/tmpfiles.d/parallel-printer.conf modprobe parport modprobe parport_pc modprobe ppdev modprobe lp echo -en "\rHello\r\f" >/dev/lp0

does it now print one sheet with the word Hello on it?

vivaldi:/home/wendy # rmmod lp rmmod: ERROR: Module lp is in use vivaldi:/home/wendy # rmmod ppdev vivaldi:/home/wendy # rmmod parport_pc rmmod: ERROR: Module parport_pc is in use vivaldi:/home/wendy # rmmod parport rmmod: ERROR: Module parport is in use by: lp parport_pc vivaldi:/home/wendy # rm /dev/lp* vivaldi:/home/wendy # systemd-tmpfiles --create /usr/lib/tmpfiles.d/parallel-printer.conf vivaldi:/home/wendy # modprobe parport vivaldi:/home/wendy # modprobe parport_pc vivaldi:/home/wendy # modprobe ppdev vivaldi:/home/wendy # modprobe lp vivaldi:/home/wendy # echo -en "\rHello\r\f" >/dev/lp0 bash: /dev/lp0: Device or resource busy And no printing! I have also attached a /var/log/cups/error_log file produced as a short debug while attempting to print a short textfile to hplaserjet5mp from KWrite. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=916781 --- Comment #21 from Johannes Meixner --- In your error_log_1print.txt in attachment#622879 there is: ------------------------------------------------------------------------- $ grep PID error_log_1print.txt I [11/Feb/2015:17:45:10 +0000] [Job 9] Started filter /usr/lib/cups/filter/pdftops (PID 3304) I [11/Feb/2015:17:45:10 +0000] [Job 9] Started backend /usr/lib/cups/backend/parallel (PID 3305) D [11/Feb/2015:17:45:10 +0000] [Job 9] Started filter pdftops (PID 3306) D [11/Feb/2015:17:45:10 +0000] [Job 9] Started filter pstops (PID 3307) D [11/Feb/2015:17:45:11 +0000] [Job 9] PID 3306 (pdftops) exited with no errors. ------------------------------------------------------------------------- Only one preocess finished. The other ones, in particular /usr/lib/cups/backend/parallel seem to just hang because there are no error messages. I guess /usr/lib/cups/backend/parallel endlessly hangs waiting to connect to the printer via the parallel port but that does somehow not work. I guess while /usr/lib/cups/backend/parallel endlessly hangs there is "/dev/lp0: Device or resource busy". Anthony Lee, ar root run cancel -a to stop and remove all pending/active print jobs, then reboot your system and retry the various echo -en "\rHello\r\f" >/dev/lp0 tests to directly access your printer. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=916781 --- Comment #23 from Anthony Lee --- (In reply to Johannes Meixner from comment #21)

In your error_log_1print.txt in attachment#622879 [details] there is: ------------------------------------------------------------------------- $ grep PID error_log_1print.txt

I [11/Feb/2015:17:45:10 +0000] [Job 9] Started filter /usr/lib/cups/filter/pdftops (PID 3304) I [11/Feb/2015:17:45:10 +0000] [Job 9] Started backend /usr/lib/cups/backend/parallel (PID 3305) D [11/Feb/2015:17:45:10 +0000] [Job 9] Started filter pdftops (PID 3306) D [11/Feb/2015:17:45:10 +0000] [Job 9] Started filter pstops (PID 3307) D [11/Feb/2015:17:45:11 +0000] [Job 9] PID 3306 (pdftops) exited with no errors. -------------------------------------------------------------------------

Only one preocess finished. The other ones, in particular /usr/lib/cups/backend/parallel seem to just hang because there are no error messages.

I guess /usr/lib/cups/backend/parallel endlessly hangs waiting to connect to the printer via the parallel port but that does somehow not work.

I guess while /usr/lib/cups/backend/parallel endlessly hangs there is "/dev/lp0: Device or resource busy".

Anthony Lee, ar root run

cancel -a

to stop and remove all pending/active print jobs, then reboot your system and retry the various echo -en "\rHello\r\f" >/dev/lp0 tests to directly access your printer.

I have to say I hate this feedback system. I ran a load of your scripts (which failed to make the printer print), recording results etc, then performed yast2 => Hardware Information, and extracted Printer stuff from file (now attached: evidence that printer is physically and logically attached at some level), but the attachment process blew away all my previous results. I'll try and copy them here: vivaldi:/home/wendy # echo -en "\rHello\r\f" >/dev/lp0 Long wait, nothing happens. Power printer down, then up, and try again: ^C vivaldi:/home/wendy # echo -en "\rHello\r\f" >/dev/lp0 Same again. ^C vivaldi:/home/wendy # rmmod lp vivaldi:/home/wendy # rmmod ppdev vivaldi:/home/wendy # rmmod parport_pc vivaldi:/home/wendy # rmmod parport vivaldi:/home/wendy # modprobe parport_pc vivaldi:/home/wendy # modprobe parport vivaldi:/home/wendy # modprobe parport_pc vivaldi:/home/wendy # modprobe ppdev vivaldi:/home/wendy # modprobe lp vivaldi:/home/wendy # echo -en "\rHello\r\f" >/dev/lp0 Same again. ^C vivaldi:/home/wendy # rmmod lp vivaldi:/home/wendy # rmmod ppdev vivaldi:/home/wendy # rmmod parport_pc vivaldi:/home/wendy # rmmod parport vivaldi:/home/wendy # rm /dev/lp* vivaldi:/home/wendy # systemd-tmpfiles --create /usr/lib/tmpfiles.d/parallel-printer.conf vivaldi:/home/wendy # modprobe parport vivaldi:/home/wendy # modprobe parport_pc vivaldi:/home/wendy # modprobe ppdev vivaldi:/home/wendy # modprobe lp vivaldi:/home/wendy # echo -en "\rHello\r\f" >/dev/lp0 Same again. Sorry it's all taking so long. Please remember I'm just a guy who is trying to use this system. My LaserJet 5MP is in good condition, and gives a sharp clean print, even if it is a little slow, so I am not planning to junk it. Furthermore, it has always worked immediately from install by yast2, so I am no expert in this area --- and do need help. My previous SuSE install was 12.3, and before that 11.2 (I think), using the same physical hardware and daughterboard, and there was never any problem. I guess if you are partitioning off some (parallel) printers during installation, SuSE needs to make sure you have a foolproof way of bringing those printers in where necessary. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=916781 --- Comment #24 from Anthony Lee --- Hi folks out there: I'm still in a position where I have a parallel (Centronics-interfaced) HP LaserJet 5MP that worked fine with earlier SuSE distributions (and still seems to work fine in broad terms), but does not work with SuSE 13.2. I understand that parallel printers are now treated separately, and have loaded the Parallel Printer Support Package. So far, none of this has worked. Come on chaps. You deliberately changed SuSE to separate off parallel printers. So what do I have to do to get mine working again? -- You are receiving this mail because: You are on the CC list for the bug.