Config Linux BIOS: Is it possible (Re: [OLPC-devel] DOS in Windows Flash Disaster Recovery Utility?

[supat at supat.eu.org]

Hi Jim Gettys,

Thank you.

It was my careless to read OLPC with below message:

=========
If you are still having trouble

Don't power off or reset the OLPC board and please get in contact with us, 
on IRC or via email, so that we have a chance to see what has gone wrong. 
If you power off or reset the board, we will have no way to diagnose the 
problem short of returning the board to OLPC and time consuming hardware 
diagnosis, and even then, may not be able to figure out what went wrong. 
=========

After reading carelessly I think there is NO way to bring back old BIOS.
I did ask question about that earlier but no one explain it.

At this moment I bring back old BIOS already and every thing go back.
(Marvell wireless can work under slackware)

On Tue, 5 Sep 2006, Jim Gettys wrote:

> Supat,
>
> I think you have 4 choices here:
>
> o you can debug why the Marvell wireless isn't working on Slackware.
> You should be using our latest drivers and firmware.  I asked before if
> you were using the development kernel that David Woodhouse hosts on
> Infradead.org, and you did not answer.

It was my careless. Sorry.
I used the .git buildrom olpc-rc2 kernel that s/o inform us pass thru this 
forum. I am sure it was updated olpc kernel that we use to build linux 
BIOS.

>
> I repeat: not all changes for supporting OLPC have made it to
> kernel.org, and/or back downstream to distributions, though we work hard
> to see them integrated as quickly as possible.  You should not expect
> either slackware's standard kernel or a kernel.org kernel to run
> unchanged at this date; the wireless driver has *not* gone into Linus'
> tree yet.  As a convenience, David keeps a git repository of all of our
> work integrated and believed to be working, so that you do not have to
> put together the individual drivers from different locations.

Yes. I know that. Because you say it very often in here.


> o you can restore Insyde BIOS, and set the date back to mid-summer, and
> run what you had working before.

Actually I change the date several times.
Not because I want to cheat but to make kernel to work correctly it always 
check the date. If .config is older than old config date then it will 
waste the time of compiling.



> o you can get a USB wireless interface as a work-around; you'll need the
> correct USB driver module for that, of course.

I don't understand. What I will do is to randomly pick up recent olpc 
image and see what one can run on slackware with USB wireless to work 
correctly.


> o you can run full Fedora on the boards off a USB disk.

I will not do so. Sorry. I love slackware too much and proud of that. I 
will not change to use other dist.


> None of us at OLPC use Slackware: we use either Fedora or Ubuntu, and
> therefore aren't able to help you; and are using Fedora on the OLPC
> boards.  In the past we've had Ubuntu running on them as well (though
> installation was difficult). And there are few if any others on the
> mailing list who run Slackware.

I recommend you and your team to take a look on slackware and I assure you 
will change your mind to use slackware to develop OLPC :)

> And the current X Window System "amd" driver are not on ftp.x.org, but
> found at http://xorg.freedesktop.org/wiki/ in the current development
> modules now in git.  They will be present in the X11R7.2 release this
> fall, but you can get them immediately in the X development environment.

Thank you. I got the old Xorg 7.1 but it can make VGA of OLPC to work 
correctly on your recent .img
Ofcause I put in the amd driver from OLPC.

> I don't know there is much more we can do for you.
>                                        Regards,
>                                           - Jim Gettys

Your messages to tell me that I can olpcflash back is already helpful. 
Thank you :)

supat