Armin Schindler wrote:
This is some bad behaviour of the Config wizard.
You should then start with
sh# /usr/lib/divas/divas_stop.rc
to clean all of it. And then really start the
divas:
sh# /usr/lib/divas/divas_cfg.rc
seems to work, thanks.
Is there a utility which shows the status of the ISDN port (layer 2
link, layer 3 link, ...)
regards
klaus
Armin
On Tue, 16 May 2006, Klaus Darilion wrote:
Hi Armin!
After make install I'm able to run the config script. I configured all 4 ports
of the card and saved the configuration.
After that:
...
Load Diva XDI driver ... OK
Check for saved MAINT debug/trace buffer ... idle
Write Diva configuration to CFGLib ... succeeded
Check Diva configuration ... succeeded, adapter not loaded
Here, "adapter not loaded" frightens me.
Nevertheless I tried to activate the config:
# /usr/lib/divas/divas_cfg.rc
Update CFGLib information ... failed
-------------------------------------------------------------------------------
DIVA CONFIGURATION: CFGLib DRIVER LOAD FAILED
PLEASE CHECK SYSTEM INSTALLATION
(kernel version, missing files)
-------------------------------------------------------------------------------
DIVAS4LINUX SHUTDOWN OK.
regards
klaus
Armin Schindler wrote:
Hi Klaus,
what happens when you try to load the DIDD module
sh# insmod /usr/lib/divas/divadidd.o
and what is the kernel (syslog) saying?
Armin
On Tue, 16 May 2006, Klaus Darilion wrote:
Hi Armin!
With the new v3 package compilation works fine. But I still have
problems when
starting the config script:
'DIDD' driver load failed. Please check system installation
(kernel version, missing files)
Do I have to load any modules before? The Eicon Card is found by
lspci:
0000:0a:03.0 Network controller: Eicon Networks Corporation Diva
Server
4BRI-8M Rev 2 (rev 01)
Subsystem: Eicon Networks Corporation Diva Server 4BRI-8M Rev 2
Flags: bus master, medium devsel, latency 32, IRQ 77
Memory at fdeffc00 (32-bit, non-prefetchable) [size=256]
I/O ports at cc00 [size=256]
Memory at fc000000 (32-bit, non-prefetchable) [size=16M]
Memory at fdee0000 (32-bit, non-prefetchable) [size=64K]
Capabilities: [40] Power Management version 1
Capabilities: [48] #06 [0080]
Capabilities: [4c] Vital Product Data
regards
klaus
Armin Schindler wrote:
On Tue, 16 May 2006, Klaus Darilion wrote:
Tzafrir Cohen wrote:
On Tue, May 16, 2006 at 11:05:01AM +0200, Klaus Darilion
wrote:
Armin Schindler wrote:
On Tue, 16 May 2006, Klaus Darilion wrote:
Hi Armin!
I now tried 2 versions:
A) I also executed "make prepare" in the
kernel
sources
before building with
"make KDIR=/usr/src/kernel-source-2.6.8"
B) I compiled with the kernel headers:
"make KDIR=/lib/modules/2.6.8-2-386/build/"
Both times I got the same error message (see
below).
It would
be great if you
can take a look at it because this Asterisk
server
should go
in production
today.
What kernel is that? When I use the plain kernel
2.6.8
from
kernel.org I don't even get any warning.
Either the kernel headers are incomplete or this
distribution
kernel is incompatible in some way. Can you
provide a tgz
of
these sources(headers) directory to me?
I think I found the problem:
"make KDIR=/lib/modules/2.6.8-2-386/build/" fails as
/lib/modules/2.6.8-2-386/build/ links to
/usr/src/kernel-headers-2.6.8-2-386
Wheres when setting KDIR to
/usr/src/kernel-headers-2.6.8-2
(note:
note adding the -386) then the compilation works
fine.
Maybe we need a Debian expert: What is the difference
between
kernel-headers-2.6.8-2 and kernel-headers-2.6.8-2-386
???
Does the compiled 2.6.8-2 works with my 2.6.8-2-386
kernel?
kernel-headers-2.6.8-2 is a large
architecture-independent
package that
contains most of what is needed from the kernel source to
build
external
modules and such.
2.6.8-2-386 , -686, -686-smp, and all others contain the
little
configuration-specific files .
/usr/src/kernel-headers-2.6.8-2-386 has
many symlinks to files under
/usr/src/kernel-headers-2.6.8-2 .
/usr/src/kernel-headers-2.6.8-2 in itself does not
contain a
"configured
source" or even a .config file.
It does:
ll /usr/src/kernel-headers-2.6.8-2/.config
-rw-r--r-- 1 root root 27535 2005-08-16 17:12
/usr/src/kernel-headers-2.6.8-2/.config
The question is: can it be used to build modules for
2.6.8-2-386 ?
I don't think so. It contains a different .config, which might
not be
compatible with the running kernel.
I have made a few fixes to build with the debian header packages.
The new
package (3.0.f) will be available for download in about 30
Minutes.
I have tested build with
make KDIR=/usr/src/kernel-headers-2.4.27-2-386
and
make KDIR=/usr/src/kernel-headers-2.6.8-2-386
Armin
_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --
Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --
Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --
Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --
Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --
Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --
Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
