Archive for the ‘linux’ Category

Got a new Sony MBR-XB500 headphones (with extra bass) last week and it seemed to be well worth it.  Except that I ran into a few problems when I plugged it into my desktop front panel audio jack.  No sound came out both on Ubuntu 10.04 and even on Windows XP.

The rear jack worked fine for both Ubuntu 10.04 and Windows.  I re-checked the audio settings on Windows using Realtek’s software and found out that it wasn’t detecting the headphones when I plugged it in.  Bingo!  Hardware issue.

Rummaging quickly through all the mess in the room, I was unsuccessful in finding the Intel motherboard manual.  A quick search on Google (I had to find the motherboard name via the receipt) got me a match that was closest to my mobo.

Ahhh… so the guys at the computer store got all the wires wrong except for the ground wire.   Wow! And to think they would’ve been experts on this already.  It was a no brainer. Just look at the manual and follow which wire goes where.  So after a bit of  “rewiring” and crossing of fingers, I had the front audio jack working on Windows.

Time to test it on Ubuntu 10.04.  There was no reason it shouldn’t work since the USB headphones was detected fine down to the brand name.  Unfortunately this wasn’t true. No sound came out even after selecting and re-selecting different audio settings.

I installed additional PulseAudio and ALSA mixer tools and still not even a faint squeak came out from the Sony MDR-XB500.  Searching on Google, Ubuntu support pages and even on its IRC channel was getting me nowhere.

…until I stumbled unto a forum thread about “options snd-hda-intel model=MODEL”.   Adding the appropriate model then appending it to alsa-base.conf file supposedly is the key to making the jack work. And it did!

First you have to find out your sound card model. Below are 2 links that can help you find it.

Then insert the appropriate model code to the alsa-base.conf file. The URL below is a list of the common sound card models and what you should put opposite “model=”.

Once you’ve found that out, append it, like I’ve mentioned before, to your alsa-base.conf file.

Must be done with root privileges (use `sudo` if you are on Ubuntu).  For my setup, I have Realtek ALC888 but my machine is unbranded. I figured “auto” would work. It did.

options snd-hda-intel model=auto

Reload ALSA afterwards

alsa forcereload

Or if you want to be sure, just restart your computer.


I was streaming music through Rythmbox shortly with the bass thumping as loud as my poor ears could manage.

Yahoo unsupported OS

unsupported OS warning from Yahoo! Mail

Seriously, I am so sick and tired of this warning that Yahoo! Mail gives out when you are not using Windows or a Mac.  For fuck’s sake get rid of that warning Yahoo! Perhaps everyone in the Linux or BSD community already know that and we’re not dumb idiots like so many of the Windows or Mac users.

The problem started as far back as June this year.  Yahoo users trying to connect to the said network through Kopete could not.  Several people were quick to notice it.

A quick fix was to override the default server for logging in to something else. But this was a temporary fix.  Eventually it didn’t work anymore.  Not wanting to use any other 3rd party messenger, I opted to log on to the messenger service through Yahoo Mail.  It works fine even on Linux versions of Firefox although Yahoo does warn you that the operating system you are using has not been tested.

Months after, I went back to using Kopete for Yahoo after I upgraded my desktop.  It appears that the newer versions has the fix for the Yahoo problem patched into it.  Currently I am using Kopete version 0.80.2 on KDE 4.3.2.  What is strange is that I can’t login to all my accounts.  I have 3 Yahoo accounts.   Out of the 3, only 2 are able to connect successfully to the Yahoo servers. The other one can’t connect and there are no apparent error messages except for,

Object::connect: No such signal ClientStream::disconnected()
Object::connect:  (receiver name: 'yahooclient')
Transfer ACCEPTED by: LoginTask
Transfer ACCEPTED by: LoginTask

If you are experiencing a similar problem drop me a note on how you fixed it.  If you still haven’t found a solution, we can go report a bug @ to make it official. I am guessing that this might not be a Kopete problem, but it won’t hurt if the developers are made aware of this weird behavior.

In the meantime, I’ll keep on searching for fixes.  Oh by the way, the one account that could not connect wasn’t like this all the time.  It was able to connect once, and that was the one time only, then after that it wouldn’t anymore.

ADSL connections on Kubuntu 9.04

Posted: October 27, 2009 in linux

What Does NOT Work

KNetworkManager can’t manage ADSL connections.  Don’t waste your time searching the web for solutions. It’s not worth it in the end.

WIDC won’t work.  I never understood what WIDC was supposed to do.  It endlessly scanned my machine and got nothing.  The configuration options is a mess as well.  It doesn’t really provide any clear options and you will just end up as confused as to how to configure your ADSL connection with KNetworkManager.

What Works

