Dietrich Bollmann wrote: > Any idea what could be the reason? Others have pointed out some of the excellent guesses that could be the possible culprit. My only suggestion is to go back to the command line and disable X. Then verify whether it is an X related problem or a kernel related issue. hth raju -- Kamaraju S Kusumanchi http://www.people.cornell.edu/pages/kk288/ http://malayamaarutham.blogspot.com/