coreboot

coreboot@coreboot.org

39717 discussions

Re: [LinuxBIOS] New Target for LinuxBios MB1030 / 3036
by Richard Smith 22 Apr '06

22 Apr '06

On 4/22/06, Christian Sühs <chris(a)suehsi.de> wrote: > > > > > Set your device and try again. If it still dosen't work then try my > > alternate card method and run testbios on a non-posted card under > > factory. > > > > I have tried -d 0:9.0 > > -d 0:9:0 > > how is the right syntax for -d Its in the wiki testbios FAQ. * How to get pci busdevfn * lspci * look for your video card o Example: 2:00:00 2 (00 << 3) | 00 = 0x200 o Example: 00:12.0: 0 (12 << 3) | 0 = 0x90 So for you its 0 (9 << 3) | 0 = 0x048 so '-d 0x48' -- Richard A. Smith

2 1

Re: [LinuxBIOS] New Target for LinuxBios MB1030 / 3036
by Richard Smith 22 Apr '06

22 Apr '06

Oops forgot to Reply to all: > 8-) > > sorry I need to learn more about this. > > Ok, it doesn't work. I will try the second method with another card. doesn't work how? More details please or we can't help much. What output did you get? If it does not work under factory with previously non-posted chip then you are going to have to re-enable the IO printfs and see whats up. Note. Comparing the IO logs between the posted and non-posted runs won't do you much good. One of the first things video bios does is check to see if the card has already been posted and if it has then it will take a different path and skip a lot of the init stuff. Welcome to the single hardest thing in Linuxbios. *grin* Well perhaps second to trying to enable RAM without a proper datasheet. Definitely the hardest from a user standpoint. -- Richard A. Smith

1 0

Re: [LinuxBIOS] New Target for LinuxBios MB1030 / 3036
by Christian Sühs 22 Apr '06

22 Apr '06

> > > Running the bios under the emu is tricky. It may be bailling out > early although normally it prints a messge. Search the archives for > info. You will probally have to add debug printf's to see whats going > on. > Ok, yesterday evening I have found the testbios faq on the linuxbios page. I have tried it twice. 1. extracted vgabios from fuctory bios. 2. bios get with dd command from /dev/mem The result of first try I have described before, it happens nothing. The second try seems to be more successfully :D The screen goes to black :D after a second. No more. The connected TFT holds the signal. There is a short flickering after 30 seconds I think. (The reason for no output on the console is the FB Mode. I have sometimes problems, if I start a normal program, than there is no output too and I need to press <return> for a while to get a prompt) The system is still running but the only way to get a new try is <ctrl><alt><del> to shutdown and reboot the system. Than I have made tests with my host system, to see what happens. I get a vga.bin with dd and try it. (PCI Nvidia Graphic Card) I get a lot of numbers on the console for about 5 seconds, than the screen switched to black and the monitor lost the signal and goes to stand by. The system is still running but only <strg><alt><del> helps. Mmmh, both systems runs in FB Mode, could that be the reason for no more output? Should I try the bios on a real console? What does USER Space mean in the wiki? chris > -- > Richard A. Smith >

3 14

[LinuxBIOS] Bios memory init
by Hugo MERCIER 22 Apr '06

22 Apr '06

Hi, I'm investigating the Linuxbios port to the ASUS A7V600 motherboard. I'm currently at an early phase of the development. I'm just trying to get the bios executing code ... and I noticed some strange behavior ... I wrote a little piece of asm to make the speaker beep. I created an "empty" bios image (full of 0xFF) except a jmp at FFFFFFF0 to a beep routine and flashed it. Result : nothing happens. I then copied and overwrite the original bios in order to make it beep only (modification of the jmp and insertion of the beep function). I flashed it and it beeps ... So, it seems the flash memory has to contain some correct bytes before the processor is "launched". Right ? Consequently, I took this modified beeping image, and iteratively filled it with 0xFF and tested if it beeps, in a dichotomic manner, in order to find what part of the memory is needed. Result: Two blocks in the memory have to be present before execution of any instruction: a 1024bytes block at FFFF7C00 and a 16bytes block at FFFFFFD0. The second block begins with "0x00 0x7C 0xFF 0xFF", so it seems to be a pointer to the first block. I can't figure out what these blocks mean. It is divided into 4 subblocks. It's not x86 code. Some sort of init table ... processor microcode ? other chipsets init ? The dump of the two blocks are in attachment. Any ideas ?

