• kernel 4.16

    From Benny Pedersen@2:230/0 to All on Thu Apr 5 21:45:20 2018
    Hello All!

    anyone tryed it ?

    sadly cant build firmware anymore in the kernel, seems it needs to be external build now


    Regards Benny

    ... there can only be one way of life, and it works :)

    --- Msged/LNX 6.2.0 (Linux/4.9.76-gentoo-r1 (i686))
    * Origin: I will always keep a PC running CPM 3.0 (2:230/0)
  • From Maurice Kinal@1:153/7001 to Benny Pedersen on Thu Apr 5 21:02:48 2018
    Hey Benny!

    anyone tryed it ?

    Yes I have tried it back with the 4.15.x kernels which is when they stopped supplying it with the regular kernel source.

    ----- '<Esc>:read !uname -a' starts
    Linux mikey 4.16.0 #2 SMP Tue Apr 3 23:36:08 UTC 2018 x86_64 Intel(R) Atom(TM) CPU C2758 @ 2.40GHz GenuineIntel GNU/Linux
    ----- '<Esc>:read !uname -a' ends

    All 8 penguins are properly displayed at bootup with the builtin - could be modular - AST2400 driver. However still having issues building a kernel with the soon to be released gcc-8 compiler but gcc-7.3.0 works just fine which is still the default compiler here as we speak.

    sadly cant build firmware anymore in the kernel, seems it needs
    to be external build now

    Just as well since there were some of the firmware I needed with the external source that wasn't provided with the regular source anyhow. This way most, if indeed not all, firmware can be found in the external source. In my particular
    situation I can find all that I require in the external source which I needed before so it's not really a big deal.

    Life is good,
    Maurice

    ... Don't cry for me I have vi.
    --- GNU bash, version 4.4.19(1)-release (x86_64-silvermont-linux-gnu)
    * Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001)
  • From Benny Pedersen@2:230/0 to Maurice Kinal on Fri Apr 6 10:42:32 2018
    Hello Maurice!

    05 Apr 2018 21:02, Maurice Kinal wrote to Benny Pedersen:

    Yes I have tried it back with the 4.15.x kernels which is when they stopped supplying it with the regular kernel source.

    ----- '<Esc>:read !uname -a' starts
    Linux mikey 4.16.0 #2 SMP Tue Apr 3 23:36:08 UTC 2018 x86_64 Intel(R) Atom(TM) CPU C2758 @ 2.40GHz GenuineIntel GNU/Linux
    ----- '<Esc>:read !uname -a' ends

    ----- uname-a begins -----
    Linux themultixpoint 4.16.0-gentoo #2 SMP Thu Apr 5 23:25:04 CEST 2018 i686 Intel(R) Pentium(R) 4 CPU 2.60GHz GenuineIntel GNU/Linux
    ----- uname-a ends -----

    All 8 penguins are properly displayed at bootup with the builtin -
    could be modular - AST2400 driver. However still having issues
    building a kernel with the soon to be released gcc-8 compiler but gcc-7.3.0 works just fine which is still the default compiler here as
    we speak.

    ----- gcc begins -----
    [I] sys-devel/gcc
    Available versions:
    (2.95.3) [M]~2.95.3-r10^s
    (3.3.6) [M]~3.3.6-r1^s
    (3.4.6) [M]3.4.6-r2^s
    (4.0.4) [M]**4.0.4^s
    (4.1.2) [M]4.1.2^s
    (4.2.4) [M]~4.2.4-r1^s
    (4.3.6) [M]4.3.6-r1^s
    (4.4.7) [M]4.4.7^s
    (4.5.4) [M]4.5.4^s
    (4.6.4) [M]4.6.4^s
    (4.7.4) [M]4.7.4-r1^s
    (4.8.5) [M]4.8.5-r1^s
    (4.9.4) [M]4.9.4^s
    (5.4.0) [M]5.4.0-r4^s
    (6.4.0) 6.4.0^s 6.4.0-r1^s
    (7.2.0) ~7.2.0^s ~7.2.0-r1^s
    (7.3.0) ~7.3.0^s **7.3.0-r1^s
    {altivec awt boundschecking cilk +cxx d debug doc fixed-point +fortran gcj go graphite hardened jit libssp mpx mudflap multilib +nls nopie nossp +nptl
    objc objc++ objc-gc +openmp +pch pgo +pie regression-test +sanitize +ssp vanilla +vtv}
    Installed versions: 6.4.0-r1(6.4.0)^s(01:17:40 28-03-2018)(cxx nptl openmp pch pie sanitize ssp vtv -altivec -awt -cilk -debug -doc -fixed-point -fortran -gcj -go -graphite -hardened -jit -libssp -mpx -multilib -nls -objc -objc++ -objc-gc -pgo -regression-test -vanilla)
    Homepage: https://gcc.gnu.org/
    Description: The GNU Compiler Collection

    ----- gcc ends -----

    only 6.4.0 here on gentoo is stable

    i dont know why older kernels stopped building firmware when 4.16 works for me,
    good its solved

    sadly cant build firmware anymore in the kernel, seems it needs
    to be external build now

    Just as well since there were some of the firmware I needed with the external source that wasn't provided with the regular source anyhow. This way most, if indeed not all, firmware can be found in the
    external source. In my particular situation I can find all that I require in the external source which I needed before so it's not
    really a big deal.

    yep, building external firmware is not easy on gentoo, it need to clena userland firmware files, and disable in kernel firmware, then build in userland
    firmware and hope it works on new kernels :)

    have it build in kernel makes sure its tested and works with the kernel version


    Regards Benny

    ... there can only be one way of life, and it works :)

    --- Msged/LNX 6.2.0 (Linux/4.16.0-gentoo (i686))
    * Origin: I will always keep a PC running CPM 3.0 (2:230/0)
  • From Maurice Kinal@1:153/7001 to Benny Pedersen on Fri Apr 6 10:47:10 2018
    Hey Benny!

    only 6.4.0 here on gentoo is stable

    I haven't used that version in awhile. My best guess is that it is perfectly fine.

    i dont know why older kernels stopped building firmware

    There is little need to rebuild firmware unless of course you are adding new hardware that requires newer firmware. If that is the case then the older kernel's in-tree firmware is unlikely to resolve that issue. All of the firmware I currently require is supplied by linux-firmware.git instead so it is
    of no consequence that it is no longer supplied by the newer kernels especially
    considering none of it was ever used in my particular situation. Exactly what firmware did you need to build with every kernel upgrade? I bet very little, if any, has changed as far as firmware is concerned especially regarding an i686 based system.

    have it build in kernel makes sure its tested and works with the
    kernel version

    For example? The newest update here was on Nov. 26, 2017 (htc_9271-1.4.0.fw) and was never supplied by the in-tree kernel's firmware. It was always maintained by linux-firmware.git. So far I've never needed to obtain firmware from any other source ... thank goodness.

    Life is good,
    Maurice

    ... Don't cry for me I have vi.
    --- GNU bash, version 4.4.19(1)-release (x86_64-silvermont-linux-gnu)
    * Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001)