Am 07.07.2012 10:25 schrieb Stefan Tauner:
> Happy day of redundancy day!
> Signed-off-by: Stefan Tauner <stefan.tauner(a)student.tuwien.ac.at>
Sir, hats off to you, sir! Your brilliantly stated brilliant comment
wins you one shippable internet, ready to be shipped over the net.
I am trying to flash Coreboot BIOS in Windows XP SP3 environment. but I got No EEPROM/flash device found when running flashrom.exe.
I have been successfully flashed BIOS in CentOS environment on the same machine by running ./flashrom -w coreboot.rom.
Does anyone know why I get this error message?
Currently README mentions some but not all options needed to get
flashrom compiled on a libpci-less system. This patch adds all of
Signed-off-by: Paul Fertser <fercerpav(a)gmail.com>
README | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/README b/README
index f88b3b5..88cc782 100644
@@ -120,8 +120,9 @@ Processor architecture dependent features:
On non-x86 architectures you have to disable a few programmers because they
use port-based I/O which is not directly available on non-x86. Please add
- CONFIG_RAYER_SPI=no CONFIG_NIC3COM=no CONFIG_ATAHPT=no CONFIG_NICREALTEK=no \
+ CONFIG_RAYER_SPI=no CONFIG_NIC3COM=no CONFIG_GFXNVIDIA=no CONFIG_SATASII=no \
+ CONFIG_ATAHPT=no CONFIG_DRKAISER=no CONFIG_NICREALTEK=no CONFIG_NICNATSEMI=no \
+ CONFIG_NICINTEL=no CONFIG_NICINTEL_SPI=no CONFIG_OGP_SPI=no CONFIG_SATAMV=no
as parameters to the "make" invocation.
Besides that, the internal programmer is only supported on x86 and MIPS. On
other architectures, please add
2012/7/1 Steven Williams <prodigiouslogic(a)gmail.com>:
> Marcos, thanks for the quick response! I searched all over for that line
> before, don't know how I missed it before :( In the svn make file as of
> 7-28-2012 it is located at line 553. It compiled without error and it almost
> executed. It was compiled with a 2.6 kernel but the machine I am trying to
> run it on has a 2.4 kernel and it segfaulted. I am probably making a mistake
> again or have overlooked a possible simple solution. I searched all over
> google for a quick fix but found none. Any pointers on that? As a last
> resort I think I am going to setup a debian 3.0 box to see if it will
> compile and run.
Your libc requires a 2.6 kernel to run ("file flashrom" to see what
version). With some pain you can build a separate toolchain targeting
Linux 2.4, but probably the easiest option is set up an old
distribution and compile flashrom there.
Please use "reply to all" in your email client, otherwise your
messages will not go to the mailing list.
2012/6/30 Steven Williams <prodigiouslogic(a)gmail.com>:
> I had a quick and probably dumb question, where in 'make' can I change the
> parameters so flashrom will compile as a static or stand alone binary? I
> found an old email where Gianluigi Tiesi
> says(http://firstname.lastname@example.org/msg05104.html) to add
> -static to the end of the cc list in his example but I cannot find anything
> that resembles it in the current make file. I looked at the instructions for
> the DOS compile but I was not sure if I needed to use this method and if I
> could even add all the lib headers required to run flashrom. I am trying to
> run flashrom on a thin client so I can install an updated version of Linux.
> Right now they only run a custom Linux build that uses a 2.4 kernel and I
> would like to have the system open to run an updated kernel and software. I
> do believe a bootstrap or lilo configuration is in place but I will not know
> for sure to modify it until I have the ability to read and write to the
> bios. It would be great if this program was more standalone centric since a
> full blown os is not always available.
> So some pointers or advice would be awesome, thanks in advance!
I'm using this and it works fine.
--- Makefile.orig 2012-01-13 09:19:59.388190891 -0200
+++ Makefile 2012-01-13 09:21:49.489193337 -0200
@@ -531 +531 @@
- $(CC) $(LDFLAGS) -o $(PROGRAM)$(EXEC_SUFFIX) $(OBJS) $(FEATURE_LIBS) $(LIBS)
+ $(CC) $(LDFLAGS) -o $(PROGRAM)$(EXEC_SUFFIX) $(OBJS) $(FEATURE_LIBS)
$(LIBS) -lz -static
You'll need static libraries to link against. On Fedora they are in
the following packages: glibc-static, zlib-static,