Recently, I finished building a low powered box, just perfect for #! It's amazing how the distro flies with an SSD. The processor requires no fan, so it's functionally silent.
I installed the most recent Stable BPO 64-bit version, and it's running great, with a solid week of uptime straight.
Before installing this version, I tried installing the most recent Waldorf 64-bit image (20121015), but, during the install process, I wasn't able to input via keyboard. It's a year old Logitech USB wireless keyboard, which has done the job with Slackware and Fedora (via Viperr2) on the same machine. I tired burning the image again, but still the same result.
I could certainly edit the apt sources to Waldorf/Wheezy, but I've read here that the results can be less than desirable, with most folks recommending a clean install (I would rather do a clean install anyway).
As you can probably tell, I did a bit of wandering distro wise, but I'm back with the speed and stability of #!, and will probably stay for quite some time. Absolutely a treat to run, and the forum is the best I've ever experienced; supportive, helpful, and fun!
Any help getting Waldorf running would be greatly appreciated.
Maybe this answer is a bit late, but you wont get a wireless usb running during the install- only after once you have bluetooth on
Thanks for the response.
I ended up getting my !# satisfaction in a roundabout way.
First, I tried the vanilla Debian Wheezy image (beta 3), but I ran into the exact same issue as with the Waldorf image (keyboard input not available during installation).
I knew that the Squeeze-based version of #! (Statler) would recognize my wireless keyboard during the install process, so I downloaded and installed a minimal version of Squeeze (netinstall), then upgraded /etc/apt/source.list to upgrade to Wheezy.
From there, I installed openbox, xorg, tint2, conky, and other goodies crunchbang provides, and am currently getting my kicks this way. Wheezy is running smoothly, no issues to speak of in the past week.
Still, I'm left wondering why the keyboard wasn't usable when using the installer Wheezy/Waldorf directly, while it works while in the Squeeze/Statler installer.
Maybe passing usbhid as a boot parameter would have worked (or is it changed to hid_generic with kernel 3.2)?