public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Arne Fitzenreiter <Arne.Fitzenreiter@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Problem with mISDN
Date: Wed, 27 Feb 2013 10:12:24 +0100	[thread overview]
Message-ID: <87053553679e8b3faf9682bbafde4302@mail01.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 3306 bytes --]

das hab ich dich in der Beta noch ausprobiert...
Auf jeden fall ist jetzt die Modulsuchreihenfolge wiedermal falsch und 
er lädt die veralteten Module aus den Kernel
(eigentlich sollte er die beim Build löschen aber da musste ja mal 
wieder an den Pfaden rumgeändert werden und ich habs nicht gemerkt.)

lösch mal
lib/modules/*-ipfire*/kernel/drivers/isdn/hardware/mISDN
lib/modules/*-ipfire*/kernel/drivers/isdn/mISDN

und mach dann "depmod -a" und einen reboot, dann sollte mISDN wieder 
laden.
Asterisk hab ich nicht probiert...

Arne


On 2013-02-26 13:04, Thomas Ebert wrote:
> Hello Michael,
>
>  can you log into the system and check the following directory: ls
> -al /lib/modules/3.2.38-ipfire/mISDN/
>
>  These are my files
>  -rw-r--r-- 1 root root 16240 2013-02-16 17:38 avmfritz.ko
>  -rw-r--r-- 1 root root 106556 2013-02-16 17:38 hfcmulti.ko
>  -rw-r--r-- 1 root root 33175 2013-02-16 17:38 hfcpci.ko
>  -rw-r--r-- 1 root root 37531 2013-02-16 17:38 hfcsusb.ko
>  -rw-r--r-- 1 root root 27446 2013-02-16 17:38 l1oip.ko
>  -rw-r--r-- 1 root root 98851 2013-02-16 17:38 mISDN_core.ko
>  -rw-r--r-- 1 root root 6062 2013-02-16 17:38 mISDN_dsp_kb1ec.ko
>  -rw-r--r-- 1 root root 71469 2013-02-16 17:38 mISDN_dsp.ko
>  -rw-r--r-- 1 root root 6025 2013-02-16 17:38 mISDN_dsp_mec2.ko
>  -rw-r--r-- 1 root root 7269 2013-02-16 17:38 mISDN_dsp_mg2ec.ko
>  -rw-r--r-- 1 root root 5093 2013-02-16 17:38 mISDN_dsp_octwareec.ko
>  -rw-r--r-- 1 root root 7610 2013-02-16 17:38 mISDN_dsp_oslec.ko
>  -rw-r--r-- 1 root root 18136 2013-02-16 17:38 mISDNinfineon.ko
>  -rw-r--r-- 1 root root 23778 2013-02-16 17:38 mISDNipac.ko
>  -rw-r--r-- 1 root root 25584 2013-02-16 17:38 mISDNisar.ko
>  -rw-r--r-- 1 root root 17157 2013-02-16 17:38 mISDN_l1loop.ko
>  -rw-r--r-- 1 root root 16898 2013-02-16 17:38 netjet.ko
>  drwxr-xr-x 2 root root 4096 2013-02-16 17:38 octvqe
>  -rw-r--r-- 1 root root 10826 2013-02-16 17:38 speedfax.ko
>  -rw-r--r-- 1 root root 19295 2013-02-16 17:38 w6692.ko
>  -rw-r--r-- 1 root root 31988 2013-02-16 17:38 xhfc.ko
>
>  But i've also a starting error (IPFire 2.13 i586):
>  [root(a)ipfire ~]# /etc/init.d/mISDN start
>  Starting mISDNv2 ...
>  FATAL: Error inserting mISDN_dsp_oslec
> (/lib/modules/3.2.38-ipfire/mISDN/mISDN_dsp_oslec.ko): Unknown symbol
> in module, or unknown parameter (see dm[ FAIL ]
>
>  Regards
>  Thomas
>
>  Am 26.02.2013 11:07, schrieb Michael Liekmeier:
>
>> Hallo,
>>
>> after the core update 66 asterisk don't work anymore.
>>
>> I get the following errow messeg
>>
>> /etc/init.d/mISDN start
>> insmod: can't read 'usrlibasteriskmodules/mISDN_core.ko': No such 
>> file or directory
>> insmod: can't read 'usrlibasteriskmodules/mISDN_dsp.ko': No such 
>> file or directory
>> insmod: can't read 'usrlibasteriskmodules/hfcpci.ko': No such file 
>> or directory
>>
>> How can fix this problem?
>>
>> Regards
>>
>> Michael
>>
>> _______________________________________________
>> Development mailing list
>> Development(a)lists.ipfire.org
>> http://lists.ipfire.org/mailman/listinfo/development [1]
>
>
>
> Links:
> ------
> [1] http://lists.ipfire.org/mailman/listinfo/development
>
> _______________________________________________
> Development mailing list
> Development(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/development

             reply	other threads:[~2013-02-27  9:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-27  9:12 Arne Fitzenreiter [this message]
2013-02-27 12:08 ` Michael Tremer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87053553679e8b3faf9682bbafde4302@mail01.ipfire.org \
    --to=arne.fitzenreiter@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox