Login Into Single User Mode Linux

LILO >>>

ok, i found the easiest way to change a root passwd on a physically
accessed machine is to apply the boot params "init=/bin/bash rw"
 
ie if you use lilo, and your image is "linux" try

press "esc" when lilo prompt comes out, and press "tab" 

linux init=/bin/bash rw

this should drop you to a root shell.

use passwd to change the root password and enter your new password.

and run "sync" before you reboot.

finally use ctlr+alt+del for reboot

GRUB >>>

if you use grub, try

(1) At grub boot screen (after restart)

(2) Select the kernel

(3) Press the e key to edit the entry

(4) Select second line (the line starting with the word kernel)

(5) Press the e key to edit kernel entry so that you can append single user mode

(6) Append the letter S (or word Single) to the end of the (kernel) line

(7) Press ENTER key

(8) Now press the b key to boot the Linux kernel into single user mode

(9) When prompted give root password and you be allowed to login into single user mode.

Installing And Using OpenVZ On CentOS 5.7

In this HowTo I will describe how to prepare a CentOS 5.7 server for OpenVZ. With OpenVZ you can create multiple Virtual Private Servers (VPS) on the same hardware, similar to Xen and the Linux Vserver project. OpenVZ is the open-source branch of Virtuozzo, a commercial virtualization solution used by many providers that offer virtual servers. The OpenVZ kernel patch is licensed under the GPL license, and the user-level tools are under the QPL license.

This howto is meant as a practical guide; it does not cover the theoretical backgrounds. They are treated in a lot of other documents in the web.

This document comes without warranty of any kind! I want to say that this is not the only way of setting up such a system. There are many ways of achieving this goal but this is the way I take. I do not issue any guarantee that this will work for you!

1 Installing OpenVZ

In order to install OpenVZ, we need to add the OpenVZ repository to yum:

cd /etc/yum.repos.d
wget http://download.openvz.org/openvz.repo
rpm --import http://download.openvz.org/RPM-GPG-Key-OpenVZ
 

Now open openvz.repo...

vi openvz.repo

... and disable the [openvz-kernel-rhel6] repository (enabled=0) and enable the [openvz-kernel-rhel5] repository instead (enabled=1):

[...] # Stable branches [openvz-kernel-rhel6] name=OpenVZ RHEL6-based kernel #baseurl=http://download.openvz.org/kernel/branches/rhel6-2.6.32/current/ mirrorlist=http://download.openvz.org/kernel/mirrors-rhel6-2.6.32 enabled=0 gpgcheck=1 gpgkey=http://download.openvz.org/RPM-GPG-Key-OpenVZ [openvz-kernel-rhel5] name=OpenVZ RHEL5-based kernel #baseurl=http://download.openvz.org/kernel/branches/rhel5-2.6.18/current/ mirrorlist=http://download.openvz.org/kernel/mirrors-rhel5-2.6.18 enabled=1 gpgcheck=1 gpgkey=http://download.openvz.org/RPM-GPG-Key-OpenVZ [openvz-kernel-rhel4] name=OpenVZ RHEL4-based kernel #baseurl=http://download.openvz.org/kernel/branches/rhel4-2.6.9/current/ mirrorlist=http://download.openvz.org/kernel/mirrors-rhel4-2.6.9 enabled=0 gpgcheck=1 gpgkey=http://download.openvz.org/RPM-GPG-Key-OpenVZ [...]

