Fedora Linux Support Community & Resources Center

Go Back   FedoraForum.org > Fedora Resources > Guides & Solutions (Not For Questions)
FedoraForum Search

Forgot Password? Join Us!

Guides & Solutions (Not For Questions) Post your guides here (No links to Blogs accepted). You can also append your comments/questions to a guide, but don't start a new thread to ask a question. Use another forum for that.

View Poll Results: Did it work for you
Yes 459 48.57%
No 343 36.30%
Nearly worked 143 15.13%
Voters: 945. You may not vote on this poll

Reply
 
Thread Tools Search this Thread Display Modes
  #1501  
Old 17th January 2008, 06:29 PM
leigh123linux
Guest
 
Posts: n/a
Quote:
Originally Posted by hauptman
Hi!

I got a strange problem and I would need some help.
I did the install according to the How-To and the Output of fglrxinfo and glxinfo seem fine:

# fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: RADEON 9800 PRO
OpenGL version string: 2.1.7170 Release

#glxinfo
[...]
direct rendering: Yes
[...]
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: RADEON 9800 PRO
OpenGL version string: 2.1.7170 Release


However, when I try glxgears, I get a black window (aka no gears) but it prints the frame stats normally on the console. When I switch back to the Mesa software driver glxgears runs without any problem (but, of course, pretty slow). However, the normal desktop (gnome) works fine with the fglrx driver.

My xorg.conf looks pretty normal:


(w/o the input section)
Please help. I haven't got a clue what could cause this problem.
Post


cat /var/log/Xorg.0.log |grep WW

and

cat /var/log/Xorg.0.log |grep EE
Reply With Quote
  #1502  
Old 17th January 2008, 08:30 PM
hauptman Offline
Registered User
 
Join Date: Jan 2008
Posts: 2
Quote:
Originally Posted by leigh123@linux
Post


cat /var/log/Xorg.0.log |grep WW

and

cat /var/log/Xorg.0.log |grep EE
Quote:
# cat /var/log/Xorg.0.log |grep WW
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(WW) No monitor specified for screen "Screen0".
(WW) The core pointer device wasn't specified explicitly in the layout.
(WW) fglrx: No matching Device section for instance (BusID PCI:1:0:1) found
(WW) fglrx(0): board is an unknown third party board, chipset is supported
(WW) fglrx(0): Only one display is connnected,so single mode is enabled
(WW) AIGLX: 3D driver claims to not support visual 0x23
(WW) AIGLX: 3D driver claims to not support visual 0x24
(WW) AIGLX: 3D driver claims to not support visual 0x25
(WW) AIGLX: 3D driver claims to not support visual 0x26
(WW) AIGLX: 3D driver claims to not support visual 0x27
(WW) AIGLX: 3D driver claims to not support visual 0x28
(WW) AIGLX: 3D driver claims to not support visual 0x29
(WW) AIGLX: 3D driver claims to not support visual 0x2a
(WW) AIGLX: 3D driver claims to not support visual 0x2b
(WW) AIGLX: 3D driver claims to not support visual 0x2c
(WW) AIGLX: 3D driver claims to not support visual 0x2d
(WW) AIGLX: 3D driver claims to not support visual 0x2e
(WW) AIGLX: 3D driver claims to not support visual 0x2f
(WW) AIGLX: 3D driver claims to not support visual 0x30
(WW) AIGLX: 3D driver claims to not support visual 0x31
(WW) AIGLX: 3D driver claims to not support visual 0x32
(WW) AIGLX: 3D driver claims to not support visual 0x33
(WW) AIGLX: 3D driver claims to not support visual 0x34
(WW) AIGLX: 3D driver claims to not support visual 0x35
(WW) AIGLX: 3D driver claims to not support visual 0x36
(WW) AIGLX: 3D driver claims to not support visual 0x37
(WW) AIGLX: 3D driver claims to not support visual 0x38
(WW) AIGLX: 3D driver claims to not support visual 0x39
(WW) AIGLX: 3D driver claims to not support visual 0x3a
(WW) AIGLX: 3D driver claims to not support visual 0x3b
(WW) AIGLX: 3D driver claims to not support visual 0x3c
(WW) AIGLX: 3D driver claims to not support visual 0x3d
(WW) AIGLX: 3D driver claims to not support visual 0x3e
(WW) AIGLX: 3D driver claims to not support visual 0x3f
(WW) AIGLX: 3D driver claims to not support visual 0x40
(WW) AIGLX: 3D driver claims to not support visual 0x41
(WW) AIGLX: 3D driver claims to not support visual 0x42
(WW) AIGLX: 3D driver claims to not support visual 0x43
(WW) AIGLX: 3D driver claims to not support visual 0x44
(WW) AIGLX: 3D driver claims to not support visual 0x45
(WW) AIGLX: 3D driver claims to not support visual 0x46
(WW) AIGLX: 3D driver claims to not support visual 0x47
(WW) AIGLX: 3D driver claims to not support visual 0x48
(WW) AIGLX: 3D driver claims to not support visual 0x49
(WW) AIGLX: 3D driver claims to not support visual 0x4a
(WW) AIGLX: 3D driver claims to not support visual 0x4b
(WW) AIGLX: 3D driver claims to not support visual 0x4c
(WW) AIGLX: 3D driver claims to not support visual 0x4d
(WW) AIGLX: 3D driver claims to not support visual 0x4e
(WW) AIGLX: 3D driver claims to not support visual 0x4f
(WW) AIGLX: 3D driver claims to not support visual 0x50
(WW) AIGLX: 3D driver claims to not support visual 0x51
(WW) AIGLX: 3D driver claims to not support visual 0x52
(WW) AIGLX: 3D driver claims to not support visual 0x53
(WW) AIGLX: 3D driver claims to not support visual 0x54
(WW) AIGLX: 3D driver claims to not support visual 0x55
(WW) AIGLX: 3D driver claims to not support visual 0x56
(WW) AIGLX: 3D driver claims to not support visual 0x57
(WW) AIGLX: 3D driver claims to not support visual 0x58
(WW) AIGLX: 3D driver claims to not support visual 0x59
(WW) AIGLX: 3D driver claims to not support visual 0x5a
(WW) AIGLX: 3D driver claims to not support visual 0x5b
(WW) AIGLX: 3D driver claims to not support visual 0x5c
(WW) AIGLX: 3D driver claims to not support visual 0x5d
(WW) AIGLX: 3D driver claims to not support visual 0x5e
(WW) AIGLX: 3D driver claims to not support visual 0x5f
(WW) AIGLX: 3D driver claims to not support visual 0x60
(WW) AIGLX: 3D driver claims to not support visual 0x61
(WW) AIGLX: 3D driver claims to not support visual 0x62
(WW) AIGLX: 3D driver claims to not support visual 0x63
(WW) AIGLX: 3D driver claims to not support visual 0x64
(WW) AIGLX: 3D driver claims to not support visual 0x65
(WW) AIGLX: 3D driver claims to not support visual 0x66
(WW) AIGLX: 3D driver claims to not support visual 0x67
(WW) AIGLX: 3D driver claims to not support visual 0x68
(WW) AIGLX: 3D driver claims to not support visual 0x69
(WW) AIGLX: 3D driver claims to not support visual 0x6a
(WW) AIGLX: 3D driver claims to not support visual 0x6b
(WW) AIGLX: 3D driver claims to not support visual 0x6c
(WW) AIGLX: 3D driver claims to not support visual 0x6d
(WW) AIGLX: 3D driver claims to not support visual 0x6e
(WW) AIGLX: 3D driver claims to not support visual 0x6f
(WW) AIGLX: 3D driver claims to not support visual 0x70
(WW) AIGLX: 3D driver claims to not support visual 0x71
(WW) AIGLX: 3D driver claims to not support visual 0x72
(WW) <default pointer>: No Device specified, looking for one...
and

