Wary/Racy 5.2.2 Release-Candidate

I have uploaded both Wary and Racy, with same version numbers,, which I consider to be 5.2.2 RC.

They are pretty good. I was tempted to bump them immediately to release versions. But, decided it would be wise to release an RC first. Anyone who wants to give these guys a run, please do.

Of course, if it turns out that these are pretty perfect as-is, then you can consider that you have got the release, then no need to download the actual 5.2.2 when I release that!

Anyway, here they are:

Wary: http://distro.ibiblio.org/quirky/test/wary-

Racy: http://distro.ibiblio.org/quirky/test/racy-

Wary is built with uniprocessor kernel. Racy is built with 3.0.7 SMP (multiprocessor) PAE kernel. Also, the former uses Aufs, the latter Unionfs.

Posted on 11 Nov 2011, 6:18


Posted on 11 Nov 2011, 6:54 by scsijon
error403 on wary
just trying to download wary
initially got a flash illegal operation, then it went through,
downloader gave a error403 on each, but trying a second time it went to downloading

Posted on 11 Nov 2011, 6:58 by scsijon
your most likely still uploading, forgot your not on daylight saving.

error403 -forbidden trying to get md5sums

Posted on 11 Nov 2011, 7:20 by BarryK
Racy forum feedback
Forum feedback for Racy:


Posted on 11 Nov 2011, 7:38 by BarryK
Wary forum feedback
Forum feedback for Wary:


Posted on 11 Nov 2011, 7:39 by BarryK
Re uploading
Everything was uploaded before I made this blog announcement.

Posted on 11 Nov 2011, 8:32 by BarryK
b43 firmware
peebee posted about possible missing firmware for b43.ko. I didn't notice that last line before:

# modinfo b43
filename: /lib/modules/3.0.7/kernel/drivers/net/wireless/b43/b43.ko
firmware: b43/ucode9.fw
firmware: b43/ucode5.fw
firmware: b43/ucode16_mimo.fw
firmware: b43/ucode15.fw
firmware: b43/ucode14.fw
firmware: b43/ucode13.fw
firmware: b43/ucode11.fw
firmware: FW13

...I don't know what "FW13" means. Perhaps it means put in all of the firmware that has "13" in it's name. Okay, I will do that.

Posted on 11 Nov 2011, 8:37 by scsijon
well, everything seems to be ok now,

I don't know why the earlier problems

maybe had something to do with rememberance day and bandwidth somewhere

Posted on 11 Nov 2011, 8:40 by BarryK
Re b43 firmware
Just checked, all of the *13.fw firmware files are already in Woof. Well, have I updated them from those in the Ubuntu firmware .deb, as they are later files and different sizes.

Posted on 11 Nov 2011, 16:15 by Terryphi
1024x768 no progress
Despite the changes you have made Wary still does not set resolution 1024x768 correctly at first run using Probe or choosing Intel. It always wants to default to 1280x1024. In order to get 1024x768 to set and survive reboot I have to manually edit xorg.conf.

To sum up: behaviour has not changed from that previously reported. :sigh:

Posted on 11 Nov 2011, 17:04 by Sage
"decided it would be wise to release an RC first"
Good thinking, Carruthers!
Reports on Forum, both are terminally faulty.

T-phi: I cracked this one on my kit. Set the monitor's native res., eg 1440x900 (or some other mythical higher value), then select 1024x768 from second menu. Works for me every time (but it shouldn't be necessary!).

Posted on 12 Nov 2011, 7:52 by BarryK
Quick Setup fix is basically working well, except for one major problem that has come up: very high CPU usage in the drop-down lists in the /usr/sbin/quicksetup script. I have now fixed this:


I will put the same fix into timezone-set.

Posted on 12 Nov 2011, 8:00 by BarryK
Ahem, no, timezone-set is now only a symlink to quicksetup, so already fixed.

Posted on 12 Nov 2011, 15:40 by Sage
Quick Setup fix
Muchos gracias.

Please can you fix the broken link issue in Flashplayer from the pop-up, and preferably, only activate the pop-up at first browser selection?
Better still, not install any default browser, but pop-up a list of options like playdaz (or is it mick0 or kirk??) which includes all available browsers/browser suites accompanied by Flashplayer. Kills two stones with one bird - substantially decreases the size of the .iso.

Posted on 13 Nov 2011, 23:29 by Risto3
virtual box problems
Hi, trying out this release of wary under VirtualBox.. found the following devx_wary_5.2.1.90.sfs
in order to get over the build problems...
But the guest additions install (invoked simply from /mnt/sr0/autorun.sh) fails with message indicating no X.Org...
Also, Xvesa only works out of the box as XOrg Vesa does't start up and somehow need to get all of guest additions loaded in order to have a working X.org module. Any hints?

Posted on 13 Nov 2011, 23:38 by BarryK
Re virtual box problems
I can't help, have never used Virtual Box. There are guys who you can find on the Forum who know about Virtual Box.

Have you tried with Racy?

Posted on 13 Nov 2011, 23:41 by BarryK
timezone-set fixed
Wary has a bug, the CLI (text-mode) timezone setter was broken. This is supposed to run at first boot, before X starts, but didn't.

Consequently, X was starting up and showing the wrong time and date.


Posted on 14 Nov 2011, 2:09 by Risto3
Re virtual box problems
I'd like to keep with wary since we're evaluating this distro for our Vortex86mx thin clients (ebox).
I wanted to get a version running well under virtualbox so we could get tigervnc built.... unfortunately can't seem to advance there yet.
Perhaps the real question is how to get TigerVNC's vncviewer running.


Posted on 15 Nov 2011, 2:04 by risto3
Re virtual box problems
well I tried your suggestion with racy, and I got a lot further... after copying the dev and 3.0.7 patched kernel .sfs files, I needed to add the shadow package and the install goes without error and after the reboot I seem to have a working video driver and the shared file directory is okay.
only thing is a serious problem with the mouse and the keyboard (fr, fr_FR@euro and Europe/Paris locale settings) did nothing, have qwerty.
The gtk dropdown box problem is rather difficult to overcome as well (perhaps related somewhere)...

Posted on 15 Nov 2011, 14:16 by Risto3
Re virtual box problems
shit, the racy bits seem to be compiled with ppro cmov, not stable on the Vortex86mx. So much for that one.

Posted on 16 Jan 2012, 2:13 by peebee
B43 problem fixed in K3.1.8
Hi Barry

wuxiandianzi has uploaded a version of lupu using the k3.1.8 kernel - and it seems to have cured the B43 problem on that build anyway.