1 0

[LinuxBIOS] New Target for LinuxBios MB1030 / 3036
by Christian Sühs 22 Apr '06

22 Apr '06

I'm back :D Ok, I will start to create a new target for LB. Board with following features. Cyrix Media GXM CPU up to 300MHz. NSC CS5530 or Cyrix CX5530 Southbridge NSC SuperIO PC97137 Cyberpro 500x Video Chipset Lan (sometimes on board) realtek 8139 DOC Support PC104 Connector Sound on board and so on ... what do you think is the best target to start? AMD has sometimes the same features and the same chipsets. Thanks chris

4 18

[LinuxBIOS] Old Tyan "Tsunami" S1846 board?
by Scott Leffel 21 Apr '06

21 Apr '06

I realize that the S1846 is quite an "antique" and it would seem support for it was dropped during the LinuxBIOS 2.0 development phase. Code support seems to be in "FreeBIOS Devel. v1.0 Base0.tar.bz2" which I have archived; I can see from old lanl.gov mailing list archives I googled where Ron Minnich merged hcyun's changes into the source tree on 28 Sept. 2001 (yes, that how ancient this is!). What's unclear to me is what version of the kernel source code might have ever worked with FreeBIOS when it supported the S1846 there for awhile under v1.0. I know the 2Mbit flash is too small for a kernel (that same message thread was in relation to an Etherboot payload originally), but I know a matching kernel source will be important nonetheless. Could I probably get away with trying 2.2.19 or 2.4.10, since they are dated closest to the time S1846 was merged into FreeBIOS v1.0 back in Sept. 2001? Or does anyone here (perhaps Yinghai Lu, who seems to have an excellent memory for all the Tyan board matters!) remember what kernel source version would have worked? I've scoured all our spare & decomissioned systems here, trying to find something more modern that's been on the supported list at some point, but unfortunately this board seems to be all we've got. I'd like to be able to lab this out, which might convince folks to buy some newer Tyan's for this purpose, but for now I'd greatly appreciate anything the community can render in terms of advice. --------------------------------- Talk is cheap. Use Yahoo! Messenger to make PC-to-Phone calls. Great rates starting at 1¢/min.

2 1

Re: [LinuxBIOS] Epia ML 5000 progress (sort of)
by Richard Smith 21 Apr '06

21 Apr '06

> > > No problem. One question: All of this occurs BEFORE LinuxBIOS prints > anything? > Thats correct. According the the comments in auto.c if the firewire device is enabled it stomps on legacy IO. So you have to disable it prior to serial port activity. -- Richard A. Smith

1 0

[LinuxBIOS] Get $20 Reward
by Chase 20 Apr '06

20 Apr '06

1 0

[LinuxBIOS] Development Utility idea
by Justin Hawkeye 20 Apr '06

20 Apr '06

Client boots, loads consisting of a tiny Linux Kernel and network driver, and a script or program [Non-NVRAM setup] Client listens for predefined broadcast from Emu(server) When found, Kernel contacts Emu and establishes connection Emu starts logging all activity Kernel reads local bios to Emu [Non-NVRAM setup] Emu executes received bios (emulated), directing all output to Kernel Kernel directs/passes received output to hardware, directs/passes hardware results to Emu Assuming the Kernel does not get overwritten or lose control of system (crash), we now have a log of all neccesary and expected results of that bios on boot on that hardware. This would allow reverse engineering bioses and developing bioses for hardware legally? BIOS | v A) Emu<->network<->Kernel OR B) ROM Image->Emu<->network<->Kernel Bios<->system/devices ^ | v system/devices If the above ascii depiction is off, bios is above kernel is above system/devices Also, as in B) Client can be burned to Flash NVRAM, and ROM images can be fed through Emu to Kernel (Bios) One possibility for A) is loading Client via PXE/bootp/Network boot.

2 1

[LinuxBIOS] Support for AM2 processors?
by Carl-Daniel Hailfinger 20 Apr '06

20 Apr '06

Hi, since the upcoming AM2 processors will have a new (DDR2) memory controller, does that mean the RAM initialization has to be rewritten completely? If so, is there any expected time when LinuxBIOS support for these processors will be available? Regards, Carl-Daniel -- http://www.hailfinger.org/

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