Quote:
cat /var/log/Xorg.0.log |grep EE
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(II) Loading extension MIT-SCREEN-SAVER
thanks for the help.
Reply With Quote
  #1503  
Old 17th January 2008, 08:39 PM
leigh123linux
Guest
 
Posts: n/a
Quote:
Originally Posted by hauptman
and



thanks for the help.
The AIGLX warning is normal , is glxgears the only problem as it may be a bug in the driver itself
Reply With Quote
  #1504  
Old 18th January 2008, 06:39 PM
leigh123linux
Guest
 
Posts: n/a
ATI released fglrx 8.1 today , lets hope it's a good one

Quote:
Resolved Issues

The following section provide a brief description of resolved issues with the latest version of the ATI Catalyst™ Linux software suite. These include:

* Corruption will no longer be noticed in the lower right corner of the display or on the mouse pointer after the system is running for a long period of time
* Connecting a display device that supports 1680x1050 to a system running Linux will no longer result in a maximum display resolution of 1280x1024 only being available
* Custom mode lines in xorg.conf will no longer be ignored by the fglrx driver
* Suspending to RAM or DISK on kernel version 2.6.23 or later no longer fails


https://a248.e.akamai.net/f/674/9206..._81_linux.html
Reply With Quote
  #1505  
Old 18th January 2008, 09:36 PM
groelofs Offline
Registered User
 
Join Date: Jun 2007
Posts: 50
Quote:
Originally Posted by leigh123@linux
I think this driver ( 8.41.7 ) is too old to build with the 2.6.23 kernel .
Have you tried re-installing the livna driver ?
i have tried 3 different drivers now, followed your howto to the point, tried different combo's of livna with ati prop driver, even installed F7 now., when i look @ the xorg.0.log i don't c my hd2600 nor the x1650 listed , but somehow the probing on install finds them perfectly on both F7 and F8 both are AGP cards, can't show the xorg.0.logs anymore since it's a new install, trying to figure it all out still.

i just can't get over the fact that the screen goes total black after reboot/X restart.


ok the --buildpkg Fedora/F7 gives me this yet again

