From Bugzilla Helper:
User-Agent: Mozilla/4.76 [en] (X11; U; Linux 2.4.2-2 i686)
Description of problem:
After printer has been idle for a time a call to lpr causes this message to
appear on the screen, "Winbond Super-IO detection, now testing ports 3F0,
370, 250, 4E, 2E (etc.)... SMSC Super-IO detection, now testing ports 2F0,
370, (etc.)." These messages even overwrite any application screen which
is running. In installing 7.1 I took the server option and let the
installer decide on all configs.
I have examined lpd, lprng, etc. and can not find the source of this
message. Can not redirect to dev/null.
This only occurs after printer has been idle for a time. If you print
again just after this message the message does not repeat (until the
printer has sat idle again for a while, - have not timed it).
Is this output possibly from new lprng utility? Or where?
Message comes up whether logged in on console or other term.
Does not come up under xterm. Does come up under command line terminal.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Don't know if you can reproduce. But, to try, set up 7.1 using server
2.After booting let printer (while switched on) stand idle for some time.
3.Print using lp or lpr and msg should come up.
I have the same problem on two rh 7.1 servers. I also have
two other servers without the problem.
The first two with the problem both use /dev/lp0 (lpt1) and
are fresh installs of rh 7.1. One is SMP and the other is
a single processor. The SMP unit gets twice the Windbond
gargage on the screen as the single.
The third unit without the problem is a fresh install but
does not use /dev/lp0. (It spools for network printers with MIO cards.)
The forth unit, also without the problem, uses /dev/lp0 but is
an upgrade from Red Hat 7.0. The only time the Windbond messages pop
up is if I deliberately restart lpd ("/etc/rc.d/init.d/lpd restart").
I hope this helps,
Super-Bond and SMSC mesgs are logged by /etc/syslog in /var/log/messages.
The clutter (Super-Bond and SMSC mesgs) in question is being sent to both
/var/log/messages and /dev/console. The problem is the echo to /dev/console.
You could reproduce this if you removed/inserted the kernel parallel port driver
modules manually (using using "rmmod" and "modprove"). See output of "lsmod" for
which modules are loaded.
Also note kernel 2.4.3-12 update.
Use the 'dmesg' command to adjust the amount of kernel traffic that goes to
This annoying message has been fixed in later kernels (2.4.5 onwards).