The repository contains a few different OpenVZ kernels (you can find more details about them here: http://wiki.openvz.org/Kernel_flavors). The command :
yum search ovzkernel

shows you the available kernels:

[root@server1 yum.repos.d]# yum search vzkernel
...
ovzkernel.i686 : Virtuozzo Linux kernel (the core of the Linux operating system)
ovzkernel.x86_64 : Virtuozzo Linux kernel (the core of the Linux operating system)
ovzkernel-PAE.i686 : The Linux kernel compiled for PAE capable machines.
ovzkernel-PAE-devel.i686 : Development package for building kernel modules to match the PAE kernel.
ovzkernel-devel.i686 : Development package for building kernel modules to match the kernel.
ovzkernel-devel.x86_64 : Development package for building kernel modules to match the kernel.
ovzkernel-ent.i686 : The Linux kernel compiled for huge mem capable machines.
ovzkernel-ent-devel.i686 : Development package for building kernel modules to match the ent kernel.
ovzkernel-xen.i686 : The Linux kernel compiled for Xen VM operations
ovzkernel-xen.x86_64 : The Linux kernel compiled for Xen VM operations
ovzkernel-xen-devel.i686 : Development package for building kernel modules to match the kernel.
ovzkernel-xen-devel.x86_64 : Development package for building kernel modules to match the kernel.
[root@server1 yum.repos.d]#

Pick one of them and install it as follows:

yum install ovzkernel

If the last command gives you errors like...

WARNING: /lib/modules/2.6.18-274.el5.028stab093.2/kernel/drivers/acpi/acpi_memhotplug.ko needs unknown symbol strcpy
WARNING: /lib/modules/2.6.18-274.el5.028stab093.2/kernel/drivers/acpi/acpi_memhotplug.ko needs unknown symbol add_memory
WARNING: /lib/modules/2.6.18-274.el5.028stab093.2/kernel/drivers/acpi/acpi_memhotplug.ko needs unknown symbol swiotlb
WARNING: /lib/modules/2.6.18-274.el5.028stab093.2/kernel/drivers/acpi/acpi_memhotplug.ko needs unknown symbol memory_add_physaddr_to_nid
WARNING: /lib/modules/2.6.18-274.el5.028stab093.2/kernel/drivers/acpi/acpi_memhotplug.ko needs unknown symbol remove_memory
WARNING: /lib/modules/2.6.18-274.el5.028stab093.2/kernel/drivers/acpi/acpi_memhotplug.ko needs unknown symbol strcmp
WARNING: /lib/modules/2.6.18-274.el5.028stab093.2/kernel/drivers/acpi/acpi_memhotplug.ko needs unknown symbol acpi_get_node
WARNING: /lib/modules/2.6.18-274.el5.028stab093.2/kernel/drivers/edac/amd64_edac_mod.ko needs unknown symbol amd_unregister_ecc_decoder
WARNING: /lib/modules/2.6.18-274.el5.028stab093.2/kernel/drivers/edac/amd64_edac_mod.ko needs unknown symbol amd_register_ecc_decoder
WARNING: /lib/modules/2.6.18-274.el5.028stab093.2/kernel/drivers/edac/amd64_edac_mod.ko needs unknown symbol amd_report_gart_errors
WARNING: /lib/modules/2.6.18-274.el5.028stab093.2/kernel/drivers/edac/amd64_edac_mod.ko needs unknown symbol amd_decode_nb_mce
WARNING: /lib/modules/2.6.18-274.el5.028stab093.2/kernel/drivers/cpufreq/freq_table.ko needs unknown symbol strcpy
WARNING: /lib/modules/2.6.18-274.el5.028stab093.2/kernel/drivers/cpufreq/freq_table.ko needs unknown symbol _cpu_pda
WARNING: /lib/modules/2.6.18-274.el5.028stab093.2/kernel/drivers/edac/i7core_edac.ko needs unknown symbol edac_mce_register
WARNING: /lib/modules/2.6.18-274.el5.028stab093.2/kernel/drivers/edac/i7core_edac.ko needs unknown symbol edac_mce_unregister
WARNING: /lib/modules/2.6.18-274.el5.028stab093.2/kernel/drivers/edac/i7core_edac.ko needs unknown symbol __memcpy
WARNING: /lib/modules/2.6.18-274.el5.028stab093.2/kernel/drivers/infiniband/hw/ipath/ib_ipath.ko needs unknown symbol dma_ops
WARNING: /lib/modules/2.6.18-274.el5.028stab093.2/kernel/drivers/infiniband/hw/ipath/ib_ipath.ko needs unknown symbol copy_from_user
WARNING: /lib/modules/2.6.18-274.el5.028stab093.2/kernel/drivers/infiniband/hw/ipath/ib_ipath.ko needs unknown symbol bad_dma_address
WARNING: /lib/modules/2.6.18-274.el5.028stab093.2/kernel/drivers/infiniband/hw/ipath/ib_ipath.ko needs unknown symbol find_first_bit
WARNING: /lib/modules/2.6.18-274.el5.028stab093.2/kernel/drivers/infiniband/hw/ipath/ib_ipath.ko needs unknown symbol strcat
WARNING: /lib/modules/2.6.18-274.el5.028stab093.2/kernel/drivers/infiniband/hw/ipath/ib_ipath.ko needs unknown symbol mem_section
WARNING: /lib/modules/2.6.18-274.el5.028stab093.2/kernel/drivers/infiniband/hw/ipath/ib_ipath.ko needs unknown symbol copy_to_user
WARNING: /lib/modules/2.6.18-274.el5.028stab093.2/kernel/drivers/infiniband/hw/ipath/ib_ipath.ko needs unknown symbol strncpy
WARNING: /lib/modules/2.6.18-274.el5.028stab093.2/kernel/drivers/infiniband/hw/ipath/ib_ipath.ko needs unknown symbol __memcpy
WARNING: /lib/modules/2.6.18-274.el5.028stab093.2/kernel/drivers/infiniband/hw/ipath/ib_ipath.ko needs unknown symbol strcmp
WARNING: /lib/modules/2.6.18-274.el5.028stab093.2/kernel/drivers/infiniband/hw/ipath/ib_ipath.ko needs unknown symbol alloc_pages_current
WARNING: /lib/modules/2.6.18-274.el5.028stab093.2/kernel/arch/x86_64/kernel/microcode.ko needs unknown symbol copy_from_user
WARNING: /lib/modules/2.6.18-274.el5.028stab093.2/kernel/arch/x86_64/oprofile/oprofile.ko needs unknown symbol cpu_to_node
WARNING: /lib/modules/2.6.18-274.el5.028stab093.2/kernel/arch/x86_64/oprofile/oprofile.ko needs unknown symbol copy_from_user
WARNING: /lib/modules/2.6.18-274.el5.028stab093.2/kernel/arch/x86_64/oprofile/oprofile.ko needs unknown symbol copy_user_generic
WARNING: /lib/modules/2.6.18-274.el5.028stab093.2/kernel/arch/x86_64/oprofile/oprofile.ko needs unknown symbol profile_pc
WARNING: /lib/modules/2.6.18-274.el5.028stab093.2/kernel/arch/x86_64/oprofile/oprofile.ko needs unknown symbol copy_to_user
WARNING: /lib/modules/2.6.18-274.el5.028stab093.2/kernel/arch/x86_64/oprofile/oprofile.ko needs unknown symbol strcmp
WARNING: /lib/modules/2.6.18-274.el5.028stab093.2/kernel/arch/x86_64/kernel/cpufreq/powernow-k8.ko needs unknown symbol strncmp
WARNING: /lib/modules/2.6.18-274.el5.028stab093.2/kernel/arch/x86_64/kernel/cpufreq/powernow-k8.ko needs unknown symbol _cpu_pda
WARNING: /lib/modules/2.6.18-274.el5.028stab093.2/kernel/drivers/pci/hotplug/shpchp.ko needs unknown symbol strcpy

... please remove ovzkernel...

yum remove ovzkernel 

... and install the ovzkernel package for your architecture:
On x86_64 systems:

yum install ovzkernel.x86_64 

On i686 systems:

yum install ovzkernel.i686 

This should automatically update the GRUB bootloader as well. Anyway, we should open /boot/grub/menu.lst; the first kernel stanza should now contain the new OpenVZ kernel. Make sure that the value of default is 0 so that the first kernel (the OpenVZ kernel) is booted automatically instead of the default CentOS kernel.

vi /boot/grub/menu.lst

# grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. # root (hd0,0) # kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00 # initrd /initrd-version.img #boot=/dev/sda default=0 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title OpenVZ (2.6.18-274.el5.028stab093.2) root (hd0,0) kernel /vmlinuz-2.6.18-274.el5.028stab093.2 ro root=/dev/VolGroup00/LogVol00 selinux=0 initrd /initrd-2.6.18-274.el5.028stab093.2.img title CentOS (2.6.18-274.el5) root (hd0,0) kernel /vmlinuz-2.6.18-274.el5 ro root=/dev/VolGroup00/LogVol00 initrd /initrd-2.6.18-274.el5.img

Now we install some OpenVZ user tools:

yum install vzctl vzquota

Open /etc/sysctl.conf and make sure that you have the following settings in it:

vi /etc/sysctl.conf

[...] net.ipv4.ip_forward = 1 net.ipv4.conf.default.proxy_arp = 0 net.ipv4.conf.all.rp_filter = 1 kernel.sysrq = 1 net.ipv4.conf.default.send_redirects = 1 net.ipv4.conf.all.send_redirects = 0 net.ipv4.icmp_echo_ignore_broadcasts=1 net.ipv4.conf.default.forwarding=1 [...]

If you need to modify /etc/sysctl.conf, run

sysctl -p

afterwards.

The following step is important if the IP addresses of your virtual machines are from a different subnet than the host system's IP address. If you don't do this, networking will not work in the virtual machines!

Open /etc/vz/vz.conf and set NEIGHBOUR_DEVS to all:

vi /etc/vz/vz.conf

[...] NEIGHBOUR_DEVS=all [...]

SELinux needs to be disabled if you want to use OpenVZ. Open /etc/sysconfig/selinux and set the value of SELINUX to disabled:

vi /etc/sysconfig/selinux

# This file controls the state of SELinux on the system. # SELINUX= can take one of these three values: # enforcing - SELinux security policy is enforced. # permissive - SELinux prints warnings instead of enforcing. # disabled - SELinux is fully disabled. SELINUX=disabled # SELINUXTYPE= type of policy in use. Possible values are: # targeted - Only targeted network daemons are protected. # strict - Full SELinux protection. SELINUXTYPE=targeted

Finally, reboot the system:

reboot

If your system reboots without problems, then everything is fine!
Run

uname -r

and your new OpenVZ kernel should show up:

[root@server1 ~]# uname -r
2.6.18-274.el5.028stab093.2
[root@server1 ~]#

2 Using OpenVZ

Before we can create virtual machines with OpenVZ, we need to have a template for the distribution that we want to use in the virtual machines in the /vz/template/cache directory. The virtual machines will be created from that template. You can find a list of precreated templates on http://wiki.openvz.org/Download/template/precreated.
I want to use CentOS 5 in my virtual machines, so I download a CentOS 5 template:

cd /vz/template/cache
wget http://download.openvz.org/template/precreated/centos-5-x86.tar.gz

I will now show you the basic commands for using OpenVZ.
To set up a VPS from the default CentOS 5 template, run:

vzctl create 101 --ostemplate centos-5-x86 --config basic

The 101 must be a uniqe ID - each virtual machine must have its own unique ID. You can use the last part of the virtual machine's IP address for it. For example, if the virtual machine's IP address is 192.168.0.101, you use 101 as the ID.
If you want to have the vm started at boot, run

vzctl set 101 --onboot yes --save

To set a hostname and IP address for the vm, run:

vzctl set 101 --hostname test.example.com --save
vzctl set 101 --ipadd 192.168.0.101 --save

Next we set the number of sockets to 120 and assign a few nameservers to the vm:

vzctl set 101 --numothersock 120 --save
vzctl set 101 --nameserver 8.8.8.8 --nameserver 8.8.4.4 --nameserver 145.253.2.75 --save

(Instead of using the vzctl set commands, you can as well directly edit the vm's configuration file which is stored in the /etc/vz/conf directory. If the ID of the vm is 101, then the configuration file is /etc/vz/conf/101.conf.)

To start the vm, run

vzctl start 101

To set a root password for the vm, execute

vzctl exec 101 passwd

You can now either connect to the vm via SSH (e.g. with PuTTY), or you enter it as follows:

vzctl enter 101

To leave the vm's console, type

exit

To stop a vm, run

vzctl stop 101

To restart a vm, run

vzctl restart 101

To delete a vm from the hard drive (it must be stopped before you can do this), run

vzctl destroy 101

To get a list of your vms and their statuses, run

vzlist -a


To find out about the resources allocated to a vm, run

vzctl exec 101 cat /proc/user_beancounters 

The failcnt column is very important, it should contain only zeros; if it doesn't, this means that the vm needs more resources than are currently allocated to the vm. Open the vm's configuration file in /etc/vz/conf and raise the appropriate resource, then restart the vm.
To find out more about the vzctl command, run

man vzctl 

Source : http://www.howtoforge.com/installing-and-using-openvz-on-centos-5.7-p2

How to install and configure smokeping on CentOS 6 or CentOS 5?

Smokeping is a very useful network monitoring tool but it’s also very complicated to install and configure.
Here are the steps for installing smokeping on CentOS 6 or CentOS 5.
To make it easier to deploy we recommend to temporarily disable selinux with this command:
setenforce 0

1 – Install rpmforge
# yum install wget
* For CentOS 6 please use this repository:
# wget http://pkgs.repoforge.org/rpmforge-release/rpmforge-release-0.5.2-2.el6.rf.x86_64.rpm
# rpm -Uvh rpmforge-release-0.5.2-2.el6.rf.x86_64.rpm
* For CentOS 5 please use this repository:
# wget http://pkgs.repoforge.org/rpmforge-release/rpmforge-release-0.5.2-2.el5.rf.x86_64.rpm
# rpm -Uvh rpmforge-release-0.5.2-2.el5.rf.x86_64.rpm

2 – Install required packages
# yum install mod_fcgid httpd httpd-devel rrdtool fping wget curl bind-utils gcc make

3 – Install more packages
# yum install perl perl-Net-Telnet perl-Net-DNS perl-LDAP perl-libwww-perl perl-RadiusPerl perl-IO-Socket-SSL perl-Socket6 perl-CGI-SpeedyCGI perl-FCGI perl-RRD-Simple perl-CGI-SpeedCGI perl-ExtUtils-MakeMaker

4 – Install smokeping
# wget http://oss.oetiker.ch/smokeping/pub/smokeping-2.6.8.tar.gz
* You should check on smokeping website for the latest version.
# tar -zxvf smokeping-2.6.8.tar.gz -C /opt/
# mkdir /opt/smokeping
# cd /opt/smokeping-2.6.8/setup
# ./build-perl-modules.sh
# cp -r ../thirdparty /opt/smokeping/
# cd ..
# ./configure –prefix=/opt/smokeping
* There are twice – before the prefix so it is –prefix. # make install

5 – Create missing folders
# cd /opt/smokeping
# mkdir data var cache

6 – Add smokeping start/stop script
# wget http://new.wedebugyou.com/static/smokeping_start_stop.txt
# mv smokeping_start_stop.txt /etc/init.d/smokeping
# chmod 755 /etc/init.d/smokeping

Here are the steps for configuring smokeping.

1 – Rename config files and change security
# cd /opt/smokeping/etc/
# for foo in *.dist; do cp $foo `basename $foo .dist`; done
# chmod 600 /opt/smokeping/etc/smokeping_secrets.dist

2 – Change the default config files
# vi config
Change the values in bold to something that fit your needs.
owner    = Peter Random
contact  = some@address.nowhere
mailhost = my.mail.host
sendmail = /usr/sbin/sendmail
# NOTE: do not put the Image Cache below cgi-bin
# since all files under cgi-bin will be executed … this is not
# good for images.
imgcache = /opt/smokeping/cache
imgurl   = cache
datadir  = /opt/smokeping/data
piddir  = /opt/smokeping/var
cgiurl   = http://some.url/smokeping.cgi
smokemail = /opt/smokeping/etc/smokemail.dist
tmail = /opt/smokeping/etc/tmail.dist

Here is an example:
owner    = Jean Debogue
contact  = noc@jeandebogue.com
mailhost = my.mail.host
sendmail = /usr/sbin/sendmail
# NOTE: do not put the Image Cache below cgi-bin
# since all files under cgi-bin will be executed … this is not
# good for images.
imgcache = /opt/smokeping/cache
imgurl   = cache
datadir  = /opt/smokeping/data
piddir  = /opt/smokeping/var
cgiurl   = http://graph.mydomain.com/smokeping/smokeping.cgi
smokemail = /opt/smokeping/etc/smokemail.dist
tmail = /opt/smokeping/etc/tmail.dist

3 – Configure smokeping into the webserver
# cd /opt/smokeping
# ln -s /opt/smokeping/cache /opt/smokeping/htdocs/cache
# chown -R apache cache
# chown -R apache data
Add these lines into the file /etc/httpd/conf.d/smokeping.conf
ScriptAlias /smokeping/smokeping.cgi /opt/smokeping/htdocs/smokeping.fcgi.dist
Alias /smokeping /opt/smokeping/htdocs
<Directory “/opt/smokeping/htdocs”>
Options FollowSymLinks
</Directory>

4 – Start smokeping
# /etc/init.d/smokeping start
# /etc/init.d/httpd start

 5 – Expect the worst hope for the best
If there are no error message you are in a very good position. You can now browse to the webpage you configure in the config file cgiurl = http://graph.mydomain.com/smokeping/smokeping.cgi.

 

 

Here are the steps to add your own configuration

1 – Add your own host in the config file
It’s quite complicated to explain all the details of smokeping configuration file. The best is to read their documentation or check the many examples available online. You can also use our example config file. Just paste this file under the line *** Probes *** in your config file. Our example contains an icmp probe, a dns check, a check on port 80 and a full fetch of the default webpage of www.google.com.

2 – Restart smokeping
After changing the config file, it is important to restart smokeping with this command:
# /etc/init.d/smokeping restart

3 – Clean installation files
# rm -rf /opt/smokeping-2.6.8

4 – Enable smokeping to start automatically on reboot
# chkconfig –add smokeping
* There are twice – before the add so it is –add.
# chkconfig httpd on
# chkconfig smokeping on

You can now also use smokeping. Do you also use smokeping? Do you monitor routers, servers, websites? Do you use it into a master/slave mode? We would like to hear from you how you use smokeping in your day to day life.

Source :  http://www.wedebugyou.com/2012/11/how-to-install-and-configure-smokeping-on-centos-6/

Httpd.conf | RewriteEngine

<Directory "/var/www/html/lg">
                Options +Indexes FollowSymLinks +ExecCGI
                AllowOverride AuthConfig FileInfo
                Order deny,allow
#               Deny from all
#               Allow from 202.65.113.0/24 202.65.112.0/24
                Allow from all
</Directory>

<VirtualHost 202.65.114.204:80>
                Options FollowSymLinks
                ServerAdmin support@jogja.citra.net.id
                DocumentRoot /var/www/html/lg
                ServerName lg.jogja.citra.net.id
                        RewriteEngine On
                        RewriteCond %{REMOTE_ADDR} ^202\.65\.11[2-3]\.
                        RewriteRule ^(/|/lg2)$ /lg [R]
                        RewriteCond %{REMOTE_ADDR} !^202\.65\.11[2-3]\.
                        RewriteRule ^(/|/lg)$ /lg2 [R]
</VirtualHost>

Alias /lg/favicon.ico "/var/www/html/lg/favicon.ico"
ScriptAlias /lg "/var/www/html/lg/lg.cgi"
ScriptAlias /lg2 "/var/www/html/lg2/lg.cgi"

CARA MENGATASI GUITAR RIG TIDAK BERSUARA

Tentang postingan kali ini,…mungkin udah banyak diantara temen temen yang tau ya,….n mungkin juga ini bukan masalah yang baru,…tentang apa,….???????….tentang guitar rig yang nggak bersuara

lah kalo udah banyak yang tau,..kenapa di posting lagi,…hehehe,…ternyata temen temen ane disini juga banyak yang masih beloom tau,…jadi nya ane mau share lagi di sini.
kali ini ane akan share tentang cara ngatasin guitar rig yang nggak ngeluarin suara.tapi sebelumnya,…di sini ane bukan bermaksud untuk menggurui ato sok ngajarin ya,…tapi ane cuman mau berbagi pengalaman ama temen temen yang mungkin kebetulan ngebaca postingan ane yang berantakann ini,…hehehehe,…
kembali kepokok bahasan,kenapa guitar rig nggak ngluarin suara,….mungkin itu terjadi karena beberapa hal,…n di bawah ini beberapa cara yang bisa temen temen lakukan untuk mengatasi maslah tersebut.

CEK GITAR

sbelum temen temen melakukan settingan pada sound di komputer,…..sebaiknya temen temen pastiin dulu kalo gitar beserta jack n perangkat lainnya dalam keadaan baik,..coba di periksa dulu siapa tau jacknya yang putus,…..
cara memeriksanya,….mungkin bisa menggunakan tester,atau temn temen bisa mencobanya di speaker lain dulu,…
kalo ternyata nggak ada masalah pada gitar ato jack nya,….mari kita coba untuk melakukan sedikit pengaturan pada komputer,…..

SETTING KOMPUTER

sbelumnnya,..pastiin dulu kalo komputer temen temen nggak dalam keadaan mute,….karena kalo dalam keadaan mute,,……sama aja boong,….
kalo komputernya nggak dalam keadaan mute,…n guitar rignya masih nggak bersuara,….coba lakukan langkah langkah brikut.
ane harapkan disini,….temen temen udah install guitar rig serta asio4all nya,…..klao belum punya ,..silahkan kesini,…..

- tutup guitar rig,n cabut gitar dari komputer.
- colokkan lagi guitarnya.( guitar rig nya jangan di jalankan dulu )
- klik start>ketik realtek>pilih realtek HD audio manager.

- klik device advance setting.

- klik sparate all input jacks,..bla bla bla,….( lihat gambar )

- dengan memilih opsi ini,…biasanya akan muncul device baru dengan nama mic in at front panel ( black )
- klik ok.

langkah brikutnya,…….

- klik start> tulis sound> pilih sound.

- kli pada tab recording.

- disable semua device yang ada disana kecuali device yang baru muncul tadi ( mic in at ……….)

- klik aply> ok.

sekarang,….sebelum temen temen menjalankan guitar rignya,……coba cek asionya terlebih dahulu.ini bertujuan supaya nggak ada program laen yang make soun device kita.

- dowble klik pada icon asio.
- lihat,ada device yang di silang ato nggak.
- kalo ada,berarti ada program laen yang make sound device temen temen,(kaya winamp,aimp,wmp,dll)
- cek n tutup program tsb terlebih dahulu.

kalo udah nggak ada program laen yang menggunakan sound device,…..coba jalankan lagi guitar rignya,…jangan buru buru,…hehehe,…coba ikuti lagkah langkah berikut.

- cabut dulu gitarnya dari laptop / komputer.
- jalankn guitar rig.
- baru colokkkan lagi guitarnya,…

gimana,…udah ada suarannya apa beloom,….
emang agak susah sih,….tapi dari hasil pengalaman ane ,….setelah menempuh beberapa cara diatas,..ini sangat berhasil untuk mengatasi guitar rig yang nggak bersuara,….tapi walaupun pada judul postingan ini sekias di tujukan untuk guitar rig,….cara ini kayanya juga berlaku untuk temen temen yang menggunakan overloud,ato amplitube.
tapi kalo ternyata cara cara diatas masih belum berhasil,…..mungkin noise nya yang terlalu tinggi,..klik disiniuntuk cara mengurangi noise pada guitar rig.

ughh,…akhirnya,…selesai juga,….kalo masih ada dian tara temen temen yang kurang jelas,atau kurang mmahami bahasa ane yang berantakan ini….silahkan berkomentar,…n tentu nantinya ane akan membantu semampu ane,…
sekian dulu postingan ane kali ini,…semoga bermanfaat,n terimakasih buat yang udah mampir.

Install WineAsio 0.9.0 on Ubuntu 11.04 (deb file included)

If you really need VST or any ASIO related application on linux the solution i simple:

WineAsio

“WineASIO provides an ASIO to JACK driver for WINE. ASIO is the most common Windows low-latency driver, so is commonly used in audio workstation programs.”

I created a little guide to install via deb file.

Install Wine and Jack:

sudo apt-get install wine jackd qjackctl

Install WineAsio

A) deb file:

Download  and install this package

wget http://www.lucamazzilli.it/downloads/wineasio_0.9.0-1_i386.deb

sudo dpkg -i wineasio_0.9.0-1_i386.deb

B) from source:

