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.