Talk:Ubuntu Feisty Installation Guide: Difference between revisions

From cchtml.com
 
No edit summary
Line 19: Line 19:
Is this a hardware limitation (I have X1650 Pro) or a driver limitation?
Is this a hardware limitation (I have X1650 Pro) or a driver limitation?
:You need to troubleshoot your installation method. -- [[User:Mooninite|Mooninite]] 14:10, 27 March 2007 (CDT)
:You need to troubleshoot your installation method. -- [[User:Mooninite|Mooninite]] 14:10, 27 March 2007 (CDT)
== 2.6.20 Patching ==
'''IMPORTANT: This method will not work with 2.6.20.* kernels.''' Is this still true? My feisty install is kernel 2.6.20-13-generic and it was trivial to install fglrx using the first method mentioned.  If the second method is still really required, it would be good to say why (eg, something is busted in Ubuntu's 26.20 ?)

Revision as of 08:41, 31 March 2007

Not works with Feisty Fawn Herd 5

The patch not works at this: sudo patch < ~/fglrx-2.6.20.patch the system asks for file can't found it.
UPDATE: The patch seems works fine but still not working for 3D acceleration install..

  • OpenGL vendor string: Mesa project: www.mesa3d.org
  • OpenGL renderer string: Mesa GLX Indirect
  • OpenGL version string: 1.4 (1.5 Mesa 6.5.2)

This is all hard

Very hard work indeed and it still doesn't do dual head. is there any way of getting a non 3d driver going, which will just show a movie on my projector. I rebooted a lot today, a lot.

OpenGL not working, so no Google Earth - and many other programs

I did my share of rebooting, too.
I'm really frustrated.
Is this a hardware limitation (I have X1650 Pro) or a driver limitation?

You need to troubleshoot your installation method. -- Mooninite 14:10, 27 March 2007 (CDT)

2.6.20 Patching

IMPORTANT: This method will not work with 2.6.20.* kernels. Is this still true? My feisty install is kernel 2.6.20-13-generic and it was trivial to install fglrx using the first method mentioned. If the second method is still really required, it would be good to say why (eg, something is busted in Ubuntu's 26.20 ?)