Slashdot Mirror
Panicking In Morse Code
An anonymous reader writes "When an i386 running Linux panics, a function in the kernel called 'panic_blink' causes the system's LEDs to blink. Andrew Rodland recently posted a creative patch to turn that steady blink into a useful message in morse code!"
and that message is...
(sos) =)
Gyrate Dot Org - "Where high-tech meets low-life"
10 comments and the site's down. Did anyone grab a copy before we killed the site?
on the SE or SE30 (SE i think), when there is a hard drive problem, the drive light blinks SOS...the 'O' is a little drawn out, but it's readable.
...of Wolfenstein 3D.
If you translated the beeping in various levels of the third episode, it was a message in Morse Code telling you to defeat Hitler!
I mod down anyone who uses M$ in their posts. I like to live on the edge.
I can't do that dave
I'm melting ....
beam me up, scotty
feed me
I wonder if there is a morse code to voice coverter device out there? that would be a neat module to have to plug in as a peripheral
of course, if the code goes fast enough, you can gain the ability to recognise whole words as a sort of warble.
"It is a greater offense to steal men's labor, than their clothes"
You're paraphrasing Richard Feyman:
Physics is like sex: sure, it may give some practical results, but that's
not why we do it. --Richard Feynman.
Although this is a neat and creative idea, I think that a better way to diagnose a sick computer would be a standard for a set of diagnostic LEDs or even a small LCD panel as part of the next motherboard standard.
Some manufacturers of motherboards and whole systems already do this, but it's far from standard, and is typically only useful for POST errors. A full standard would allow O/Ses, as well as the BIOS to access the output device (be it LEDs or an LCD) and display a standard code for whatever the error is, which the user could then look up in the manual, or on the web.
My other sig is funny!
Linux: Panicking In Morse Code Submitted by Jeremy on Saturday, July 20, 2002 - 08:12
/* Tell the user who may be running in X and not see the console that we have
Digging through the source code of a recent kernel, in the file 'linux/drivers/char/pc_keyb.c', above the definition for the function 'panic_blink', one reads the following comment:
panic'ed. This is to distingush panics from "real" lockups.
Could in theory send the panic message as morse, but that is left as an
exercise for the reader. */
Andrew Rodland stumbled across this comment, and as he explains, "not being the kind to step down from a challenge (unless it's just really hard), I decided to write morse code output code." His patch against Linux kernel version 2.4.19-rc1-ac1 (plus preempt) actually modifies the kernel to report a panic in morse code! Andrew also submitted a small sample module for generating test panics.
From: Andrew Rodland
To: linux-kernel AT vger.kernel.org
Subject: [PATCH -ac] Panicking in morse code
Date: Fri, 19 Jul 2002 01:13:00 -0400
No, it's not 1 April.
I was researching panic_blink() for someone who needed a little help,
when I noticed the comment above the function definition, not being the
kind to step down from a challenge (unless it's just really hard), I
decided to write morse code output code.
The option panicblink= has been hijacked to be a simple bitfield:
bit 1 : blink LEDs
bit 2 : sound the PC speaker.
the blinking option depends only on pc_keyb.c. the pcspeaker option
depends on kb_mksound() actually doing something. At the moment, both of
these mean i386. The call to panic_blink() in panic() is still guarded
by an i386 #ifdef, anyway, for the moment. The default is to blink only,
because I figured the beeps would be too annoying. Opinions?
It recognizes letters, and digits, and treats everything else as a
space. The timings are tunable by #defines. It repeats the message
indefinitely. And it should only bloat the kernel by a few hundred
bytes, although if someone wants to wrap this in its own config option,
well, that's good too.
Anyway, here's the patch. It's against linux-2.4.19-rc1-ac1+preempt, but
I suspect it applies against all recent -ac. If 2.5 has this, it will
hopefully apply with some fuzz against that, too. I don't have a tree.
Four dits!
Two dits!
Dah!
Windows! Windows! Rah Rah Rah!
Perhaps a more useful hack would have been to have the blinky lights signal SOS when a server is being slashdotted. They could have checked it out when submitting this story.
Here's some more ideas:
1. Blinky lights go crazy when portsentry reports block yet another attempt at port 80 (best learn how to replace worn out blinky lights first);
2. Blinky lights make pretty patterns depending on up time of machine (Oops, now I'm flamebait since Windows users will never see pretty blinky lights);
3. Blinky lights go wild whenever a human female is within 10 feet of machine (unlike the machine's owner who may or may not notice, depending on the task at hand -- oy, did I really say that?);
I love blinky lights and thank the gods every day that I don't have adverse reactions to them. Now if I can just find a female who doesn't cause adverse reactions, I'm doing good!
Everything in the Universe sucks: It's the law!
I donwloaded a winamp plugin that would flash the LEDs with the oscilliscope(sp). Anyway, I thought it was pretty neat untill I tried being productive with it turned on. Turns out that it actually just switches the caps/num lock on and off. So in the middle of my text, i'd Get TExt LiKE THIs. It was neat, but annoying if I planned on typing.
My other sig is an import.
Just checking. I can't believe no one's mentioned the part in Neal Stephenson's Cryptonomicon where Randy "prints" out the "message" (trying to avoid a spoiler) on his laptop's LED.
Here's an LED controller program inspired by that bit in the book.
c-hack.com |
Ummmmmmmmmm........ isn't that what serial is for?
The streets shall flow with the blood of the Guberminky.
If I didn't know better I'd say that's what Compaq's, or was it old ALRs (remember them?) did when hardware wasn't right.
A string of varying beeps. This was years ago, don't know if any recent hardware still does it.
Tech support: Hold the phone close to the system board so I can hear it.
That was funny.
-Pete
Soccer Goal Plans
The kerneltrap.org server's led's are furiously flashing:
[imagine 'slashdotted' in morse here]
Lameness filter encountered. Post aborted!
Reason: Please use fewer 'junk' characters.
Morse != Junk! Damn you lameness filter!!
mstyne: real name, no gimmicks
This is a good page for the morse code and common abbreviations used by HAM (amateur radio) operators. You could always have your computer die with QSB? (are my signals fading?)...
Mordor...a magical, mythical land where women are more rare than dragons--but where every man would rather find a dragon
All your funny are belong to a year and a half ago!
Someone set up us the dead horse!
You have no chance to be funny make your time!
Karma: Non-Heinous
As to the question of flashing the LED because Morse on the speaker might be too annoying, I say go for the speaker. Those who do know Morse know it by sound, not by individual dots and dashes, and seeing it on an LED is a very different thing than listening to it. If the system has panicked I'm already annoyed, beeping isn't going to be a problem. Just the opposite, if I'm nearby but not looking at the computer I want the beeping to get my attention to the problem.
And here's the really stupid question: What is this blinking system LED he's talking about???? I have a power LED on my PC, but it's not software controlled. Some PC's used to have a "turbo" LED, but that's been phased out. I sure hope he's not using the hard disk LED. Is he using a Keyboard LED or am I missing something really obvious here?
I'm an American. I love this country and the freedoms that we used to have.
As an old army telgraphist and hamradio operator I would prefer morse to be sent via the PC speaker instead of some LED's. A human can attain much higher reception speed by using his eara as opposed to using his eys.
//Pingo
Since I myself is capable of morse ear reception much faster than normal people are able to speak, I would really like to have a morse interface to my Linux boxes.
Imagine also to get rid of the keyboard and use a simple morse key as input device. Ahhh nirvana at last.
--- Linux or FreeBSD, it's like blondes or brunettes. I like both. ---
I've mirrored the comment page and the patch
here for your pleasure.
I remember doing this on a embedded FORTH-system in the 80-ies. The only way to communicate with the board when the RS232 was gone was a little piezo-beeper.
A quick trip to Google found me the CGI Morse Code Translator, which translates "server slashdotted" to:
:)
(Lameness filter encountered. Post aborted!
Reason: Please use fewer 'junk' characters.)
slashdot sucks
dot dot dah dot dot dah dot dah dot dah dot dah dot dah dot dot
___
Cogito cogito, ergo cogito sum.
As opposed to Windows, where you get error messages like "An invalid page fault has occurred in module KERNEL.DLL at: " and then a page and a half of hex. By which time, your system and anything you were working on is completely buggered.
At least on a bunch of the HP Netserver models we've used - LX Pro, LH3, LH4, etc. They seemed to have dropped it on the smaller 2U and 1U models like the 1000 and 2000 due to lack of space or something.
It's too bad there's not a standardized motherboard resource (built-in PCI device, etc)for LCD displays like this; OS and app vendors would then be able to utilize it out of the box.
The idiotic thing is the displays on our LH3s and LH4s didn't show much and were useless, even with the "interactive" buttons that let you cruise around like on a printer. If they could display system load, temperature, yadda yadda they would be be much more useful.
Of course we know the logical conclusion to LCD displays on the front of computers -- someobody will have to have a full-blown 6" color LCD display on the front of the machine...
Thanx to the people to worked on it...it is silliness like this that make Linux well worth the effort to learn, understand and play with!
ttyl
Farrell
CAN-CON 2019 - Ottawa's only book oriented Science Fiction Convention! October 18-20, Sheraton Hotel, Ottawa, Canada h
If you follow the link, you'll see that he implimented it for the PC speaker as well. (You can set this as an option.) Of course, that depends on the speaker driver being in a decent state during the panic.
Hire a Linux system administrator, systems engineer,
One of the cool things about Cobalt RaQ servers is the LCD on the front panel. There's a simple driver control program that can be used to spit out the text (or bit-graphics, apparently).
We have about 120 of these in our data center and we tech occasionally play practical jokes on or leave messages for one another on them. =)
Hire a Linux system administrator, systems engineer,
"Hey, I'm getting a message in morse code. Get my pencil, Let's see:
e r r o r - i n - m o r s e - c o d e - g e n e r z k b g h i l e r l b v c t q z
Doh!"
Table-ized A.I.
One of the (many) cool things that differentiate Macs from PC's is the way the report POST failures.
Depending on if the video driver was sane or not yet, you'd get an infamous "San Mac" display, followed by a few codes in hex describing what was wrong. If not, you'd get POST-coded beeps.
What was really cool were the "chimes of death". Each Mac model family had a specific sound that played when the POST test failed. These ranged from the opening to the Twilight Zone theme, to a drum crash, to the sound of glass breaking, to a full-on car crash. (You get get some of them here, but I KNOW there's a more comprehensive list with samples out there somewhere.)
Ahh, memories...
Hire a Linux system administrator, systems engineer,
No, always have a stop bit. The highest on bit is the stop bit, and not played. This allows up to 7 bits of useful bits.
Infuriate left and right
Each Operating System displayed a different pattern, so sometimes you could walk up to a computer and immediately know what OS was running without touching it. This was a very useful skill for impressing the gullable.
RSTS - displayed a pattern that cycled from left to right.
DSM - displayed a pattern that went from the sides to the center.
RSX - I can't remember what this one did, can anyone else recall?
I find this idea interesting - especially since only a few of the kernel hackers actually KNOW
morse code. AC and BP have ham licenses. Don't know about the rest of the hackers..
Have you compiled your kernel today??
A company in Lynchburg Va has a patent on this. Most likly they don't even know it but their patent on a one wire control system describes a computer sending (and recieving) morse code as well as sending out warnings via morse code. The guy who "invented" it said he didn't even understand what the patent application said and he already had about twenty patents. The patent was supposed to be for using a single wire control system in places where you can't drill holes to run wires but turns out to be a patent on morse code. They guy whos name is on the patent said there was piror art that he knew of involving mechanical devices so its not a major issue but like so many other ideas, in theory you can't sell this one without a license.
Many years I had suggested using Morse Code instead of BIOS-beep error codes.
At the time, there were many different BIOSes out there, with their own different beep-code values. It seemed that morse code was already the most wide-spread binary communication system in use by humans.
Now, there's really only two BIOS manufactures you'll see out there, and there's an increasing trend of having more advnaced BIOSes (non-Intel systems) which output error messages in different ways, (on-screen, serial cable, etc) which limits the usefullness of that idea today.
So... Why not do the same thing with Linux? Output to the screen, serial port, or parallel ports (print it out!). If nothing else, it would allow automation of information gathering, rather than requiring someone be right there, to translate the dots and dashes to messages.
Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
Way OT.. just wanted to say that I wonder how many people are aware that when their cellphones receive a text message and beep loudly with "dit-dit-dit, dah-dah, dit-dit-dit" their cellphones are actually sending "SMS" in morse code -- SMS, "SMS", get it? :)
I commute in the masses making their way to and through NYC everyday, and I must hear that four times a day on the train.
Intelligent Life on Earth
Oh, well, if we're going to descend to ancient hardware blinkenlights stories... (which model PDP-11, BTW?)
The Burroughs B6700 (and similar models) was a 48-bit word (96-bit double) stack oriented mainframe. The main panel had an array of 12 by 16 lights showing the bits in the top two words (double words) in the current stack. At idle, those would light up with the Burroughs "B" logo.
Of course the challenge was to come up with code that would load those registers with some interesting pattern and keep it there long enough for the operators to notice.
-- Alastair
For some hardware functions like that. A nice LCD screen, like IBM UNIX boxes have.. so that when your computer hangs for apparently no reason (like mine) you at least have a clue as to why (unlike mine). Just a nice little hex display or something.. *sigh*
theres one from mac hack that would make your dock icons bounce up and down in the dock with the music. Unfortunately it rapes the event que, making it difficult to even move the mouse to shut it off. useless but cool.
I want 2D games back.