From: Felix Brack <fb@ltec.ch>
To: linux-hotplug@vger.kernel.org
Subject: AVM FRITZ!Card DSL generating udev error messages
Date: Fri, 20 Apr 2007 10:12:43 +0000 [thread overview]
Message-ID: <661268054.20070420121243@ltec.ch> (raw)
Hello,
I just installed an AVM FRITZ!Card DSL in a Debian 4.0 ("Etch") system
with kernel 2.6.18. The DSL part seems ok, I did not yet check if the
ISDN part is working too.
However when I startup the system syslog shows a lot of error
messages about udev not being able to execute mknod (see contents of
syslog below).
If my interpretation of the the syslog is correct, udev is trying to
create nodes with major number 191; according to 'devices.txt' this is
the major number reserved to PCMCIA not to CAPI devices.
Do I have to change some rules of udev to make it work correctly?
Could this be a problem of the driver 'fcdsl' not being fully loaded
at the time udev receives the events in question?
many thanks, Felix
----------- contents of syslog STARTS ------------
Apr 20 11:34:58 nebula kernel: intel_rng: FWH not detected
Apr 20 11:34:58 nebula kernel: CAPI Subsystem Rev 1.1.2.8
Apr 20 11:34:58 nebula kernel: fcdsl: module license 'Proprietary' taints kernel.
Apr 20 11:34:58 nebula kernel: fcdsl: AVM FRITZ!Card DSL driver, revision 0.5.2
Apr 20 11:34:58 nebula kernel: fcdsl: fcdsl built on Apr 19 2007 at 20:15:32)
Apr 20 11:34:58 nebula kernel: ACPI: PCI Interrupt 0000:01:0b.0[A] -> GSI 22 (level, low) -> IRQ 209
Apr 20 11:34:58 nebula kernel: fcdsl: Loading...
Apr 20 11:34:58 nebula kernel: fcdsl: Driver 'fcdsl' attached to fcdsl-stack. (164)
Apr 20 11:34:58 nebula kernel: kcapi: Controller 1: fcdsl-fbc00000-209 attached
Apr 20 11:34:58 nebula kernel: kcapi: Controller 2: fcdsl-fbc00000-209 attached
Apr 20 11:34:58 nebula kernel: fcdsl: Loaded.
Apr 20 11:34:58 nebula kernel: Adding 979956k swap on /dev/sda3. Priority:-1 extents:1 across:979956k
Apr 20 11:34:58 nebula kernel: EXT3 FS on sda1, internal journal
Apr 20 11:34:58 nebula kernel: loop: loaded (max 8 devices)
Apr 20 11:34:58 nebula kernel: device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised: dm-devel@redhat.com
Apr 20 11:34:58 nebula kernel: kjournald starting. Commit interval 5 seconds
Apr 20 11:34:58 nebula kernel: EXT3 FS on sda2, internal journal
Apr 20 11:34:58 nebula kernel: EXT3-fs: mounted filesystem with ordered data mode.
Apr 20 11:34:58 nebula kernel: skge eth0: enabling interface
Apr 20 11:34:58 nebula kernel: capifs: Rev 1.1.2.3
Apr 20 11:34:58 nebula udevd-event[1977]: udev_node_mknod: mknod(/dev/capi/0, 020660, 191, 0) failed: Operation not permitted
Apr 20 11:34:58 nebula udevd-event[1978]: udev_node_mknod: mknod(/dev/capi/1, 020660, 191, 1) failed: Operation not permitted
Apr 20 11:34:58 nebula udevd-event[1979]: udev_node_mknod: mknod(/dev/capi/2, 020660, 191, 2) failed: Operation not permitted
Apr 20 11:34:58 nebula udevd-event[1980]: udev_node_mknod: mknod(/dev/capi/3, 020660, 191, 3) failed: Operation not permitted
Apr 20 11:34:58 nebula udevd-event[1981]: udev_node_mknod: mknod(/dev/capi/4, 020660, 191, 4) failed: Operation not permitted
Apr 20 11:34:58 nebula kernel: capi20: Rev 1.1.2.7: started up with major 68 (middleware+capifs)
Apr 20 11:34:58 nebula udevd-event[1982]: udev_node_mknod: mknod(/dev/capi/5, 020660, 191, 5) failed: Operation not permitted
Apr 20 11:34:58 nebula udevd-event[1983]: udev_node_mknod: mknod(/dev/capi/6, 020660, 191, 6) failed: Operation not permitted
Apr 20 11:34:58 nebula udevd-event[1984]: udev_node_mknod: mknod(/dev/capi/7, 020660, 191, 7) failed: Operation not permitted
Apr 20 11:34:58 nebula udevd-event[1985]: udev_node_mknod: mknod(/dev/capi/8, 020660, 191, 8) failed: Operation not permitted
Apr 20 11:34:58 nebula udevd-event[1986]: udev_node_mknod: mknod(/dev/capi/9, 020660, 191, 9) failed: Operation not permitted
Apr 20 11:34:58 nebula udevd-event[1987]: udev_node_mknod: mknod(/dev/capi/10, 020660, 191, 10) failed: Operation not permitted
Apr 20 11:34:58 nebula udevd-event[1988]: udev_node_mknod: mknod(/dev/capi/11, 020660, 191, 11) failed: Operation not permitted
Apr 20 11:34:58 nebula udevd-event[1989]: udev_node_mknod: mknod(/dev/capi/12, 020660, 191, 12) failed: Operation not permitted
Apr 20 11:34:58 nebula udevd-event[1990]: udev_node_mknod: mknod(/dev/capi/13, 020660, 191, 13) failed: Operation not permitted
Apr 20 11:34:58 nebula udevd-event[1991]: udev_node_mknod: mknod(/dev/capi/14, 020660, 191, 14) failed: Operation not permitted
Apr 20 11:34:58 nebula udevd-event[1992]: udev_node_mknod: mknod(/dev/capi/15, 020660, 191, 15) failed: Operation not permitted
Apr 20 11:34:58 nebula udevd-event[1993]: udev_node_mknod: mknod(/dev/capi/16, 020660, 191, 16) failed: Operation not permitted
Apr 20 11:34:58 nebula udevd-event[1994]: udev_node_mknod: mknod(/dev/capi/17, 020660, 191, 17) failed: Operation not permitted
Apr 20 11:34:58 nebula udevd-event[1995]: udev_node_mknod: mknod(/dev/capi/18, 020660, 191, 18) failed: Operation not permitted
Apr 20 11:34:58 nebula udevd-event[1996]: udev_node_mknod: mknod(/dev/capi/19, 020660, 191, 19) failed: Operation not permitted
Apr 20 11:34:58 nebula udevd-event[1997]: udev_node_mknod: mknod(/dev/capi/20, 020660, 191, 20) failed: Operation not permitted
Apr 20 11:34:58 nebula udevd-event[1998]: udev_node_mknod: mknod(/dev/capi/21, 020660, 191, 21) failed: Operation not permitted
Apr 20 11:34:58 nebula udevd-event[1999]: udev_node_mknod: mknod(/dev/capi/22, 020660, 191, 22) failed: Operation not permitted
Apr 20 11:34:58 nebula udevd-event[2000]: udev_node_mknod: mknod(/dev/capi/23, 020660, 191, 23) failed: Operation not permitted
Apr 20 11:34:58 nebula udevd-event[2001]: udev_node_mknod: mknod(/dev/capi/24, 020660, 191, 24) failed: Operation not permitted
Apr 20 11:34:58 nebula udevd-event[2002]: udev_node_mknod: mknod(/dev/capi/25, 020660, 191, 25) failed: Operation not permitted
Apr 20 11:34:58 nebula udevd-event[2004]: udev_node_mknod: mknod(/dev/capi/27, 020660, 191, 27) failed: Operation not permitted
Apr 20 11:34:58 nebula udevd-event[2005]: udev_node_mknod: mknod(/dev/capi/28, 020660, 191, 28) failed: Operation not permitted
Apr 20 11:34:58 nebula udevd-event[2006]: udev_node_mknod: mknod(/dev/capi/29, 020660, 191, 29) failed: Operation not permitted
Apr 20 11:34:58 nebula udevd-event[2007]: udev_node_mknod: mknod(/dev/capi/30, 020660, 191, 30) failed: Operation not permitted
Apr 20 11:34:58 nebula udevd-event[2008]: udev_node_mknod: mknod(/dev/capi/31, 020660, 191, 31) failed: Operation not permitted
Apr 20 11:34:58 nebula udevd-event[2003]: udev_node_mknod: mknod(/dev/capi/26, 020660, 191, 26) failed: Operation not permitted
Apr 20 11:34:59 nebula kernel: fcdsl: Using VCC/VPI/VCI = 0x1/0x1/0x20
Apr 20 11:34:59 nebula kernel: fcdsl: Stack version 3.11-07
Apr 20 11:34:59 nebula kernel: fcdsl: Stack version 3.11-07
Apr 20 11:34:59 nebula kernel: kcapi: card 1 "fcdsl-fbc00000-209" ready.
Apr 20 11:34:59 nebula kernel: kcapi: card 2 "fcdsl-fbc00000-209" ready.
Apr 20 11:34:59 nebula kernel: ACPI: Power Button (FF) [PWRF]
Apr 20 11:34:59 nebula kernel: ACPI: Power Button (CM) [PWRB]
Apr 20 11:34:59 nebula kernel: skge eth0: Link is up at 100 Mbps, full duplex, flow control tx and rx
------------ contents of syslog ENDS ------------------
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next reply other threads:[~2007-04-20 10:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-20 10:12 Felix Brack [this message]
2007-04-20 15:03 ` AVM FRITZ!Card DSL generating udev error messages Kay Sievers
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=661268054.20070420121243@ltec.ch \
--to=fb@ltec.ch \
--cc=linux-hotplug@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).