View Full Version : Doesn't boot with "no3d"

Luke M
05-21-2010, 02:11 PM
Boot crashes when "no3d" used. When not used, boots fine but compiz is extremely slow and buggy (Worst. Software. Ever.)ATI Radeon 8500 graphics card.Another option to try?

05-23-2010, 06:57 AM
This has something to do with the video driver in use. Try booting with one of this cheatcodes
fb1024x768, or knoppix xmodule=vesa, or knoppix xmodule=fbdev
This is not a permanent solution but at least you will know where the problem is and try to update the video driver if there is one available

Luke M
06-11-2010, 03:34 AM
I got it to work this way: knoppix xmodule=radeon no3d

Luke M
06-11-2010, 09:10 AM
Further investigation has clarified the situation. I can reliably boot Knoppix 6 (any options) from a COLD start. But it's not reliable from a reset. (Never had this problem with Knoppix 5)

06-11-2010, 10:21 PM
I encountered this same problem/symptom occasionally over the years, before Knoppix 6 was released. I think it may be some hardware initialization that is left to the hardware itself. I've seen some pretty strange hardware glitches over time...

Krishna :mrgreen:

Luke M
06-13-2010, 07:57 PM
Well, I thought I had it figured out, but no. It's just not reliable, period. Doesn't matter what options, or cold or warm boot...it fails randomly.In any case, no3d is absolutely essential. Without no3d, the system is unusable even when the boot works.

06-14-2010, 02:05 AM
Can you post with what video driver does knoppix boot ? Did you try the xmodule=vesa ? When you use xmodule=radeon it's not guerantee that knoppix will use that driver - it will try to use it, but if it does not work it will fall back to fbdev or vesa. So if you boot a few times successfully using vesa or fbdev then it's really the video driver to blame. I still think there is nothing else to blame

06-19-2010, 10:59 AM
Sounds like a hardware detection problem to me. Hardware response patterns may vary from time to time, in particular in timing, and the system gets set off in different directions. I would have tried heaping up cheatcodes to see if it could possibly stabilize the initialization, and eventually remove them one by one afterwards. Did you try to specify the screen resolution, for example? I have had to do that.