<body><script type="text/javascript"> function setAttributeOnload(object, attribute, val) { if(window.addEventListener) { window.addEventListener('load', function(){ object[attribute] = val; }, false); } else { window.attachEvent('onload', function(){ object[attribute] = val; }); } } </script> <div id="navbar-iframe-container"></div> <script type="text/javascript" src="https://apis.google.com/js/platform.js"></script> <script type="text/javascript"> gapi.load("gapi.iframes:gapi.iframes.style.bubble", function() { if (gapi.iframes && gapi.iframes.getContext) { gapi.iframes.getContext().openChild({ url: 'https://www.blogger.com/navbar/15532271?origin\x3dhttp://eclectice.blogspot.com', where: document.getElementById("navbar-iframe-container"), id: "navbar-iframe", messageHandlersFilter: gapi.iframes.CROSS_ORIGIN_IFRAMES_FILTER, messageHandlers: { 'blogger-ping': function() {} } }); } }); </script>

Saturday, July 22, 2006

Getting laid by Xgl/Compiz



Copyright © 2006 Ee. All rights reserved

My desktop wobbles!

Copyright © 2006 Ee. All rights reserved

I was introduced to Xgl/Compiz quite recently when I saw it on the Internet. Setting up Xgl/Campiz was straight-forward. I would be able to get it working straight away after buying a new NVIDIA GeForce FX 5500 256MB to replace my old rusty AGP 8X graphics card. But before that, I had to set up my NVIDIA card driver properly first. I opted for latest NVIDIA driver and set up nvidia-settings.

And, Xgl/Compiz was brilliantly executed on my Ubuntu Dapper Drake. There were several options available to set up Xgl/Compiz (you can find the instructions in here). But, the next time I tried to log into another Xgl session, I was bogged by this GLX problem:



X Error of failed request: BadLength (poly request too large or internal Xlib length error)
Major opcode of failed request: 142 (GLX)
Minor opcode of failed request: 1 (X_GLXRender)
Serial number of failed request: 98
Current serial number in output stream: 99


Oh my! What was that?

continued


I searched for the solution in Google and I found out it was a famous problem hitting Xgl/Compiz users. I tried all the solutions but I could not get hanged with it anymore. I went on reading some articles about Xgl/Compiz architecture. The articles said that NVIDIA had implemented its own indirect rendering with its binaries instead of open-source OpengGL MESA library. And, I realized that I had not installed nvidia-glx yet which it contained MESA GLX component needed by Xgl. It was evident that NVIDIA's nvidia-settings would not work with MESA-based nvidia-glx.

Once, I set up nvidia-glx immediately. Voila! I get my beloved Xgl/Compiz session back!


posted by Eclectic Ee @ 5:16 AM
1 comments | 

Tuesday, July 18, 2006

Microsoft Sites Down?



As for today since this post is written, all Microsoft sites are down. Hmm.

posted by Eclectic Ee @ 11:52 AM
0 comments | 

Thursday, July 06, 2006

Cool Linksys WAG354G Wireless-G ADSL Home Gateway



Certification ID: W003478
Certification ID: W003478

Copyright © 2006 Wi-Fi.org. All rights reserved
This is my first entry in 2006!


I've just recently bought Linksys WAG354G Wireless-G ADSL Home Gateway (WAG354G-SG) from PC Zone (Lot 2-42, 2nd. Floor, Low Yat Plaza, Kuala Lumpur) on the 4th of July 2006. After googling all way through Internet to look for a good all-in-one ADSL Internet gateway, I've finally decided to go for this model.

Below is the summary of my choice for the model:

  • ADSL modem + Router (LAN & Wireless) + Internet Gateway

  • Future Wireless-G support (up to 25Mbps; no Wireless-N support yet)

  • Compatible with TM ADSL Streamyx G.dmt scheme

  • Support WPA-Personal™ Pre-Shared Key (PSK)

  • Easy configuration (damn simple and straight-forward)

  • Simple design (with enough ventilation system)

  • Quite cheap among all-in-one models (you can get around RM330-RM370; I paid RM360 for it)



WAG354G is still a new model at Low Yat Plaza, and there is only one shop that sells it (yeah, yeah).

I consider WAG354G a reliable all-in-one internet gateway to connect to ADSL TM Streamyx broadband connection from my home. Even, at this time, I am testing it as a wireless router at my office besides the existing office's local LAN network.


continued

If you want to configure WAG354G as a wireless router in an existing local LAN network, you need to do the following (assuming that the default WAG354G gateway is 192.168.1.1 and its DHCP server is enabled; my existing LAN gateway is at 10.12.28.1):

  1. Connect any empty LAN port on WAG354G to your LAN network with a LAN cable (non-loopback)

  2. Connect your PC to any empty LAN port on WAG354G with another LAN cable (non-loopback)

  3. Open TCP/IP configuration (Windows, Linux, Mac OS X)

  4. Add 192.168.1.1 to the list of gateways and set it as Metric 1

  5. Reconfigure other gateways to use Metric 1

  6. Add static IP 192.168.1.X to the list of IP addresses (X must be a valid value listed in your WAG354G's DHCP server setting)

  7. Open WAG354G's setting (default http://192.168.1.1)

  8. Enable RIP routing (optional) under WAG354G's advanced routing setting

  9. Use "Obtain an IP Address Automatically" under WAG354G's basic setup setting

  10. Test connection to your existing LAN router from any PC in your local LAN network (use command-line "ping 10.12.28.1"); it should be 100% successful

  11. Test connection to WAG354G router from any PC in your local LAN network (use command-line "ping 192.168.1.1"); it should be 100% successful

  12. Do Steps 3 to 6 to configure other PCs in your local LAN network, especially the ones with WI-FI capability

  13. Add the same DNS settings like the DNS settings of your LAN local network into your PC's TCP/IP configuration




I've upgraded WAG354G firmware from 1.01.03 to 1.01.05. And, it seems to work fine at this moment. Next, I will test Wi-Fi certified WAG354G access points (AP) with Wi-Fi capable notebooks.

Update: My friend has tested my configuration with his notebook and it works flawlessly! He can surf the Internet via LAN local network.


posted by Eclectic Ee @ 11:33 AM
2 comments |