Wednesday, May 23, 2007

XServer Configuration in MiNevada Fixed!


Lintang and Adhari from Open Solaris User Group Indonesia (OSUG-ID) has answered my question in the Open Solaris User Group. The answer is referring to previous post sometimes ago by Adhari (thanks to Lintang for the pointer and thanks to Adhari for the resourceful answer). I posted the answer here just in case the Google Groups link is available no more.

Mungkin ada yang mengalami problem yang sama ketika configure Xserver di VMWare. Sedikit berbagi trick ketika configure XServer pakai Xsun provider Solaris 10 di atas VMWare. Beberapa hari coba-coba install Solaris 10 di VMWare, inginnya mau start XServer dengan resolusi 1024x768. Problem muncul, konfigurasi sudah benar pakai 1024x768 tapi output selalu produce resolusi 800x600.
Step konfigurasi:
1. Jalankan kdmconfig di single user mode (init level 1)
2. Pilih Xsun
3. Pilih Change Video Device/Monitor
4. Pilih XF86-VMWARE VMWare Inc vmware0405
5. Pilih MultiFreq 56khz (up to 1280x1024 interlaced)
6. Pilih 17"
7. Pilih 1024x768 - 16M colors
8. Continue dan test
9. Jika tampil dengan benar pilih Yes
10. Kembali ke Init Level 3

No worry if you don't understand Bahasa, I'll translate it for you.
May be there are people who experience the same problem when configuring the Xserver on VMWare. I want to share a little trick to configure the XServer using Sun Solaris 10 Xsun provider on VMWare. After days of trial and errors installing Solaris 10 in VMWare, I just wanted to start XServer using the 1024x768 resolution. The problem occurs, though the configuration is for 1024x768 but the output always produces the 800x600 resolution.
This is my configuration step by step:
1. Run kdmconfig in single user mode (init level 1)
2. Choose Xsun
3. Choose Change Video Device/Monitor
4. Choose XF86-VMWARE VMWare Inc vmware0405
5. Choose MultiFreq 56khz (up to 1280x1024 interlaced)
6. Choose 17"
7. Choose 1024x768 - 16M colors
8. Continue and test
9. If it shows correctly then choose Yes
10. Back to Init Level 3

The article itself does not directly answer my question, because I don't know whether the vmware solution applies to me which uses different vm (that is Microsoft Virtual PC). But I believe this article is a highly resourceful one, because it gives me idea on what to try.

So, this is what I actually did:
Crawling through the broken graphics, try to locate and click the [Command line login].

Change to single user mode:
# init 1

Try to run the kdmconfig
# kdmconfig

Not working, because the term is not recognized. I eventually managed to find a working terminal type (remember those good ol' they when ANSI terminals are luxurious stuffs).

# export TERM=ansi
# kdmconfig

Choose Xsun, continue.
Change Video device/Monitor, continue.
Notebook LCD XGA 48kHz (1024x768 @60Hz), continue.
15-inch, continue.
1024x768 - 256 colors @60 MHz, continue.
No changes needed - Test/Save and Exit, continue.
Test.
If you can see the display, click the [OK] button.
Voila, it works!!!

Back to init level 3.

# init 3

Yipeeee!

Friday, May 11, 2007

WebLogic 10.0 Users: Apply Critical Patch

BEA has identified a problem that affects all BEA WebLogic Server 10, BEA Workshop for WebLogic Platform 10, and BEA WebLogic Portal 10 users. The problem is caused by an erroneous license check against an internal license file that will expire on May 14, 2007.

BEA has addressed this problem. Two solutions are available:

  • A patch for existing WebLogic 10 installations, and

  • Updated installers


The patch is available from the BEA Patch Repository; the Patch ID is 2VJT.

Until a solution is applied, the implications of this problem are as follows:

  • If you attempt to boot a WebLogic Server 10 or WebLogic Portal 10 server prior to May 14, you will receive a warning that "sales@bea.com for information on extending your license.>".

  • If you attempt to boot a WebLogic Server 10 or WebLogic Portal 10 server on May 14 or afterwards, the server will not boot.

  • If you have booted a WebLogic Server 10 or WebLogic Portal 10 server prior to May 14, it will continue to run past May 14. However after May 14, attempts to make policy changes in the console will fail, and the server cannot be rebooted after May 14.


Please monitor http://support.bea.com for updates on this problem.