My thoughts on Slackware, life and everything

Tag: qemu

Steam client update, also fresh Wine, QEMU, MinGW-w64

It was already a while ago that I refreshed my ‘steamclient‘ package for Slackware.

The steamclient package is meant to bootstrap the installation of Valve’s Steam gaming platform on your Slackware computer. The package installs a couple of scripts and a 32-bit Linux runtime based on Ubuntu. When you first start ‘steam’ from the menu or from the X terminal commandline, the client will download a larger set of runtime libraries, including 64-bit support. Onwards, the client will keep its runtime libraries up-to-date automatically, every time it starts up and connects to the Steam servers.
The Slackware package has a couple of tweaks because we obviously do not have Ubuntu tools on board. As a result, on Slackware-current (32bit and 64-bit with multilib) Steam works out of the box.

The reason for a package refresh is a recent bug report on Valve’s github, about an ALSA related crash on Slackware. The root cause was eventually found and it was part of the customization I added to the steam launcher 6 years ago when we were still on release 14.1 and we did not have pulseaudio as part of the Operating System.

So I removed (actually, commented-out) these lines, and that should fix the root cause for that bug. If you do not use Pulseaudio or want to enforce ALSA sound regardless, just un-comment the relevant lines at the top of the ‘/usr/bin/steam’ script again – it’s self-explanatory.
I have also refreshed the READMEs for Slackware and additionally removed support for all Slackware versions older than 14.2. To be realistic, I assume that gamers are all on the -current platform already.

NOTE:
If you have an older ‘steamclient’ package installed on 64bit Slackware and use the slackpkg+ extension to manage 3rd-party repositories, you need to un-install the old steamclient package first. The old packages have a ‘i386’ architecture tag whereas the new one has a ‘i386’ architecture tag for the 32bit Slackware, and a x86_64 tag for use on 64bit Slackware.
They are the same package actually but I was asked to make ‘steamclient’ installable via slackpkg/slackpkg+ also on 64bit Slackware. So:

# removepkg steamclient
# slackpkg update
# slackpkg install steamclient

Have fun playing games on Steam!

Some other recent package updates in my Slackware-current repository are:

Wine: we’re up to version 6.23 now. The 32bit wine package is just that – 32bit Wine. My 64bit wine package contains both 64bit Wine and the 32bit WoW64 (Wine on Wine64). Both have the ‘staging‘ patches applied.
The external dependencies for this package remain the same: FAudio and vkd3d are required. On 64bit Slackware you need to have multilib installed. In addition to multilib, you need to convert the 32bit versions of the FAudio and vkd3d packages to ‘compat32’ packages and install those.

MinGW-w64: I have updated this package to v9.0.0_gcc11.2.0. Mingw-w64 is based on the original mingw.org project (which was created to support the GCC compiler on Windows systems), particularly adding 64-bit support.

The MinGW compiler suite is used to generate the native Windows DLLs in the wine package.

The QEMU machine emulator and virtualizer got a refresh because I am preparing (fingers crossed!) for a release of Slackware 15.0 which according to an online statement could happen soon after New Year 2022.
I run Slackware Virtual Machines (VMs) in QEMU and I wanted to take advantage of the newest QEMU features. At the moment my VM host is Slackware 14.2 and that has a fairly old QEMU package installed. The VM host will get an upgrade to Slackware 15.0 as soon as the new release is made available.
Dependencies for my qemu package are: vde (historically for non-root network bridge support) and as of now also: device-tree-compiler, jack2 (note that jack2 has its own sub-dependencies!) and virglrenderer.


Have fun with these during the holiday break, and I wish you all a Happy New Year.

My new mirror

I have a new mirror server.

I have configured a VPS (a virtually hosted server using QEMU) which was donated to me by a Slackware supporter who wishes to remain anonymous. The physical server is on a gigabit Internet connection, so I guess I can offer a speedy  mirror service!

In fact, the mirrors are already complete. With a re-sync of several times a day, I hope to offer an uptodate service. I am mirroring the following:

  • My own complete package repository and tools – including my “restricted SlackBuilds” area, containing things like lame, libdvdcss etc.
  • My “Ktown” repository of KDE packages – where I made available new packages for KDE 4.5.1 earlier today.
  • The full SlackBuilds.org repository.
  • Slackware-current – both 32-bit and 64-bit architectures will be mirrorred.

Plus, I am using my mirror-slackware-current.sh script to create bootable DVD ISO images of slackware-current (32-bit and 64-bit). These ISO images will be re-generated every time there is an update to the -current ChangeLog.txt.
These ISO images do not contain source code. This allows me to keep the ISO file size below 2 GB which will make it a worthwhile download for you.

And most important – mirror access:

Hammer it good!

Cheers, Eric

Wondering how to spend my computer cycles

I am beginning to feel the lack of computing power in my attic…

There is a pending KDE 4.5.0 release, which needs to be built for slackware-current. Then there is also VLC 1.1.2 which was released a few days ago… and those packages need to be built for Slackware 13.1 (so that they can join my main repository). I have only one “build box” which is fairly old and sporting a CPU without hardware virtualization capabilities.

Decisions, decisions… there’s only 24 hours in a day.

So I decided to start with building a test set of KDE 4.5.0 (the sources of which I already have) because that will be a big event for a lot of people, and leave the new VLC for another time. Don’t worry! Linux users will find that the 1.1.2 release of VLC does not offer anything worthwhile, except perhaps for some bugfixes in the DVB (digital video) module. The VLC 1.1.1 packages which I have created for Slackware are still very much OK.

Having to build packages for Slackware 13.1 as well as -current, and for two architectures (32-bit and 64-bit) is proving a bit too much for that old computer (which happens to be my home desktop as well), so I decided to use the donation money that has been accumulating and order an Athlon II X4 640 boxed CPU, along with an Asus M4N68T motherboard and 8 GB of RAM, completed with a 2 TB SATA hard drive. Once all that arrives on my doorstep, I will assemble a full computer using the case I have here (with a motherboard that caught fire last month because of a crappy condensator). That machine will become my new server.

Thanks to all of you who took the trouble to click my PayPal button – you know who you are, even if I did not thank you in person. Your gracious gifts will be spent with the purpose of making Slackware an even better experience.

By the way – I intend to use qemu-kvm to run a load of virtual machines on that computer, so that it will be easier to build in parallel. I have been considering VMware, VirtualBox and Xen as well. I decided against VMware for being closed-source. VirtualBox could still find its way onto the computer at some later stage; I decided against it because of the mixed license model where you get additional functionality only in the closed-source version. And Xen, well I am quite interested in how that works and performs, but unfortunately it requires a patched “xenified” kernel for the host and Linux guest. That was one bridge too far for me.

Nevertheless, there was a recent post from Chris Abela on the slackbuilds.org mailing list about the “The Xenification of Slack” which will most certainly help Slackware users get jumpstarted into the Xen world. Worth checking out, there is a tarball attached to that post with scripts and configuration files. Well done.

Enough of this, time for a beer.

Cheers, Eric

© 2024 Alien Pastures

Theme by Anders NorenUp ↑