For years and years I (as many others) have waited for Diablo 3. And now it’s finally here!!

For all gaming Linux people, one of the biggest excitements about new games is if they will run under Wine.

And Diablo 3 does.. Almost…

There are still some patching which haven’t (yet) been merged into standard wine, but besides of that it really runs well.

If you want to follow the way I run Diablo 3 on my Alienware X11M, here it goes:

Download the Diablo 3 installer from Battle.net. (just run with regular wine to download installer)

Download compiled modified wine (sorry I forgot where I got this):

Unpack it:

tar zxvf wine-diablo3.tar.gz

and place the folder diablo3-1.5.4 somewhere e.g. /home/<user>/games/Wine/

Create a Diablo 3 folder:

mkdir -p /home/<user>/games/Diablo\ III

Now run:

WINEPREFIX=/home/<user>/games/Diablo\ III/.wine /home/<user>/games/Wine/diablo3-1.5.4/usr/bin/winecfg (Just press ok, when configuration box appears.)

WINEPREFIX=/home/<user>/games/Diablo\ III/.wine winetricks vcrun2008 (install winetricks with “apt-get install winetricks”)

Install Diablo:

WINEPREFIX=/home/<user>/games/Diablo\ III/.wine /home/<user>/games/Wine/diablo3-1.5.4/usr/bin/wine <Diablo Installer exe>

If you having problems with the installer hanging, just copy the installed game from a Window$ box or something..

When the game is installed, start it with

WINEPREFIX=/home/<user>/games/Diablo\ III/.wine taskset -c 1 /home/<user>/games/Wine/diablo3-1.5.4/usr/bin/wine Diablo\ III.exe –launch

or if you are using Ironhide or The Bumblebee Project:

WINEPREFIX=/home/<user>/games/Diablo\ III/.wine optirun taskset -c 1 /home/<user>/games/Wine/diablo3-1.5.4/usr/bin/wine Diablo\ III.exe –launch

Happy gaming…

Signing service is now also working..

I’m still missing a few RHEL dependencies, but I hope to get this sorted out soon…

Once again, the installation instructions:

First of all, remember to setup either DNS or /etc/hosts to match hostname of the server…

RHEL6:

wget -O /etc/yum.repos.d/RHEL-CBS.repo http://download.opensuse.org/repositories/home:/martin-juhl:/branches:/openSUSE:/Tools/RHEL_6/home:martin-juhl:branches:openSUSE:Tools.repo

or

CentOS6:

wget -O /etc/yum.repos.d/CentOS-CBS.repo http://download.opensuse.org/repositories/home:/martin-juhl:/branches:/openSUSE:/Tools/CentOS_6/home:martin-juhl:branches:openSUSE:Tools.repo

For dependencies we also need the EPEL repository:

rpm -ivh http://ftp.crc.dk/fedora-epel/6/i386/epel-release-6-5.noarch.rpm

yum install obs-web-httpd obs-server obs-worker obs-api mysql-server

chkconfig obsworker on
chkconfig iptables off
chkconfig mysqld on
service mysqld start

Configure:
/etc/sysconfig/obs-server

Set:
OBS_API_AUTOSETUP=”no”
to:
OBS_API_AUTOSETUP=”yes”

and:
OBS_VM_TYPE=”auto”
to:
OBS_VM_TYPE=”none”

/etc/init.d/obsapisetup start

mv /etc/httpd/conf.d/ssl.conf /etc/httpd/conf.d/ssl.conf.bak

chkconfig httpd on
chkconfig obssignd on

reboot

Now go the servers IP-adresse/Hostname for the web-interface…

Login: Admin

Pass: opensuse

Everything seems to be running now, except for the obssigner..

obssigner needs obs-signd installed, and right now I have some problems building some of the dependencies.. but we’re moving forward..

If you have any comments/bugs/experiences .. feel free to contact me on Twitter.

A quick howto, on installing CBS/OBS on CentOS 6/RHEL 6:

RHEL6:

wget -O /etc/yum.repos.d/RHEL-CBS.repo http://download.opensuse.org/repositories/home:/martin-juhl:/branches:/openSUSE:/Tools/RHEL_6/home:martin-juhl:branches:openSUSE:Tools.repo

or

CentOS6:

wget -O /etc/yum.repos.d/CentOS-CBS.repo http://download.opensuse.org/repositories/home:/martin-juhl:/branches:/openSUSE:/Tools/CentOS_6/home:martin-juhl:branches:openSUSE:Tools.repo

yum install obs-web-httpd obs-server obs-worker obs-api mysql-server

chkconfig obsworker on
chkconfig mysqld on
service mysqld start

/etc/sysconfig/obs-server

OBS_API_AUTOSETUP=”no”
OBS_API_AUTOSETUP=”yes”

OBS_VM_TYPE=”auto”
OBS_VM_TYPE=”none”

/etc/init.d/obsapisetup start

mv /etc/httpd/conf.d/ssl.conf /etc/httpd/conf.d/ssl.conf.bak

chkconfig httpd on

reboot

Now go the servers IP-adresse/Hostname for the web-interface…

Login: Admin

Pass: opensuse

Hi all

Time for YASP (Yet Another Sparetime Project)…

I have now for some time been using OBS (OpenSuSE Build Services) in my local home environment, as well as at several customers…

If you are using a packaged based distribution (RHEL/CentOS/SLES/OpenSuSE/Ubuntu/Debian and more) and in some way are creating your own packages, I will really suggest you to take a look into this project..

It’s basically a build server with a web interface. Packages are built in small environment and all dependencies are handled by the server (of caused speficied by the user)..

