Re: DO NOT UPGRADE UNSTABLE: Terminal text stops functioning
I wrote: The bug is most likely caused by initscripts, sysvinit or sysv-rc. If you have upgraded you may wish to downgrade/wait for a fix before rebooting, especially if your computer doesn't automatically boot into X. I have confirmed that downgrading to initscripts_2.85-4.1_all.deb sysv-rc_2.85-4.1_all.deb and sysvinit_2.85-4.1_i386.deb will resolve the lack of terminal output. I am submitting a bug report for the initscripts package, soon to appear here: http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=initscripts Regards, Adam
Re: DO NOT UPGRADE UNSTABLE: Terminal text stops functioning
On Tue, Jul 22, 2003 at 06:14:01PM +1200, Adam Warner wrote: I wrote: The bug is most likely caused by initscripts, sysvinit or sysv-rc. If you have upgraded you may wish to downgrade/wait for a fix before rebooting, especially if your computer doesn't automatically boot into X. I have confirmed that downgrading to initscripts_2.85-4.1_all.deb sysv-rc_2.85-4.1_all.deb and sysvinit_2.85-4.1_i386.deb will resolve the lack of terminal output. I am submitting a bug report for the initscripts package, soon to appear here: http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=initscripts FWIW, I have version 2.85-5 of initscripts, sysvinit, and sysv-rc installed and am not having any problems re. terminal output. Geordie.
Re: DO NOT UPGRADE UNSTABLE: Terminal text stops functioning
Hi Geordie Birch, On Tue, Jul 22, 2003 at 06:14:01PM +1200, Adam Warner wrote: I wrote: The bug is most likely caused by initscripts, sysvinit or sysv-rc. If you have upgraded you may wish to downgrade/wait for a fix before rebooting, especially if your computer doesn't automatically boot into X. I have confirmed that downgrading to initscripts_2.85-4.1_all.deb sysv-rc_2.85-4.1_all.deb and sysvinit_2.85-4.1_i386.deb will resolve the lack of terminal output. I am submitting a bug report for the initscripts package, soon to appear here: http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=initscripts FWIW, I have version 2.85-5 of initscripts, sysvinit, and sysv-rc installed and am not having any problems re. terminal output. Just to confirm, your system boots into a terminal by default, you rebooted your computer and all text was displayed at the terminal including the login prompt? How about if you boot into single-user mode? (you should be able to do this by entering linux single (without the quotation marks) at the lilo prompt). Regards, Adam
Re: DO NOT UPGRADE UNSTABLE: Terminal text stops functioning
Hi Geordie Birch, The bug is most likely caused by initscripts, sysvinit or sysv-rc. If you have upgraded you may wish to downgrade/wait for a fix before rebooting, especially if your computer doesn't automatically boot into X. I have confirmed that downgrading to initscripts_2.85-4.1_all.deb sysv-rc_2.85-4.1_all.deb and sysvinit_2.85-4.1_i386.deb will resolve the lack of terminal output. I am submitting a bug report for the initscripts package, soon to appear here: http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=initscripts FWIW, I have version 2.85-5 of initscripts, sysvinit, and sysv-rc installed and am not having any problems re. terminal output. FWIW this has also happened on a third system. I am running out of additional computers to break. Regards, Adam
Re: DO NOT UPGRADE UNSTABLE: Terminal text stops functioning
Hi Geordie Birch, FWIW, I have version 2.85-5 of initscripts, sysvinit, and sysv-rc installed and am not having any problems re. terminal output. Upon standard bootup into a terminal it appears that output ceases before the INIT: Entering Runlevel : 2 message but will start up again if the kernel sends a message to the terminal. This could explain how you were still able to see the login. I suspect if you look harder at your terminal output you will see some of it is missing. You could be fortunate that a kernel message restarted the terminal output. On my third system output had also fully ceased in single user mode just like the rest. But when booting normally it restarted after a while when the parport module produced output. Perhaps one of the upgraded scripts contains an XOFF (CTRL-S) character code. Regards, Adam
Re: DO NOT UPGRADE UNSTABLE: Terminal text stops functioning
On Tue, Jul 22, 2003 at 06:45:26PM +1200, Adam Warner wrote: Hi Geordie Birch, On Tue, Jul 22, 2003 at 06:14:01PM +1200, Adam Warner wrote: I wrote: I have confirmed that downgrading to initscripts_2.85-4.1_all.deb sysv-rc_2.85-4.1_all.deb and sysvinit_2.85-4.1_i386.deb will resolve the lack of terminal output. FWIW, I have version 2.85-5 of initscripts, sysvinit, and sysv-rc installed and am not having any problems re. terminal output. Just to confirm, your system boots into a terminal by default, you rebooted your computer and all text was displayed at the terminal including the login prompt? Yes, this machine boots fine into the console. How about if you boot into single-user mode? (you should be able to do this by entering linux single (without the quotation marks) at the lilo prompt). When I boot into single-user mode I get the same results as you, ie. no output to the screen after the Setting up X sockets message. I can blindly log in as root at this point also. If I hit ctrl-d instead of the password, booting continues normally, ie. with regular terminal output. Geordie.
Re: DO NOT UPGRADE UNSTABLE: Terminal text stops functioning
On Tue, Jul 22, 2003 at 07:17:50PM +1200, Adam Warner wrote: Hi Geordie Birch, FWIW, I have version 2.85-5 of initscripts, sysvinit, and sysv-rc installed and am not having any problems re. terminal output. Upon standard bootup into a terminal it appears that output ceases before the INIT: Entering Runlevel : 2 message but will start up again if the kernel sends a message to the terminal. This could explain how you were still able to see the login. I suspect if you look harder at your terminal output you will see some of it is missing. You could be fortunate that a kernel message restarted the terminal output. On my third system output had also fully ceased in single user mode just like the rest. But when booting normally it restarted after a while when the parport module produced output. Perhaps one of the upgraded scripts contains an XOFF (CTRL-S) character code. I don't think it is a kernel message that is causing the output to start up again: on this system the arpwatch startup script (/etc/rc2.dS40arpwatch) causes a kernel message but non-kernel message output still does not appear on the terminal. The output of the the scripts in /etc/rcS.d/ is not affected; that of those in /etc/rc2.d/ is. On this system output begins to appear normally after bootlogd has been stopped, by the last script in the boot sequence, /etc/rc2.d/S99stop-bootlogd. Geordie.
Re: DO NOT UPGRADE UNSTABLE: Terminal text stops functioning
On mar, jui 22 09:17 Adam Warner [EMAIL PROTECTED] wrote : [...] This could explain how you were still able to see the login. I suspect if you look harder at your terminal output you will see some of it is missing. You could be fortunate that a kernel message restarted the terminal output. On my third system output had also fully ceased in single user mode just like the rest. But when booting normally it restarted after a while when the parport module produced output. Perhaps one of the upgraded scripts contains an XOFF (CTRL-S) character code. I've upgraded my system yesterday, and I've seen the problem you're talking about. Actually, I don't see any boot messages after Setting up ICE socket..., but I see wdm starting, and I got the login prompt right after. That makes me think this is bootlogd related. -- Lucas Moulin [EMAIL PROTECTED] | http://brebis.org There's no point in democracy when ignorance is celebrated NOFX - Idiots Are Taking Over pgphpfIc2oQ1h.pgp Description: PGP signature
Re: DO NOT UPGRADE UNSTABLE: Terminal text stops functioning
In article [EMAIL PROTECTED], Adam Warner [EMAIL PROTECTED] wrote: Since upgrading to the latest unstable I have discovered that after my startup reaches Setting up X socket server directory ... that I get no further output at the terminal. I have confirmed this on two different computers. Format: 1.7 Date: Tue, 22 Jul 2003 12:43:07 +0200 Source: sysvinit Binary: sysv-rc sysvinit initscripts Architecture: source i386 all Version: 2.85-6 Distribution: unstable Urgency: high Maintainer: Miquel van Smoorenburg [EMAIL PROTECTED] Changed-By: Miquel van Smoorenburg [EMAIL PROTECTED] Description: initscripts - Standard scripts needed for booting and shutting down sysv-rc- Standard boot mechanism using symlinks in /etc/rc?.d sysvinit - System-V like init. Closes: 202382 Changes: sysvinit (2.85-6) unstable; urgency=high . * When bootlogd gets an error writing to the real console, try to re-open. If that fails, roll over and die (closes: #202382) Mike.
Re: DO NOT UPGRADE UNSTABLE: Terminal text stops functioning
Hi Lucas Moulin, I've upgraded my system yesterday, and I've seen the problem you're talking about. Actually, I don't see any boot messages after Setting up ICE socket..., but I see wdm starting, and I got the login prompt right after. That makes me think this is bootlogd related. It is. And it has hopefully been addressed by Miquel van Smoorenburg (thanks Miquel). Less than five hours from report to new packages being created: Changes: sysvinit (2.85-6) unstable; urgency=high . * When bootlogd gets an error writing to the real console, try to re-open. If that fails, roll over and die (closes: #202382) Why should bootlogd get an error writing to the real console? What's the significance of this? I'm pleased this didn't result from carelessness. Miquel writes on #202382 that he had thoroughly tested it [bootlogd]. It's not worthy of comparison with the 2001 PAM login bug. Regards, Adam
