[Bug 228795] New: YaST causes printer to become unresponsive
https://bugzilla.novell.com/show_bug.cgi?id=228795 Summary: YaST causes printer to become unresponsive Product: openSUSE 10.2 Version: Final Platform: x86 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Printing AssignedTo: jsmeix@novell.com ReportedBy: kq8z67r6309fo9001@sneakemail.com QAContact: jsmeix@novell.com With an HP LaserJet 6L (a parallel port printer): 1. Print something successfully 2. Start YaST printer module 3. Printing is no longer possible Subsequent to starting the yast printer module, jobs are queued but apparently not sent to the printer, which sits with the "ready" indicator lit but does not print. The following have no effect: 1. Exiting yast or reconfiguring the printer 2. /etc/init.d/cups restart 3. /etc/init.d/cups stop; rmmod lp parport_pc parport; modprobe lp; /etc/init.d/cups start Rebooting, however, works fine: anything that was queued after starting yast then prints. No idea if this is a hwinfo, yast, or kernel problem. Previous 2.6 kernels have caused trouble with parallel port printers (including the one shipped with suse 10.0, as I recall); this may be caused by a similar problem. A side-effect of this is that it is impossible in all circumstances to print test pages from yast, making the troubleshooting of PPD files, and printer configuration in general, very tedious. I do not know if this affects any other printers, parallel-port or otherwise, as we're taking things very slowly with 10.2 and thus have it only on one machine at present. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=228795 jsmeix@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |DUPLICATE ------- Comment #1 from jsmeix@novell.com 2006-12-15 02:59 MST ------- This does not and did never happen for any of my systems. I assume it is not caused directly by YaST. Regarding the parallel port, see bug #185135. See also the other bug reports which are mentioned there. Something is fishy with the parallel port stuff in the kernels since Suse Linux 10.0, see http://lists.suse.com/archive/suse-linux-e/2005-Nov/1206.html The current workaround is to experiment with various BIOS settings and explicite additional settings in /etc/modprobe.conf to find a setup, which actually works in a particular problematic case. According to what you decribed it matches to the known parallel port problems and therefore I close this bug as duplicate of bug #185135. *** This bug has been marked as a duplicate of bug 185135 *** -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=228795 ------- Comment #2 from kq8z67r6309fo9001@sneakemail.com 2006-12-16 22:09 MST ------- I do not believe this is a duplicate of #185135, as it describes problems with initial autodetection of the printer, but in this case the printer is properly detected and functions until yast2 printer is run. This may be due to yast unloading and reloading the lp/parport_pc/parport modules, I cannot say as I am not sufficiently familiar with yast. If that is the case, then this is probably related to #185135, but is not a duplicate of it. Moreover, the remedies suggested in the other bug are not effective in this case. No combination of bios settings or modprobe.conf alteration cause the printer to survive running yast. One additional piece of information is that the following appears in /var/log/messages if the port is in ECP mode after running yast: Dec 16 22:05:04 hostname kernel: DMA write timed out Dec 16 22:05:44 hostname last message repeated 4 times Dec 16 22:06:54 hostname last message repeated 7 times This seems to support the idea that it's a parport_pc.ko bug being triggered by yast reloading the module. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=228795 ------- Comment #3 from jsmeix@novell.com 2006-12-18 06:18 MST ------- Because of "DMA write timed out" it is a duplicate of the various known parport problems for which I choose bug #185135 as representative because it is a good summary and it is is public accessible (actually the "DMA write timed out" is bug #116655 which might not be public accessible). In particular regarding DMA problems with the parallel port see http://lists.suse.com/archive/suse-linux-e/2005-Nov/1206.html (see what I wrote in comment #1) which is public accessible and which tells about the reason and not to use the ECP mode. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
participants (1)
-
bugzilla_noreply＠novell.com