that was a post by Richard Smith, not Ron. my bad<br><br><div><span class="gmail_quote">2007/3/29, Oscar Molin <<a href="mailto:firstname.lastname@example.org">email@example.com</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi Peter<br>I said in an email to Corey about unbricking, that I think it might be possible to use the recovery part of the bios, appending that file from Intels own bios with a linuxbios.<br>I'm not 100% sure that works but it might. I forgot to forward that message to the mailing list.
<br>Intels bios structure is divided in 64k parts and there are 3-4 (or more depending on size i guess) that is the bios.<br>There are two that intels readme says is "recovery" bios (two identical files, two different places on the flash chip, I think)
<br>Then there is one which seems to have settings and "stuff".<br>If I can include these recvery files, and place the linuxbios in the regular bios files (with intels header info to make their flash-program accept it), I don't see a reason why it shouldn't work.
<br>Intels flasher also has a function that checks validity of the files before flashing, so if there is a checksum or something in the header that has to match, I would be able to solve it or even bruteforce it to make it accept my files instead.
<br>The reason I'm looking at this way of handling things, and not just soldering a socket the first thing I do, is:<br>1) I'm lazy<br>2) This is the way it has to be done if there is ever going to be Intel OEM support, since their flasher is AFAIK the only one that can flash there chips. Regular users can't be expected to solder bios chips.
<br><br>Thanks for the offer about the socket, but I'm too far away so I'll have to do it myself.<br><br>One last thing about 440bx.<br>Since Rons assembly code from v1 works, why is it that it is so hard to port it to C?
<br>Is it a compiler bug/feature that makes it not work correctly or what is the exact problem?<br>I've just started trying to understand this stuff and I read a post by Ron from 2004 where he had two boards working well apparently, he didn't mention any memory issues.
<br>If the working assembler code can be put in with the C code, and then change it line by line until it stops working, you should be able to pinpoint the problem right?<br>Maybe my thinking is flawed, I'm not a good programmer.
<br><br><div><span class="gmail_quote">2007/3/26, Peter Stuge <<a href="mailto:firstname.lastname@example.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">email@example.com</a>>:</span><div>
<span class="e" id="q_1119e0542001f3c8_1"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Mon, Mar 26, 2007 at 01:09:57PM +0200, Oscar Molin wrote:<br>> I have 2 Intel SE440BX and one Intel SE440bx-3 (it's some kind of<br>> subversion to sebx-2)<br>> These were very popular Intel OEM boards and were used by Dell,
<br>> compaq, fujitsu and the like.<br>> If someone wants info on what chips they have etc I'm willing to be<br>> of assistance and help with testing code one them to make them<br>> work. Since they all have Intels soldered on flash chips you can't
<br>> make too many mistakes but I have no problem losing one in the<br>> process as I don't need all of them.<br><br>I would wait with flashing until there was a practical way to unbrick<br>the board. :) That said, 440BX is getting some work in v2, so more
<br>systems to test on would be great. If need be I could replace your<br>flash with a socket. (I'm in Malmö)<br><br><br>//Peter<br><br>--<br>linuxbios mailing list<br><a href="mailto:firstname.lastname@example.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
</a><br><a href="http://www.linuxbios.org/mailman/listinfo/linuxbios" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://www.linuxbios.org/mailman/listinfo/linuxbios</a><br></blockquote></span>