knoppix doesn't boot

**rporticio** · 05-08-2007, 05:00 AM

dear friends,

i'm using a cpu with intel pentium D processor. i tried to boot knoppix 5.0 from the dvd drive so that i can retrieve the files from the linux hardisk installed in the cpu. this is slave drive with a primary drive having a windows OS. the cd boot a while but i noticed that the knoppix images are just blank and not visible. when the gui of knoppix is supposed to show up the monitor went blank and the light indicators just below the screen flash on and off continuously.

i tried this to other cpu with the same capability and the result is the same. but on older cpu there is no problem. is this a support problem with the new intel pentium D. what is the remedy for this?

thank you for any help on this matter.

sincerely,

ramon

**ckamin** · 05-08-2007, 05:42 AM

See: http://www.knoppix.net/forum/viewtopic.php?t=27218

If you have similar hardware to the systems mentioned in the above thread, try the cheat code: "knoppix xmodule=vesa"

**Harry Kuhman** · 05-08-2007, 06:53 AM

While we were not told what the video card is, so we can't know if it's supported, it sounds to me more like the monior is being pushed beyond it's scan rate capability. Using the cheat codes to force the scan rates within the monitor's spec seems to be a likely fix.

**rporticio** · 05-09-2007, 04:43 AM

dear harry & ckamin,

thank you for your time in making your suggestion. i typed knoppix xmodule=vesa after boot when i loaded the knoppix cd and it worked. i sent this message to you through knoppix 5.0

what's the magic behind knoppix xmodule=vesa?

thanks again.

**ckamin** · 05-12-2007, 08:51 AM

rporticio,

The cheat code "knoppix xmodule=vesa" simply appears to define a more generic graphics hardware device and driver than Knoppix may have detected during the boot process. It seems that the current versions are having a little trouble with certain graphics adaptors. The "black screen" is a good indicator that the graphics adaptor is not set up correctly in Knoppix and the xmodule=vesa cheatcode seems to be a decent workaround. There may be some resulting issues with the display while doing so, but it's usually workable.