please update zaphfc driver to tip of trunk

Bug #612091 reported by eliza
22
This bug affects 3 people
Affects Status Importance Assigned to Milestone
dahdi-linux (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

Binary package hint: dahdi-dkms

Please update the file base.c of the zaphfc driver to the tip of the trunk. Otherwise hfc cards will recognised but wont work, because the D-channel appears to be down. (see http://code.google.com/p/zaphfc/issues/detail?id=1&can=1)

Tags: patch

Related branches

Revision history for this message
Antonis Kanouras (akanouras) wrote :

It's just an one-line change, without which the driver is totally useless.

Is there anything we can do to help push this forward?

Revision history for this message
Dave Walker (davewalker) wrote :

@Antonis, if you could provide the 1 line - it would make it easier to update.

Thanks.

Changed in dahdi-linux (Ubuntu):
status: New → Confirmed
importance: Undecided → Low
Revision history for this message
eliza (r-launchpad-frithjof-hammer-de) wrote :

I'll try:
This is a patch against the deb source directory of dahdi-linux-2.2.1+dfsg.

Revision history for this message
Antonis Kanouras (akanouras) wrote :

What Eliza said :)

Thanks for the prompt response!

Revision history for this message
Antonis Kanouras (akanouras) wrote :

Hmm,

did apt-get source ...
applied Eliza's patch
ran dpkg-buildpackage
installed the resulting dahdi-dkms...deb
and base.c is still unpatched in /var/lib/dkms/...

Debugging atm.

Cheers,
Antonio

Revision history for this message
Antonis Kanouras (akanouras) wrote :

Hello again,

after a long and educational session with quilt, I attach a refreshed version of the debian/patches/dahdi_linux_extra file.

The only change I made was updating drivers/dahdi/zaphfc/base.c to r7 in SVN (was r5). It contains two small changes - the first is an additional header include (linux/sched.h) for building with kernels 2.6.32+ and the second one is a typo fix (D -> DAHDI_D) which did all the damage.

I didn't touch the file debian/patches/zaphfc, as the Debian maintainer merged all extra driver patches into dahdi_linux_extra in http://bugs.debian.org/564720 and did not provide a way to automatically produce it, which I assume means he's going to drop them at a later stage.

I've tested the resulting package on my system and it seemed ok.

Feel free to ask me if anything else is needed.

Cheers,
Antonio

Revision history for this message
Antonis Kanouras (akanouras) wrote :

Attaching a minimal version of the patch which can be applied after dahdi_linux_extra, in case you prefer it in that form.

Also, disregard what I said about the header include, it actually seems like a (minimal) fix for kernels <2.6.32.

Cheers,
Antonio

tags: added: patch
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package dahdi-linux - 1:2.5.0.1+dfsg-1ubuntu1

---------------
dahdi-linux (1:2.5.0.1+dfsg-1ubuntu1) precise; urgency=low

  * Merge from Debian testing (LP: #879743). Remaining changes:
    - debian/dahdi-dkms.install.in : add .version
    - Import modifications by Javier Uruen Val <email address hidden>:
      - debian/system.conf
      - debian/modules
    - DKMS support:
      - debian/control: Added Depends to dahdi-linux (dahdi-dkms | dahdi-source)
      - debian/control: Add dkms package
      - debian/dahdi-dkms.install
      - debian/dahdi-dkms.postinst
      - debian/dahdi-dkms.prerm
      - debian/dahdi-linux.install
      - debian/rules: add code to automatically configure dkms.conf
      - debian/dkms.conf.in
  * Dropped changes:
    - debian/control: Fix typo (right command is m-a a-i dahdi-source)
    - debian/patches/define_spinlock: Fixed upstream
  * debian/rules: Debian moved to dh, re-add code to automatically configure
    dkms.conf
  * debian/dkms.conf.in: update to reflect dahdi-linux-extra patch update
    (opvxa1200's new location (subdir) and to include ap400 and opvxd115)
  * debian/patches/zaphfc_d_channel_fix.patch: Correct typo in zaphfc module
    until fix gets synced into dahdi-linux-extra patch in Debian (LP: #612091)

dahdi-linux (1:2.5.0.1+dfsg-1) unstable; urgency=low

  * New upstream release (Closes: #639702).
    - Patch wcb4xxp_bn4s0e removed: merged upstream.
    - Patch define_spinlock removed: merged upstream.
    - Patch dahdi-linux-extra updated.
  * Updated dahdi-linux-extra:
    - "Upstream" is now a complete git mirror.
    - Actually include ap400 in the list of modules to build.
    - Updated OpenVox drivers: opvxa1200 is a subdirectory
    - Updated OpenVox drivers: opvxd115 added (digital cards).
  * Patch define_spinlock: include a (slightly big) build fix from upstream.
  * Standards version 3.9.2 (no change needed).
  * Switch to dh.
  * Patch notest: Remove a bogus upstream 'test' target.
  * Lintian override for an odd interpteter a dummy kernel module init script.
  * Dahdi udev rules are now named 'dahdi-linux.conf'.
  * Patch xpp_fix_2fxs6fxo: bugfix for Xorcom 2FXX6FXO module code.
 -- Adam Gandelman <email address hidden> Fri, 21 Oct 2011 17:32:09 -0700

Changed in dahdi-linux (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
Adam Gandelman (gandelman-a) wrote :

Would someone who has been affected by this bug and still has the hardware available please confirm the fix in the newest upload to precise so that we may prepare an SRU for previous Ubuntu releases? Thanks.

Revision history for this message
Antonis Kanouras (akanouras) wrote :

Unfortunately I cannot test this anymore as I had to switch that machine to Debian Squeeze, which already contained this fix (among others).

Apparently, although with this fix the card is correctly initialised ("pri show spans" in the Asterisk console shows "PRI span 1/0: Provisioned, Up, Active"), it exhibits severe instability after a while (loses interrupts, etc.) leading me to believe other parts of DAHDI needed patching as well.

By all means though, do prepare an SRU, it may work on hardware configurations other than mine.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.