nur FM bei BRI-STUFF Install - Projekt Voicemail-Anbindg.m.*

teletreff

Neuer User
Mitglied seit
25 Jul 2004
Beiträge
20
Punkte für Reaktionen
0
Punkte
1
Hallo VoIP-Freaks,

hat jemand Lust etwas zusammen an Asterisk+HFC-ISDN zu arbeiten?
Habe vor über hierüber mein Voicemailsystem über weitere SIP-Rufnummern
anzubinden, da ich jetzt im Urlaub etwas Zeit habe.

Jedoch bin ich mit Linux und vor allem der Installation von ZAP-HFC nicht
erfahren - bringt nur FM bei der Installation auf SuSE Linux 9.0 , 2.4er
Kernel bei Installation via install.sh von der aktuellen bri-stuff-Version.

Freue mich von Euch zu hören

Via fon 089-61 50 1009
SIPgate: 0211-58 00 5997

hier ein paar Infos. Andere bitte erfragen.

- SuSE Linux 9.0 (i586)
Kernel 2.4.21-231-default / i686

- AVM Fritz! PnP (ISA)+ Capi 2.0 Treiber
- AVM Fritz! PCI (wird noch eingebaut)+CAPI 2.0 Treiber
- ACER Surf 128PCI mit HFC-S Chipsatz (wird als HFC 2BDS0 erkannt) - nur
HiSax-Treiber möglich
Laden in /var/log/boot.msg ist ok:

Setting up ISDN card contr0 AVM FRITZ!Card PnPdone
contr1 CC HFC 2BDS0done
Loading Driver contr0 1 kcapi capi capidrvdone
Initializing capi for contr0 (1)done
Loading Driver contr1 hisaxdone


- bri-stuff.0.1.0-RC2

bringt beim starten via ./install.sh im Verzeichnis
/usr/src/bri-stuff.0.1.0-RC2/
nur FM:
Code:
config, and run"
/usr/src/linux/include/linux/version.h:11:2: #error "'make oldconfig && make
dep' to configure the kernel"
/usr/src/linux/include/linux/version.h:12:2: #error "for that
configuration."
In file included from /usr/src/linux/include/linux/poll.h:11,
                 from zaptel.h:856,
                 from zaptel.c:82:
