When will realport be supported on Ubuntu Trusty 14.04

The latest driver should work on this distibution version:

http://ftp1.digi.com/support/driver/40002086_U.src.rpm

Installation instructions:

http://www.digi.com/support/kbase/kbaseresultdetl?id=3125

Hope this helps.

3.13.0-34-generic
40002086_U.src.rpm

Doesnt seem to work Im afraid. Struggling cutting and pasting from a VM.
Following instructions here
http://www.digi.com/support/kbase/kbaseresultdetl?id=3125

Tia
JD

In file included from include/linux/sched.h:52:0,
from /root/rpmbuild/BUILD/dgrp-1.9/driver/build/dgrp_common.c:57:
include/linux/cred.h:77:12: note: expected ‘kgid_t’ but argument is of type ‘gid_t’
extern int in_egroup_p(kgid_t);
^
/root/rpmbuild/BUILD/dgrp-1.9/driver/build/dgrp_common.c:638:1: warning: control reaches end of non-void function [-Wreturn-type]
}
^
make[3]: *** [/root/rpmbuild/BUILD/dgrp-1.9/driver/build/dgrp_common.o] Error 1
make[2]: *** [module/root/rpmbuild/BUILD/dgrp-1.9/driver/build] Error 2
make[2]: Leaving directory /usr/src/linux-headers-3.13.0-34-generic' make[1]: *** [build] Error 2 make[1]: Leaving directory /root/rpmbuild/BUILD/dgrp-1.9/driver/2.6.27’
make: *** [build] Error 2
error: Bad exit status from /var/tmp/rpm-tmp.5lKxPv (%build)

RPM build errors:
Bad exit status from /var/tmp/rpm-tmp.5lKxPv (%build)
root@ubuntu:~#

Tried exactly same procedure on 12.04 64 bit and worked fine.

There is not enough information, can you post the entire build results leading up to the error?

I had the same error

I had also perform the same procedure on 12.04 which is the Precise Pangoline and there was no error

I even tried using docker where docker host is trusty but the docker container is precise and it is definitely not building which is much predicted.

I have been able to replicate this. It has been written up for Digi’s Engineering team.

Can you contact Digi Tech. Support in order to get a case set up for this? This might help to expedite a fix:

Eservice Support: http://mydigi.force.com/customers
Email: tech.support@digi.com

Can you contact Digi Tech. Support in order to get a case set up for this? This might help to expedite a fix:

Eservice Support: http://mydigi.force.com/customers
Email: tech.support@digi.com

Having the same problems on red hat 7