Install dependencies

- if you are using jack 1

sudo apt-get install libjack-dev

- if you are using jack2

sudo apt-get install libjack-jackd2-dev

Download and extract

wget http://leaseweb.dl.sourceforge.net/project/wineasio/wineasio-0.9.0.tar.gz

tar -zxvf wineasio-*

cd wineasio

search google for asio.h (file:asio.h) than copy to your source folder and:

make

sudo make install

if you get an error like this:

luca@pc:~/wineasio$ sudo make install
if [ -d /usr/lib32/wine ]; then cp wineasio.dll.so /usr/lib32/wine; else cp wineasio.dll.so /usr/lib/wine; fi

just copy wineasio.dll.so on the correct folder in old fashioned way:

- 64bit

sudo cp wineasio.dll.so /usr/lib32/wine

- 32bit

sudo cp wineasio.dll.so /usr/lib/wine

register wine library

regsvr32 wineasio.dll

Configure Wine to use alsa and jack

winecfg

select audio tab, than pick Jack Driver and Alsa Driver

Install some cool stuff like EnergyXT or Reaper.

Making Music on Linux; It’s A Thing

I was never a great, or even good, guitar player, but it’s something I really enjoyed doing for a decent chunk of my life. But as life and work grew more complex, it kind of fell by the wayside, a casualty of the demands of adulthood.

