-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't compile Dahdi Linux on kernel 5.19.0-76051900-generic #10
Comments
What distro and version are you using? (Version of Linux distro, as well as version of DAHDI Linux). Make sure you are using DAHDI Linux 3.2.0, not 3.1.0! If you are installing from Git, use the next head, not master head. |
Ubuntu (Pop OS!) 22.04 LTS
On Tue, Sep 6, 2022 at 12:48 PM InterLinked1 ***@***.***> wrote:
What distro and version are you using?
—
Reply to this email directly, view it on GitHub
<#10 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEIO45ZEDMZB247WNHWVO53V46NXZANCNFSM6AAAAAAQGAVXTU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
--
Chad Jones
***@***.***
Inline image
|
You didn't answer the other questions (DAHDI version) (or if you did, it didn't come through as it appears an inline image was stripped). Please copy and paste as text. I doubt many people use PopOS for this, and Debian tends to be more popular than Ubuntu for Asterisk so this may have not been seen before. It's important to have as many details as possible if someone is going to replicate. |
My apologies; distro is Pop OS! (based upon Ubuntu LTS 22.04), kernel is 5.19.0-76051900-generic, and Dahdi was cloned from Asterisk repo using: git clone -b next https://github.com/asterisk/dahdi-linux.git. Prereqs installed (build-essential, nodejs, etc). |
Thanks for the info. Out of curiosity, if you install using PhreakScript, does it work for you? https://github.com/InterLinked1/phreakscript e.g. Just used that to install on Debian 11 with a 5.10 kernel and no issues with DAHDI install there. |
I've not tried Phreakscript yet; thanks for the tip! As for nodejs, it seems it's a prereq for either FreePBX or Asterisk these days: https://www.google.com/search?client=firefox-b-1-d&q=nodejs+prereq+FreePBX+Asterisk |
Unfortunately, I get the same result using phreaknet: /usr/src/dahdi-linux-3.2.0-rc1/drivers/dahdi/wct4xxp/base.c: In function ‘t4_allocate_buffers’: |
nodejs would be required for FreePBX, but not for Asterisk (you hadn't mentioned FreePBX before). |
Hello all, I have a fresh build of Debian 12 (amd64) and am also seeing this issue. Looks like dahdi support may now be broken on the updated kernel used by popular distros?
|
Hi Mike! If you use PhreakScript to install DAHDI, that should patch this (known issue) |
@push143smart I think this issue was resolved by merge of ee13cb2 and can be closed. |
Hi everyone, I need to build v3.2.0 (and not newer) on debian 12. I gave a try to phreakscript which works really great but the --no-rc option was not taken and I ended up with 3.3.0-rc version. EDIT : IDK if it helps, I'm running kernel '6.1.0-13-amd64' |
Is there a reason you want 3.2.0 over 3.3.0? I know it's "technically" an RC, but it's really the only suitable version for production. It should have been GA released a LONG time ago, Sangoma has just not done it yet because they're very slow. |
Yes, there is a reason. |
In general, I think newer versions of DAHDI can be used just fine on older kernels (though the reverse does not hold).
What are the exact issues that you encounter? Can you post a log? Do you mind sharing the driver to reproduce this issue?
There is really no difference between 3.2 and 3.3 apart from some long overdue compilation fixes being included. It's really a rather small update. I'm not sure I'm fully convinced that they know what they're talking about. |
Thx for your reply.
I'm not sure I want to try this : )
When building their driver on top of DAHDI v3.3.0, it returns errors and does not proceed. I had a successful build one or two months ago with version 3.2. I don't know why I'm just not able to reproduce this.
Yes I can share (logs and driver) but I would prefer to make it not public if it's okay.
Absolutely, I'm not a developer, but to me, these build errors look ridiculous, just some basic syntax stuff. I'm pretty sure as well that would be worth fixing on their side but their last email didn't sound like that. |
I wouldn't either, as current Asterisk will run into issues with older systems.
Can you share the logs at least, if properly sanitizer? Keeping them public ensures anyone can look at them and work on the issue.
I wouldn't feel bad, you paid for a product presumably, and I think it's reasonable as a customer to expect that it build on a current system. If they are not willing to do their due diligence, then posting the driver here may at least allow one of us to patch whatever issue you are seeing. If you really do want to get DAHDI v 3.2.0 working, you can try one of two things:
|
Hi,
I tried the version just before 0497566df8d406c9ceb2db61dea3ac422e3ba48f and another prior one that has the 'verified' label. It's always looking for 'dahdi-current' which means v3.3.0 now. I couldn't find any 'dahdi version' variable in these versions. Maybe me missing something anyway.
Agreed 100%. So, here is a build log against DAHDI v3.3.0-rc1 (same output with v3.3.0) :
Any thoughts ? Likely something minor ? Thx for your support |
Currently, it's at line 200 of the script.
It seems to think these all belong to the It's likely something small missing/changed somewhere which is causing it to output an error like that. But I'd need to see the actual driver source to get further insight on that. You could try compiling with 3.2.0 with the change above, but I'd honestly be very surprised if that worked. |
Hi, Thx again for your help. |
Keep getting the following error:
root/dahdi-linux/drivers/dahdi/wct4xxp/base.c: In function ‘t4_allocate_buffers’:
/root/dahdi-linux/drivers/dahdi/wct4xxp/base.c:3864:17: error: implicit declaration of function ‘pci_alloc_consistent’ [-Werror=implicit-function-declaration]
3864 | alloc = pci_alloc_consistent(wc->dev, numbufs * T4_BASE_SIZE(wc) * 2,
| ^~~~~~~~~~~~~~~~~~~~
/root/dahdi-linux/drivers/dahdi/wct4xxp/base.c:3864:15: warning: assignment to ‘void *’ from ‘int’ makes pointer from integer without a cast [-Wint-conversion]
3864 | alloc = pci_alloc_consistent(wc->dev, numbufs * T4_BASE_SIZE(wc) * 2,
| ^
/root/dahdi-linux/drivers/dahdi/wct4xxp/base.c: In function ‘t4_increase_latency’:
/root/dahdi-linux/drivers/dahdi/wct4xxp/base.c:3943:9: error: implicit declaration of function ‘pci_free_consistent’ [-Werror=implicit-function-declaration]
3943 | pci_free_consistent(wc->dev, T4_BASE_SIZE(wc) * oldbufs * 2,
Please advise.
The text was updated successfully, but these errors were encountered: