Is installing the ATI proprietary driver fglrx supported on Siduction? There is a section in the Bluewater manual on the nVidia proprietary driver, but nothing similar for ATI.
The reason I ask is because my HD6770 card runs very hot with the open source radeon driver. I have tested this in Ubuntu, Sabayon, and Arch and my card runs about 15-20C cooler with fglrx. The fan also runs slower, consequently.
In Siduction, I have attempted to install the driver downloaded directly from AMD, but I had conflicts both with the 3.4 kernel and Xorg. I also tried installing it with the smxi scripts. However, I have fglrx running successfully on Sabayon and Arch Linux with kernel 3.4 and Xorg 1.12.
Tim
AFAIK: fglrx does not work with the current xserver. So it is _pointless_ to install that driver. But towo is the expert, I'm sure he'll chime in soon.
fglrx 12.6 supports xserver 1.12.x but the kernel 3.4 is not supported by fglrx. Btw many users has told, that fglrx 12.6 does not work in 64bit at the moment.
Thanks. I will not try to push my question but, like I said, I do have Catalyst 12.6 working with Xorg 1.12 on Arch Linux with 3.4.2 kernel 64-bit. I need to check the exact versions I have on Sabayon 9, but it is also a 3.4 64-bit kernel.
I will wait, patiently..
Tim
Since i don't use fglrx i can only tell, what users have sayed.
Maybe th 64bit problem only exist in debian.
Ok, thank you, towo.
Tim
I believe I have found the solution, but it is somewhat complicated and I am not sure I want to mess with it. It involves making sure to have the exact correct version of xserver-xorg-core and "pinning" it so it does not get updated. What a mess.
These instructions are for Debian sid, so I assume they would also work for Siduction.
http://packages.debian.org/sid/fglrx-driver
http://wiki.debian.org/ATIProprietary
Tim
Again, the xserver in sid is not the problem for fglrx in sid, since
fglrx 12.6-beta is in sid.
You can't use fglrx on kernels > 3.3.x and in siduction we have 3.4.4 at the moment.
If you have running fglrx in Arch with linux 3.4.x, then for sure the fglrx-kernel-module is patched, otherwise it would not work.
simple minds like positive expressions:
Stick with Debian Wheezy Linux-3.2 and fglrx-beta without needles and pins.
Ok, thanks again, towo and ralul. I give up.
Tim
I have at least found a workaround for the open source driver making the ATI video card run very hot:
echo low > /sys/class/drm/card0/device/power_profile
https://bugs.freedesktop.org/show_bug.cgi?id=41762
My card is now running about 15C cooler.
Tim
Yes, put this command into your /etc/rc.local
There is a AMD Catalyst Driver You can download from the AMD Site. There's 12.10 and 12.11 Beta Drivers that can be used with 64bit and kernel 3.6. I'm running the Liquorix kernel and Catalyst 12.10 without a problem. If you want 12.10, in a terminal:
wget http://www2.ati.com/drivers/linux/amd-driver-installer-catalyst-12.10-x86.x86_64.zip
unzip amd-driver-installer-catalyst-12.10-x86.x86_64.zip
sudo sh ./amd-driver-installer-12-10-x86.x86_64.run
If you want 12.11 Beta go here:
http://www2.ati.com/drivers/beta/amd-driver-installer-catalyst-12.11-beta-x86.x86_64.zip
unzip it then open a terminal:
sudo sh ./amd-driver-installer-12-11-beta-x86.x86_64.run
Enjoy!
This is not ubuntu, this is sid. So most of the year the prop. drivers are broken badly. Please recommend prop. drivers directly from ati only if you are able and willing to fix a lot of broken systems.
I'm not running ubuntu, I'm running sid on lmde with the liquorix 3.6 kernel and i have an amd radeon chipset. The 12.10 Catalyst is NOT a beta driver.
The amd-run-installer is breaking every deb based system.
Especialy if multiarch is needed, have fun with this shit.
And btw, fglrx 12.10 is in sid, so no need to break things.
deb http://packages.linuxmint.com/ debian main upstream import incoming backport romeo
deb http://ftp.debian.org/debian unstable main contrib non-free
deb http://www.deb-multimedia.org sid main non-free
lmde with sid
And, what you will tell us?
This is a siduction forum, so please stay with our rules or search another forum.
Feel free to delete my user forum account. After reviewing the resonse from the moderators, I find I no longer have any interest in using siduction for any purpose whatsoever. Good riddance!
With xserver-xorg-video-radeon installed, VGAswitcheroo can be used to switch dual GPUs and turn off an inactive GPU.
mount -t debugfs debugfs /sys/kernel/debug
echo OFF > /sys/kernel/debug/vgaswitcheroo/switch
This How-To article on VGA_switcheroo was helpful:
http://www.linuxquestions.org/questions/slackware-14/how-to-switch-between-graphics-processors-using-vga-switcheroo-4175437338/
Kernel Mode Settings that work similarly to fglrx to manage the GPUs are already active. The problem is that GPUs are set to run at maximum by default.
These two articles were most helpful for learning about the KMS options and creating a script to run them at boot:
http://radeon.koolfy.be/tag/power-management/
http://www.techytalk.info/ubuntu-open-source-ati-radeon-driver-power-usage-tweaks/
I opted to use the 'dynpm' option so both GPUs in my HP Dv7-4170us with Radeon HD 4250/5470 could remain active but run cooler and use less power. Unfortunately, they still run hotter than when using Windows 7 and Catalyst - there is no workable fglrx driver known to me for this HP laptop.
The KMS and VGA_switcheroo methods can be used together to manage dual GPUs. For example, the discrete GPU can be deactivated with VGA_switcheroo until it is needed - doing so on my HP machine reduced temperature by 8 to 10 degrees Celcius.
Quote from: "lizbeth"Feel free to delete my user forum account. After reviewing the resonse from the moderators, I find I no longer have any interest in using siduction for any purpose whatsoever. Good riddance!
It would be very easy to nuke your account. However, you might (eventually) find there are things you can learn here, and reasons why we don't encourage using third-party repos, especially for drivers, and perhaps you might come to a different point of view about participating in the siduction community. So you can keep your account --- "just in case".
:)
When will fglrx ever run smoothly on sid anyway? Its just a sad state of affairs,while nvidia's driver is quite usable in comparison
Quote from: "DeepDayze"Its just a sad state of affairs,while nvidia's driver is quite usable in comparison
Sad, yes, and kind of strange too, when you consider how "evil" the binary blob is considered by the FOSS advocates, and how AMD are supposedly the more cooperative with open source developers.
Quote from: "dibl"Quote from: "DeepDayze"Its just a sad state of affairs,while nvidia's driver is quite usable in comparison
Sad, yes, and kind of strange too, when you consider how "evil" the binary blob is considered by the FOSS advocates, and how AMD are supposedly the more cooperative with open source developers.
Yet the open AMD driver still has issues with power management for example.
dibl: There is nothing strange with the catalyst. The fact is that the amd people develop mainstream. We are not mainstream :P. Without joking - the ati-driver works well with a lot of distributions. Unfortunally unstable and testing debianoids are not the best choice because of the structure of the most repos.
to be happy with the catalyst it needs a) a matching X-Server and b) a matching kernel. Booth you will find in stable (or Arch ..). Beside of these issues its a good idea to learn to patch and build booth Server and/or drivers. That was my start with ubuntu and debian-packaging. It's a little bit steep learning curve, but it is worth it. (OK, one can think about using intel or nvidia right from the start :twisted: )
Quote from: "agaida"
to be happy with the catalyst it needs a) a matching X-Server and b) a matching kernel. Booth you will find in stable (or Arch ..). Beside of these issues its a good idea to learn to patch and build booth Server and/or drivers. That was my start with ubuntu and debian-packaging. It's a little bit steep learning curve, but it is worth it. (OK, one can think about using intel or nvidia right from the start :twisted: )
I see -- so, with our frequent kernel updates in sid, we would have to rebuild our X-server and catalyst packages for every new kernel (or pin our kernel for a few months).
The first computer that I tried Ubuntu on had an ATI card in it, and the difficulties that I had configuring a /etc/X11/xorg.conf file were so painful that I nearly gave up the project. (Of course I am now very glad that I stayed with it.) But ever since that terrible experience, I have built my computers with Nvidia cards (or bought them with Intel chips). There are too many better ways to spend time in life, than wrestling with such difficulties when you have another choice.
Wow -- this thread has become very philosophical -- I hope the OP is not offended! :)
@dibl - No problem for the OP.
@DeepDayze - I have learned to deal with the power management problems. If you want any help, let me know.
Tim
System: Host: amd-box Kernel: 3.9.0-rc7-experimental-686 i686 (32 bit, gcc: 4.7.2)
Desktop: Xfce 4.10.2 (Gtk 2.24.10) Distro: siduction 12.2.0 Riders on the Storm - xfce - (201212092126)
Machine: System: FUJITSU SIEMENS product: ESPRIMO E
Mobo: FUJITSU SIEMENS model: D2464-A2 version: S26361-D2464-A2
Bios: FUJITSU SIEMENS // Phoenix version: 6.00 R1.14.2464.A2 date: 05/22/2007
CPU: Dual core AMD Athlon 64 X2 3600+ (-MCP-) cache: 1024 KB flags: (lm nx pae sse sse2 sse3 svm) bmips: 4018.24
Clock Speeds: 1: 1000.00 MHz 2: 1000.00 MHz
Graphics: Card: Advanced Micro Devices [AMD] nee ATI Caicos [Radeon HD 6450] bus-ID: 03:00.0
X.Org: 1.12.4 driver: fglrx Resolution: 1280x1024@60.0hz
GLX Renderer: AMD Radeon HD 6450 GLX Version: 4.2.12172 - CPC 12.10.17 Direct Rendering: Yes
Network: Card: NVIDIA MCP51 Ethernet Controller driver: forcedeth port: 8c60 bus-ID: 00:14.0
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: 00:19:99:0c:92:42
Drives: HDD Total Size: 160.0GB (-) 1: model: SAMSUNG_HD161HJ
Info: Processes: 135 Uptime: 1:24 Memory: 247.3/3040.9MB Runlevel: 5 Gcc sys: 4.7.2
Client: Shell (bash 4.2.45) inxi: 1.8.45
I don't see the problem. ;)
Quote from: "towo"
I don't see the problem. ;)
Says the guy who makes the kernels!
:lol:
You see, that i have running fglrx?
towo@amd-box:~$ dpkg -l | grep fglrx
ii fglrx-atieventsd 1:13.3~beta3-0.siduction.1 i386 external events daemon for the non-free ATI/AMD RadeonHD display driver
ii fglrx-control 1:13.3~beta3-0.siduction.1 i386 control panel for the non-free ATI/AMD RadeonHD display driver
ii fglrx-driver 1:13.3~beta3-0.siduction.1 i386 non-free ATI/AMD RadeonHD display driver
ii fglrx-modules-dkms 1:13.3~beta3-0.siduction.1 i386 dkms module source for the non-free ATI/AMD RadeonHD display driver
ii glx-alternative-fglrx 0.2.90 i386 allows the selection of FGLRX as GLX provider
ii libfglrx:i386 1:13.3~beta3-0.siduction.1 i386 non-free ATI/AMD RadeonHD display driver (runtime libraries)
ii libfglrx-amdxvba1:i386 1:13.3~beta3-0.siduction.1 i386 AMD XvBA (X-Video Bitstream Acceleration) runtime libraries
ii libgl1-fglrx-glx:i386 1:13.3~beta3-0.siduction.1 i386 proprietary libGL for the non-free ATI/AMD RadeonHD display driver
That's why i do not see the problem.
http://siduction.org
Strange - but work for me. Sorry for change your post, JustDebian. Really don't know, whats going on. F*** bbcode-rendering :twisted:
:?
Quote from: "agaida"
Strange - but work for me. Sorry for change your post, JustDebian. Really don't know, whats going on. F*** bbcode-rendering :twisted:
Thank you for fixing that. I think I caused the problem by not highlighting text before clicking the 'url' button.
Sorry for the problem. :oops:
Good morning, stressed people out there
Quote from: "towo"You see, that i have running fglrx?
That's why i do not see the problem.
if somebody finds the adequate glx-alternate-fglrx package version (0.2.90) from the experimental repository, then there is no problem.
Not everybody is using experimental either.....
Wolfen
Since my ti 4890 pass away i'm a happy user of a ten years old passive nvidia 7300gt. Wow, what a card. Faster then the 4890 with linux, not so noisy and the evil blobs work perfect :D
After an installation of the amd fglrx drive 13.4 (i followed this advice: http://crunchbang.org/forums/viewtopic.php?pid=312471#p312471) i've some positive results:
- Standby finally works
- it's getting definitively less hot
- battery is lasting way longer
(And that's great! Before, and above any kernel newer than 3.2, there were practically not any reasonable powermanagement which is not so fun on a laptop mad ).
BUT: I lost the console Ctrl-Alt-F1 thru F6! They result in dark, dead window. Although, Ctrl-Alt-F7 brings me back to X. The same happens if i'm calling smxi or if i choose Rightclick->Exit->Logout.
Is there a simple, harmless way to get the consoles back?
Trying the other existing kernels (which worked but also without any reasonable powermanagement), starts but with some, ugly, screen distortion. When i try to get into the console from there happens the same like with my "main" kernel whereto i installed the fglrx-driver.
My laptop is a Samsung 535U3C running kernel 3.9-4.towo-siduction-amd64 (#1 SMP PREEMPT Sat May 25 15:50:25 UTC 2013) & crunchbang waldorf tracking sid.
Thanks in advance for any help!
PS. Sorry if it's hurting i'm using crunchbang.