[root@wp1 dgrp-1.9]# ./configure
checking for Digi Driver package version… 1.9-33 built on 04/17/2014
checking for awk… /usr/bin/awk
checking for arch… /usr/bin/arch
checking for cat… /usr/bin/cat
checking for cd… /usr/bin/cd
checking for chkconfig… /usr/sbin/chkconfig
checking for chmod… /usr/bin/chmod
checking for chown… /usr/bin/chown
checking for cp… /usr/bin/cp
checking for depmod… /usr/sbin/depmod
checking for echo… /usr/bin/echo
checking for fuser… /usr/sbin/fuser
checking for grep… /usr/bin/grep
checking for init… /usr/sbin/init
checking for insmod… /usr/sbin/insmod
checking for kill… /usr/bin/kill
checking for ln… /usr/bin/ln
checking for ls… /usr/bin/ls
checking for lsmod… /usr/sbin/lsmod
checking for make… /usr/bin/make
checking for mkdir… /usr/bin/mkdir
checking for mknod… /usr/bin/mknod
checking for more… /usr/bin/more
checking for mv… /usr/bin/mv
checking for ps… /usr/bin/ps
checking for rm… /usr/bin/rm
checking for rmdir… /usr/bin/rmdir
checking for rmmod… /usr/sbin/rmmod
checking for sed… /usr/bin/sed
checking for sleep… /usr/bin/sleep
checking for stty… /usr/bin/stty
checking for tar… /usr/bin/tar
checking for tr… /usr/bin/tr
checking for touch… /usr/bin/touch
checking for true… /usr/bin/true
checking for udevadm… /usr/sbin/udevadm
checking for udevcontrol… Not Found
checking for udevd… Not Found
checking for udevinfo… Not Found
checking for uname… /usr/bin/uname
checking for platform type… x86_64
checking for gcc… gcc
checking for gcc version… >= 3.2 (4.8.2)
checking for gcc… gcc
checking for C compiler default output file name… a.out
checking whether the C compiler works… yes
checking whether we are cross compiling… no
checking for suffix of executables…
checking for suffix of object files… o
checking whether we are using the GNU C compiler… yes
checking whether gcc accepts -g… yes
checking for gcc option to accept ISO C89… none needed
checking for current kernel version… 3.10.0-123.4.4.el7.x86_64 -> 3.10.0-123.4.4.7.86_64 -> 3.10.0
checking for kernel headers… “/lib/modules/3.10.0-123.4.4.el7.x86_64/build”
checking extra version of kernel… -123.4.4.el7.x86_64
checking if running kernel was compiled for SMP… Yes
checking what type of build we will do… KBUILD.
checking for modules directory… “/lib/modules/3.10.0-123.4.4.el7.x86_64”
checking OpenSSL header version… 1000105f (OpenSSL 1.0.1e 11 Feb 2013)
checking OpenSSL library version… 1000105f (OpenSSL 1.0.1e-fips 11 Feb 2013)
checking whether OpenSSL’s headers match the library… yes
checking whether your OpenSSL version is current enough… yes
configure: checking for tgetent…
configure: checking for libncurses…
checking if Distro specified… None
checking if New TTY Locking was specified… No - Defaulting to a value of “No”
checking if New TTY Buffering was specified… No - Defaulting to a value of “No”
checking if UDEV checking is overridden… No
checking if UDEV exists… No
configure: creating ./config.status
config.status: creating Makefile
config.status: creating driver/build/Makefile
config.status: creating daemon/Makefile
config.status: creating ditty/Makefile
config.status: creating config/Makefile
config.status: creating dparp/os/Makefile.Linux
config.status: creating dgipserv/Makefile.linux
config.status: creating dgelreset/Makefile.linux
config.status: creating init/dgrp_udev
config.status: creating init/Makefile
config.status: creating commoninc/config.h
config.status: commoninc/config.h is unchanged
config.status: executing default commands
[root@wp1 dgrp-1.9]# make
(cd driver/build; make all)
make[1]: Entering directory /root/digi2/dgrp-1.9/driver/2.6.27' make -C /lib/modules/3.10.0-123.4.4.el7.x86_64/build SUBDIRS=$PWD modules MYPWD=/root/digi2/dgrp-1.9/driver/2.6.27 MYMANDIR=/share/man make[2]: Entering directory /usr/src/kernels/3.10.0-123.4.4.el7.x86_64’
CC [M] /root/digi2/dgrp-1.9/driver/build/dgrp_common.o
/root/digi2/dgrp-1.9/driver/build/dgrp_common.c: In function ‘dgrp_in_egroup_p’:
/root/digi2/dgrp-1.9/driver/build/dgrp_common.c:637:2: error: incompatible type for argument 1 of ‘in_egroup_p’
return in_egroup_p(grp);
^
In file included from include/linux/sched.h:51:0,
from /root/digi2/dgrp-1.9/driver/build/dgrp_common.c:57:
include/linux/cred.h:77:12: note: expected ‘kgid_t’ but argument is of type ‘gid_t’
extern int in_egroup_p(kgid_t);
^
/root/digi2/dgrp-1.9/driver/build/dgrp_common.c:638:1: warning: control reaches end of non-void function [-Wreturn-type]
}
^
make[3]: *** [/root/digi2/dgrp-1.9/driver/build/dgrp_common.o] Error 1
make[2]: *** [module/root/digi2/dgrp-1.9/driver/build] Error 2
make[2]: Leaving directory /usr/src/kernels/3.10.0-123.4.4.el7.x86_64' make[1]: *** [build] Error 2 make[1]: Leaving directory /root/digi2/dgrp-1.9/driver/2.6.27’
make: *** [build] Error 2
[root@wp1 dgrp-1.9]# uname -r
3.10.0-123.4.4.el7.x86_64
[root@wp1 dgrp-1.9]# cat /etc/redhat-release
Red Hat Enterprise Linux Server release 7.0 (Maipo)
[root@wp1 dgrp-1.9]#

This error is due to a kernel change: https://lkml.org/lkml/2012/4/8/32

For the Ubuntu kernel, this change occurred sometime in the 3.12.x kernel, I found that the driver compiles in 3.11.x kernels if you want to back-rev. For Red Hat 7 and CentOS 7, I have not been able to test granular kernels. I am asking that this be reported to Digi Tech. Support as it makes a larger case/priority for Digi Engineering to accommodate the kernel change in the driver.

Thank you for the update. From what I have heard from Digi is that the Engineering team has a priority ticket open to fix this issue. But we may try fixing the code or back-reving the kernels. Don’t know either or is a great solution to the issues but may allow us to continue to move forward for testing while digi fixes their stuff. Thanks

FYI: There is now a beta driver build available from Digi.

Where? I couldn’t find it on FTP server? May you provide file name?

Thanks

The driver has been released to Digi’s support site:

http://www.digi.com/support/productdetail?pid=2247&type=drivers