But recently, I’ve been actively trying to carve out time to mess around with my guitar. Because I live in an apartment, I became intrigued by the idea of amp and pedal modeling, where instead of playing through a physical amp or guitar pedal, one plays into a computer, with the amp and pedal sound created by software.

I was intrigued for a few reasons. I liked that I could get an amp sound without having to disturb anyone. But I also loved the access to different kinds of amps and pedals modeling provided. I could enhance my sound without having to invest money or space in equipment.

There are lots of ways to model amps and pedals. Apple’s GarageBand is probably one of the most popular consumer avenues. But I wanted to try and implement something on Linux, despite the near constant refrain that Linux doesn’t do audio production well.

I decided to repurpose my T43 ThinkPad for music and downloaded Ubuntu Studio 11.04 (the Ubuntu Studio people very candidly recommend against 11.10). Ubuntu Studio is a fairly standard Ubuntu with a bunch of multimedia packages pre-installed. I liked that aspect since it let me play with a lot of software without having to figure out what I should be playing with.

In order to play into my laptop mic jack, I got a cheap 1/4”-1/8” converter for my guitar cable at RadioShack and then I was ready to go.

I share my experiences as a production amateur. My previous recording setups were a cheap cassette four-track and prior to that, a tape recorder from the early 1990s. Digital recording had, up to a few weeks ago, completely passed me by.

