coreboot

coreboot@coreboot.org

39717 discussions

Re: [LinuxBIOS] Is this system supported? SUN FIRE X4100
by Lu, Yinghai 11 Apr '06

11 Apr '06

What OS are you going to use? Things to be checked 1. settings for to make management card working 2. Is the LSI FW on BIOS flash or another separate flash? 3. Boot from SAS raid directly? We may need to use big IDE flash for using tiny kernel and kexec... YH -----Original Message----- From: linuxbios-bounces(a)linuxbios.org [mailto:linuxbios-bounces@linuxbios.org] On Behalf Of Frank Rust Sent: Monday, April 10, 2006 12:42 AM To: linuxbios(a)linuxbios.org Subject: [LinuxBIOS] Is this system supported? SUN FIRE X4100 Is this one supported, or might become supported soon? System SUN FIRE X4100 Mainboard manufacturer: (SUN?) Processor: one or two Opteron or Opteron Dual Core Chipset: AMD 8131, AMD 8111 IO: quad channel SAS raid (LSI SAS 1064) Net: 2 dual 10/100/1000 Ethernet Controllers (Intel FW82546 GB NIC) Video: ATI Rage XL Floppy Disc, legacy Serial: SMSC LPC47B272 Super IO Controller (additional: Management: Motorola MPC8248PowerPC Processor) Supported OS: Solaris 10 x64, RedHat Enterprise Linux 3.0-4.0, SUSE Linux Enterprise Server 9, MS Windows Server 2003 (Documentation: white paper: http://www.sun.com/servers/entry/x4100/arch-wp.pdf) Best regards, Frank. -- ________________________________________________________________________ Frank Rust, Technische Universität, Institut für Theoretische Informatik Tel.: +49 531 391 9525 Postfach 3329, D-38023 Braunschweig Fax.: +49 531 391 9529 Mühlenpfordtstr. 22-23, D-38106 Braunschweig -- linuxbios mailing list linuxbios(a)linuxbios.org http://www.openbios.org/mailman/listinfo/linuxbios

4 4

[LinuxBIOS] some more tyan/s2881 questions
by Ward Vandewege 11 Apr '06

11 Apr '06

So the board is stable now. That's great. Some observations: 1. 'halt' no longer powers the machine off, which it does with the proprietary bios. 'halt -p' does the job though. LinuxBIOS oddity? 2. reboots seem to cause problems sometimes. I'm not sure yet what causes this, but I've had problems with the machine hanging after ACPI: Unable to locate RSDP It normally sits there for a few seconds, but I had the machine in such a state that it simply hung at that point. This may have had something to do with the IPMI card, which I'm experimenting with. I had to unplug the power before this problem went away, a cold restart didn't help. I will do more testing to see if I can pinpoint this. Thanks for all your help so far! Ward. -- Ward Vandewege <ward(a)fsf.org> Free Software Foundation - Senior System Administrator

1 0

Re: [LinuxBIOS] Is this system supported? SUN FIRE X4100
by Lu, Yinghai 10 Apr '06

10 Apr '06

1. Is there anything special in BIOS to be done for making serial over LAN or IPMI over LAN working with your BMC daughter card...? I mean connection to NIC shared or I2C. 2. Good to hear that separated FLASH for LSI... 3. Can you check the protocol for USB that BMC simulated? OHCI or UHCI or EHCI only? YH -----Original Message----- From: Duncan Laurie [mailto:dlaurie@google.com] Sent: Monday, April 10, 2006 11:13 AM To: Lu, Yinghai Cc: Frank Rust; linuxbios(a)linuxbios.org Subject: Re: [LinuxBIOS] Is this system supported? SUN FIRE X4100 On Mon, 10 Apr 2006, Lu, Yinghai wrote: > What OS are you going to use? > > Things to be checked > 1. settings for to make management card working Nothing required IIRC, but optional features such as the boot mailbox are available. The service processor does not have an RTC so it relies on the BIOS to set its time with Set SEL Time command but this could be easily done after boot with the OpenIPMI driver and ipmitool script. Flash of system BIOS can be done through the service processor as it has hooks into the LPC bus (system must be in reset for this to work). This means a LinuxBIOS port would not be overly dangerous since you can always flash a working BIOS by reloading SP firmware (which includes a system BIOS). > 2. Is the LSI FW on BIOS flash or another separate flash? > 3. Boot from SAS raid directly? We may need to use big IDE flash for using tiny kernel and kexec... > LSI firmware is on a separate flash. Disk boot will be tricky but getting network boot working should be easier. Boot over redirected USB via service processor might also work... -duncan

2 1

Re: [LinuxBIOS] CONFIG_LB_MEM_TOPK
by Lu, Yinghai 10 Apr '06

10 Apr '06

1. Can you make one elf image with mkelfImage ( combine the kernel and initrd)? 2. use latest kernel + suse rescue disk to make on elf to check your /dev/md3... YH -----Original Message----- From: Ward Vandewege [mailto:ward@gnu.org] Sent: Friday, April 07, 2006 1:55 PM To: Lu, Yinghai Cc: linuxbios(a)linuxbios.org Subject: Re: [LinuxBIOS] CONFIG_LB_MEM_TOPK On Fri, Apr 07, 2006 at 01:37:06PM -0700, Lu, Yinghai wrote: > I fixed one merge typo in > src/southbride/amd/amd8111/amd8111_early_ctrl.c > > Please change 15 to 11 at line 13. OK; did that, but it did not help. Same problem still. Ward. -- Ward Vandewege <ward(a)fsf.org> Free Software Foundation - Senior System Administrator

3 8

Re: [LinuxBIOS] CONFIG_LB_MEM_TOPK (and a patch)
by Alan Mimms 10 Apr '06

10 Apr '06

One side comment from a lurker on this list. Your experience with the error hang after your login prompt (prints message like the one below) LinuxBIOS-1.1.8_s2881_Fallback Fri Apr 7 18:06:33 EDT 2006 starting... (0,1) link=00 (1,0) link=00 02 nodes initialized. SBLink=02 NC node|link=02 reminded me of something I found and fixed a couple of weeks ago. The board hangs when it does a warm reset on a bus error condition. This is due to a typo in the code in src/northbridge/amdk8/incoherent_ht.c in the function ht_setup_chainx (base indentation removed for clarity): if (ctrl & ((1 << 4) | (1 << 8))) { /* * Either the link has failed, or we have * a CRC error. * Sometimes this can happen due to link * retrain, so lets knock it down and see * if its transient */ --> ctrl |= ((1 << 6) | (1 <<8)); // Link fail + Crc pci_write_config16(udev, upos + LINK_CTRL(uoffs), ctrl); ctrl = pci_read_config16(udev, upos + LINK_CTRL(uoffs)); if (ctrl & ((1 << 4) | (1 << 8))) { print_err("Detected error on Hypertransport Link\n"); break; } } The line (marked with "-->" above) where the error bits to be cleared are set to '1' ctrl |= ((1 << 6) | (1 <<8)); // Link fail + Crc SHOULD be ctrl |= ((1 << 4) | (1 <<8)); // Link fail + Crc The code should be setting the 1<<4 bit (so as to clear one of the error bits) instead of 1<<6 (the read only bit that signals end of HT bus chain). After making this change, your board won't hang when the BIOS or Linux detects a need to reboot due to some fatal error. This is a pretty trivial change to an error case that hardly ever occurs but was crucial for us. I claim this change is safe and correct and should be merged into the main line code. Cheers, and thanks to all you who work so hard for all of the good and useful LinuxBIOS code. We have been very successful with it thus far in our project. Alan Mimms, Senior Architect F5 Networks, Inc. Spokane Development Center 1322 North Whitman Lane Liberty Lake, Washington 99019 v: 509-343-3524 f: 509-343-3501 -----Original Message----- From: linuxbios-bounces(a)linuxbios.org [mailto:linuxbios-bounces@linuxbios.org] On Behalf Of Ward Vandewege Sent: Friday, April 07, 2006 3:15 PM To: Lu, Yinghai Cc: linuxbios(a)linuxbios.org Subject: Re: [LinuxBIOS] CONFIG_LB_MEM_TOPK On Fri, Apr 07, 2006 at 02:02:47PM -0700, Lu, Yinghai wrote: > 1. Can you make one elf image with mkelfImage ( combine the kernel and > initrd)? OK; this is what I've done: 1. Retrieved the mkelfImage program (v2.7) from ftp://ftp.lnxi.com 2. mkelfImage --command-line="ro root=/dev/md3 quiet splash console=tty0 console=ttyS0,115200n8" \ --kernel="/boot/vmlinuz-2.6.12-9-amd64-generic" \ --initrd="/boot/initrd.img-2.6.12-9-amd64-generic" \ --output="/boot/linuxbios_2.6.12-9-amd64-generic.elf" 3. Adjusted etherboot-5.4.1/file/Config AUTOBOOT_FILE = "hde1:/linuxbios_2.6.12-9-amd64-generic.elf" 4. cd etherboot-5.4.1/src make bin/tg3--filo.elf 5. Adjusted targets/tyan/s2881/Config.lb to point to the new payload (tg3--filo.elf) 6. Tried booting - it actually got to a login prompt this time, but as I hit enter on the kbd, it crashed again. Log is attached. So that did not help. I'm going to try your next suggestion now. Thanks, Ward. > 2. use latest kernel + suse rescue disk to make on elf to check your > /dev/md3... > > YH > > > -----Original Message----- > From: Ward Vandewege [mailto:ward@gnu.org] > Sent: Friday, April 07, 2006 1:55 PM > To: Lu, Yinghai > Cc: linuxbios(a)linuxbios.org > Subject: Re: [LinuxBIOS] CONFIG_LB_MEM_TOPK > > On Fri, Apr 07, 2006 at 01:37:06PM -0700, Lu, Yinghai wrote: > > I fixed one merge typo in > > src/southbride/amd/amd8111/amd8111_early_ctrl.c > > > > Please change 15 to 11 at line 13. > > OK; did that, but it did not help. Same problem still. > > Ward. > > -- > Ward Vandewege <ward(a)fsf.org> > Free Software Foundation - Senior System Administrator > > > > -- > linuxbios mailing list > linuxbios(a)linuxbios.org > http://www.openbios.org/mailman/listinfo/linuxbios > > > !DSPAM:4436d470278011542430122! > -- Ward Vandewege <ward(a)fsf.org> Free Software Foundation - Senior System Administrator

2 1

[LinuxBIOS] Is this system supported? SUN FIRE X4100
by Frank Rust 10 Apr '06

10 Apr '06

Is this one supported, or might become supported soon? System SUN FIRE X4100 Mainboard manufacturer: (SUN?) Processor: one or two Opteron or Opteron Dual Core Chipset: AMD 8131, AMD 8111 IO: quad channel SAS raid (LSI SAS 1064) Net: 2 dual 10/100/1000 Ethernet Controllers (Intel FW82546 GB NIC) Video: ATI Rage XL Floppy Disc, legacy Serial: SMSC LPC47B272 Super IO Controller (additional: Management: Motorola MPC8248PowerPC Processor) Supported OS: Solaris 10 x64, RedHat Enterprise Linux 3.0-4.0, SUSE Linux Enterprise Server 9, MS Windows Server 2003 (Documentation: white paper: http://www.sun.com/servers/entry/x4100/arch-wp.pdf) Best regards, Frank. -- ________________________________________________________________________ Frank Rust, Technische Universität, Institut für Theoretische Informatik Tel.: +49 531 391 9525 Postfach 3329, D-38023 Braunschweig Fax.: +49 531 391 9529 Mühlenpfordtstr. 22-23, D-38106 Braunschweig

3 2

[LinuxBIOS] SockelA Mainboards supporting LinuxBIOS
by Art Tevs 08 Apr '06

08 Apr '06

Hi, folks! I am new in the "Linux on BIOS" section. But I like it :-) Does there exists SockelA (AMD Athlon XP) mainboards that are supported by the linuxbios project? On the homepage there is no such boards listed. I think each board that has removeable BIOS chip should be able to support linux. I mean it should be possible to write new version of LinuxBIOS for such a board. Or do I think wrong? Thanks! ___________________________________________________________ Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de

2 1

Re: [LinuxBIOS] CONFIG_LB_MEM_TOPK (and a patch)
by Lu, Yinghai 08 Apr '06

08 Apr '06

You are right. It should be 4 instead of 6.... YH -----Original Message----- From: Alan Mimms [mailto:a.mimms@f5.com] Sent: Friday, April 07, 2006 4:00 PM To: Ward Vandewege; Lu, Yinghai Cc: linuxbios(a)linuxbios.org Subject: RE: [LinuxBIOS] CONFIG_LB_MEM_TOPK (and a patch) One side comment from a lurker on this list. Your experience with the error hang after your login prompt (prints message like the one below) LinuxBIOS-1.1.8_s2881_Fallback Fri Apr 7 18:06:33 EDT 2006 starting... (0,1) link=00 (1,0) link=00 02 nodes initialized. SBLink=02 NC node|link=02 reminded me of something I found and fixed a couple of weeks ago. The board hangs when it does a warm reset on a bus error condition. This is due to a typo in the code in src/northbridge/amdk8/incoherent_ht.c in the function ht_setup_chainx (base indentation removed for clarity): if (ctrl & ((1 << 4) | (1 << 8))) { /* * Either the link has failed, or we have * a CRC error. * Sometimes this can happen due to link * retrain, so lets knock it down and see * if its transient */ --> ctrl |= ((1 << 6) | (1 <<8)); // Link fail + Crc pci_write_config16(udev, upos + LINK_CTRL(uoffs), ctrl); ctrl = pci_read_config16(udev, upos + LINK_CTRL(uoffs)); if (ctrl & ((1 << 4) | (1 << 8))) { print_err("Detected error on Hypertransport Link\n"); break; } } The line (marked with "-->" above) where the error bits to be cleared are set to '1' ctrl |= ((1 << 6) | (1 <<8)); // Link fail + Crc SHOULD be ctrl |= ((1 << 4) | (1 <<8)); // Link fail + Crc The code should be setting the 1<<4 bit (so as to clear one of the error bits) instead of 1<<6 (the read only bit that signals end of HT bus chain). After making this change, your board won't hang when the BIOS or Linux detects a need to reboot due to some fatal error. This is a pretty trivial change to an error case that hardly ever occurs but was crucial for us. I claim this change is safe and correct and should be merged into the main line code. Cheers, and thanks to all you who work so hard for all of the good and useful LinuxBIOS code. We have been very successful with it thus far in our project. Alan Mimms, Senior Architect F5 Networks, Inc. Spokane Development Center 1322 North Whitman Lane Liberty Lake, Washington 99019 v: 509-343-3524 f: 509-343-3501 -----Original Message----- From: linuxbios-bounces(a)linuxbios.org [mailto:linuxbios-bounces@linuxbios.org] On Behalf Of Ward Vandewege Sent: Friday, April 07, 2006 3:15 PM To: Lu, Yinghai Cc: linuxbios(a)linuxbios.org Subject: Re: [LinuxBIOS] CONFIG_LB_MEM_TOPK On Fri, Apr 07, 2006 at 02:02:47PM -0700, Lu, Yinghai wrote: > 1. Can you make one elf image with mkelfImage ( combine the kernel and > initrd)? OK; this is what I've done: 1. Retrieved the mkelfImage program (v2.7) from ftp://ftp.lnxi.com 2. mkelfImage --command-line="ro root=/dev/md3 quiet splash console=tty0 console=ttyS0,115200n8" \ --kernel="/boot/vmlinuz-2.6.12-9-amd64-generic" \ --initrd="/boot/initrd.img-2.6.12-9-amd64-generic" \ --output="/boot/linuxbios_2.6.12-9-amd64-generic.elf" 3. Adjusted etherboot-5.4.1/file/Config AUTOBOOT_FILE = "hde1:/linuxbios_2.6.12-9-amd64-generic.elf" 4. cd etherboot-5.4.1/src make bin/tg3--filo.elf 5. Adjusted targets/tyan/s2881/Config.lb to point to the new payload (tg3--filo.elf) 6. Tried booting - it actually got to a login prompt this time, but as I hit enter on the kbd, it crashed again. Log is attached. So that did not help. I'm going to try your next suggestion now. Thanks, Ward. > 2. use latest kernel + suse rescue disk to make on elf to check your > /dev/md3... > > YH > > > -----Original Message----- > From: Ward Vandewege [mailto:ward@gnu.org] > Sent: Friday, April 07, 2006 1:55 PM > To: Lu, Yinghai > Cc: linuxbios(a)linuxbios.org > Subject: Re: [LinuxBIOS] CONFIG_LB_MEM_TOPK > > On Fri, Apr 07, 2006 at 01:37:06PM -0700, Lu, Yinghai wrote: > > I fixed one merge typo in > > src/southbride/amd/amd8111/amd8111_early_ctrl.c > > > > Please change 15 to 11 at line 13. > > OK; did that, but it did not help. Same problem still. > > Ward. > > -- > Ward Vandewege <ward(a)fsf.org> > Free Software Foundation - Senior System Administrator > > > > -- > linuxbios mailing list > linuxbios(a)linuxbios.org > http://www.openbios.org/mailman/listinfo/linuxbios > > > !DSPAM:4436d470278011542430122! > -- Ward Vandewege <ward(a)fsf.org> Free Software Foundation - Senior System Administrator

1 0

Re: [LinuxBIOS] CONFIG_LB_MEM_TOPK
by Lu, Yinghai 08 Apr '06

08 Apr '06

device pnp 2e.3 off # Com2 ===> device pnp 2e.3 on # Com2 -----Original Message----- From: Ward Vandewege [mailto:ward@gnu.org] Sent: Friday, April 07, 2006 3:46 PM To: Lu, Yinghai Cc: linuxbios(a)linuxbios.org; Ronald G Minnich Subject: Re: [LinuxBIOS] CONFIG_LB_MEM_TOPK On Fri, Apr 07, 2006 at 03:38:05PM -0700, Lu, Yinghai wrote: > What is the T0 in your /etc/inittab? It puts the console on com2, which is probably why it is failing. > Also com2 is disabled in LB, and Linux bring it out ? > > So can you enable the com2 in your MB Config.lb, 2e.3 off==> 2e.3 on... Can you give me an example of the exact line to add to Config.lb? It doesn't have any serial configuration in it right now. Thanks, Ward. -- Ward Vandewege <ward(a)fsf.org> Free Software Foundation - Senior System Administrator

1 0

Re: [LinuxBIOS] CONFIG_LB_MEM_TOPK
by Lu, Yinghai 08 Apr '06

08 Apr '06

What is the T0 in your /etc/inittab? Also com2 is disabled in LB, and Linux bring it out ? So can you enable the com2 in your MB Config.lb, 2e.3 off==> 2e.3 on... YH

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

coreboot