Hi all,
I am not sure if this is true. I just tried current coreboot source tree (revision 6084) for ASUS M2V-MX SE, it cannot boot. It could compile successfully, and it will be dead at the beginning when booting. Below are the info from serial port:
coreboot-4.0-r6070M Wed Nov 17 16:20:19 EST 2010 starting... now booting...
INIT detected from --- { APICID = 00 NODEID = 00 COREID = 00} ---
Issuing SOFT_RESET... soft reset
I also compiled old versions, it could boot. such as version 5555(I just random picked up and tested it)
I am wondering if there is anyone has some problem?
Best, Fengwei
* Fengwei Zhang namedylan@gmail.com [101117 22:41]:
Hi all,
I am not sure if this is true. I just tried current coreboot source tree (revision 6084) for ASUS M2V-MX SE, it cannot boot. It could compile successfully, and it will be dead at the beginning when booting. Below are the info from serial port:
coreboot-4.0-r6070M Wed Nov 17 16:20:19 EST 2010 starting... now booting...
INIT detected from --- { APICID = 00 NODEID = 00 COREID = 00} ---
Issuing SOFT_RESET... soft reset
I also compiled old versions, it could boot. such as version 5555(I just random picked up and tested it)
I am wondering if there is anyone has some problem?
Can you please find out which revision broke it?
Stefan
The broken version is 6062, version 6061 is good. there is the diff
http://tracker.coreboot.org/trac/coreboot/changeset?old_path=%2Ftrunk&ol...
Best, Fengwei
On 11/17/2010 06:08 PM, Stefan Reinauer wrote:
- Fengwei Zhangnamedylan@gmail.com [101117 22:41]:
Hi all,
I am not sure if this is true. I just tried current coreboot source tree (revision 6084) for ASUS M2V-MX SE, it cannot boot. It could compile successfully, and it will be dead at the beginning when booting. Below are the info from serial port:
coreboot-4.0-r6070M Wed Nov 17 16:20:19 EST 2010 starting... now booting...
INIT detected from --- { APICID = 00 NODEID = 00 COREID = 00} ---
Issuing SOFT_RESET... soft reset
I also compiled old versions, it could boot. such as version 5555(I just random picked up and tested it)
I am wondering if there is anyone has some problem?
Can you please find out which revision broke it?
Stefan
CCing author and reviewer.. Tobias, Peter, any idea?
* Fengwei Zhang namedylan@gmail.com [101118 01:24]:
The broken version is 6062, version 6061 is good. there is the diff
http://tracker.coreboot.org/trac/coreboot/changeset?old_path=%2Ftrunk&ol...
Best, Fengwei
On 11/17/2010 06:08 PM, Stefan Reinauer wrote:
- Fengwei Zhangnamedylan@gmail.com [101117 22:41]:
Hi all,
I am not sure if this is true. I just tried current coreboot source tree (revision 6084) for ASUS M2V-MX SE, it cannot boot. It could compile successfully, and it will be dead at the beginning when booting. Below are the info from serial port:
coreboot-4.0-r6070M Wed Nov 17 16:20:19 EST 2010 starting... now booting...
INIT detected from --- { APICID = 00 NODEID = 00 COREID = 00} ---
Issuing SOFT_RESET... soft reset
I also compiled old versions, it could boot. such as version 5555(I just random picked up and tested it)
I am wondering if there is anyone has some problem?
Can you please find out which revision broke it?
Stefan
-- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
That looks very unlikely to be the real rootcause I think. For the M2V-MX SE the added code path shouldn't be taken anyway. And given that you do get output on the serial console the bootblock should be working just fine I think.
Fengwei: Can you check that reverting just the bootblock.c changes from the current revision fixes it? I think it's more likely that the changes to src/southbridge/via/vt8237r/vt8237r_early_smbus.c cause the problem.
Tobias
Stefan Reinauer wrote:
CCing author and reviewer.. Tobias, Peter, any idea?
- Fengwei Zhang namedylan@gmail.com [101118 01:24]:
The broken version is 6062, version 6061 is good. there is the diff
http://tracker.coreboot.org/trac/coreboot/changeset?old_path=%2Ftrunk&ol...
Best, Fengwei
On 11/17/2010 06:08 PM, Stefan Reinauer wrote:
- Fengwei Zhangnamedylan@gmail.com [101117 22:41]:
Hi all,
I am not sure if this is true. I just tried current coreboot source tree (revision 6084) for ASUS M2V-MX SE, it cannot boot. It could compile successfully, and it will be dead at the beginning when booting. Below are the info from serial port:
coreboot-4.0-r6070M Wed Nov 17 16:20:19 EST 2010 starting... now booting...
INIT detected from --- { APICID = 00 NODEID = 00 COREID = 00} ---
Issuing SOFT_RESET... soft reset
I also compiled old versions, it could boot. such as version 5555(I just random picked up and tested it)
I am wondering if there is anyone has some problem?
Can you please find out which revision broke it?
Stefan
-- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
-- coresystems GmbH • Brahmsstr. 16 • D-79104 Freiburg i. Br. Tel.: +49 761 7668825 • Fax: +49 761 7664613 Email: info@coresystems.de • http://www.coresystems.de/ Registergericht: Amtsgericht Freiburg • HRB 7656 Geschäftsführer: Stefan Reinauer • Ust-IdNr.: DE245674866
Yes, I just checked reverting the bootblock.c changes from the current revision. it fixes the problem.
Best, Fengwei
On 11/18/2010 08:18 AM, Tobias Diedrich wrote:
That looks very unlikely to be the real rootcause I think. For the M2V-MX SE the added code path shouldn't be taken anyway. And given that you do get output on the serial console the bootblock should be working just fine I think.
Fengwei: Can you check that reverting just the bootblock.c changes from the current revision fixes it? I think it's more likely that the changes to src/southbridge/via/vt8237r/vt8237r_early_smbus.c cause the problem.
Tobias
Stefan Reinauer wrote:
CCing author and reviewer.. Tobias, Peter, any idea?
- Fengwei Zhangnamedylan@gmail.com [101118 01:24]:
The broken version is 6062, version 6061 is good. there is the diff
http://tracker.coreboot.org/trac/coreboot/changeset?old_path=%2Ftrunk&ol...
Best, Fengwei
On 11/17/2010 06:08 PM, Stefan Reinauer wrote:
- Fengwei Zhangnamedylan@gmail.com [101117 22:41]:
Hi all,
I am not sure if this is true. I just tried current coreboot source tree (revision 6084) for ASUS M2V-MX SE, it cannot boot. It could compile successfully, and it will be dead at the beginning when booting. Below are the info from serial port:
coreboot-4.0-r6070M Wed Nov 17 16:20:19 EST 2010 starting... now booting...
INIT detected from --- { APICID = 00 NODEID = 00 COREID = 00} ---
Issuing SOFT_RESET... soft reset
I also compiled old versions, it could boot. such as version 5555(I just random picked up and tested it)
I am wondering if there is anyone has some problem?
Can you please find out which revision broke it?
Stefan
-- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
-- coresystems GmbH • Brahmsstr. 16 • D-79104 Freiburg i. Br. Tel.: +49 761 7668825 • Fax: +49 761 7664613 Email: info@coresystems.de • http://www.coresystems.de/ Registergericht: Amtsgericht Freiburg • HRB 7656 Geschäftsführer: Stefan Reinauer • Ust-IdNr.: DE245674866
hi,
This is strange. Can you check what code romcc generated?
Also a assembly check would be nice. I seem to have kind of dejavu although i dont recall what it was ;)
Thanks, Rudolf
Hi
Just for a record I use the latest version without problems. Maybe your binutils/gcc is wrong? What distribution/version you use?
Thanks, Rudolf