dahdi-dkms failed to install/upgrade (failed to download firmware from downloads.digium.com)

[richard]

the module dahdi_vpmadt032_loader.ko failed to build without a direct connection to the internet, an authenticating proxy, a firewall or any filtering system.
The makefile tries a direct wget to the firmware and build failed without any useful notice if the firmware can't be downloaded.

1. Return a useful error message is the firmware failed to download
2. Add the ability to set proxy credentials or get it from the system (apt or gconf)

Binary package hint: dahdi-linux

im new and have no ideal on how to fix this

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: dahdi-dkms 1:2.2.1+dfsg-1ubuntu2
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic i686
Architecture: i386
Date: Wed May 5 20:42:53 2010
ErrorMessage: subprocess installed post-installation script returned error exit status 7
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
PackageArchitecture: all
SourcePackage: dahdi-linux
Title: package dahdi-dkms 1:2.2.1+dfsg-1ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 7

[David Biczo (dave-bullantsclub)]

Temp workaround if not using dahdi_vpmadt032_loader module:

Comment out as follows in /usr/src/dahdi-2.2.1+dfsg-1ubuntu2/dkms.conf:

#BUILT_MODULE_NAME[34]="dahdi_vpmadt032_loader"
#BUILT_MODULE_LOCATION[34]="drivers/dahdi/"
#DEST_MODULE_LOCATION[34]="/kernel/drivers/telephony/dahdi"

[Jean-Baptiste Lallement (jibel)]

Could someone experiencing this issue attach the build log. The log file is make.log located in /var/lib/dkms/dahdi/2.2.1+dfsg-1ubuntu2/build/

Thanks in advance.

[Steve Switzer (steve-switzer)]

Here you go... This was a fresh build tonight. Google brought me to this page

[Jean-Baptiste Lallement (jibel)]

Hm, pretty useless build log :/
Anyway, lets try something else. Open a terminal and sudo to root:
$ sudo -s

Then run the following commands:
$ cd /var/lib/dkms/dahdi/2.2.1+dfsg-1ubuntu2/build
$ (make distclean; make; make firmware-loaders; make) 2>&1 | tee /tmp/dahdi-make.log

And attach the file /tmp/dahdi-make.log

I suspect that something is going wrong with the download of the firmware. I can reproduce the exit status 7 by installing the module when offline.
just a blind guess were you connected to the internet while installing this module or are you using any kind of proxy or specific mean to access the internet ?

[Steve Switzer (steve-switzer)]

Yeah, I noticed the build log was rather thin, but that was indeed the full contents of the log.

I commented out the lines show above in post #2 and I was able to build it correctly.. The system has been delivered and installed at a customer site now.

However, your suspicion could be correct. In my office, the firewall blocks 100% of outbound Internet connections by default, and APT is configured to use a proxy server. I have a few pinhole rules here and there for things that can't use a proxy. However, neither the log file nor stdout suggested that it was a port blocking issue. I checked the firewall logs as well - didn't see any attempts. If I can get my hands on this system again before it's in production, I'll give this a try and let you know.

[Jean-Baptiste Lallement (jibel)]

From the way the makefile is done, it can't work without a direct connection to the internet or behind an authenticated proxy excepted if you put the full proxy string in the http_proxy environment variable. And if there's a firewall somewhere the module can't be installed either
At least the error message should be informative.

[Richard Powell (richard-powell)]

I'm hitting this issue as well. My machine has a direct connection to the internet but it's failing to retrieve the firmware. Is it possible Digium has relocated it on their website?

[Richard Powell (richard-powell)]

Here is my dahdi-make.log. Note that I am using a newer release of dahdi than what was originally reported (2.2.1+dfsg-1ubuntu3).

[Roger Tolhurst (roger-tolhurst)]

This has been an build failure issue for me also for some time despite an open Internet connection (Australia location).
A work-around that I have been using for some time is to manually do the nslookup of downloads.digium.com and enter the result into the /etc/hosts file.

The current entry in my hosts file is as follows:
“76.164.171.232 downloads.digium.com”

Why ‘wget’ cannot resolve this address during the build is the unresolved question.? But the ‘dahdi’ build constantly works this entry in the hosts file.

Roger