PDA

View Full Version : 8.42.3 and FireGL


nicweb
10-23-2007, 01:26 PM
If anyone tries 8.42.3 on FireGL cards please post your results here...

Michael
10-23-2007, 01:28 PM
8.43 adds official FireGL certification

slickhenry
10-23-2007, 01:37 PM
doesn't work, but might get it going with some pci-id-hacks.

chrisr
10-23-2007, 01:41 PM
8.43 adds official FireGL certification

Sorry, sick and **&%! tired of waiting. How do I hack it?

Michael
10-23-2007, 01:42 PM
Sorry, sick and **&%! tired of waiting. How do I hack it?

I know this is not what you want to hear, but I know the wait for fglrx 8.43 will be worth it for FireGL along with other features coming.

chrisr
10-23-2007, 01:51 PM
I know this is not what you want to hear, but I know the wait for fglrx 8.43 will be worth it for FireGL along with other features coming.

You didn't spend a small fortune on a laptop you can't use for months on end! (Although I doubt that NVIDIA graphics would have been much better.)

Now how do I hack it?

d2kx
10-23-2007, 01:57 PM
Ask Kano, The Master.

slickhenry
10-23-2007, 02:18 PM
and success. I do get an AMD Unsupported Hardware in the bottom right corner tho'

I followed the steps from http://www.phoronix.com/forums/showthread.php?t=5203

but applied the patch manually.

now let's test aiglx on this z61p :)

chrisr
10-23-2007, 05:10 PM
Following these instructions and using a chip ID of "0x71D5" (Radeon X1700) for my FireGL V5250, I have managed to:

- enable DRI
- enable AIGLX
- run Compiz
- run celestia with OpenGL 2.0 support (although it interacts badly with Compiz)
- run glxgears with approx 2400 fps

This is all great! However, it fails at the final hurdle of running World of Warcraft, where it presents me with a completely black login screen. I am thinking that this must be a configuration issue, because everything else is working so well.

Obviously I have the "unsupported hardware" rectangle in the bottom RH corner of the screen, and these messages are written to my kernel log:

[fglrx] Maximum main memory to use for locked dma buffers: 1898 MBytes.
[fglrx] ASYNCIO init succeed!
[fglrx] PAT is enabled successfully!
[fglrx] module loaded - fglrx 8.42.3 [Oct 19 2007] on minor 0
BUG: sleeping function called from invalid context at include/asm/semaphore.h:99
in_atomic():1, irqs_disabled():0
[<f924b178>] __ke_down_struct_sem+0x14/0x2b [fglrx]
[<f924fd4f>] firegl_remove_all_drawables+0x3f/0x100 [fglrx]
[<f92527c9>] firegl_release_helper+0x6b9/0xa20 [fglrx]
[<f9255e7b>] firegl_takedown+0x6b/0xc50 [fglrx]
[<f925568f>] firegl_release+0x12f/0x190 [fglrx]
[<f9249c4c>] ip_firegl_release+0xf/0x12 [fglrx]
[<c0167302>] __fput+0xb5/0x15d
[<c0164f00>] filp_close+0x51/0x58
[<c010702b>] do_syscall_trace+0x13d/0x182
[<c0165e5b>] sys_close+0x67/0x9e
[<c0103ee2>] syscall_call+0x7/0xb
=======================
BUG: sleeping function called from invalid context at include/asm/semaphore.h:99
in_atomic():1, irqs_disabled():0
[<f924b178>] __ke_down_struct_sem+0x14/0x2b [fglrx]
[<f924fd4f>] firegl_remove_all_drawables+0x3f/0x100 [fglrx]
[<f92527c9>] firegl_release_helper+0x6b9/0xa20 [fglrx]
[<f9255e7b>] firegl_takedown+0x6b/0xc50 [fglrx]
[<f925568f>] firegl_release+0x12f/0x190 [fglrx]
[<f9249c4c>] ip_firegl_release+0xf/0x12 [fglrx]
[<c0167302>] __fput+0xb5/0x15d
[<c0164f00>] filp_close+0x51/0x58
[<c010702b>] do_syscall_trace+0x13d/0x182
[<c0165e5b>] sys_close+0x67/0x9e
[<c0103ee2>] syscall_call+0x7/0xb
[<c02a0000>] unix_shutdown+0x113/0x13b
=======================
[fglrx] Maximum main memory to use for locked dma buffers: 1898 MBytes.
[fglrx] Reserve Block - 0 offset = 0Xfffb000 length = 0X5000
[fglrx] Reserve Block - 1 offset = 0X0 length = 0X1000000
[fglrx] Reserve Block - 2 offset = 0Xffbb000 length = 0X40000