For instance, I quickly learned that anyone working with instrument recording in Linux needs to work with JACK. JACK serves as virtual jacks, allowing you to connect sounds to each other. For instance, if you’re playing through an amp modeler, you need JACK running to connect your guitar output to the amp modelling software. If you’re recording, you need JACK to connect the output to the recorder. It’s very logical but until you know that JACK is what moves sound around, it can be a bit frustrating to hear nothing but your unprocessed guitar coming through your headphones. It also seems that sound is always going to come through your headphones and not your laptop speakers. I was happy with the sound in my headphones, so I never investigated getting sound out of my built-in speakers.

Linux has some very nice modeling options. Rakarrack is a great processor, with lots of interesting options. It’s incredibly customizable, in a paralyzingly intimidating way, but it has some nice presets to get you started carving out the right sound. It’s a truly amazing piece of software.

I had also heard some good things about AmpliTube, a Windows/OS X product. AmpliTube comes with a few pedals, amps, and cabinets, with users able to buy more. It’s an intriguing model, but I mostly just wanted to mess around with the free pedals, of which there is a nice variety. I couldn’t get it running via Wine in Ubuntu Studio, and the old GNOME interface was killing me, so, having figured out which music software I wanted, I just installed Xubuntu 11.10 and grabbed everything from the repositories (I’m still madly in love with OpenSUSE but you really can’t beat the Ubuntu repositories for scope and convenience).

