August 2005 - coreboot - mail.coreboot.org

Re: [LinuxBIOS] BIOS Saver RD1
by Ken Fuchs June 5, 2007

June 5, 2007

> On Wed, Aug 03, 2005 at 11:59:20AM +0900, Jun OKAJIMA wrote: > > Probably, most guys here use BIOS Saver. > > And it works well? > > In mine, RD1 for PLCC gets not being writable suddenly. > > I mean, it seems writable but # flash_rom -v fails. > > I solved this problem by a quick hack. > > > > How about yours? You can write RD1 or W49F002U well? > > Any problem happen? Johnathan McDowell wrote: > Even after that it's sometimes a bit flakey and I have to erase, then > write it. I've put the board's original BIOS in the RD1 and am writing > to the SST 39SF020A instead, which works without problems. I've read posts about the RD1 that suggest its integrated flash device is low quality and it may take 10 or more flash attempts to get a good flash update to the RD1 flash device. As a result, many RD1 BIOS Savior users will flash the commercial BIOS image (or other known good BIOS image) into the RD1 integrated flash device as many times as needed to get an image that boots. Then use the original BIOS device to flash test BIOS image (usually LinuxBIOS images among this group), since the original BIOS device usually flashes OK on the first attempt. I've used the RD1 in the above fashion with great success on the Tyan S2885 mainboard. The same RD1 would not work on the nVidia CK8-04 CRB mainboard. I think the CK8-04 CRB requires a flash device that the RD1 does not support. However, the RD1 worked well as an "do nothing" adapter which allowed swapping the BIOS flash device between my flash burner and the mainboard without any wear to the mainboard's BIOS socket. BTW, my flash burner is an older Enhanced Willem Universal Programmer. I got mine for only $60 US over a year ago. I've seen it for less than $40 on eBay a few weeks ago. The newest model is going for about $50 US. It does a LinuxBIOS flash in about 5 minutes; not bad for a $60 burner. However, it does require changing DIP switches to match an image for each device it can program. Great for the amateur or professional with a small budget. > > BTW, a cable of your RD1 is not broken? > > I needed soldering to fix it. > Mine was fine out of the box. Mine cable and switch worked fine out of the box as well. Sincerely, Ken Fuchs <kfuchs(a)winternet.com> ami-mac-sun

16 47

[LinuxBIOS] RE: Does LinuxBIOS support the Mac Mini?
by Angel Sept. 3, 2005

Sept. 3, 2005

Well, the wiki says it supports the PPC series MPC74xx, MPC4xx and MPC7xx. The CPU built in the Mac Mini is a MPC7447 (revision B I believe), so I think it should be supported, shouldn't it? The wiki also says the Motorola northbridge MPC107 is supported. According to this page ( http://e-www.motorola.com/webapp/sps/site/prod_summary.jsp?code=MPC107 ) this chipset seems to be only suitable for older CPU up to the MPC7410. I couldn't find any information about the chipset used in the Mac Mini. But as Apple is just an OEM, it should be from Motorola/Freescale as well.

3 3

[LinuxBIOS] Open Gaming Console
by Nathaniel Dube Sept. 1, 2005

Sept. 1, 2005

Has any one ever thought of making a gaming console using LinuxBIOS? I would like to put one together using open standard hardware and with a linux based OS. The goal, to create a openstandard/opensource game console. Then game companies can make games for low prices since this system doesn't have to deal in royalties. I hear the Xbox360 will be around $300 and the games $60. I think that's complete bull spit. I think it's time for people in the Linux world to make our own game console. We made a operating system as an alternative to Windows now it's time to do the same with their game console. We gave the computer world freedom now lets give the gaming world freedom so junior (as well as adults) aren't spending arm and leg for games, consoles and other parts. It's not just money I want people to save but to give them back freedom in the technology they use. The hardware side of this project is easy. The hard part is putting together a small Linux OS for it and customizing LinuxBIOS for this kind of system. If any one wants to start such project let me know. All I have are ideas, what I don't have is the knowledge to pull this off. Which is why I need some of you talented people to help me start a project to pull this off.