Those BUGs worry me...:confused:

wlindner
10-23-2007, 06:25 PM
If anyone tries 8.42.3 on FireGL cards please post your results here...

I tried the patch with the new drivers on my Firegl V3200, but it didn't work.... Anyone have any suggestions other than wait another month?

chrisr
10-23-2007, 06:40 PM
I am finding that the dynamic linker is unwilling to find libGL.so.1.2 in the /usr/lib/fglrx directory, despite there correctly being an entry in /etc/ld.so.conf.d that lists the directory name. I was forced to add a symlink /usr/lib/libGL.so.1 to the /usr/lib/fglrx/libGL.so.1.2 shared object.

When I tried to run prelink on glxinfo, I received the following error:

prelink: /usr/bin/glxinfo: Cannot prelink against non-PIC shared library /usr/lib/libGL.so.1

wlindner
10-23-2007, 06:45 PM
I am finding that the dynamic linker is unwilling to find libGL.so.1.2 in the /usr/lib/fglrx directory, despite there correctly being an entry in /etc/ld.so.conf.d that lists the directory name. I was forced to add a symlink /usr/lib/libGL.so.1 to the /usr/lib/fglrx/libGL.so.1.2 shared object.

When I tried to run prelink on glxinfo, I received the following error:

prelink: /usr/bin/glxinfo: Cannot prelink against non-PIC shared library /usr/lib/libGL.so.1

I had that same problem, but gutsy had switched me over to vesa drivers..... this bulletproof-x stuff is kinda a pain, you have to run displayconfig-gtk as root and set the driver used back to the opensource ati drivers and maybe set up xorg.conf how it was before trying to move to fglrx and uninstalling fglrx.... OR, just revert back to fglrx

chrisr
10-23-2007, 06:51 PM
I had that same problem, but gutsy had switched me over to vesa drivers.....

If I don't link manually to libGL.so.1.2 then programs like glxinfo and glxgears completely refuse to run because they cannot locate the libGL.so.1 library. So there's no possibility of being secretly switched back to Mesa.

mintcoffee
10-23-2007, 09:01 PM
Hmm i can't seem to get direct rendering working for my V5200 on Arch Linux. Anyone have any success?

chrisr
10-24-2007, 03:31 AM
Hmm i can't seem to get direct rendering working for my V5200 on Arch Linux. Anyone have any success?

My direct rendering didn't work straight away because I only upgraded the RPMs and forgot that I would need to unload the fglrx.ko from v8.40.4 as well.

Then I had to install a symlink in /usr/lib to /usr/lib/fglrx/libGL.so.1 by hand.

Which ChipID are you using in your xorg.conf file?

Llogi
10-24-2007, 04:47 AM
Same problem here. Mobility FireGL T2 with ChipID 1002:4e54, using the Mobility 9600 ID: 1002:4c66.

My name ist Llogi, btw. Following this forum for some month now. That damn driver led me to my first post here.

At first I applied Ambro814s patch http://www.phoronix.com/forums/showthread.php?t=5203.

Instead of "./ati-installer.sh 8.41.7 --install" I built the package using "./ati-installer.sh 8.41.7 --buildpkg Ubuntu/gutsy" following the instructions from here: http://wiki.cchtml.com/index.php/Ubuntu_Gutsy_Installation_Guide

I even linked the libGL like You told some posts before.

Unfortunatley I don't even see the XServer. I get kicked to console before the login-screen appears.


Questions: how EXACTLY do I have to type the ChipID? 1002:4c66, 0x4c66 or just 4c66?

BTW: Following exatly the instruction of Ambro814 with "--install" instead of "--buildpk" did not work either.


Any help is appreciated.
Thanks

Llogi
10-24-2007, 06:40 AM
Post has not been eaten. Sorry for doubleposting.

chrisr
10-24-2007, 08:15 AM
Same problem here. Mobility FireGL T2 with ChipID 1002:4e54, using the Mobility 9600 ID: 1002:4c66.

I'm not familiar with that one, so I don't know whether your new chip ID is appropriate. I deduced mine by browsing the Xorg.0.log file to discover both the chip name underlying my laptop's onboard graphics device (M66), as well as all other ATI products using the exact same chip (e.g. Radeon X1700). Then I looked up the PCI ID of a supported X1700 device in /usr/share/hwdata/pci.ids .

