SliTaz Forum

RaspPi Kernel performance

(5 posts) (2 voices)

• Started 10 years ago by pirandr
• Latest reply from pirandr
• This topic is not a support question

Tags:

No tags yet.

1. 

   pirandr
   

   offline

   Member

   Hi everyone and thanks for getting so much working!

   Dillo seems to be running just fine in X now!

   However, to run X, I needed to update the kernel (I'm booting from USB key so I normally don't change the first FAT32 partition except for putting in different cmdline.txt. I'm doing this so I can switch distributions and test things quickly). I was using 3.6.x before and 3.10.33 now.

   However, there was a noticeable speed drop just about everywhere. This isn't something Slitaz specific, of course but I was just wondering if anyone else noticed. I tried removing the frequency related lines in config.txt but the speed remained the same. In the old kernel version, I didn't have any overclocking enable (that I know of). Its more or less a stock boot partition from early 2013 where I added some screen resolution parameters (I've put them in the new config as well).

   Boot timer

   More on topic with Slitaz, would it be possible to get the boot timer back? the one that says something like

   Welcome to your box: 10s

   Of course it doesn't count the kernel blob but seems like it would still be useful for estimates.

   3.6.x behaviour

   Back in 3.6.x (I can check the exact version if this is important), everything ran more or less fine, even directfb with dfbterm. But X hangs when I start slim. I do get to see the login screen with the picture of a raspberry and root pre-filled in but can't do anything then.

   The only error I could find in the Xorg.?.log is

   <br />
   (EE) FBDEV(0): FBIOBLANK: Operation not permitted<br />

   but I get these errors now even when things <i>are</i> working.

   New forum

   I'm making separate topics now since we got a brand new subforum for ARM. Just tell me if I should put everything in one post instead.

   Posted 10 years ago #
2. 

   pirandr
   

   offline

   Member

   So the latest build seem to be much faster. I can get to a prompt in about 10s! And not that much more even for a GUI! Although I did change a few other things in the meantime (SD card, USB key) but I didn't notice anything special about them.

   But when my system accidentally broke (/usr/ was deleted by accident), I could boot into a console in 2-3s! And it was just an initramfs (does slitaz even have an initramfs? I guess we are using busybox anyway). Now I'd like to be able to do this deliberately. Be able to boot with (almost) nothing, just a USB keyboard and the ability to read/write text files on the USB stick (no network, no graphics, no detecting other devices if that helps).

   Posted 9 years ago #
3. 

   pirandr
   

   offline

   Member

   So of course I went ahead and played with /etc/init.d/rcS.

   It seems that for mostly what I want, I don't need most of it at all! About the first 40 lines seems to be enough, right before it checks for udevd. Timing rcS alone with time (after booting with a missing rcS) gives real 0.09s (compared to real 7.79s for the default rcS (base image, no X).

   I think the network parts eat up a lot of that but that might depends on how fast your dhcp server boots. On the other hand, I wouldn't mind having the network services be brought up in parallel to login (I don't type that fast!).

   If you want to live dangerously, you can even replace getty by /bin/sh in /etc/inittab. This gets 5 to 7s total boot to console time depending on how it is measured (7 is from plugging it it and 5 is from first seeing the "coloured square" RPi first screen, plus the time for me to react and press a stopwatch).

   I don't know if this is useful for anyone else though, but it works for me. I have a mobile use for the RPi and since it doesn't have a sleep mode, to avoid draining the battery, I just wanted to shut it off and turn it back on again, which is why startup time is so important. I still need to get audio working...

   Posted 9 years ago #
4. 

   necrophcodr
   

   offline

   Member

   Audio should really not be the biggest issue. Someone else posted on these forums about that, and seemingly got it solved I believe. If not, I do believe it is more a matter of identifying the exact issue, and putting the correct solution to work.

   Posted 9 years ago #
5. 

   pirandr
   

   offline

   Member

   This probably belongs in the audio thread

   http://forum.slitaz.org/topic/audio

   but there are at least two people on this forum I can think of who managed to get audio working at some point. For me, that never happened. It blocks/fails on pcm_write in alsa-lib which I think is basically saying that "there's space for 0 more bytes of audio" all the time.

   Does audio work for you? I hope its not my setup and/or the kernel module.

   Posted 9 years ago #

RSS feed for this topic

Reply

You must log in to post.