8 20

RE: [LinuxBIOS] PCI Express add-on cards and Expansion Roms
by Peter.VanEchaute＠bench.com Aug. 31, 2005

Aug. 31, 2005

No, I am not sure. I haven't gotten the card to work with my LinuxBIOS yet. I have seen it work with a Pheonix BIOS and FC3 kernel with the driver. So I know it works. The Pheonix BIOS doesn't show me an output of what it is doing as it loads. So I am looking for a direction of why it isn't working yet. I was thinking it might be the lack of executing a ROM, but didn't want to waste my time going down a path not needed. It seems that I should look deeper into the register set on my PCI-E device for the slot and the PCI-E expansion register space for why it isn't working yet. -Pete -----Original Message----- From: Li-Ta Lo [mailto:ollie@lanl.gov] Sent: Wednesday, August 31, 2005 5:48 PM To: Van Echaute, Peter Cc: LinuxBIOS Subject: Re: [LinuxBIOS] PCI Express add-on cards and Expansion Roms On Wed, 2005-08-31 at 15:13 -0400, Peter.VanEchaute(a)bench.com wrote: > Hello All, > > > > I am trying to work on getting a PCI-E card working and came across an > error that I am wondering if I need to worry about. Below shows that > the VGA ROM is loading, but not the ROM from the PCI-E card (at the > bottom). Both of these cards are in slots and not onboard. The PCI-E > card is an Ethernet card. As the device is getting a bus and > resources seemingly just fine, I would think that the ROM would have > been found. My question is ... do all add-on cards need to load an > expansion ROM or can they run just fine without it? The error in > question is "Incorrect Expansion ROM Header Signature ffff". > > Are you sure there is anything on the expansion rom? > > FYI on devices: > > 00:01.0 is the PCI-PCI bridge > > 02:06.0 is the VGA card on the PCI-PCI bridge > > 00:02.0 is the PCI-E bridge > > 04:00.0 is the ethernet card on the PCI-E bridge > > > > PCI: 00:01.0 1c <- [0x0000001000 - 0x0000001fff] bus 2 io > > PCI: 00:01.0 20 <- [0x00fc000000 - 0x00fdffffff] bus 2 mem > > PCI: 02:06.0 10 <- [0x00fc000000 - 0x00fcffffff] mem > > PCI: 02:06.0 14 <- [0x0000001000 - 0x00000010ff] io > > PCI: 02:06.0 30 <- [0x00fd000000 - 0x00fdffffff] rom > > > > PCI: 00:02.0 1c <- [0x0000002000 - 0x0000002fff] bus 4 io > > PCI: 00:02.0 20 <- [0x00fe000000 - 0x00fe0fffff] bus 4 mem > > PCI: 04:00.0 10 <- [0x00fe020000 - 0x00fe023fff] mem > > PCI: 04:00.0 18 <- [0x0000002000 - 0x00000020ff] io > > PCI: 04:00.0 30 <- [0x00fe000000 - 0x00fe01ffff] rom > > > > > > PCI: 00:01.0 bridge ctrl <- 000b > > PCI: 00:01.0 cmd <- 147 > > PCI: 02:06.0 cmd <- 143 > > > > PCI: 00:02.0 bridge ctrl <- 0007 > > PCI: 00:02.0 cmd <- 547 > > PCI: 04:00.0 cmd <- 143 > > > > > > PCI: 02:06.0 init > > rom address for PCI: 02:06.0 = fd000000 > > Class Code mismatch ROM 00000003, dev 00030000 > > copying VGA ROM Image from fd000000 to c0000, 8000 bytes > > halt_sys: > file /home/vanecp/design/freebios2-3/src/devices/emulator/x86emu/ops.c > > , line 4400 > > PCI: 04:00.0 init > > rom address for PCI: 04:00.0 = fe000000 > > Incorrect Expansion ROM Header Signature ffff > > Devices initialized > > > > > > > > Cheers, > Peter Van Echaute > > > > > > > -- > LinuxBIOS mailing list > LinuxBIOS(a)openbios.org > http://www.openbios.org/mailman/listinfo/linuxbios -- Li-Ta Lo <ollie(a)lanl.gov> Los Alamos National Lab

