From: Bernhard Rosenkraenzer <bero@arklinux.org>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.23-rc5-pac1 released
Date: Sat, 29 Nov 2003 14:42:20 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.58.0311291431320.29214@dot.kde.org> (raw)
In-Reply-To: <1070053162.12656.180.camel@pegasus>
On Fri, 28 Nov 2003, Marcel Holtmann wrote:
> Hi Bernhard,
>
> > - Increase timeout in firmware_class.c [several people reported timeout
> > related problems with Netgear WG511 cards]
>
> please tell me more about it.
Extract from the syslog of a user trying to use a Netgear WG511 with the
prism54.org drivers in a Dell SmartStep 250N:
Nov 18 15:14:52 rumsfeldsux kernel: cs: cb_alloc(bus 4): vendor 0x1260, device 0x3890
Nov 18 15:14:52 rumsfeldsux kernel: PCI: Enabling device 04:00.0 (0000 -> 0002)
Nov 18 15:14:52 rumsfeldsux cardmgr[1098]: socket 1: CardBus hotplug device
Nov 18 15:14:52 rumsfeldsux default.hotplug[1837]: ======= START HOTPLUG FOR PID 1837 =======
Nov 18 15:14:53 rumsfeldsux kernel: Loaded prism54 driver, version 1.0.2.2
Nov 18 15:14:53 rumsfeldsux default.hotplug[1862]: ======= START HOTPLUG FOR PID 1862 =======
Nov 18 15:14:53 rumsfeldsux default.hotplug[1870]: ======= START HOTPLUG FOR PID 1870 =======
Nov 18 15:15:03 rumsfeldsux kernel: prism54: request_firmware() failed for 'isl3890'
Nov 18 15:15:03 rumsfeldsux kernel: eth1: could not upload firmware ('isl3890')
We got a similar report from someone using the same card in an Asus
Pundit, and another from someone using a D-Link DWL-g650 A1 in a
Gericom notebook.
Telling the users to
echo 100 >/proc/driver/firmware/timeout
and try again fixed it for all of them.
All 3 are using Ark Linux Dockyard, meaning 2.4.23-rcsomething-pacwhatever
with a couple of extra patches and a fairly recent userland hotplug.
Due to lack of hardware I haven't yet figured out what the exact problem
is (I'm suspecting either the prism54 driver takes forever to handle the
firmware, or the hotplug scripts cause delays where they shouldn't), but
increasing the timeout definitely solves the problem for our users.
LLaP
bero
--
Ark Linux - Linux for the masses
http://www.arklinux.org/
Redistribution and processing of this message is subject to
http://www.arklinux.org/terms.php
prev parent reply other threads:[~2003-11-29 13:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-28 18:15 2.4.23-rc5-pac1 released Bernhard Rosenkraenzer
2003-11-28 20:59 ` Marcel Holtmann
2003-11-29 13:42 ` Bernhard Rosenkraenzer [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=Pine.LNX.4.58.0311291431320.29214@dot.kde.org \
--to=bero@arklinux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.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).