From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] ISDN problems
Date: Wed, 23 Jun 2010 20:09:00 +0100 [thread overview]
Message-ID: <201006232009.19962.michaelkintzios@gmail.com> (raw)
In-Reply-To: <201006230023.55141.wonko@wonkology.org>
[-- Attachment #1: Type: text/plain, Size: 1288 bytes --]
On Tuesday 22 June 2010 23:23:53 Alex Schuster wrote:
> But /etc/init.d/capi fails to start, when calling 'capiinit activate':
> ERROR: cannot open /dev/capi20 nor /dev/isdn/capi20 - No such device or
> address (6)
>
> This file is existing:
> crw------- 1 root root 191, 20 22. Jun 23:35 /dev/capi20
>
> Changing permissions does not help.
>
> I also tried the other kernel modules, net-dialup/fritzcapi, but that does
> not build either - it does not find linux/auconf.h. Huh? I have this in
> /usr/lib64/klibc/include/ only. On other Gentoo systems, this should be in
> the kernel's include directory. Maybe 2.6.33 is too new for that?
>
> Then I tried mISDN, and guess what, it also does not compile at all. There
> is a bug report (#265581), but its over a year old without progress.
>
> So I downloaded mISDN and built it according to http://www.misdn.org/,
> which seemed to work. But I get the same capi error. So it's probably not
> a problem with the ISDN card kernel driver, but with the CAPI setup.
>
> I'm out of ideas. What's wrong with /dev/capi20?
Should the ownership be different than root:root perhaps? e.g. have you tried
root:tty, or root:dialup, or root:uucp, or whichever group is appropriate for
ISDN?
--
Regards,
Mick
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2010-06-23 20:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-22 22:23 [gentoo-user] ISDN problems Alex Schuster
2010-06-23 7:20 ` Thomas U. Nockmann
2010-07-02 1:01 ` Alex Schuster
2010-07-13 16:20 ` Alex Schuster
2010-06-23 19:09 ` Mick [this message]
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=201006232009.19962.michaelkintzios@gmail.com \
--to=michaelkintzios@gmail.com \
--cc=gentoo-user@lists.gentoo.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