I had problem with hdmi audio from ubuntu. Video is going fine to LCD tv through HDMI cable, but no audio.
Not sure if that is a problem with operating system or the multimedia softwares, but I found mplayer supporting audio as well.
Following line has fixed hdmi audio for me.
mplayer -afm hwac3,hwdts, -ao alsa:device=hdmi -channels 2 file
Skype, web cam:
Web cam was not detected by skype on ubuntu (9.04). After searching on internet, installed gspcs-source, followed by a system restart.
sudo apt-get install gspca-source
Skype recognized my webcam and when ever I am on voice call with my skype contacts, I am able to share video through webcam.
Kopete, yahoo IM problem:
Kopete was not able to connect to Yahoo server. fix I found on internet is add subdomain "cn" in the server name (account preferences). this "cn.scs.msg.yahoo.com" one worked for me. the default port of 5050 is same.
kopete is not able to detect webcam. It needs jasper conversion utility installed. I tried to to install libjasper-progs, but it seems replaced by another one in the ubuntu repository.
Here is the line that worked for me.
sudo apt-get install libjasper-runtime
Showing posts with label ubuntu. Show all posts
Showing posts with label ubuntu. Show all posts
Friday, August 28, 2009
Tuesday, August 04, 2009
Low volumne in ubuntu
If you are struck up with low volumn in Ubuntu (even in 9.04)
do the following:
sudo apt-get install gnome-alsamixer
after installing gnome-alsamixer run it, it pops up a UI. Increase the PCM value towards maximum.
try the sound now, you got it full right?
do the following:
sudo apt-get install gnome-alsamixer
after installing gnome-alsamixer run it, it pops up a UI. Increase the PCM value towards maximum.
try the sound now, you got it full right?
Wednesday, July 29, 2009
Linux /Ubuntu tomcat -> too many open files
Issue:
How do I set the maximum number of files allowed to be open on a system
scenario: I am running 3 war files of magnolia CMS on local tomcat, third one is not getting deployed properly because of the "too many files" opened.
Resolution:
The current setting for maximum number of open files can be viewed with the command:
ulimit -n
This number indicates the maximum number of files normal users (i.e. non-root) can have open in a single session. Note that for the root user, ulimit -n will sometimes output 1024 even after following the procedure to increase the maximum number of open files. This won't effect root's ability to open large numbers of files, as only normal users are bound by this value.
To increase the maximum number of open files beyond the default of 1024, two changes to the system may be necessary. In these examples, we will increase the maximum number of open files to the arbitrary value of 2048. All changes need to be made by the root user and users will need to log out and log back in before the changes will take effect.
1. Configure the system to accept the desired value for maximum number of open files Check the value in /proc/sys/fs/file-max to see if it is larger than the value needed for the maximum number of open files:
# cat /proc/sys/fs/file-max
If the value isn't large enough, echo an appropriate number into the variable and add the change to /etc/sysctl.conf to make it persistent across reboots. If the number is already larger than the value you wish to use, skip to step 2.
# echo 2048 > /proc/sys/fs/file-max
and edit /etc/sysctl.conf to include the line:
fs.file-max = 2048
2. Set the value for maximum number of open files In the file /etc/security/limits.conf, below the commented line that reads
# -
add this line:
* - nofile 2048
This line sets the default number of open file descriptors for every user on the system to 2048. Note that the "nofile" item has two possible limit values under the header: hard and soft. Both types of limits must be set before the change in the maximum number of open files will take effect. By using the "-" character, both hard and soft limits are set simultaneously.
The hard limit represents the maximum value a soft limit may have and the soft limit represents the limit being actively enforced on the system at that time. Hard limits can be lowered by normal users, but not raised and soft limits cannot be set higher than hard limits. Only root may raise hard limits.
When increasing file limit descriptors, you may want to simply double the value. For example, if you need to increase the default value of 1024, increase the value to 2048 first. If you need to increase it again, try 4096, etc.
How do I set the maximum number of files allowed to be open on a system
scenario: I am running 3 war files of magnolia CMS on local tomcat, third one is not getting deployed properly because of the "too many files" opened.
Resolution:
The current setting for maximum number of open files can be viewed with the command:
ulimit -n
This number indicates the maximum number of files normal users (i.e. non-root) can have open in a single session. Note that for the root user, ulimit -n will sometimes output 1024 even after following the procedure to increase the maximum number of open files. This won't effect root's ability to open large numbers of files, as only normal users are bound by this value.
To increase the maximum number of open files beyond the default of 1024, two changes to the system may be necessary. In these examples, we will increase the maximum number of open files to the arbitrary value of 2048. All changes need to be made by the root user and users will need to log out and log back in before the changes will take effect.
1. Configure the system to accept the desired value for maximum number of open files Check the value in /proc/sys/fs/file-max to see if it is larger than the value needed for the maximum number of open files:
# cat /proc/sys/fs/file-max
If the value isn't large enough, echo an appropriate number into the variable and add the change to /etc/sysctl.conf to make it persistent across reboots. If the number is already larger than the value you wish to use, skip to step 2.
# echo 2048 > /proc/sys/fs/file-max
and edit /etc/sysctl.conf to include the line:
fs.file-max = 2048
2. Set the value for maximum number of open files In the file /etc/security/limits.conf, below the commented line that reads
#
add this line:
* - nofile 2048
This line sets the default number of open file descriptors for every user on the system to 2048. Note that the "nofile" item has two possible limit values under the
The hard limit represents the maximum value a soft limit may have and the soft limit represents the limit being actively enforced on the system at that time. Hard limits can be lowered by normal users, but not raised and soft limits cannot be set higher than hard limits. Only root may raise hard limits.
When increasing file limit descriptors, you may want to simply double the value. For example, if you need to increase the default value of 1024, increase the value to 2048 first. If you need to increase it again, try 4096, etc.
Sunday, July 19, 2009
vmware keys not working on vmware server 2.0.1
Keys like del, arrows are not working for me. ubuntu host and windows guest (xp,2003).
as per the forum suggestion, i have appended the following lines to /etc/vmware/config file (sudo credentials required on ubuntu).
xkeymap.keycode.108 = 0x138 # Alt_R
xkeymap.keycode.106 = 0x135 # KP_Divide
xkeymap.keycode.104 = 0x11c # KP_Enter
xkeymap.keycode.111 = 0x148 # Up
xkeymap.keycode.116 = 0x150 # Down
xkeymap.keycode.113 = 0x14b # Left
xkeymap.keycode.114 = 0x14d # Right
xkeymap.keycode.105 = 0x11d # Control_R
xkeymap.keycode.118 = 0x152 # Insert
xkeymap.keycode.119 = 0x153 # Delete
xkeymap.keycode.110 = 0x147 # Home
xkeymap.keycode.115 = 0x14f # End
xkeymap.keycode.112 = 0x149 # Prior
xkeymap.keycode.117 = 0x151 # Next
xkeymap.keycode.78 = 0x46 # Scroll_Lock
xkeymap.keycode.127 = 0x100 # Pause
xkeymap.keycode.133 = 0x15b # Meta_L
xkeymap.keycode.134 = 0x15c # Meta_R
well, a short cut suggestion was adding the following line alone.
xkeymap.keycode.135 = 0x15d # Menu
But I pasted both of them, not sure which one caused the fix.
as per the forum suggestion, i have appended the following lines to /etc/vmware/config file (sudo credentials required on ubuntu).
xkeymap.keycode.108 = 0x138 # Alt_R
xkeymap.keycode.106 = 0x135 # KP_Divide
xkeymap.keycode.104 = 0x11c # KP_Enter
xkeymap.keycode.111 = 0x148 # Up
xkeymap.keycode.116 = 0x150 # Down
xkeymap.keycode.113 = 0x14b # Left
xkeymap.keycode.114 = 0x14d # Right
xkeymap.keycode.105 = 0x11d # Control_R
xkeymap.keycode.118 = 0x152 # Insert
xkeymap.keycode.119 = 0x153 # Delete
xkeymap.keycode.110 = 0x147 # Home
xkeymap.keycode.115 = 0x14f # End
xkeymap.keycode.112 = 0x149 # Prior
xkeymap.keycode.117 = 0x151 # Next
xkeymap.keycode.78 = 0x46 # Scroll_Lock
xkeymap.keycode.127 = 0x100 # Pause
xkeymap.keycode.133 = 0x15b # Meta_L
xkeymap.keycode.134 = 0x15c # Meta_R
well, a short cut suggestion was adding the following line alone.
xkeymap.keycode.135 = 0x15d # Menu
But I pasted both of them, not sure which one caused the fix.
Saturday, December 27, 2008
Sify broadband from Ubuntu/Kubuntu
Here are the instructions to install sify broadband client in Kubuntu/Ubuntu 8.10
Download the client from the location http://202.144.65.70:8090
When I clicked the link for linux, it opened up a PDF file with the details. look for the li. for ux client link http://202.144.65.70:8090/bbandclient_v30/sify_bbclient-3.0.tar.gz
then execute the following commands (after downloading the file).
gunzip sify_bbclient-3.0.tar.gz
tar -xvf sify_bbclient-3.0.tar
From the exploded location, execute install.sh
execute sudo ./install.sh
gksudo ln -s /usr/lib/libcrypto.so /usr/lib/libcrypto.so.4
gksudo ln -s /usr/lib/libssl.so /usr/lib/libssl.so.4
now, you can execute "sifyconnect" command from terminal and it pops up sify bb client.
Make sure you call sify customer care to register your system/laptop physical address so as you can connect without any problem.
Download the client from the location http://202.144.65.70:8090
When I clicked the link for linux, it opened up a PDF file with the details. look for the li. for ux client link http://202.144.65.70:8090/bbandclient_v30/sify_bbclient-3.0.tar.gz
then execute the following commands (after downloading the file).
gunzip sify_bbclient-3.0.tar.gz
tar -xvf sify_bbclient-3.0.tar
From the exploded location, execute install.sh
execute sudo ./install.sh
gksudo ln -s /usr/lib/libcrypto.so /usr/lib/libcrypto.so.4
gksudo ln -s /usr/lib/libssl.so /usr/lib/libssl.so.4
now, you can execute "sifyconnect" command from terminal and it pops up sify bb client.
Make sure you call sify customer care to register your system/laptop physical address so as you can connect without any problem.
Subscribe to:
Posts (Atom)