From: Matthias Thomae <thomae@ei.tum.de>
To: bluez-users <bluez-users@lists.sourceforge.net>
Subject: [Bluez-users] cmtp, capidrv and kernel 2.6
Date: Fri, 30 Jan 2004 10:40:44 +0100 [thread overview]
Message-ID: <401A269C.7070104@ei.tum.de> (raw)
Hi Marcel et al,
could anyone give a hint what changes are necessary from kernel 2.4.X to
2.6.X to get an isdn dialup setup via cmtp and capidrv (i4l)?
I have a very well working setup for 2.4.22-mh2, essentially following
Marcel's (BTW excellent :) instructions from
http://www.holtmann.org/linux/bluetooth/isdn.html and had a quick try
using the same setup on an unpatched 2.6.2-rc2 vanilla kernel, getting
the following symptoms:
- cmtp and kernelcapi are loaded and connecting to an AP-X works
- capiinfo and capiinit complain about not being able to load
kernelcapi, although it is already loaded
- capidrv isn't loaded automatically any more
- "/etc/init.d/isdnutils start" complains about /dev/isdnctrl (because
of missing capidrv?)
- when modprobing capidrv the console is flooded with messages
I use debian/unstable with the latest isdn and capi packages (3.3-7).
Do I need any kernel patches (e.g. the i4l patch from
http://rcum.uni-mb.si/~uvp00845b/)?
Do I have to modify the module loading definitions in /etc/modutils?
Does pppdcapiplugin work without additional kernel patches?
Regards.
Matthias
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next reply other threads:[~2004-01-30 9:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-30 9:40 Matthias Thomae [this message]
2004-01-31 15:19 ` [Bluez-users] cmtp, capidrv and kernel 2.6 Marcel Holtmann
2004-02-03 9:09 ` Matthias Thomae
2004-02-03 11:37 ` Marcel Holtmann
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=401A269C.7070104@ei.tum.de \
--to=thomae@ei.tum.de \
--cc=bluez-users@lists.sourceforge.net \
/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