coreboot May 2006

coreboot@coreboot.org

50 participants
101 discussions

Re: [LinuxBIOS] s2881 fan control
by Lu, Yinghai 11 May '06

11 May '06

init() in amd8111_acpi.c YH -----Original Message----- From: Ward Vandewege [mailto:ward@gnu.org] Sent: Thursday, May 11, 2006 1:45 PM To: Stefan Reinauer Cc: linuxbios(a)linuxbios.org; Lu, Yinghai Subject: Re: [LinuxBIOS] s2881 fan control On Tue, May 09, 2006 at 03:05:07PM -0400, Ward Vandewege wrote: ... lspci output ... > But there are actually quite a few other differences throughout the file, > which surprises me a litte. Lots of differences in the various northbridge > entries, and even the network cards and the sata controller. Is this normal? A followup on this. First of all, I didn't realize that the PCI configuration space is dynamic - things change all the time. Secondly; > 0000:01:04.3 Bridge: Advanced Micro Devices [AMD] AMD-8111 ACPI (rev 05) ... snip ... > -f0: 19 5f 3b 00 00 00 00 00 00 00 00 00 00 00 00 00 > +f0: c3 ad 1e 00 00 00 00 00 00 00 00 00 00 00 00 00 As it turns out, those three bytes change constantly, so I guess they are not significant. Also, I missed one byte that IS consistently different after a boot with the proprietary BIOS: 0000:01:04.3 Bridge: Advanced Micro Devices [AMD] AMD-8111 ACPI (rev 05) ... -40: 80 f1 00 04 00 00 00 00 20 14 50 00 00 00 00 00 +40: 80 f1 00 07 00 00 00 00 20 14 50 00 00 00 00 00 How would I go about changing that byte during the LinuxBIOS boot? Do I need to edit resourcemap.c in src/mainboard/tyan/s2881? Thanks, Ward. -- Ward Vandewege <ward(a)fsf.org> Free Software Foundation - Senior System Administrator

1 0

Re: [LinuxBIOS] New guy in LinuxBios
by Lu, Yinghai 11 May '06

11 May '06

Comment out several lines about links in resourcemap.c. Current inherent_ht.c already could probe the links automatically... amd/Serengeti_leopard is good model. If you want mptable and irqtable and acpitable create automatically. YH ________________________________ From: linuxbios-bounces(a)linuxbios.org [mailto:linuxbios-bounces@linuxbios.org] On Behalf Of Vincente Tsou Sent: Thursday, May 11, 2006 2:31 AM To: linuxbios(a)linuxbios.org Subject: [LinuxBIOS] New guy in LinuxBios Hello LinuxBios elders, I'm sorry to bother you. I'm begining to study LinuxBios and I have some problem in it. Hope you can give me some idea. My target board is an AMD Opteron (chipset: K8 / 8111 / 8131) mainboard, it is similar to Tyan s2880 / s2881 / s2882. So I base on Tyan s2880 to change some config file to compile a linuxbios.rom, but it doesn't work. Following is what do I changed in s2880: 1. I changed the payload path in targets/tyan/s2880/Config.lb. 2. modify src/mainboard/tyan/s2880/Config.lb as 42812-pci.txt. ( as attachment ) I don't know is it correct that I modified. If you have interest you can refer to Attachment. 3. generated irq_tables.c by getpir.c and replaced the original one. compile and burn it in rom. After I boot up the target board, it always alert emergency beep. Then, I unmark some debug message in 'src/northbridge/amd/amdk8/raminit.c' to see where is it hang. The last step is hang on setup_default_resource_map() in 'src/mainboard/tyan/s2880/cache_as_ram_auto.c', I can see it from serial console ( as attachment again. ) Is there any configuration I should change, and I didn't do ? How can I debug it ? Thanks a lot. -- Best Regards, Vincente Tsou Engineer R/D, S/W Dept. NEXCOM International Co. Tel: 886-2-82280606 Ext. 3205 Fax: 886-2-82280506 E-mail: vincentetsou(a)nexcom.com.tw Web: http://www.nexcom.com.tw/

