Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #176974 > unrolled thread
| Started by | Mattia Oss <mais.toast@gmail.com> |
|---|---|
| First post | 2017-01-24 17:20 +0100 |
| Last post | 2017-01-26 20:50 +0100 |
| Articles | 3 on this page of 23 — 7 participants |
Back to article view | Back to linux.debian.user
Early boot became slower Mattia Oss <mais.toast@gmail.com> - 2017-01-24 17:20 +0100
Re: Early boot became slower Sven Joachim <svenjoac@gmx.de> - 2017-01-24 17:40 +0100
Re: Early boot became slower Mattia Oss <mais.toast@gmail.com> - 2017-01-24 18:10 +0100
Re: Early boot became slower Mattia Oss <mais.toast@gmail.com> - 2017-01-25 16:30 +0100
Re: Early boot became slower Sven Joachim <svenjoac@gmx.de> - 2017-01-25 20:40 +0100
Re: Early boot became slower Mattia Oss <mais.toast@gmail.com> - 2017-01-26 18:50 +0100
Re: Early boot became slower Felix Miata <mrmazda@earthlink.net> - 2017-01-26 20:20 +0100
Re: Early boot became slower Mattia Oss <mais.toast@gmail.com> - 2017-01-27 01:40 +0100
Re: Early boot became slower Felix Miata <mrmazda@earthlink.net> - 2017-01-27 10:20 +0100
Re: Early boot became slower Mattia Oss <mais.toast@gmail.com> - 2017-01-27 18:00 +0100
Re: Early boot became slower Felix Miata <mrmazda@earthlink.net> - 2017-01-27 19:10 +0100
Re: Early boot became slower Lisi Reisz <lisi.reisz@gmail.com> - 2017-01-27 20:20 +0100
Early boot became slower Jonathan de Boyne Pollard <J.deBoynePollard-newsgroups@NTLWorld.com> - 2017-01-30 10:10 +0100
Re: Early boot became slower Felix Miata <mrmazda@earthlink.net> - 2017-01-30 11:30 +0100
Early boot became slower Jonathan de Boyne Pollard <J.deBoynePollard-newsgroups@NTLWorld.com> - 2017-01-30 23:50 +0100
Re: Early boot became slower Felix Miata <mrmazda@earthlink.net> - 2017-01-31 01:00 +0100
Re: Early boot became slower David Wright <deblis@lionunicorn.co.uk> - 2017-01-31 04:00 +0100
Re: Early boot became slower deloptes <deloptes@gmail.com> - 2017-01-31 18:30 +0100
Re: Early boot became slower deloptes <deloptes@gmail.com> - 2017-01-27 22:10 +0100
Re: Early boot became slower Mattia Oss <mais.toast@gmail.com> - 2017-01-28 18:20 +0100
Re: Early boot became slower deloptes <deloptes@gmail.com> - 2017-01-28 23:00 +0100
Re: Early boot became slower Felix Miata <mrmazda@earthlink.net> - 2017-01-28 23:10 +0100
Re: Early boot became slower deloptes <deloptes@gmail.com> - 2017-01-26 20:50 +0100
Page 2 of 2 — ← Prev page 1 [2]
| From | deloptes <deloptes@gmail.com> |
|---|---|
| Date | 2017-01-28 23:00 +0100 |
| Message-ID | <t4Jcm-6Pp-5@gated-at.bofh.it> |
| In reply to | #177074 |
Mattia Oss wrote: > BUT, I made a progress. :) > I installed linux-source-4.9 and compiled the kernel with the 4.8.0-1 > config. The result: it boots fast! :) > printk.time=1 as kernel param at boot would help you find out where it slows down. It looks like something takes more time to initialize, might be because in 4.8.0-2 it is a module. There were also some interesting stories about inteldrmfb, but I can't recall - it might be related. > This is the kernel log of the custom kernel: > https://github.com/maistoast/share/blob/master/kernel/log/4.9.2/dmesg_4.9.2--bymattia > > As you can see it uses simplefb and not vesafb. I'm quite sure that this > is the problem. As Sven Joachim pointed out, the Debian devs disabled > simplefb because it has problems with KMS framebuffer. Reading the link > he provided they disabled the X86_SYSFB and FB_SIMPLE options to fix > some bugs. I think there's no solution for me because these options are > not enabled in the Debian kernel anymore.. :/ > > Se either I use a custom kernel, or I keep my sweet fat characters with > the Debian kernel. I prefer to build and keep custom kernel regards
[toc] | [prev] | [next] | [standalone]
| From | Felix Miata <mrmazda@earthlink.net> |
|---|---|
| Date | 2017-01-28 23:10 +0100 |
| Message-ID | <t4Jm1-77Y-13@gated-at.bofh.it> |
| In reply to | #177074 |
Mattia Oss composed on 2017-01-28 18:14 (UTC+0100): > As you can see it uses simplefb and not vesafb. I'm quite sure that this > is the problem. As Sven Joachim pointed out, the Debian devs disabled > simplefb because it has problems with KMS framebuffer. Reading the link > he provided they disabled the X86_SYSFB and FB_SIMPLE options to fix > some bugs. I think there's no solution for me because these options are > not enabled in the Debian kernel anymore.. :/ > Se either I use a custom kernel, or I keep my sweet fat characters with > the Debian kernel. I'm having no luck distinguishing between any "sweet fat characters" and any others from those blurry videos. All I can do is guess is that the difference you see is more subtle than your description. Over many many moons I've seen the init screens and framebuffer vttys use slightly different default fonts on some installations than on others, and I do prefer those I first saw used last century over those commonly seen more recently. I suppose simplefb and vesafb may indeed be using different 16x9 fonts, or maybe one or the other with 4.8 is using 16x8 instead of 16x9. When I boot stretch 4.8.x on host big41 here, I do see a subtle font switch around halfway through init, from a font I prefer, to one less liked. Capital "R" is a giveaway which I like or not, a very big upper loop on the not. "Slow" boot on this big41 Intel 3.0GHz Core2Duo host is an understatement. Boot times have been in the 4-8 minute range in Stretch for several months, but it's not unique to Stretch, and it isn't insanely long on every kernel on every installed OS. It mostly seems random, on a per initrd basis, some OK, some not, and not has been a continuous string on Stretch at least back to 4.7 on 01 Oct. Last Stretch 4.9 boot time was ~325 seconds. It's only ever happened on 64bit installations, and began only after various distros switched to using dracut for building initrds. I've mentioned these long boots, which can vary in extra length anywhere from under a minute to more than 13 minutes, in various threads going back over a year. Here are a few threads: http://www.spinics.net/lists/linux-initramfs/msg04173.html http://www.mail-archive.com/initramfs@vger.kernel.org/msg04168.html http://lists.opensuse.org/opensuse-kernel/2016-03/msg00024.html -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
[toc] | [prev] | [next] | [standalone]
| From | deloptes <deloptes@gmail.com> |
|---|---|
| Date | 2017-01-26 20:50 +0100 |
| Message-ID | <t3Ydt-2X9-61@gated-at.bofh.it> |
| In reply to | #177014 |
Mattia Oss wrote: > On Wed, Jan 25, 2017 at 08:33:16PM +0100, Sven Joachim wrote: >> On 2017-01-25 16:26 +0100, Mattia Oss wrote: >> >> > On Tue, Jan 24, 2017 at 05:59:42PM +0100, Mattia Oss wrote: >> >> I use grub2. I tried the "text" kernel parameter: it works but it >> >> obviously isn't what I was looking for. >> > >> > I tried with video=vesafb:off but it doesn't seem to work. I've >> > recompiled the kernel without vesafb but I get a blank screen (only at >> > the early phase). >> >> Does GRUB_GFXPAYLOAD_LINUX=text in /etc/default/grub help? Don't forget >> to run update-grub after changing that file. > > Yes as mentioned above this works but I have HUGE characters. > >> > I'm open to any suggestion... >> >> I usually put the graphics driver in the initramfs to load it as early >> as possible. >> >> # echo radeon >> /etc/initramfs-tools/modules >> # update-initramfs -u > > Thanks for the suggestions. I tried it but still got a blank screen. > At this point I think I'll stay with GRUB_GFXPAYLOAD_LINUX=text. > At least it's fast. I use following in /etc/default/grub as my notebook supports 1024x768 and 1366x768. The later being the native resolution. Perhaps you check with (ex.: xrandr) what your native resolution is and try it out. # The resolution used on graphical terminal # note that you can use only modes which your graphic card supports via VBE # you can see them in real GRUB with the command `vbeinfo' GRUB_GFXMODE=1366x768 #GRUB_GFXMODE=1024x768x24 #GRUB_GFXMODE=1360x768x8,1360x768 GRUB_GFXPAYLOAD_LINUX=keep you need update-grub after changing /etc/default/grub. regards
[toc] | [prev] | [standalone]
Page 2 of 2 — ← Prev page 1 [2]
Back to top | Article view | linux.debian.user
csiph-web