Questions: how EXACTLY do I have to type the ChipID? 1002:4c66, 0x4c66 or just 4c66?

I believe it's:

ChipID 0x4c66

chrisr
10-24-2007, 08:20 AM
Instead of "./ati-installer.sh 8.41.7 --install" I built the package using "./ati-installer.sh 8.41.7 --buildpkg Ubuntu/gutsy"

Shouldn't that have been

./ati-installer.sh 8.42.3 --buildpkg Ubuntu/gutsy

???

Llogi
10-24-2007, 08:29 AM
The Chip Id should be correct:
scanpci and http://www.thinkwiki.org/wiki/ATI_Mobility_FireGL_T2 are identical. The wiki says "Chipset: ATI RV350 (M10) - Similar to Radeon 9600"


Shouldn't that have been

./ati-installer.sh 8.42.3 --buildpkg Ubuntu/gutsy

???

Oh sure. I just copied that from the cchtml-wiki. Building the package, I used the right number.

Btw: here is, what the Xorg.log tells me
http://ubuntuusers.de/paste/16774/

I'm not that good in reading log-files. "But Fatal server error: no screens found" does not sound to good.

chrisr
10-24-2007, 08:52 AM
(WW) fglrx: ChipID 0x4C66 in Device section "ATI Technologies Inc M10 NT [FireGL Mobility T2]" isn't valid for this driver
(EE) No devices detected.

The fglrx driver doesn't support the ChipID 0x4c66 either, because it belongs to another FireGL device. You need to find one that it does support :).

Llogi
10-24-2007, 08:53 AM
Hoho pretending to be a X600 (ID 0x3150) DOES WORK.

Just wanted to tell. Should be more people out there with a Mobility FireGL T2.

planetf1
10-26-2007, 06:28 AM
Following these instructions and using a chip ID of "0x71D5" (Radeon X1700) for my FireGL V5250, I have managed to:

Hi Chris,
That would be a T60p?

I built a modified 8.42.3 for the FireGL V5250 also.

Out of interest I used 0x71c5 (X1600 I think) for my V5250 - I *think* that's closer?

I was after basic desktop with
- suspend/resume
- ability to dynamically flip to dual screens
and compiz (fusion) would be nice
Good GL (Secondlife) would be even better
As would video

Right now 8.35 is the best I've got on RHEL 5.1

Could you possibly share your "best so far" xorg.conf?

I'm going to try some experiments tonight - need to get a real days work done first ;-)

- Nigel.

chrisr
10-26-2007, 07:34 AM
Out of interest I used 0x71c5 (X1600 I think) for my V5250 - I *think* that's closer?
I'm not sure about that. The Xorg.0.log file says that the V5250 is based upon the M66GL chipset, as is the X1700. But there seem to be many variants of the T60p; mine is a widescreen with native 1680x1050 resolution.

I was after basic desktop with
- suspend/resume
- ability to dynamically flip to dual screens
and compiz (fusion) would be nice
Good GL (Secondlife) would be even better
As would video

Could you possibly share your "best so far" xorg.conf?

I didn't test suspend/resume or dual screens, but AIGLX and compiz both worked OK, as did celestia (native OpenGL application). World of Warcraft gave a completely black screen, and glxgears gave about 2400 fps. I can't remember my Device section, but I removed all of the special "hackish" options needed by earlier versions and set the "Fast TLS" option to 1 instead of 2. VideoOverlay was on, OpenGLOverlay was off.

Textured video playback crashed at the very end.

planetf1
10-26-2007, 07:46 AM
I'm not sure about that. The Xorg.0.log file says that the V5250 is based upon the M66GL chipset, as is the X1700. But there seem to be many variants of the T60p; mine is a widescreen with native 1680x1050 resolution.

Ok. I appear to have
(II) fglrx(0): VESA VBE OEM Product: M56GL
which is a T60p model 2008 1600x1200.

I'm pretty sure X1600 is also a M56 variant, so hence why I chose this.

Guess as you say T60p != T60p ..



I didn't test suspend/resume or dual screens, but AIGLX and compiz both worked OK, as did celestia

Thanks, I'll report back later/tomorrow

I can't remember my Device section, but I removed all of the special "hackish" options needed by earlier versions and set the "Fast TLS" option to 1 instead of 2. VideoOverlay was on, OpenGLOverlay was off.

Thanks, will try with some basic options and work up.

planetf1
10-26-2007, 07:49 PM
Thanks, I'll report back later/tomorrow


Pretty disasterous.