1 0

[LinuxBIOS] PCI Express add-on cards and Expansion Roms
by Peter.VanEchaute＠bench.com Aug. 31, 2005

Aug. 31, 2005

Hello All, I am trying to work on getting a PCI-E card working and came across an error that I am wondering if I need to worry about. Below shows that the VGA ROM is loading, but not the ROM from the PCI-E card (at the bottom). Both of these cards are in slots and not onboard. The PCI-E card is an Ethernet card. As the device is getting a bus and resources seemingly just fine, I would think that the ROM would have been found. My question is ... do all add-on cards need to load an expansion ROM or can they run just fine without it? The error in question is "Incorrect Expansion ROM Header Signature ffff". FYI on devices: 00:01.0 is the PCI-PCI bridge 02:06.0 is the VGA card on the PCI-PCI bridge 00:02.0 is the PCI-E bridge 04:00.0 is the ethernet card on the PCI-E bridge PCI: 00:01.0 1c <- [0x0000001000 - 0x0000001fff] bus 2 io PCI: 00:01.0 20 <- [0x00fc000000 - 0x00fdffffff] bus 2 mem PCI: 02:06.0 10 <- [0x00fc000000 - 0x00fcffffff] mem PCI: 02:06.0 14 <- [0x0000001000 - 0x00000010ff] io PCI: 02:06.0 30 <- [0x00fd000000 - 0x00fdffffff] rom PCI: 00:02.0 1c <- [0x0000002000 - 0x0000002fff] bus 4 io PCI: 00:02.0 20 <- [0x00fe000000 - 0x00fe0fffff] bus 4 mem PCI: 04:00.0 10 <- [0x00fe020000 - 0x00fe023fff] mem PCI: 04:00.0 18 <- [0x0000002000 - 0x00000020ff] io PCI: 04:00.0 30 <- [0x00fe000000 - 0x00fe01ffff] rom PCI: 00:01.0 bridge ctrl <- 000b PCI: 00:01.0 cmd <- 147 PCI: 02:06.0 cmd <- 143 PCI: 00:02.0 bridge ctrl <- 0007 PCI: 00:02.0 cmd <- 547 PCI: 04:00.0 cmd <- 143 PCI: 02:06.0 init rom address for PCI: 02:06.0 = fd000000 Class Code mismatch ROM 00000003, dev 00030000 copying VGA ROM Image from fd000000 to c0000, 8000 bytes halt_sys: file /home/vanecp/design/freebios2-3/src/devices/emulator/x86emu/ops.c , line 4400 PCI: 04:00.0 init rom address for PCI: 04:00.0 = fe000000 Incorrect Expansion ROM Header Signature ffff Devices initialized Cheers, Peter Van Echaute

2 1

RE: [LinuxBIOS] PCI Express add-on cards and Expansion Roms
by Lu, Yinghai Aug. 31, 2005

Aug. 31, 2005

