ThinkWiki - User contributions [en]

Additional options for the radeon driver

2007-07-21T14:02:01Z

Fbianco: typo

Options for the [[radeon]] driver are documented on the radeon(4x) man page.

==External Monitors==

First of all, suppose you want to plug in your laptop into a projector occasionally, but you
don't want to restart X when you do so.
The easiest thing is to not use any of the CRT2 options and use

Option "MonitorLayout" "LVDS,NONE"

The vga port will carry the same signal as the laptop display
(at least on my T42p). If the projector does not support the resolution, you can change it using xrandr.

===Using Xinerama===

You can use '''MergedFB''' to provide dualhead '''Xinerama'''-like setups. MergedFB's pseudo-Xinerama is not Xorg server's Xinerama. You don't have to enable Xorg server's Xinerama to use MergedFB's pseudo-Xinerama. However, applications compiled with Xinerama support (Gentoo users USE="xinerama") can interpret pseudo-Xinerama hints, for example, to maximize to a single monitor instead of spanning two monitors.

The following (partial) '''Xorg''' config will make the Radeon card use '''1024x768''' on the internal lcd display and '''1280x1024''' on the external ('''Note''': only one screen/monitor section is needed (it controls the setup of the internal monitor) even though we have two displays):
'''N.B.:''' Modes used in the ''MetaModes'' also have to be present in the ''screen'' modes section.

Section "Device"
Identifier "ATI"
Driver "radeon"
'''# accelration'''
Option "AGPMode" "4"
Option "EnablePageFlip" "on"
Option "RenderAccel" "on"
'''# enable (partial) PowerPlay features'''
Option "DynamicClocks" "on"
'''# use bios hot keys on thinkpad (aka fn+f7)'''
Option "BIOSHotkeys" "on"
'''# enable radeon specific xinerama'''
Option "MergedFB" "true"
Option "CRT2Position" "RightOf"
Option "CRT2Hsync" "50-75"
Option "CRT2VRefresh" "30-82"
Option "MetaModes" "1024x768-1280x1024"
Option "MergedNonRectangular" "true"
BusID "PCI:1:0:0"
EndSection
Section "Monitor"
Identifier "InternalLCD"
Option "DPMS"
EndSection
Section "Screen"
Identifier "Default Screen"
Device "ATI"
Monitor "InternalLCD"
DefaultDepth 24
SubSection "Display"
Depth 24
Modes "1024x768"
EndSubSection
EndSection

Note: The '''CRT2''' directives always applies for the external monitor regardless of type (LCD, CRT...). The option '''MergedNonRectangular''' is needed to force the screens into two different sizes.

===External Monitors and Docking Stations/Port Replicators===
I seems that '''Xorg''' incorectly discovers the external displays when connected to a docking station/port replicator - the only solution to this problem (at least that I know of) is to start the laptop (and boot all the way into X) prior to inserting it in the dock.

It also happens that if you are attempting to use the mergedFB trick to
do dual head with out a docking station, you have to start X on the laptop
LCD first, then plug a monitor into the VGA port. If the external monitor
is already plugged in, the internal LCD will be blank.

I found that if I add '''Option "MonitorLayout" "LVDS, CRT"''' to my xorg.conf file - I don't have the 'blank' LCD panel problem when I plug the external monitor in before powering up. (Radeon 9600 M10 [RV350] with xorg 7.0.0). However - if you want anything other than 'Clone' mode of MergeFB, then you also have to make sure your "Modes" line in the "Screen" section contains the both modes defined in your MetaModes option.
<pre>
Option "MonitorLayout" "LVDS, CRT"
Option "MetaModes" "1024x768-1280x1024"
....
SubSection "Display"
Depth 24
Modes "1024x768" "1280x1024"
</pre>
This also resulted in my Notebook having a Virtual screen size of "2304x1024" when the external monitor is connected - but only 1024x768 when it's not connected. Until I did this - even with the external monitor disconnected - the virtual screen size was "2304x1024" and windows would open where I couldn't get to them.

