fastboot cmdline


9 posts
by alpha_one_x86 » Mon Jul 09, 2012 7:29 am
Hello, I use "fastboot" into my command line to boost the boot time. But with the official kernel, it's not work with the raspberry pi. Somebody with serial can diag it?

Thanks.
Dev of Ultracopier (Supercopier/Teracopy like)
Posts: 25
Joined: Sat Dec 24, 2011 4:45 pm
by jojopi » Mon Jul 09, 2012 12:33 pm
"fastboot" is not a parameter understood by the mainstream linux kernel. In whichever distribution you have used this previously it is either a non-standard kernel patch, or more likely a leftover parameter that is passed on to user-space and affects the way the init scripts run.

During the boot sequence in most Pi distros you will see that the kernel messages are in gray and preceded by a time code, while the user-space messages have a colour-coded ok/fail status. The user-space stuff normally takes much longer and would be a better target for optimization.
User avatar
Posts: 2132
Joined: Tue Oct 11, 2011 8:38 pm
by alpha_one_x86 » Mon Jul 09, 2012 1:17 pm
2.6.29 brings 'fastboot' kernel parameter:
http://lwn.net/Articles/314808/
https://bbs.archlinux.org/viewtopic.php?id=69258
I'm in wrong? I use it since lot of time.

In my case, the user space is done into less than a second.
Dev of Ultracopier (Supercopier/Teracopy like)
Posts: 25
Joined: Sat Dec 24, 2011 4:45 pm
by jojopi » Mon Jul 09, 2012 1:58 pm
alpha_one_x86 wrote:2.6.29 brings 'fastboot' kernel parameter: http://lwn.net/Articles/314808/
That article describes a parameter that was added in 2.6.29 and removed again in 2.6.30, over three years ago.
In my case, the user space is done into less than a second.
So how long does the kernel take and what were you hoping to improve.
User avatar
Posts: 2132
Joined: Tue Oct 11, 2011 8:38 pm
by alpha_one_x86 » Mon Jul 09, 2012 2:08 pm
It make 6s to boot. Well, my sd card is slow (class 4).
I'm trying do my own kernel (like on all my desktop), but lot of time, raspberry pi refuse to boot (ok down + color test on hdmi). Then I need progress very slowly and recompil with each new options into the kernel.
Dev of Ultracopier (Supercopier/Teracopy like)
Posts: 25
Joined: Sat Dec 24, 2011 4:45 pm
by keylevel » Mon Jul 09, 2012 8:28 pm
Do you use kernel compression? This seems to stop the kernel booting some of the time. If you are using it, try rebuilding with it off to see if that makes a difference.
Posts: 13
Joined: Sun May 20, 2012 6:44 pm
by alpha_one_x86 » Mon Jul 09, 2012 10:15 pm
I have use same config than the official kernel or debian kernel (zcat /proc/config.gz > .config), then with gzip.
I will try without, any other config with frequent fail to boot + display? If I have the display I can fix it my self.
Dev of Ultracopier (Supercopier/Teracopy like)
Posts: 25
Joined: Sat Dec 24, 2011 4:45 pm
by alpha_one_x86 » Tue Jul 10, 2012 7:44 am
Exactly, the zImage not work here!!! the Image or old way (mkimage/imagetool-uncompressed.py) work.

The it's wrong into the wiki what I have see (http://elinux.org/RPi_Kernel_Compilation):
With the latest firmware (available from https://github.com/raspberrypi/firmware), you no longer need to create an explicit kernel image; you can directly use Image or zImage from the kernel build process (under 'arch/arm/boot/' of the linux directory) as /boot/kernel.img.

The compressed kernel should be supported in all case, to prevent this kind of error + gain space 9 speed boot up. Why the loaded not support it?
Dev of Ultracopier (Supercopier/Teracopy like)
Posts: 25
Joined: Sat Dec 24, 2011 4:45 pm
by alpha_one_x86 » Wed Jul 11, 2012 11:16 am
Hello, with the last compression to try fix the compression:
arch/arm/mach-bcm2708/include/mach/uncompress.h:61 error: UART0_CLOCK underclared
Dev of Ultracopier (Supercopier/Teracopy like)
Posts: 25
Joined: Sat Dec 24, 2011 4:45 pm