option rom purposes 1. patch chip bugs 2. installed BIOS call, so OS can boot from SCSI... 3. PXE boot from network... 4. Some UO for setup. 5. VGA card, init .... So depend what card that you are going to use. YH -----Original Message----- From: linuxbios-bounces(a)openbios.org on behalf of Peter.VanEchaute(a)bench.com Sent: Wed 8/31/2005 12:13 PM To: linuxbios(a)openbios.org Subject: [LinuxBIOS] PCI Express add-on cards and Expansion Roms Hello All, I am trying to work on getting a PCI-E card working and came across an error that I am wondering if I need to worry about. Below shows that the VGA ROM is loading, but not the ROM from the PCI-E card (at the bottom). Both of these cards are in slots and not onboard. The PCI-E card is an Ethernet card. As the device is getting a bus and resources seemingly just fine, I would think that the ROM would have been found. My question is ... do all add-on cards need to load an expansion ROM or can they run just fine without it? The error in question is "Incorrect Expansion ROM Header Signature ffff". FYI on devices: 00:01.0 is the PCI-PCI bridge 02:06.0 is the VGA card on the PCI-PCI bridge 00:02.0 is the PCI-E bridge 04:00.0 is the ethernet card on the PCI-E bridge PCI: 00:01.0 1c <- [0x0000001000 - 0x0000001fff] bus 2 io PCI: 00:01.0 20 <- [0x00fc000000 - 0x00fdffffff] bus 2 mem PCI: 02:06.0 10 <- [0x00fc000000 - 0x00fcffffff] mem PCI: 02:06.0 14 <- [0x0000001000 - 0x00000010ff] io PCI: 02:06.0 30 <- [0x00fd000000 - 0x00fdffffff] rom PCI: 00:02.0 1c <- [0x0000002000 - 0x0000002fff] bus 4 io PCI: 00:02.0 20 <- [0x00fe000000 - 0x00fe0fffff] bus 4 mem PCI: 04:00.0 10 <- [0x00fe020000 - 0x00fe023fff] mem PCI: 04:00.0 18 <- [0x0000002000 - 0x00000020ff] io PCI: 04:00.0 30 <- [0x00fe000000 - 0x00fe01ffff] rom PCI: 00:01.0 bridge ctrl <- 000b PCI: 00:01.0 cmd <- 147 PCI: 02:06.0 cmd <- 143 PCI: 00:02.0 bridge ctrl <- 0007 PCI: 00:02.0 cmd <- 547 PCI: 04:00.0 cmd <- 143 PCI: 02:06.0 init rom address for PCI: 02:06.0 = fd000000 Class Code mismatch ROM 00000003, dev 00030000 copying VGA ROM Image from fd000000 to c0000, 8000 bytes halt_sys: file /home/vanecp/design/freebios2-3/src/devices/emulator/x86emu/ops.c , line 4400 PCI: 04:00.0 init rom address for PCI: 04:00.0 = fe000000 Incorrect Expansion ROM Header Signature ffff Devices initialized Cheers, Peter Van Echaute

1 0

RE: [LinuxBIOS] Etherboot BIOS.
by Lu, Yinghai Aug. 31, 2005

Aug. 31, 2005

get one USB ROM emulator... It could be usefull etherboot to load etherboot to test ehterboot. YH -----Original Message----- From: linuxbios-bounces(a)openbios.org on behalf of Steve Casselman Sent: Wed 8/31/2005 12:10 PM To: LinuxBios(a)openbios.org Subject: [LinuxBIOS] Etherboot BIOS. I was wondering how difficult/useful it would be to have a very small bios that boots enough to get on the network and then loads the working bios from there. I keep making little changes (printing stuff out) and it is a pain to keep burning Roms. This would also let you have as big a bios as you want. In a cluster you could make a bios change just by updating one file. Steve -- LinuxBIOS mailing list LinuxBIOS(a)openbios.org http://www.openbios.org/mailman/listinfo/linuxbios

2 1

[LinuxBIOS] VIA EPIA-MII + fastboot (2.03)
by skb tdf Aug. 31, 2005

Aug. 31, 2005