/usr/include/asm/uaccess.h: At top level:
/usr/include/asm/uaccess.h:102: error: parse error before '*' token
/usr/include/asm/uaccess.h: In function `verify_area':
/usr/include/asm/uaccess.h:104: error: `addr' undeclared (first use in this
function)
/usr/include/asm/uaccess.h:104: error: `size' undeclared (first use in this
function)
/usr/include/asm/uaccess.h: At top level:
/usr/include/asm/uaccess.h:374: error: parse error before '*' token
/usr/include/asm/uaccess.h:375: error: parse error before '*' token
/usr/include/asm/uaccess.h:399: error: parse error before '*' token
/usr/include/asm/uaccess.h: In function `__copy_to_user':
/usr/include/asm/uaccess.h:401: error: `n' undeclared (first use in this
function)
/usr/include/asm/uaccess.h:406: error: `to' undeclared (first use in this
function)
/usr/include/asm/uaccess.h:406: error: `from' undeclared (first use in this
function)
/usr/include/asm/uaccess.h: At top level:
/usr/include/asm/uaccess.h:437: error: parse error before '*' token
/usr/include/asm/uaccess.h: In function `__copy_from_user':
/usr/include/asm/uaccess.h:439: error: `n' undeclared (first use in this
function)
/usr/include/asm/uaccess.h:444: error: `to' undeclared (first use in this
function)
/usr/include/asm/uaccess.h:444: error: `from' undeclared (first use in this
function)
/usr/include/asm/uaccess.h: At top level:
/usr/include/asm/uaccess.h:471: error: parse error before '*' token
/usr/include/asm/uaccess.h: In function `copy_to_user':
/usr/include/asm/uaccess.h:474: error: `to' undeclared (first use in this
function)
/usr/include/asm/uaccess.h:474: error: `n' undeclared (first use in this
function)
/usr/include/asm/uaccess.h:475: error: `from' undeclared (first use in this
function)
/usr/include/asm/uaccess.h: At top level:
/usr/include/asm/uaccess.h:496: error: parse error before '*' token
/usr/include/asm/uaccess.h: In function `copy_from_user':
/usr/include/asm/uaccess.h:499: error: `from' undeclared (first use in this
function)
/usr/include/asm/uaccess.h:499: error: `n' undeclared (first use in this
function)
/usr/include/asm/uaccess.h:500: error: `to' undeclared (first use in this
function)
/usr/include/asm/uaccess.h: At top level:
/usr/include/asm/uaccess.h:506: error: parse error before '*' token
/usr/include/asm/uaccess.h:507: error: parse error before '*' token
/usr/include/asm/uaccess.h:525: error: parse error before '*' token
/usr/include/asm/uaccess.h:526: error: parse error before '*' token
/usr/include/asm/uaccess.h:527: error: parse error before '*' token
In file included from zaptel.c:82:
zaptel.h:1421:41: missing binary operator before token "("
zaptel.c:110: error: parse error before
"config_must_be_included_before_module"
zaptel.c:110: warning: type defaults to `int' in declaration of
`config_must_be_included_before_module'
zaptel.c:110: warning: data definition has no type or storage class
zaptel.c:111: error: parse error before
"config_must_be_included_before_module"
zaptel.c:111: warning: type defaults to `int' in declaration of
`config_must_be_included_before_module'
zaptel.c:111: warning: data definition has no type or storage class
zaptel.c:112: error: parse error before
"config_must_be_included_before_module"
zaptel.c:112: warning: type defaults to `int' in declaration of
`config_must_be_included_before_module'
zaptel.c:112: warning: data definition has no type or storage class
zaptel.c:113: error: parse error before
"config_must_be_included_before_module"
zaptel.c:113: warning: type defaults to `int' in declaration of
`config_must_be_included_before_module'
zaptel.c:113: warning: data definition has no type or storage class
zaptel.c:114: error: parse error before
"config_must_be_included_before_module"
zaptel.c:114: warning: type defaults to `int' in declaration of
`config_must_be_included_before_module'
zaptel.c:114: warning: data definition has no type or storage class
zaptel.c:115: error: parse error before
"config_must_be_included_before_module"
zaptel.c:115: warning: type defaults to `int' in declaration of
`config_must_be_included_before_module'
zaptel.c:115: warning: data definition has no type or storage class
zaptel.c:120: error: parse error before
"config_must_be_included_before_module"
zaptel.c:120: warning: type defaults to `int' in declaration of
`config_must_be_included_before_module'
zaptel.c:120: warning: data definition has no type or storage class
zaptel.c:121: error: parse error before
"config_must_be_included_before_module"
zaptel.c:121: warning: type defaults to `int' in declaration of
`config_must_be_included_before_module'
zaptel.c:121: warning: data definition has no type or storage class
zaptel.c:123: error: parse error before
"config_must_be_included_before_module"
zaptel.c:123: warning: type defaults to `int' in declaration of
`config_must_be_included_before_module'
zaptel.c:123: warning: data definition has no type or storage class
zaptel.c:124: error: parse error before
"config_must_be_included_before_module"
zaptel.c:124: warning: type defaults to `int' in declaration of
`config_must_be_included_before_module'
zaptel.c:124: warning: data definition has no type or storage class
zaptel.c:125: error: parse error before
"config_must_be_included_before_module"
zaptel.c:125: warning: type defaults to `int' in declaration of
`config_must_be_included_before_module'
zaptel.c:125: warning: data definition has no type or storage class
zaptel.c:126: error: parse error before
"config_must_be_included_before_module"
zaptel.c:126: warning: type defaults to `int' in declaration of
`config_must_be_included_before_module'
zaptel.c:126: warning: data definition has no type or storage class
zaptel.c:127: error: parse error before
"config_must_be_included_before_module"
zaptel.c:127: warning: type defaults to `int' in declaration of
`config_must_be_included_before_module'
zaptel.c:127: warning: data definition has no type or storage class
zaptel.c:128: error: parse error before
"config_must_be_included_before_module"
zaptel.c:128: warning: type defaults to `int' in declaration of
`config_must_be_included_before_module'
zaptel.c:128: warning: data definition has no type or storage class
zaptel.c:129: error: parse error before
"config_must_be_included_before_module"
zaptel.c:129: warning: type defaults to `int' in declaration of
`config_must_be_included_before_module'
zaptel.c:129: warning: data definition has no type or storage class
zaptel.c:130: error: parse error before
"config_must_be_included_before_module"
zaptel.c:130: warning: type defaults to `int' in declaration of
`config_must_be_included_before_module'
zaptel.c:130: warning: data definition has no type or storage class
zaptel.c:131: error: parse error before
"config_must_be_included_before_module"
zaptel.c:131: warning: type defaults to `int' in declaration of
`config_must_be_included_before_module'
zaptel.c:131: warning: data definition has no type or storage class
zaptel.c:132: error: parse error before
"config_must_be_included_before_module"
zaptel.c:132: warning: type defaults to `int' in declaration of
`config_must_be_included_before_module'
zaptel.c:132: warning: data definition has no type or storage class
zaptel.c: In function `zt_qevent_lock':
zaptel.c:650: error: parse error before "unsigned"
zaptel.c: In function `zt_reallocbufs':
zaptel.c:746: error: parse error before "unsigned"
zaptel.c: In function `close_channel':
zaptel.c:936: error: parse error before "unsigned"
zaptel.c: In function `zt_chan_reg':
zaptel.c:1143: error: parse error before "unsigned"
zaptel.c: In function `zt_chan_unreg':
zaptel.c:1518: error: parse error before "unsigned"
zaptel.c: In function `zt_chan_read':
zaptel.c:1537: error: parse error before "unsigned"
zaptel.c:1543: error: parse error before "unsigned"
zaptel.c:1596: error: parse error before "unsigned"
zaptel.c: In function `zt_chan_write':
zaptel.c:1621: error: parse error before "unsigned"
zaptel.c:1625: error: parse error before "unsigned"
zaptel.c:1691: error: parse error before "unsigned"
zaptel.c: In function `initialize_channel':
zaptel.c:2018: error: parse error before "unsigned"
zaptel.c: In function `zt_timing_open':
zaptel.c:2044: error: parse error before "unsigned"
zaptel.c: In function `zt_timer_release':
zaptel.c:2069: error: parse error before "unsigned"
zaptel.c: In function `zt_release':
zaptel.c:2503: error: parse error before "unsigned"
zaptel.c: In function `zt_timer_ioctl':
zaptel.c:2563: error: parse error before "unsigned"
zaptel.c:2571: error: parse error before "unsigned"
zaptel.c:2581: error: parse error before "unsigned"
zaptel.c:2588: error: parse error before "unsigned"
zaptel.c:2593: error: parse error before "unsigned"
zaptel.c: In function `zt_common_ioctl':
zaptel.c:2794: error: parse error before "unsigned"
zaptel.c: In function `zt_ctl_ioctl':
zaptel.c:2915: error: parse error before "unsigned"
zaptel.c:2962: error: parse error before "unsigned"
zaptel.c:3066: error: parse error before "unsigned"
zaptel.c:3079: error: parse error before "unsigned"
zaptel.c:3106: error: parse error before "unsigned"
zaptel.c:3170: error: parse error before "unsigned"
zaptel.c:3178: error: parse error before "unsigned"
zaptel.c:3188: error: parse error before "unsigned"
zaptel.c: In function `zt_chanandpseudo_ioctl':
zaptel.c:3223: error: parse error before "unsigned"
zaptel.c:3262: error: parse error before "unsigned"
zaptel.c:3341: error: parse error before "unsigned"
zaptel.c:3349: error: parse error before "unsigned"
zaptel.c:3391: error: parse error before "unsigned"
zaptel.c:3418: error: parse error before "unsigned"
zaptel.c:3426: error: parse error before "unsigned"
zaptel.c:3438: error: parse error before "unsigned"
zaptel.c:3446: error: parse error before "unsigned"
zaptel.c:3453: error: parse error before "unsigned"
zaptel.c:3495: error: parse error before "unsigned"
zaptel.c:3496: error: parse error before "unsigned"
zaptel.c:3518: error: parse error before "unsigned"
zaptel.c:3519: error: parse error before "unsigned"
zaptel.c:3538: error: parse error before "unsigned"
zaptel.c:3539: error: parse error before "unsigned"
zaptel.c:3589: error: parse error before "unsigned"
zaptel.c:3590: error: parse error before "unsigned"
zaptel.c: In function `zt_chan_ioctl':
zaptel.c:3724: error: parse error before "unsigned"
zaptel.c:3753: error: parse error before "unsigned"
zaptel.c:3871: error: parse error before "unsigned"
zaptel.c:3882: error: parse error before "unsigned"
zaptel.c:3923: error: parse error before "unsigned"
zaptel.c:3929: error: parse error before "unsigned"
zaptel.c:3933: error: parse error before "unsigned"
zaptel.c:3939: error: parse error before "unsigned"
zaptel.c:3949: error: parse error before "unsigned"
zaptel.c:3961: error: parse error before "unsigned"
zaptel.c:3965: error: parse error before "unsigned"
zaptel.c:3974: error: parse error before "unsigned"
zaptel.c:3978: error: parse error before "unsigned"
zaptel.c:3987: error: parse error before "unsigned"
zaptel.c: In function `zt_hooksig':
zaptel.c:4970: error: parse error before "unsigned"
zaptel.c: In function `zt_rbsbits':
zaptel.c:5024: error: parse error before "unsigned"
zaptel.c: In function `zt_ec_chunk':
zaptel.c:5075: error: parse error before "unsigned"
zaptel.c: In function `process_timers':
zaptel.c:5618: error: parse error before "unsigned"
zaptel.c: In function `zt_timer_poll':
zaptel.c:5631: error: parse error before "unsigned"
zaptel.c: In function `zt_chan_poll':
zaptel.c:5663: error: parse error before "unsigned"
u.s.w.

Bin für jeden Tipp dankbar

wer sich herausgefordert sieht kann sich gerne auch telefonisch melden.

Via fon 089-61 50 1009
SIPgate: 0211-58 00 5997

Rufe auch gerne zurück!

Gruß
 

teletreff

Neuer User
Mitglied seit
25 Jul 2004
Beiträge
20
Punkte für Reaktionen
0
Punkte
1
lsmod - Ausgabe

Hier noch die Ausgabe von lsmod

mit SuSeLinux9.0 Kernel: 2.4.21-231-default
Code:
Module                  Size  Used by    Tainted: P
usbserial              19580   0  (autoclean) (unused)
lp                      6208   0  (autoclean)
parport                22888   0  (autoclean) [lp]
ipv6                  210016  -1  (autoclean)
key                    63256   0  (autoclean) [ipv6]
keybdev                 1996   0  (unused)
mousedev                4084   0  (unused)
joydev                  5120   0  (unused)
evdev                   3584   0  (unused)
input                   3360   0  [keybdev mousedev joydev evdev]
usb-uhci               22224   0  (unused)
usbcore                58668   1  [usbserial usb-uhci]
raw1394                16592   0  (unused)
ieee1394              183364   0  [raw1394]
sundance               13248   1
mii                     2320   0  [sundance]
hisax                 466832   1
fcpnp                 527520   2
isa-pnp                30664   0  [hisax fcpnp]
capidrv                25684   3
isdn                  125260   4  [hisax capidrv]
slhc                    4880   0  [isdn]
capi                   16384   0
capifs                  3600   1  [capi]
kernelcapi             29472   4  [fcpnp capidrv capi]
capiutil               22656   0  [capidrv kernelcapi]
lvm-mod                63044   0  (autoclean)
dm-mod                 42096   0  (unused)
reiserfs              199636   1
pdc-ultra              64256   0  (unused)
sd_mod                 12288   0  (unused)
scsi_mod               97524   2  [pdc-ultra sd_mod]
 

teletreff

Neuer User
Mitglied seit
25 Jul 2004
Beiträge
20
Punkte für Reaktionen
0
Punkte
1
Hups hier ist die richtige Nummer (die andere war noch im Display - war von
meinem Freund :)
Meine SIPgate Rufnummer: 0911-30 83 88 78

Viele Grüße

Ralf
 

rajo

Admin-Team
Mitglied seit
31 Mrz 2004
Beiträge
1,958
Punkte für Reaktionen
0
Punkte
36
Eieiei....

Bub... es iss zwar schee, dass De die ganze Debugg-Meldunge do poschdeschd, awwa mach sowas es negschde mohl midd dem "code" Knöbbsche do... :)
Dat kann ma vieeel besser lese...

(und es gibt ne "edit" Funktion für die Beiträge ;) )


So, nun aber zurück zum Thema:

Eigentlich müsstes Du die Fehlermeldungen nur lesen ;)
/usr/src/linux/include/linux/version.h:11:2: #error "'make oldconfig && make dep' to configure the kernel"

- cd /usr/src/linux
- Dort schauen, ob eine passende .config zu Deinem aktuell verwendeten Kern auffindbar ist (ggf. kann die bei Suse auch in /boot/config-irgendwas herumliegen, dann eben die von /boot/ nach /usr/src/linux/.config kopieren
- Dann make oldconfig && make dep ausführen, wie die Fehlermeldung schon sagt


...und dann klappt das auch mit dem install.sh :)
 

teletreff

Neuer User
Mitglied seit
25 Jul 2004
Beiträge
20
Punkte für Reaktionen
0
Punkte
1
Danke erst mal für die Aufkärung mit der Code-Einblendung - ach daher kommt das elegante Code-Scroll-Fenter :)

Nun bin leider noch nicht so erfahren - kannst Du mir da die einzelnen Schritte kurz schreiben?

Finde keine .config bei ls im Verzeichnis /usr/src/linux

Mercy

Ralf aus MUC
 

teletreff

Neuer User
Mitglied seit
25 Jul 2004
Beiträge
20
Punkte für Reaktionen
0
Punkte
1
Hab schon weitergelesen- in boot war er - läuft gerade..


Code:
host2:/boot # ls
.                              initrd
..                             initrd-2.4.21-231-default
Kerntypes-2.4.21-231-default   memtest.bin
System.map-2.4.21-231-default  message
backup_mbr                     vmlinux-2.4.21-231-default.gz
boot                           vmlinuz
config-2.4.21-231-default      vmlinuz-2.4.21-231-default
grub

Dann schau´n ma mal

Gruß

Ralf
 

teletreff

Neuer User
Mitglied seit
25 Jul 2004
Beiträge
20
Punkte für Reaktionen
0
Punkte
1
./Install.sh läuft noch - schaut gut aus - ZAP-HFC ist schon mal ohne Error
Installiert, auch LIBPRI aber nun kamen wieder FM bei quadPRI (habe keine eingebaut, da mit ZAP-HFC) sind die FM dann normal?

Gruß

Ralf

Fehler :

Code:
****************************************************
LIBPRI installed.
Press <Enter> to continue, or <CTRL> + <C> to abort.
****************************************************

rm -f qozap.o *.ko *.mod.c *.mod.o .*o.cmd *~
cc -c qozap.c -D__KERNEL__ -DMODULE -DEXPORT_SYMTAB -fomit-frame-pointer -O2 -Wall -I/usr/src/linux/include -I../zaptel -DMODVERSIONS -include /usr/src/linux/include/linux/modversions.h  -DCONFIG_ZAPATA_BRI_DCHANS
qozap.c: In function `qoz_fifo_tx':
qozap.c:206: error: structure has no member named `bytes2transmit'
qozap.c:211: error: structure has no member named `eoftx'
qozap.c:217: error: structure has no member named `bytes2transmit'
qozap.c:223: error: structure has no member named `bytes2transmit'
qozap.c:231: error: structure has no member named `bytes2transmit'
qozap.c:234: error: structure has no member named `eoftx'
qozap.c: In function `qoz_prepare_rx':
qozap.c:374: error: structure has no member named `bytes2receive'
qozap.c:377: error: structure has no member named `eofrx'
qozap.c:380: error: structure has no member named `eofrx'
qozap.c:383: error: structure has no member named `bytes2receive'
qozap.c:384: error: structure has no member named `eofrx'
qozap.c: In function `qoz_run':
qozap.c:401: error: structure has no member named `bytes2receive'
qozap.c:402: error: structure has no member named `bytes2transmit'
qozap.c:403: error: structure has no member named `eofrx'
qozap.c:404: error: structure has no member named `eoftx'
qozap.c: In function `ztqoz_startup':
qozap.c:617: error: `ZT_FLAG_BRIDCHAN' undeclared (first use in this function)
qozap.c:617: error: (Each undeclared identifier is reported only once
qozap.c:617: error: for each function it appears in.)
qozap.c: In function `qoz_findCards':
qozap.c:959: warning: int format, long unsigned int arg (arg 4)
qozap.c:966: warning: int format, long unsigned int arg (arg 4)
qozap.c:976: warning: int format, long unsigned int arg (arg 4)
make: *** [qozap.o] Error 1
****************************************************
quadBRI driver installed.
Press <Enter> to continue, or <CTRL> + <C> to abort.
****************************************************
 

