On Thu, Feb 5, 2009 at 7:42 PM, David Melik wrote:
> Thanks again (Myles & everyone) for discussing coreboot for s4882 until I
> could compile & install. After doing so, my s4882 just has a blank screen
Do you have a null-modem cable? Did you see anything on the serial console?
> and continual
> -Original Message-
> From: Carl-Daniel Hailfinger [mailto:c-d.hailfinger.devel.2...@gmx.net]
> Sent: Thursday, February 05, 2009 4:19 PM
> To: Myles Watson
> Cc: Coreboot
> Subject: Re: [coreboot] flashrom: Can't mmap memory
>
> On 05.02.2009 21:26, Myles Watson wrote:
> > When I boot
On 06.02.2009 02:52, ron minnich wrote:
> On Thu, Feb 5, 2009 at 5:43 PM, wrote:
>
>
>> I ask my colleague who work for EFI. He said in his EFI project, SMM
>> area should not be cached, and he had tried to cache that area, but
>> cause system crashed.
>> I don't know if he is right, since I
Thanks again (Myles & everyone) for discussing coreboot for s4882 until I
could compile & install. After doing so, my s4882 just has a blank screen
and continually does 2 alternating beeps (like a siren.)
I saw no POST codes on coreboot.org. I saved coreboot.rom and now have a
Slackware pII syst
On Thu, Feb 5, 2009 at 5:43 PM, wrote:
> I ask my colleague who work for EFI. He said in his EFI project, SMM
> area should not be cached, and he had tried to cache that area, but
> cause system crashed.
> I don't know if he is right, since I can not find any reason why SMM
> area should not be
-jasonzhao
> -Original Message-
> From: Kevin O'Connor [mailto:ke...@koconnor.net]
> Sent: Thursday, February 05, 2009 9:37 PM
> To: Jason Zhao
> Cc: coreboot@coreboot.org
> Subject: Re: [coreboot] FW: Two test result(linux+2G-RAM>10minutes
andinstall
> ubuntu8.10) of vx800 patch
>
> O
On 05.02.2009 21:26, Myles Watson wrote:
> When I boot using the factory BIOS on my s2895 flashrom works. When I
> boot with Coreboot, I get the Error:
>
> Can't mmap memory using /dev/mem: Operation not permitted
>
> It shouldn't be kernel parameters since I'm using the same grub2 entry
> to boot
Peter Stuge wrote:
> > Can't mmap memory using /dev/mem: Operation not permitted
>
> I have seen this once before, in a system with a custom BIOS.
Should mention that it was resolved with lseek()+read() instead of
mmap().
//Peter
--
coreboot mailing list: coreboot@coreboot.org
http://www.coreb
Myles Watson wrote:
> When I boot using the factory BIOS on my s2895 flashrom works. When I
> boot with Coreboot, I get the Error:
>
> Can't mmap memory using /dev/mem: Operation not permitted
Please try this with the latest revision, which will have a slightly
better error message.
> This sou
ron minnich writes:
> On Tue, Feb 3, 2009 at 7:55 AM, Peter Stuge wrote:
>> Piotr Brostovski wrote:
>>> I'm asking myself if it is possible that mkelfImage simply isn't
>>> compatible with current gPXE releases?
>>
>> mkelfImage is strictly for Linux.
>>
>> Upstream gPXE can not be built for cor
When I boot using the factory BIOS on my s2895 flashrom works. When I
boot with Coreboot, I get the Error:
Can't mmap memory using /dev/mem: Operation not permitted
It shouldn't be kernel parameters since I'm using the same grub2 entry
to boot either way.
This sounds a little too familiar, but
On Mon, Feb 2, 2009 at 9:01 AM, Dan Lykowski wrote:
> CoreBoot Kernel Log:
> [0.412025] PCI: Bridge: :00:01.0
> [0.416027] IO window: 1000-1fff
> [0.420032] MEM window: 0xfc50-0xfc6f
> [0.427975] PREFETCH window: 0xf000- 0xf7ff
> [0.440
On Thu, Feb 5, 2009 at 5:43 PM, wrote:
> Erasing flash chip... Some block protection in effect, disabling
> Invalid OPCODE 0x50
> spi_write_status_enable failed
> spi_disable_blockprotect failed
IIRC that "block protection" is implemented by the flash chip. If
opcode 0x50 succeeded, erase may wo
Hi there folks,
my name is Jiri Svoboda, of HelenOS project. While it delights us that Coreboot
makes use of some of our code, I'd like to warn you that the memxxx()
operations in libpayload/libc/memory.c you copied from the HelenOS C library
are terribly flawed. They have been fixed in HelenO
Kevin O'Connor wrote:
On Thu, Feb 05, 2009 at 11:33:02AM +0800, jasonz...@viatech.com.cn wrote:
My VX800 bug of "boot linux with 2G mem >10 minutes" has been proved to
be the problem of MTRR setting. Thanks for Carldani, Rudolf and Bari.
1 The root cause is:
1) The free memory I report to coreb
On Thu, Feb 05, 2009 at 11:33:02AM +0800, jasonz...@viatech.com.cn wrote:
> My VX800 bug of "boot linux with 2G mem >10 minutes" has been proved to
> be the problem of MTRR setting. Thanks for Carldani, Rudolf and Bari.
> 1 The root cause is:
> 1) The free memory I report to coreboot through ram_r
On Thu, Feb 05, 2009 at 01:43:23PM +0100, Rudolf Marek wrote:
>> We have been working on the RS780/SB700 for about 2 weeks. Before we can
>> submit our code, we realized that it doesn't make sense if the
>> documentation is not available.
>
> Well it does. Sometimes code is better than nothing ;)
Hi,
We have been working on the RS780/SB700 for about 2 weeks. Before we can
submit our code, we realized that it doesn't make sense if the
documentation is not available.
Well it does. Sometimes code is better than nothing ;)
We can get the datasheet as an AMD
engineer. How can the develop
18 matches
Mail list logo