SuSE has been behind this project for some time now, and it’s generally working pretty good.. Either you can use SuSE’s own server to build your packages or get your own local installation..

This local installation is limited to a SuSE machine at the moment, and this is where I see a small problem..

In my work as a Consultant I see a lot of customers using Red Hat or CentOS, and some of these guys will not easily allow installation of a SuSE based distribution.

Therefore I have taken up the challenge to port the OBS server to CentOS/RHEL.

For now I have gotten the packages built (which wasn’t always easy), and have started modifying the startup scripts. In time I plan to start modifying the theme as well, and maybe come up with a name for this fork (Maybe CBS, CentOS Build Services)..

If anyone has an interest of following the progress, and maybe trying out the result, then to repository is available here and the source code here.

Jeg har brugt det meste af for/efteråret på at prøve at give at alternativ til dommerplanlæggerne i de danske klubber.. I starten var det et meget primitivt project, men nu er produktet i en tilstand hvor alle burde kunne få glæde af det.

Så hvis jeres/din klub gerne vil løse dommerplanlægningen lidt nemmere, så kig forbi www.dommerplan.dk.

Software er gratis og opensource, men vi har valgt at give mulighed for tilkøb af support..

God fornøjelse og spred budskabet..

Just wanted to write a few words..

First of all, thanks for all the support and the great feedback I’ve had over the last 7-8 months.. It has really been a ride..

Over the last few month my job situation has changed, I’m a Consultant and right now I’m at a place where I don’t have as much spare time as I used to have.. mainly caused by longer transport times..

So for the next 3-4 months there probably will be very limited support and probably no updates to ironhide…

I will be back though, and hopefully even stronger than before..

In the meantime, please help each other out (as you are doing) or check out TBP (The Bumblebee Project).. The guys over there are doing some great work, so go check it out..

Also just to clarify.. I haven’t got anything to do with the Bumblebee project anymore (expect for providing the original solution)… But we might merge again in the future… only time will tell..

Again.. Thanks for your support, and you’ll hear from me again in May….

/Martin

Yesterday I moved from Natty to Oneiric. I know that some users are already running Ironhide on Oneiric, but was still a little excited to how easy/hard the process would be.

It turned out to be an pretty easy job.. but still not without problems.. those problem where not caused by ironhide though, but by a change to udev, or rather to the folder structure of /var/run..

The /var/run directory has been moved to /run and /var/lock to /run/lock.. Either the Ubuntu people forgot this in their update scripts, or something didn’t go as planned.

When rebooting after the upgrade, I was stuck at the Ubuntu splash-screen. It took me a while to figure out what was wrong.. but here’s a quick howto.. I guess you could do this before rebooting.. but else reboot in recovery mode afterwards (holding Shift to get into the Grub boot menu) and select remount the root partition. After that, drop to a command prompt.

mkdir -p /run/lock
mv /var/run/* /run/
mv /var/lock/* /run/lock/
rm -rf “/var/run”
rm -rf “/var/lock”
ln -s /run /var/run
ln -s /run/lock /var/lock

reboot

After that I had to re-add the ironhide ppa:

apt-add-repository ppa:mj-casalogic/ironhide

and rerun ironhide-configuration, to get graphics running…

Everything else seems to work fine…

News..
I have released the first version of Ironhide, which is going to be my branch of bumblebee..

This version features:

* Graphical User Interface for Configuration and Submitsystem.
* Tests build into the Configuration, should help us narrow down problems.
* Major cleanup, removed all content not related to Ubuntu.
* Updated VirtualGL.

For now there is only natty packages available. This is soon to change…

The Ironhide packages conflict with bumblebee, so you should be asked to remove the old packages when installing Ironhide.. If your having problems getting ironhide to work, please reboot after uninstalling bumblebee… and then rerun ironhide-configuration..

https://launchpad.net/~mj-casalogic/+archive/ironhide/

Installation notes:

I have given up on supporting the nvidia packages myself.. The version in Natty works just fine, and if you want newer versions, I can confirm that the X-org edgers repository works great with Ironhide:

https://launchpad.net/~xorg-edgers/+archive/ppa

When new versions come out, just rerun the configuration.

Report problems/issues here:

https://github.com/MrMEEE/ironhide/issues

The “New” Bumblebee Project is available here:

https://github.com/Bumblebee-Project/Bumblebee

I know that I haven’t been very active lately, partly due to vacation…

I’ve also been doing a lot of thinking about the way that bumblebee has been implemented.. The popularity really surprised me, and looking back a LOT of things where done too quickly and implemented wrong.. All in all it seems like every bugs-fix, triggered two new bugs…

I also allowed a lot of people to contribute to the project which, with all respect to their work, at times made me feel like I lost control a little over which way bumblebee was “flying”… I think this also was a reason why I lost some inspiration…

What is happening right now is that:

A lot of the people who has been contributing to the bumblebee-project, is now starting over from scratch in one combined project: https://github.com/Bumblebee-Project

Right now, I have chosen not to contribute to the Bumblebee-project, and try some stuff out on my own… nothing has really been published : https://github.com/MrMEEE/ironhide, this will include a graphical bumblebee setup and probably extentions to bumblebee-ui.. This project will probably be renamed to distinguish the two.. but just to be clear, I much appreciate the work the other guys are doing and there is no bad air between us.. I just need some “creative” time off…

So, right now, yes… things are broken, both in the ppa and in the git versions.. I hope that the above efforts will solve this as soon as possible, and a BIG thanks to every tester, contributor, programmer and user of bumblebee out there..