Okay here is the deal.
When you run Blender on my laptop IBM t40p with an ATI Technologies Inc Radeon RV250 [Mobility FireGL 9000] (rev 02) gfx card (xorg.conf setting: Driver "radeon") it will eventually crash (it always crashes, when I change the view to camera).
I never used Blender before, but now I would like to play around with it, so I realized that I must do something with my gfx card driver. Well, the standard suggestion is... install fglrx driver, and yes I have tried that without luck.
The facts:
PC: IBM laptop t40p
Gfx card from lspci: 01:00.0 VGA compatible controller: ATI Technologies Inc Radeon RV250 [Mobility FireGL 9000] (rev 02)
Resolution: 1400x1050 may be an issue for the fglrx proprietary driver?
System:
Running KDE 3.58
Kernel: 2.6.22-14-generic
Release: 7.10
Codename: gutsy
Here is what I have tried:
1) Change my gfx driver through the KDE GUI, to Ati Radeon (fglrx) standard and proprietary.
With standard fglrx (xorg.conf setting: Driver "ati") the same crash in Blender.
With proprietary fglrx (xorg.conf setting: Driver "fglrx") I can't boot into my x-session no gfx.
No luck with 1).
2) I thought I could win something by adding xorg drivers to my sources list from launchpad:
No luck with 2).
3) Different options in xorg.conf in the gfx device section (http://www.phoronix.com/forums/showthread.php?t=7448)
Option "OpenGLOverlay" "off"
Option "VideoOverlay" "off"
No luck with 3).
4) Install from Ubuntu repositories (easier) - BinaryDriverHowto/ATI guide (https://help.ubuntu.com/community/BinaryDriverHowto/ATI).
5) Install from ati.com (latest version of drivers) - BinaryDriverHowto/ATI guide (https://help.ubuntu.com/community/BinaryDriverHowto/ATI).
No luck with 4) and 5) I can't boot into my x-session no gfx, output from Xorg.0.log:
***
(II) Primary Device is: PCI 01:00:0
(II) ATI Proprietary Linux Driver Version Identifier:8.44.3
(II) ATI Proprietary Linux Driver Release Identifier: UNSUPPORTED-8.443.1
(II) ATI Proprietary Linux Driver Build Date: Dec 19 2007 21:29:14
(EE) No devices detected.
Fatal server error:
no screens found
***
6) Install Envy 0.9.10 -> Choose install the ATI Driver -> Output:
Hmm the driver does not support Ubuntu Gutsy..?
No luck with that either.
7) Envy -> Install the ATI driver Manually
I tried all the possibilities: version 8-01, 8.40.4 and 8.28.8 without luck, I can't get back to kdm after restart.
8)Tried the installation script for fglrx (http://kubuntuforums.net/forums/inde...opic=3082777.0)
I know it's an old one probably outdated.. but hey ;-)
I didn't succeed.
9) Give up fglrx and play with Blender in M$ winDOS.
I have attached my current xorg.conf, probably pretty messy.
Hmm any suggestions for a valid solution?
When you run Blender on my laptop IBM t40p with an ATI Technologies Inc Radeon RV250 [Mobility FireGL 9000] (rev 02) gfx card (xorg.conf setting: Driver "radeon") it will eventually crash (it always crashes, when I change the view to camera).
I never used Blender before, but now I would like to play around with it, so I realized that I must do something with my gfx card driver. Well, the standard suggestion is... install fglrx driver, and yes I have tried that without luck.
The facts:
PC: IBM laptop t40p
Gfx card from lspci: 01:00.0 VGA compatible controller: ATI Technologies Inc Radeon RV250 [Mobility FireGL 9000] (rev 02)
Resolution: 1400x1050 may be an issue for the fglrx proprietary driver?
System:
Running KDE 3.58
Kernel: 2.6.22-14-generic
Release: 7.10
Codename: gutsy
Code:
fglrxinfo display: :0.0 screen: 0 OpenGL vendor string: Tungsten Graphics, Inc. OpenGL renderer string: Mesa DRI R200 20060602 AGP 4x x86/MMX/SSE2 TCL OpenGL version string: 1.3 Mesa 7.0.1
1) Change my gfx driver through the KDE GUI, to Ati Radeon (fglrx) standard and proprietary.
With standard fglrx (xorg.conf setting: Driver "ati") the same crash in Blender.
With proprietary fglrx (xorg.conf setting: Driver "fglrx") I can't boot into my x-session no gfx.
No luck with 1).
2) I thought I could win something by adding xorg drivers to my sources list from launchpad:
Code:
#xorg drivers deb [url]http://ppa.launchpad.net/tormodvolden/ubuntu[/url] gutsy main deb-src [url]http://ppa.launchpad.net/tormodvolden/ubuntu[/url] gutsy main
3) Different options in xorg.conf in the gfx device section (http://www.phoronix.com/forums/showthread.php?t=7448)
Option "OpenGLOverlay" "off"
Option "VideoOverlay" "off"
No luck with 3).
4) Install from Ubuntu repositories (easier) - BinaryDriverHowto/ATI guide (https://help.ubuntu.com/community/BinaryDriverHowto/ATI).
5) Install from ati.com (latest version of drivers) - BinaryDriverHowto/ATI guide (https://help.ubuntu.com/community/BinaryDriverHowto/ATI).
No luck with 4) and 5) I can't boot into my x-session no gfx, output from Xorg.0.log:
***
(II) Primary Device is: PCI 01:00:0
(II) ATI Proprietary Linux Driver Version Identifier:8.44.3
(II) ATI Proprietary Linux Driver Release Identifier: UNSUPPORTED-8.443.1
(II) ATI Proprietary Linux Driver Build Date: Dec 19 2007 21:29:14
(EE) No devices detected.
Fatal server error:
no screens found
***
6) Install Envy 0.9.10 -> Choose install the ATI Driver -> Output:
Code:
python pulse.py ati root@t40p:/usr/share/envy# python pulse.py ati Envy - Version 0.9.10 Ubuntu Gutsy 32bit Your graphic card has been detected as a ATI Mobility / Radeon 9000 Your graphic card is supported by the legacy Driver ENVY ERROR: ATI's legacy driver does not support your operating system root@t40p:/usr/share/envy# uname -r 2.6.22-14-generic root@t40p:/usr/share/envy# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 7.10 Release: 7.10 Codename: gutsy root@t40p:/usr/share/envy#
No luck with that either.
7) Envy -> Install the ATI driver Manually
I tried all the possibilities: version 8-01, 8.40.4 and 8.28.8 without luck, I can't get back to kdm after restart.
8)Tried the installation script for fglrx (http://kubuntuforums.net/forums/inde...opic=3082777.0)
I know it's an old one probably outdated.. but hey ;-)
I didn't succeed.
9) Give up fglrx and play with Blender in M$ winDOS.
I have attached my current xorg.conf, probably pretty messy.
Hmm any suggestions for a valid solution?