> Date: Mon, 23 Jul 2007 22:00:21 +0200 > From: Jeremie Le Hen <jeremie_at_le-hen.org> > Sender: owner-freebsd-current_at_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_at_es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:15 UTC