digi dgap drivers issue
From: Captain Dondo (yan_at_NsOeSiPnAeMr.com)
Date: 01/23/05
- Previous message: Henrik Carlqvist: "Re: second display won't work"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sun, 23 Jan 2005 11:14:29 -0800
I have a Digi Acceleport 920 2r card. I got the latest drivers from digi,
compiled everything, and all seems to compile and install correctly.
I can bring up the digi monitoring utility, and see RTS/CTS/DSR/DCD/DTR
turn on and off as connections are made.
But absolutely no information flows. I've tried this with two different
cables, with all sorts of baud rates, etc. and I get absolutely nothing.
I even tried a loopback between the two ports on the card, using a
null-modem cable, no dice.
The card should be OK; it worked fine when it was pulled from the old
machine, so I have no idea why it doesn't work. Unfortunately the old
machine is gone, so I can't re-test the card.
I remember on my last go around with digi drivers that they can be
finicky, so I'm looking for advice or suggestions.
Any settings I have to make with ditty? Any tests I can run to see if the
card works?
I'm running FC2 with a vanilla 2.6.10 driver. I even tried the kernel
epca driver; it loads but I don't have any of the other utilities
(digiDload, etc.) so I can't test any further.
The only indication that something may be wrong is if I enable interrupts
- I get this in my logs:
an 23 10:42:07 tooth kernel: dgap: dgap-1.1-1, Digi International Part Number 40002347_A
Jan 23 10:42:07 tooth kernel: dgap: For the tools package or updated drivers please visit http://www.digi.com
Jan 23 10:42:07 tooth kernel: dgap: board 0: AccelePort Xr920 2 port (rev 1), irq 9
Jan 23 10:42:07 tooth kernel: Debug: sleeping function called from invalid context at mm/slab.c:2055
Jan 23 10:42:07 tooth kernel: in_atomic():1, irqs_disabled():1
Jan 23 10:42:07 tooth kernel: [<c0118106>] __might_sleep+0xb6/0xe0
Jan 23 10:42:07 tooth kernel: [<c013ffea>] __kmalloc+0x8a/0xa0
Jan 23 10:42:07 tooth kernel: [<c0186bb2>] proc_create+0x72/0xd0
Jan 23 10:42:07 tooth kernel: [<c0186cd6>] proc_mkdir_mode+0x26/0x60
Jan 23 10:42:07 tooth kernel: [<c0136d3e>] register_handler_proc+0xae/0xc0
Jan 23 10:42:07 tooth kernel: [<c013660d>] setup_irq+0xcd/0x120
Jan 23 10:42:07 tooth kernel: [<c8b79970>] dgap_intr+0x0/0x80 [dgap]
Jan 23 10:42:07 tooth kernel: [<c01367c4>] request_irq+0x74/0x90
Jan 23 10:42:07 tooth kernel: [<c8b79903>] dgap_finalize_board_init+0x73/0xe0 [dgap]
Jan 23 10:42:07 tooth kernel: [<c8b7a2e4>] dgap_mgmt_ioctl+0x544/0xf20 [dgap]
Jan 23 10:42:07 tooth kernel: [<c0138104>] __generic_file_aio_read+0x1e4/0x220
Jan 23 10:42:07 tooth kernel: [<c0137e30>] file_read_actor+0x0/0xf0
Jan 23 10:42:07 tooth kernel: [<c0138187>] generic_file_aio_read+0x47/0x70
Jan 23 10:42:07 tooth kernel: [<c0153fea>] do_sync_read+0x9a/0xd0
Jan 23 10:42:07 tooth kernel: [<c0115124>] do_page_fault+0x3a4/0x5ac
Jan 23 10:42:07 tooth kernel: [<c01470d0>] vma_link+0x50/0x100
Jan 23 10:42:08 tooth kernel: [<c012d890>] autoremove_wake_function+0x0/0x50
Jan 23 10:42:08 tooth kernel: [<c012d890>] autoremove_wake_function+0x0/0x50
Jan 23 10:42:08 tooth kernel: [<c016a8d5>] dput+0x25/0x220
Jan 23 10:42:08 tooth kernel: [<c0165e04>] sys_ioctl+0xd4/0x210
Jan 23 10:42:08 tooth kernel: [<c01538cf>] filp_close+0x4f/0x80
Jan 23 10:42:08 tooth kernel: [<c0102f69>] sysenter_past_esp+0x52/0x75
- Previous message: Henrik Carlqvist: "Re: second display won't work"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|