From: Artem Bityutskiy <dedekind1@gmail.com>
To: Arno Steffen <arno.steffen@googlemail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: error!: "/dev/ubi0" is not a character device ?!?
Date: Fri, 30 Jul 2010 09:23:09 +0300 [thread overview]
Message-ID: <1280470989.2838.16.camel@localhost.localdomain> (raw)
In-Reply-To: <AANLkTik7CdwdyhzVYFXG66V3LKZvqnZhLbg4eVC0nQ=S@mail.gmail.com>
On Mon, 2010-07-26 at 15:49 +0200, Arno Steffen wrote:
> > Your udev rules, perhaps? Creating device nodes is responsibility of
> > your system, not UBI/ubi-utils.
>
> My mtd8 is a character device as it should be.
> crw-rw---- 1 root root 90, 16 Jan 1 00:00 /dev/mtd8
>
> I don't know who is creating the device node, but it is avauilable
> after ubiattach.
> If it is done by udev - how to control it and change it's behaviour?
> I can delete the device node and create one manually as described by
> free_electrons.
When UBI registers character devices, the generic linux chdev code sends
an uevent to user-space. This uevent event contains the information
about what was created, major/minor of that, etc.
In user-space there is udevd, which is listening on a netlink socket,
and handles the uevents. There are udev rules which describe how to
handle events, the rules are usually at /etc/udev/rules.d/
So, I suspect that one of your rules is screwed.
You should use udevmonitor and take a look at the events and how they
are handled. And google a bit, perhaps. udev has nothing to do with UBI.
And I do not know much about udev.
> cat /sys/class/ubi/ubi0/dev (e.g. 253:0)
> mknod /dev/ubi0 c 253 0
This looks correct
> Calling ubimkvol then creates a lot of other errors. (see below)
This is strange.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
prev parent reply other threads:[~2010-07-30 6:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-26 12:00 error!: "/dev/ubi0" is not a character device ?!? Arno Steffen
2010-07-26 13:14 ` Artem Bityutskiy
2010-07-26 13:49 ` Arno Steffen
2010-07-27 15:25 ` Artem Bityutskiy
2010-07-28 11:04 ` Arno Steffen
2010-07-30 6:35 ` Artem Bityutskiy
2010-08-05 11:55 ` Arno Steffen
2010-08-05 13:23 ` twebb
2010-08-05 13:36 ` Artem Bityutskiy
[not found] ` <AANLkTikkRNqnEX0PkHigv=zT+Z36J52DEtoVeMGbBExf@mail.gmail.com>
2010-08-16 11:27 ` Arno Steffen
2010-08-23 12:34 ` Artem Bityutskiy
2010-08-23 14:13 ` Arno Steffen
2010-08-23 14:41 ` Artem Bityutskiy
2010-08-24 8:32 ` Arno Steffen
2010-08-24 8:53 ` Artem Bityutskiy
2010-08-24 9:19 ` Arno Steffen
2010-08-24 9:33 ` Artem Bityutskiy
2010-07-30 6:23 ` Artem Bityutskiy [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=1280470989.2838.16.camel@localhost.localdomain \
--to=dedekind1@gmail.com \
--cc=arno.steffen@googlemail.com \
--cc=linux-mtd@lists.infradead.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).