Starting Compiz (Slack 12.2, ATI Radeon 3870)
Hey all,
When I type "compiz --replace", I get the following error: Code:
compiz (core) - Fatal: No GLXFBConfig for default depth, this isn't going to work. glxinfo output: Code:
name of display: :0.0 Code:
Section "Module" |
Code:
Section "Device" The driver supports full modesetting (read: any mode is usable, not only those provided by the BIOS), and is compatible to RandR 1.3. Future work is happening especially on more advanced features like 2D, 3D, and video acceleration. The short answer is the driver you appear to be using does not support 3D. |
I stuck "radeonhd" in by hand to enable higher resolutions, originally it was something else. Am I able to use Emerald themes without having Compiz running?
|
From what I understand, Emerald only works with a compositing window manager. I do not know if it will work with newer WM's that feature built in compositing (such as Xfce or (I believe) KDE4).
|
That's really unfortunate :( I know I was able to get it running on other distros of Linux, with this very hardware.
|
I do not believe it's Slackware's fault. You will need to install and configure an Xorg video driver capable of utilizing the 3D capabilities of your video card. I have no experience with ATI cards, so I'm pretty much useless from this point on. :)
|
What videocard do you have? There are proprietary ATI drivers that might help you. Sometime ago ATI discontinued support for older chips, but the legacy drivers are still better than the current state of radeon and radeonhd. For example, I have Radeon X1200 on my laptop and it works quite nicely with ATI 9.3 driver.
|
Uncle Theodore,
My card is an ATI Radeon 3870. I manually typed "radeonhd" as my driver to enable the highest resolution my card could handle, but if you know of something else that would work, that would also allow Emerald/compiz to work, please do let me know. |
Quote:
http://support.amd.com/us/psearch/Pa...ords=&items=20 and select your card and Linux as the operating system. My search came out with versions 9.3 and 9.5. The installation instructions are also there. |
Hmm. Well, I installed the driver, but now I can't load X at all. I can log in, but typing "startx" causes the screen to go black, and no longer loads the graphical environment. I hope there is a way to fix that :/
|
Quote:
Another common thread can be found here: http://www.linuxquestions.org/questi...ighlight=fglrx. Forgive me if you came across that site already. |
Yeah, I took note about running 'aticonfig --initial -f', but I was skeptical to actually use it, because the instructions said using it will remove the device, monitor, and screen sections from the X server config file. I wasn't sure just how much damage would be done by removing all of those sections, but apparently it's safe?
|
It will back up the initial configuration.
Anyway, if you decide to install the driver, you've got to configure it. You can't do it half way... BTW, if you decide to uninstall it, the uninstaller will return your config files to the original state. |
someone said they got fglrx to compile with slack 12.2 by running this
Code:
./ati-driver-installer-8-12-x86.x86_64.run --buildpkg Slackware/All Code:
root@(none):~/Desktop# aticonfig --initial --overlay-type=Xv --resolution=0,1024x768 So I continued with the instructional code and this is the error message I get with that. Code:
root@(none):~/Desktop# modeprobe fglrx Anyways. Someone out there knows, they just didn't read our forums yet. |
Quote:
|
fglrx: Unknown symbol pci_disable_msi
fglrx: Unknown symbol pci_enable_msi Sheesh! Completely forgot about that piece... Sorry. Yes, I had this problem with Slackware 12.2, and had to recompile my kernel with CONFIG_ARCH_SUPPORTS_MSI=y CONFIG_PCI_MSI=y Then it worked. And it's still working. |
Yeah, so I ran "aticonfig --initial -f"
and now I can't even log in at all. I just get an error at startup: Code:
init[1]: segment at 0 ip 080ac345 sp bfe5434 error 6 in init [8048000+87000] Edit: I booted again, and I'm getting an entirely new error. Code:
sh[1406]: segfault at 458b14f0 ip 0805f343 sp bfbe59d8 error 6 in bash[8048000+a0000] I don't think a graphics driver should have the capability to render an operating system useless. |
Hm. That's very strange. I've been using this driver for several months now, I've never heard that it could cause bash segfaults or /etc/rc.d/rc.udev syntax (!!) errors... Line 92 is this
MAJORNUMBER=$(($DEVICENUMBER / 256)) I don't see any syntax errors here... Why did you use the -f ("force") key in the aticonfig command? Anyways. You can try to roll back to your original configuration like this: 1. Boot from your instllaltion CD. 2. Login as root (press Enter twice, actually). 3. Locate your / partition with the fdisk -l command. Let's say, it's /dev/sda3 4. Type mount /dev/sda3 /mnt mount -t proc proc /mnt/proc chroot /mnt /bin/bash Now you can edit your files and run programs. You have your old system, only the kernel is the one from the installation CD. 5. Type /usr/share/ati/fglrx-uninstall.sh and reboot. This should restore your system back to what it was before installing the driver. Sorry, didn't think it would cause so much trouble. The thing works perfectly on my side... |
Uncle Theodore,
Thank you very much, my system is running properly now. I don't know what made it freak out so much about the driver though. |
So I read in another thread that the latest versions (9-x) of fglrx require a kernel recompile, but 8-12 works great out of the box. So I downloaded and installed the driver, and did aticonfig --initial.
Here is my most current xorg.conf file: Code:
# ********************************************************************** Now, when I use "compiz --replace", I don't get any warnings, but the whole screen goes black, and I can't do anything except move the cursor around. When I use "emerald --replace", there are no errors, but in fact nothing at all happens. When I open up the Emerald Theme Manager and click on my "Black Crystal WT" theme, the console says "Reloading..." but nothing happens. What other step am I missing? Is there anything else? glxinfo output: Code:
name of display: :0.0 |
Any ideas?
|
When starting Compiz (with compiz --replace), you're not specifying any plugins to load. Since all of Compiz's functionality is provided by the various plugins, it's not got anything to do.
As for your Emerald problem, it's probably related to Compiz's lack of plugins as well. I recommend you use "CompizConfig Settings Manager" (http://www.compiz-fusion.org) to start and manage both Compiz and Emerald. This is how I use Compiz, via a .desktop file in my autostart directory, and rarely have any problems. I don't know if there are packages available for Slackware, as I built all of Compiz from source. |
You need to compile a kernel with msi (pci_msi). This is under bus options. I'm currently using kernel 2.6.27.15 and the catalyst autoinstaller works fine with slackware 12.2 and slackware-current (32).
I suggest you NOT put the new kernel in /usr/src so the distribution remains mostly original. When you compile your kernel, be careful to include the file system and ide/scsi/sata drivers into the kernel, or if you want modules you will need at initrd (brief instructions for initrd are found in /boot). For fglrx you do not need radeon or drm. If you compile these as modules, you may wish to rename them in the /lib/modules/.../drm area as it is possible they interfere with fglrx. Good luck. Edit: for your hardware (hd...) I would think the newer catalysts would be better. You should try 9-5 but you could read the changelogs to see when the last improvements for your video card occurred. I almost think 9-5 is a little slower (I have hd3200 integrated) but I haven't had time to revert and see. edit2: I also note the changes you've made to xorg.conf are in the radeonhd section which is not used as you've directed it to use fglrx. Also review /var/log/Xorg.0.log to see feedback on options you've added. Many you've added are enabled by default or you will find they don't work. About all I have in my xorg.conf for the fglrx driver is: Code:
Section "Device" |
X3J11, Using the CCSM, (by typing 'ccsm' into the terminal), I am able to select all the various options, but I am not sure how to get them to actually take effect. Also, launching CCSM from terminal, the following error is displayed maybe 50 times:
Code:
** (ccsm:3420): WARNING **: expected enumeration type PangoWrapMode, but got GtkWrapMode instead |
The comments I made were on two topics. The first was to compile a newer kernel to use newer catalyst drivers (ati installer). There is some learning required to do that. You can download or get link to download newer kernel at www.kernel.org. General instructions are located in the readme and other documentation. Do that at your own pace. If you do this, for time being I would stay in the 2.6.27 series. I've had problems with 2.6.28 and the catalyst driver doesn't install with 2.6.29. 2.6.30 just came out and I've only tried it with 64 bit and the installer doesn't work. It might work at 32 bit but I don't know.
The second topic started at my edit2, where I point out the changes you made to your xorg.conf file were under the radeonhd section and will have no effect on the fglrx driver. I also suggested what you might wish to use initially in the fglrx driver section of xorg.conf. Try this part first. If it doesn't help you, you may need to do a custom kernel. Regarding part 2, do you understand? Initially you had it set to run radeonhd. When you installed catalyst (sh ati*8-12*.run) it changed your xorg.conf and added an fglrx section (Driver "fglrx"). It also made other changes to cause X to use fglrx. So the radeonhd section is ignored and that is where you put your changes. |
Quote:
As for the error from ccsm, I have no idea what that's about. If I had to guess, I would say that it's expecting one thing (as said) but getting another. Pango is, I belive, a text rendering library. Presumably it's getting some sort of fallback where gtk is providing the functionality it's expecting from pango. Sorry I can't be more helpful, but aside from a few issues here and there figuring it out (shortly after 12.2's release) I haven't had any problems with it. |
All times are GMT -5. The time now is 10:47 AM. |