2 1

[LinuxBIOS] New guy in LinuxBios
by Vincente Tsou 11 May '06

11 May '06

Hello LinuxBios elders, I'm sorry to bother you. I'm begining to study LinuxBios and I have some problem in it. Hope you can give me some idea. My target board is an AMD Opteron (chipset: K8 / 8111 / 8131) mainboard, it is similar to Tyan s2880 / s2881 / s2882. So I base on Tyan s2880 to change some config file to compile a linuxbios.rom, but it doesn't work. Following is what do I changed in s2880: 1. I changed the payload path in targets/tyan/s2880/Config.lb. 2. modify src/mainboard/tyan/s2880/Config.lb as 42812-pci.txt. ( as attachment ) I don't know is it correct that I modified. If you have interest you can refer to Attachment. 3. generated irq_tables.c by getpir.c and replaced the original one. compile and burn it in rom. After I boot up the target board, it always alert emergency beep. Then, I unmark some debug message in 'src/northbridge/amd/amdk8/raminit.c' to see where is it hang. The last step is hang on setup_default_resource_map() in 'src/mainboard/tyan/s2880/cache_as_ram_auto.c', I can see it from serial console ( as attachment again. ) Is there any configuration I should change, and I didn't do ? How can I debug it ? Thanks a lot. -- Best Regards, Vincente Tsou Engineer R/D, S/W Dept. NEXCOM International Co. Tel: 886-2-82280606 Ext. 3205 Fax: 886-2-82280506 E-mail: vincentetsou(a)nexcom.com.tw Web: http://www.nexcom.com.tw/

2 1

[LinuxBIOS] I give up -- time for a new plan.
by Eric Poulsen 10 May '06

10 May '06

I've been researching the IDE/DMA/Linux issue that appears to plague the VT8235 southbridge. Seems there is _no_ reliable fix for this issue, which has been known to exhibit itself even in Windows if you're using the old/stock via drivers. Even if I do get the LB issues figured out, the DMA issue (as far as I can tell) is _unfixable_. Reliability is a huge thing for me (hence the use of Linux). The Epia board is bound for Ebay. Here's the big question: Can someone recommend a _NON-VIA_ small form factor motherboard (mini-itx, preferrably), that has all the usual goodies (IDE,USB,VGA,serial, etc) that is known to work well with LinuxBios? Naturally, one without a VIA chipset?

6 7

[LinuxBIOS] svn logs
by Richard Smith 09 May '06

09 May '06

Going back and looking at the logfiles it seems we havn't done a very good job of detailing things when they get changed. ie a log commit that just says: 'fixes' Dosen't really tell you much. Say when you are reviewing the logs a year later to try and find possible areas that might have busted a board. I think a little more verbosity in the logs for future commits would help a bit. At least some more verbosity when you think you have fixed up things to a point that they work. -- Richard A. Smith

1 0

[LinuxBIOS] No VGA with EPIA-MII 6000
by scott 08 May '06

08 May '06