I couldn't get suspend/resume working ok with this driver. I tried vga=0 kernel option, but no joy - the screen would always be black after resume.

That's a blocking issue for me - no amount of increased performance, glx etc will make a difference.

So -- yet again -- I'm back to 8.35 as the best so far.

I also tried the radeon driver - didn't realise this doesn't handle this chip.

Have to just wait for 8.43...44...45....46.... sigh.

ambro814
10-27-2007, 06:40 AM
hey guys, if you haven't noticed I've described a better method that doesn't need you to specify any pci id: http://www.phoronix.com/forums/showthread.php?t=6091.
It works great on my Thinkpad T60p.

planetf1
10-27-2007, 07:09 AM
hey guys, if you haven't noticed I've described a better method that doesn't need you to specify any pci id: http://www.phoronix.com/forums/showthread.php?t=6091.
It works great on my Thinkpad T60p.

Hi, I did notice - it's obviously much easier to patch - not having to enter an id, but once that is done, is it working any different?

Specifically
a) Do you know what chipset you have in your T60p - I have the V5200 (lcd 1600x1200)
b) Have you tried suspend/resume and got that to work - specifically under RHEL or Fedora?

ambro814
10-27-2007, 07:59 AM
Hi, I did notice - it's obviously much easier to patch - not having to enter an id, but once that is done, is it working any different?

Specifically
a) Do you know what chipset you have in your T60p - I have the V5200 (lcd 1600x1200)
b) Have you tried suspend/resume and got that to work - specifically under RHEL or Fedora?

lspci says: ATI Technologies Inc M56GL [ATI Mobility FireGL V5200]
and it's also 1600x1200.
Pci id is 0x71c4.
Suspend/resume works flawlessly with X running, I'm using gentoo with kernel suspend2-sources-2.6.22-r2.

ambro814
10-27-2007, 08:05 AM
I meant Suspend2 works great, but also does ACPI suspend.

ambro814
10-27-2007, 08:23 AM
Here's my xorg.conf, it's pretty basic however, all I did was turn on composite, add XAANoOffscreenPixmaps and the DRI section.
http://xtruder.homelinux.net/~ambro/xorg.conf

planetf1
10-27-2007, 08:29 AM
I meant Suspend2 works great, but also does ACPI suspend.

Ok thanks, guess I'll try this patch too later today.

I'm using a redhat 2.6.18 kernel though (with lots of redhat patches)

Did you put anything special in your suspend / acpi / boot config for the video - changing of VT? disabling of framebuffer etc ie anything non-default which wouldn't be in the xorg.conf.

It's great you have a good config..

ambro814
10-27-2007, 09:22 AM
Did you put anything special in your suspend / acpi / boot config for the video
I added the following to suspend2 config for hibernate script:


ProcSetting extra_pages_allowance 0
RestartServices net.eth0


along with other configuration, like unmounting the windows partition.

I add RestartServices becouse the network card wouldn't work after resume otherwise.
Also I don't use framebuffer console as it only causes problems, like being slow and problems with X.

kewlemer
10-30-2007, 03:18 AM
Out of interest I used 0x71c5 (X1600 I think) for my V5250 - I *think* that's closer?

It cannot get more frustrating than this I suppose. I spent half the Sunday (in spite of being sick) to get my fglrx running after the upgrade, then thankfully saw this thread, tried everyting today and yet it doesn't work. :-(

I tried both 0x20a4, 0x71c5 and 0x71d4 and still it doesn't work. Here is all the relavent information. Can anyone PLEASE tell me if I'm missing something.
1. lspci -vvv (FireGL part of the output, its a T60p BTW)

01:00.0 VGA compatible controller: ATI Technologies Inc M56GL [Mobility FireGL V5250] (prog-if 00 [VGA])
Subsystem: Lenovo Unknown device 20a4
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-

............
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [58] Express Legacy Endpoint IRQ 0
Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag+
Device: Latency L0s <4us, L1 unlimited
Device: AtnBtn- AtnInd- PwrInd-
Device: Errors: Correctable- Non-Fatal- Fatal- Unsupported-
Device: RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
Device: MaxPayload 128 bytes, MaxReadReq 128 bytes
Link: Supported Speed 2.5Gb/s, Width x16, ASPM L0s L1, Port 0
Link: Latency L0s <64ns, L1 <1us
Link: ASPM L0s L1 Enabled RCB 64 bytes CommClk+ ExtSynch-
Link: Speed 2.5Gb/s, Width x16
Capabilities: [80] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
Address: 0000000000000000 Data: 0000



