Re: PRO/Wireless 3945ABG (Device not configured)

Torfinn Ingolfsen <[email protected]>
Newsgroups gmane.os.freebsd.devel.mobile
Message-ID <[email protected]>
On Sun, 23 Jul 2006 08:49:41 -0400 (EDT)
Daniel Eischen <[email protected]> wrote:

> Sorry, I don't run 6.x, so I can't help.  Everything works fine
> on -current.  If you're not at 6-stable, I'd try that.

I installed -current from the Julysnapshot on the last free
slice in the machine:
FreeBSD kg-home.kg4.no 7.0-CURRENT-200607 FreeBSD 7.0-CURRENT-200607 #0: Fri Jul  7 23:24:18 UTC 2006     [email protected]:/usr/obj/usr/src/sys/GENERIC  i386

And then I tried the driver again. Note: this is with acpi enabled,
because for some reason the machine hangs if I try to boot -current with acpi disabled
(see another thread in this mailing list).

after
kldload firmware
kldload wpi_ucode
kldload if_wpi

I get the following in /var/log/messages:
Aug  4 16:11:02 kg-home kernel: wpi0: <Intel(R) PRO/Wireless 3945ABG> irq 17 at device 0.0 on pci3
Aug  4 16:11:02 kg-home kernel: wpi0: 0x1000 bytes of rid 0x10 res 3 failed (0, 0xffffffff).
Aug  4 16:11:02 kg-home kernel: wpi0: could not allocate memory resource
Aug  4 16:11:02 kg-home kernel: device_attach: wpi0 attach returned 12
Aug  4 16:11:02 kg-home kernel: bge0: <Broadcom BCM5750 C1, ASIC rev. 0x4201> irq 18 at device 0.0 on pci4
Aug  4 16:11:02 kg-home kernel: bge0: 0x10000 bytes of rid 0x10 res 3 failed (0, 0xffffffff).
Aug  4 16:11:02 kg-home kernel: bge0: couldn't map memory
Aug  4 16:11:02 kg-home kernel: device_attach: bge0 attach returned 6


I suspect it is because of the broken ACPI / dsdt on this laptop, and would love to try it with acpi disabled.
Any hints on making -current boot with acpi disabled on this laptop?
-- 
Regards,
Torfinn Ingolfsen,
Norway

_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-mobile
To unsubscribe, send any mail to "[email protected]"
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.