I've been trying to stop the boot animation from showing, but for now without any luck. The problem is I don't know how it's started. I've been looking in the init.d folder but can't find anything there. Also looked a bit at the kernel code, but not sure where to search for this code. Does anyone perhaps have any pointers?

The ultimate goal is to have the DR shutdown and boot without updating the screen, to make it more book-like. I have the shutdown process figured out, but I'm stuck on the boot animation.

Device: iRex iLiad, in love with iRex DR800S. Also a K4NT. Now a Kobo Aura

Quote:

Originally Posted by rvs

Hi,

I've been trying to stop the boot animation from showing, but for now without any luck. The problem is I don't know how it's started. I've been looking in the init.d folder but can't find anything there. Also looked a bit at the kernel code, but not sure where to search for this code. Does anyone perhaps have any pointers?

The ultimate goal is to have the DR shutdown and boot without updating the screen, to make it more book-like. I have the shutdown process figured out, but I'm stuck on the boot animation.

Thanks in advance for any ideas.

Best regards,

Roderick

I guess boot image is inside /boot/zImage-2.6.24-irex file, so you'd need to unpackage that file to control boot process.
Sadly enough it doesn't look like any known format.

I didn't manage to change the bootloader (and also skipped the kernel), but I have found a pretty usable workaround.

I now make a screenshot on shutdown and use this screenshot in an init.d script. It now takes about 15 seconds before the screenshot shows up, not what I was looking for, but still a substantial upgrade from the >1 minute it usually takes to boot.

Interestingly, the real boot time also seems to decrease by about 12 seconds.

There's only one possibly large downside: the screenshot (>1 MB) is written to the internal memory everytime the DR shuts down, possibly reducing the lifetime of the device.

I didn't manage to change the bootloader (and also skipped the kernel), but I have found a pretty usable workaround.

I now make a screenshot on shutdown and use this screenshot in an init.d script. It now takes about 15 seconds before the screenshot shows up, not what I was looking for, but still a substantial upgrade from the >1 minute it usually takes to boot.

Interestingly, the real boot time also seems to decrease by about 12 seconds.

There's only one possibly large downside: the screenshot (>1 MB) is written to the internal memory everytime the DR shuts down, possibly reducing the lifetime of the device.

that's interesting, could you please explain exactly us what you did ?

You can make a screenshot simply by copying the framebuffer to a file (e.g. cat /dev/fb0 > /usr/share/screenshot.raw). To copy the screenshot back into the framebuffer you do the reverse and do a screen update. For the screen update I made a slightly modified version of the "blank" executable.

Then it's a matter of modifying and creating /etc/init.d scripts (in particular the "blank" script) and changing the Irex firmware (the hardest part) to stop updating the screen on boot and shutdown and create the screenshot on shutdown.

The reason I copy the screenshot to the internal memory is because the sd-card isn't mounted yet when the init scripts run. I tried mounting the sd-card myself in an init script, but it failed for some reason.

If you're really interested and have a developer environment I can post the sources as soon as I've worked out the kinks and cleaned up the code a bit (there are still a few bugs, one of which is that it won't boot on the qemu ).