Some news.

Hello everyone,

I bet you are thinking we vanished into oblivion!

Nope!! Our team actually increased secretly and has been working a lot these days to make 3.0 final release come true.

Until that happens 1.8 beta will be available in the next days or so.

Also our chat has been fixed so it’s now easier to visit us.

We also are in need of a person that is confortable to maintain launchpad and help the project manager (yes we created a project manager to keep things tidy from now on hehe)

We want to see our support channel full again so please drop by and have a chat with us.

We will be there to give you support as usual, or check the forum and open a topic with your questions and you will surely be answered asap.

Also if you see you would be helpful to this project do send me an email.

This said i’ll be waiting to hear from you all!

How-to 3G using Huawei USB dongle

How to get 3G working on Kuki using a Huawei Model E169 with the Danish provider 3 (and probably others)

This guide is a bit more hardcore as it requires you to use an editor and configure system files the old fasion way.

First thing to check is that the device is supported by your kernel: Before you plug in the dongle Open a terminal and type

ls /dev/tty*

There should be at long list of tty’s. Now plug in your dongle, wait a few seconds and repeat above command.
Some more ttyUSB devices should now have been added to the list.

Now lets start talking to the dongle. 3G support using the Huawei is working like a old fashioned modem, using commands like ATi to get the modem manufacture and so on. (A list of AT commands for Huawei can be found at here.)

We will be using the pppd program for 3G connection. pppd in turn uses program called chat to deal with the AT commands of the modem.

First we configure chat: Open an editor
sudo mousepad /etc/chatscripts/[providername]
and enter the below code

#
# abortstring
ECHO OFF
ABORT BUSY
ABORT 'NO CARRIER'
ABORT 'NO DIALTONE'
ABORT 'NO DIAL TONE'
ABORT 'NO ANSWER'
ABORT DELAYED
TIMEOUT 3
# modeminit
'' \dATZ
TIMEOUT 4
OK AT+CPIN?
READY-AT+CPIN=9999-OK \d\d\dATDT*99#
TIMEOUT 60
CONNECT ''

Remember to replace 9999 above with your PIN code
Save and close.

At first chat will ask the dongle if it is READY. If not it usually because it have not been unlocked and a AT+CPIN=9999 is inserted. After READY – or in the second case OK is received, we have to wait a while for the receiver to find the network. Currently this is done by \d\d before the dial command but I think this could be improved by asking the dongle for its state. Possibilities in chat is wery limited and as it is now I do not always get connection in first attempt.

Chat is called from pppd which is configured in /etc/ppp/peers. Open the editor again
sudo mousepad /etc/ppp/peers/[providername]
Fill in the following:

hide-password
noauth
connect "/usr/sbin/chat -v -f /etc/chatscripts/[providername]"
debug
/dev/ttyUSB0
460800
defaultroute
replacedefaultroute
noipdefault
user "notNeeded"
usepeerdns

For the initial test just type pon [providername] in your terminal to connect. Wait a little while and test that you are connected to the internet. poff to close the connection.

If it does not work, open the first file and change ECHO to ON. Save it, open a new terminal and type

tail -f /var/log/ppp-connect-errors


and try to establish the connection again while you observe the ppp-connect-errors terminal. In tail display you can follow the chat/dongle conversation and may spot the problem. The chat should end with a CONNECT statement from the modem and then the communication channel is handed over to pppd

When you got pon working it is time to add a nice gui. I installed ppp-tray wich work wery well and fit perfectly in Kuki’s small formfactor desktop. Please refer to Ubuntu forums for help on ppp-tray

Tip: With the above setup you can have configurations for several dongles in ppp-peers and select the one you want from ppp-tray.

If you have any doubt or question just ask on Kuki Forum (we have a dedicated topic for this how-to here) or come to our #kukilinux channel on Freenode IRC.

This How-to as been made by Klaus, thank you for your contribution!

Kuki: ”Because leak coudn’t find anything on telly”

BOLO DE BOLACHA (portuguese cookie cake)

Ingredients

