Re: [coreboot] Seabios problems
patching file src/biosvar.h Hunk #1 FAILED at 97. patch: malformed patch at line 45: // Accessor functions Could you send me your patch file please ? Mine is definitely out. Message du 21/01/10 à 00h58 De : Kevin O'Connor ke...@koconnor.net A : conged...@voila.fr Copie à : seab...@seabios.org, coreboot coreboot@coreboot.org Objet : Re: [coreboot] Seabios problems On Wed, Jan 20, 2010 at 05:46:25PM +0100, conged...@voila.fr wrote: Hello, I can't apply the diff to the biosvar.h, so I do it by hand. All other diffs applied correctly. I've confirmed that the patch I sent applies cleanly: git clone git://git.linuxtogo.org/home/kevin/seabios.git cd seabios patch -p1 /path/to/ps2.patch make Please retry. Thanks, -Kevin -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot Je m’évite la cohue dans les magasins et je profite des petits prix sur http://shopping.voila.fr -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
[coreboot] Memtest86+ failing on coreboot system.
Hello, I've finally got my board working with Coreboot now I started to stress test the whole system to know if it is stable. Now, when I'm trying to test my memory with Memtest86+ it doesn't starts! instead it shows correct information about my cpus and caches but at Memory there is just a 0K and in the middle of the screen a 0K LxBIOS what is that mean? After waiting a few minutes I'm getting the whole screen full of rubbish symbols and than the monitors goes off. I already tried several versions of memtest86+ without luck. I know there is a payload with Memtest86+ I haven't tried yet but I just don't think it will make any difference, won't it? THX, Knut Kujat -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] Memtest86+ failing on coreboot system.
can you remind us what hardware this is? ron -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] The default value of TOM (MSRC001_001A) just after Power-On
On Wed, Jan 20, 2010 at 2:13 AM, Darmawan Salihun darmawan.sali...@gmail.com wrote: The default value of MSRC001_001A (Top of Memory below the 4GB limit) according to BKDG for AMD Fam 10h rev. 3.06 is undefined (after Reset/power-on). However, AMD64 Architecture Programmer's Manual Volume 2: System Programming Rev. 3.14 states that the value of MSRC001_001A after Reset or power on is: __0400_h Which one of this information is correct? I need to know it because I want to know what is the default MMIO range after reset. Hi Darmawan, I think that the BKDG is correct. I get 000_0001F_7780_ on a K8. You can take a look at cpu/amd/car/cache_as_ram.inc for the initial setup. Marc -- http://se-eng.com -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] Memtest86+ failing on coreboot system.
Knut Kujat wrote: Now, when I'm trying to test my memory with Memtest86+ it doesn't starts! How are you trying to start it? I know there is a payload with Memtest86+ I haven't tried yet but I just don't think it will make any difference, won't it? Using memtest as payload is the only way I have tried, and it works for me. Feel free to grab http://stuge.se/memtest.elf and try if using that as payload works any better. //Peter -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] Memtest86+ failing on coreboot system.
Hi, sorry, of course. I did the necessary changes on the alrady existing supermicro h8dmr_fam10 board to make it work on a h8qme_fam10. Supermicro H8QME-2+ 4 CPUs (Opterons) 16 GB ram MCP55 PRO AMD 8132 I used the memtest that comes with the OPENSuse 11.2 installation CD I also installed memtest to my grub boot menu. Seems like memtest doesn't find any memory at all?! But linux boots fine and recognized the whole memory amount. I already did some benchmarks and they finished without any problems. thx. can you remind us what hardware this is? ron -- Knut Kujat -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] Memtest86+ failing on coreboot system.
memtest in many ways is not my favorite program. I would rather have a simple non-GUI tester, because in the past I've had trouble with it (it can fail) when it did not like the device it was trying to do its GUI on. Also, the way memtest finds top of memory can fail on some chipsets. Have not seen that for a while but I did see it. No idea if any of this is your problem but ... ron -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] Memtest86+ failing on coreboot system.
OK, thx anyway. I found another one memtester 4.1 usable from linux so it won't test the whole amount but memtest86 doesn't either :P. bye! memtest in many ways is not my favorite program. I would rather have a simple non-GUI tester, because in the past I've had trouble with it (it can fail) when it did not like the device it was trying to do its GUI on. Also, the way memtest finds top of memory can fail on some chipsets. Have not seen that for a while but I did see it. No idea if any of this is your problem but ... ron -- Knut Kujat -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] Memtest86+ failing on coreboot system.
Ah, ok! I'll try this. At least now I know from you and ron that it isn't necessary my ram thats failing. thx a lot! Knut. I used the memtest that comes with the OPENSuse 11.2 installation CD I also installed memtest to my grub boot menu. Seems like memtest doesn't find any memory at all?! But linux boots fine and recognized the whole memory amount. I already did some benchmarks and they finished without any problems. Your problem sounds very similar to the one I had. Memtest looks to see if you have LinuxBIOS tables, but doesn't support tables in high memory, so it fails. Since you are using SeaBIOS, you'd prefer that it used the BIOS tables. I modified SeaBIOS to destroy the marker for the LinuxBIOS tables after reading them (since they are no longer useful.) It's a hack, but it's quick and easy. Suggestions: Use a similar hack to destroy the signature so Memtest doesn't get confused Use a version of Memtest that already supports high tables. Thanks, Myles -- Knut Kujat -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] Memtest86+ failing on coreboot system.
I used the memtest that comes with the OPENSuse 11.2 installation CD I also installed memtest to my grub boot menu. Seems like memtest doesn't find any memory at all?! But linux boots fine and recognized the whole memory amount. I already did some benchmarks and they finished without any problems. Your problem sounds very similar to the one I had. Memtest looks to see if you have LinuxBIOS tables, but doesn't support tables in high memory, so it fails. Since you are using SeaBIOS, you'd prefer that it used the BIOS tables. I modified SeaBIOS to destroy the marker for the LinuxBIOS tables after reading them (since they are no longer useful.) It's a hack, but it's quick and easy. Suggestions: Use a similar hack to destroy the signature so Memtest doesn't get confused Use a version of Memtest that already supports high tables. Thanks, Myles -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] Memtest86+ failing on coreboot system.
On Fri, Jan 22, 2010 at 12:09:59AM +0100, Knut Kujat wrote: sorry, of course. I did the necessary changes on the alrady existing supermicro h8dmr_fam10 board to make it work on a h8qme_fam10. I'm interested in your port. It should go into the tree. Do you want to send a patch to the list? Thanks, Ward. -- Ward Vandewege w...@fsf.org Free Software Foundation - Senior Systems Administrator -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
[coreboot] FOSDEM DevRoom schedule completed.
http://www.coreboot.org/FOSDEM_2010 Schedule is now complete: * 13:00 : Peter Stuge - coreboot introduction. * 14:00 : Peter Stuge - coreboot and PC technical details. * 15:00 : Rudolf Marek - ACPI and Suspend/Resume under coreboot. * 16:00 : Rudolf Marek - coreboot board porting. * 17:00 : Carl-Daniel Hailfinger - Flashrom. * 18:00 : Luc Verhaegen - Flash Enable BIOS Reverse Engineering. Hope to see tons of people there. Luc Verhaegen. -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] [flashrom] FOSDEM DevRoom schedule completed.
On 22.01.2010 02:48, Luc Verhaegen wrote: http://www.coreboot.org/FOSDEM_2010 Schedule is now complete: * 13:00 : Peter Stuge - coreboot introduction. * 14:00 : Peter Stuge - coreboot and PC technical details. * 15:00 : Rudolf Marek - ACPI and Suspend/Resume under coreboot. * 16:00 : Rudolf Marek - coreboot board porting. * 17:00 : Carl-Daniel Hailfinger - Flashrom. * 18:00 : Luc Verhaegen - Flash Enable BIOS Reverse Engineering. Thank you very much for all the work you put into organizing the devroom! Regards, Carl-Daniel -- Developer quote of the year: We are juggling too many chainsaws and flaming arrows and tigers. -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] The default value of TOM (MSRC001_001A) just after Power-On
Hi Mark, Thanks. I'll have a look. -Darmawan On 1/22/10, Marc Jones marcj...@gmail.com wrote: On Wed, Jan 20, 2010 at 2:13 AM, Darmawan Salihun darmawan.sali...@gmail.com wrote: The default value of MSRC001_001A (Top of Memory below the 4GB limit) according to BKDG for AMD Fam 10h rev. 3.06 is undefined (after Reset/power-on). However, AMD64 Architecture Programmer's Manual Volume 2: System Programming Rev. 3.14 states that the value of MSRC001_001A after Reset or power on is: __0400_h Which one of this information is correct? I need to know it because I want to know what is the default MMIO range after reset. Hi Darmawan, I think that the BKDG is correct. I get 000_0001F_7780_ on a K8. You can take a look at cpu/amd/car/cache_as_ram.inc for the initial setup. Marc -- http://se-eng.com -- Regards, Darmawan Salihun -= Human knowledge belongs to the world =- -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
