Re: [coreboot] H8DME-2 woes, hints?
Joe Korty joe.ko...@ccur.com writes: As a first time coreboot user, I thought that I should first try it out on a supported board. That way I would learn the ropes a bit before even thinking about doing something more challenging. Naturally I am having troubles. I suspect that as a newbie I am probably doing something stupid. But then I've heard that mb manufacturers like to change things around without notice, so maybe I'm doing things right and what was once a supported mb, no longer is. The hardware: SuperMicro H8DME-2. Four 1Gbyte DDR2-667/533/400 Registered ECC SDRAM sticks from Crucial. Two Quad-Core AMD 2378 2.4 GHz Processors. Onboard video. One SATA disk. One PATA DVD-ROM reader. NULL modem serial cable from COM1 to COM1 on another PC. The details: When booting coreboot, nothing happens for about 45 seconds. Then the fans speed up to high and some messages start appearing on the serial line. These messages print rather slowly (maybe 1 second/message). They are: coreboot-4.0-r5521M Wed May 5 10:53:42 EDT 2010 starting... *sysinfo range: [000cf000,000cf730] bsp_apicid=00 Enabling routing table for node 00 done. Enabling SMP settings (0,1) link=00 This looks like the bootup code for gen f Opterons. It doesn't look like the h8dme has a fam10 variant yet, which is what you need for the 2378 CPUs. -- Arne. -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] H8DME-2 woes, hints?
On Fri, May 07, 2010 at 05:57:35AM -0400, Arne Georg Gleditsch wrote: Joe Korty joe.ko...@ccur.com writes: As a first time coreboot user, I thought that I should first try it out on a supported board. That way I would learn the ropes a bit before even thinking about doing something more challenging. Naturally I am having troubles. I suspect that as a newbie I am probably doing something stupid. But then I've heard that mb manufacturers like to change things around without notice, so maybe I'm doing things right and what was once a supported mb, no longer is. The hardware: SuperMicro H8DME-2. Four 1Gbyte DDR2-667/533/400 Registered ECC SDRAM sticks from Crucial. Two Quad-Core AMD 2378 2.4 GHz Processors. Onboard video. One SATA disk. One PATA DVD-ROM reader. NULL modem serial cable from COM1 to COM1 on another PC. The details: When booting coreboot, nothing happens for about 45 seconds. Then the fans speed up to high and some messages start appearing on the serial line. These messages print rather slowly (maybe 1 second/message). They are: coreboot-4.0-r5521M Wed May 5 10:53:42 EDT 2010 starting... *sysinfo range: [000cf000,000cf730] bsp_apicid=00 Enabling routing table for node 00 done. Enabling SMP settings (0,1) link=00 This looks like the bootup code for gen f Opterons. It doesn't look like the h8dme has a fam10 variant yet, which is what you need for the 2378 CPUs. Thanks Arne! I'll have to figure out how to proceed from here. On a side note, it _looks_ like the slowdown might be due to the udelay unification. Still bisecting. Joe -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] H8DME-2 woes, hints?
The hardware: SuperMicro H8DME-2. Four 1Gbyte DDR2-667/533/400 Registered ECC SDRAM sticks from Crucial. Two Quad-Core AMD 2378 2.4 GHz Processors. Onboard video. One SATA disk. One PATA DVD-ROM reader. NULL modem serial cable from COM1 to COM1 on another PC. The details: When booting coreboot, nothing happens for about 45 seconds. Then the fans speed up to high and some messages start appearing on the serial line. These messages print rather slowly (maybe 1 second/message). They are: coreboot-4.0-r5521M Wed May 5 10:53:42 EDT 2010 starting... *sysinfo range: [000cf000,000cf730] bsp_apicid=00 Enabling routing table for node 00 done. Enabling SMP settings (0,1) link=00 This looks like the bootup code for gen f Opterons. It doesn't look like the h8dme has a fam10 variant yet, which is what you need for the 2378 CPUs. Thanks Arne! I'll have to figure out how to proceed from here. On a side note, it _looks_ like the slowdown might be due to the udelay unification. Still bisecting. I'm surprised you found a revision that works, since it has never supported fam10. I think it would be more fruitful for you to look at one of the boards that has both fam10 and k8 support, and try to put together an h8dme_fam10 port. Thanks, Myles -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] H8DME-2 woes, hints?
On Fri, May 07, 2010 at 07:30:08AM -0600, Myles Watson wrote: This looks like the bootup code for gen f Opterons. It doesn't look like the h8dme has a fam10 variant yet, which is what you need for the 2378 CPUs. Thanks Arne! I'll have to figure out how to proceed from here. On a side note, it _looks_ like the slowdown might be due to the udelay unification. Still bisecting. I'm surprised you found a revision that works, since it has never supported fam10. I think it would be more fruitful for you to look at one of the boards that has both fam10 and k8 support, and try to put together an h8dme_fam10 port. For the record, I've been trying to get that going for a while, but have not had much success - very early hangs in the fam10 code on this board. Cf. the problems Knut is having, I think... 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
Re: [coreboot] H8DME-2 woes, hints?
On Fri, May 07, 2010 at 07:30:08AM -0600, Myles Watson wrote: This looks like the bootup code for gen f Opterons. It doesn't look like the h8dme has a fam10 variant yet, which is what you need for the 2378 CPUs. Thanks Arne! I'll have to figure out how to proceed from here. On a side note, it _looks_ like the slowdown might be due to the udelay unification. Still bisecting. I'm surprised you found a revision that works, since it has never supported fam10. I think it would be more fruitful for you to look at one of the boards that has both fam10 and k8 support, and try to put together an h8dme_fam10 port. For the record, I've been trying to get that going for a while, but have not had much success - very early hangs in the fam10 code on this board. Cf. the problems Knut is having, I think... Sorry I forgot that. The Supermicro names all blend together for me. Have you tried adding the extra bits to the masks in resourcemap.c? Thanks, Myles -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] H8DME-2 woes, hints?
On Wed, May 05, 2010 at 04:26:15PM -0400, Myles Watson wrote: On Wed, May 5, 2010 at 2:06 PM, Joe Korty joe.ko...@ccur.comwrote: Naturally I am having troubles. I suspect that as a newbie I am probably doing something stupid. But then I've heard that mb manufacturers like to change things around without notice, so maybe I'm doing things right and what was once a supported mb, no longer is. It looks like you're doing things right. It's dying really early, though. When booting coreboot, nothing happens for about 45 seconds. Then the fans speed up to high and some messages start appearing on the serial line. These messages print rather slowly (maybe 1 second/message). They are: coreboot-4.0-r5521M Wed May 5 10:53:42 EDT 2010 starting... *sysinfo range: [000cf000,000cf730] bsp_apicid=00 Enabling routing table for node 00 done. Enabling SMP settings (0,1) link=00 You could try an earlier revision. I can't think of what would slow it down that much. I put some printk's in setup_smb2, the crashing routine. They show that setup_temp_row is called by setup_smb2 but never returns. Since it takes so long to get there, I think you'll have better luck trying to figure out what's wrong before that. fgrep 'Video ROM' /proc/iomem # displays 000c-000cafff : Video ROM sudo dd if=/dev/mem of=/tmp/vgabios.bin bs=4k skip=$((0xc0)) count=$((0xb)) # --- figure out the Video ROM's PCI Vendor,Device ID # --- I _think_ the numbers I want are the second set shown, ie 15d9:1611. You want the first set. The second set is Supermicro's board ID. Hi Myles, Thanks for the pointers. I'm going to try some earlier releases of coreboot and if I can find one that lacks the slowdown. If that fails I am going to have to figure out how to debug the earliest stages of coreboot, when nothing is visible and little can be saved. Joe -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
[coreboot] H8DME-2 woes, hints?
As a first time coreboot user, I thought that I should first try it out on a supported board. That way I would learn the ropes a bit before even thinking about doing something more challenging. Naturally I am having troubles. I suspect that as a newbie I am probably doing something stupid. But then I've heard that mb manufacturers like to change things around without notice, so maybe I'm doing things right and what was once a supported mb, no longer is. The hardware: SuperMicro H8DME-2. Four 1Gbyte DDR2-667/533/400 Registered ECC SDRAM sticks from Crucial. Two Quad-Core AMD 2378 2.4 GHz Processors. Onboard video. One SATA disk. One PATA DVD-ROM reader. NULL modem serial cable from COM1 to COM1 on another PC. The details: When booting coreboot, nothing happens for about 45 seconds. Then the fans speed up to high and some messages start appearing on the serial line. These messages print rather slowly (maybe 1 second/message). They are: coreboot-4.0-r5521M Wed May 5 10:53:42 EDT 2010 starting... *sysinfo range: [000cf000,000cf730] bsp_apicid=00 Enabling routing table for node 00 done. Enabling SMP settings (0,1) link=00 At this point coreboot ceases to make forward progress. The fans remain spinning at their highest settings. The VGA screen is blank throughout. I put some printk's in setup_smb2, the crashing routine. They show that setup_temp_row is called by setup_smb2 but never returns. Anyways, I've attached the entire build procedure I used to achieve these results. Perhaps there is something in this sequence that I am doing wrong??? And, what kind of luck have others had with recent H8DME-2 boards? Regards, Joe # install RHEL5 32-bit on H8DME-2 test stand # log in as myself # --- make flashrom(1) tool cd svn co svn://coreboot.org/flashrom/trunk flashrom cd flashrom make sudo make install # --- get latest coreboot sources cd .. svn co svn://coreboot.org/coreboot/trunk coreboot cd coreboot # --- get pre-built SeaBIOS coreboot payload wget -O payload.elf http://linuxtogo.org/~kevin/SeaBIOS/bios.bin.elf-0.6.0 # --- extract H8DME-2's onboard Video ROM fgrep 'Video ROM' /proc/iomem # displays 000c-000cafff : Video ROM sudo dd if=/dev/mem of=/tmp/vgabios.bin bs=4k skip=$((0xc0)) count=$((0xb)) # --- figure out the Video ROM's PCI Vendor,Device ID # --- I _think_ the numbers I want are the second set shown, ie 15d9:1611. lspci -v | fgrep VGA # displays 01:05.0 VGA compatible controller: ATI Technologies Inc ES1000 ... lspci -vn | fgrep -A1 01:05.0 # displays 01:05.0 0300: 1002:515e (rev 02) Subsystem: 15d9:1611 # --- build-n-burn coreboot make menuconfig # select Mainboard - SuperMicro - H8DME-2 # select Payload - Add A Payload - ELF # select VGA Bios - Add A VGA BIOS - VGA Device PCI IDS - 15d9,1611 make /usr/local/sbin/flashrom -w build/coreboot.rom -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] H8DME-2 woes, hints?
On Wed, May 5, 2010 at 2:06 PM, Joe Korty joe.ko...@ccur.com wrote: As a first time coreboot user, I thought that I should first try it out on a supported board. That way I would learn the ropes a bit before even thinking about doing something more challenging. Naturally I am having troubles. I suspect that as a newbie I am probably doing something stupid. But then I've heard that mb manufacturers like to change things around without notice, so maybe I'm doing things right and what was once a supported mb, no longer is. It looks like you're doing things right. It's dying really early, though. The details: When booting coreboot, nothing happens for about 45 seconds. Then the fans speed up to high and some messages start appearing on the serial line. These messages print rather slowly (maybe 1 second/message). They are: coreboot-4.0-r5521M Wed May 5 10:53:42 EDT 2010 starting... *sysinfo range: [000cf000,000cf730] bsp_apicid=00 Enabling routing table for node 00 done. Enabling SMP settings (0,1) link=00 You could try an earlier revision. I can't think of what would slow it down that much. At this point coreboot ceases to make forward progress. The fans remain spinning at their highest settings. The VGA screen is blank throughout. I put some printk's in setup_smb2, the crashing routine. They show that setup_temp_row is called by setup_smb2 but never returns. Since it takes so long to get there, I think you'll have better luck trying to figure out what's wrong before that. # --- extract H8DME-2's onboard Video ROM fgrep 'Video ROM' /proc/iomem # displays 000c-000cafff : Video ROM sudo dd if=/dev/mem of=/tmp/vgabios.bin bs=4k skip=$((0xc0)) count=$((0xb)) # --- figure out the Video ROM's PCI Vendor,Device ID # --- I _think_ the numbers I want are the second set shown, ie 15d9:1611. You want the first set. The second set is Supermicro's board ID. lspci -v | fgrep VGA # displays 01:05.0 VGA compatible controller: ATI Technologies Inc ES1000 ... lspci -vn | fgrep -A1 01:05.0 # displays 01:05.0 0300: 1002:515e (rev 02) Subsystem: 15d9:1611 Good luck, Myles -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