I am getting to grips with flashing my bios. I have followed the documentation in the EPIA_M HOWTO and I have flashed a couple bios'es and my epia still works, so far so good. I do not want a serial console (I have the serial port connected to the car, so I dont want stuff going down there), but I would like a VGA console. I copied the Config.vga.filo as it comes from svn to Config.lb (just changing the path to filo.elf), but I get this after running buildtarget, then make: "XIP_ROM_BASE is not a multiple of XIP_ROM_SIZE" make[1]: *** [auto.inc] Error 1 make[1]: Leaving directory `/home/scott/ibus/bios/LinuxBIOSv2/targets/via/epia-m/epia-m/normal' make: *** [normal/linuxbios.rom] Error 1 So I went back to my Config.lb which did work (but with no VGA) and I changed: < option CONFIG_CONSOLE_SERIAL8250=1 --- > option CONFIG_CONSOLE_SERIAL8250=0 > option CONFIG_CONSOLE_VGA=1 in an attempt to turn off serial console and turn on the VGA console, this builds fine, and boots, but with no VGA output. I think I am missing a trick here? Anyone have a Config file for the EPIA M II 6000 with VGA enabled? My Config file is below: # Sample config file for EPIA-M # This will make a target directory of ./epia-m target epia-m mainboard via/epia-m option MAXIMUM_CONSOLE_LOGLEVEL=8 option DEFAULT_CONSOLE_LOGLEVEL=8 option CONFIG_CONSOLE_SERIAL8250=0 option CONFIG_CONSOLE_VGA=1 option ROM_SIZE=256*1024 option HAVE_OPTION_TABLE=1 option CONFIG_ROM_STREAM=1 option HAVE_FALLBACK_BOOT=1 ### ### Compute the location and size of where this firmware image ### (linuxBIOS plus bootloader) will live in the boot rom chip. ### option FALLBACK_SIZE=0x30000 ## LinuxBIOS C code runs at this location in RAM option _RAMBASE=0x00004000 # ### ### Compute the start location and size size of ### The linuxBIOS bootloader. ### # # EPIA-M # #romimage "normal" # option USE_FALLBACK_IMAGE=0 # option ROM_IMAGE_SIZE=0xc000 # option ROM_SECTION_OFFSET=0x10000 # option ROM_SECTION_SIZE=0x18000 # option XIP_ROM_BASE=0xfffd0000 # option LINUXBIOS_EXTRA_VERSION=".0Normal" # payload /usr/share/etherboot/5.1.9pre2-lnxi-lb/tg3--ide_disk.zelf # payload ../../../../tg3--ide_disk.zelf # payload ../../../../../lnxieepro100.ebi # payload /filo.elf #end romimage "fallback" option USE_FALLBACK_IMAGE=1 option ROM_IMAGE_SIZE=0x10000 option ROM_SECTION_OFFSET=0x10000 option ROM_SECTION_SIZE=0x30000 # option XIP_ROM_BASE=0xfffe0000 option LINUXBIOS_EXTRA_VERSION=".0Fallback" # payload /usr/share/etherboot/5.1.9pre2-lnxi-lb/tg3--ide_disk.zelf # payload ../../../../tg3--ide_disk.zelf # payload ../../../../../lnxieepro100.ebi payload /home/scott/ibus/bios/filo-0.5/filo.elf end buildrom ./linuxbios.rom ROM_SIZE "fallback"

1 0

Re: [LinuxBIOS] [linuxbios-checkins] r2301 - trunk/LinuxBIOSv2/src/cpu/amd/model_gx2
by Stefan Reinauer 07 May '06

07 May '06

* svn(a)openbios.org <svn(a)openbios.org> [060506 04:54]: > Modified: > trunk/LinuxBIOSv2/src/cpu/amd/model_gx2/vsmsetup.c > Log: > Use a real variable to configure rom base for vsa ... > > > Modified: trunk/LinuxBIOSv2/src/cpu/amd/model_gx2/vsmsetup.c > =================================================================== > --- trunk/LinuxBIOSv2/src/cpu/amd/model_gx2/vsmsetup.c 2006-05-06 02:35:08 UTC (rev 2300) > +++ trunk/LinuxBIOSv2/src/cpu/amd/model_gx2/vsmsetup.c 2006-05-06 02:54:45 UTC (rev 2301) > + //rom = 0xfffc0000; > + /* the VSA starts at the base of rom - 128k */ > + rom = ((unsigned long) 0) - (ROM_SIZE + 128*1024); dumb question: Since this is in the CPU code and not motherboard specific, should this be a config variable, in case someone uses different VSMs? Or are they always 128k? Stefan -- coresystems GmbH • Brahmsstr. 16 • D-79104 Freiburg i. Br. Tel.: +49 761 7668825 • Fax: +49 761 7664613 Email: info(a)coresystems.de • http://www.coresystems.de/

2 1

Re: [LinuxBIOS] State of vt8237 and consequently epia-ms
by Samet, Matt 06 May '06

06 May '06

