coreboot June 2008

coreboot@coreboot.org

75 participants
230 discussions

Re: [coreboot] #14: Rename "stream" to "payload"
by coreboot 15 Jun '08

15 Jun '08

#14: Rename "stream" to "payload" ----------------------------+----------------------------------------------- Reporter: uwe | Owner: somebody Type: enhancement | Status: closed Priority: major | Milestone: Cosmetic fixes Component: coreboot | Version: v2 Resolution: fixed | Keywords: Dependencies: #22 | Patchstatus: patch has been committed ----------------------------+----------------------------------------------- Changes (by eswierk): * status: new => closed * resolution: => fixed -- Ticket URL: <http://tracker.coreboot.org/trac/coreboot/ticket/14#comment:11> coreboot <http://www.coreboot.org/>

1 0

Trac reminder: list of new ticket(s)
by coreboot tracker 15 Jun '08

15 Jun '08

1 0

work on intel 440gx
by Marek Becka 15 Jun '08

15 Jun '08

Hi all, I have one older motherboard with Intel 440 GX chipset. During this summer I would like to try to port coreboot on it. I like idea of this project and I would like to support it and learn something new. There is already work on 440 BX chipset, so I can establish on it. Documentation from Intel is also available. The only problem should be Ali M5132 Super I/O. I haven't found anything about this chip. It is real problem?

1 0

Re: [coreboot] [oc] 3 Chip Open BIOS + ESP: Backup/Secure BIOS with Redundancy
by Won De Erick 14 Jun '08

14 Jun '08

http://www.gigabyte.com.tw/FileList/NewTech/2006_motherboard_newtech/how_do… ----- Original Message ---- From: Nathaniel Dube <njdube(a)gmail.com> To: coreboot(a)coreboot.org; cores(a)opencores.org Sent: Thursday, June 12, 2008 2:42:30 PM Subject: [oc] 3 Chip Open BIOS + ESP: Backup/Secure BIOS with Redundancy -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 First off, I'm by no means a engineer. This message is going out to real engineers that might have interest in bringing the idea I'm about to share with you to reality. This idea came to me after some light reading about rootkits on wikipedia and playing around with the program "rkhunter". Malware designers are writing code that can infect a system via rootkits. I've even read about the possibility of malware that can infect ROM chips on mother boards as well as ROM chips on PCI cards. Meaning, anything that is rewritable isn't safe from malware. Then it dawned on me that most of these security issues could be minimized at the hardware level at preboot, meaning before the operating system loads. My brother brought his laptop to me complaning the internet wont work and that it's slow as a whale turd. When I looked at it I found it swarming with viruses. I asked him what happened to the firewall and antivirus that In installed for him and he said he turned them off because the firewall was messing with his internet and he didn't know how to turn it off with out also turning off the antivirus. I think it was Eset Internet Security. I use Linux on my system so I don't touch Windows software all that often. I've come to the conclusion that it doesn't matter what software you put on there or what you do, stupid users (and most users are stupid) will fsck up there system. That's when I decided that mother boards need to be dramatically redesigned from the ground up with a proactive role in security. Now here's where I will start with my wonderful idea that will save the world. You will either see that world with me or you wont. I'm sure most of you are aware of the history of the BIOS and the ROM's they're on. Back in the day they really where ROM in every sense of the term that they where READ only. They where embed on the board so you would need a solder iron to remove them. Then they came out with the removable kind with sockets that you can replace with a new chip. Then comes the kind you can flash with software but are embedded. I'm sorry but impeded un-removeable ROM chips are completely asinine. Now on to my idea. Instead of one ROM chip for the BIOS there should be 3 and use "coreboot" as the BIOS. All 3 will utilize sockets to be removeable for easy replacement. The first chip will have the purpose as a backup of the default BIOS and the chip will be read only. The second chip will house a copy of the primary BIOS which will be rewritable and allow for updates. The third chip I will call the ESP (Emergency Security Protocols) ROM which may or may not be read only, I haven't decided yet. The third chip will have the open source programs rkhunter, clamav and perhaps other programs that might be useful for a preboot. In the event the other two are corrupted for what ever reason you need only flip a jumper, turn on the computer and the backup BIOS takes control and allows you to wipe the other two chips and restore a rewritable copy of the BIOS to chip 2 and the ESP BIOS to chip 3. The backup BIOS will also have the Linux program "wipe" so in the unlikeliness a rootkit takes control of chips 2 and 3 chip 1 will wipe it out and start from scratch. This board will also have integrated wifi as well as lan making it easy to get a internet connection. The goal being to be able to update the signatures of rkhunter and clamav as well as update both firmware by direct download before the OS even loads. This entire process will have a liberal use of checksums to make sure at no time is any malware being installed during the preboot process. I'm still trying to work out the finer details in my head. So my idea may make sense or it may not. Ultimately what I'm trying to do is build a mother board with BIOS backup/security redundancy. The 3 chips act as a triad that protect one another. The board should be designed so it tries to load the second chip with the rewritable BIOS and use the third chip to do a quick self scan for rootkits. If for some reason the first BIOS wont load it will fall back on the backup BIOS restoring the primary. Perhaps some one can share a better way of implimenting my idea. The goal is to make it damn near impossible for malware to alter or change the BIOS or load at preboot. These security meause could also be used to protect rewritable ROM on other hardware. Please share your thoughts. I would really like to see a board like this see the light of reality. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFIUMVWvsn/sQCIOqQRAnqwAJ9lYdjiBqnaVArQvHZIcIIaD8A0gQCfSKn1 YYOUf33mToJpZ7N/HI6Q7jY= =VeHI -----END PGP SIGNATURE----- _______________________________________________ http://www.opencores.org/mailman/listinfo/cores

