From: Shawn Starr <shawn.starr@rogers.com>
To: linux-kernel@vger.kernel.org
Cc: ipw2100-devel@lists.sourceforge.net, smiler@lanil.mine.nu
Subject: Re: [2.6.10-rc1-mm2] Firmware loader gone bogus?
Date: Sun, 31 Oct 2004 16:27:01 -0500 [thread overview]
Message-ID: <200410311627.02116.shawn.starr@rogers.com> (raw)
Yeah I noticed my ipw2200 firmware broke in 2.6.10-rc1-bk5
Does 2.6.10-rc1 non-bk snapshots work for you?
Shawn.
> List: linux-kernel
> Subject: [2.6.10-rc1-mm2] Firmware loader gone bogus?
> From: Christian Axelsson <smiler () lanil ! mine ! nu>
> Date: 2004-10-31 19:51:28
> Message-ID: <41854240.3050909 () lanil ! mine ! nu>
> [Download message RAW]
>
> Ive upgraded from 2.6.9-rc4-mm1 to 2.6.10-rc1-mm2 and now the firmware
> loader seems broken. I have an internal wlan-adapter that runs the
> ipw2200-driver and I get errors when trying to load the firmware.
> Then I tried my prism54-based card and got the following errors in dmesg:
>
> Loaded prism54 driver, version 1.2
> PCI: Enabling device 0000:03:00.0 (0000 -> 0002)
> ACPI: PCI interrupt 0000:03:00.0[A] -> GSI 6 (level, low) -> IRQ 6
> eth1: resetting device...
> eth1: uploading firmware...
> prism54: request_firmware() failed for 'isl3890'
> eth1: could not upload firmware ('isl3890')
> eth1: islpci_reset: failure
>
> The firmware files are in place and both these cards with drivers have
> worked fine before. Config attached
>
> --
> Regards,
> Christian
next reply other threads:[~2004-10-31 20:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-31 21:27 Shawn Starr [this message]
2004-11-01 0:34 ` [2.6.10-rc1-mm2] Firmware loader gone bogus? Oliver Neukum
2004-11-01 0:49 ` Marcel Holtmann
2004-11-01 1:50 ` Shawn Starr
2004-11-01 2:34 ` [Ipw2100-devel] " Shawn Starr
2004-11-01 16:40 ` Christian Axelsson
-- strict thread matches above, loose matches on Subject: below --
2004-10-31 19:51 Christian Axelsson
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=200410311627.02116.shawn.starr@rogers.com \
--to=shawn.starr@rogers.com \
--cc=ipw2100-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=smiler@lanil.mine.nu \
/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