Urgent help need
Submitted by mikelee on Fri, 05/02/2008 - 10:33am.
I use Intel Mother board. DG33TL with Core2 Quad CPU, 4gb DDR2 RAM. and Sangoma A200D 8 port FXO with echo cancellation board. after installation I find there are two "kernal" at start up time
trixbox (2.6.18-53.1.4.el5PAE)
trixbox base (2.6.18-53.1.4.el5)
When I start with 2.6.18-53.1.4.el5PAE, it will stop at "Starting udev" for a while and eventually it will failed in this module udev, and it will continue with slowly to load other modules. When finished, you login seems over all it is much slow than 2.6.18-53.1.4.el5 kernel. and it also had problem to install Sangoma A200D drivers.
James suggest me that el5PAE kernel is not useful, refer to following links
http://www.trixbox.org/wiki/kernel-PAE
I should use (2.6.18-53.1.4.el5 kernel. I did that. all modules are loaded very fast, and system response is also very fast, that match my hardware, Core2 Quad CPU, 4GB RAM.
and I installed Sangoma A200D driver and configure the Zaptel channel. Everything seems to work. But just have one problem. need resolve. every time when it reboot, it automatically go to default kernel 2.6.18-53.1.4.el5PAE, I try to change /boot/grub/grub.conf, use vi to change default from 0 to 1. after reboot, the system stop at grub> prompt.
I tried to reinstall several times, and tried to use $do2unix grub.conf one of my friends suggest grub.conf is DOS format file it use vi will mess up the file. But nothing worked. Whenever I touched grub.conf use vi it will failed.
Is anyone can help ?
Thanks in advance.
Mik
do yum install webminthen
Fri, 05/02/2008 - 10:55am
do yum install webmin
then on a workstation go to https://your.trixbox.ip.address:10000 (must be https)
login as root
Go to Hardware, then grub, and you can then select the non-PAE kernel as the default boot kernel.
VI should never hurt any files on your system, users can hurt files;), alternatively you could use winscp on a windows workstation to edit that.
a proper grub.conf should look like (although I dont know if this matches your drive types):
# 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/sda2
# initrd /initrd-version.img
#boot=/dev/sda
default=0
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
#hiddenmenu
title trixbox (2.6.18-53.1.4.el5)
root (hd0,0)
kernel /vmlinuz-2.6.18-53.1.4.el5 ro root=LABEL=/ acpi=off
initrd /initrd-2.6.18-53.1.4.el5.img
oh - and Kodak means www.pastebin.ca - dont put your config in a forum posting unless you use code tags, or pastebin
Thanks all reply
Fri, 05/02/2008 - 9:40pm
Here is my /boot/grub/grub.conf
# 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/mapper/isw_cbbjdjdhdi_RAID1_DISKp2
# initrd /initrd-version.img
#boot=/dev/mapper/isw_cbbjdjdhdi_RAID1_DISK
default=0
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
#hiddenmenu
title trixbox (2.6.18-53.1.4.el5PAE)
root (hd0,0)
kernel /vmlinuz-2.6.18-53.1.4.el5PAE ro root=LABEL=/ acpi=off
initrd /initrd-2.6.18-53.1.4.el5PAE.img
title trixbox-base (2.6.18-53.1.4.el5)
root (hd0,0)
kernel /vmlinuz-2.6.18-53.1.4.el5 ro root=LABEL=/ acpi=off
initrd /initrd-2.6.18-53.1.4.el5.img
----------------------------------------------------
All I do is just use vi change default=0 to default=1 and save it.
I'm long term UNIX user, so I could not be wrong in vi.
Here is my situation
Fri, 05/02/2008 - 9:36pm
Because system wll stop at grub > the OS did not event boot up. so you can not ;login as root or https://your.trixbox.ip.address:10000 http service have no start yet. The only thing I can try to boot it up again is re-install.
if you use vi to comment out
Fri, 05/02/2008 - 9:39pm
if you use vi to comment out it will lead system boot stop at " grub> " prompt.
I had follow that instruction to comment out those your suggestion, and it lead system stop boot at " grub> " prompt.
I find out if you use vi to edit this file, any part it could lead not bootable again.
Member Since:
2006-11-06