2. Xorg.0.log

X Window System Version 1.3.0
Release Date: 19 April 2007
X Protocol Version 11, Revision 0, Release 1.3
Build Operating System: Fedora Core 7 Red Hat, Inc.
Current Operating System: Linux thinkpad-t60p 2.6.22.9-91.fc7 #1
...
(==) Using config file: "/etc/X11/xorg.conf"
(==) ServerLayout "single head configuration"
(**) |-->Screen "Screen0" (0)
(**) | |-->Monitor "Thinkpad-LCD"
(**) | |-->Device "FireGL-fglrx"
(**) |-->Input Device "Keyboard0"
(**) |-->Input Device "Synaptics"
(II) No default mouse found, adding one
(**) |-->Input Device "<default pointer>"
(**) FontPath set to:
unix/:7100
(==) RgbPath set to "/usr/share/X11/rgb"
(==) ModulePath set to "/usr/lib/xorg/modules"
(**) Option "BlankTime" "0"
(**) Option "StandbyTime" "0"
(**) Option "OffTime" "15"
(**) Option "AIGLX" "off"
(**) Extension "Composite" is disabled
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
(II) No APM support in BIOS or kernel
(II) Loader magic: 0x820d960
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.3
X.Org Video Driver: 1.2
X.Org XInput driver : 0.7
X.Org Server Extension : 0.3
X.Org Font Renderer : 0.5
(II) Loader running on linux
(II) LoadModule: "pcidata"
(II) Loading /usr/lib/xorg/modules//libpcidata.so
(II) Module pcidata: vendor="X.Org Foundation"
compiled for 1.3.0, module version = 1.0.0
ABI class: X.Org Video Driver, version 1.2
(++) using VT number 7

(II) LoadModule: "extmod"
(II) Loading /usr/lib/xorg/modules/extensions//libextmod.so
(II) Module extmod: vendor="X.Org Foundation"
compiled for 1.3.0, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 0.3
(II) Loading extension SHAPE
(II) Loading extension MIT-SUNDRY-NONSTANDARD
(II) Loading extension BIG-REQUESTS
(II) Loading extension SYNC
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XC-MISC
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-Misc
(II) Loading extension XFree86-DGA
(II) Loading extension DPMS
(II) Loading extension TOG-CUP
(II) Loading extension Extended-Visual-Information
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) Loading extension X-Resource
(II) LoadModule: "record"
(II) Loading /usr/lib/xorg/modules/extensions//librecord.so
(II) Module record: vendor="X.Org Foundation"
compiled for 1.3.0, module version = 1.13.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 0.3
(II) Loading extension RECORD
(II) LoadModule: "xtrap"
(II) Loading /usr/lib/xorg/modules/extensions//libxtrap.so
(II) Module xtrap: vendor="X.Org Foundation"
compiled for 1.3.0, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 0.3
(II) Loading extension DEC-XTRAP
(II) LoadModule: "glx"
(II) Loading /usr/lib/xorg/modules/extensions//libglx.so
(II) Module glx: vendor="X.Org Foundation"
compiled for 1.3.0, module version = 1.0.0
ABI class: X.Org Server Extension, version 0.3
(**) AIGLX disabled
(II) Loading extension GLX
(II) LoadModule: "dri"
(II) Loading /usr/lib/xorg/modules/extensions//libdri.so
(II) Module dri: vendor="X.Org Foundation"
compiled for 1.3.0, module version = 1.0.0
ABI class: X.Org Server Extension, version 0.3
(II) Loading extension XFree86-DRI
(II) LoadModule: "vbe"
(II) Loading /usr/lib/xorg/modules//libvbe.so
(II) Module vbe: vendor="X.Org Foundation"
compiled for 1.3.0, module version = 1.1.0
ABI class: X.Org Video Driver, version 1.2
(II) LoadModule: "dbe"
(II) Loading /usr/lib/xorg/modules/extensions//libdbe.so
(II) Module dbe: vendor="X.Org Foundation"
compiled for 1.3.0, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 0.3
(II) Loading extension DOUBLE-BUFFER
(II) LoadModule: "fglrx"
(II) Loading /usr/lib/xorg/modules/drivers//fglrx_drv.so
(II) Module fglrx: vendor="FireGL - ATI Technologies Inc."
compiled for 7.1.0, module version = 8.42.3
Module class: X.Org Video Driver
(II) LoadModule: "kbd"
(II) Loading /usr/lib/xorg/modules/input//kbd_drv.so
(II) Module kbd: vendor="X.Org Foundation"
compiled for 7.2.0, module version = 1.1.0
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 0.6
(II) LoadModule: "synaptics"
(II) Loading /usr/lib/xorg/modules/input//synaptics_drv.so
(II) Module synaptics: vendor="X.Org Foundation"
compiled for 4.3.99.902, module version = 1.0.0
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 0.6
(II) LoadModule: "mouse"
(II) Loading /usr/lib/xorg/modules/input//mouse_drv.so
(II) Module mouse: vendor="X.Org Foundation"
compiled for 7.2.0, module version = 1.1.1
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 0.6
(II) Primary Device is: PCI 01:00:0
(II) ATI Proprietary Linux Driver Version Identifier:8.42.3
(II) ATI Proprietary Linux Driver Release Identifier: UNSUPPORTED-8.423.2
(II) ATI Proprietary Linux Driver Build Date: Oct 19 2007 16:13:26
(EE) No devices detected.