Hi, Although I know, LinuxBIOS != VIA fastboot (and mainly closed source), I have no idea where can I get answer to my question (There was no success on Via forum or Google). Since LinuxBIOS can not be compile for EPIA-MII I tried to reach my aim with fastboot (2.03). After a few hours, it seems that system is not so far from ready, but unfortunately still not finished. On the serial debug line I got the following info: ... ... ... User Routine 1:Jun 25 2004,18:02:57 VIA WINCE FastBoot/FreeBoot Loader V2.03 for EPIA-M2 Jun 25 2004,18:02:51 Zero memory:0x06000000... User Routine 2 0,1,2,3,4, Check DOC... fail. Finding Primary/Master IDE... Enter FindDevice IssueIdentify Identify IDE Device : Heads:16 SectorsPerTrack:63 MBLK:1 Return from (IDE_COMMAND_IDENTIFY) Sanity check FastBootRom:Boot from IDE device:0x31 h/w reset status byte:50 Boot partition found! (File System ID = 0xff83) Found file system used by Linux.(File System ID = 0x83) User Routine 3 +init_text_mode() -init_text_mode() Current cursor is at (0,0) Move loader function from rom to ram Packet found_os = 0Set VESA VGA mode(for non-MVP4)... Call jump_loader () Enter loader ReservedRootDirSectors = 0x205, filesys_id = 0xff83 Heads = 0xfe0a, SectorsPerTrack = 0x1 BytesPerSector = 0x0, SectorsPerFat = 0x0 nkimg_cluster = 0xffffffff, nkimg_length = 0xffffffff KernelPath = hda1:/boot/vmlinuz-m2 found_os = 0x2 found_os = 0x2 Enter FindDevice IssueIdentify Identify IDE Device : Heads:16 SectorsPerTrack:63 MBLK:1 Return from (IDE_COMMAND_IDENTIFY) Sanity check h/w reset status byte:50 Try to load Linux(0xff83) at dev 0x31 error code:0x1! Partition starts at 0x3f Path = /boot/vmlinuz-m2 Enter LoadKernel() mount succ Found filename is vmlinuz-m2 File "/boot/vmlinuz-m2" is Found! ELF Header check ok! Enter ParsePHDR() PHDR 0, type=1, Offset=0x001000, Addr=0x010000, Size=0x000a5c, MemSize=0x004a60 Checksum 0 = 0x6f860000 Clean memory range 0x10a5c - 0x14a60 PHDR 1, type=1, Offset=0x002000, Addr=0x091000, Size=0x00002c, MemSize=0x00002c Checksum 1 = 0x30d0000 Clean memory range 0x9102c - 0x9102c PHDR 2, type=1, Offset=0x003000, Addr=0x100000, Size=0x13d529, MemSize=0x13d529 Checksum 2 = 0x5b140000 Clean memory range 0x23d529 - 0x23d529 But after this there is no any activity. Can anybody help? (Maybe this question is off-topic but I think there are other people who tried fastboot like me). Thx, Sza2 _______________________________________________________________________ [freemail] extra 1GB-os postafiókkal, Önnek már van? http://freemail.hu

1 0

Re: [LinuxBIOS] Etherboot BIOS.
by Richard Smith Aug. 31, 2005

Aug. 31, 2005

On 8/31/05, Steve Casselman <sc(a)drccomputer.com> wrote: > Yes. So I would just use linuxbios to boot and then > use etherboot to boot the linuxbios I want (which > would then load the kernal?) The etherboot I see being > used is an elf loader. Is linuxbios compiled in elf > format? Ah. I misread your desires. So no I was incorrect. Its not done. Thats a interesting idea but I think its going to run into some issues. Many of the chipset registers can only be played with after reset. getting linuxbios build as an elf shouldn't be too hard but splitting linuxbios up into core "only do once" and "repeatable" sections may be more difficult. I'm not guru enough with the ld magic to know so someone else will have to comment. -- Richard A. Smith

1 0

[LinuxBIOS] BIOS
by spidermantm＠freenet.de Aug. 30, 2005

Aug. 30, 2005

BIOS is BIOS no matter if you use Linux or Unix or WindowsXP XP is unix ! and me tried eternally times to get out of this list . . . spiderman getting cobwebbed or what ??? meow. wish to you what. sincerely and thank you for seeing that puting is not the essence of life

2 1