Recover bricked bios

39 views
Skip to first unread message

stig atle steffensen

unread,
Sep 20, 2014, 8:14:19 AM9/20/14
to loongs...@googlegroups.com
Hi,
I was looking around in my bios - because I had issues booting any OS except from OpenBSD on it.
I then ran a command (I do not remember which one) which then caused it to never boot properly again.
It does not even show the Bios key shortcut text. it just shows the first boot picture, nothing else, no matter what I do.

Is there a way to reflash the bios to it's default? If so - how can I do this?

I appreciate any help I can get on this, I paid a lot for the machine and I would love to get it running again.

stig atle steffensen

unread,
Sep 20, 2014, 8:19:16 AM9/20/14
to loongs...@googlegroups.com
I booted it back up now, It does show the first 'boot' picture, and the text.
It's a Lemote Yeeloong 8089_B notebook.
But no matter how much I press delete or tab nothing happens, and it never get's past that splashscreen.

Lluís Batlle i Rossell

unread,
Sep 20, 2014, 6:14:42 PM9/20/14
to loongs...@googlegroups.com
I remember as if there wasn't any way to recover the bios other than changing
the flash chip. I remember as if it were a removable chip.

In that case you could also use an external programmer to rewrite it.

I remember this from some readings; I don't have a yeelong myself.
> --
> You received this message because you are subscribed to the Google Groups "loongson-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to loongson-dev...@googlegroups.com.
> To post to this group, send email to loongs...@googlegroups.com.
> Visit this group at http://groups.google.com/group/loongson-dev.
> For more options, visit https://groups.google.com/d/optout.

David Kuehling

unread,
Sep 20, 2014, 6:32:06 PM9/20/14
to loongs...@googlegroups.com
>>>>> "Lluís" == Lluís Batlle i Rossell <vi...@viric.name> writes:

> On Sat, Sep 20, 2014 at 05:19:16AM -0700, stig atle steffensen wrote:
>> I booted it back up now, It does show the first 'boot' picture, and
>> the text. It's a Lemote Yeeloong 8089_B notebook. But no matter how
>> much I press delete or tab nothing happens, and it never get's past
>> that splashscreen.
>>

> I remember as if there wasn't any way to recover the bios other than
> changing the flash chip. I remember as if it were a removable chip.

> In that case you could also use an external programmer to rewrite it.

> I remember this from some readings; I don't have a yeelong myself.

There may be some guys reading grub-devel [1] that have experience with
Yeeloong reflashing. These people developed a version of grub that can
be flashed as Yeeloong bios replacement (or at least they have for
Fuloong).

Maybe you can find somebody there who'd be willing to reflash your bios
flash IC and mail it back to you. Maybe you'll even end up with Grub
instead of the crappy pmon boot loader :)

cheers,

David

[1] https://lists.gnu.org/mailman/listinfo/grub-devel
--
GnuPG public key: http://dvdkhlng.users.sourceforge.net/dk2.gpg
Fingerprint: B63B 6AF2 4EEB F033 46F7 7F1D 935E 6F08 E457 205F

stig atle steffensen

unread,
Sep 21, 2014, 2:29:40 AM9/21/14
to loongs...@googlegroups.com
Yeah, that could be a solution.

Are there any information on what you need to flash it yourself?

--
Best regards, Stig Atle Steffensen.
http://stigatle.net

Lluís Batlle i Rossell

unread,
Sep 21, 2014, 4:00:26 AM9/21/14
to loongs...@googlegroups.com
I don't know. Usually it's a matter of knowing the flash chip, and find a
programmer hardware/software for it.

stig atle steffensen

unread,
Oct 3, 2014, 10:30:36 AM10/3/14
to loongs...@googlegroups.com, vi...@viric.name
I was able to fix it today.
I mistakenly thought the bios was bricked (since keyboard did not respond and it did not get past the bios splash screen),
today I sat down again, and now I feel stupid.
I simply hooked up a USB keyboard, and through that one I was able to get back into pmon.
So now everything works.
What i think happend was a bios setting that I reset, that caused the keyboard not to get initialized, then it got stuck there.

Anyways - I wanted to say its solved, just in case someone else is as stupid as myself one day.
Reply all
Reply to author
Forward
0 new messages