Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

I crashed Linux



Ron Peterson wrote:
> 
> I crashed Linux.  For the first time.  I didn't think it was possible.
> 
> I was trying to get my old Microtek ScanMaker E3 going vis-a-vis RH 7.0,
> kernel 2.4-test10 and SANE 1.0.3.  It was ugly, but it wasn't pretty.
> SANE's 'scanimage' saw my scanner o.k., but when I ran:
> 
> scanimage --format=tiff --mode Color --speed 2
> --device=microtek:/dev/scanner -l 0 -t 0 -x 100 -y 150
> 
> the scanner just make a couple of blurps, then... nothing.  My KDE
> session was dead.  I killed X o.k., but then I couldn't get a console.
> I had to hard reboot.
> 
> I don't really know what the point of this post is.  Just interesting
> that it could even happen.  I guess it is a test kernel.

I've had cases where the console goes completely dead (you can't
see anything on the screen, and the keyboard won't work), but
Linux STILL hasn't crashed - just the console code. Did you try
using telnet to get into the box? (It hasn't happened to me for a
long time, by the way.) 


-- 
Mark J. Dulcey               mark at buttery.org
Visit my house's home page:  http://www.buttery.org/
Visit my home page:          http://www.buttery.org/markpoly/
-
Subcription/unsubscription/info requests: send e-mail with
"subscribe", "unsubscribe", or "info" on the first line of the
message body to discuss-request at blu.org (Subject line is ignored).




BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org