pppoeconf works out of the box most of time. Unless if your ISP really has a weird ADSL setup, then chances are, your connection won’t work if configured through this app.  The chances are slim.

The program pppoeconf should be accessible under /usr/sbin/pppoeconf on Kubuntu 9.04 and should be used with administrator or root privileges.  So use sudo on this command. By the way, this is an application that should be run on the terminal.  Get konsole or, for me, yakuake, on the ready.

Just go with the defaults.  It works fine. Once you’ve got it configured you’re good to go.

pon dsl-provider – to turn ON the  ADSL connection

poff dsl-provider – to turn OFF the ADSL connection

Again, both commands above should be used with administrator or root privileges.  Sudo is your friend!  But you shouldn’t be using these commands at all.  If everything goes right, Kubuntu Jaunty Jackalope should remember all of you your settings on the next session.  You don’t have to add anything to have your connection start automatically on boot.  Everything should already be set correctly.

Have fun surfing the web!

Since last week I have had trouble connecting to Yahoo! using Kopete.  I guess the same holds true for those who are using Pidgin.  At first I thought my Amarok was just eating up too much bandwidth since I was streaming party music from Cool Streams.  So I didn’t really bother connecting to Yahoo, exiting it (Kopete) after it was unable to login to my account.

Today I tried connecting to Yahoo again.  This time Amarok wasn’t streaming.  After some time I still didn’t see any buddy icons in the list.  Strange.  I checked the connection status and it said, “Connecting.”  I tried changing the status from offline to online several times and waited several minutes without any success. Just to be sure that Kopete wasn’t doing anything stupid, I added my Google Talk account.  It connected fast after the setup!  Ok this calls for some google-ing!

I Googled for any news that was affecting Kopete from connecting to the Yahoo! message service.. .  And there it was! A lot of people using Kopete, and Pidgin as well, were having the same problems.  Here is a link to the bug that was reported to

So for a quick and temporary fix, they suggested to change servers.  From the default you should change your server to either of the following:


You can change this by going to Settings > Configure > Accounts.  Then select your Yahoo! account, press Modify Account.  Change to the Account Preferences tab.  Check Override default server information then edit to either of the ones above.

The port is still 5050.

Both servers 1 and 2 didn’t work for me, though some people confirmed that it worked for them.  Only server 3 allowed me to connect.

Try it out and welcome back online!

the pattern:


what it does:

this is a nice regular expression pattern that spans multiple lines.


pattern used – <label>Address:(\n|.)*<label>Website:

<div id=’cominfo_hdr_div’>Company Information</div>¶

33rd Flr. PBCom Tower, Ayala Ave., Corner Herrera St.<br>Makati City, Metro Manila <br><br>¶
</label><br>¶ <br><br> ¶
<label>More Information</label><br>¶

this is very useful for parsing text from data with a repeating pattern.  just queue up the data source in a loop, run the regular expression pattern through it and you should have that particular text you want in no time.  yes?

Nope!  at least for me it didn’t. it got me something else instead.

from my repeated manual tests using patterned strings spanning multiple lines similar to the example above, this regular expression would work.  however, when i started feeding the actual data for parsing in a loop, i got a PHP Segmentation Fault at some point. the data source isn’t that huge.  about 15 – 30 KB each in size, and close to a thousand.  sometimes it went through once or twice without an error, but after several iterations in the loop it always went down to a Segmentation Fault.

what seems to be the matter?

this has been around for a while.  i’m posting this on my blog because i keep on forgetting the steps.  at least i don’t have to search the web for it now.  and i’m spreading the `love` too!  hehe.. . 😛

here are the three (3) easy steps to make your start up faster.  many people find a bit slow and heavy.  this is very noticeable when you start it up.  while there is a quickstarter applet for this, i never liked to use it. it’s only eating up valuable memory.

note: before you do this, start and try to observe how fast (or slow) it initializes.  then compare the start-up time after you’ve done these steps.

Step 1 > Open up the Options dialog box. You can do this by clicking on Tools, then selecting Options from the menu as shown below.


Step 2 > Select Memory from under  There are like 5 things you can set under Memory.  Copy the ones shown in the image.  These are the advisable values.


in other How To sites, they recommend to enable the QuickStarter applet.  i don’t recommend this. in fact, i never use that applet.  i don’t know if it’s still packaged with the newer versions. it seems like that is in the older versions of  the Memory  Options in the newer versions of this wonderful office suite doesn’t have that quickstarter option.  you won’t see it anymore.  i’m using 3.0 as packaged with Kubuntu 9.04.

Last Step (3) > Go to Java Options. Make sure the checkbox is not checked.


After you’ve done these steps, click OK and you are good to go!  Exit  Start it again and see the difference these 3 simple steps make.

you may want to read this post too >>