Am 07.03.2010 15:40, schrieb Stefan Reinauer:
Ron and Peter should like this Panic Room there you go.
It's of course completely useless if the machine hangs. It could be made
part of die() though.
Maybe guard the Kconfig option with depends on CONFIG_EXPERT?
With or without, it's
Hi,
I finally know that my issue must be related with the smbus registers
because on a vendor bios running machine and using i2cdetect and i2cdump
I get several values for different i2c devices detected, I get the same
values when I successfully start with coreboot. But when I start with
coreboot
Dear Knut,
Am Mittwoch, den 10.03.2010, 17:26 +0100 schrieb Knut Kujat:
[…]
I know that because I found a nice piece of code dumping smbus registers
on the h8dme board :D thx to the autor!!
is it possible to share that piece of code?
[…]
Anyway, nice to hear you ar making some progress
I think every UEFI/EFI implementation will boot to old school boot
mode when it can't find any EFI/UEFI-compliant
boot-device/boot-partition. It would take too long though but at least
the fallback is there.
-Darmawan
On 3/9/10, Ed Swierk eswi...@aristanetworks.com wrote:
On Fri, Mar 5, 2010 at
On 3/9/10, Ed Swierk eswi...@aristanetworks.com wrote:
On Fri, Mar 5, 2010 at 8:58 AM, ron minnich rminn...@gmail.com wrote:
Just got a new nehalem box in for test yesterday. Experiences so far:
1. POST from power-on takes 45 seconds. *45 SECONDS*. Now, I had it
said to me at SCALE7x last
Hi guys,
I posted a new 440BX RAM init code a few days ago that was segfaulting
romcc, and I didn't get any response.
In the meantime I have narrowed the cause to this code fragment, with enough
wrapper added so it can be fed to romcc on its own:
void romcc_fail(void) {
int dimm03 = 0;
int
6 matches
Mail list logo
