We update the kernel every 4 months or so to keep up with current security fixes and drivers. I just added the CentOS 2.6.18-164.11.1.el5 kernel to the trixbox 2.8 repo.
If you would like to test out the new kernel please update by using
yum update
from the command line. You should get the latest kernel and the latest zaptel drivers. Once the update is complete reboot your system. You will be booting with the new kernel. Make sure that DAHDI loads correctly during the reboot.
Andrew - Don't you mean the
Andrew - Don't you mean the latest DAHDI drivers?
Asterisk rpm
Will you update the asterisk rpm soon ?
Thanks.
Yes DAHDI drivers. Please
Yes DAHDI drivers. Please keep responses to this post about this post. If you have other questions post them in the forum.
Wont 2.6 get a new
Wont 2.6 get a new Centos??
VMware says that Centos 5.4 has no timing issues under ESX(i)
FWIW, my test box downloaded
FWIW, my test box downloaded 40mb worth of kernel and dahdi, and I rebooted it without any fanfare. All seems to be going well here.
Your mileage may vary.
yum update
Just did a yum update on my 2.8.0.3 with a openvox A400P card.
Lost my inbound calls. No answer when calling. Lost outbound calls too . "All circuits are busy now????"
Local calls ok!!
Probably something with the Dahdidriver but I'm no expert.
So back to a reinstall :-(
Regard Carsten
I'm not familiar with
I'm not familiar with openvox, but you probably need a driver from them that handles the 164 version of the kernel.
Not sure if you'll get this in time, but you don't need a reinstall.
Reboot, and select the 'old' 128 kernel from the grub menu, or change the grub.conf setup file to default to that kernel. (remember this starts at 0, so the first one listed will be 0, the second one listed will be 1, and so on. In my installation it was the fourth one listed, so I put a 3). Reboot and you'll be back on the old kernel.
I've got a Sangoma card, and I'll wait for their compiled driver for this kernel...
dahdi
post bellow
how DAHDI loads correctly during the reboot?
How to make DAHDI loads correctly during the reboot?
I updated with new kermel and lost all pstn, isdn lines. "All circuits are busy now"
I cant remove
rpm -del --nodeps kmod-mISDN mISDN-kmod-base kmod-dahdi-linux
got message
error: "kmod-mISDN" specifies multiple packages
error: package mISDN-kmod-base is not installed
error: "kmod-dahdi-linux" specifies multiple package
I tried
rpm -qa | grep mISDN-kmod-base
but no multiples
Any help,
Many thanks in anticipation.
Update success
My experience doing the upgrade...
Starting point:
* Originally installed Trixbox version 2.8.0.1 from ISO, running on an Intel Atom D945GLF2
* Did "yum update" a couple of days ago, which upgraded about 300 packages, including installing the new kernel & dahdi
* No problems with yum, rebooted..
Small things I had to fix on first boot:
* The default boot option in grub was the Xen variant of the new kernel, which didn't have any dahdi modules. Fixed this by re-ordering stuff in /boot/grub.conf, and rebooting. dahdi now loaded OK.
* When opening the web UI, it asked me to register, even though I had previously told it not to ask me again, and the option to ask was already off.
Things this update fixed for me:
* New kernel has fixed out-of-control eth0 rx errors on dual core Atom (Realtek RTL8168C/8111C) (https://bugzilla.redhat.com/show_bug.cgi?id=474334, I think)
* and, possibly related to that: fixed problem with packets being dropped, or getting very delayed (e.g. ping another machine on the LAN: usually 0.5ms, but with some coming back after 89 seconds)
* Fixed dahdi "all circuits busy" for outgoing calls after reboot, until at least one incoming call has been received (https://issues.asterisk.org/view.php?id=15429)
So, thanks for providing this new kernel and dahdi drivers :)
carsten & danac: Check to see which kernel your machine is booting. I found that the Xen one, which started by default for me after updating, didn't have dahdi drivers. Enter "uname -a" on the command line to find out which kernel is loaded, and edit /boot/grub.conf, or choose a different kernel at the grub menu.
I found that DAHDI was not
I found that DAHDI was not loading because by default the new CentOS xen kernel was being loaded.
I modified /boot/grub/grub.conf
and just commented out the XEN versions. Alternatively, you can set the default to your preference.
# 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 CentOS (2.6.18-164.11.1.el5xen)
# root (hd0,0)
# kernel /xen.gz-2.6.18-164.11.1.el5
# module /vmlinuz-2.6.18-164.11.1.el5xen ro root=LABEL=/
# module /initrd-2.6.18-164.11.1.el5xen.img
title CentOS (2.6.18-164.11.1.el5)
root (hd0,0)
kernel /vmlinuz-2.6.18-164.11.1.el5 ro root=LABEL=/
initrd /initrd-2.6.18-164.11.1.el5.img
#title trixbox (2.6.18-128.1.10.el5xen)
# root (hd0,0)
# kernel /xen.gz-2.6.18-128.1.10.el5
# module /vmlinuz-2.6.18-128.1.10.el5xen ro root=LABEL=/
# module /initrd-2.6.18-128.1.10.el5xen.img
title trixbox-base (2.6.18-128.1.10.el5)
root (hd0,0)
kernel /vmlinuz-2.6.18-128.1.10.el5 ro root=LABEL=/
initrd /initrd-2.6.18-128.1.10.el5.img
If anybody know a good way
If anybody know a good way to keep the xen kernel from installing by default I'd love to hear it. I guess I could put the xen kernel in another repo. But some trixbox users run trixbox on XEN so I don't want to delete the XEN kernel completely.
I pulled the XEN kernel from
I pulled the XEN kernel from the trixbox 2.8 repo. You can still get it from the devel repo if you need it.
yum install
I did yum update on my box. and it worked this time. Got Dahdi working.
but a peculiar thing has happened ?
The ringing tone has changed from the natural danish one to the english????
Is that on purpose?
regards
carsten