I just picked up an awesome little Hi-Grade micro-Media PC for £150 - it's 5-6 years old and runs ubuntu karmic fine, so I'm expecting great things when I try Statler out for the first time on it big_smile.

I'm starting to look into new netbooks too - currently using a 901 which has always worked fine with any linux distro I put on it, but as it approaches 2 years old I've started thinking about upgrading to something with a bigger keyboard and better specs. So far, I reckon the asus eee 1201n looks like the ideal setup (although I'd like a slightly smaller screen), but I've read the battery life is a bit disappointing at around 3-4 hours. I've heard good things about the upcoming 1201pn too, so that might be worth researching a bit more. If you arent prepared to wait for a new model, I'd actually suggest getting either a 901 or some variant of the 1000, looking for good battery life and a low price, so you can upgrade again that bit sooner big_smile

My i7 has 4 cores plus 4 "virtual" cores due to hyperthreading, but i just use "cpu" rather than "cpu0, cpu1" etc in conky, as I found that it doesn't really give you any meaningful information. For example, if 1 core is running at 100% load and the other 7 at 0%, my overall usage is shown as 15% rather than 12.5% (100/8). I think this is probably due to the fact that the virtual part of a hyperthreaded core can only use spare clock cycles rather than just taking any it likes, plus the load balancing shifts the cpu usage between the cores over time anyway. It may also be due to the cores over/underclocking themselves automatically to deal with load - the i7 definitely does this and I believe Atom processors do too.

zen: I'm using 3.0.17, but i seem to remember using 3.5 briefly when trying a mint 8 liveCD (also 64-bit) although I haven't used that nearly as much. "If it aint broke" and all that. smile Also, I have no idea what ubuntuzilla is - I used the FF that came with #! and have just applied updates when prompted.

I've been running the 64 bit version since it was released and have had no problems whatsoever. Firefox works fine for me and I haven't had to do any unusual setting up just for day-to-day use, including some testing of other distro's in virtualbox. Unfortunately I can't comment on performance as I haven't used a 32-bit OS on this machine for longer than an hour or so.

6

(49 replies, posted in CrunchBang Talk)

I'm another eee user - my 901 went through xandros easy->xandros advanced->ubuntu-eee->#! as well.
I don't use it nearly as much now I have my desktop but it's still running fine with 8.10. Planning on upgrading to 9.10 when it becomes available.
I doubt I'll be upgrading to another netbook for at least another year but when ION and a better processor are available I'll start looking again smile

Recently, I bought a Belkin G+ wireless card (this one) for my new desktop. I'm having some problems getting it working under #! - hoping someone might have a suggestion.

The network is detected and the security all set up, and the connection can be established fine...but after 5-10 minutes the speed (as listed by right-clicking the NW manager icon -> Connection Information) falls from around 48Mbps to 1Mbps. For comparison, the eee I'm using to type this constantly sitting at 54Mbps. While the N wireless this thing is substantially better than the G+ card, the speed really should not be falling that low. In addition, the G+ card repeatedly reconnects and the internet, while definitely accessible, is far from useable.

During the set-up I had to download broadcom drivers (broadcom B43 wireless drivers). These allowed the card to be detected in the first place, but I haven't been able to find anything to solve the speed problem.

In case it helps, the problem occured both on my original install, and also after a fresh install from the livecd.

Thanks in advance for your help.

I've no experience of programming properly myself, but I've been looking into it a lot recently and everywhere I look I read that starting with C isn't a good idea - most places recommend learning Python first then moving to C and the other main languages. Is there a particular purpose you want to learn programming for, or just for general knowledge? Other people may be able to help more if they know this.

In the meantime if you want to look into Python, I've found the following pages pretty helpful:
http://www.python.org/doc/2.5.2/tut/tut.html
http://wiki.python.org/moin/BeginnersGuide/Download

9

(42 replies, posted in Off Topic / General Chat)

Just based on the youtube video and an article in Linux Format about this, I can't say I'm particularly keen. Reminds me far too much of the god-awful Xandros which came with my eee. Might give it a go when a stable version shows up as long as its bootable from a pen drive, but otherwise I'll be sticking with #eee for the foreseeable future big_smile

So over the last few days I've begun to contemplate setting about compiling a new kernel for my eee901, which currently runs #eee 8.10.02. It would partially just be an exercise in geeky fun, but at the same time I would really like to get my boot time down from the current 50ish seconds to around 30, or less if possible. However, with Ubuntu 9.04 just released, is it really worth it? I've heard boot times in Jaunty are much lower anyway, in which case I'd probably leave the kernel changes for another time when I'm less busy. Anyone have any thoughts on this?

Now onto a couple of questions...

- First, how is the hotkey compatability looking for the 901 under Jaunty? Since a recent update I no longer have a working lvds-toggle button, but other than that everything seems to be working ok with a little help from Elmurato's scripts. Will it be possible to do away with secondary programs like this and eee-control in the newest Ubuntu, or is full ACPI support still a bit hindered?

- Also, when a #! version of 9.04 is released, will we be seeing a 64-bit version at the same time, or will that take quite a bit of further development? I'm due to recieve my new desktop this week and would like #! to be my main distro, but if a full 64-bit version isn't available I'll probably use it as an excuse to try out SUSE and a few other distro's too, with a regular #! too of course smile

There was something else, but it's slipped my mind for the moment. Ah well, may come back to that later.

Cheers
KFC

11

(473 replies, posted in CrunchBang Talk)

Plans have changed since my last post (prev page) smile

Most of the components for the desktop have stayed the same, but its upgraded to an i7-920 with a Gigabyte X58 motherboard and 6GB of RAM. Order has been placed, now I just have to wait for the bits to get here big_smile

Planning on trying a quad boot setup with XP (for games and office), #! (for most use), openSUSE (for more 64-bit usage and experimentation) and another linux distro, probably Mint (for testing apps). The 3rd and 4th may be dropped if 64-bit #! works well on the machine.

Regardless of any symbolism issues, I don't think this new logo is as suitable as the original. Just isn't as instantly recognizable which is important in a small text-less icon IMO.  Vote: Old logo

13

(473 replies, posted in CrunchBang Talk)

Currently just using #! on my eee 901, but I'm intending on buying a desktop with the following specs sometime in the next month, which will almost certainly have a CB partition:

Name:  Custom built
Processor:  Intel Core 2 Quad Q6600 (2.4GHz, 1066Mz) Socket 775 L2 8MB Cache (2x4MB)
Screen:  26" Belinea LCD, 1900x1200
RAM:  8GB DDR2 (probably Crucial)
HDD:  500GB Western Digital SATA II 7200RPM 16MB Cach
Optical Drive:  Pioneer 20x DVD±RW Dual Layer SATA
Graphics:  ASUS 9600GT 1GB DDR3 Dual DVI HDTV out PCI-E Graphics Card
Sound:  In built
Network:  In built ethernet, Belkin Wireless N PCI card (possibly just G depending on price)
Other:  750W PSU, possibly a fan controller/card reader panel for the front

Comments: Looking to get most of these bits from Ebuyer, except the screen which I already have. If anyone has any suggestions on better alternatives feel free to let me know.

Seems to have worked so far smile With the /etc/acpi/events/powerbtn file you provided and some changes to the /etc/acpi/powerbtn.sh file, I've now got 100% success with the power button. Here's my powerbtn.sh file in case anyone is having a similar problem:

#!/bin/sh
# /etc/acpi/powerbtn.sh
# Initiates a shutdown when the power putton has been
# pressed.

# Skip if we just in the middle of resuming.
test -f /var/lock/acpisleep && exit 0

# If gnome-power-manager, kpowersave or klaptopdaemon are running, let
# them handle policy This is effectively the same as 'acpi-support's
# '/usr/share/acpi-support/policy-funcs' file.

#if pidof gnome-power-manager kpowersave > /dev/null ||
#  (pidof dcopserver > /dev/null && test -x /usr/bin/dcop && /usr/bin/dcop kded kded loadedModules | grep -q klaptopdaemon) ; then
#    exit
#fi

# Otherwise, if KDE is found, try to ask it to logout.
# If KDE is not found, just shutdown now.
#if ps -Af | grep -q '[k]desktop' && pidof dcopserver > /dev/null && test -x /usr/bin/dcop ; then
#    KDESES=`pidof dcopserver | wc -w`
#    if [ $KDESES -eq 1 ] ; then
#        # single KDE session -> ask user
#        /usr/bin/dcop --all-sessions --all-users ksmserver ksmserver logout 1 2 0
#        exit 0
#    else
#        # more than one KDE session - just send shutdown signal to all of them
#        /usr/bin/dcop --all-sessions --all-users ksmserver ksmserver logout 0 2 0 && exit 0
#    fi
#fi

# If all else failed, just initiate a plain shutdown.
/sbin/shutdown -h now "Power button pressed"

It is likely that this will disable the ability to set what the Power Button does (using gnome-power-manager), leaving you with just an on/off function. This shouldn't be a problem though, as the button seems to work fine when the power-manager is telling the netbook to hibernate/suspend - only power off was causing trouble. To re-enable the gnome-power-manager settings for the button, return the file to it's original setup (in w1zard's post above).

Thanks for your help with this. That was the last niggling problem left with the eee for me, so now everything is just right. smile

Pretty cool smile
Weird to see how far removed different distro's are from each other. The ones I've heard about most (Ubuntu, #!, Mint) must be doing something right, but I'm surprised DSL and Puppy are so far removed from each other.

Thanks, my powerbtn.sh seems to be the same as yours. When I first encountered this problem I thought that by commenting out all the sections of that file except the last line, I could avoid the interference by gnome-power-manager, but I'm not sure. It didn't work the first time, but I'll try again with the etc/acpi/events/powerbtn file in place to see if that makes any difference.

Thanks!

Adding that has improved the situation for me, from having a power button that works 20% of the time, to about 80% so far. Any ideas what could be preventing full functionality? I've so far assumed its to do with the contents of etc/acpi/powerbtn.sh, but regardless of what changes I make it doesn't improve. Suggestions are appreciated smile

Hey, I've been having the same issues, tried editing powerbtn but no luck. Any chaance you could post the contents of your working powerbtn file here for me to try out?

Thanks
KFC

19

(197 replies, posted in Off Topic / General Chat)

Never tried linux before getting the EEE, but since then it's been Xandros -> eeebuntu - > EasyPeasy -> CrunchEee, which seems to be a common sort of progression. I think a lot of people see Xandros and think "Yeah, it's a bit lame but I can live with that cos it's simple." A week later, they're out hunting for a new distro tongue

When I get my desktop I'm hoping to get 64bit Ubuntu and Crunchbang dual booting, and possibly windows if I don't find WINE and the other Windows VM's to my liking.

My first was a windows 95, pentium II 166Mhz with about 16mb RAM and a 2.1GB hard drive big_smile
That was about 12 years ago or something, but my grandparents have had an even older pc in the meantime running windows 3.1 and the huge bendy floppy disks.

Amazing to think that this eee-pc probably cost about a quarter of what that thing did, but has 10 times the power, and the pc I'll be buying this month will have the equivalent of 80x the processing power 250x the hard drive capacity and half the price tongue

Thanks guys, I managed to sort this out using a technique similar to anon's , going into ~/.mozilla and deleting some files (tried deleting the whole folder but got some error to do with NTFS handle - then went to the files that could be deleted and got rid of them) My was was probably unnecessarily destructive, clearing saved passwords and such, but if this happens again I'll just try deleting those 3 files.

Thanks again!
p.s. As a matter of interest I was indeed running 3.0.6 smile

Today, my CrunchEee seems to have developed some sort of fault with firefox. Every time I start it up, the following things are incorrect:
- My home page defaults to the ubuntu one set by the ubuntu-addons.
- The StumbleUpon addon behaves as though this is the first time I've loaded it (it isn't - I downloaded it yesterday)
- The Download Statusbar addon does the same (had this for ages)
- A file I downloaded yesterday appears in the Download Statusbar, even though I've cleared it several times.
- Going to Tools -> Addons, none of my installed addons or plugins are displayed, preventing me from updating/removing them...even though I know at least 2 are still present since they're bugging me on every start-up tongue

I've tried re-installing firefox twice, but the problem still occurs. I haven't edited any files to do with firefox recently other than changing the icon location bit, as detailed here.

Other than that, the only changes I've been making to the system are a system upgrade using Super+U this morning, and editing powerbtn.sh in an attempt to get the power button working (thread where  requested help with this here.

Any suggestions anyone can make? The power button was niggling me, but this is a full-on pain in the backside!

Thanks
KFC

Sods law - as soon as I posted, I realized a workaround for problem 2. In case anyone is having a similar issue, here's what I've done:

Navigate to:

/etc/acpi/screenblank.sh

Go into super user mode and copy this file.

Navigate to:

/etc/acpi/eeepc

Make a copy of "eeepc-lvds-toggle.sh" to somewhere safe, just in case. (Again, super-user mode will be necessary)

Paste in the screenblank.sh file and rename it eeepc-lvds-toggle.sh

Go to the emlurato menu and make sure "Launch program with first hotkey" is unticked

That should be it!

Hi all,

After a few days of reading around, I'm left with a couple of issues I haven't been able to find solutions to anywhere - sorry if any of this has been resolved elsewhere, I however haven't been able to find it tongue

Firstly, since replacing eee-control with elmurato's scripts, the power button only works intermittently.
This is a consistent problem which has occurred both times I've tried installing the scripts. Pressing the power button only has an effect about 1 time in 10.

Secondly, the first hotkey (toggle display on/off) causes some sort of error, which crashes the system to the login screen.
Again, a consistent problem. In this case the crashes occur 100% of the time. I was thinking of avoiding this by setting the hotkey in the elmurato settings to run a .sh file for toggling the screen, but don't know where a working one of these would be found (since the elmurato one is presumably what's causing the crash)

There was something else...but that's slipped my mind for now. I'll update the post if it comes back to me though. Thanks in advance for your help!

So for a reason I can't remember now, I decided to try the Elmurato scripts again today. The display-off button doesn't work, and the power button is still broken. The power button DID work earlier, and has since stopped without me knowingly changing anything to do with the scripts hmm

If anyone can advise a solution for these problems it would be greatly appreciated, having tried the scripts again I would prefer to stick with Elmurato's stuff IF the power and display buttons can be fixed - I haven't read anywhere of others having this issue so I am assuming at the moment that it isn't just a bug.

Cheers all!