Can Fedora 14 users use Gnome 3?

Another influx of visitors searching for the answer to this question. I think this is probably coming from listing the referring keywords right on the page, and then Google indexing those. Anyway, to answer the question, apparently not, at least not via official RPMs:

Hi

GNOME 3 won’t be available as a update to Fedora 14. You can try the Fedora 15 Beta that is about to be released in a few days.

Perhaps not you wanted but you can try the Live CD at

http://gnome3.org/tryit.html
__________________
Rahul
http://fedoraproject.org/wiki/RahulSundaram

Source: http://forums.fedoraforum.org/showthread.php?p=1459175
Continue reading “Can Fedora 14 users use Gnome 3?”

Clean install of FC14, regain Radeon X1600 support (!)

So I was complaining the other day about losing support for the Radeon X1600 when I upgraded my work laptop from FC12 to FC14. I was on the verge of ordering a new laptop (ThinkPad W510 with quadcore i7 and 1GB Quadro looks niiiice…) when I figured it was worth at least giving a true clean install a shot. I backed up all my stuff to an external USB drive, repartitioned my drive (finally done in a sane way), did a fresh FC14 install, and miraculously everything seemed to work. rsynced all my stuff back over and it was almost perfect. I still have a weird issue when trying to unlock my screen after it goes into screensaver – basically I can’t, it just stays locked and I’ve resorted to doing “init 3” and then “init 5” to make it work again. That’s a minor annoyance though at this point. So, yay again for Fedora! I wouldn’t go with ATi for a Linux machine again though.

Upgrading FC12 to FC14, lose support for Radeon X1600

I’d been running FC12 for quite a while and I noticed the past few weeks have been devoid of yum updates (except for Google Chrome). I figured FC15 is on the horizon; now’s a good time to upgrade to FC14.

I followed the basic procedure laid out here and went 12 -> 13 no problem. 13 -> 14: problem. The upgrade appeared to go well (loooong time to complete, downloading/installing 1+ gigs of packages, even over my 25 mbps home line) but X would not start no matter what. At this point I learned that system-config-display has been deprecated in FC14 and isn’t even there! I tried “Xorg –configure” but that configuration still didn’t work. I then tried doing a yum downgrade to FC13… let me save you the trouble: never try this.

I ended up downloading the FC14 DVD ISO and burning it, and doing a fresh install (repair, of course, just drops you to a shell – the equivalent of throwing you a life preserver in the middle of the ocean and leaving you there) without touching any of my existing partitions. This ended up being pretty painless and after it was complete everything worked. Or so it seemed…

I did the FC14 fresh install on Saturday (after having borked the laptop on Friday). At work on Monday I plugged in my secondary monitor and immediately noticed weirdness. Lines all over both displays, the Gnome panel unusable, any window that was created wasn’t drawing properly. And the topper was rebooting didn’t work – it would go to this colorful jumbley screen and just sit there until I did a hard poweroff. If I unplugged the external monitor and turned the computer on, it worked fine.

I’ve tried several things – installing the akmod-catalyst stuff and x11-catalyst-drv stuff via yum, but none of that seems to make much of a difference. livna-display-config throws an error that I don’t have the radeon drivers installed. I’ve tried the official ATI radeon driver for X1600, which complains that it can’t find XFree86. I tried to get around this by symlinking /usr/bin/Xorg to /usr/bin/XFree86, which got me past that hurdle, but then it complained that I have no adapter. I tried the other Linux radeon driver, which didn’t complain about XFree86 at least, but also said it didn’t find any AMD/ATI adapters.

At this point it seems these are my options:

  • Live with one monitor (annoying)
  • Downgrade/reinstall to FC13 (eventual obsolescence)
  • Switch OS (Not an Ubuntu fan; Win7 doesn’t really make sense)
  • Switch to Mac (can’t imagine using one for work)
  • Buy a new computer and put FC14 on it (my C2D T7200 is kind of old…)

None of these options is very good. For now I’m just sticking with 1 monitor. Not the end of the world, but it’s annoying to run a WinXP VM and do my regular tasks inside a single screen.

dmesg below showing stupid errors:

