Many of my traditional blog post live on this site, but a great majority of my social-style posts can be found on my much-busier microbloging site at updates.passthejoe.net. It's busier because my BlogPoster "microblogging" script generates short, Twitter-style posts from the Linux or Windows (or anywhere you can run Ruby with too many Gems) command line, uploads them to the web server and send them out on my Twitter and Mastodon feeds.
I used to post to this blog via scripts and Unix/Linux utilities (curl and Unison) that helped me mirror the files locally and on the server. Since this site recently moved hosts, none of that is set up. I'm just using SFTP and SSH to write posts and manage the site.
Disqus comments are not live just yet because I'm not sure about what I'm going to do for the domain on this site. I'll probably restore the old domain at first just to have some continuity, but for now I like using the "free" domain from this site's new host, NearlyFreeSpeech.net.
Thanks to the help of a few, proud Fedora users, I was able to install the AMD Catalyst 13.11 beta (version 9.95 to be exact) driver on my Xfce-running Fedora 20 system.
And thus the long local (as opposed to national) nightmare of poor video performance and a CPU running 30 to 40 degrees hotter is over.
I would love to stick around and wait for the open-source Radeon drive to get better, and I'll continue to keep an eye on it. But my test of the 3.13.rc7 Linux kernel -- which is supposed to include some key Radeon patches -- showed that it is no better on my machine than 3.12.x. That means it's not time to wait on the open driver but instead time to get serious about putting Catalyst -- direct from AMD -- on the laptop.
Today I was successful, and the CPU on my HP Pavilion g6-2210us is running at a cool 80 degrees as opposed to the not-as-cool 120 degrees under Radeon. And I can watch full-screen video in VLC (and any player other than MPlayer) without a) that video stuttering and b) both CPU cores jumping to 100 percent.
Update: Thanks to tips from Bernhard J. Wolf, I have successfully installed the AMD Catalyst 13.11 beta driver in Fedora 20. I did not need to use Maxorete's install-file hack. When I opened the file that needed to be changed, it looked like AMD had already made the fix -- and since Catalyst did install, I can confirm that they did. Thanks, AMD! Keys to success were adding the kernel-devel package in Fedora. It probably couldn't hurt to make sure you also have kernel-headers, which I already had. Bernhard also said the installation wouldn't work with GNOME installed. GNOME, you are now history on this machine. With kernel-devel and without GNOME, the install of AMD Catalyst 13.11 beta went like butter. I will do a new post that contains all of this information, but for now I leave what I wrote earlier today in its original form below. You know, for history's sake:
Original post below (I didn't need the install-file hack)
Anybody who has read anything I've written in the past month know that the sudden absence of the AMD Catalyst driver in packaged-for-Fedora form is really chapping what's left of my Linux hide. The fact that so few seem to care is just stamping my "get out of Dodge/Fedora" ticket.
But given momentum's pull, principally the fact that I have Fedora set up the way I want it, I'd rather stay for now and move at some time in the future. When I'm ready, that is.
So I've gone against the advice I've held to since Fedora 14 crapped out on me, that advice being, Don't install Catalyst directly from AMD.
Update on Jan. 16, 2014: Since I originally wrote this post, I succeeded in installing Catalyst with AMD's script in Fedora and buying myself a whole lot of time with that distribution. I also tried Debian Wheezy with live media containing nonfree firmware, and that is looking even better than Jessie if I don't want/need an EFI-friendly installer. My original plan was to stick with Fedora until the Debian Jessie freeze and then make the move (sometime late this year). But if Wheezy works out, I'd want to go to it sooner rather than later and avoid Jessie for as long as possible (or until suspend/resume somehow returns to my neglected AMD APU chip.
Update on Feb. 4, 2014: I have suspend/resume working in Fedora 20 with the fglrx/Catalyst driver, and I'm very confident that the same technique I used to get it working there will also work in Debian Jessie, so that means if I do want to run Debian in the near future, I can get working fglrx video, working suspend/resume and EFI booting with Testing/Jessie and don't need to use Wheezy unless I absolutely want to. The only thing that makes me nervous about installing Jessie now is the uncertainty over which init system Debian will end up with -- both in the Jessie and Jessie+1 cycles. But since I have everything but printing to my crappy HP USB printer working in Fedora, it's likely that I'll stick with it for the near (and maybe farther) future.
To keep a short story short, the maintainer of the proprietary AMD Catalyst (aka fglrx) driver for the Fedora-focused RPM Fusion repository doesn't want to do it anymore.
And he made this decision not before the release of Fedora 20 with lots of notice -- and not after with lots of notice BUT PRETTY MUCH DURING THE RELEASE with no notice.
That means my Fedora 19-to-20 upgrade left me without Catalyst. And that means much poorer video performance, higher heat and more fan noise for my newish AMD APU chip -- the Trinity series A4-4300M model with AMD Radeon HD 7420g graphics.
And while the open-source Radeon driver has gotten a whole lot better in the 3.12 Linux kernel, the Catalyst driver is much, much better for this hardware.
I already mentioned the slow video. I can barely run GNOME 3 with the open driver, and THIS LAPTOP ISN'T EVEN A YEAR OLD.
Read the excellent year-end proprietary AMD Catalyst and free Radeon driver roundup from Phoronix and find out why I'm recommending against buying AMD hardware for Linux
I got a lot out of reading Michael Larabel's AMD Catalyst 2013 Linux Graphics Driver Year-In-Review on his Phoronix site.
He's been following all of the Linux video drivers for years, and his perspective is very valuable, especially in his assessment that it's been a horrible year for the proprietary Catalyst driver and a great one for the open Radeon driver.
I can confirm that I finally have 3D acceleration in the open Radeon driver on the 3.12.x Linux kernel but that the performance isn't what it is with the Catalyst driver. That Fedora users might no longer have a choice between the two when it comes to a pre-packaged driver is troubling.
But thanks, Michael, for a thorough look at AMD graphics and Linux.
Of course things are going better for Nvidia, Michael reports.
That's cold comfort for me with my AMD hardware, and while desktop users can generally chose to shove an AMD or Nvidia card into the box, there aren't all that many laptops with Nvidia chips on them. No, AMD is a whole lot more common, especially if you're trying to save a few dollars over an Intel-based laptop.
So overall, it's pretty much AMD vs. Intel when it comes to laptop graphics, and AMD's extremely lackluster performance in 2013 is leading to me recommend against buying AMD hardware. While the open Radeon driver project is going from strength to strength, sometimes you need (and/or want) the proprietary driver.
And in 2013, there appears to be no contest when it comes to graphics for Linux. Intel and Nvidia are doing a lot. AMD is doing a whole lot less.
If you want to delve further into the rabbit hole that is Linux graphics, start at this part of Phoronix. Good luck. I really appreciate Michael Larabel's testing and writing, but I'd rather things just worked (and wish I had opted for an Intel-based laptop when I needed one on short notice in March of this year).