2 1

How to build coreboot for AMD/Opteron nVnida/CK804 CRB
by Ken.Fuchs＠bench.com 13 Jun '08

13 Jun '08

There doesn't seem to be a target defined for this board in the current source for coreboot. I tried: $ cd ./targets $ ./buildtarget nvidia/ck804 No target config file found Tried both nvidia/ck804 and nvidia/ck804/Config.lb $ Where are the target files for the Opteron/CK804 CRB? --- Chipset Reference Boards --- It is very important that coreboot contains the targets of all chipset reference boards, since mainboard designers often use them as the basis of their own designs. Thus coreboot ports from these chipset reference boards to the mainboards based on them would seem to be the easiest way to do these board-level ports. The only exception might be a mainboard family whose various members may be closer in design that the chipset reference board. Sincerely, Ken Fuchs

4 7

flashrom: Board enable for GIGABYTE GA-7VT600
by Peter Stuge 13 Jun '08

13 Jun '08

See patch. //Peter

2 4

r3366 - trunk/util/flashrom
by svn＠coreboot.org 13 Jun '08

13 Jun '08

Author: stuge Date: 2008-06-13 03:39:45 +0200 (Fri, 13 Jun 2008) New Revision: 3366 Modified: trunk/util/flashrom/board_enable.c Log: flashrom: Board enable and autodetection for GIGABYTE GA-7VT600 Uses the VT8237 ISA bridge with mainboard subsystem ID and Realtek 8139 with mainboard subsystem ID for board detection. Signed-off-by: Peter Stuge <peter(a)stuge.se> Acked-by: Lyos Gemini Norezel <lyos.gemininorezel(a)gmail.com> Modified: trunk/util/flashrom/board_enable.c =================================================================== --- trunk/util/flashrom/board_enable.c 2008-06-11 02:24:15 UTC (rev 3365) +++ trunk/util/flashrom/board_enable.c 2008-06-13 01:39:45 UTC (rev 3366) @@ -517,6 +517,7 @@ /** * Suited for: * - BioStar P4M80-M4: Intel P4 + VIA P4M800 + VT8237 + * - GIGABYTE GA-7VT600: AMD K7 + VIA KT600 + VT8237 */ static int board_biostar_p4m80_m4(const char *name) { @@ -612,6 +613,8 @@ "kontron", "986lcd-m", "Kontron 986LCD-M", board_kontron_986lcd_m}, {0x1106, 0x3149, 0x1565, 0x3206, 0x1106, 0x3344, 0x1565, 0x1202, NULL, NULL, "BioStar P4M80-M4", board_biostar_p4m80_m4}, + {0x1106, 0x3227, 0x1458, 0x5001, 0x10ec, 0x8139, 0x1458, 0xe000, + NULL, NULL, "GIGABYTE GA-7VT600", board_biostar_p4m80_m4}, {0, 0, 0, 0, 0, 0, 0, 0, NULL, NULL} /* Keep this */ };