[root@ehoffman ~]# aticonfig
aticonfig: No supported adapters detected
[root@ehoffman ~]# uname -a
Linux ehoffman 2.6.35.10-74.fc14.x86_64 #1 SMP Thu Dec 23 16:04:50 UTC 2010 x86_64 x86_64 x86_64 GNU/Linux
[root@ehoffman ~]# lspci | grep -i radeon
01:00.0 VGA compatible controller: ATI Technologies Inc M56P [Radeon Mobility X1600]
[root@ehoffman ~]# dmesg | grep -i radeon
[   14.717757] [drm] radeon defaulting to kernel modesetting.
[   14.717761] [drm] radeon kernel modesetting enabled.
[   14.717827] radeon 0000:01:00.0: setting latency timer to 64
[   14.723052] radeon 0000:01:00.0: VRAM: 256M 0x00000000 - 0x0FFFFFFF (256M used)
[   14.723056] radeon 0000:01:00.0: GTT: 512M 0x10000000 - 0x2FFFFFFF
[   14.723167] radeon 0000:01:00.0: irq 48 for MSI/MSI-X
[   14.723174] radeon 0000:01:00.0: radeon: using MSI.
[   14.723211] [drm] radeon: irq initialized.
[   14.723322] [drm] radeon: 256M of VRAM memory ready
[   14.723325] [drm] radeon: 512M of GTT memory ready.
[   14.725519] [drm] radeon: 1 quad pipes, 2 z pipes initialized.
[   14.733804] [drm] radeon: ring at 0x0000000010000000
[   14.734017] [drm] radeon: ib pool ready.
[   14.734446] [drm] Radeon Display Connectors
[   14.844393] [drm] radeon: power management initialized
[   15.295827] fbcon: radeondrmfb (fb0) is primary device
[   15.296451] fb0: radeondrmfb frame buffer device
[   15.296546] [drm] Initialized radeon 2.5.0 20080528 for 0000:01:00.0 on minor 0
[root@ehoffman ~]#

Edit: I should probably mention that as soon as I install the xorg-x11-drv-catalyst stuff, X won’t start. If I remove it, it boots up fine (though the 2nd monitor screws causes it to freak out). This is pretty strange; I’ve done it several times to confirm:

Feb 08 11:35:09 Erased: fglrx64_6_9_0
Feb 08 11:36:53 Updated: libuuid-2.18-4.8.fc14.i686
Feb 08 11:36:54 Updated: postgresql-libs-8.4.7-1.fc14.x86_64
Feb 08 11:36:54 Updated: libuuid-devel-2.18-4.8.fc14.x86_64
Feb 08 11:41:52 Updated: google-chrome-stable-9.0.597.94-73967.x86_64
Feb 08 11:44:11 Installed: fglrx64_7_5_0-8.812-1.x86_64
Feb 08 11:48:21 Erased: fglrx64_7_5_0
Feb 08 12:25:01 Installed: xorg-x11-drv-catalyst-libs-10.12-2.fc14.x86_64
Feb 08 12:25:07 Installed: xorg-x11-drv-catalyst-10.12-2.fc14.x86_64
Feb 08 12:25:08 Installed: akmod-catalyst-10.12-1.fc14.x86_64
Feb 08 12:39:16 Erased: kmod-catalyst-2.6.35.10-74.fc14.x86_64
Feb 08 12:39:20 Erased: xorg-x11-drv-catalyst-libs
Feb 08 12:39:21 Erased: xorg-x11-drv-catalyst
Feb 08 12:39:21 Erased: akmod-catalyst

How to install the 64-bit Sun Java plugin on 64-bit firefox on 64-bit Fedora Core 11 Linux (which happens to use 64 bits)

I’m giddy! I found this post on mozdev.org which was magical.

[evan@ehoffman ~]$ java -version
java version "1.6.0_17"
Java(TM) SE Runtime Environment (build 1.6.0_17-b04)
Java HotSpot(TM) 64-Bit Server VM (build 14.3-b01, mixed mode)
[root@ehoffman plugins]# uname -a
Linux ehoffman 2.6.30.8-64.fc11.x86_64 #1 SMP Fri Sep 25 04:43:32 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux
[root@ehoffman plugins]# pwd
/usr/lib64/mozilla/plugins
[root@ehoffman plugins]# ln -s /usr/java/jdk1.6.0_16/jre/lib/amd64/libnpjp2.so

The main thing I was missing was that the plugin isn’t libpluginjava_oji.so, or whatever I thought it was, but libnpjp2.so. Once I created the symlink into /usr/lib64/mozilla/plugins it worked (as verified on http://www.java.com/en/download/help/testvm.xml and http://www.java.com/en/download/installed.jsp).

That’s all it takes to get the Sun Java plugin working in Firefox on Linux.