Yesterday I dug up a whole lot of stuff and I was able to see my x4100. Next time I should be able to get it home. Sorry for the delay.
On Fri, Nov 30, 2007 at 02:21:54AM -0500, Daniel Ouellet wrote: > Stuart Henderson wrote: >> On 2007/11/28 21:00, Daniel Ouellet wrote: >>> Stuart Henderson wrote: >>>> Well, it's certainly a bit odd that amd64 doesn't detect the ipmi, and i386 >>>> does... I don't really have any other clues though :( >> >> Ah. It's not odd at all... >> >> ---------------------------- >> revision 1.139 >> date: 2006/06/01 00:35:51; author: beck; state: Exp; lines: +2 -2 >> Disable ipmi in GENERIC for the moment - it breaks too much stuff >> on any of my sun amd64's as well as other ones (hp). We can re-enable >> it again when marco fixes it to be stable. >> >> ok deraadt@ and the crocodile hunter.. >> ---------------------------- >> >> /me crawls back under rock. > > I did many tests and even if that was disable, it was turn back on > > Revision 1.148 > Thu Aug 3 18:19:04 2006 UTC > Re-enable IPMI. Tested by beck & ckuethe prompted by deraadt > > Then off again by Theo > Revision 1.203 > Thu Nov 15 22:21:31 2007 UTC > enable most acpi functionality by default. now instead of 'enable > acpi', you use 'disable acpi' or 'disable apm' withn you encounter > problems (depending on which kind of problems). if we work hard enough, > this can remain the situation by the time we ship the next release. > otherwise, we will re-disable acpi... so let's crackin' > > No note for the ipmi issue in this commit as to if there is still issue or > not however. So, I guess there is. > > Anyway, I try to enable it and it does show in the dmesg as before. > > So, I guess for the crash in writing, I am back to the driver I guess. > > I spend the last two days on the ipmi stuff testing, etc to see why it was > gone. So, now I know, but it doesn't help more, however, I can't say it > hurt either now. So, if there is some tests that may be needed, I could do > that for sure. if that help. > > Thanks > > Daniel