Hi Adam - I'd like to start looking into the VT8237 myself. If possible, could I get that VT8237 doc from you? And possibly your WIP code? I can start to take a look, I have some time. Thanks... -=matt -----Original Message----- From: linuxbios-bounces(a)linuxbios.org [mailto:linuxbios-bounces@linuxbios.org] On Behalf Of Adam Talbot Sent: Saturday, April 29, 2006 12:37 PM To: Andy Somerville Cc: linuxbios(a)linuxbios.org Subject: Re: [LinuxBIOS] State of vt8237 and consequently epia-ms -Andy Currently the is no support for the vt8237. What would it take to support? Some one who has a few weeks to work on it. I spent a few weeks, but was never able to get the console running. With out that, I had no way of doing debugging. My board does not have any PCI slots, so I was unable to use a post card to debug. -Adam Andy Somerville wrote: > Hi all, > > > Im new to linuxbios and the mailing list so please excuse any > newbie stupidity. I was wondering about the state of vt8237 > southbridge support. From my limited understanding of linuxBios this > is virtually all that is missing for Epia-MS support since CLE266 > northbridge is already supported. > > I saw a post in february which mentioned vt8237 and that it was being > worked on, but I have seen nothing since. Forgive me if Ive missed > something. > > So I guess my overall question is: Is Epia-MS support a near > possiblity, and what would it take to produce? > > > Andy > > -- linuxbios mailing list linuxbios(a)linuxbios.org http://www.openbios.org/mailman/listinfo/linuxbios

2 1

[LinuxBIOS] FILO build error
by scott 06 May '06

06 May '06

Hi, I am new to this project, but I want to flash my EPIA MII 6000 to get better boot times. I have downloaded filo (0.5) and have edited the Config file to remove GRUB because I dont want a menu, I just want it to boot a single image which I understand to be the autoboot option. I get this error when I run make: ld -N -T i386/ldscript -o filo main/builtin.o main/grub/builtin.o fs/builtin.o drivers/builtin.o drivers/usb/builtin.o i386/builtin.o /usr/lib/gcc-lib/i486-slackware-linux/3.2.3/libgcc.a drivers/usb/builtin.o(.text+0xcb): In function `dump_td': : undefined reference to `grub_strcpy' drivers/usb/builtin.o(.text+0x19d): In function `dump_queue_head': : undefined reference to `grub_strcpy' drivers/usb/builtin.o(.text+0x2c4): In function `dump_transaction': : undefined reference to `grub_strcpy' drivers/usb/builtin.o(.text+0x306): In function `dump_usbdev': : undefined reference to `grub_strcpy' drivers/usb/builtin.o(.text+0x37e): In function `dump_config_descriptor': : undefined reference to `grub_strcpy' drivers/usb/builtin.o(.text+0x3a0): more undefined references to `grub_strcpy' follow drivers/usb/builtin.o(.text+0x3089): In function `configure_device': : undefined reference to `grub_printf' drivers/usb/builtin.o(.text+0x32e7): In function `configure_device': : undefined reference to `grub_printf' drivers/usb/builtin.o(.text+0x3321): In function `configure_device': : undefined reference to `grub_printf' drivers/usb/builtin.o(.text+0x3345): In function `configure_device': : undefined reference to `grub_printf' drivers/usb/builtin.o(.text+0x3366): In function `configure_device': : undefined reference to `grub_printf' Here is my Config: # !!! NOTE !!! # Do NOT add spaces or comments at the end of option lines. # It confuses some versions of make. # Use grub instead of autoboot? USE_GRUB = 0 # Grub menu.lst path #MENULST_FILE = "hda3:/boot/filo/menu.lst" # Image filename for automatic boot and optional command line parameter AUTOBOOT_FILE = "hda1:/boot/vmlinuz root=/dev/hda1 console=ttyS0,38400" #AUTOBOOT_FILE = "mem@0xfff80000" #AUTOBOOT_FILE = "hde1@0" #AUTOBOOT_FILE = "uda1:/vmlinuz.elf" # Time in second before booting AUTOBOOT_FILE AUTOBOOT_DELAY = 1 # Driver for hard disk, CompactFlash, and CD-ROM on IDE bus IDE_DISK = 1 # Add a short delay when polling status registers # (required on some broken SATA controllers) IDE_DISK_POLL_DELAY = 1 # Driver for USB Storage USB_DISK = 1 # VGA text console VGA_CONSOLE = 1 PC_KEYBOARD = 1 # Serial console SERIAL_CONSOLE = 1 SERIAL_IOBASE = 0x3f8 # if SERIAL_SPEED is commented out, the speed will not be changed. #SERIAL_SPEED = 115200 # Filesystems FSYS_EXT2FS = 1 #FSYS_FAT = 1 #FSYS_JFS = 1 #FSYS_MINIX = 1 FSYS_REISERFS = 1 #FSYS_XFS = 1 #FSYS_ISO9660 = 1 # Support for boot disk image in bootable CD-ROM (El Torito) #ELTORITO = 1 # PCI support SUPPORT_PCI = 1 # Enable this to scan PCI busses above bus 0 # AMD64 based boards do need this. #PCI_BRUTE_SCAN = 1 # Sound support (needs SUPPORT_PCI) #SUPPORT_SOUND = 1 # Sound drivers #VIA_SOUND = 1 # Debugging #DEBUG_ALL = 1 #DEBUG_ELFBOOT = 1 #DEBUG_ELFNOTE = 1 #DEBUG_LINUXBIOS = 1 #DEBUG_MALLOC = 1 #DEBUG_MULTIBOOT = 1 #DEBUG_SEGMENT = 1 #DEBUG_SYS_INFO = 1 #DEBUG_TIMER = 1 #DEBUG_BLOCKDEV = 1 #DEBUG_PCI = 1 #DEBUG_VIA_SOUND = 1 #DEBUG_LINUXLOAD = 1 #DEBUG_IDE = 1 #DEBUG_USB = 1 #DEBUG_ELTORITO = 1 # i386 options # Loader for standard Linux kernel image, a.k.a. /vmlinuz LINUX_LOADER = 1 # Boot FILO from Multiboot loader (eg. GRUB) #MULTIBOOT_IMAGE = 1 # Use PCI Configuration Mechanism #1 (most boards) PCI_CONFIG_1 = 1

