This procedure is not very comprehensively covered in the PBX manual. Below are some basic facts:
1. The pair to use from the "Free fork connector" "D-type" cable is the BROWN-WHITE.
2. You need to initiate music-on-hold for each extension.
Therefore:
ASPAC:PARNUM=154,PARVAL=1;
(PARVAL may have a different value if you use more than one device).
ASPAC:PARNUM=116,PARVAL=63;
(This PARVAL allows all call-types to receive music-on-hold).
RACEI:DIR=xxxx,CONT=251; --Repeat for all extensions
(The 251 value indicates that Music-on-hold source 1 is being used,i.e. BROWN-WHITE).
Wednesday, May 18, 2011
Saturday, May 14, 2011
Getting to Grips with GRUB
The fault was mine. I had resized my HDD with gparted and as a result my GRUB was no longer on /dev/sda8 but now on /dev/sda6. And to aggravate the problem I tried a lazy repair of the GRUB file which merely replaced the old file with a new empty one. Do I found myself staring at a screen proclaiming: "error:unknown file system" and "grub rescue>".
The minimal shell provided does not even have a help option. The following commands are possible:
set - to set a parameter
insmod - to activate a module
To manually boot your computer you need to gain access to the normal GRUB module.
grub rescue> set prefix=(hda,b)/boot/grub will tell the minimal bash shell to set it's current working directory to HDD a and partition b. So if your GRUB had been installed on your first hard drive and now existed in the sixth partition, then /dev/sda6 = (hd0,6) in GRUB speak.
grub rescue> insmod (hda,b)/boot/grub/linux.mod will activate the more well known grub shell.
Now that you find yourself in the standard GRUB shell, you can attempt to boot your OS.
rescue:grub> root=(hda,b) Here you specify the root partition of your OS
rescue:grub> linux /boot/vmlinuz-xxx Here you specify the kernel you want to boot. Naturally the "/boot" directory is located on the partition you specified in the command just before. It is good to note that TAB-completion does work!
rescue:grub> initrd /boot/initrd.img-xx.xx This specifies the inital image necessary to go from GRUB to booting the kernel.
rescue:grub> boot Will attempt to boot the specified initrd and vmlinuz files.
Of course, all you have accomplished is to boot your OS. But you have NOT repaired it. Normally the OS installer will scan your hard drive and generate a menu.lst file automatically for the boot process. To have this process repeated:
grub-install --root-directory=/boot /dev/sda
This will probe your hard drive for existing operating systems and generate a menu.lst "/boot/grub" on the specified hard drive.
Most of this I have done from memory, so I may have left out a step. If you still battle to get your grub repaired, other avenues to consider is:
*Editing menu.lst
*Using grub in a terminal.
The minimal shell provided does not even have a help option. The following commands are possible:
set - to set a parameter
insmod - to activate a module
To manually boot your computer you need to gain access to the normal GRUB module.
grub rescue> set prefix=(hda,b)/boot/grub will tell the minimal bash shell to set it's current working directory to HDD a and partition b. So if your GRUB had been installed on your first hard drive and now existed in the sixth partition, then /dev/sda6 = (hd0,6) in GRUB speak.
grub rescue> insmod (hda,b)/boot/grub/linux.mod will activate the more well known grub shell.
Now that you find yourself in the standard GRUB shell, you can attempt to boot your OS.
rescue:grub> root=(hda,b) Here you specify the root partition of your OS
rescue:grub> linux /boot/vmlinuz-xxx Here you specify the kernel you want to boot. Naturally the "/boot" directory is located on the partition you specified in the command just before. It is good to note that TAB-completion does work!
rescue:grub> initrd /boot/initrd.img-xx.xx This specifies the inital image necessary to go from GRUB to booting the kernel.
rescue:grub> boot Will attempt to boot the specified initrd and vmlinuz files.
Of course, all you have accomplished is to boot your OS. But you have NOT repaired it. Normally the OS installer will scan your hard drive and generate a menu.lst file automatically for the boot process. To have this process repeated:
grub-install --root-directory=/boot /dev/sda
This will probe your hard drive for existing operating systems and generate a menu.lst "/boot/grub" on the specified hard drive.
Most of this I have done from memory, so I may have left out a step. If you still battle to get your grub repaired, other avenues to consider is:
*Editing menu.lst
*Using grub in a terminal.
Subscribe to:
Posts (Atom)