AmpliTube works perfectly in Xubuntu via Wine. It did require WineAsio, which isn’t in any repositories. I couldn’t get it to run off of the project download page, but I found this guide and it got everything working for me.

AmpliTube has a snazzier interface than Rakarrack and Guitarix, but I found it harder to manipulate the sound variables in AmpliTube. AmpliTube tries to preserve the pedal/rack/dial metaphor and that doesn’t always translate to a mouse and computer screen interface. AmpliTube has some great sounds, though. Plus, it lets you demo pedals, although when I tried to record with a pedal I was trialing, I got random static bursts every few seconds. But it’s still nice to get a sense of if a pedal is worth “purchasing.”

Guitarix is a Linux product. It’s an amp simulator, but it also has some pedal-like effects in its virtual rack. The big trick for me was figuring out to tell Guitarix to show the racks so I could tweak the effects. But once I found that option, under the Plugins menu, I really got into playing with Guitarix. It had some very nice, organic-sounding tones.

Once I had some sounds down, I figured I should record. Ardour is a hardcore digital audio workstation, but it was way too much tool for me, so I’ve been using Audacity. Linux music people online seem very excited about Bitwig Studio, which isn’t available yet. Depending upon pricing, I might check that out once it’s available.

When recording, you need to tell the tool to pull the signal from JACK. And you need to make sure JACK is connecting your sound to the recording tool. Usually this involves starting to record and then making the connection.

