On Fri, Apr 17, 2009 at 11:53 AM, Sascha Gering <span dir="ltr"><<a href="mailto:haxxx@gmx.li">haxxx@gmx.li</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi Filip,<br>
<br>
Here is my output:<br>
<br>
> root@MuhKo:~# cat /proc/cmdline<br>
> loglevel=4 console=tty0 console=ttySAC2,115200 init=/sbin/init ro mtdparts=physmap-flash:-(nor);neo1973-nand:0x00040000(qi),0x00040000(depr-ub-env),0x00800000(kernel),0x000a0000(depr),0x00040000(identity-ext2),0x0f6a0000(rootfs) g_ether.host_addr=00:1F:11:01:6D:2E g_ether.dev_addr=00:1F:11:01:6D:2E rootfstype=jffs2 root=/dev/mtdblock6<br>
<br>
> root@MuhKo:~# cat /boot/append-GTA02<br>
> rw rootdelay=5 loglevel=1 quiet<br>
<br>
Hmm, why is there a "loglevel=4" in my cmdline, but "loglevel=1" in my<br>
append file?<br>
<br>
Sascha<br>
<br>
Filip Onkelinx schrieb:<br>
<div class="im">> Hi all,<br>
><br>
> I know boot speed and resume speed is influenced by kernel boot<br>
> parameters: the more kernel/debug messages displayed (on rather slow<br>
> framebuffer), the slower the device will boot/resume. Might want to<br>
> compare boot params (cat /proc/cmdline , look for loglevel= and console= )<br>
><br>
> F.<br>
</div></blockquote><div><br>The FSO boots very quickly (without qte), what I've found is that it takes a long time to launch qtextended. It seems to launch once, abort and then launch again.<br>In the AtChat log output, I see that it tries different times to send a Ctrl-Z command to the modem, and only succeeds on the third time, which might explain the slow boot as well. <br>
<br>Franky<br></div></div>