linux-kernel - Re: Intel DG965WH / Case 745-44-22 (slow bios/upgrade) [UPDATE] / Intel, status of HECI support patch for the kernel?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 1 Jul 2008 14:43:49 -0400 (EDT)
From:	Justin Piszcz <jpiszcz@...idpixels.com>
To:	crmotherboard@...lbox.intel.com,
	Jesse Barnes <jesse.barnes@...el.com>,
	Dan Williams <dan.j.williams@...el.com>
cc:	linux-kernel@...r.kernel.org, lm-sensors@...sensors.org
Subject: Re: Intel DG965WH / Case 745-44-22 (slow bios/upgrade) [UPDATE] /
 Intel, status of HECI support patch for the kernel?



On Mon, 30 Jun 2008, Justin Piszcz wrote:

> Hello,
>
> I have two revisions of the 965WH motherboard, one that supports dual-core 
> only and another quad-core.
>
> I have an E6300 in the old one and a Q6600 in the new one with 4GiB and 8GiB 
> of RAM respectively.
>
> I would like to report a success and also a bug with BIOS 1738.
>
> The success is this case can be resolved, the Linux/memory/mapping is correct 
> now and I no longer have to use mem="8832M" in my LILO configuration to avoid 
> the bios setting memory that is not cachable.
>
> However, on my new revision 965WH (I did not check with my old motherboard), 
> that supports the quad-core CPU, I went into the BIOS and went to the [Hard 
> Disks] option and when I selected it, the part of the screen that should 
> update showing me the hard disks in the system was blank, I could not escape 
> out of the bios or go to another menu, I had to reboot to get back into the 
> bios.  This is not normal behavior, can someone at Intel attach 1-6 (I use 6) 
> WD Veliciraptor 300GiB drives to this motherboard to replicate the problem if
> it is not obvious in the code/bios how to fix it?  I cannot view the hard 
> disks in that menu, I believe its the 2nd or 3rd menu over when you initially 
> enter the BIOS.  I do not recall if this problem existed prior to 1738.
>
> Also, people have e-mailed me in relation to my posts and I am curious as 
> well
> to follow up, when will the HECI/fan/voltage sensor support (that is a 
> project
> at Intel) be merged into the kernel tree so that lm sensors will eventually 
> be
> able to read these values?
>
> This is from 2007:
> http://softwareblogs.intel.com/2007/04/13/intel-me-interface-heci-now-available/
>
> Their updated project page:
> http://www.openamt.org/
>
> Justin.
>

The issue regarding accessing the hard drive menu was fixed by simpling 
power cycling/rebooting the host.

All issues are now resolved (regarding the slow speed/memory/etc)..

Only other question left is the HECI support in the kernel.

Justin.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/