2 packs of Maria Biscuits (Maria is a portuguese cookie brand, they are simple cookies, the most simple you can buy )
2 cups of butter softened
2 cups of powdered sugar
1 egg
strong coffee

How-to

Mix butter and sugar until creamy, add the egg and beat until well incorporated. Set aside.

Start dipping the cookies one at a time in the coffee, don’t let them sit in there long, just a quick dip, then place on the serving plate in the shape of a flower.

Do one layer of cookies, then spread a thin layer of the butter cream mixture.

Repeat layers as high as you want to go. I used one and half packs of the Maria cookies.

Cover the whole cake with the remaining butter cream mixture.

Take some of the remaining cookies and crumble them on top.

It’s best when it’s cold so make sure to keep it refrigerated…..ENJOY!

——————————————————————– // ——————————————————————–

Thanks sis!
NEXT PROJECT: KUKI TIRAMISSU( something like this )

Kernel Installation

Hey guys!

It seems that some kuki users are having questions about kernel installation.

If during installation, a question regarding the copy of the file menu.lst is asked, you have to say YES!

menu.lst needs to be upgraded so you can boot with the new kernel, you have to accept the upgrade/change or the new kernel will be installed, but you will not be able to boot into it (unless you want to manually edit the menu.lst)

To install Kuki, our kernel or kernel headers please follow our guides at: http://www.kuki.me/how-to/

If you still have questions after reading and trying our guides please come to our #kukilinux channel on Freenode IRC (please be patient we sleep and work too) or use our support forum www.kuki.me/forum

New Kernel Released: 2.6.31-rc3-kuki-20090722!!

We are proud to announce the release of our latest kernel 2.6.31-rc3-kuki-20090722 (go to our download page to get it! This kernel is based on Release Candidate 3 of the 2.6.31 series of kernels. A lot has changed between the 2.6.31 series and the kernel that installed with Kuki 3.0 Pre Release 1.7. A lot has even changed since our last kernel based on 2.6.30!

The biggest change that impacts Kuki and the Acer Aspire One is that the Intel Video driver is once again working! Using the default xorg.conf, glxgears once again reports around 825 fps (yes, we know that glxgears is not a true benchmark, but the last kernel was only around 150fps).

To read all of the changes in the 2.6.31-rc3 kernel, check out the change log at www.kernel.org.

Besides working video, the left card slot is working with or without a card at boot. Unfortunately, the right card slot is still quite finicky. You may want to try adding “pciehp.pciehp_force=1″ to the defoptions in /boot/grub/menu.lst. (pciehp is compiled into the kernel instead of loading as a module)

The ath5k driver seems to be working very well now, too. And, the problem with the /dev/snd permissions with the last kernel are fixed, so there is no need for the patch in the forums. Also, the webcam is working again! And as before, acerhdf is compiled in.

Finally, to make things a little easier, this kuki kernel also has working bluetooth, ipv4 and ipv6, and the following file systems: ext2, ext3, ext4, reiserfs, jbd.

Before installing this kernel, you may want to uninstall the splash screen (sudo apt-get remove splashy). The kernel will still boot, but, it doesn’t like the vga-0×314 line in the /boot/grub/menu.lst. The kernel will boot, but you will have a blank screen if you don’t remove that line and if you do, splashy won’t work anyway.

Actually, to be on the safe side, you should edit the menu.lst (sudo mousepad /boot/grub/menu.lst), and on the line that begins # defoptions change it so that it looks like this “# defoptions=quiet splash” (without the quotes). If you have already installed the kernel (shame on you for not reading all the directions!), you would want to edit the line with the new kernel and remove the “clocksource=hpet”, “vga=0×314″ and “elevator=deadline”. (The clocksource and elevator are already set to those values and are no longer needed on the line.)

This should be the last kernel update until either a) the next release of kuki or b) the 2.6.31 kernel goes from being a release candidate to an actual production kernel or c) something is still really broke and needs fixing.

We will be opening a new thread in the forum specific to this kernel, so post any problems, or questions, there.

vw72