Re: Nuking damned scrambled consoles.
On: Sun, 16 Aug 1998 15:02:09 -0400 Hank Fay writes: > > Cool. Thanks. > How would I hook this in to run whenever I come out of X? If you call x using startx, just create a alias. alias startx="/usr/bin/X11/startx; " Torsten
RE: Nuking damned scrambled consoles.
Cool. Thanks. How would I hook this in to run whenever I come out of X? Thanks, Hank Using VFP: MS's OOP Production Tool http://ourworld.compuserve.com/homepages/fayhj -Original Message- From: D'jinnie [mailto:[EMAIL PROTECTED] Sent: Sunday, August 16, 1998 2:01 PM To: debian-user Subject: RE: Nuking damned scrambled consoles. Don't know where I got this little script - but it usually fixes most console problems for me... #!/bin/sh # fixvt 1.00 # Fixes console corruption from vt bombs and the like #(c) 1994 Brian Stoler -- [EMAIL PROTECTED] #Freely redistributable under the GPL 2 #Mail me any changes/fixes/etc #Send flames to /dev/null -- I'm no scripter if [ -r /etc/?getty ]; then DAG=/etc/?getty elif [ -r /sbin/?getty ]; then DAG=/sbin/?getty elif [ -r /sbin/?getty ]; then DAG=/sbin/getty_ps elif [ -r /sbin/?getty ]; then DAG=/sbin/getty_ps elif [ -r $1 ]; then DAG=$1 else echo NO GETTY FOUND -- PUT GETTY ON CMD LINE exit 1 fi cat $DAG echo c clear echo Display restored. --- Trying to define yourself is like trying to bite your own teeth. -- Alan Watts D'jinnie/Jinn, encountered on IRC and select MU**. ([EMAIL PROTECTED]) -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
RE: Nuking damned scrambled consoles.
Don't know where I got this little script - but it usually fixes most console problems for me... #!/bin/sh # fixvt 1.00 # Fixes console corruption from vt bombs and the like #(c) 1994 Brian Stoler -- [EMAIL PROTECTED] #Freely redistributable under the GPL 2 #Mail me any changes/fixes/etc #Send flames to /dev/null -- I'm no scripter if [ -r /etc/?getty ]; then DAG=/etc/?getty elif [ -r /sbin/?getty ]; then DAG=/sbin/?getty elif [ -r /sbin/?getty ]; then DAG=/sbin/getty_ps elif [ -r /sbin/?getty ]; then DAG=/sbin/getty_ps elif [ -r $1 ]; then DAG=$1 else echo NO GETTY FOUND -- PUT GETTY ON CMD LINE exit 1 fi cat $DAG echo c clear echo Display restored. --- Trying to define yourself is like trying to bite your own teeth. -- Alan Watts D'jinnie/Jinn, encountered on IRC and select MU**. ([EMAIL PROTECTED])
RE: Nuking damned scrambled consoles.
Yes, setfont does work, fixing all consoles (all are affected) at once. Now I'm trying to learn how to make setfont run on my way out of X. If I don't learn that, I can try what you have below, but that seems to be one-VC oriented. Thanks much, Hank -Original Message- From: David B. Teague [mailto:[EMAIL PROTECTED] Sent: Sunday, August 16, 1998 6:27 AM To: Hank Fay Cc: debian-user Subject: RE: Nuking damned scrambled consoles. On Fri, 14 Aug 1998, Hank Fay and others wrote: > Well you could also try typing > > setfont default8x16 > > This is the only thing that would sort out an old Avance card that I > have when i exitted from X to a VC. But I'm not optimistic, as my > problem affected *all* VCs. [..] > Yup; it affects all vc's, just as you say. It looks like I need to reset > the video card to another mode; the question is how. My current approach > is to nuke the partitions and start over. Does the setfont command clear the console for anyone? I think part of this may have already been said, but I've been off for several days and cleaned my mail instead of reading it. Sorry. I have not found that this problem affects all virtual consoles. If so, I have been lucky. Such a situation suggests a mode on the video card itself that is hard to get out of, and that any solution will require a program to reset the card to some reasonable mode. Such a program will, of course, require carnal knowledge of the cards internal codes etc. At risk of being superfluous, this solution fixes systems that use a TVG 9400, an ATI Wonder, and another that uses a diamond speed star card. On neither machine does the problem affect affect more than one console. Typing directly control O to the console doesn't work for me, even preceeded by a control V. I get 04:53:53:~/projects/fix-console$^O bash: : command not found both for control o attempts and for the escape c solution below. My fix, from someone who told me about this: Linux consoles behave as a superset of vt100. My experience is that the vt100 reset codes sent raw to the console will reset a scrambled console. You can cat a file containing the character control O: With emacs, I create a new file called controlO and type control Q control O, exit and save. Any editor that allows entry of binary works. I have a short script, fixit, that does nothing but cat the file: #!/bin/sh cat controO This fixes the scrambled console for me. An alternative is to put the escape character followed by 'c' in the file that is cat'ed to the screen. This clears the screen and restores the console. This also works for me. I have not needed this since 1.1 where the reset command invariably fixes the problem. Even cat'ing an executable does not give problems. I can only scramble a console now by cat'ing a dvi file. Please forgive repetition, and I hope this helps. Some one helped me in the past with this problem. Linux, because, "Reboots are for hardware upgrades." --David --- LINUX: the FREE 32 bit OS for [3456]86 PC's available NOW! David B Teague | Ask me how user interface copyrights & software [EMAIL PROTECTED] | patents make programing a dangerous business. National Security Council nuclear explosion Linda Tripp destabilize Kenneth Starr Delta Force atomic bomb India Monica Lewinski data Ghanna encryption munitions counter-intelligence wild porno sex gold bullion
RE: Nuking damned scrambled consoles.
On Fri, 14 Aug 1998, Hank Fay and others wrote: > Well you could also try typing > > setfont default8x16 > > This is the only thing that would sort out an old Avance card that I > have when i exitted from X to a VC. But I'm not optimistic, as my > problem affected *all* VCs. [..] > Yup; it affects all vc's, just as you say. It looks like I need to reset > the video card to another mode; the question is how. My current approach > is to nuke the partitions and start over. Does the setfont command clear the console for anyone? I think part of this may have already been said, but I've been off for several days and cleaned my mail instead of reading it. Sorry. I have not found that this problem affects all virtual consoles. If so, I have been lucky. Such a situation suggests a mode on the video card itself that is hard to get out of, and that any solution will require a program to reset the card to some reasonable mode. Such a program will, of course, require carnal knowledge of the cards internal codes etc. At risk of being superfluous, this solution fixes systems that use a TVG 9400, an ATI Wonder, and another that uses a diamond speed star card. On neither machine does the problem affect affect more than one console. Typing directly control O to the console doesn't work for me, even preceeded by a control V. I get 04:53:53:~/projects/fix-console$^O bash: : command not found both for control o attempts and for the escape c solution below. My fix, from someone who told me about this: Linux consoles behave as a superset of vt100. My experience is that the vt100 reset codes sent raw to the console will reset a scrambled console. You can cat a file containing the character control O: With emacs, I create a new file called controlO and type control Q control O, exit and save. Any editor that allows entry of binary works. I have a short script, fixit, that does nothing but cat the file: #!/bin/sh cat controO This fixes the scrambled console for me. An alternative is to put the escape character followed by 'c' in the file that is cat'ed to the screen. This clears the screen and restores the console. This also works for me. I have not needed this since 1.1 where the reset command invariably fixes the problem. Even cat'ing an executable does not give problems. I can only scramble a console now by cat'ing a dvi file. Please forgive repetition, and I hope this helps. Some one helped me in the past with this problem. Linux, because, "Reboots are for hardware upgrades." --David --- LINUX: the FREE 32 bit OS for [3456]86 PC's available NOW! David B Teague | Ask me how user interface copyrights & software [EMAIL PROTECTED] | patents make programing a dangerous business. National Security Council nuclear explosion Linda Tripp destabilize Kenneth Starr Delta Force atomic bomb India Monica Lewinski data Ghanna encryption munitions counter-intelligence wild porno sex gold bullion
RE: Nuking damned scrambled consoles.
Yup; it affects all vc's, just as you say. It looks like I need to reset the video card to another mode; the question is how. My current approach is to nuke the partitions and start over. Hank Using VFP: MS's OOP Production Tool http://ourworld.compuserve.com/homepages/fayhj -Original Message- From: David Wright [mailto:[EMAIL PROTECTED] Sent: Friday, August 14, 1998 10:39 AM To: Hank Fay Cc: Mike Schmitz; debian-user Subject: RE: Nuking damned scrambled consoles. On Thu, 13 Aug 1998, Hank Fay wrote: > Well nothing seems to get rid of the little critters except shutdown. I > had to switch to another VC this time, because something unknown was going > on in the first one. It seems to be getting stuck in a different video > mode. Well you could also try typing setfont default8x16 This is the only thing that would sort out an old Avance card that I have when i exitted from X to a VC. But I'm not optimistic, as my problem affected *all* VCs. Rather than rebooting, have you tried just killing the relevant VC from another one? Cheers, > > well, it helped jumble up the funny critters. The only thing that > > works so far is shutdown > > > > > > Every now and then I do a little goof-up that scrambles a virtual > > > console and I'm sure we all do sometimes but lately I've been doing a > > > little programming and if I accidentally gib a string argument then it > > > corrupts the console every single time so I quickly run out of all 6 > > > consoles and am forced to reboot. > > > > > The way that I get ride of a scrambled console. > > 1. Try typing "reset" > > 2. Try typing "clear" > > 3. Try running "top" This always seems to work. don't know why but it > > does. > > > Try vo -- Email: [EMAIL PROTECTED] Tel: +44 1908 653 739 Fax: +44 1908 655 151 Snail: David Wright, Earth Science Dept., Milton Keynes, England, MK7 6AA Disclaimer: These addresses are only for reaching me, and do not signify official stationery. Views expressed here are either my own or plagiarised.
RE: Nuking damned scrambled consoles.
On Thu, 13 Aug 1998, Hank Fay wrote: > Well nothing seems to get rid of the little critters except shutdown. I > had to switch to another VC this time, because something unknown was going > on in the first one. It seems to be getting stuck in a different video > mode. Well you could also try typing setfont default8x16 This is the only thing that would sort out an old Avance card that I have when i exitted from X to a VC. But I'm not optimistic, as my problem affected *all* VCs. Rather than rebooting, have you tried just killing the relevant VC from another one? Cheers, > > well, it helped jumble up the funny critters. The only thing that > > works so far is shutdown > > > > > > Every now and then I do a little goof-up that scrambles a virtual > > > console and I'm sure we all do sometimes but lately I've been doing a > > > little programming and if I accidentally gib a string argument then it > > > corrupts the console every single time so I quickly run out of all 6 > > > consoles and am forced to reboot. > > > > > The way that I get ride of a scrambled console. > > 1. Try typing "reset" > > 2. Try typing "clear" > > 3. Try running "top" This always seems to work. don't know why but it > > does. > > > Try vo -- Email: [EMAIL PROTECTED] Tel: +44 1908 653 739 Fax: +44 1908 655 151 Snail: David Wright, Earth Science Dept., Milton Keynes, England, MK7 6AA Disclaimer: These addresses are only for reaching me, and do not signify official stationery. Views expressed here are either my own or plagiarised.
RE: Nuking damned scrambled consoles.
Well nothing seems to get rid of the little critters except shutdown. I had to switch to another VC this time, because something unknown was going on in the first one. It seems to be getting stuck in a different video mode. Hank -Original Message- From: Mike Schmitz [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 12, 1998 11:01 PM To: debian-user@lists.debian.org Subject: Re: Nuking damned scrambled consoles. On Wed, Aug 12, 1998 at 10:47:58PM -0400, Hank Fay wrote: > Chris, > > well, it helped jumble up the funny critters. The only thing that > works so far is shutdown > > Hank > > > Using VFP: MS's OOP Production Tool > http://ourworld.compuserve.com/homepages/fayhj > > -Original Message- > From: Ronn Pimentel [mailto:[EMAIL PROTECTED] > Sent: Wednesday, August 12, 1998 10:12 AM > To: Christopher Barry; debian-user@lists.debian.org > Subject: Re: Nuking damned scrambled consoles. > > > On Tue, Aug 11, 1998 at 12:23:22PM -0700, Christopher Barry wrote: > > Hi, > > > > Every now and then I do a little goof-up that scrambles a virtual > > console and I'm sure we all do sometimes but lately I've been doing a > > little programming and if I accidentally gib a string argument then it > > corrupts the console every single time so I quickly run out of all 6 > > consoles and am forced to reboot. > > > > The way that I get ride of a scrambled console. > 1. Try typing "reset" > 2. Try typing "clear" > 3. Try running "top" This always seems to work. don't know why but it > does. > Try vo -- Mike Schmitz [EMAIL PROTECTED]http://www.bend-or.com/~mschmitz Don't blame me - I voted libertarian!http://www.lp.org/ Use Debian Linux - the free Gnu/Linuxhttp://www.debian.org/ --- "If encryption is outlawed, only outlaws will have encryption"
Re: Nuking damned scrambled consoles.
On Wed, Aug 12, 1998 at 10:47:58PM -0400, Hank Fay wrote: > Chris, > > well, it helped jumble up the funny critters. The only thing that > works so far is shutdown > > Hank > > > Using VFP: MS's OOP Production Tool > http://ourworld.compuserve.com/homepages/fayhj > > -Original Message- > From: Ronn Pimentel [mailto:[EMAIL PROTECTED] > Sent: Wednesday, August 12, 1998 10:12 AM > To: Christopher Barry; debian-user@lists.debian.org > Subject: Re: Nuking damned scrambled consoles. > > > On Tue, Aug 11, 1998 at 12:23:22PM -0700, Christopher Barry wrote: > > Hi, > > > > Every now and then I do a little goof-up that scrambles a virtual > > console and I'm sure we all do sometimes but lately I've been doing a > > little programming and if I accidentally gib a string argument then it > > corrupts the console every single time so I quickly run out of all 6 > > consoles and am forced to reboot. > > > > The way that I get ride of a scrambled console. > 1. Try typing "reset" > 2. Try typing "clear" > 3. Try running "top" This always seems to work. don't know why but it > does. > Try vo -- Mike Schmitz [EMAIL PROTECTED]http://www.bend-or.com/~mschmitz Don't blame me - I voted libertarian!http://www.lp.org/ Use Debian Linux - the free Gnu/Linuxhttp://www.debian.org/ --- "If encryption is outlawed, only outlaws will have encryption"
RE: Nuking damned scrambled consoles.
Chris, well, it helped jumble up the funny critters. The only thing that works so far is shutdown Hank Using VFP: MS's OOP Production Tool http://ourworld.compuserve.com/homepages/fayhj -Original Message- From: Ronn Pimentel [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 12, 1998 10:12 AM To: Christopher Barry; debian-user@lists.debian.org Subject: Re: Nuking damned scrambled consoles. On Tue, Aug 11, 1998 at 12:23:22PM -0700, Christopher Barry wrote: > Hi, > > Every now and then I do a little goof-up that scrambles a virtual > console and I'm sure we all do sometimes but lately I've been doing a > little programming and if I accidentally gib a string argument then it > corrupts the console every single time so I quickly run out of all 6 > consoles and am forced to reboot. > The way that I get ride of a scrambled console. 1. Try typing "reset" 2. Try typing "clear" 3. Try running "top" This always seems to work. don't know why but it does. .ronn -- [EMAIL PROTECTED] and in your eyes i see a million candles burning bright.
Re: Nuking damned scrambled consoles.
On Tue, Aug 11, 1998 at 12:23:22PM -0700, Christopher Barry wrote: > Hi, > > Every now and then I do a little goof-up that scrambles a virtual > console and I'm sure we all do sometimes but lately I've been doing a > little programming and if I accidentally gib a string argument then it > corrupts the console every single time so I quickly run out of all 6 > consoles and am forced to reboot. > The way that I get ride of a scrambled console. 1. Try typing "reset" 2. Try typing "clear" 3. Try running "top" This always seems to work. don't know why but it does. .ronn -- [EMAIL PROTECTED] and in your eyes i see a million candles burning bright.
Re: Nuking damned scrambled consoles.
Richard E. Hawkins Esq. wrote: > > > Also, if there are any vim users reading this what does ^x ^s do? I > > sometimes accidentally type this when I mean to save a file (bad habit > > from using ae), and this seems to lock up vim pretty hard. > > ^S generally is a command to stopp sending . . . try ^Q if this freezes > things. > > rick > FWIW. ^S and ^Q are used on the tty for XON/XOFF processing. For those who mentioned that they are often hitting ^S by accident, you can disable ^S/^Q with the command 'stty -ixon'. -- Ed C.
RE: Nuking damned scrambled consoles.
When I come out of X, reset changes the dots to funny symbols, and ctrl-j bring me back to MC. That's progress from bold and not-bold periods. Now to get the rest of the way back... Hank -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 11, 1998 4:42 PM To: debian-user@lists.debian.org Subject: Re: Nuking damned scrambled consoles. Shaleh writes: > Try typing the word "reset" -- yes it will come out looking like > gibberish but type it anyway and hit return. This USUALLY works. In some cases you may need to type control-j instead of return. -- John Hasler [EMAIL PROTECTED] (John Hasler) Dancing Horse Hill Elmwood, WI
Re: Nuking damned scrambled consoles.
On Tue, 11 Aug 1998, Christopher Barry wrote: > Hi, > > Every now and then I do a little goof-up that scrambles a virtual > console and I'm sure we all do sometimes but lately I've been doing a > little programming and if I accidentally gib a string argument then it > corrupts the console every single time so I quickly run out of all 6 > consoles and am forced to reboot. > > Now, there has GOT to be a way to recover a scrambled console, right? Right. Try typing reset. Liran. --- http://www.math.tau.ac.il/~liranz/
Re: Nuking damned scrambled consoles.
Shaleh writes: > Try typing the word "reset" -- yes it will come out looking like > gibberish but type it anyway and hit return. This USUALLY works. In some cases you may need to type control-j instead of return. -- John Hasler [EMAIL PROTECTED] (John Hasler) Dancing Horse Hill Elmwood, WI
Re: Nuking damned scrambled consoles.
> Also, if there are any vim users reading this what does ^x ^s do? I > sometimes accidentally type this when I mean to save a file (bad habit > from using ae), and this seems to lock up vim pretty hard. ^S generally is a command to stopp sending . . . try ^Q if this freezes things. rick
Re: Nuking damned scrambled consoles.
>> "CB" == Christopher Barry <[EMAIL PROTECTED]> writes: [answered by Shaleh] CB> Also, if there are any vim users reading this what does ^x ^s do? I CB> sometimes accidentally type this when I mean to save a file (bad habit CB> from using ae), and this seems to lock up vim pretty hard. I don't use vim either. I rather use xemacs. Sometimes I use joe at the console. Used to C-x C-s to save files I somtimes type that in and joe freezes as well. It is C-s that causes this (Maybe *S*top or something). C-q will bring it back to live. Ciao, Martin
Re: Nuking damned scrambled consoles.
On Tue, 11 Aug 1998, Christopher Barry wrote: : Hi, : : Every now and then I do a little goof-up that scrambles a virtual : console and I'm sure we all do sometimes but lately I've been doing a : little programming and if I accidentally gib a string argument then it : corrupts the console every single time so I quickly run out of all 6 : consoles and am forced to reboot. Try the 'reset' command. You won't be able to read it, but it'll work (usually). : Now, there has GOT to be a way to recover a scrambled console, right? : Why isn't there protection for this in the first place? I don't see why : this would ever be desired behavior, unless this property is somehow : essential for 'correctness'? Well, ppp uses a "scrambled" console to set up the link, so it is desired behavior (though not in your case!) Remember, UNIX doesn't do much to protect you from yourself. : Also, if there are any vim users reading this what does ^x ^s do? I : sometimes accidentally type this when I mean to save a file (bad habit : from using ae), and this seems to lock up vim pretty hard. I don't use vim, but I'm pretty sure that ^s and ^q are software flow control characters ... ^s means "stop sending" and ^q means "start sending". If you type a ^s and the screen quits "working", type ^q and all should be well again. (I always thought these two characters did the reverse, but I guess my memory is poor). -- Nathan Norman MidcoNet - 410 South Phillips Avenue - Sioux Falls, SD mailto:[EMAIL PROTECTED] http://www.midco.net finger [EMAIL PROTECTED] for PGP Key: (0xA33B86E9)
Re: Nuking damned scrambled consoles.
Try typing the word "reset" -- yes it will come out looking like gibberish but type it anyway and hit return. This USUALLY works. I am known for letting grep go through binary files. Has the same effect as you describe. Also try ^o^u or ^u^o (I forget the sequence). This seems to help when nothing else does. I use vim, but never tried the control sequence you gave. Sorry.