Code:
[root@localhost Desktop]# sh ati-driver-installer-8-01-x86.x86_64.run --buildpkg Fedora/F7
Created directory fglrx-install.y30314
Verifying archive integrity... All good.
Uncompressing ATI Proprietary Linux Driver-8.452.1.....................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................
==================================================
 ATI Technologies Linux Driver Installer/Packager 
==================================================
Generating package: Fedora/F7
Package build failed!
Package build utility output:
Building target platforms: i386
Building for target i386
Executing(%prep): /bin/sh -e /tmp/ATI-fglrx-8.452.1-1-30392-root/tmp/rpm-tmp.29825
+ umask 022
+ cd /tmp/ATI-fglrx-8.452.1-1-30392-root/BUILD
+ LANG=C
+ export LANG
+ unset DISPLAY
+ cd /tmp/ATI-fglrx-8.452.1-1-30392-root/BUILD
+ cd ATI-fglrx-8.452.1
++ /usr/bin/id -u
+ '[' 0 = 0 ']'
+ /bin/chown -Rhf root .
++ /usr/bin/id -u
+ '[' 0 = 0 ']'
+ /bin/chgrp -Rhf root .
+ /bin/chmod -Rf a+rX,u+w,g-w,o-w .
+ exit 0

//

/tmp/ATI-fglrx-8.452.1-1-30392-root/tmp/ATI-fglrx-8.452.1-1.f7-root-root/lib/modules/fglrx/build_mod/2.6.x/fglrx.mod.o
  LD [M]  /tmp/ATI-fglrx-8.452.1-1-30392-root/tmp/ATI-fglrx-8.452.1-1.f7-root-root/lib/modules/fglrx/build_mod/2.6.x/fglrx.ko
