nick has a blog! » ubuntu http://www.nickpeters.net Thu, 16 Dec 2010 07:07:21 +0000 en hourly 1 http://wordpress.org/?v=3.0.3 Fix for “uninitialized constant Gem::GemRunner (NameError)” http://www.nickpeters.net/2007/12/31/fix-for-uninitialized-constant-gemgemrunner-nameerror/ http://www.nickpeters.net/2007/12/31/fix-for-uninitialized-constant-gemgemrunner-nameerror/#comments Mon, 31 Dec 2007 20:43:08 +0000 Nick http://www.nickpeters.net/2007/12/31/fix-for-uninitialized-constant-gemgemrunner-nameerror/ I tried upgrading my version of rubygems to the most current version by running
sudo gem update --system
Which introduced this error:
/usr/bin/gem:23: uninitialized constant Gem::GemRunner(NameError)
whenever I tried to run rubygems. On the rails forum, I found a fix for it!
Simply add the line to the file /usr/bin/gem (may be different on a mac)
require 'rubygems/gem_runner'
after
require 'rubygems'
This fixed the issue in both Ubuntu and OS 10.4.

]]> http://www.nickpeters.net/2007/12/31/fix-for-uninitialized-constant-gemgemrunner-nameerror/feed/ 100 Wireless Issues on Gutsy Gibbon (and a fix!) http://www.nickpeters.net/2007/10/17/wireless-issues-on-gutsy-gibbon-and-a-fix/ http://www.nickpeters.net/2007/10/17/wireless-issues-on-gutsy-gibbon-and-a-fix/#comments Thu, 18 Oct 2007 05:41:26 +0000 Nick http://www.nickpeters.net/2007/10/17/wireless-issues-on-gutsy-gibbon-and-a-fix/ I couldn’t wait and installed the latest RC of Gutsy Gibbon today. To my surprise the wireless did not work whatsoever! ifconfig didn’t list my interface, but it showed up when I ran lspci. I decided to boot into an older kernel (2.6.20) and it showed up! It must’ve been some sort of module that wasn’t loading in the 2.6.22 kernel. After doing some research I found out that this particular version of the kernel wasn’t loading restricted modules. If you’re having problems using devices that used to work in in Feisty Fawn try running this command:
sudo apt-get install linux-restricted-modules
After running this command my wireless drivers work (ipw2200bg) on my Dell Inspiron 9300.
I’m still trying to figure out how to get my screen resolution back to normal (It’s at 1680×1050 when it should be at 1920×1200). The moral of the story is to wait for everyone else to find the bugs before you make an upgrade!
Edit:
I fixed my display issue. Here’s a snippet of my xorg.conf file. Don’t simply copy and paste it, but use it as a reference to get yours to work
Section "Monitor"
Identifier "monitor1"
VendorName "Unknown"
ModelName "Unknown"
HorizSync 30.0 - 110.0
VertRefresh 50.0 - 150.0
Option "DPMS"
EndSection

Section "Device"
Identifier "Generic Video Card"
Driver "nvidia"
BoardName "nv"
BusID "PCI:1:0:0"
Screen 1
EndSection

Section "Device"
#
Identifier "device1"
Driver "nvidia"
BoardName "nv"
BusID "PCI:1:0:0"
Screen 0
EndSection

Section "Screen"
Identifier "screen1"
Device "device1"
Monitor "monitor1"
DefaultDepth 24
SubSection "Display"
Depth 24
Modes "1920x1200" "1440x900"
EndSubSection
EndSection
Afterwards I used System->Preferences->Screen Resolution to change the resolution and it works beautifully.
I recommend you make a backup of your xorg.conf file. Who knows when you might mess with it and everything goes wrong. It’s nice to have that backup in case things take a turn for the worse.

]]> http://www.nickpeters.net/2007/10/17/wireless-issues-on-gutsy-gibbon-and-a-fix/feed/ 0