1 0

Where to begin?
by Bret Orsburn 12 Jun '08

12 Jun '08

Corebooters: Which version of coreboot, and which target, would you start with if you wanted to support this board: http://www.bcmcom.com/bcm_product_mx965gme.htm with a Celeron M processor. Thanks. ---- Bret Orsburn

2 1

3 Chip Open BIOS + ESP: Backup/Secure BIOS with Redundancy
by Nathaniel Dube 12 Jun '08

12 Jun '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 First off, I'm by no means a engineer. This message is going out to real engineers that might have interest in bringing the idea I'm about to share with you to reality. This idea came to me after some light reading about rootkits on wikipedia and playing around with the program "rkhunter". Malware designers are writing code that can infect a system via rootkits. I've even read about the possibility of malware that can infect ROM chips on mother boards as well as ROM chips on PCI cards. Meaning, anything that is rewritable isn't safe from malware. Then it dawned on me that most of these security issues could be minimized at the hardware level at preboot, meaning before the operating system loads. My brother brought his laptop to me complaning the internet wont work and that it's slow as a whale turd. When I looked at it I found it swarming with viruses. I asked him what happened to the firewall and antivirus that In installed for him and he said he turned them off because the firewall was messing with his internet and he didn't know how to turn it off with out also turning off the antivirus. I think it was Eset Internet Security. I use Linux on my system so I don't touch Windows software all that often. I've come to the conclusion that it doesn't matter what software you put on there or what you do, stupid users (and most users are stupid) will fsck up there system. That's when I decided that mother boards need to be dramatically redesigned from the ground up with a proactive role in security. Now here's where I will start with my wonderful idea that will save the world. You will either see that world with me or you wont. I'm sure most of you are aware of the history of the BIOS and the ROM's they're on. Back in the day they really where ROM in every sense of the term that they where READ only. They where embed on the board so you would need a solder iron to remove them. Then they came out with the removable kind with sockets that you can replace with a new chip. Then comes the kind you can flash with software but are embedded. I'm sorry but impeded un-removeable ROM chips are completely asinine. Now on to my idea. Instead of one ROM chip for the BIOS there should be 3 and use "coreboot" as the BIOS. All 3 will utilize sockets to be removeable for easy replacement. The first chip will have the purpose as a backup of the default BIOS and the chip will be read only. The second chip will house a copy of the primary BIOS which will be rewritable and allow for updates. The third chip I will call the ESP (Emergency Security Protocols) ROM which may or may not be read only, I haven't decided yet. The third chip will have the open source programs rkhunter, clamav and perhaps other programs that might be useful for a preboot. In the event the other two are corrupted for what ever reason you need only flip a jumper, turn on the computer and the backup BIOS takes control and allows you to wipe the other two chips and restore a rewritable copy of the BIOS to chip 2 and the ESP BIOS to chip 3. The backup BIOS will also have the Linux program "wipe" so in the unlikeliness a rootkit takes control of chips 2 and 3 chip 1 will wipe it out and start from scratch. This board will also have integrated wifi as well as lan making it easy to get a internet connection. The goal being to be able to update the signatures of rkhunter and clamav as well as update both firmware by direct download before the OS even loads. This entire process will have a liberal use of checksums to make sure at no time is any malware being installed during the preboot process. I'm still trying to work out the finer details in my head. So my idea may make sense or it may not. Ultimately what I'm trying to do is build a mother board with BIOS backup/security redundancy. The 3 chips act as a triad that protect one another. The board should be designed so it tries to load the second chip with the rewritable BIOS and use the third chip to do a quick self scan for rootkits. If for some reason the first BIOS wont load it will fall back on the backup BIOS restoring the primary. Perhaps some one can share a better way of implimenting my idea. The goal is to make it damn near impossible for malware to alter or change the BIOS or load at preboot. These security meause could also be used to protect rewritable ROM on other hardware. Please share your thoughts. I would really like to see a board like this see the light of reality. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFIUMVWvsn/sQCIOqQRAnqwAJ9lYdjiBqnaVArQvHZIcIIaD8A0gQCfSKn1 YYOUf33mToJpZ7N/HI6Q7jY= =VeHI -----END PGP SIGNATURE-----

