Home/Support/Support Forum/supported redhat 6.5 kernel level for Digi Neo PCI card
Welcome to Digi Forum, where you can ask questions and receive answers from other members of the community.

supported redhat 6.5 kernel level for Digi Neo PCI card

0 votes
Hi Userid0,

I tried to install the kernel source and kernel devel packages to match the kernel version but however i couldnt find the same version for kernel.

I managed to upgrade the kernel to the latest level and installed kernel-headers and kernel- devel. after that i was able to to compile the driver package.

now the issue is im testing the serial ports using minicom but still its not working. Is there anyway to verify the serial ports are detected. Below is the results im getting when open dev/tty

[root@smsgateway ~]# ll /sys/class/tty/
console/ tty1/ tty17/ tty24/ tty31/ tty39/ tty46/ tty53/ tty60/ tty_dgnc_0_1/
pr_dgnc_0_0/ tty10/ tty18/ tty25/ tty32/ tty4/ tty47/ tty54/ tty61/ tty_dgnc_0_2/
pr_dgnc_0_1/ tty11/ tty19/ tty26/ tty33/ tty40/ tty48/ tty55/ tty62/ tty_dgnc_0_3/
pr_dgnc_0_2/ tty12/ tty2/ tty27/ tty34/ tty41/ tty49/ tty56/ tty63/ ttyS0/
pr_dgnc_0_3/ tty13/ tty20/ tty28/ tty35/ tty42/ tty5/ tty57/ tty7/ ttyS1/
ptmx/ tty14/ tty21/ tty29/ tty36/ tty43/ tty50/ tty58/ tty8/ ttyS2/
tty/ tty15/ tty22/ tty3/ tty37/ tty44/ tty51/ tty59/ tty9/ ttyS3/
tty0/ tty16/ tty23/ tty30/ tty38/ tty45/ tty52/ tty6/ tty_dgnc_0_0/
asked Sep 22, 2015 in Serial Cards by rifdhy New to the Community (3 points)

Please log in or register to answer this question.

1 Answer

+1 vote
You should be seeing /dev/ttyn1x ports on the host (as configured by UDEV).

Make sure the jsm driver is not enabled in your new kernel:

http://knowledge.digi.com/articles/Knowledge_Base_Article/Digi-NEO-adapter-is-not-recognized-in-Linux/?q=dgnc&l=en_US&fs=Search&pn=1

Next, make sure the adapter is initialized and the ports successfully created by looking in dpa.dgnc from the root prompt:

# dpa.dgnc

Let me know the results.
answered Sep 22, 2015 by userid0 Veteran of the Digi Community (2,156 points)
Hi,

seems i cant attach the screen of the output from # dpa.dgnc

but i am not sure if its working as expected. Sorry for being a noob here.

My redhat version is as below. can you please verify if i have installed the right driver version.

Linux smsgateway 2.6.32-573.3.1.el6.x86_64 #1 SMP Thu Aug 13 22:55:16 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
Red Hat Enterprise Linux Server release 6.5 (Santiago)

output from lspci

Serial controller: Digi International Digi Neo PCI-E 4 port (rev 02)
0b:00.0

Thanks,
Rifdhy.
What do you see in /var/log/messages for dgnc?

cat /var/log/messages | grep dgnc
Hi Below are the output from /var/logs/messages