Fatal server error:
no screens found

3. xorg.conf
# Xorg configuration created by system-config-display

Section "ServerLayout"
Identifier "single head configuration"
Screen 0 "Screen0" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Synaptics" "CorePointer"
EndSection

Section "Files"
FontPath "unix/:7100"
EndSection

Section "Module"
Load "extmod"
Load "record"
Load "xtrap"
Load "GLcore"
Load "glx"
Load "dri"
Load "vbe"
Load "dbe"
EndSection

Section "ServerFlags"
Option "BlankTime" "0"
Option "StandByTime" "0"
Option "OffTime" "15"
Option "AIGLX" "off"
EndSection

Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
Option "XkbOptions" "ctrl:nocaps"
EndSection

Section "InputDevice"
Identifier "Synaptics"
Driver "synaptics"
Option "Device" "/dev/input/mice"
Option "Protocol" "auto-dev"
Option "Emulate3Buttons" "yes"
Option "SHMConfig" "on"
EndSection

Section "Monitor"
Identifier "Thinkpad-LCD"
Option "VendorName" "ATI Proprietary Driver"
Option "ModelName" "Generic Autodetecting Monitor"
Option "DPMS" "true"
EndSection

Section "Device"
Identifier "FireGL-vesa"
Driver "vesa"
BusID "PCI:1:0:0"
EndSection

Section "Device"
Identifier "FireGL-fglrx"
Driver "fglrx"
Option "OpenGLOverlay" "off"
Option "VideoOverlay" "on"
Option "UseFastTls" "1"
Option "UseInternalAGPGART" "no"
Option "MaxGARTSize" "256"
Option "Capabilities" "0x00000800"
Option "KernelModuleParm" "locked-userpages=0"
Option "Centermode" "on"
Option "PseudoColorVisuals" "off"
Option "EnablePrivateBackZ" "off"
BusID "PCI:1:0:0"
EndSection

Section "Screen"
Identifier "Screen0"
Device "FireGL-fglrx"
Monitor "Thinkpad-LCD"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 16
Modes "1680x1050" "1280x1024" "1280x960" "1024x768" "800x600" "640x480"
EndSubSection
EndSection

Section "DRI"
Group "video"
Mode 0660
EndSection

Section "Extensions"
Option "Composite" "off"
EndSection


Any help greatly appreciated.

Thanks,
KM

chrisr
10-30-2007, 04:32 AM
I tried both 0x20a4, 0x71c5 and 0x71d4 and still it doesn't work. Here is all the relavent information. Can anyone PLEASE tell me if I'm missing something.
1. lspci -vvv (FireGL part of the output, its a T60p BTW)

3. xorg.conf

Section "Device"
Identifier "FireGL-fglrx"
Driver "fglrx"
Option "OpenGLOverlay" "off"
Option "VideoOverlay" "on"
Option "UseFastTls" "1"
Option "UseInternalAGPGART" "no"
Option "MaxGARTSize" "256"
Option "Capabilities" "0x00000800"
Option "KernelModuleParm" "locked-userpages=0"
Option "Centermode" "on"
Option "PseudoColorVisuals" "off"
Option "EnablePrivateBackZ" "off"
BusID "PCI:1:0:0"
EndSection


Where's your

ChipID 0x71D5

line in your Device section? You need to hack the 8.42.3 driver so that it thinks the FireGL is a Mobility Radeon because otherwise it will fail to initialise. Proper FireGL support won't arrive until 8.43.

BTW, I don't think you're going to need the Capabilities and KernelModuleParm lines either.

