From: Kay Sievers <kay.sievers@vrfy.org>
To: Greg KH <greg@kroah.com>
Cc: Alistair John Strachan <s0348365@sms.ed.ac.uk>,
linux-kernel@vger.kernel.org
Subject: Re: udev-067 and 2.6.12?
Date: Wed, 17 Aug 2005 01:09:20 +0200 [thread overview]
Message-ID: <20050816230920.GA11750@vrfy.org> (raw)
In-Reply-To: <20050816221450.GA28520@kroah.com>
On Tue, Aug 16, 2005 at 03:14:50PM -0700, Greg KH wrote:
> On Tue, Aug 16, 2005 at 11:12:26PM +0100, Alistair John Strachan wrote:
> > On Tuesday 16 August 2005 23:05, Greg KH wrote:
> > > On Tue, Aug 16, 2005 at 11:02:00PM +0100, Alistair John Strachan wrote:
> > > > Hi,
> > > >
> > > > I just tried upgrading udev 053 to 067 on a 2.6.12 system and although
> > > > the system booted, firmware_class failed to upload the firmware for my
> > > > wireless card, prism54 was no longer auto loaded, etc. Even manually
> > > > loading the driver didn't help.
> > > >
> > > > Any reason why 067 wouldn't work with 2.6.12? Do you have to do something
> > > > special with hotplug prior to upgrading?
> > >
> > > What distro are you using? What rules file are you using?
> > >
> > > 067 should work just fine for you, it is for a lot of Gentoo and SuSE
> > > users right now, on 2.6.12.
> > >
> >
> > An LFS from April 05, with the stock 50-udev.rules, 25-lfs.rules (which
> > doesn't do anything suspicious, I think; certainly nothing related to my
> > problem).
>
> There are no "stock" udev rules anymore. That's probably the issue, all
> of the distros made their own, so we provide them in the tarball. I
> suggest you talk to the LFS people about this.
>
> > 25-lfs.rules does duplicate some of the things in 50-udev.rules, but I think
> > that's deliberate (they want to interfere with the stock install as little as
> > possible, and the overrides take precedence). I've put my /etc/udev directory
> > unmodified up here:
> >
> > http://devzero.co.uk/~alistair/udev/
>
> s/=/==/ for most of your rules and see if that works.
>
> > If I reinstall 053 and reboot, everything that's broken on 067 works again. Do
> > you need a specific hotplug installed?
Do you provide hooks for handling /etc/hotplug.d/? We are on the way of
getting rid of that directory and recent udev versions don't handle
that by default anymore. If you don't know, read the udev RELEASE-NOTES.
Kay
next prev parent reply other threads:[~2005-08-16 23:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-16 22:02 Alistair John Strachan
2005-08-16 22:05 ` Greg KH
2005-08-16 22:12 ` Alistair John Strachan
2005-08-16 22:14 ` Greg KH
2005-08-16 23:09 ` Kay Sievers [this message]
2005-08-16 23:33 ` Alistair John Strachan
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=20050816230920.GA11750@vrfy.org \
--to=kay.sievers@vrfy.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=s0348365@sms.ed.ac.uk \
/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
all inboxes | Powered by JetHome®