Debian Hardware :: No 3D Rendering With AMD Catalyst Legacy 13.1
Jul 27, 2014
After seeing disappointing FPS in games with the open source AMD driver, I decided to install the proprietary one using the instructions on the Debian wiki. As I have a Mobility Radeon HD 3670, I needed to install the legacy driver. Everything installed fine, and I was able to configure my GPU by putting
Code: Select allSection "Device"
Identifier "My GPU"
Driver "fglrx"
EndSection
in /etc/X11/xorg.conf.d/20-fglrx.conf. I then restarted the computer, so that the open source driver could be blacklisted. In addition to the base driver installation, I installed the legacy Catalyst Control Center and the 32-bit fglrx OpenGL library. The problem is that, whenever I run fgl_glxgears, the rendering window is just a black screen. KDE renders just fine, and I am currently typing this using Iceweasel. I have tried using aticonfig to disable fast TLS, but the problem still occurs. The packages that I have installed are:
firmware-linux-nonfree
fglrx-legacy-control amd64
fglrx-legacy-atieventsd amd64
fglrx-legacy-driver amd64
fglrx-legacy-modules-dkms amd64
libfglrx-legacy amd64 and i386
libfglrx-legacy-amdxvba1 amd64
and libgl1-fglrx-legacy-glx amd64 and i386
. Also, when I type fglrxinfo, the renderer string is my GPU and not a software renderer.
I have an ATI Radeon 9200 AGP card. I plan to upgrade it mainly because the 2D performance in KDE (3.x without Beryl or Compiz) is just bad. Since we are talking about a relatively old desktop, I do not want to completely upgrade it. So, I want to just upgrade the VGA card. I have found the following cards: Nvidia GeForce 6200
Radeon HD 2400 Pro Radeon X1600 Pro Avivo Edition
Now, the simple question: Their prices are just OK (just a couple of � separate them). Which chip is better? And which chip is better supported from our beloved distro?
I downloaded an FLV video and placed an extra MP3 file over it. Two files. Total: 30 MBI experimented with about seven rendering containers, and QuickTime renderer was the only rendering container that didn't result in sped-up/compressed video or correct rendering for just fifteen seconds.How in the name of all that is holy did this rendering end up with 570 extra MB?
I recently downloaded Frets On Fire and the HRP Polymer pack for Duke3D...Duke3D runs fine with just EDuke32 and no mods, just Duke3D and EDuke32. But when I try the HRP Polymer pack, it says in Terminal "NVIDIA: Direct Rendering failed, attempting indirect rendering." This is fine...if I want the game to lag like hell, I'm sure my video card and the driver for it support DR, the video card is a NVIDIA Geforce FX 5200, the same message appears in terminal when I run Frets On Fire, I think it does with other games too, if someone could explain how to enable Direct Rendering.
We installed Debain 6.0 (Squeeze) on a Seagate ST2000DL003 (2 TB SATA HDD) and the installer choose GPT for us. Only came to light when we tried to run fdisk and got "WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted". parted was not installed by default (!). Investigating further we found dd cannot be used to back up and restore GPT; for that you need gptfdisk (a.k.a. gdisk) which is still in beta and does not have a 64-bit .deb.
Clearly GPT is the future but I am not convinced it is mature yet (Bug#599437) and the online knowledgebase is not yet extensive. Taking all this into account, I am considering changing to a traditional MBR and included partition table. [Note on terminology: when using a GPT, the MBR is considered distinct from the partition table; when using a legacy partition table, the partition table is commonly considered part of the MBR]
Would this be wise? If the good people at Debian have programmed the installer to use GPT for this HDD, despite GPT's youth, they must have had their reasons. The most informative Debian documentation found is the Debian GNU/Linux Installation Guide, 6.3.3. Partitioning and Mount Point Selection which says "... Defaults may vary as well. The type of partition table used by default can for example be different for large capacity hard disks than for smaller hard disks. Some options can only be changed when installing at medium or low debconf priority; at higher priorities sensible defaults will be used".
I purchased an older Dell (p4 1.8G 256M) just to run some low demand programs. They don't require a GUI - just ssh/cli type of access. will be a server type - no kb or monitor. Can someone give me some pointers where to start at? I've never done a Debian install - the install process may address these questions - but figured I would throw it out here. I've used Ubuntu for several years now but I doubt that it would be the best distro for a legacy system....
I recently updated my Debian Jessie and somehow that update broke my Debian. I have a Gtx 465 and this has been working fine under Jessie for a year.
After the update I no longer have X running. I tried removing all the Nvida stuff and reinstalling 304-legacy which did not get the Xserver back. I also tried to install Nvidia 304 driver binary but this time it refuses to compile ;( So I am out of luck at the moment.
I am runing Jessie Linux 3.18 Nvidia 465 Gtx Intel Cpu
Code: Select all   built-ins [  41.306] (==) ModulePath set to "/usr/lib/xorg/modules" [  41.306] (II) The server relies on udev to provide the list of input devices.     If no devices become available, reconfigure udev or disable AutoAddDevices. [  41.306] (II) Loader magic: 0x7ff757496d80
Does anyone know when or if the nvidia legacy drivers are going into Squeeze? I tried the ones in the Sid repos but ran into unresolvable dependencies. Lots of people were telling me that testing works just fine so I've been trying it out, but to be honest I've run into quite a few problems of this nature. I admit that I'm running a real Rube Goldberg mix of older and newer hardware on this box, but I wouldn't think it would be this much of a problem.
I recently installed the Nvidia proprietary drivers and I have a problem starting gdm. Xserver fails, only throwing a warning concerned to xkbcomp, something about ralt having two symbols... but just a warning anyway. Then, after waiting the screen flash between the tty and a black screen a few times;
i'm on the tty, from where I can "startx" without problem. I tried using the nv driver and gdm worked.. so i think it has relation with the nvidia drivers... If I start gdm from the tty, instead of using the startx command, then gdm appears but if I try to log in.. all freezes up.. Here's my xorg.conf generated by nvidia-xconfig: [URL]
I have some scripts that need to use a newer version of PHP, Im running Debian 6 which has PHP 5.3.3 support, I found I could install php 5.4 using [URL]. This worked, it updated my PHP to a newer version, the only issue is that when the install completed apache now downloads the PHP file instead of rendering it.
Im guessing this has something to do with the Apache configs, but I don't know what to do.
Code:
Select alltom@vps:~$ dpkg --list |grep -E '(apache)|(php5-)' ii apache2                 2.2.16-6+squeeze12      Apache  HTTP Server metapackage ii apache2-doc               2.2.16-6+squeeze12      Apache                                                          [Code] ...
I'm "happy" owner of ATI x1250 video-card. Used manual from [URL] to install Catalyst 9.3 in lenny, but I have 64bit system,so have lot's of errors. kernel & xorg info:
[code]....
For kernel versions past the released 2.6.25, the git series. They�ve removed the tlb stuff from smp_[32|64].c and added new files specially for tlb: tlb_32.c and tlb_64.c.i'm using not proper patch, or something else, but i can't patch my kernel. I saved this text into fglrx.patch
[code]....
console asks me to provide "File to patch" because there is no such file as /arch/x86/kernel/tlb_64.c i created manually just an empty doc tlb_64.c and then launched patch but it shows:
I've compiled Firefox 3.6.3 on Debian Lenny with the following mozconfig: http://pastebin.mozilla.org/713438When executed, I'm getting strange rendering errors: http://imgur.com/Bmosk
I have an ATI Radeon 5850 card with 2 17" monitors, plus a 46" TV via HDMI (disabled, except for BD plaback under windows) under Debian 6.0/Squeeze. When I first installed this system, it worked fine with all 3 screens (only 2 enabled at a time). Sometime in the past few weeks though, it's decided to revert to a single-display setup. I can't find any errors in the logfiles, and it works perfectly fine when I re-enabled the secondary display via the ATI Catalyst Control center.
The auto-generated xorg.conf isn't configured to use the second display (even after re-generating one using "aticonfig -initial=dual-head"), and it is not being modified when I change settings in the Catalyst Control Center.Updating display settings after every boot is just a bit annoying.
I'm noticing some odd rendering glitches under Iceweasle 3.5.16, with GNOME 2.30.2 running Debian 6.0 i386 default install.Google for example has an odd black bar that blinks, it almost seems like some odd selection bug (but I have not made any selection). Sometimes it doesn't appear other times right after starting Iceweasle it happens. Any ideas? It happens on other websites in random areas.
I'm running Debian Squeeze/current fine with the default kernel & ATi's Catalyset drivers. I'm struggling to get the display drivers to work with the bigmem kernel as I've got 4GB ram on my machine so might as well try to enable it.
I can have my system work with the normal Squeeze kernel by installing the normal kernel headers & then FGLRX drivers, but after additionally installing the bigmem kernel & headers (linux-image-2.6-686-bigmem & linux-headers-2.6-686-bigmem) I cannot get the system to reach X after removing & then re-installing the video drivers.
I installed compiz with nvidia trouble is when I run compiz white bars or lines (bars) appear in open windows (icewease, gedit, etc.). They disappear after a few moment and reappear when scrolling a page. BTW everything works fine with metacity running as window manager.
Here is my xorg.conf: # nvidia-xconfig: X configuration file generated by nvidia-xconfig # nvidia-xconfig: version 1.0 (randy@juliet2) Fri Sep 5 15:03:39 PDT 2008 # nvidia-settings: X configuration file generated by nvidia-settings # nvidia-settings: version 1.0 (randy@juliet2) Tue Jun 24 10:44:02 PDT 2008 Section "ServerLayout" Identifier "Layout0" Screen 0 "Screen0" 0 0 InputDevice "Keyboard0" "CoreKeyboard" InputDevice "Mouse0" "CorePointer" EndSection .....
I have the nvidia driver 173.14.09 installed. Running Debian Lenny stable x64 and turion x2 with a geforce 8200M G graphics card with dual screens. I first installed the debian repos compiz, then upgraded to the tuxfamily repo version. I installed the nvidia driver 190 from nvidia's website and that fixed it!
Alright ... recently switched from Ubuntu with FF 4.0 to Debian with Iceweasel which I had to upgrade to 4.0 since I really liked the way it worked on Ubu 10.10 ... but I'm having some really strange rendering issues. Flash is not a problem at all, works fine on all flash sites that I've checked out. Some sites though, including this Debian forum, do not show everything in the Iceweasel browser window.
For example, sometimes I'll be browsing on a page with huge chunks of white, clearly indicating that "something" should be in those spaces. When I look at those same pages with Chrome or Opera, everything is filled the way it should be ... all content is displaying properly.
On some sites, like this forum, the rendering is even worse because not only do some items not show up, but in addition most of the links don't work at all. For example, if I use Iceweasel 4.0 to look at the board index of this forum, I can't click on any of the links, not the links in the main sections anyway. If I open up Chrome (that's what I'm using to write this) or Opera, the problem is gone.
What the heck is going on, does anyone know? Is this an Iceweasel bug? Am I missing some package update? I'd hate to have to switch my preferred browser just because this weirdness is going on. At first I thought it was a fluke, specific to a site or two only, but at this point I've seen these rendering issues on about 10 sites ...
How can i change that login window's font rendering, i mean that screen which you can select user and type password. Is anybody have the experience for tweaking gnome login font or background image?
according to [URL]... glx server only supported in 2.6-32-21-generic. so to get 3d rendering support i need to compile a that kernel version in squeeze or install from sid/experimental?
I've been trying to get hardware acceleration (Direct Rendering) working on my system without success. I'm not even sure if my card supports DR or not, my searchs haven't turned up a result for this question. I don't know if its the video card, nvidia packages or bad configurations. Any help with the diagnosis?
I guess this is a part deux, since I already posted one rendering issue which was eventually resolved ... having to do with the themes of this Debian Forum. Well, I don't know if this is related to that, but yesterday I noticed on another site that my Iceweasel 4.01 is not displaying portions of pages properly. See attached images. Both Chrome & Opera display that page correctly, I've included a screenshot of the same page with Chrome. I have JAVA installed and everything works perfectly fine accross the board on all browsers, except for this "once in a while" issue with Iceweasel. I've noticed this "missing content oddity" on three sites so far (out of 50 or more). No problem with eBay, craigslist, paypal, and other major players.
Open the images with a new tab, then compare both images side by side for best results. Iceweasel: [url] Chrome: [url]
I've been working on this off and on for the last couple of days and I can't seem to get this working. I'm using the latest Catalyst Control Center (11.5) and I've also got xorg.conf set up for this resolution. If I switch the driver in xorg.conf to radeon from fglrx, I can get my 1920x1080 resolution (only on GNOME;the login screen and Fluxbox have a black bar on the left that cuts off about a quarter of the screen). When using fglrx and Catalyst Control Center, I can only get a maximum resolution of 1600x1200.
I've set up this new PC, the graphic card I picked is the ATI R7 260X, pretty good card with lots of core processors, high clock and 2GB memory. I'm now currently using the 14.4 catalyst drive, it works actually alright, though, there are some mishaps with this driver:
First my hdmi screen had scale down, leaving black borders around, even though the catalyst control said the correct native resolution, this turned out to be a underscan that fglrx does and I've finally managed to fix it. Other caveat is that the screen simply won't suspend or turn off( via software), DPMS actually works, forcing it turns the screen blank for some seconds but something does not allow the screen to sleep.
Performance wise it seems pretty good though, everything is pretty smooth, being able to play games maxed out on resolution and ultra settings, though, I still haven't tested out that many games.
The open-source radeon on the other hand, well its open-source, fully xorg and linux compatible, which is a major plus point. It seem it has come a long way, supporting lot of features and providing better performance in some cases.
Before installing Catalyst I had issues with mesa and steam, steam would complain about not finding the 32bit libraries, this is however a steam runtime issue, maybe it could already be fixed.
I've been using linux distros on my desktop forever, and got a windows 10 laptop recently. I want to dual-boot debain (jessie), so I installed it and it worked fine. Unfortunately, I have to enable Legacy mode in BIOS to boot into my grub then linux machine. Is there a way I can have my computer boot without legacy boot?
how to replace grub2 with grub-legacy hassle-free? I mean, is there any danger in doing the following procedure: purging grub2 and installing the legacy version after that? I'm using Squeeze system with ext4.
I downloaded Catalyst 9.3 and tried to install, but it doesn't want to install, sorry, but i can't paste you error message, because my laptop is far away from me now. I can do it tomorrow. May be it is just impossible to install ATI Catalyst 9,3 on lenny and i should try a lower version of Debian? Could u suggest me what to do? I searched over the net for a long period of time, but found nothing relevant to my problem.
Legacy Hardware I have a chunk of hardware I bought in 2005 that came with Windoze verzhun Whatever. Very soon after buying it I decided to discard the trash that came with it, and installed Mandrake. I lived with Mandrake for a while until I decided to install Debian. Debian lasted me very well, until Lenny became Squeeze.All of a sudden, my hardware was slow. I couldn't keep up. Lenny had seen my applications crash more and more often, but Squeeze just couldn't keep me in the race. I chose to go to Ubuntu.
With my hardware, Ubuntu 10.10 just would not see my disks. Ubuntu 9.10 could not install grub. I tried everything - take a look at a google forum that I didn't look at, if you can.Ubuntu 8.04 loads and runs without any special work. I suggest that Ubuntu 9.10 and 10.10 have special hardware requirements.
root@gizmo:~# lshw gizmo description: Desktop Computer product: System Product Name
