Posts by kp

kp · Devel: CrunchBang 11 "Waldorf"

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)?

kp · Devel: CrunchBang 11 "Waldorf"

HI all,

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.

Thanks.

kp · CrunchBang Talk

@typewriterjason

What netbook did you go with? I finally chose the Asus 1001PXD, but I was yearning for the SSD instead of the spinning hard drive it came with...

I ended up with a teo pro from Zareason http://zareason.com/shop/Teo-Pro-Netbook.html.

They are a Linux OEM. Great customer service, and each box comes with a screwdriver, so they encourage you to make modifications, in the spirit of open-source hacking I would say.

kp · CrunchBang Talk

Thanks for all of your replies.

I ended up finding a cheap netbook for the time being:

1.6 ghz atom processor
2 GB RAM
40 GB SSD
11-inch screen with 1366x768 resolution

The school has Linux server in the style of a mainframe, and I'm assuming I can SSH into there for any major lifting. Eventually, I'll get a more beefy machine, but this is a suitable solution.

Crunchbang is still running strong on this netbook, no problems at all, and speedy as can be.

Thanks again!

kp · CrunchBang Talk

Hi,

I will be returning to school for Computer Science program in the spring. I'm looking to get a low-powered desktop to use strictly for class projects, maybe filestorage for remote access and potentially running a light duty LAMP service for script testing [(running on #! of course). I'm told most school work will involve C++, Assembly, shell scripting and LISP, as well as SSHing into their *nix server.

I'm looking at a cheap system right now that has the following specs:

(1)

Sempron LE 1250 processor (2.2 ghz)
1 GB DDR-3 (up to 8 GB) RAM
500 GB 5400 harddrive
ATI Radeon HD 4250

Even with the excellent resource use of #!, am I naive to expect decent performance from such a modest machine? My knowledge of hardware is minimal, but I like the idea of running a system with lean resources, if for no other reason that to keep away from the distraction of running many applications.

I'm also tracking another small box that's more expensive:

(2)
Intel Atom D525 Dual Core (1.8 ghz)
2 GB DDR-3 (up to 4 GB) RAM
320 GB 5400 harddrive
Nvidia ION GPU

Any guidance would be much appreciated.

Thanks!

kp

kp · Introductions

Hi all,

During my first year with Linux, I've been distro-hopping. The combination of the Debian base, defaults and design that makes sense to me, and the friendly community have swayed me to stay with #! for the foreseeable and a big chunk of the unforeseeable future.

I'm still working to become technically proficient with Linux, so having a culture of patience and assistance is great! I'm humbled to be a part of a gracious and knowledgeable community.

Thanks for all of the helpful information!

kp

CrunchBang Linux

SEARCH

#1 Re: Devel: CrunchBang 11 "Waldorf" » Keyboard not recognized while installing Waldorf » 2012-11-05 21:51:58

#2 Devel: CrunchBang 11 "Waldorf" » Keyboard not recognized while installing Waldorf » 2012-10-25 00:29:32

#3 Re: CrunchBang Talk » Low-powered system for College/Uni » 2011-10-15 18:22:55

#4 Re: CrunchBang Talk » Low-powered system for College/Uni » 2011-10-12 17:18:17

#5 CrunchBang Talk » Low-powered system for College/Uni » 2011-09-23 21:12:11

#6 Introductions » Hello » 2011-09-23 19:47:07

Board footer