mber 40002369_G
Sep 30 11:21:48 smsgateway kernel: dgnc: For the tools package or updated driver                                             s please visit http://www.digi.com
Sep 30 11:21:48 smsgateway kernel: dgnc 0000:08:00.0: PCI INT A -> GSI 40 (level                                             , low) -> IRQ 40
Sep 30 11:21:48 smsgateway kernel: dgnc: board 0: Neo 4 PCI Express (rev 2), irq                                              40
Sep 30 11:21:48 smsgateway modem-manager: (pr_dgnc_0_0) opening serial device...
Sep 30 11:21:48 smsgateway modem-manager: (pr_dgnc_0_3) opening serial device...
Sep 30 11:21:48 smsgateway modem-manager: (pr_dgnc_0_2) opening serial device...
Sep 30 11:21:48 smsgateway modem-manager: (pr_dgnc_0_1) opening serial device...
Sep 30 11:21:48 smsgateway modem-manager: (tty_dgnc_0_0) opening serial device..                                             .
Sep 30 11:21:48 smsgateway modem-manager: (tty_dgnc_0_1) opening serial device..                                             .
Sep 30 11:21:48 smsgateway modem-manager: (tty_dgnc_0_2) opening serial device..                                             .
Sep 30 11:21:48 smsgateway modem-manager: (tty_dgnc_0_3) opening serial device..                                             .
Sep 30 11:22:01 smsgateway modem-manager: (tty_dgnc_0_0) closing serial device..                                             .
Sep 30 11:22:01 smsgateway modem-manager: (tty_dgnc_0_0) opening serial device..                                             .
Sep 30 11:22:01 smsgateway modem-manager: (tty_dgnc_0_0) failed to parse QCDM ve                                             rsion info command result: (2) DM command 0 response not long enough (got 1, exp                                             ected at least 55)..
Sep 30 11:22:01 smsgateway modem-manager: (tty_dgnc_0_0) closing serial device..                                             .
Sep 30 11:22:01 smsgateway modem-manager: (tty_dgnc_0_1) closing serial device..                                             .
Sep 30 11:22:02 smsgateway modem-manager: (tty_dgnc_0_1) opening serial device..                                             .
Sep 30 11:22:03 smsgateway modem-manager: (tty_dgnc_0_2) closing serial device..                                             .
Sep 30 11:22:03 smsgateway modem-manager: (tty_dgnc_0_2) opening serial device..                                             .
Sep 30 11:22:04 smsgateway modem-manager: (tty_dgnc_0_3) closing serial device..                                             .
Sep 30 11:22:04 smsgateway modem-manager: (tty_dgnc_0_3) opening serial device..                                             .
Sep 30 11:22:09 smsgateway modem-manager: (tty_dgnc_0_1) closing serial device..                                             .
Sep 30 11:22:10 smsgateway modem-manager: (tty_dgnc_0_2) closing serial device..                                             .
Sep 30 11:22:11 smsgateway modem-manager: (tty_dgnc_0_3) closing serial device..                                             .
[root@smsgateway ~]#

We managed to find out the problem. Its not an issue with the driver and the card is working but the problem was we have been testing with the secondary card.

we have two digi cards on the server but only one is detected. Below is the output from lspci

04:00.3 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01)
06:00.0 RAID bus controller: LSI Logic / Symbios Logic MegaRAID SAS 2208 [Thunderbolt] (rev 05)
07:00.0 PCI bridge: PLX Technology, Inc. PEX8112 x1 Lane PCI Express-to-PCI Bridge (rev aa)
08:00.0 Serial controller: Digi International Digi Neo PCI-E 4 port (rev 02)
0b:00.0 VGA compatible controller: Matrox Electronics Systems Ltd. MGA G200e [Pilot] ServerEngines (SEP1) (rev 02)
ff:08.0 System peripheral: Intel Corporation Xeon E5 v2/Core i7 QPI Link 0 (rev 04)
ff:09.0 System peripheral: Intel Corporation Xeon E5 v2/Core i7 QPI Link 1 (rev 04)

any idea why this is not detected?

Thanks,
Rifdhy.
Have you tried another adapter slot in the host to see if the adapter is recognized?

If this does not work, is the adapter recognized if put in the same slot as the working adapter?

Typically, the inability to see the hardware points to a bad PCI(e) slot, BIOS resource issue, or a bad adapter.  By switching around to differenct slots, including a known working slot, you should be able to narrow in on the problem.
...