PDA

View Full Version : [ubuntu] fglrx Thinkpad t60P



treyphan
July 17th, 2008, 03:30 PM
I can't get big desktop to work.. I enable it, it prompts me to restart my system I do so, and the changes are never applied?

treyphan
July 17th, 2008, 07:14 PM
bump ?

markbuntu
July 18th, 2008, 03:09 AM
Which version of fglrx are you using and what video card?
Does it work in clone?

treyphan
July 18th, 2008, 01:05 PM
8.47.3

It does show up in clone mode but not properly. I'm about at my wits end with this whole ATI thing.

markbuntu
July 19th, 2008, 07:03 AM
Ok. There have been some major changes to flgrx since 8.47.3. I had a lot of problems getting dual monitors to work right with 8.47.3. Since then I have used the 8.5 and now 8.6 drivers and their improved CCC and it has made a big difference.

If you want to get the 8.6 driver, you can follow Method 2 here:

http://wiki.cchtml.com/index.php/Ubuntu_Hardy_Installation_Guide

If you want some tweaks for it and some general explanation about how to use xorg.conf with fglrx, you can go here:

http://forum.compiz-fusion.org/showthread.php?t=6794

If you want to learn some more general options about aticonfig, type aticonfig --help.

treyphan
July 19th, 2008, 06:12 PM
Awesome thanks a million.

treyphan
July 20th, 2008, 03:08 AM
hmm went through the manual install and got to where I run


fglrxinfo

and get


fglrxinfo: error while loading shared libraries: libGL.so.1: cannot open shared object file: No such file or directory

steffen
August 4th, 2008, 04:06 PM
This worked up until the new unbreakable X.org. Since then I've had constant trouble with dual screen - switching on the fly does not work any more, TV-out does not work at all and I've had serious trouble getting 1680x1050 working. I was able to for some time, but now recently an Xorg update broke it.

Seems that with the new unbreakable X.org it is very hard to edit Xorg.conf by hand in order to force X to work in a specific way, but with the new GUI-system, it is impossible to force X into accepting new resolutions...

From the Compiz-Fusion Forum link in markbuntu's post, I see that what was missing was that AMD does not pick up edits done in Xorg.conf. I now found an old Xorg.conf file that worked prior to unbreakable X, inserted it in X11 and entered command

sudo aticonfig --input=/etc/X11/xorg.conf --tls=1
Now the update was picked up by X and I have dual screen working again :)

treyphan
August 4th, 2008, 04:45 PM
Any chance you could post that working config?

steffen
August 5th, 2008, 09:09 AM
Any chance you could post that working config?

Here you go:


# xorg.conf (xorg X Window System server configuration file)
#
# This file was generated by failsafeDexconf, using
# values from the debconf database and some overrides to use vesa mode.
#
# You should use dexconf or another such tool for creating a "real" xorg.conf
# For example:
# sudo dpkg-reconfigure -phigh xserver-xorg

Section "ServerLayout"
Identifier "Default Layout"
Screen 0 "Default Screen" 0 0
InputDevice "Generic Keyboard"
InputDevice "Configured Mouse"
InputDevice "Synaptics Touchpad"
EndSection

Section "Files"
EndSection

Section "Module"
Load "GLcore"
Load "glx"
Load "dbe"
Load "v4l"
EndSection

Section "InputDevice"
Identifier "Generic Keyboard"
Driver "kbd"
Option "CoreKeyboard"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "no"
Option "XkbOptions" "lv3:ralt_switch"
EndSection

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ImPS/2"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "true"
EndSection

Section "InputDevice"
Identifier "Synaptics Touchpad"
Driver "synaptics"
Option "SendCoreEvents" "true"
Option "Device" "/dev/psaux"
Option "Protocol" "auto-dev"
Option "HorizScrollDelta" "0"
EndSection

Section "Monitor"
Identifier "Failsafe Monitor"
VendorName "Generic LCD Display"
ModelName "LCD Panel 1680x1050"
HorizSync 31.5 - 65.5
VertRefresh 56.0 - 65.0
Gamma 1
ModeLine "800x600@56" 36.0 800 824 896 1024 600 601 603 625 +hsync +vsync
ModeLine "800x600@60" 40.0 800 840 968 1056 600 601 605 628 +hsync +vsync
ModeLine "1280x768@60" 80.1 1280 1344 1480 1680 768 769 772 795 -hsync +vsync
ModeLine "1280x720@60" 74.5 1280 1336 1472 1664 720 721 724 746 -hsync +vsync
ModeLine "1280x800@60" 83.5 1280 1344 1480 1680 800 801 804 828 -hsync +vsync
ModeLine "1440x900@60" 106.5 1440 1520 1672 1904 900 901 904 932 -hsync +vsync
ModeLine "1600x1024@60" 136.4 1600 1704 1872 2144 1024 1025 1028 1060 -hsync +vsync
ModeLine "1680x1050@60" 147.1 1680 1784 1968 2256 1050 1051 1054 1087 -hsync +vsync
EndSection

Section "Monitor"

#
Identifier "monitor1"
Gamma 1
EndSection

Section "Device"
Identifier "Failsafe Device"
Driver "fglrx"
BoardName "vesa"
Option "UseFastTLS" "1"
Option "EnableMonitor" "crt1,lvds"
BusID "PCI:1:0:0"
EndSection

Section "Device"

#
Identifier "device1"
Driver "fglrx"
BoardName "vesa"
BusID "PCI:1:0:0"
Screen 1
EndSection

Section "Screen"
Identifier "Default Screen"
Device "Failsafe Device"
Monitor "Failsafe Monitor"
DefaultDepth 24
SubSection "Display"
Virtual 1680 1050
Depth 24
Modes "1680x1050@60" "1600x1024@60" "1440x900@60" "1280x800@60" "1280x720@60" "1280x768@60" "800x600@60" "800x600@56"
EndSubSection
EndSection

Section "Screen"

#
Identifier "screen1"
Device "device1"
Monitor "monitor1"
DefaultDepth 24
EndSection

After backing up and replacing your old /etc/X11/xorg.conf with this one, type

sudo aticonfig --input=/etc/X11/xorg.conf --tls=1 and reboot with the external monitor plugged in. This worked for me. However, I had to visit the Gnome display config to set the new (but now available) screen resolution.

(note that under InputDevice section I have my keyboard set to "no". You might want to change this.

treyphan
August 5th, 2008, 01:34 PM
Curious -

What is the "failsafe" section referring to VESA? Is that incase the FGLRX goes south?

Why did you turn the keyboard option to off? Because of an eternal keyboard?

Sorry just trying to suck up as much knowledge as I can

:popcorn:

treyphan
August 5th, 2008, 04:37 PM
It worked! It actually worked. Thanks SO much for the help I am freekin thrilled.