ambro814
10-30-2007, 05:23 AM
Please use the better method that doesn't need you to specify any pci id: http://www.phoronix.com/forums/showthread.php?t=6091
Anyway for FireGL V5200 you should say ChipID 0x71c5, and in the kernel module put the real pci id (0x71c4).

kewlemer
10-30-2007, 01:37 PM
Where's your

ChipID 0x71D5

line in your Device section? You need to hack the 8.42.3 driver so that it thinks the FireGL is a Mobility Radeon because otherwise it will fail to initialise. Proper FireGL support won't arrive until 8.43.

BTW, I don't think you're going to need the Capabilities and KernelModuleParm lines either.
Yup, I've missed it. Thanks for pointing it out. Will try it tonight and update the thread.

kewlemer
10-31-2007, 03:44 AM
Where's your

ChipID 0x71D5

line in your Device section? You need to hack the 8.42.3 driver so that it thinks the FireGL is a Mobility Radeon because otherwise it will fail to initialise. Proper FireGL support won't arrive until 8.43.

BTW, I don't think you're going to need the Capabilities and KernelModuleParm lines either.
Made both changes. Though I didn't get no screen detected error, the screen went blank. I then unplugged the docking station and the external monitor, just in case, but no use. Then I looked dmesg and saw that I have a "Cannot find Asic ID: 0x71d5" message and this Asic error is also there in xorg log file. I'm posting both dmesg out out and xorg log. Any suggestions ?

Note that the logs are too long to post on the thread. I'll have to post it on Google Docs.

1.dmesg -
http://docs.google.com/Doc?id=ddjtzn4_0d38bsm

2. Xorg.0.log complete file content-
http://docs.google.com/Doc?id=ddjtzn4_1fj2tqp

3. xorg.conf -
http://docs.google.com/Doc?id=ddjtzn4_2pns85s

My build options are -
./ati-installer.sh 8.42.3 --buildpkg Fedora/F7

I'm at my wit's end. Any help greatly appreciated.

Thanks,
KM

ambro814
10-31-2007, 07:09 AM
Once again, use the new patch: http://www.phoronix.com/forums/showthread.php?t=6091
Anyway, ChipID should be 0x71C5 and not 0x71D5.

kewlemer
11-01-2007, 12:09 AM
Once again, use the new patch: http://www.phoronix.com/forums/showthread.php?t=6091
Anyway, ChipID should be 0x71C5 and not 0x71D5.
Thanks for the reply. Tried the old patch method with 0x71C5, but no use.

The new patch method also gave problems. Please see those results here-
http://www.phoronix.com/forums/showthread.php?p=17453#post17453

Any suggestions greatly welcome.

Thanks,
KM

Michael
11-13-2007, 04:36 PM
It looks like FireGL ASICs will now be disabled in 8.43...

planetf1
11-13-2007, 04:56 PM
It looks like FireGL ASICs will now be disabled in 8.43...

Can you elaborate -- do you mean that you're saying that perhaps the FireGL chips will be disabled in 8.43 -- ie no FireGL support.

I think I'm going to cry :-(

mintcoffee
11-13-2007, 08:11 PM
lol that is ridiculous.. you figure that 3 months is enough to enable the very cards that the driver is named after.

