[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Lemote YeeLoong 8089 mips based notebook repository switch



Dear all,

Yeeloong Pmon manual fully translated and available in both English and
Chinese here:
http://olph.gdium.com/wiki/doku.php/manual:pmon_full

Hope that helps.

Fred

fxzhang@ict.ac.cn wrote:
> Thank you very much.
>   
>> Hi!
>>
>> I have started the Pmon manual translatation but it might only be
>> finished after Chinese New Year. Hopefully I might make the translation
>> available on a wiki soon so I can get more volunteers to help translate
>> the 28 pages.
>>
>> I'll let the list know once this is done.
>>
>> Fred
>>
>> fxzhang@ict.ac.cn wrote:
>>     
>>> To rescue a yeeloong,we have several methods:
>>>   download a rescue kernel from
>>> http://www.lemote.com/software/8.9inch/loonux/V1.1.0/rescue
>>>
>>> load it via usb, then you can have a shell in ramdisk to do things.
>>>
>>> to reinstall the whole machine, just put the whole V1.1.0 directory into
>>> a
>>> usb stick or disk(first ext2/3 partition, root directory), then use the
>>> 'recover' function of the pmon(press tab key during boot up).
>>>
>>> For more about pmon, we have a pmon manual but unfortunately it is now
>>> in
>>> Chinese, but you should be able to guess most of the content because the
>>> commands are always in English:) Here:
>>> http://www.lemote.com/Files/DownLoad/8089PMON%CA%B9%D3%C3%CA%D6%B2%E1.pdf
>>> I will try to arrange the translation.
>>>
>>> Packages modified by Lemote that might lead to breakage:
>>>   1. the x server. To make the server know how to mmap the io port. It
>>> seems the latest X server/linux kernel has standard way to do this now.
>>>   2. linux kernel. We have to provide custom kernel before it is
>>> accepted
>>> by debian official, the source is provided via
>>> http://dev.lemote.com/git?p=linux_loongson.git;a=summary
>>>
>>> And to compile the kernel natively, we need to patch the binutils a bit
>>> to
>>> workaround a bug between CPU/southbridge.
>>>
>>> Any difficulties, please ask us as we probably can give answers.
>>>
>>> Best Regards
>>>
>>>
>>>       
>>>> That's why the gNewSenseToMips team is figuring out smart ways to
>>>> rescue a
>>>> yeeloong laptop or a fuloong mini box, after a successful breakage ;-)
>>>> resulting
>>>> from aventurous hacking experiments.
>>>>
>>>> Best regards
>>>>
>>>> Samy
>>>>
>>>>
>>>>
>>>>         
>>>>> The Debian standard Kernel does not work very well with the Loonsong
>>>>> CPU
>>>>> I have the Evaluation Board for the CPU from there  Laptop  since  I
>>>>> am
>>>>> building my own Computer.
>>>>>
>>>>>
>>>>>           
>>>>>> Yes I had this one in my bookmarks but it doesn't mention
>>>>>> (yet) the slowness of the www.lemote.com repository from
>>>>>> Europe. When I have enough information I'll update the wiki :).
>>>>>>
>>>>>>             
>>>>> I live in Strasbourg and get the GSM  Network  from  O2/Telephonica
>>>>> and
>>>>> with HSDPA I can access thr Lemote server with arround 480 kByte/Sek.
>>>>>
>>>>> A friend, which live in the same hause as me,  with  Wanadoo/Orange
>>>>> can
>>>>> access the site with 300 kByte/Sek.
>>>>>
>>>>> Thanks, Greetings and nice Day/Evening
>>>>>     Michelle Konzack
>>>>>     Systemadministrator
>>>>>     24V Electronic Engineer
>>>>>     Tamay Dogan Network
>>>>>     Debian GNU/Linux Consultant
>>>>>
>>>>>
>>>>> --
>>>>> Linux-User #280138 with the Linux Counter, http://counter.li.org/
>>>>> ##################### Debian GNU/Linux Consultant
>>>>> #####################
>>>>> <http://www.tamay-dogan.net/>
>>>>> <http://www.can4linux.org/>
>>>>> Michelle Konzack   Apt. 917                  ICQ #328449886
>>>>> +49/177/9351947    50, rue de Soultz         MSN LinuxMichi
>>>>> +33/6/61925193     67100 Strasbourg/France   IRC #Debian (irc.icq.com)
>>>>>
>>>>>
>>>>>           
>>>> --
>>>> To UNSUBSCRIBE, email to debian-mips-REQUEST@lists.debian.org
>>>> with a subject of "unsubscribe". Trouble? Contact
>>>> listmaster@lists.debian.org
>>>>
>>>>
>>>>
>>>>
>>>>         
>>>
>>>
>>>       
>>     
>
>
>
>   


Reply to: