![]() |
Re: Introducing ubiboot N9 (multiboot OS loader)
I had the same problem yesterday, but reflashing ubiboot kernel fixed that!!
|
Re: Introducing ubiboot N9 (multiboot OS loader)
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 |
Re: Introducing ubiboot N9 (multiboot OS loader)
Quote:
If so, your log will be in /var/log/ubiboot.log |
Re: Introducing ubiboot N9 (multiboot OS loader)
Quote:
|
Re: Introducing ubiboot N9 (multiboot OS loader)
@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. :) |
Re: Introducing ubiboot N9 (multiboot OS loader)
Quote:
Maybe I should put a directory "histrorical" under the ubiboot main directory and move all non-current stuff there :D However the version number is the more important indication on which is the latest version. |
Re: Introducing ubiboot N9 (multiboot OS loader)
Quote:
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') ;) |
Re: Introducing ubiboot N9 (multiboot OS loader)
Quote:
2. What's the difference between dfl openmode and the l2fix openmode? |
Re: Introducing ubiboot N9 (multiboot OS loader)
l2fix need for faster booting kernel with kexec()
and all custom kernels are openmode :) |
Re: Introducing ubiboot N9 (multiboot OS loader)
Quote:
(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. |
All times are GMT. The time now is 07:21. |
vBulletin® Version 3.8.8