===External Monitors and FireGL Boards with x.org 7===
x.org release 7, the modular release, broke mergedfb mode with FireGL boards (t4xp systems). Dual screen displays hard locked the machine in certain cases. This is fixed in x.org cvs. Fedora Core 5 (and possibly other distros using x.org 7) can get a new version of radeon_drv.so [http://www.marcuswatkins.net/firegl_xorg7_fedora.html here].

==AGP speed==

By default, the open source radeon driver forces 1x AGP speed. Quote from the developers:

tuning to the highest speed possible has caused hangs on some boxes, with no
discernable pattern, so we default to 'slow but safe' whilst giving the option
to go fast if the user wants to try it.

Higher speeds can be enabled by adding '''Option "AGPMode" "X"''' (where X is a number) in the '''Device''' section in {{path|/etc/X11/xorg.conf}}.

Section "Device"
Identifier "Videocard0"
Driver "radeon"
VendorName "IBM Thinkpad"
BoardName "ATIdd Mobility FireGL 7800"
'''Option "AGPMode" "4"'''
EndSection

With this option enabled (set to 4x speed), the X11 server should print ({{path|/var/log/Xorg.0.log}}):

(**) RADEON(0): Option "AGPMode" "4"
(**) RADEON(0): Using AGP 4x mode

==AGP Fast Writes==

By default, the open source radeon driver disables AGP Fast Writes. Fast Writes can be enabled by adding '''Option "AGPFastWrite" "yes"''' in the '''Device''' section in {{path|/etc/X11/xorg.conf}}.

Section "Device"
Identifier "Videocard0"
Driver "radeon"
VendorName "IBM Thinkpad"
BoardName "ATI Mobility FireGL 7800"
'''Option "AGPFastWrite" "yes"'''
EndSection

{{NOTE|With this one X hangs on startup (black screen) on my ThinkPad T42 (helios42)}}
{{NOTE|The same problem as above (X hangs on startup (black screen)) has been experienced on a ThinkPad T41p}}

==Dynamic Clock scaling==

Please see:

*[[How to make use of Graphics Chips Power Management features]] <tt>(save even more battery power)</tt>
*[https://bugs.freedesktop.org/show_bug.cgi?id=2187 Xorg bug] <tt>DynamicClocks may hang your machine</tt>

==Color Tiling==

ColorTiling is supposed to be enabled by default. But, it looks like setting it explicitely to "on" increases the FPS in glxgears.

Option "ColorTiling" "on"

==Acceleration Architecture==

By default, the XAA architecture is used. EXA is newer and supposed to have better performance. It looks like it reduces the FPS in glxgears (maybe because it disables Page Flip) but makes the Composite extension be fast.

Option "AccelMethod" "EXA"

==Page Flip==

Page Flip increases performance but is not always supported. It will be disabled if the EXA architecture is used.

Option "EnablePageFlip" "on"

==Video overlay==

When the video overlay is used (e.g., by most video players) in dual-screen configuration, the content will be shown only on one head (LCD or CRT) and the other will display a blank rectangle. To control which head displays the video, use the following:

Option "OverlayOnCRTC2" "on"

Note : You may want to have the video overlay on ''both'' Screens. Simply add the following 2 lines :

Option "OverlayOnCRTC1" "on"
Option "OverlayOnCRTC2" "on"

To switch on the fly, use these commands:

:{{cmd|xvattr -a XV_SWITCHCRT -v 0|}}   (LCD)
:{{cmd|xvattr -a XV_SWITCHCRT -v 1|}}   (CRT)

{{HINT|You can configure [[acpid]] to execute these commands automatically when the lid is opened or closed.}}

== Related Links ==
*[http://www.x.org/X11R6.8.2/doc/radeon.4.html xorg 6.8.2 Radeon manual page]

Installing Ubuntu 6.06 on a ThinkPad T43

2006-12-23T22:06:58Z

Fbianco: word spelling correction

Installation Log of {{Ubuntu}} 6.06 on a {{T43}}

__TOC__

==Overview==
Worked right out of the box
* 1400*1050 resolution
* Battery Management
* Ultra Nav (Trackpoint and synaptic touchpad)
* WLAN (Atheros, IBM 11a/b/g Wireless LAN Mini PCI Adapter II)
* Hibernate and Standby
* Fn keys (switch between monitors untested)
* Audio Keys
* ThinkLight

Was easy or required some work
* easy ubuntu (includes skype and some codecs)
* middle key of Ultra Nav (Trackpoint)
* ATI 3D Acceleration (Mobility Radeon X300)
* Xgl / Compiz

Still TODO
* Fingerprint reader
* Forward/Backward keys, Access IBM Key

Untested
* Bluetooth (light indicates working)
* Modem
* IrDA
* TV out, VGA out

Failed / still requires work
* Active Protection System (solved 'out of the box' in edgy)

==Installation==

===Recovery copy of data===

Before installing a new OS you should create a security copy of your old system. As the IBM Rescue and Recovery tool quit with an error message I used the Ubuntu live CD, mounted and cd'ed into my external hard drive and ran the following command:

$ cmduser|sudo dd if=/dev/sda1 | gzip | dd of=./sda1.img

where /dev/sda1 is the device with my windows partition and sda1.img the gzipped security copy.
In case of problems one can now restore lost information using

$ sudo dd if=./sda1.img | gzip -d | dd of=/dev/sda1

After creating the recovery copy we are ready to resize the existing windows partition. This article assumes you want to keep your IBM Rescue and Recovery Partition, shrink in size, but keep your windows partition and create a new partition for Dapper Drake.

===Resizing Partitions===

Probably the best choice is now to boot from the alternate CD (read [http://gawrysiak.org/corvus/?p=4] to know why) and use it to resize the existing NTFS partition. Unfortionately in my case it didn't work. So I booted the Live CD, but gparted and parted refused to resize my Windows, too. If the same happens to you, use the example [http://crashrecovery.org/CrashRecoveryKit/iso/2.4.21/HOWTO.ntfs.html here] to know how to resize it "manually" using ntfsresize and fdisk.

After resizing your windows partition you should reboot window to check everything's in order. It probably will run checkdisk and reboot two times - according to experieces you can read in the web, you should better let windows do that.

===Installation of Ubuntu===

Now it's the time to install Ubuntu. I used the alternate CD for that because I chose to install grub into the Linux partition and not into the Master Boot Record ([http://gawrysiak.org/corvus/?p=4 read why]). The graphical LiveCD installer automatically installs grub to the MBR. If you want to use grub in the MBR read [[Rescue and Recovery]]. There is a description of what you have to do in order to still be able to use the IBM R'n'R partition.

* remember that you're installing GRUB to an '''sda''' mount, not an hda mount like the GRUB installer will prompt you for what you should enter after you tell GRUB not to install in the MBR will be something like this:

/dev/sda3

After the installation is finshed it will reboot your system. Now windows should start. In my case it didn't, but playing around, booting into the R'n'R partition, starting PC Doctor and doing some Diagnostics (no changes) somehow and surprisingly made windows boot again.

To boot you freshly installed Linux you have to reboot the LiveCD one last time. Use

$ sudo dd if=/dev/sda5 of=ubuntu.img bs=512 count=1

to copy the first block of grub into an image file and use e.g. an usb flash drive to transfer it to your newly booted windows. Copy paste the image to C:\ and add the following line to your C:\boot.ini:

C:\ubuntu.img="Ubuntu Dapper Drake"

At the next restart the windows boot manager should now welcome you with the choice to boot windows or ubuntu. Choose ubuntu to (finally ;-) boot your newly installed linux for the first time.

==Configuration==

===Easyubuntu===

[http://easyubuntu.freecontrib.org/ Easyubuntu] is a helpful tool to install Skype, codecs, ATi 3D drivers and further things that can make your live easier.

===Keyboard Layout===

My T43 has a German keyboard layout. Most worked just fine, but some keys (in my case the "at" and the "tilde" among others) just didn't. If the same happens to you, just go to the Gnome System Preferences menu and choose the right layout for your keyboard (probably named after your language and something like eliminate-dead-keys or no-dead-keys)

===3D Acceleration and Xgl/Compiz===

If you have an ATI Radeon X300, use [http://wiki.cchtml.com/index.php/Ubuntu_Dapper_Installation_Guide this explanation] to make your hardware 3d acceleration work.

To test if it works type

$ glxinfo | grep rendering

The answer should be: "direct rendering: Yes". If it says "No", you don't have 3D acceleration.

If you want to install Xgl/Compiz like me, [http://www.compiz.net/viewtopic.php?id=389 here] is a great installation help for ATI cards (use way two.)

If you have another card you might find a good explanation [http://ubuntuforums.org/showthread.php?t=148351 here].

===3D Acceleration using open-source radeon driver and AIGLX/Beryl===
From my experience it was better to use "radeon" driver, the open source one, on top of "drm" driver,
also part of the kernel, instead of fglrx. I get direct rendering and similar performance---maybe fglrx
driver gives 50-100 more fps. The most annoying thing about fglrx driver is that it can cause hard locks
every now and then and your suspend doesn't work properly...believe me I tried the ones that the Thinkwiki
says supposed to work.

$ glxinfo | grep rendering
direct rendering: Yes
OpenGL renderer string: Mesa DRI R300 20060815 TCL

Use the directions in the previous section to install fglrx driver, library. (I just installed them from shell
rather than making them into packages, I found the uninstall script in /usr/share/fglrx to work properly).
FYI, I used the version 8.26.18-x86.

If you don't get rendering use ''LIBGL_DEBUG=verbose glxinfo'' to diagnose the problem. The most common problem
is that xorg looks for DRI library files in ''/usr/X11R6/lib/dri'', which didn't exist for me. A simple way to
solve this is creating a symlink to where those files are located (/usr/lib/dri/):
$ cd /usr/X11R6/lib/
$ ln -s /usr/lib/dri/ .

Open your ''/etc/modules'' file and add these lines and comment 'fglrx' if there is any:
intel-agp
drm
radeon

Also, from my experience, it was better to use '''AIGLX''' than Xgl and '''Beryl''' instead of Compiz
in terms of performance and integration---things like suspend and hibernate. And you can use nice
start/shutdown scripts to disable beryl-manager since it can cause hang when you resume from suspension.
For more information about suspend/resume scripts, [http://ubuntuforums.org/showthread.php?p=1656484 here].
For more information about installing aiglx and beryl, see [http://wiki.beryl-project.org/index.php/Install/Ubuntu/Dapper/AiGLX here]).

ATI X300 is pretty pitiful though...I get around ~570 average FPS when running AIGLX/beryl
$ glxgears
2850 frames in 5.0 seconds = 569.997 FPS
2925 frames in 5.0 seconds = 584.925 FPS
2904 frames in 5.0 seconds = 580.741 FPS
2923 frames in 5.0 seconds = 584.524 FPS...
With metacity (default Gnome window manager) I get around slightly over 1000 FPS
$ glxgears
5073 frames in 5.0 seconds = 1014.423 FPS
5073 frames in 5.0 seconds = 1014.531 FPS
5252 frames in 5.0 seconds = 1049.326 FPS
5803 frames in 5.0 seconds = 1160.502 FPS...

If anyone know how to get rid of the weird warning, I would really appreciate it:
libGL warning: 3D driver claims to not support visual 0x4b

I added the following options under ati Device section of ''/etc/X11/xorg.conf''
Option "EnablePageFlip" "True"
Option "ColorTiling" "True"
Then after that the performance boosted by quite a bit:
7026 frames in 5.0 seconds = 1405.147 FPS
7058 frames in 5.0 seconds = 1411.493 FPS
7062 frames in 5.0 seconds = 1412.393 FPS...

===Active Protection System===

See end of this chapter if you have ubuntu edgy eft.

The T43 has a great system to protect your hard disk, the Active Protection System APS. [[How to protect the harddisk through APS]] describes how you can use it.

{{WARN|Only follow these instructions if you know what you are doing!}}

If you didn't until now you will have to install make, libc, gcc, ... Best is you use

$ sudo apt-get install build-essentials

Determine your kernel version using

$ uname -a

You should see somthing like

Linux ibm 2.6.15-26-386 #1 PREEMPT Thu Aug 3 02:52:00 UTC 2006 i686 GNU/Linux

Install the kernel sources "linux-source" e.g. using Synaptic.
Download the right kernel patch from [[HDAPS#Applications]] according to your kernel version and system (I chose "sata/ide disk protection patch for 2.6.15")
adapt following steps to your needs:

$ cd /usr/src/
$ sudo su
# bunzip2 linux-source-2.6.15.tar.bz2
# tar -xf linux-source-2.6.15.tar
# cd linux-source-2.6.15
# patch -p1 -l < /home/silvan/hdaps_protect.20060118.patch

You should see several lines with the word "suceeded". If you see many "failed" instead you probably chose the wrong patch for your kernel. You can use the --dry-run option to try it out first. If you get errors in the following steps you should better stop unless you know what you are doing.

# make clean
# make oldconfig # use old config, ask for new items, only
# make clean
# make # takes quite a long time, several minutes
# make modules
# make modules_install

Afterwards use the debian sources mentioned in [[How to protect the harddisk through APS]] to install the user space deamon hdapsd and the gnome applet gnome-hdaps-applet, e.g. using Synaptic.

If this worked for you, you can find some nice applications at [[HDAPS#Applications]] which make use of the APS.

{{HELP|For me unfortunately it didn't work as making the patched kernel failed. Please update ths section if you have different experiences and a better, more detailed working explanation.}}

{{NOTE|After I updated to edgy eft hdaps works without further work: edgy comes with hdaps built in. You can check if it is working by installing hdaps-utils

# sudo apt-get install hdaps-utils

and calling

# hdaps-gl

for a nice 3D show. If it is not, load the kernel module using

# sudo modprobe hdaps

and it should work. But if you want to use hdaps for disk protection, you have to recompile your kernel in edgy, too. Follow this post for an howto:

}}
[http://ubuntuforums.org/showthread.php?t=122863 Howto for edgy]

===Track Point Middle Key Scrolling===

In my case the track point worked out of the box, but the middle mouse button for scrolling did not. [[How to configure the TrackPoint]] explains how to solve this. The steps you need to follow are in section "Using the X server (kernel 2.6.11+)".
However you don't need to follow the steps in "EmulateWheelTimeout temporarily broken (-> fix for Ubuntu Dapper)" as this is fixed already if you have all your packages up-to-date.

Follow the instructions in the sections "Configure firefox for using trackpoint horizontal scrolling" and "Configure Opera for using trackpoint horizontal scrolling" as well, if you are using one of the two browsers.

===Fingerprint Reader===
{{Todo|Needs editing}}
Look at [[How to enable the fingerprint reader]] if you want to use your fingerprint reader.

===Forward / Backward Keys, Access IBM===
{{Todo|Needs editing}}
You'll find more here: [[How to get special keys to work]]

===IrDA===
{{Todo|Needs editing}}
Find information here: [[How to make use of IrDA]]

===VGA out ===
{{Todo|Needs editing}}
I didn't try it, but it looks easy: [http://help.nceas.ucsb.edu/index.php/Enable_vga_out_on_ATI_Thinkpads How to enable VGA out]

==References==
* [http://gawrysiak.org/corvus/?p=4 Dapper Drake on T42]

==External Sources==
* This guide is listed at the [http://tuxmobil.org/ibm.html TuxMobil Linux laptop and notebook installation survey (IBM/Lenovo)].

Hope this helped somehow :-)
tec

Talk:Problems with fglrx

2006-02-26T12:36:45Z

Fbianco: /* 8.20.8 and later works with current Debian sid packages */

== using kernel AGP vs fglrx AGP ==

Anyone know whether this makes a performance and/or stability difference?

== 8.20.8 and later works with current Debian sid packages ==

<pre>
spiney@t43p:~$ dpkg -l xserver-xorg
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name Version Description
+++-============================-============================-==================
ii xserver-xorg 6.9.0.dfsg.1-2 the X.Org X server
spiney@t43p:~$ fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: MOBILITY FireGL V3200 Pentium 4 (SSE2) (FireGL) (GNU_ICD)
OpenGL version string: 1.3.5519 (X4.3.0-8.20.8)
</pre>

--[[User:Spiney|spiney]]
----

Ahh - thanks for the info. You perhaps compiled the modules for the drivers yourself and did not use the debian packaged fglrx-driver? Thus, it must be an unneeded limitation on the debian packaged driver which limits its installation... Full listing at http://packages.debian.org/unstable/x11/fglrx-driver which lists as required packages:

xserver-xorg (<< 6.8.99)
the X.Org X server
xserver-xorg (>= 6.8.0)

The first limitation (<<6.8.99) is what prevents installation. I'm sure I could force apt to install it, but I may go back to compiling the modules myself, as using fglrx 8.20.8 with kernel 2.6.15 needs a small patch to compile correctly anyway... --[[User:gsmenden|gsmenden]]

Spiney, where exactly do you have your package from? I re-build the 8.20.8-package from debian with the <<6.8.99 dependecy removed, but when I try to run X, I get
[R200Setup] X version mismatch - detected X.org 7.0.0.0, required X.org 6.8.0.0
(EE) Failed to load module "fglrx" (module requirement mismatch, 0)
Any hints? --[User:nomeata|nomeata]

I used the ati-installer (the huge download), created a Debian sid package and installed it, but got the same error. The installer seems to fetch the wrong driver version from the archive, so I extracted it with

{{cmd|./ati-driver-installer-8.20.8-i386.run --extract <sometempdir>|}}

and put the necessary files from the created {{path|<sometempdir>/x690}} subdirectory into {{path|/usr}} by hand. All IIRC, it's been some time since. :)

--[[User:Spiney|spiney]] 07:29, 11 Jan 2006 (CET)

Thanks for the pointer. This is how you get proper debian packages out of the ati-installer:
./ati-driver-installer-8.20.8-i386.run --extract fglrx-tmp
cd fglrx-tmp
$editor packages/Debian/ati-packager.sh # in the line "sid|unstable) X_DIR=x680;;", put a x690 for the x680
./fglrx-tmp/packages/Debian/ati-packager.sh --buildpkg sid
cd ..
sudo dpkg -i fglrx-kernel-src_8.20.8-1_i386.deb fglrx-driver_8.20.8-1_i386.deb
--[[User:Nomeata|Nomeata]] 00:35, 13 Jan 2006 (CET)

----

I had to do following steps :

$ ./ati-driver-installer-8.20.8-i386.run --extract fglrx-tmp
$ cd fglrx-tmp
$ ''editor'' packages/Debian/ati-packager.sh # in the line "sid|unstable) X_DIR=x680;;", put a x690 for the x680
$ ./packages/Debian/ati-packager.sh --buildpkg sid
$ cd /tmp
$ sudo dpkg -i fglrx-kernel-src_8.20.8-1_i386.deb fglrx-driver_8.20.8-1_i386.deb
--[[User:Fbianco|Fbianco]] 13:36, 26 February 2006 (CET)

----

Nice - confirmed works on my T43p running sid. From then on (or until 8.21.x comes out) you'll have to tell apt to hold back fglrx-driver package, or it will try to "update" fglrx-driver to 8.20.8-1.1 and therefore revert back to the problematic drivers.
--[[User:gsmenden|gsmenden]]
----

Thanks for the info, Nomeata, that's a lot cleaner a solution than my manual way.

--[[User:Spiney|spiney]] 08:32, 13 Jan 2006 (CET)
----

To get this working under 2.6.15 with x.org 6.9, you will also need to apply a small patch - there is a link on the main article page. After you install the fglrx-driver package with the 6.9 versioning hack above, go to
/usr/src/modules
and copy the patch here. Modify the first two lines of the patch file to take out the "build_mod" directory, e.g. first line should begin with
--- fglrx.orig/firegl_public.c
and call it with the -p0 strip option. It should patch the firegl_public.c file cleanly. You can then install as usual for your kernel (2.6.14.x or 2.6.15) using module-assistant.

Update - although X will come up in kernel 2.6.15 with the fglrx drivers patched as above, there is some strange behavior exhibited in all of X apllications - frequent hanging of applications when closing windows. Reverting back to the radeon driver in 2.6.15 solves these - so it is likely the ATI proprietary driver causing some problems.

Yet another update - fglrx 8.21.7 is out as of 1/19/2006, now supporting OpenGL 2.0, so eventually we will have beautiful complex shading / fog effects on Linux, too. It works well with X.Org 6.9 out of the box.

Unfortunately, this version gives the same problems when used (unpatched) with kernel 2.6.15 with strange lockups occasionally requiring reset of X. I have not tried this with the ~10 line patch listed on the main site, but that patch not work for me with 8.20.8. Anybody else have experience with 2.6.15 and fglrx?

Yay - new version out - 8.22.5 - works well with 2.6.15.x. Finally, running a plain-vanilla kernel on a T43p! (SATA+libata passthrough+SMART in mainline, 3d accel drivers up to date. Linux life is good.)

--[[User:gsmenden|gsmenden]] 12:39, 9 Feb 2006 (EST)
----

I don't know which patch you mean exactly (10 lines? the patch from lkml is just one line changed, no?), but I've been using 8.20.8 with 2.6.15 for quite some time (actually started with some -rc version IIRC), no lockups at all. No idea about 8.21.7 though, because I switched to 2.6.16-rc1 and can't compile the fglrx module at the moment, need to investigate the cause.

--[[User:Spiney|spiney]] 07:24, 21 January 2006 (CET)
----

Ok - strange. Yeah, the actual change is only one line, the rest is just commenting, etc. The lockups that I get are quite rare, but flightgear occasionally gives a hard lock. glxgears and fgl_glxgears work fine, netscape occasionally will hard-lock, and strangely enough issuing a shutdown command often makes the display blank and hard lock. I can't reproduce them too consistently, but these _never_ occur with the radeon driver / mesa or under 2.6.14.x.

Unfortunately vanilla 8.21.7 with kernel 2.6.15.1 (Xorg 6.9) gives the same X lockups.

--[[User:gsmenden|gsmenden]] 11:36, 21 Jan 2006 (EST)
----

I can't compile the 8.21.7 driver modules with 2.6.15.1 at all. They compile with 2.6.14.4 cleanly and 8.20.8 compile with 2.6.15.1.
What I don't understand though is, that when I let the ATI installer build debian packages, it does so without hassle, but the packages don't work.
(this is about 8.21.7 - 2.6.15.1) Also patching doesn't seem to help. It shouldn't of course.

--[[User:Rasto|Rasto]] 15:04, 23 Jan 2006 (CET)

I looked at the compile problems last night. I have no idea, how it is possible that it works for other people with 2.6.15, perhaps when you install
precompiled modules? I don't really understand how that ati-installer thing works. Anyway. This may solve the problems with 8.21.7 and 2.6.15-
it is just two minor line changes (+ the one line patch with little extra), but now it compiles. pm_register and similar were moved to linux/pm_legacy.h
in 2.6.15, so that's one problem. It also reports unknown symbol verify_area, but this should not pose a problem, as it is already obsolete and redundant.
If you feel, that the one line should be left as the separate patch, copy it somewhere else and change it. It's here [http://people.ksp.sk/~rasto/fglrx_with_2.6.15.patch], but I'll put it on the main page as well.

--[[User:Rasto|Rasto]] 18:29, 25 Jan 2006 (CET)

== Disabling the external VGA port? ==

Does anyone know how disable the VGA port ''completely'' even when a cable is attached? Fiddling around with the DesktopSetup and ForceMonitor options didn't do the trick for me, and the MonitorLayout option found in some documentation is no longer valid in the current fglrx driver.

--[[User:Spiney|spiney]] 19:42, 10 Jan 2006 (CET)
----

== Debian-specific script to switch fglrx<->radeon ==

Don't know where to put it exactly, but if someone's interested (and using Debian), I've put up a [http://linux.spiney.org/debian_gnu_linux_on_an_ibm_thinkpad_t43p_graphics_card_switching_fglrx_radeon script for easily switching graphics driver configurations]. Feedback appreciated (altho I haven't got any to the xscreensaver patch ;)), especially if someone could do something similar for other distributions (Gentoo being half-way there it seems) and incorporate it into the script.

--[[User:Spiney|spiney]] 15:25, 17 January 2006 (CET)
----

----
==Compile ATI driver???==
How can you compile a binary only distributed driver? If I'm not getting something wrong, please change the formulation of the just added info.
[[User:Wyrfel|Wyrfel]] 20:10, 25 January 2006 (CET)
----
[http://xoomer.virgilio.it/flavio.stanchina/debian/fglrx-installer.html#overview1]
"The driver as a whole is made of three main components: the driver proper, a replacement libGL and a kernel module. The driver and libGL are in the fglrx-driver package, the kernel module's source code is in the fglrx-kernel-src package."
--[[User:Dunno|Dunno]] 23:49, 13 February 2006 (CET)
----
Yepp, my fault, didn't think of the kernel part when i wrote that. [[User:Wyrfel|Wyrfel]] 02:50, 14 February 2006 (CET)
----

== On Kernel 2.6.16(_rc4-mm1) fglrx doesnÂ´t load anymore ==

Hi,

if i emerge ati-drivers 8.22.5 and try to modprobe it on Kernel 2.6.16_rc4-mm1 i get the following console output:
<pre>
FATAL: Error inserting fglrx (/lib/modules/2.6.16-rc4-mm1/video/fglrx.ko): Unknown symbol in module, or unknown parameter (see dmesg)
</pre>
my dmesg Output reads:
<pre>
fglrx: Unknown symbol inter_module_unregister
fglrx: Unknown symbol inter_module_get_request
fglrx: Unknown symbol inter_module_put
fglrx: Unknown symbol inter_module_register
</pre>
from the ati-driver wiki i know that the driver runs on 2.6.16 up to rc3. But on the mm Series it doesnt run since 2.6.15.4-mm4.

Help would be appreciated...

Thanks and Greets

Oli