teletreff

Neuer User
Mitglied seit
25 Jul 2004
Beiträge
20
Punkte für Reaktionen
0
Punkte
1
Und leider auch HFC-PCI bringt FM:



Code:
rm -f zaphfc.o *.ko *.mod.c *.mod.o .*o.cmd *~
cc -c zaphfc.c -D__KERNEL__ -DMODULE -DEXPORT_SYMTAB -fomit-frame-pointer -O2 -Wall -I/usr/src/linux/include -I../zaptel -Wall -DMODVERSIONS -include /usr/src/linux/include/linux/modversions.h  -DCONFIG_ZAPATA_BRI_DCHANS
zaphfc.c: In function `hfc_dtrans':
zaphfc.c:340: error: structure has no member named `bytes2transmit'
zaphfc.c:363: error: structure has no member named `bytes2transmit'
zaphfc.c:394: error: structure has no member named `eoftx'
zaphfc.c:398: error: structure has no member named `eoftx'
zaphfc.c: In function `hfc_drec':
zaphfc.c:409: error: structure has no member named `bytes2receive'
zaphfc.c:410: error: structure has no member named `eofrx'
zaphfc.c:452: error: structure has no member named `eofrx'
zaphfc.c:493: error: structure has no member named `eofrx'
zaphfc.c:507: error: structure has no member named `bytes2receive'
zaphfc.c:513: error: structure has no member named `bytes2receive'
zaphfc.c: In function `hfc_interrupt':
zaphfc.c:648: error: structure has no member named `bytes2transmit'
zaphfc.c:662: error: structure has no member named `bytes2receive'
zaphfc.c:671: error: structure has no member named `bytes2receive'
zaphfc.c: In function `zthfc_startup':
zaphfc.c:743: error: `ZT_FLAG_BRIDCHAN' undeclared (first use in this function)
zaphfc.c:743: error: (Each undeclared identifier is reported only once
zaphfc.c:743: error: for each function it appears in.)
zaphfc.c: In function `hfc_findCards':
zaphfc.c:898: warning: int format, long unsigned int arg (arg 8)
make: *** [zaphfc.o] Error 1
****************************************************
hfc-pci driver installed.
Press <Enter> to continue, or <CTRL> + <C> to abort.
****************************************************
 

teletreff

Neuer User
Mitglied seit
25 Jul 2004
Beiträge
20
Punkte für Reaktionen
0
Punkte
1
Leider macht auch das Treiber laden Fehler.

Kann mir jemand helfen - mit Eurer großen Erfahrung???

-> laut INSTALL - Anleitung

Loading the drivers (zaphfc):
cd zaphfc
make load (for TE mode)
or make loadNT (for NT mode)


Code:
host2:/usr/src/bri-stuff.0.1.0-RC2 # cd zaphfc
host2:/usr/src/bri-stuff.0.1.0-RC2/zaphfc # make loadNT
cc -c zaphfc.c -D__KERNEL__ -DMODULE -DEXPORT_SYMTAB -fomit-frame-pointer -O2 -Wall -I/usr/src/linux/include -I../zaptel -Wall -DMODVERSIONS -include /usr/src/linux/include/linux/modversions.h  -DCONFIG_ZAPATA_BRI_DCHANS
zaphfc.c: In function `hfc_dtrans':
zaphfc.c:340: error: structure has no member named `bytes2transmit'
zaphfc.c:363: error: structure has no member named `bytes2transmit'
zaphfc.c:394: error: structure has no member named `eoftx'
zaphfc.c:398: error: structure has no member named `eoftx'
zaphfc.c: In function `hfc_drec':
zaphfc.c:409: error: structure has no member named `bytes2receive'
zaphfc.c:410: error: structure has no member named `eofrx'
zaphfc.c:452: error: structure has no member named `eofrx'
zaphfc.c:493: error: structure has no member named `eofrx'
zaphfc.c:507: error: structure has no member named `bytes2receive'
zaphfc.c:513: error: structure has no member named `bytes2receive'
zaphfc.c: In function `hfc_interrupt':
zaphfc.c:648: error: structure has no member named `bytes2transmit'
zaphfc.c:662: error: structure has no member named `bytes2receive'
zaphfc.c:671: error: structure has no member named `bytes2receive'
zaphfc.c: In function `zthfc_startup':
zaphfc.c:743: error: `ZT_FLAG_BRIDCHAN' undeclared (first use in this function)
zaphfc.c:743: error: (Each undeclared identifier is reported only once
zaphfc.c:743: error: for each function it appears in.)
zaphfc.c: In function `hfc_findCards':
zaphfc.c:898: warning: int format, long unsigned int arg (arg 8)
make: *** [zaphfc.o] Error 1

