Magma Digital » Fedora

YuuGuu on Linux x86_64 (64bit) CPUs

Jeremy Coates — Thu, 08 Jan 2009 16:36:54 +0000

Here at Solution Perspective we use YuuGuu quite a lot, especially with some of our clients, for remote screen sharing and to check out that we’re all talking about the same things or to take control of their screens to sort an issue out. We also happen to use Linux (Fedora in particular) a lot, and several of our machines are 64bit (x86_64 processors). For quite some time we’ve had to use, the fairly brilliant Linux – Windows layer called Wine to get YuuGuu to run on our Linux boxes.

Well no more! YuuGuu have released a native Linux version, available for Ubuntu, Fedora and Suse flavours (which can probably be coaxed to work on other distributions as well). This works fine for i386 (32bit) CPUs but not on our machines with the 64bit ones.

After a bit of digging and playing about, we’ve found they’ve also got native 64bit versions in testing and that works well, so there’s no more need for us to use Wine in order to run this very useful screen sharing application – life’s a little less complicated now.

IP 1000A ethernet driver Fedora 7

Jeremy Coates — Sat, 25 Aug 2007 22:03:00 +0000

Discovered today that a previously working ethernet driver for the IP1000A chipset stopped working when upgrading to the latest Fedora 7 kernel (2.6.22.1-41). When compiling the driver there’s now output indicating a problem:

ipg_main.c:4045: warning: implicit declaration of function ‘pci_module_init’

If you’ve installed or upgraded to Fedora 7 (or are running a 2.6.22+ kernel) along with an ethernet adapter using the IP1000A chipset (e.g. from /sbin/lspci getting something similar to "Sundance Technology / IC Plus Corp IP1000 Family Gigabit Ethernet" – running on an Abit motherboard here) and are using the drivers as found at http://www.icplus.com.tw/driver-pp-IP1000A.html (and this zip file in particular) then you’ll need the following mod for the source code:

Suspend / resume finally working Acer Ferrari 4005WLMi

Jeremy Coates — Thu, 15 Mar 2007 21:54:54 +0000

The day has finally come, my laptop finally suspends and resumes correctly under Fedora Core 6 – it’s mostly got part way through the suspend operation before and then hung, or on the few occasions where it shutdown, it would hang or panic on resume.

Today using kernel 2.6.19-1.2911.6.5.fc6 it worked – suspend all the way to power off, and on resume even got the WiFi fired back up. The only one minor thing it didn’t quite pull off was getting the attached usb hard drive back in action – a quick unplug and replug later and it’s sorted.

This is quite cool, however I’m just in the middle of downloading another kernel update and I hope that keeps the progress made with suspend and resume on this laptop.

VMware need to re-run vmware-config.pl every reboot on linux

Jeremy Coates — Thu, 29 Jun 2006 10:47:21 +0000

I found using VMware server or workstation on udev based linux kernel (2.6.x) hosts, that I had to re-run the vmware-config.pl script after every reboot – which is quite annoying when you want the guest OS to run as the service starts.

The issue is that due to udev being a dynamic system, nodes are wiped and re-created in /dev each boot. So the simple solution is to get the VMware init script to check for and re-create the nodes as required:

Add the following just under the start) line in /etc/init.d/vmware

   start)
# Start insert
      if [ ! -e "/dev/vmmon" ]; then
         mknod /dev/vmmon c 10 165
         chmod 600 /dev/vmmon
      fi
      for a in `seq 0 9`; do
         if [ ! -e "/dev/vmnet$a" ]; then
            mknod /dev/vmnet$a c 119 $a
            chmod 600 /dev/vmnet$a
         fi
      done
# End insert
      if [ -e "$vmware_etc_dir"/not_configured ]; then

Which recreates the nodes that are required – just need VMware to pick that up for future versions. Remember, you’ll still need to re-run vmware-config.pl after a kernel upgrade.

Yum upgrade FC4 to FC5 dbus session failure

Jeremy Coates — Tue, 06 Jun 2006 09:35:10 +0000

Just solved an issue on a machine upgraded via yum from FC4 to FC5 tha had been bugging me for ages. The symptoms were that gnome power manager would fail with a message saying that dbus was not running and that eval `dbus-launch –auto-syntax` needed to be run.

The other symptom I noticed was that dbus-monitor or anything else that connected to dbus session would fail with a ‘connection refused’ message.

After trawling round the net, I found a Redhat Bugzilla posting that resolved the issue – between FC4 and FC5 the location of dbus-daemon had moved from /usr/bin to /bin (and also dbus-cleanup-sockets). The yum upgrade for the dbus packages had not removed the FC4 versions from /usr/bin so a quick rm /usr/bin/dbus-daemon and rm /usr/bin/dbus-cleanup-sockets followed by a reboot sorted the problem altogether.

Perhaps that should be added to the Yum upgrade FAQ on Fedora wiki. Another small but annoying problem resolved