I have been following this list for a while, and noted down the names of socketed motherboards. When I went to purchase one, they were all obsolete/unobtainable in the United Kingdom. The local computer shop is Linux friendly, so I asked them to find a motherboard with a socketed chip, and they suggested the above. At last I can try coreboot without soldering and switches.
The board comes with a ITE IT8716F 4MB chip; but that is compatible with SST49LF040A chips. I already have these and some SST49LF080A chips; just wish there were 160 or 320MB
The motherboard is electrically very similar to the Gigabyte M57SLI having a NVidea 570 SLI MCP(MCP55) chip set.
I have only had the machine 6 hours, have loaded Linux, and had a go at building and booting coreboot; must get more fall back chips before proceeding. My coreboot got as far as filo; but that could not find the disks; possibly because it is SATA. (Because the machine is so similar to a M57SLI, I just duplicate the directories using the names dfi for gigabyte and nf570sli for m57sli; copied the files, and did some minor editing for the name couplets).
I am going to add an IDE drive tomorrow, and start setting up systems properly. If anyone is interested in DFI machines, I can get more chips. Money is not a problem, so let me know if you need any of the above chips, and I can put in a bulk order and get discount.
Chris Lingard
On Sat, Oct 25, 2008 at 11:13 AM, Chris Lingard chris@stockwith.co.ukwrote:
I have been following this list for a while, and noted down the names of socketed motherboards. When I went to purchase one, they were all obsolete/unobtainable in the United Kingdom. The local computer shop is Linux friendly, so I asked them to find a motherboard with a socketed chip, and they suggested the above. At last I can try coreboot without soldering and switches.
The board comes with a ITE IT8716F 4MB chip; but that is compatible with SST49LF040A chips. I already have these and some SST49LF080A chips; just wish there were 160 or 320MB
I'm hoping that's a typo, SST49LF080 is 8Mb (that's 8 megabits, or 1 megabyte), larger chips would be 16 or 32Mb (2 or 4MB).
The motherboard is electrically very similar to the Gigabyte M57SLI having a NVidea 570 SLI MCP(MCP55) chip set.
I have only had the machine 6 hours, have loaded Linux, and had a go at building and booting coreboot; must get more fall back chips before proceeding.
How many do you have? You can use an SST49LF080 as a backup chip for the stock bios, just cat the stock bios onto itself to get two copies of it back to back, and then flash it onto the chip.
My coreboot got as far as filo; but that could not find the disks; possibly because it is SATA. (Because the machine is so similar to a M57SLI, I just duplicate the directories using the names dfi for gigabyte and nf570sli for m57sli; copied the files, and did some minor editing for the name couplets).
Weird, are you sure you've got the right disk names? Filo orders drives starting with IDE, so if the southbridge (not the motherboard) supports 2 IDE channels, (4 drives), the first SATA device would be hde. That should change if any of the ide channels are disabled, but that depends on wether or not their being disabled correctly. Also, FILO should have an option to use longer delays for some buggy SATA devices, can you try it?
I am going to add an IDE drive tomorrow, and start setting up systems
properly. If anyone is interested in DFI machines, I can get more chips. Money is not a problem, so let me know if you need any of the above chips, and I can put in a bulk order and get discount.
Let us know how it goes! You will probably need to do some work on the IRQ tables before Linux will boot, but who knows ;)
-Corey
Corey Osgood wrote:
Filo orders drives starting with IDE,
For filo-0.5 the drive order is actually two drives per PCI bus controller.
For filo-0.6 (current trunk, using libpayload) the drive enumeration has changed to something else, but I don't know exactly what. I spent some time tracing through the code but just looking at it, it seems like it has changed the 0.5 functionality. Not sure.
so if the southbridge (not the motherboard) supports 2 IDE channels, (4 drives), the first SATA device would be hde.
Again it's in bus order so the right name depends on what comes before SATA on the PCI bus.
That should change if any of the ide channels are disabled, but that depends on wether or not their being disabled correctly.
Correct.
Also, FILO should have an option to use longer delays for some buggy SATA devices, can you try it?
Right - this is likely to be neccessary with mechanical media.
//Peter
Corey Osgood wrote:
On Sat, Oct 25, 2008 at 11:13 AM, Chris Lingard <chris@stockwith.co.uk mailto:chris@stockwith.co.uk> wrote:
The board comes with a ITE IT8716F 4MB chip; but that is compatible with SST49LF040A chips. I already have these and some SST49LF080A chips; just wish there were 160 or 320MBI'm hoping that's a typo, SST49LF080 is 8Mb (that's 8 megabits, or 1 megabyte), larger chips would be 16 or 32Mb (2 or 4MB).
Well if 040 is 4MB and 080 is 8MB, I would hope there is a 160 at 16MB and so on; or do engineers use a secret numbering system :-)
I used to do boot CDs pretending to be 2.8Mb floppies, and would be happy with a 4Mb chip to get a Linux kernel into.
How many do you have? You can use an SST49LF080 as a backup chip for the stock bios, just cat the stock bios onto itself to get two copies of it back to back, and then flash it onto the chip.
Yes, I will duplicate the factory BIOS, got about 6 chips. The BIOS does not have an option to write to a floppy; but flashrom works fine
Let us know how it goes! You will probably need to do some work on the IRQ tables before Linux will boot, but who knows ;)
Thanks I will, setting up a clean Linux development system right now, I like Linux from Scratch. How I hate distros that load in an hour; but it takes a week to find the header files.
Just for completeness I add the lspci -v. Once I have a stable system, and have duplicated the factory BIOS, I can start properly.
00:00.0 RAM memory: nVidia Corporation MCP55 Memory Controller (rev a1) Subsystem: nVidia Corporation Unknown device cb84 Flags: bus master, 66MHz, fast devsel, latency 0 Capabilities: <access denied>
00:01.0 ISA bridge: nVidia Corporation MCP55 LPC Bridge (rev a2) Subsystem: nVidia Corporation Unknown device cb84 Flags: bus master, 66MHz, fast devsel, latency 0 I/O ports at 1d00 [size=256]
00:01.1 SMBus: nVidia Corporation MCP55 SMBus (rev a2) Subsystem: nVidia Corporation Unknown device cb84 Flags: 66MHz, fast devsel, IRQ 11 I/O ports at fc00 [size=64] I/O ports at 1c00 [size=64] I/O ports at 1c40 [size=64] Capabilities: <access denied>
00:02.0 USB Controller: nVidia Corporation MCP55 USB Controller (rev a1) (prog-if 10 [OHCI]) Subsystem: nVidia Corporation Unknown device cb84 Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 23 Memory at fe02f000 (32-bit, non-prefetchable) [size=4K] Capabilities: <access denied>
00:02.1 USB Controller: nVidia Corporation MCP55 USB Controller (rev a2) (prog-if 20 [EHCI]) Subsystem: nVidia Corporation Unknown device cb84 Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 22 Memory at fe02e000 (32-bit, non-prefetchable) [size=256] Capabilities: <access denied>
00:04.0 IDE interface: nVidia Corporation MCP55 IDE (rev a1) (prog-if 8a [Master SecP PriP]) Subsystem: Unknown device f0de:cb84 Flags: bus master, 66MHz, fast devsel, latency 0 [virtual] Memory at 000001f0 (32-bit, non-prefetchable) [disabled] [size=8] [virtual] Memory at 000003f0 (type 3, non-prefetchable) [disabled] [size=1] [virtual] Memory at 00000170 (32-bit, non-prefetchable) [disabled] [size=8] [virtual] Memory at 00000370 (type 3, non-prefetchable) [disabled] [size=1] I/O ports at f000 [size=16] Capabilities: <access denied>
00:05.0 IDE interface: nVidia Corporation MCP55 SATA Controller (rev a2) (prog-if 85 [Master SecO PriO]) Subsystem: nVidia Corporation Unknown device cb84 Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 21 I/O ports at 09f0 [size=8] I/O ports at 0bf0 [size=4] I/O ports at 0970 [size=8] I/O ports at 0b70 [size=4] I/O ports at dc00 [size=16] Memory at fe02d000 (32-bit, non-prefetchable) [size=4K] Capabilities: <access denied>
00:05.1 IDE interface: nVidia Corporation MCP55 SATA Controller (rev a2) (prog-if 85 [Master SecO PriO]) Subsystem: nVidia Corporation Unknown device cb84 Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 20 I/O ports at 09e0 [size=8] I/O ports at 0be0 [size=4] I/O ports at 0960 [size=8] I/O ports at 0b60 [size=4] I/O ports at c800 [size=16] Memory at fe02c000 (32-bit, non-prefetchable) [size=4K] Capabilities: <access denied>
00:05.2 IDE interface: nVidia Corporation MCP55 SATA Controller (rev a2) (prog-if 85 [Master SecO PriO]) Subsystem: nVidia Corporation Unknown device cb84 Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 23 I/O ports at c400 [size=8] I/O ports at c000 [size=4] I/O ports at bc00 [size=8] I/O ports at b800 [size=4] I/O ports at b400 [size=16] Memory at fe02b000 (32-bit, non-prefetchable) [size=4K] Capabilities: <access denied>
00:06.0 PCI bridge: nVidia Corporation MCP55 PCI bridge (rev a2) (prog-if 01 [Subtractive decode]) Flags: bus master, 66MHz, fast devsel, latency 0 Bus: primary=00, secondary=01, subordinate=01, sec-latency=32 I/O behind bridge: 00009000-00009fff Memory behind bridge: fdd00000-fddfffff Prefetchable memory behind bridge: fde00000-fdefffff Capabilities: <access denied>
00:06.1 Audio device: nVidia Corporation MCP55 High Definition Audio (rev a2) Subsystem: nVidia Corporation MCP55 High Definition Audio Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 21 Memory at fe020000 (32-bit, non-prefetchable) [size=16K] Capabilities: <access denied>
00:08.0 Bridge: nVidia Corporation MCP55 Ethernet (rev a2) Subsystem: nVidia Corporation Unknown device cb84 Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 506 Memory at fe02a000 (32-bit, non-prefetchable) [size=4K] I/O ports at b000 [size=8] Memory at fe029000 (32-bit, non-prefetchable) [size=256] Memory at fe028000 (32-bit, non-prefetchable) [size=16] Capabilities: <access denied>
00:0b.0 PCI bridge: nVidia Corporation MCP55 PCI Express bridge (rev a2) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=02, subordinate=02, sec-latency=0 I/O behind bridge: 00008000-00008fff Memory behind bridge: fdc00000-fdcfffff Prefetchable memory behind bridge: 00000000fdb00000-00000000fdbfffff Capabilities: <access denied>
00:0c.0 PCI bridge: nVidia Corporation MCP55 PCI Express bridge (rev a2) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=03, subordinate=03, sec-latency=0 I/O behind bridge: 00007000-00007fff Memory behind bridge: fda00000-fdafffff Prefetchable memory behind bridge: 00000000fd900000-00000000fd9fffff Capabilities: <access denied>
00:0d.0 PCI bridge: nVidia Corporation MCP55 PCI Express bridge (rev a2) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=04, subordinate=04, sec-latency=0 I/O behind bridge: 00006000-00006fff Memory behind bridge: fd800000-fd8fffff Prefetchable memory behind bridge: 00000000fd700000-00000000fd7fffff Capabilities: <access denied>
00:0e.0 PCI bridge: nVidia Corporation MCP55 PCI Express bridge (rev a2) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=05, subordinate=05, sec-latency=0 I/O behind bridge: 00005000-00005fff Memory behind bridge: fd600000-fd6fffff Prefetchable memory behind bridge: 00000000fd500000-00000000fd5fffff Capabilities: <access denied>
00:0f.0 PCI bridge: nVidia Corporation MCP55 PCI Express bridge (rev a2) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=06, subordinate=06, sec-latency=0 I/O behind bridge: 00004000-00004fff Memory behind bridge: fd400000-fd4fffff Prefetchable memory behind bridge: 00000000e0000000-00000000efffffff Capabilities: <access denied>
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration Flags: fast devsel Capabilities: <access denied>
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map Flags: fast devsel
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller Flags: fast devsel
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control Flags: fast devsel Capabilities: <access denied>
01:07.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 80) (prog-if 10 [OHCI]) Subsystem: DFI Inc Unknown device 1006 Flags: bus master, stepping, medium devsel, latency 64, IRQ 16 Memory at fddff000 (32-bit, non-prefetchable) [size=2K] I/O ports at 9c00 [size=128] Capabilities: <access denied>
06:00.0 VGA compatible controller: ATI Technologies Inc RV630 [Radeon HD 2600XT] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited Unknown device e420 Flags: bus master, fast devsel, latency 0, IRQ 11 Memory at e0000000 (64-bit, prefetchable) [size=256M] Memory at fd4e0000 (64-bit, non-prefetchable) [size=64K] I/O ports at 4c00 [size=256] [virtual] Expansion ROM at fd400000 [disabled] [size=128K] Capabilities: <access denied>
06:00.1 Audio device: ATI Technologies Inc RV630/M76 audio device [Radeon HD 2600 Series] Subsystem: PC Partner Limited Unknown device aa08 Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at fd4fc000 (64-bit, non-prefetchable) [size=16K] Capabilities: <access denied>
Chris Lingard
On 26.10.2008 15:39, Chris Lingard wrote:
Corey Osgood wrote:
On Sat, Oct 25, 2008 at 11:13 AM, Chris Lingard <chris@stockwith.co.uk mailto:chris@stockwith.co.uk> wrote:
The board comes with a ITE IT8716F 4MB chip; but that is compatible with SST49LF040A chips. I already have these and some SST49LF080A chips; just wish there were 160 or 320MBI'm hoping that's a typo, SST49LF080 is 8Mb (that's 8 megabits, or 1 megabyte), larger chips would be 16 or 32Mb (2 or 4MB).
Well if 040 is 4MB and 080 is 8MB, I would hope there is a 160 at 16MB and so on; or do engineers use a secret numbering system :-)
Secret numbering system. 040 is 4 Mbit = 512 kByte 080 is 8 Mbit = 1 MByte 160 is 16 Mbit = 2 MByte
I used to do boot CDs pretending to be 2.8Mb floppies, and would be happy with a 4Mb chip to get a Linux kernel into.
No, these were 2.88 MByte floppies, not 2.88 Mbit floppies. Even the SST49LF160 chip is smaller than that floppy.
Regards, Carl-Daniel
Carl-Daniel Hailfinger wrote:
On 26.10.2008 15:39, Chris Lingard wrote:
Corey Osgood wrote:
On Sat, Oct 25, 2008 at 11:13 AM, Chris Lingard <chris@stockwith.co.uk mailto:chris@stockwith.co.uk> wrote: The board comes with a ITE IT8716F 4MB chip; but that is compatible with SST49LF040A chips. I already have these and some SST49LF080A chips; just wish there were 160 or 320MB
I'm hoping that's a typo, SST49LF080 is 8Mb (that's 8 megabits, or 1 megabyte), larger chips would be 16 or 32Mb (2 or 4MB).
Well if 040 is 4MB and 080 is 8MB, I would hope there is a 160 at 16MB and so on; or do engineers use a secret numbering system :-)
Secret numbering system. 040 is 4 Mbit = 512 kByte 080 is 8 Mbit = 1 MByte 160 is 16 Mbit = 2 MByte
I used to do boot CDs pretending to be 2.8Mb floppies, and would be happy with a 4Mb chip to get a Linux kernel into.
No, these were 2.88 MByte floppies, not 2.88 Mbit floppies. Even the SST49LF160 chip is smaller than that floppy.
Regards, Carl-Daniel
LOL
We use different terms
To me a Mb is one million bytes And a MB is one million bits
But we all agree in the end
Chris Lingard
On Sun, Oct 26, 2008 at 03:37:23PM +0000, Chris Lingard wrote:
LOL
We use different terms
To me a Mb is one million bytes And a MB is one million bits
Oh, wow, that's completely the opposite of what I've always used/seen. Where does this come frome?
Thanks, Ward.
On Sun, Oct 26, 2008 at 8:43 AM, Ward Vandewege ward@gnu.org wrote:
On Sun, Oct 26, 2008 at 03:37:23PM +0000, Chris Lingard wrote:
LOL
We use different terms
To me a Mb is one million bytes And a MB is one million bits
Oh, wow, that's completely the opposite of what I've always used/seen. Where does this come frome?
it's not standard usage but it is very english-language centric.
B is > b and 8 is > 1, so typical usage is B is Bytes, and b is bits.
I've never seen B=bits and b = bytes, but, that said, lots of people (like me) are not careful about MB vs. mb.
ron
-
Carl-Daniel Hailfinger -
Chris Lingard -
Corey Osgood -
Peter Stuge -
ron minnich -
Ward Vandewege