make[1]: Leaving directory `/usr/src/kernels/2.6.23.12-52.fc7-i686'
build succeeded with return value 0
duplicating results into driver repository...
done.
==============================
You must change your working directory to /tmp/ATI-fglrx-8.452.1-1-30392-root/tmp/ATI-fglrx-8.452.1-1.f7-root-root/lib/modules/fglrx
and then call ./make_install.sh in order to install the built module.
==============================
+ mkdir -p /tmp/ATI-fglrx-8.452.1-1-30392-root/tmp/ATI-fglrx-8.452.1-1.f7-root-root/lib/modules/2.6.23.12-52.fc7/extra
+ install -D -m 0644 fglrx.ko /tmp/ATI-fglrx-8.452.1-1-30392-root/tmp/ATI-fglrx-8.452.1-1.f7-root-root/lib/modules/2.6.23.12-52.fc7/extra/fglrx/fglrx.ko
+ rm -rf /tmp/ATI-fglrx-8.452.1-1-30392-root/tmp/ATI-fglrx-8.452.1-1.f7-root-root/lib/modules/fglrx
+ popd
/tmp/ATI-fglrx-8.452.1-1-30392-root/BUILD/ATI-fglrx-8.452.1
+ /usr/lib/rpm/redhat/brp-compress
+ /usr/lib/rpm/redhat/brp-strip /usr/bin/strip
+ /usr/lib/rpm/redhat/brp-strip-static-archive /usr/bin/strip
+ /usr/lib/rpm/redhat/brp-strip-comment-note /usr/bin/strip /usr/bin/objdump
+ /usr/lib/rpm/brp-python-bytecompile
+ /usr/lib/rpm/redhat/brp-java-repack-jars
Processing files: ATI-fglrx-8.452.1-1.f7
Provides: config(ATI-fglrx) = 8.452.1-1.f7 fglrx_dri.so fglrx_drv.so glesx.so libGL.so.1 libfglrx_dm.so.1.0 libfglrx_gamma.so.1 libfglrx_pp.so.1.0 libfglrx_tvout.so.1 libfglrxdrm.so
Requires(interp): /bin/sh /bin/sh /bin/sh
Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1
Requires(post): /bin/sh /sbin/chkconfig /sbin/ldconfig
Requires(preun): /bin/sh /sbin/chkconfig /sbin/service
Requires(postun): /bin/sh /sbin/ldconfig /sbin/service
Requires: /bin/bash /bin/sh config(ATI-fglrx) = 8.452.1-1.f7 kernel-module-ATI-fglrx-2.6.23.12-52.fc7 = 8.452.1-1.f7 libGL.so.1 libX11.so.6 libXext.so.6 libXrandr.so.2 libXrender.so.1 libc.so.6 libc.so.6(GLIBC_2.0) libc.so.6(GLIBC_2.1) libc.so.6(GLIBC_2.1.3) libc.so.6(GLIBC_2.2) libc.so.6(GLIBC_2.2.3) libdl.so.2 libdl.so.2(GLIBC_2.0) libdl.so.2(GLIBC_2.1) libfglrx_dm.so.1.0 libfglrx_gamma.so.1 libfglrx_pp.so.1.0 libfglrx_tvout.so.1 libgcc_s.so.1 libgcc_s.so.1(GCC_3.0) libm.so.6 libm.so.6(GLIBC_2.0) libpthread.so.0 libpthread.so.0(GLIBC_2.0) libpthread.so.0(GLIBC_2.1) libpthread.so.0(GLIBC_2.2) librt.so.1 librt.so.1(GLIBC_2.2) system-config-display
Conflicts: fglrx fglrx-glc22 fglrx_4_3_0 fglrx_6_8_0 kernel-module-fglrx ati-fglrx ati-fglrx-devel kmod-fglrx xorg-x11-drv-fglrx xorg-x11-drv-fglrx-devel nvidia-glx nvidia-glx-legacy xorg-x11-drv-nvidia xorg-x11-drv-nvidia-legacy
Processing files: ATI-fglrx-control-center-8.452.1-1.f7
Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1
Requires: ATI-fglrx = 8.452.1-1.f7 libGL.so.1 libICE.so.6 libSM.so.6 libX11.so.6 libXcursor.so.1 libXext.so.6 libXi.so.6 libXrandr.so.2 libXrender.so.1 libc.so.6 libc.so.6(GLIBC_2.0) libc.so.6(GLIBC_2.1) libc.so.6(GLIBC_2.1.3) libc.so.6(GLIBC_2.2) libc.so.6(GLIBC_2.2.4) libdl.so.2 libdl.so.2(GLIBC_2.0) libdl.so.2(GLIBC_2.1) libfontconfig.so.1 libfreetype.so.6 libm.so.6 libm.so.6(GLIBC_2.0) libm.so.6(GLIBC_2.1) libm.so.6(GLIBC_2.2) libpthread.so.0 libpthread.so.0(GLIBC_2.0) libpthread.so.0(GLIBC_2.1) libpthread.so.0(GLIBC_2.2)
Processing files: ATI-fglrx-devel-8.452.1-1.f7
Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1
Requires: /usr/include/GL ATI-fglrx = 8.452.1-1.f7 libGL.so.1
Processing files: kernel-module-ATI-fglrx-2.6.23.12-52.fc7-8.452.1-1.f7
Requires(interp): /bin/sh /bin/sh
Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1
Requires(post): /bin/sh
Requires(postun): /bin/sh
Checking for unpackaged file(s): /usr/lib/rpm/check-files /tmp/ATI-fglrx-8.452.1-1-30392-root/tmp/ATI-fglrx-8.452.1-1.f7-root-root
error: Installed (but unpackaged) file(s) found:
   /usr/sbin/amdnotifyui


RPM build errors:
    Installed (but unpackaged) file(s) found:
   /usr/sbin/amdnotifyui
Removing temporary directory: fglrx-install.y30314
[root@localhost Desktop]#
let's try a standard install then.....

Last edited by groelofs; 18th January 2008 at 09:50 PM.
Reply With Quote
  #1506  
Old 18th January 2008, 09:52 PM
Jasbo Offline
Registered User
 
Join Date: Jan 2005
Location: Wells, Maine
Posts: 15
how long does it usually take for a new driver to land in the livna repo?? I can't wait to try this one out and hopefully leave the open source driver behind...everything else works...I just need my direct rendering with 1650x1050 and I will be a happy camper
Reply With Quote
  #1507  
Old 18th January 2008, 09:53 PM
groelofs Offline
Registered User
 
Join Date: Jun 2007
Posts: 50
[QUOTE=groelofs]
Requires(postun): /bin/sh
Checking for unpackaged file(s): /usr/lib/rpm/check-files /tmp/ATI-fglrx-8.452.1-1-30392-root/tmp/ATI-fglrx-8.452.1-1.f7-root-root
error: Installed (but unpackaged) file(s) found:
/usr/sbin/amdnotifyui


RPM build errors:
Installed (but unpackaged) file(s) found:
/usr/sbin/amdnotifyui
Removing temporary directory: fglrx-install.y30314
[root@localhost Desktop]# [/CODE]

let's try a standard install then.....



[CODE]fglrx-install.log gives me this, all looks good as far as i can tell..
Code:
[Message] Kernel Module : Trying to install a precompiled kernel module.
[Message] Kernel Module : Precompiled kernel module version mismatched.
[Message] Kernel Module : Found kernel module build environment, generating kernel module now.
ATI module generator V 2.0
==========================
initializing...
cleaning...
patching 'highmem.h'...
assuming new VMA API since we do have kernel 2.6.x...
 Assuming default VMAP API
 Assuming default munmap API
doing Makefile based build for kernel 2.6.x and higher
make -C /lib/modules/2.6.23.12-52.fc7/build SUBDIRS=/lib/modules/fglrx/build_mod/2.6.x modules
make[1]: Entering directory `/usr/src/kernels/2.6.23.12-52.fc7-i686'
  CC [M]  /lib/modules/fglrx/build_mod/2.6.x/firegl_public.o
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c: In function ‘__ke_check_pci’:
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:1951: warning: ‘pci_find_slot’ is deprecated (declared at include/linux/pci.h:481)
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c: In function ‘__ke_pci_find_slot’:
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:2840: warning: ‘pci_find_slot’ is deprecated (declared at include/linux/pci.h:481)
  LD [M]  /lib/modules/fglrx/build_mod/2.6.x/fglrx.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /lib/modules/fglrx/build_mod/2.6.x/fglrx.mod.o
  LD [M]  /lib/modules/fglrx/build_mod/2.6.x/fglrx.ko