2 2

[LinuxBIOS] Can anyone confirm if linuxbios works on EPIA PD10000?
by Matt 06 May '06

06 May '06

Hi Im new to the list, so apoligise if this has been asked before :( I use the EPIA PD10000 boards for various projects and would like to use linux bios on the boards, the PD range is not listed on the site, so i thought id ask here :) I understand that video can be a problem with the EPIA boards but all i realy want is a serial output :) The PD10000 board has the following chipsets :- # Processor VIA C3/ VIA Eden EBGA processor # Chipset VIA CLE266 North Bridge # VIA VT8235 South Bridge # System Memory 1 DDR266 DIMM socket # Up to 1GB memory size # VGA Integrated VIA UniChrome AGP graphics with MPEG-2 Accelerator # Expansion Slots 1 PCI # Onboard IDE 2 X UltraDMA 133/100/66 Connector # Onboard LAN VIA VT6105 LOM+VT6103 10/100 Base-T Ethernet PHY # Onboard Audio VIA VT1612A 2 channel AC' 97 codec # Award BIOS # 2/4Mbit flash memory # CPU voltage monitoring # Wake-on-LAN, Keyboard Power-on, Timer Power-on # System power management # AC power failure recovery (data taken from VIA website : http://www.via.com.tw/en/products/mainboards/mini_itx/epia_pd/) as i use these boards mainly as routers, all i realy need functioning is the IDE and LAN, and serial access (VERY basic 80x40 video text output might be nice thow :) ) the only other thing might be to have the audio working and the pci slot, as i have used these boards in the past for Asterisk PBX sytsem. Again, if this has been asked before im sorry any help would be great Yours Matt

2 1

← Newer
1
...
4
5
6
7
8
9
10
11
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

coreboot May 2006