Date: Fri, 10 Aug 2007 08:48:35 +0200 From: Jeremie Le Hen <jeremie@le-hen.org> To: Kevin Oberman <oberman@es.net> Cc: freebsd-current@freebsd.org Subject: Re: Cannot use iwi(4): "could not load firmware iwi_bss" Message-ID: <20070810064835.GC48218@obiwan.tataz.chchile.org> In-Reply-To: <20070723201326.C539945045@ptavv.es.net> References: <20070723200021.GB96643@obiwan.tataz.chchile.org> <20070723201326.C539945045@ptavv.es.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Kevin, Sorry for this late reply. On Mon, Jul 23, 2007 at 01:13:26PM -0700, Kevin Oberman wrote: > > Date: Mon, 23 Jul 2007 22:00:21 +0200 > > From: Jeremie Le Hen <jeremie@le-hen.org> > > Sender: owner-freebsd-current@freebsd.org > > > > 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"?) I meant "root" prompt :-). > 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. I wished to try this but unfortunately psm(4) doesn't seem to be available as a module. # cd /sys/modules # grep -rl psm\\.c . # > jhb suggested an approach to fixing this, but I have not gotten around > to trying it. Could you point out this please? Thank you. Best regards, -- Jeremie Le Hen < jeremie at le-hen dot org >< ttz at chchile dot org >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070810064835.GC48218>