Date: Mon, 23 Jul 2007 13:13:26 -0700 From: "Kevin Oberman" <oberman@es.net> To: Jeremie Le Hen <jeremie@le-hen.org> Cc: freebsd-current@freebsd.org Subject: Re: Cannot use iwi(4): "could not load firmware iwi_bss" Message-ID: <20070723201326.C539945045@ptavv.es.net> In-Reply-To: Your message of "Mon, 23 Jul 2007 22:00:21 %2B0200." <20070723200021.GB96643@obiwan.tataz.chchile.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--==_Exmh_1185221606_51096P Content-Type: text/plain; charset=us-ascii Content-Disposition: inline > Date: Mon, 23 Jul 2007 22:00:21 +0200 > From: Jeremie Le Hen <jeremie@le-hen.org> > Sender: owner-freebsd-current@freebsd.org > > John, > > On Mon, Jul 23, 2007 at 11:16:00AM -0400, John Baldwin wrote: > > On Friday 20 July 2007 07:21:00 pm Jeremie Le Hen wrote: > > > Ok, I've tried with ACPI enabled and I confirm that iwi(4) can > > > successfully load its firmware in this case. Unfortunately psm(4) > > > doesn't work so this is not an option for me. > > > > Can you get verbose dmesg's both with and without ACPI? > > I've not attached them as verbose dmesgs are quite huge, you can get > them here. > > With ACPI (psm(4) doesn't work, iwi(4) does): > http://tataz.chchile.org/~tataz/tmp/dmesg.with_acpi.gz > > Without ACPI (hint.acpi.0.disabled="1", psm(4) works, iwi(4) doesn't): > http://tataz.chchile.org/~tataz/tmp/dmesg.without_acpi.gz > > Note that I've manually loaded iwi_bss and if_iwi modules from root > prompt. I have a very similar problem when I load drivers at the boot prompt (or did you mean "root"?) If you look at your dmesg (verbose not needed). I suspect that you will se that there is no interrupt assigned to psm. If you are loading them before the probe, try booting with ACPI and boot to single user (boot -s). Hit Enter to get a shell prompt and load the needed modules (kldload). Then exit to move to multi-user. I bet everything works. I found that my system fails to assign an interrupt to psm if I have the module loaded before I probe I/O devices. jhb suggested an approach to fixing this, but I have not gotten around to trying it. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 --==_Exmh_1185221606_51096P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) Comment: Exmh version 2.5 06/03/2002 iD8DBQFGpQvmkn3rs5h7N1ERAj6NAJ4jSZSqcZs7r4TysxyENm4akxrkAwCfaRYw Akopdt4nt23b9+vjbLqCFGg= =65pk -----END PGP SIGNATURE----- --==_Exmh_1185221606_51096P--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070723201326.C539945045>