kewlemer
11-14-2007, 02:09 AM
It looks like FireGL ASICs will now be disabled in 8.43...
What are we supposed to do then ?? :-(

I'm having issues with the patch workaround and my T60p only runs windows now :-(..and I'm running 32 bit Fedora 8 on vmware on a 64 bit AMD box with NIVIDIA card...

Alexander Heß
11-14-2007, 03:32 PM
It looks like FireGL ASICs will now be disabled in 8.43...

You're f<beep>ing kidding, right?

When is AMD/ATI finally going to release a driver that will officially support (mobility) FireGL cards?

When selecting Linux/FireGL on ati.amd.com/support/driver.html, the only version that is being offered is 8.35.5 which was released in March! That's like 8 months ago.

I'm currently running a patched 8.42.3 which works with the V5250 in my T60p without any problems the Radeon users don't have also. So… Why disable if it actually works?

Kano
11-14-2007, 03:37 PM
I guess you never tried it with "real" 3d apps, like test 3/4 of gl2benchmark which uses openscenegraph...

ctirpak
11-14-2007, 09:41 PM
You're f<beep>ing kidding, right?

When is AMD/ATI finally going to release a driver that will officially support (mobility) FireGL cards?

Ditto! What? I just said yesterday that I was sick and tired of not being able to use my laptop for real (T60p) because of this exact issue. Even when I have the POS 8.35 installed with other distro's it loses its mind and reports false temperature reading to ACPI and the machine shutsdown. Reporting anything realated to a FireGL V5250 to AMD/ATI results in "call the vendor (Lenovo), its not an AMD/ATI product"

How many times are they going to say "next month"

Why doesn't an ATI engineer dare to show there face here?

When selecting Linux/FireGL on ati.amd.com/support/driver.html, the only version that is being offered is 8.35.5 which was released in March! That's like 8 months ago.

I'm currently running a patched 8.42.3 which works with the V5250 in my T60p without any problems the Radeon users don't have also. So… Why disable if it actually works?

Could you please post the pointer to how you got this working with F8? I can not for the life of me make it work.

Thanks

Alexander Heß
11-15-2007, 06:27 AM
Reporting anything realated to a FireGL V5250 to AMD/ATI results in "call the vendor (Lenovo), its not an AMD/ATI product"

Hm, I guess Lenovo is also fed up with AMD/ATI since they switched to Nvidia on the 61 models.

How many times are they going to say "next month"

Probably until "next month"

Could you please post the pointer to how you got this working with F8? I can not for the life of me make it work.

I used Kano's method which has been described by ambro814 in this thread (http://phoronix.com/forums/showthread.php?t=6091). I'm running Ubuntu 7.10 and it worked on the first try.

ctirpak
11-15-2007, 10:06 AM
I used Kano's method which has been described by ambro814 in this thread (http://phoronix.com/forums/showthread.php?t=6091). I'm running Ubuntu 7.10 and it worked on the first try.

Thanks - I'll give that a try. Does it only work on 8.41 or can it also be used on 8.42?

I'll give this a whirl on F8/64 tonight.

planetf1
11-15-2007, 02:21 PM
This discussion is the kind of thing that makes me think carefully about buying ANY ati card in future. Indeed for my last PC card I was hovering between ATI and Nvidia. In HW specs ATI was better, but my confidence in drivers far lower...... I went for Nvidia.

Ok so 8.42.3 in a T60p .. I tried that but didn't have good results, most serious problem was that after resuming from suspend the screen would be blank ,and sometimes would hit a kernel dump.

Also I could not get compiz working properly with a 2nd DVI screen with hot plugging, the full resolution could not be selected.

What I need is
- RHEL5.1 support
- stability (no kernel hangs)
- suspend/resume
- hot dock/undock with external display
- basic GL support (google earth, Secondlife)
- Ideally compiz

Right now with 8.35.5 I can mostly get the first 4 of those. No driver since has come close...

chrisr
11-15-2007, 04:05 PM
It looks like FireGL ASICs will now be disabled in 8.43...

If only it were even slightly funny!

I am so glad that I didn't wait, and hacked 8.42.3 to work instead.

ctirpak
11-15-2007, 04:22 PM
If only it were even slightly funny!

I am so glad that I didn't wait, and hacked 8.42.3 to work instead.

chrisr - which version of the hacks did you use? Looks like your T60p may be closest to mine based on resolution and such that I've seen listed here.
Also - what distro are you running on?
Thanks

ctirpak
11-15-2007, 04:26 PM
I used Kano's method which has been described by ambro814 in this thread (http://phoronix.com/forums/showthread.php?t=6091). I'm running Ubuntu 7.10 and it worked on the first try.[/QUOTE]

Thanks - I have F8 installed currently. I had no luck getting past the boot screen with 7.04 so didn't try 7.10.

chrisr
11-15-2007, 08:01 PM
Also - what distro are you running on?

I won't upgrade to Fedora 8 until 8.43 is released (assuming that I can hack that too).

I can't remember which version of the hack I am using; there is a patch for the driver, and I add a ChipID to xorg.conf.

Malikith
11-15-2007, 08:39 PM
How many times are they going to say "next month"

Why doesn't an ATI engineer dare to show there face here?

Because if a ATI engineer showed up in here, and started praising things about the next driver, and then a bunch of people have issues with it, that guy is in big trouble hahaha. Personally if I was a ATI engineer, and just took one quick read on this forum, I would probably just close the browser and forget about it. Its not that people are only having problems with the drivers, they seem to want to kill the people responsible haha.

Its like a mob with torches and pitch forks chanting give us working drivers or die.

If they don't have firegl support by 8.44 they are definiately in big trouble. Hell I'd say they already are but they did just hire some more people so we'll see what happens.