Date: Tue, 12 Apr 2005 17:03:12 +1200 From: Philip Murray <pmurray@nevada.net.nz> To: Mike Tancsa <mike@sentex.net> Cc: freebsd-stable@freebsd.org Subject: Re: Intel 6300ESB (ICH) SMBus controller not working Message-ID: <b2f76f46515c71406dd432f80c32d819@nevada.net.nz> In-Reply-To: <6.2.1.2.0.20050411223651.04f62e18@64.7.153.2> References: <d2f6dbc5642c1f7400d70b44250c999b@nevada.net.nz> <6.2.1.2.0.20050411223651.04f62e18@64.7.153.2>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12/04/2005, at 2:38 PM, Mike Tancsa wrote: > At 09:24 PM 11/04/2005, Philip Murray wrote: >> Hi, >> >> I'm running RELENG_5 on a Dell PowerEdge 750 and the ichsmb driver >> doesn't want to work with it, I get the following on boot: >> >> ichsmb0: <Intel 6300ESB (ICH) SMBus controller> port 0x8c0-0x8df irq >> 17 at device 31.3 on pci0 >> device_attach: ichsmb0 attach returned 6 > > Does it work if you add > > debug.acpi.disabled="sysresource" > > to /boot/loader.conf > > Thanks for that, It kind of worked. Am I correct in thinking that, that prevents ACPI attaching to the controller so that the ichsmb driver can? In which case, if ACPI does attach to it, does that mean I'd get temperature values in the hw.acpi.thermal tree? sysutils/xmbmon and sysutils/healthd can't seem to read anything from it anyway. Is this because the SMBus has no temperature sensors tied to it? It has them in the BIOS, so I assumed I could read them in FreeBSD. I get ichsmb0: irq 0x04 during -1 in dmesg when trying healthd and root@alexis:~/ > healthd -S ioctl(SMB_WRITEB): Permission denied Cheers, Phil
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b2f76f46515c71406dd432f80c32d819>