2 2

(no subject)
by Nathaniel Dube 12 Jun '08

12 Jun '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 First off, I'm by no means a engineer. This message is going out to real engineers that might have interest in bringing the idea I'm about to share with you to reality. This idea came to me after some light reading about rootkits on wikipedia and playing around with the program "rkhunter". Malware designers are writing code that can infect a system via rootkits. I've even read about the possibility of malware that can infect ROM chips on mother boards as well as ROM chips on PCI cards. Meaning, anything that is rewritable isn't safe from malware. Then it dawned on me that most of these security issues could be minimized at the hardware level at preboot, meaning before the operating system loads. My brother brought his laptop to me complaning the internet wont work and that it's slow as a whale turd. When I looked at it I found it swarming with viruses. I asked him what happened to the firewall and antivirus that In installed for him and he said he turned them off because the firewall was messing with his internet and he didn't know how to turn it off with out also turning off the antivirus. I think it was Eset Internet Security. I use Linux on my system so I don't touch Windows software all that often. I've come to the conclusion that it doesn't matter what software you put on there or what you do, stupid users (and most users are stupid) will fsck up there system. That's when I decided that mother boards need to be dramatically redesigned from the ground up with a proactive role in security. Now here's where I will start with my wonderful idea that will save the world. You will either see that world with me or you wont. I'm sure most of you are aware of the history of the BIOS and the ROM's they're on. Back in the day they really where ROM in every sense of the term that they where READ only. They where embed on the board so you would need a solder iron to remove them. Then they came out with the removable kind with sockets that you can replace with a new chip. Then comes the kind you can flash with software but are embedded. I'm sorry but impeded un-removeable ROM chips are completely asinine. Now on to my idea. Instead of one ROM chip for the BIOS there should be 3 and use "coreboot" as the BIOS. All 3 will utilize sockets to be removeable for easy replacement. The first chip will have the purpose as a backup of the default BIOS and the chip will be read only. The second chip will house a copy of the primary BIOS which will be rewritable and allow for updates. The third chip I will call the ESP (Emergency Security Protocols) ROM which may or may not be read only, I haven't decided yet. The third chip will have the open source programs rkhunter, clamav and perhaps other programs that might be useful for a preboot. In the event the other two are corrupted for what ever reason you need only flip a jumper, turn on the computer and the backup BIOS takes control and allows you to wipe the other two chips and restore a rewritable copy of the BIOS to chip 2 and the ESP BIOS to chip 3. The backup BIOS will also have the Linux program "wipe" so in the unlikeliness a rootkit takes control of chips 2 and 3 chip 1 will wipe it out and start from scratch. This board will also have integrated wifi as well as lan making it easy to get a internet connection. The goal being to be able to update the signatures of rkhunter and clamav as well as update both firmware by direct download before the OS even loads. This entire process will have a liberal use of checksums to make sure at no time is any malware being installed during the preboot process. I'm still trying to work out the finer details in my head. So my idea may make sense or it may not. Ultimately what I'm trying to do is build a mother board with BIOS backup/security redundancy. The 3 chips act as a triad that protect one another. The board should be designed so it tries to load the second chip with the rewritable BIOS and use the third chip to do a quick self scan for rootkits. If for some reason the first BIOS wont load it will fall back on the backup BIOS restoring the primary. Perhaps some one can share a better way of implimenting my idea. The goal is to make it damn near impossible for malware to alter or change the BIOS or load at preboot. These security meause could also be used to protect rewritable ROM on other hardware. Please share your thoughts. I would really like to see a board like this see the light of reality. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFIUMNzvsn/sQCIOqQRAqG+AJ9t1W14EgBRJQrOmvdpaNK5edMeNACggq+G ij2koHbQDzhTVXpv+AQbEHE= =V7L3 -----END PGP SIGNATURE-----

1 1

← Newer
1
...
13
14
15
16
17
18
19
...
23
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

coreboot June 2008