linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: Bug#297481: hotplug: Fails to load firmware for ipw2200 after
Date: Tue, 01 Mar 2005 20:02:49 +0000	[thread overview]
Message-ID: <1109707369.481.5.camel@localhost.localdomain> (raw)
In-Reply-To: <20050301192504.GA24710@wonderland.linux.it>

On Tue, 2005-03-01 at 20:25 +0100, Marco d'Itri wrote:
>What's wrong? The user is running udev 0054 with udevsend as the
>hotplug multiplexer, if /sbin/hotplug is restored then the firmware
>loader works again.
>(In the report he talks about hotplug, but we later verified that udev
>was upgraded at the same time.)

>1.0.0-1, running on standard Debian kernel image 2.6.8-1-686.

This kernel will not work correctly with managed events. It has holes in
the sequence numbers. You need at least 2.6.10 if I remember correctly.

Kay



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id\x14396&op=click
_______________________________________________
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

  reply	other threads:[~2005-03-01 20:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-01 19:25 Bug#297481: hotplug: Fails to load firmware for ipw2200 after upgrade Marco d'Itri
2005-03-01 20:02 ` Kay Sievers [this message]
2005-03-01 20:26 ` Marco d'Itri
2005-03-01 20:41 ` Bug#297481: hotplug: Fails to load firmware for ipw2200 after 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=1109707369.481.5.camel@localhost.localdomain \
    --to=kay.sievers@vrfy.org \
    --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).