Your message dated Tue, 2 Oct 2012 18:26:19 -0700 with message-id <[email protected]> and subject line Re: With last kernels, terminal/console processing getting worth. has caused the Debian Bug report #575660, regarding With last kernels, terminal/console processing getting worse to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 575660: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=575660 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: linux-source-2.6.32 Version: 2.6.32-9 Severity: normal I am making my own kernels out of Debian's linux-source. I upgraded the source from 32-5 to 32-9. I have added a few more kernel modules with 32-9. I believe the config diff is not relevant for this report. 1) With 32-9, when tty1 shows the login prompt after boot, I can't see the characters that I type. I believe they are not processed as expected. This doesn't happen with 32-5. 2) I am using /etc/console-tools/config to get the terminal into BLANK_DPMS=powerdown. With both 32-5 and 32-9, pressing anything on the keyboard doesn't seem to get the terminal out of BLANK_DPMS=powerdown mode. In the past it did work as expected. I can not tell from which kernel version the problem is apparent. 3) Also with both 32-5 and 32-9, the shutdown command doesn't take the screen out of BLANK_DPMS=powerdown mode. So nothing is displayed on the screen when the system goes down. It was not like that in the past. I can't tell from which kernel version the problem emerged. _________________________________________________________________ Hotmail: Powerful Free email with security by Microsoft. https://signup.live.com/signup.aspx?id=60969
--- End Message ---
--- Begin Message ---Regid Ichira wrote: >> In 2010, Regid Ichira wrote: >>> By connecting over the network one can see that the i8042 interrupt >>> counter does not go up. [...] > For some time now, the machine has problems with the display. Could > be a bios setting issue, or some sort of a software problem. More > likely there is one, or more, hardware failures. I am reluctened to > make any tests or changes. No problem. Closing for now, but if you get more information I'd be happy to look into this one again. Regards, Jonathan
--- End Message ---
