Menu

Main Menu
Talk Get Daily Search

Member's Online

    User Name
    Password

    Introducing ubiboot N9 (multiboot OS loader)

    Reply
    Page 110 of 140 | Prev | 100   108     109   110   111     112   120 | Next | Last
    Lucazz990 | # 1091 | 2014-01-05, 18:09 | Report

    I had the same problem yesterday, but reflashing ubiboot kernel fixed that!!

    Edit | Forward | Quote | Quick Reply | Thanks

     
    marmistrz | # 1092 | 2014-01-05, 19:58 | Report

    Hi,

    I've just installed ubiboot, and have some doubts...

    1. I can't notice the dfl openmode kernel. Should it be added manually
    2. What's the difference between dfl openmode and the l2fix openmode?
    3. What are those other entries in the Harmattan section of ubiboot?

    Thanks

    Edit | Forward | Quote | Quick Reply | Thanks

     
    juiceme | # 1093 | 2014-01-05, 21:22 | Report

    Originally Posted by Ta76eem View Post
    it is Boot Menu Script not found
    no ubiboot.log was created
    Do you have an older ubiboot version installed, then?
    If so, your log will be in /var/log/ubiboot.log

    Edit | Forward | Quote | Quick Reply | Thanks
    The Following User Says Thank You to juiceme For This Useful Post:
    hrbani

     
    juiceme | # 1094 | 2014-01-05, 21:24 | Report

    Originally Posted by marmistrz View Post
    Hi,

    I've just installed ubiboot, and have some doubts...

    1. I can't notice the dfl openmode kernel. Should it be added manually
    2. What's the difference between dfl openmode and the l2fix openmode?
    3. What are those other entries in the Harmattan section of ubiboot?

    Thanks
    There are a fair number of "example entries" as the config was oiginally pulled from my device which had a number of test kernels installed

    Edit | Forward | Quote | Quick Reply | Thanks
    The Following User Says Thank You to juiceme For This Useful Post:
    hrbani

     
    peterleinchen | # 1095 | 2014-01-05, 22:11 | Report

    @juiceme

    It seems there are a few people out there fetching older revisions/kernels and 'claiming' a non-working ubiboot.

    One suggestion/beg from my side.
    What would you think of changing the naming style of your revisions to something like
    ubiboot_vX.Y.Z_yyyymmdd ?
    This way the listing would always be ordered and easily searchable. And it would make it easier to fetch the latest revision.
    The way you give dates is local way and confusing (english/american style) /and not sortable. [in your notation: 15 aug is earlier than 17 may, but later 12 dec]

    Just a (late) thought.

    Edit | Forward | Quote | Quick Reply | Thanks

     
    juiceme | # 1096 | 2014-01-05, 22:21 | Report

    Originally Posted by peterleinchen View Post
    @juiceme

    It seems there are a few people out there fetching older revisions/kernels and 'claiming' a non-working ubiboot.

    One suggestion/beg from my side.
    What would you think of changing the naming style of your revisions to something like
    ubiboot_vX.Y.Z_yyyymmdd ?
    This way the listing would always be ordered and easily searchable. And it would make it easier to fetch the latest revision.
    The way you give dates is local way and confusing (english/american style) /and not sortable. [in your notation: 15 aug is earlier than 17 may, but later 12 dec]

    Just a (late) thought.
    You do have a point there... In the newer versions am using the finnish way of marking dates, that is ddmmyyyy and indeed that does not sort correctly with unix directory listing. On some of the earlier releases I used just what I happened to make it at that given moment.

    Maybe I should put a directory "histrorical" under the ubiboot main directory and move all non-current stuff there

    However the version number is the more important indication on which is the latest version.

    Edit | Forward | Quote | Quick Reply | Thanks
    The Following User Says Thank You to juiceme For This Useful Post:
    hrbani

     
    peterleinchen | # 1097 | 2014-01-05, 22:28 | Report

    Originally Posted by juiceme View Post
    Maybe I should put a directory "historical" under the ubiboot main directory and move all non-current stuff there

    However the version number is the more important indication on which is the latest version.
    Yeah, maybe.
    But even same revision had small (date numbered) updates.

    Again, just a thought. I will find my way through your 'jungle' (erm sorry: 'ice cave')

    Edit | Forward | Quote | Quick Reply | Thanks

    Last edited by peterleinchen; 2014-01-05 at 22:31.
    The Following User Says Thank You to peterleinchen For This Useful Post:
    juiceme

     
    marmistrz | # 1098 | 2014-01-06, 09:09 | Report

    Originally Posted by juiceme View Post
    There are a fair number of "example entries" as the config was oiginally pulled from my device which had a number of test kernels installed
    Thanks, but repeating my question, which wasn't replied
    2. What's the difference between dfl openmode and the l2fix openmode?

    Edit | Forward | Quote | Quick Reply | Thanks

     
    coderus | # 1099 | 2014-01-06, 09:24 | Report

    l2fix need for faster booting kernel with kexec()

    and all custom kernels are openmode

    Edit | Forward | Quote | Quick Reply | Thanks
    The Following 3 Users Say Thank You to coderus For This Useful Post:
    hrbani, juiceme, marmistrz

     
    juiceme | # 1100 | 2014-01-06, 14:25 | Report

    Originally Posted by marmistrz View Post
    Thanks, but repeating my question, which wasn't replied
    2. What's the difference between dfl openmode and the l2fix openmode?
    It is exactly as @coderus states. The dfl-openmode is the simplest aegis-neutering modification on kernel, it stubs out the aegisfs calls so that if caller is root everything is always allowed.
    (in contrast, in the Closed Mode kernels everything is checked against the aegis capability flags the caller is holding, regardless of whether it is user or root...)

    The l2-fix is a change on the L2-cache enabling code in the kernel chainloading sequence when it is started as a 2nd stage kernel via kexec() from previously running kernel. There are number of things that are done when kernel is restarted, among them the L2 cache is turned off before the kexec() call.
    Now, originally the cache was not re-enabled until very much later, actually only after the CPU went to sleep first time after a whole lot of things should already been initialized and done. This meant that the boot was extremely slow, taking minutes of wathching the spinner rotate before it got to user-interactive stage.

    Edit | Forward | Quote | Quick Reply | Thanks
    The Following 2 Users Say Thank You to juiceme For This Useful Post:
    hrbani, marmistrz

     
    Page 110 of 140 | Prev | 100   108     109   110   111     112   120 | Next | Last
vBulletin® Version 3.8.8
Normal Logout