Danke für Euer Feedback im voraus!

Ralf
 

Blackvel

Mitglied
Mitglied seit
4 Mai 2004
Beiträge
624
Punkte für Reaktionen
0
Punkte
0
Nein die Meldungen sind nicht normal.
Ändere mal zaphfc/Makefile.
Alles mit -I/usr/src/linux/include z.B auf -I/usr/src/linux-2.4/include abändern.
Das gleiche gilt für zaptel, libpri.
 

teletreff

Neuer User
Mitglied seit
25 Jul 2004
Beiträge
20
Punkte für Reaktionen
0
Punkte
1
Hallo an alle !

an Blackvel - Also lt. den obigen logs ist ja zaphfc und libpri ohne FM gelaufen. Habe in den Unterverzeichnissen von bri-stuff mir die Makefile&acute;s angeschaut - da war kein Eintrag I/usr/src/linux/include zu finden ...

an oktaku42 - jep habe vorher /usr/lib/asterisk/modules gelöscht.

Was nun ...

Habt Ihr eine Idee - das Zeug kann doch nicht soviel Probs machen - sonst würde es ja bei keinem Funktionieren...


Gruß

Ralf
 

NDEAlex

Neuer User
Mitglied seit
6 Aug 2004
Beiträge
5
Punkte für Reaktionen
0
Punkte
0
Hi teletreff,

