Open celsoannes opened 1 month ago
Same problem here with Rocky 9 on Proliant Gen9, work with other server Gen8 Gen10. On the same server Centos 7 Dahdi 2.11 work .
didnt find any solution at this time.
Considering that the card works on the same machine with an older version, it should work with a newer version.
Can anyone help me?
Thank you!
I agree it should work... these kinds of issues are tricky to track down though and hard for others to reproduce as they don't have all the same hardware. I do have a Proliant ML110 G7 but it doesn't look like there are ever issues with that you've observed.
One thing that's worked for me in the past, you could try is doing a git bisect
(or manually bisecting by going back to each commit). If you do binary search between the Git head at the time of 2.11 and now, you should be able to identify a commit that broke something. If that can be identified, that gives us something to work with.
@InterLinked1 I've always installed the DAHDI package from the address http://downloads.asterisk.org/pub/telephony/dahdi-linux-complete/.
I've never installed it via Git, which makes me hesitant to use git bisect
because I wouldn't know how to do it precisely. This uncertainty could potentially lead us in the wrong direction when diagnosing the issue.
Additionally, I can't install a version of DAHDI earlier than 3.2.0 on Debian 11 due to kernel limitations. If there's a way for me to contact you, I can provide access to the machine if you're interested in testing.
@InterLinked1 I've always installed the DAHDI package from the address http://downloads.asterisk.org/pub/telephony/dahdi-linux-complete/.
It's generally recommended to install dahdi-linux and dahdi-tools separately (and that's what I do), I can't say anything about using the complete tarball.
I've never installed it via Git, which makes me hesitant to use
git bisect
because I wouldn't know how to do it precisely. This uncertainty could potentially lead us in the wrong direction when diagnosing the issue.
I actually don't use git bisect
proper myself. You can simply checkout a specific commit git checkout <COMMIT>
(git log
will provide a list of these in descending order). You can basically start in the middle and keep dividing the commits in half until you narrow it down. Since DAHDI is a much smaller project than, say, Asterisk, it shouldn't take more than 5-10 tries to narrow it down in this manner.
Additionally, I can't install a version of DAHDI earlier than 3.2.0 on Debian 11 due to kernel limitations.
Yeah, that can be a challenge with these sorts of things... I think newer DAHDI versiond should run on an older kernel since they are intended to be backwards compatible, so you could maybe try using an older kernel + range of DAHDI versions and see if you notice anything.
If there's a way for me to contact you, I can provide access to the machine if you're interested in testing.
Unfortunately, I don't have time to do personalized troubleshooting, but I'm happy to provide guidance if it's helpful, and if you narrow it down to a specific commit, I could at least take a look at it from there.
Hello,
I currently have the following setup working perfectly:
However, when I try to upgrade to the following configuration:
The Digium Wildcard TE220 card does not work and gives the message:
I have tested using the same card on different servers with the same configurations:
ProLiant ML110 G7 (Work)
ProLiant ML110 G3 (Work)
I even tested this configuration:
Both the ProLiant ML110 G7 and ProLiant ML110 G3 work perfectly without any issues.
For some reason, the combination of (ML110 Gen9, Debian 11+, DAHDI 3.2.0+, TE220) does not work. I have the DAHDI configurations as follows:
/etc/dahdi/modules
/etc/dahdi/system.conf
kernel:
5.10.0-30-amd64
.dahdi_cfg -vvvvvvvvv
cat /proc/interrupts
dmesg
Considering that the card works on the same machine with an older version, it should work with a newer version.
Can anyone help me?
Thank you!