Search:

For starters, you're using the unstable development version, 1.8. Try with 1.7 and see what happens! :)

Sorry, use the CMake instructions above.

Oh god, that's probably ****** graphics card drivers. I had that for a year on my old laptop before Ubuntu finally updated their drivers. I'm not sure there's much I can do for you there.

Umm... CMake is only used for building Ogre itself. Follow the instructions in Step 5 of the HowTo for setting up a project with CodeBlocks.

Great, glad you figured it out! And glad the tutorial helped someone! :D

Hmm... How are you initializing the Ogre Root object? Also, can you post your Ogre.log file as well as the console output?

Sorry, Ogre has moved to CMake for its build process. The instructions are now simply


cmake .
make
sudo make install


I'll change the HowTo once Ogre's tutorials are updated and 1.7...

Sorry, I hadn't gotten around to updating these instructions for 1.7 yet. I think you can get by with replacing all the Ogre build instructions with


cmake .
make -j 4
sudo make install
...

So sorry, you're right, I'd completely forgotten that.

[FIXED]

Fixed another inconsistency Joel pointed out.

The reason I'd recommended keeping the build directory around is because people will often link to the sample app header or media files with a lot of their early applications, and be extremely...

I just replied to your personal message, but in case anyone else encounters this extremely strange error, it's more likely to be a compiler error than an Ogre one, but I would still check the Ogre...

To configure Grub 2 boot options, you must first get to the Grub menu. This may require changing the timeout so the first OS doesn't automatically load. Only when you are in the Grub menu may you...

One second, now I really don't understand. You're saying regardless of what OS you put in the CD drive, when you boot from it you are met with a black screen? That doesn't make any sense.

Now,...

What is your Grub timeout set to? Because 'e' should just bring it to the boot option editor within Grub, not actually boot anything. If you can't do that then either Grub is automatically booting...

Sorry, you have it installed properly, no? If so, you should be booting off the hard drive, not a LiveCD.

You'll have to edit the Grub boot options. This can be done (I think) by pressing selecting the boot menu option and pressing 'e', then appending options to after '... splash quiet'.

Yep, I'm actually posting this from the Karmic partition on my HD. Everything is working great except for the graphics. GLXGears still gets around 500FPS, and I can't run any 3D anything, including...

Cool, I'll try that right now. Thanks!

EDIT: It works! With 'i915.modeset=0 acpi=off' added to my boot commands, I finally have a functional Karmic installation! Thank you so so so much!

http://www.roflcat.com/images/cats/halp.jpg plz?

Thanks! :D

Huh... Did you add 'i915.modeset=0' to the boot options?

Actually, I just recently found out that the keyboard and mouse not responding aren't graphics card related but most likely a bug in gnome. See this thread again:...

This was two weeks ago, and still no progress.

On a whim, I tried install Kubuntu 9.10, and with the same 'i915.modeset=0' it works! So the keyboard and mouse hanging are a glitch with GDM then? ...

No, that's just for recovery mode.

Ok, bad news. After running '/etc/init.d/acpid start', the ACPI warning goes away but the exact same thing happens. This is REALLY weird, because now the log files from the CD and the harddrive...

Hopeful bump?