Re: Collecting information after installation
Don't inform the list, report a bug ;). -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1387632364.688.6.camel@archlinux
Re: Collecting information after installation
Since the 7.x version does my computer freeze; and that after installing GRUB and rebooting. Installing GRUB and rebooting is the last process of installation, but your information is not enough, so we can hardly help. Do you mean that, it cannot be shut down, or it cannot boot? What was the information on your screen? My system seem to work correctly but I thougth to inform you. Do you mean you have already found a workaround? If yes, how did you fix it? Like what Ralf Mardorf said, if you think it is a bug, you can consider to report it. For more information about bug reporting, please read: http://www.debian.org/Bugs/Reporting Sincerely, Bo -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1387633719.24794.7.camel@debian-bo
Re: Collecting information after installation
Assuming it should be booting to a graphical login screen, hit Ctrl-Alt-F1 which will take you to a text console which may show some errors that you can post here. rob On 21 December 2013 12:58, Ali ISIN a.i...@live.be wrote: Hi, My name is Ali, and I am a spoiled user of Debian. Debian is smooth and fast. Debian is sober and really what I expect from an operating system. But, that's not why I write to you: Since the 7.x version does my computer freeze; and that after installing GRUB and rebooting. My system seem to work correctly but I thougth to inform you. A. ISIN Student NB: I use Multimedia PC MEDION® AKOYA® P7350 D (MD8860) with only Debian as OS. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/blu0-smtp19983192980a09d1d0ca28f97...@phx.gbl -- *rob*
Re: Collecting information after installation
On Sat 21 Dec 2013 at 14:38:30 +, Robin wrote: Assuming it should be booting to a graphical login screen, hit Ctrl-Alt-F1 which will take you to a text console which may show some errors that you can post here. By default the screen is cleared of boot messages, There is only a login prompt. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/21122013174527.792b7cab5...@desktop.copernicus.demon.co.uk
Re: Collecting information after installation
Ali ISIN a.i...@live.be wrote: Hi, Since the 7.x version does my computer freeze; In what way? No more messages are logged? Doesn't respond to pings? SysRq doesn't reboot it (is the kernel totally hosed)? and that after installing GRUB and rebooting. My system seem to work correctly but I thougth to inform you. Installing or upgrading? If you copy the first, say, 448 bytes (I think that's right - 512-64 but it doesn't matter) to a file and then copy it back, does the same thing happen as with grub-install (grub-install has helper scripts to figure out things and it might be an issue with something done in there). -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/04902e62-9090-4ca6-80c8-cb8549bc3...@email.android.com
Re: Collecting information after installation
Brian wrote: On Sat 21 Dec 2013 at 14:38:30 +, Robin wrote: Assuming it should be booting to a graphical login screen, hit Ctrl-Alt-F1 which will take you to a text console which may show some errors that you can post here. By default the screen is cleared of boot messages, There is only a login prompt. Yes. Between util-linux 2.17.2-9 and 2.20.1-4 getty has changed and it now clears the screen. This seems like a good thing on the surface until you find out that it destroys the boot time messages including any errors that are on the screen at the time. To prevent this a new option --noclear has appeared. Editing the /etc/inittab to add the --noclear option to getty will prevent the new screen clearing behavior and allow the error messages there to be seen. 1:2345:respawn:/sbin/getty --noclear 38400 tty1 Also in Wheezy 7 the bootlogd is broken out into a separate package. If you want bootlogs in /var/log as it was in Squeezy 6 then you need to install the new package. apt-get install bootlogd The changelog for the package says: sysvinit-utils (2.88dsf-17) unstable; urgency=low bootlogd has moved from sysvinit-utils to a separate bootlogd package. If you wish to continue using bootlogd, please install the bootlogd package. Note that the configuration file /etc/default/bootlogd and its option BOOTLOGD_ENABLE no longer exist; if you do not wish to run bootlogd, remove the bootlogd package. -- Josh Triplett Mon, 19 Dec 2011 12:03:08 + Bob signature.asc Description: Digital signature
Re: Collecting information after installation
On 21 December 2013 17:47, Brian a...@cityscape.co.uk wrote: On Sat 21 Dec 2013 at 14:38:30 +, Robin wrote: Assuming it should be booting to a graphical login screen, hit Ctrl-Alt-F1 which will take you to a text console which may show some errors that you can post here. By default the screen is cleared of boot messages, There is only a login prompt. Depends when it froze. Won't there be xorg errors if it's a graphics driver problem? My sid install is 3.5 years old so I may be out of date:) -- *rob *
Re: Collecting information after installation
On Sat 21 Dec 2013 at 12:01:52 -0700, Bob Proulx wrote: Brian wrote: By default the screen is cleared of boot messages, There is only a login prompt. Yes. Between util-linux 2.17.2-9 and 2.20.1-4 getty has changed and it now clears the screen. This seems like a good thing on the surface until you find out that it destroys the boot time messages including any errors that are on the screen at the time. To prevent this a new The screen clearing was implemented by upstream as a response to concerns about security. Debian itself has never done it. option --noclear has appeared. Editing the /etc/inittab to add the --noclear option to getty will prevent the new screen clearing behavior and allow the error messages there to be seen. 1:2345:respawn:/sbin/getty --noclear 38400 tty1 This is one of the first things I do on any install ; I prefer the traditional way. Also in Wheezy 7 the bootlogd is broken out into a separate package. If you want bootlogs in /var/log as it was in Squeezy 6 then you need to install the new package. apt-get install bootlogd The changelog for the package says: sysvinit-utils (2.88dsf-17) unstable; urgency=low bootlogd has moved from sysvinit-utils to a separate bootlogd package. If you wish to continue using bootlogd, please install the bootlogd package. Note that the configuration file /etc/default/bootlogd and its option BOOTLOGD_ENABLE no longer exist; if you do not wish to run bootlogd, remove the bootlogd package. This lucid tip encourages me to consider including it as part of my normal practice. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/21122013191646.ba585acff...@desktop.copernicus.demon.co.uk
Re: Collecting information after installation
Brian wrote: Bob Proulx wrote: Brian wrote: By default the screen is cleared of boot messages, There is only a login prompt. Yes. Between util-linux 2.17.2-9 and 2.20.1-4 getty has changed and it now clears the screen. This seems like a good thing on the surface until you find out that it destroys the boot time messages including any errors that are on the screen at the time. To prevent this a new The screen clearing was implemented by upstream as a response to concerns about security. Debian itself has never done it. option --noclear has appeared. Editing the /etc/inittab to add the --noclear option to getty will prevent the new screen clearing behavior and allow the error messages there to be seen. 1:2345:respawn:/sbin/getty --noclear 38400 tty1 I can see that Debian wouldn't want to be different from upstream on this. But I wish upstream had not gone this way. Because the intent is to protect a clueless user from being clueless. But the practice hurts a cluefull user from being cluefull. The damage to the latter group is worse than the damage to the former group. And this is one of those features that both affects everyone and affects almost no one. When things are working with a graphical login manager then no one will be looking at this information. When there are problems then the messages are cleared and gone and the information is then missing. I really dislike things that cause problems only when there are problems. It is like having a failure to print an error message. This is one of the first things I do on any install ; I prefer the traditional way. Me too. It is now part of my standard system setup since Wheezy 7. In this context of console logins and security I am compelled to mention the Secure Attention Key. https://en.wikipedia.org/wiki/Secure_attention_key Also in Wheezy 7 the bootlogd is broken out into a separate package. If you want bootlogs in /var/log as it was in Squeezy 6 then you need to install the new package. apt-get install bootlogd This lucid tip encourages me to consider including it as part of my normal practice. It is part of my standard system setup since Wheezy 7 too. :-) Bob signature.asc Description: Digital signature
Re: Collecting information after installation
On Sat, 21 Dec 2013 12:01:52 -0700 Bob Proulx sent: Yes. Between util-linux 2.17.2-9 and 2.20.1-4 getty has changed and it now clears the screen. This seems like a good thing on the surface until you find out that it destroys the boot time messages including any errors that are on the screen at the time. To prevent this a new option --noclear has appeared. Editing the /etc/inittab to add the --noclear option to getty will prevent the new screen clearing behavior and allow the error messages there to be seen. 1:2345:respawn:/sbin/getty --noclear 38400 tty1 Thank you Bob. I also didn't like all that information suddenly disappearing before my eyes before I log in. But didn't know how to do that. You have helped me with your advice. Much better. Thank you, Charlie -- Registered Linux User:- 329524 *** Drugs are marvellous if you want to escape, but reality is so rich, why escape? - Geraldine Chaplin *** Debian GNU/Linux - just the best way to create magic - -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131222121836.35f4de93@taogypsy.wildlife