habe das Problem auch gehabt. Nach langer sucherei habe ich dann festgestellt, dass die sourcen nicht gepatcht wurden.
Nach installtion des Tools patch und erneuten Aufruf ./install.sh, lief das compilieren ohne FM.

@all:

Nur habe ich jetzt das nächste Problem, bei "make loadNT" bekomme ich folgende FM:
Code:
make loadNT
make -C /usr/src/linux-2.6 SUBDIRS=/usr/src/bri-stuff.0.1.0-RC2k/zaphfc modules
make[1]: Entering directory `/usr/src/kernel-headers-2.6.6-1'
  Building modules, stage 2.
  MODPOST
make[1]: Leaving directory `/usr/src/kernel-headers-2.6.6-1'
modprobe zaptel
FATAL: Error inserting zaptel (/lib/modules/2.6.6-1-k7/misc/zaptel.ko): Invalid module format
make: *** [loadlinux26NT] Fehler 1
Kann jemand was damit anfangen?
 

schakal2k

Mitglied
Mitglied seit
16 Aug 2004
Beiträge
309
Punkte für Reaktionen
0
Punkte
16
NDEAlex schrieb:
Hi teletreff,

....

@all:

Nur habe ich jetzt das nächste Problem, bei "make loadNT" bekomme ich folgende FM:
Code:
make loadNT
make -C /usr/src/linux-2.6 SUBDIRS=/usr/src/bri-stuff.0.1.0-RC2k/zaphfc modules
make[1]: Entering directory `/usr/src/kernel-headers-2.6.6-1'
  Building modules, stage 2.
  MODPOST
make[1]: Leaving directory `/usr/src/kernel-headers-2.6.6-1'
modprobe zaptel
FATAL: Error inserting zaptel (/lib/modules/2.6.6-1-k7/misc/zaptel.ko): Invalid module format
make: *** [loadlinux26NT] Fehler 1
Kann jemand was damit anfangen?

Die gleiche Fehlermeldung bekomme ich auch...

EDIT:

Hat sich erledigt, nun läufts...
 
Holen Sie sich 3CX - völlig kostenlos!
Verbinden Sie Ihr Team und Ihre Kunden Telefonie Livechat Videokonferenzen

Gehostet oder selbst-verwaltet. Für bis zu 10 Nutzer dauerhaft kostenlos. Keine Kreditkartendetails erforderlich. Ohne Risiko testen.

3CX
Für diese E-Mail-Adresse besteht bereits ein 3CX-Konto. Sie werden zum Kundenportal weitergeleitet, wo Sie sich anmelden oder Ihr Passwort zurücksetzen können, falls Sie dieses vergessen haben.