make[1]: Leaving directory `/usr/src/kernels/2.6.23.12-52.fc7-i686'
build succeeded with return value 0
duplicating results into driver repository...
done.
==============================
- recreating module dependency list
- trying a sample load of the kernel modules
done.
no reboot/restart x yet.. xorg.conf looks unchanged :

Code:
# Xorg configuration created by system-config-display

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

Section "InputDevice"
	Identifier  "Keyboard0"
	Driver      "kbd"
	Option	    "XkbModel" "pc105"
	Option	    "XkbLayout" "us"
EndSection

Section "Device"
	Identifier  "Videocard0"
	Driver      "vesa"
EndSection

Section "Screen"
	Identifier "Screen0"
	Device     "Videocard0"
	DefaultDepth     24
	SubSection "Display"
		Viewport   0 0
		Depth     24
		Modes    "1280x1024" "800x600" "640x480"
	EndSubSection
EndSection
weird, let's do a reboot now

hope i'll be back shortly
Reply With Quote
  #1508  
Old 18th January 2008, 10:03 PM
groelofs Offline
Registered User
 
Join Date: Jun 2007
Posts: 50
after the aticonfig --initial (which was found in /usr/bin) this is my xorg.conf :

Code:
# Xorg configuration created by system-config-display

Section "ServerLayout"
	Identifier     "single head configuration"
	Screen      0  "aticonfig-Screen[0]" 0 0
	InputDevice    "Keyboard0" "CoreKeyboard"
EndSection

Section "Files"
EndSection

Section "Module"
EndSection

Section "InputDevice"
	Identifier  "Keyboard0"
	Driver      "kbd"
	Option	    "XkbModel" "pc105"
	Option	    "XkbLayout" "us"
EndSection

Section "Monitor"
	Identifier   "aticonfig-Monitor[0]"
	Option	    "VendorName" "ATI Proprietary Driver"
	Option	    "ModelName" "Generic Autodetecting Monitor"
	Option	    "DPMS" "true"
EndSection

Section "Device"
	Identifier  "Videocard0"
	Driver      "vesa"
EndSection

Section "Device"
	Identifier  "aticonfig-Device[0]"
	Driver      "fglrx"
EndSection

Section "Screen"
	Identifier "Screen0"
	Device     "Videocard0"
	DefaultDepth     24
	SubSection "Display"
		Viewport   0 0
		Depth     24
		Modes    "1280x1024" "800x600" "640x480"
	EndSubSection
EndSection

Section "Screen"
	Identifier "aticonfig-Screen[0]"
	Device     "aticonfig-Device[0]"
	Monitor    "aticonfig-Monitor[0]"
	DefaultDepth     24
	SubSection "Display"
		Viewport   0 0
		Depth     24
	EndSubSection
EndSection
is it meant to do everything double?? or should i erase that what was in the original xorg.conf? like the original "Device" section??
Reply With Quote
  #1509  
Old 18th January 2008, 10:14 PM
leigh123linux
Guest
 
Posts: n/a
Yes

Code:
# Xorg configuration created by system-config-display

Section "ServerLayout"
	Identifier     "single head configuration"
	Screen      0  "aticonfig-Screen[0]" 0 0
	InputDevice    "Keyboard0" "CoreKeyboard"
EndSection

Section "Files"
EndSection

Section "Module"
EndSection

Section "InputDevice"
	Identifier  "Keyboard0"
	Driver      "kbd"
	Option	    "XkbModel" "pc105"
	Option	    "XkbLayout" "us"
EndSection

Section "Monitor"
	Identifier   "aticonfig-Monitor[0]"
	Option	    "VendorName" "ATI Proprietary Driver"
	Option	    "ModelName" "Generic Autodetecting Monitor"
	Option	    "DPMS" "true"
EndSection



Section "Device"
	Identifier  "aticonfig-Device[0]"
	Driver      "fglrx"
EndSection


Section "Screen"
	Identifier "aticonfig-Screen[0]"
	Device     "aticonfig-Device[0]"
	Monitor    "aticonfig-Monitor[0]"
	DefaultDepth     24
	SubSection "Display"
		Viewport   0 0
		Depth     24
	EndSubSection
EndSection
Reply With Quote
  #1510  
Old 18th January 2008, 10:17 PM
groelofs Offline
Registered User
 
Join Date: Jun 2007
Posts: 50
Quote:
Originally Posted by leigh123@linux
Yes

Code:
# Xorg configuration created by system-config-display

Section "ServerLayout"
	Identifier     "single head configuration"
	Screen      0  "aticonfig-Screen[0]" 0 0
	InputDevice    "Keyboard0" "CoreKeyboard"
EndSection

Section "Files"
EndSection

Section "Module"
EndSection

Section "InputDevice"
	Identifier  "Keyboard0"
	Driver      "kbd"
	Option	    "XkbModel" "pc105"
	Option	    "XkbLayout" "us"
EndSection

Section "Monitor"
	Identifier   "aticonfig-Monitor[0]"
	Option	    "VendorName" "ATI Proprietary Driver"
	Option	    "ModelName" "Generic Autodetecting Monitor"
	Option	    "DPMS" "true"
EndSection



Section "Device"
	Identifier  "aticonfig-Device[0]"
	Driver      "fglrx"
EndSection


Section "Screen"
	Identifier "aticonfig-Screen[0]"
	Device     "aticonfig-Device[0]"
	Monitor    "aticonfig-Monitor[0]"
	DefaultDepth     24
	SubSection "Display"
		Viewport   0 0
		Depth     24
	EndSubSection
EndSection
thought so, well i did that, caus running 2 devices tends to get stuff confused, so i deleted it, rebooted and guess what, black screen as it loads the login window.

i'm starting to believe there is no direct rendering with my x1650

is there a way to boot the latest kernel in commandline mode??

well i logged into old kernel, changed the fglrx driver into ati and forced X to find me a new driver, so i'm back @ vesa again, that was a downer

Last edited by groelofs; 18th January 2008 at 10:42 PM.
Reply With Quote
  #1511  
Old 18th January 2008, 10:49 PM
groelofs Offline
Registered User
 
Join Date: Jun 2007
Posts: 50
deleted ati prop driver, i can try the livna again, but that'll prob end up with the same result it did last time. fetching something to drink, cooling down be back in 30 minutes to melt the brain over it again.
Reply With Quote
  #1512  
Old 18th January 2008, 11:44 PM
ajamison Offline
Registered User
 
Join Date: Sep 2006
Location: Dundee, Michigan
Age: 38
Posts: 1,213
I am not sure if the livna driver is compiled with the newest fglrx driver yet but when it does I am going to use that
__________________
Andrew Jamison
IRC:ajamison5579
Linux Counter # 435228
-----------------
Wiki page helping to show appropriate Fedora versions of Ubuntu commands [url=https://fedoraproject.org/wiki/FedorianDictionary]Fedora Dictionary[/url <--- Outdated been very busy looking to update it soon
Reply With Quote
  #1513  
Old 19th January 2008, 12:18 AM
groelofs Offline
Registered User
 
Join Date: Jun 2007
Posts: 50
i've found a new driver set that has my card in it, downloaded and installed xorg-x11-driver-video-radeonhd-1.1.0-9.1.i386.rpm from http://download.opensuse.org/reposit...Fedora_7/i386/

now it shows this in Xorg0.conf:
Code:
(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) RADEONHD: X driver for the following AMD GPG (ATI) graphics devices:
	RV505 : Radeon X1550, X1550 64bit.
	RV515 : Radeon X1300, X1550, X1600; FireGL V3300, V3350.
	RV516 : Radeon X1300, X1550, X1550 64-bit, X1600; FireMV 2250.
	R520  : Radeon X1800; FireGL V5300, V7200, V7300, V7350.
	RV530 : Radeon X1300 XT, X1600, X1600 Pro, X1650; FireGL V3400, V5200.
	RV535 : Radeon X1300, X1650.
	RV550 : Radeon X2300 HD.
	RV560 : Radeon X1650.
	RV570 : Radeon X1950, X1950 GT; FireGL V7400.
	R580  : Radeon X1900, X1950; AMD Stream Processor.
	R600  : Radeon HD 2900 GT/Pro/XT; FireGL V7600/V8600/V8650.
	RV610 : Radeon HD 2350, HD 2400 Pro/XT, HD 2400 Pro AGP; FireGL V4000.
	RV630 : Radeon HD 2600 LE/Pro/XT, HD 2600 Pro/XT AGP; Gemini RV630;
		FireGL V3600/V5600.
	RV670 : Radeon HD 3850, HD 3870, FireGL V7700.
	M52   : Mobility Radeon X1300.
	M54   : Mobility Radeon X1400; M54-GL.
	M56   : Mobility Radeon X1600; Mobility FireGL V5200.
	M58   : Mobility Radeon X1800, X1800 XT; Mobility FireGL V7100, V7200.
	M62   : Mobility Radeon X1350.
	M64   : Mobility Radeon X1450, X2300.
	M66   : Mobility Radeon X1700, X1700 XT; FireGL V5250.
	M68   : Mobility Radeon X1900.
	M71   : Mobility Radeon HD 2300.
	M72   : Mobility Radeon HD 2400; Radeon E2400.
	M74   : Mobility Radeon HD 2400 XT.
	M76   : Mobility Radeon HD 2600
		(Gemini ATI) Mobility Radeon HD 2600 XT.
	RS600 : Radeon Xpress 1200, Xpress 1250.
	RS690 : Radeon X1200, X1250, X1270.
direct rendering is still no

glxinfo shows :
Code:
name of display: :0.0
display: :0  screen: 0
direct rendering: No
server glx vendor string: SGI
server glx version string: 1.2
server glx extensions:


GLX extensions:
    GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context, 
    GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_copy_sub_buffer, 
    GLX_OML_swap_method, GLX_SGI_make_current_read, GLX_SGIS_multisample, 
    GLX_SGIX_fbconfig, GLX_EXT_texture_from_pixmap
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)
OpenGL extensions:
    GL_ARB_depth_texture, GL_ARB_draw_buffers, GL_ARB_fragment_program, 
    GL_ARB_imaging, GL_ARB_multisample, GL_ARB_multitexture, 
    GL_ARB_occlusion_query, GL_ARB_point_parameters, GL_ARB_point_sprite, 
    GL_ARB_shadow, GL_ARB_shadow_ambient, GL_ARB_
i don't know how this will affect the ati prop driver, do you know?? i finally got something done after a week now, change the Driver section from vesa to radeonhd, without crashing the X-server.

do you know how i can c what files are in the rpm file? and where it puts it, and if it will be used or overwritten by the ati prop driver??

Last edited by groelofs; 19th January 2008 at 12:23 AM.
Reply With Quote
  #1514  
Old 19th January 2008, 12:29 AM
groelofs Offline
Registered User
 
Join Date: Jun 2007
Posts: 50
copied from other forum, i found on the radeonhd file :
I dont even use linux with my ATi rig, but its still important to announce this.
Today openSuSE news announced the release of the new ATi driver for R5xx and R6xx series cards. Its not ready yet, but still provide some functions that some may find usefull.

Info:
X.Org Wiki - radeonhd

Source:
openSUSE News » Blog Archive » ATI RadeonHD Driver: First Release!

Repositories where you can find it:
Index of /repositories/X11:/Drivers:/Video:/radeonhd

The Driver:
ftp://ftp.freedesktop.org/pub/indivi...-1.0.0.tar.bz2

Quote:

* First released version.
* Full modesetting driver, capable of driving multiple monitors.
* Support for VGA, DVI, DMS-59, and laptop panels.
* Support for monitor hotplug detection, DDC, and dynamic reconfiguration.
* Full RandR 1.2 compatibility.
* AtomBIOS support for initialization, data tables, etc.
* Early RandR 1.3 property support (subject to change).
* Hardware cursor support.
* No 2D & 3D acceleration, no XVideo yet. No TV, Component, and HDMI yet.


Quote:
The radeonhd driver supports video cards based on the following ATI chips:

* RV505: Radeon X1550, X1550 64bit
* RV515: Radeon X1300, X1550, X1600; FireGL V3300, V3350
* RV516: Radeon X1300, X1550, X1550 64-bit, X1600; FireMV 2250
* R520: Radeon X1800; FireGL V5300, V7200, V7300, V7350
* RV530: Radeon X1300 XT, X1600, X1600 Pro, X1650; FireGL V3400, V5200
* RV535: Radeon X1300, X1650
* RV550: Radeon X2300 HD
* RV560: Radeon X1650
* RV570: Radeon X1950, X1950 GT; FireGL V7400
* R580: Radeon X1900, X1950; AMD Stream Processor
* R600: Radeon HD 2900 GT/Pro/XT; FireGL V7600/V8600/V8650
* RV610: Radeon HD 2350, HD 2400 Pro/XT, HD 2400 Pro AGP; FireGL V4000
* RV630: Radeon HD 2600 LE/Pro/XT, HD 2600 Pro/XT AGP; Gemini RV630; FireGL V3600/V5600
* M52: Mobility Radeon X1300
* M54: Mobility Radeon X1400; M54-GL
* M56: Mobility Radeon X1600; Mobility FireGL V5200
* M58: Mobility Radeon X1800, X1800 XT; Mobility FireGL V7100, V7200
* M62: Mobility Radeon X1350
* M64: Mobility Radeon X1450, X2300
* M66: Mobility Radeon X1700, X1700 XT; FireGL V5250
* M68: Mobility Radeon X1900
* M71: Mobility Radeon HD 2300
* M72: Mobility Radeon HD 2400; Radeon E2400
* M74: Mobility Radeon HD 2400 XT
* M76: Mobility Radeon HD 2600; (Gemini ATI) Mobility Radeon HD 2600 XT
* RS690: Radeon X1200, X1250, X1270

This section is taken straight from the radeonhd(4) man page, and should be kept in sync with radeonhd(4) and the src/rhd_id.c file in the source.
Quote:
Why is radeonhd so much slower than avivo?

There may be an old, obsolete line in your xorg.conf file from some fglrx setup a long time ago:

Option "mtrr" "no" # ancient, obsolete option: REMOVE IT!
If you have such a line, removing it can speed up radeonhd considerably.
General note: As a rule, one does not need any xorg.conf file with Xserver 1.4 and up, so it is always a good idea to make sure you really need all the statements in there.
__________________
Live Chat in NGOHQ - http://www.ngohq.com/misc.php?do=flashchat
Easy MoBlock for linux - http://www.ngohq.com/general-softwar...ock-linux.html
Are you a linux user? http://counter.li.org/ - Get counted.
Need help with linux? http://www.ngohq.com/showthread.php?t=9370
Reply With Quote
  #1515  
Old 19th January 2008, 12:36 AM
leigh123linux
Guest
 
Posts: n/a
Quote:
Originally Posted by groelofs
copied from other forum, i found on the radeonhd file :
I dont even use linux with my ATi rig, but its still important to announce this.
Today openSuSE news announced the release of the new ATi driver for R5xx and R6xx series cards. Its not ready yet, but still provide some functions that some may find usefull.

Info:
X.Org Wiki - radeonhd

Source:
openSUSE News » Blog Archive » ATI RadeonHD Driver: First Release!

Repositories where you can find it:
Index of /repositories/X11:/Drivers:/Video:/radeonhd

The Driver:
ftp://ftp.freedesktop.org/pub/indivi...-1.0.0.tar.bz2

Quote:

* First released version.
* Full modesetting driver, capable of driving multiple monitors.
* Support for VGA, DVI, DMS-59, and laptop panels.
* Support for monitor hotplug detection, DDC, and dynamic reconfiguration.
* Full RandR 1.2 compatibility.
* AtomBIOS support for initialization, data tables, etc.
* Early RandR 1.3 property support (subject to change).
* Hardware cursor support.
* No 2D & 3D acceleration, no XVideo yet. No TV, Component, and HDMI yet.


Quote:
The radeonhd driver supports video cards based on the following ATI chips:

* RV505: Radeon X1550, X1550 64bit
* RV515: Radeon X1300, X1550, X1600; FireGL V3300, V3350
* RV516: Radeon X1300, X1550, X1550 64-bit, X1600; FireMV 2250
* R520: Radeon X1800; FireGL V5300, V7200, V7300, V7350
* RV530: Radeon X1300 XT, X1600, X1600 Pro, X1650; FireGL V3400, V5200
* RV535: Radeon X1300, X1650
* RV550: Radeon X2300 HD
* RV560: Radeon X1650
* RV570: Radeon X1950, X1950 GT; FireGL V7400
* R580: Radeon X1900, X1950; AMD Stream Processor
* R600: Radeon HD 2900 GT/Pro/XT; FireGL V7600/V8600/V8650
* RV610: Radeon HD 2350, HD 2400 Pro/XT, HD 2400 Pro AGP; FireGL V4000
* RV630: Radeon HD 2600 LE/Pro/XT, HD 2600 Pro/XT AGP; Gemini RV630; FireGL V3600/V5600
* M52: Mobility Radeon X1300
* M54: Mobility Radeon X1400; M54-GL
* M56: Mobility Radeon X1600; Mobility FireGL V5200
* M58: Mobility Radeon X1800, X1800 XT; Mobility FireGL V7100, V7200
* M62: Mobility Radeon X1350
* M64: Mobility Radeon X1450, X2300
* M66: Mobility Radeon X1700, X1700 XT; FireGL V5250
* M68: Mobility Radeon X1900
* M71: Mobility Radeon HD 2300
* M72: Mobility Radeon HD 2400; Radeon E2400
* M74: Mobility Radeon HD 2400 XT
* M76: Mobility Radeon HD 2600; (Gemini ATI) Mobility Radeon HD 2600 XT
* RS690: Radeon X1200, X1250, X1270

This section is taken straight from the radeonhd(4) man page, and should be kept in sync with radeonhd(4) and the src/rhd_id.c file in the source.
Quote:
Why is radeonhd so much slower than avivo?

There may be an old, obsolete line in your xorg.conf file from some fglrx setup a long time ago:

Option "mtrr" "no" # ancient, obsolete option: REMOVE IT!
If you have such a line, removing it can speed up radeonhd considerably.
General note: As a rule, one does not need any xorg.conf file with Xserver 1.4 and up, so it is always a good idea to make sure you really need all the statements in there.
__________________
Live Chat in NGOHQ - http://www.ngohq.com/misc.php?do=flashchat
Easy MoBlock for linux - http://www.ngohq.com/general-softwar...ock-linux.html
Are you a linux user? http://counter.li.org/ - Get counted.
Need help with linux? http://www.ngohq.com/showthread.php?t=9370


The line in red = no direct rendering
Reply With Quote
Reply

Tags
ati, fglrx, howto

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
ATI Catalyst fglrx driver manual install on Fedora 12 Jeff72 Guides & Solutions (Not For Questions) 15 13th August 2010 09:17 PM
ATI Catalyst™ Display Driver v9.12 rich52 Hardware & Laptops 1 31st December 2009 05:59 AM
HOWTO - make less noise from video card while using fglrx driver multescugeorge@ Guides & Solutions (Not For Questions) 2 3rd October 2009 08:02 AM
ATI Catalyst 9.x fglrx driver manual install on Fedora 11 Jeff72 Guides & Solutions (Not For Questions) 25 30th August 2009 08:29 PM


Current GMT-time: 12:47 (Wednesday, 20-09-2017)

TopSubscribe to XML RSS for all Threads in all ForumsFedoraForumDotOrg Archive
logo

All trademarks, and forum posts in this site are property of their respective owner(s).
FedoraForum.org is privately owned and is not directly sponsored by the Fedora Project or Red Hat, Inc.

Privacy Policy | Term of Use | Posting Guidelines | Archive | Contact Us | Founding Members

Powered by vBulletin® Copyright ©2000 - 2012, vBulletin Solutions, Inc.

FedoraForum is Powered by RedHat