From: Romit <romit.linux@gmail.com>
To: "Michal Piotrowski" <michal.k.k.piotrowski@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: CONFIG for udev to work?
Date: Tue, 4 Jul 2006 03:57:13 +0530 [thread overview]
Message-ID: <200607040357.14123.romit.linux@gmail.com> (raw)
In-Reply-To: <6bffcb0e0607031514r6e14c68am5964f07265e0caeb@mail.gmail.com>
Hi Michal,
Thanks. I checked the udev version and it is 068. Meanwhile, what
I did was I booted into 2.6.13-15 and
zcat /proc/config.gz > $(KERN_SOURCEDIR_2.6.17.1)/
and then ran
make xconfig.
Ofcourse there were some CONFIG options that were present in 2.6.13-15 and
missing in 2.6.17.1 and vice versa but once I resolved those and built the
kernel, udev seems to be working. So I did not upgrade udev to 071 but still
it works. I think there should be some CONFIG option that I am missing. I am
not sure which one.
Thanks again,
-Romit
On Tuesday 04 July 2006 03:44, you wrote:
> Hi,
>
> On 04/07/06, Romit <romit.linux@gmail.com> wrote:
> > Hi,
> >
> > I sent a query to linux-hotplug-devel a few days back but did not get
> > any reply, so I am posting it here.
> > I upgraded from 2.6.13-15 to 2.6.17.1 and I can't see any UEVENT message
> > generation. I am running udevmonitor and it is just blocking on receiving
> > UEVENT from the kernel even after I insert a usb keyboard/ usb storage /
> > usb bluetooth dongle.
> > I am running SUSE LINUX 10.0.
> > I am sure that I am missing some CONFIG iitem. All I want to know is what
> > arethem essential items that I need to enable for udev to work.Kindly let
> > me know what CONFIG item I am missing.
>
> Documentation/Changes
>
> "udev 071 # udevinfo -V"
>
> > Thanks in advance
> > -Romit
>
> Regards,
> Michal
next prev parent reply other threads:[~2006-07-03 22:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-03 22:02 CONFIG for udev to work? Romit
2006-07-03 22:14 ` Michal Piotrowski
2006-07-03 22:27 ` Romit [this message]
2006-07-04 1:47 ` Marc D Ronell
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=200607040357.14123.romit.linux@gmail.com \
--to=romit.linux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.k.k.piotrowski@gmail.com \
/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