Once I was able to record some guitar (and some bass — Rakarrack has a bass simulation that’s not bad), I figured I should put some drums on my tracks, too. Hydrogen is a neat little drum machine. The drum kit sounds are nice but there weren’t a lot of preset beats to work with. But programming Hydrogen isn’t too bad, once you know a few basic drum patterns. I poked around on YouTube and learned you have a snare on the 1 and the 3, bass drum on the 2 and the 4, and some sort of cymbal on each beat. The sad thing is, I’ve played with drummers a bit over the years, but really had no idea what they were doing on a theoretical level.

My Hydrogen beats aren’t horribly inventive, but they allow me to work on my rhythm and to give my tracks the vague impression that the music is played by humans. And playing with drums is helping me tremendously with my rhythm, or lack thereof. I did some very rough demos, just to give a sense of the various guitar sounds available, as well as a basic application of Hydrogen. You can hear them here.

In addition to the fun of playing guitar and of messing around with Linux, I’m actually learning a lot about music. Things I never thought about, like rhythm and time signatures and arranging, have suddenly become very visible to me. And while I can’t say I have a handle on any of those things, I do feel more aware of them than I was when I was just bashing away on a guitar without any of these audio tools.

Was this a lot of work to get going? It took some time to figure out how to do everything, but it was time I enjoyed.

Would this be easier on a Mac with GarageBand? Probably. But the results, now that everything is setup, are impressive. I’m able to relatively easily make music and flesh out ideas. Obviously, as someone who’s not a professional musician and not looking to release any music, my standards are different than someone with more serious goals. But for the casual home recorder, Linux is a perfectly viable option.

If you’re at all interested in home recording, give Linux a try. It’s a little work to get rolling, but once it’s up and running, you’ll find a lot of great tools to bring your ideas to life. It’s pretty amazing to think I can do all of this with a 2GB machine that’s over five years old and that creating this entire studio didn’t cost me anything out of pocket.

Source :http://www.mylinuxrig.com/post/16693327231/making-music-on-linux-its-a-thing