1. Forum
  2. Usenet
  3. LINUX.GENTOO.USER

  • [gentoo-user] kernel 5.15+ (thru 5.16.5)

    From Alan Grimes@21:1/5 to All on Thu Feb 3 03:10:01 2022
    Do any of the kernels post 5.15.0 boot? I tried 5.15.2 and imediately
    wrote off the 5.15 branch because it didn't even boot.

    I came back to 5.16.5, same symptom, says "loading linux 5.16.5" and
    then hangs, no further kernel output.

    5.14.20 works great with same config, no known issues.

    Now it's possible that something fantasmagorically stupid is going on
    here, as is usual, but for the love of god WHY, just WHY?!?!??!

    --
    Beware of Zombies. =O
    #EggCrisis #BlackWinter
    White is the new Kulak.
    Powers are not rights.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Neil Bothwick@21:1/5 to Alan Grimes on Thu Feb 3 09:10:01 2022
    On Wed, 2 Feb 2022 21:02:46 -0500, Alan Grimes wrote:

    Do any of the kernels post 5.15.0 boot? I tried 5.15.2 and imediately
    wrote off the 5.15 branch because it didn't even boot.

    I came back to 5.16.5, same symptom, says "loading linux 5.16.5" and
    then hangs, no further kernel output.

    5.14.20 works great with same config, no known issues.

    Now it's possible that something fantasmagorically stupid is going on
    here, as is usual, but for the love of god WHY, just WHY?!?!??!

    I have the same with one machine, see the thread "Kernel 5.15.11 won't
    boot". Nothing there helped me, and I haven't had time to investigate
    further, but there may be something for you.


    --
    Neil Bothwick

    Windows Error #56: Operator fell asleep while waiting.

    -----BEGIN PGP SIGNATURE-----

    iQIzBAEBCAAdFiEE8k9T/rX16EJxEKG692eFu0QSMJgFAmH7jHgACgkQ92eFu0QS MJjatw//efLt7oLTuqqCtQVprtGVwhb1kF6ZrODTIMpmYOrQkZlm8ev9gXTww/gm Ze3m2lO9ddHbm926LmSO6CUcY7y6xu3fwQQjjDA0gkVSz9eeVOrqxRufROTUvLRq 707m9sdHeBG3lnUG9QAKT5GgJhkHtidtBQXWgcnhREO+dBcRJaA8vPe610RK24zm Sc6VjK9oqlNbqC8eMc0pMJjYEJ6YT8rdx5eFUp8BCkD3BGiVEPDB5hPz363CEy/L jri8vRzpVYHKre8X8lgXRfM5T0HY7ApUAV4WJQv3ae8UeizXyLAEm4o7y7chzZHu xEILF+yEdlXyGDO/3aGH9Sf15D8LiIO0+TiSqIz7OHWl7RK6uvn27XrI52JCMlpX OiJpKVveq9C11JEu/I4AP/Hful0W6j2T9JKdqPjap5sv3MwGK8NXl0KGarciK2Hm WAFl2i/Rtx9LcfpF0UM4k1LC23/dA1KmkSxwb4TnLSjWsJ2OhOUxUe0VdOVs5P4i hoTOfGGsKdgurz2N/fP0UFu2ugAx6EV8WCBAuQ5CnhJqVBlbwd0yn7f/7ZW8L+Z+ 40tvNE2t57f4xkeJGqWYccwBNNwXa+OQgeswWJ802vcL/WSOd76SaSgLE5ZgB42R nIAcQ5BvJhvkyKlcWE7kgxu8H/q+zKzR4ZClRDOD9QcZA68SdOA=
    =+wpk
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Michael@21:1/5 to All on Thu Feb 3 08:17:06 2022
    On Thursday, 3 February 2022 08:04:07 GMT Neil Bothwick wrote:
    On Wed, 2 Feb 2022 21:02:46 -0500, Alan Grimes wrote:
    Do any of the kernels post 5.15.0 boot? I tried 5.15.2 and imediately
    wrote off the 5.15 branch because it didn't even boot.

    I came back to 5.16.5, same symptom, says "loading linux 5.16.5" and
    then hangs, no further kernel output.

    5.14.20 works great with same config, no known issues.

    Now it's possible that something fantasmagorically stupid is going on
    here, as is usual, but for the love of god WHY, just WHY?!?!??!

    I have the same with one machine, see the thread "Kernel 5.15.11 won't
    boot". Nothing there helped me, and I haven't had time to investigate further, but there may be something for you.

    I recall reading some foobar with "simple framebuffer" cropping up and also I found this bug in case it helps with either of your machines:

    https://bugs.gentoo.org/821406
    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCAAdFiEEXqhvaVh2ERicA8Ceseqq9sKVZxkFAmH7j4IACgkQseqq9sKV Zxm3Bw//RUbxg2ky2ez2bX9iO93huW3eUMpBegUGl+jg8+qBuGM9bLnHjG4HYYBV ieMKY11jPOpi2V5W1/dkRswamVJ6/fY9Ng86P7vzpQjBb84uaQEAkWI8EgE9v3// 0ReD+wSAiC4XmRpeO5yop20l2VVIjeK6mxhrYPtOaxpGip9hwwfcg66gbSSJ9Stg xcRvBFRfYCOL6g2qBb/39c+F9AfQvCVgFglz0p6DuZR5vYwm1AhOvRl7GVC73N+g xc66n1i3NyGEnqBTPozC9FRxbB7Vyp0HO4/ngCfV3TCe5n9zOgQbGHKGOctf+nCW MSKs45Sg/d0P7pybo6FiyLbGQKQllefsPCJUpJRLxciKtzug7qWaQtMIiscNF5lV JwQc19WItX3Bruq3W5398bwqo93pPO99XO+D4jpU3ppOlacB9aiBM3xYhNqhd5af yilEcd/Pdx8FLXnTJ8AtMJ+iJZ2agSxUYNDMN/uKc+3EqZid+q5epNfPfLUewp/F zqBNyN4Z5td9pNK2qXovQKcK4b2E8XZ5vseDVK8JPJn0ARy8B8CO8H/Y97kmwo8+ WSU+3uTjf7YJLBGAvE1bBfy/ocbyjCxKb6WURmaTZhGzEfS3ppWR91+iTOv6FzOL bT+pxI/zPyGGDpqOFtU6NAcwwqeoA+4MFGpHbrtfq3JPEaU4ZkE=
    =vZxO
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Adam Carter@21:1/5 to All on Thu Feb 3 10:40:02 2022

    I recall reading some foobar with "simple framebuffer" cropping up and
    also I
    found this bug in case it helps with either of your machines:

    https://bugs.gentoo.org/821406


    That's not the first time CONFIG_MPILEDRIVER=y has caused issues. I just
    stick to CONFIG_MBULLDOZER=y on my FX-8530.

    <div dir="ltr"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
    I recall reading some foobar with &quot;simple framebuffer&quot; cropping up and also I <br>
    found this bug in case it helps with either of your machines:<br>

    <a href="https://bugs.gentoo.org/821406" rel="noreferrer" target="_blank">https://bugs.gentoo.org/821406</a> <br></blockquote><div><br></div><div>That&#39;s not the first time CONFIG_MPILEDRIVER=y has caused issues. I just stick to CONFIG_MBULLDOZER=y on
    my FX-8530.<br><div dir="ltr"><br></div></div></div></div>

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Alan J. Wylie@21:1/5 to Alan Grimes on Thu Feb 3 12:10:01 2022
    Alan Grimes <alonzotg@verizon.net> writes:

    Do any of the kernels post 5.15.0 boot? I tried 5.15.2 and imediately
    wrote off the 5.15 branch because it didn't even boot.

    I came back to 5.16.5, same symptom, says "loading linux 5.16.5" and
    then hangs, no further kernel output.

    5.14.20 works great with same config, no known issues.

    Now it's possible that something fantasmagorically stupid is going on
    here, as is usual, but for the love of god WHY, just WHY?!?!??!

    See the thread on the LKML at https://lore.kernel.org/lkml/d8981e2a-4f61-72bb-e5cc-bf4ded29c08a@synopsys.com/

    Try setting "CONFIG_FB=y"

    I had problems building nvidia-drivers, turning on
    "CONFIG_DRM_CIRRUS_QEMU"
    worked around the problem

    https://lore.kernel.org/lkml/871r3cr08w.fsf@wylie.me.uk/

    --
    Alan J. Wylie https://www.wylie.me.uk/

    Dance like no-one's watching. / Encrypt like everyone is.
    Security is inversely proportional to convenience

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Alan Grimes@21:1/5 to Alan J. Wylie on Thu Feb 3 13:30:01 2022
    Thanks for the link. What I'm reading sounds pretty horrible.

    My hardware is:

    Threadripper 3960x.  (some heat dammage, very difficult to cool the SOB,
    have to check the water levels frequently....), runs OK despite heat
    dammage. (just CPU and mobo are $2,000)

    video:

    Rusty GTX 980Ti

    I did have to muck with the framebuffer settings to get it to boot in
    EFI mode.

    Behavior of 5.14 is to show a row of penguins across the top of the
    screen as the kernel has done for many many years and quickly scroll
    through the kernel boot and all the other error messages that scroll too
    fast for me to care about....


    Alan J. Wylie wrote:
    Alan Grimes <alonzotg@verizon.net> writes:

    Do any of the kernels post 5.15.0 boot? I tried 5.15.2 and imediately
    wrote off the 5.15 branch because it didn't even boot.

    I came back to 5.16.5, same symptom, says "loading linux 5.16.5" and
    then hangs, no further kernel output.

    5.14.20 works great with same config, no known issues.

    Now it's possible that something fantasmagorically stupid is going on
    here, as is usual, but for the love of god WHY, just WHY?!?!??!
    See the thread on the LKML at https://lore.kernel.org/lkml/d8981e2a-4f61-72bb-e5cc-bf4ded29c08a@synopsys.com/

    Try setting "CONFIG_FB=y"

    I had problems building nvidia-drivers, turning on
    "CONFIG_DRM_CIRRUS_QEMU"
    worked around the problem

    https://lore.kernel.org/lkml/871r3cr08w.fsf@wylie.me.uk/

    --
    Beware of Zombies. =O
    #EggCrisis #BlackWinter
    White is the new Kulak.
    Powers are not rights.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Jack@21:1/5 to Michael on Thu Feb 3 16:10:03 2022
    On 2/3/22 03:17, Michael wrote:
    On Thursday, 3 February 2022 08:04:07 GMT Neil Bothwick wrote:
    On Wed, 2 Feb 2022 21:02:46 -0500, Alan Grimes wrote:
    Do any of the kernels post 5.15.0 boot? I tried 5.15.2 and imediately
    wrote off the 5.15 branch because it didn't even boot.

    I came back to 5.16.5, same symptom, says "loading linux 5.16.5" and
    then hangs, no further kernel output.

    5.14.20 works great with same config, no known issues.

    Now it's possible that something fantasmagorically stupid is going on
    here, as is usual, but for the love of god WHY, just WHY?!?!??!
    I have the same with one machine, see the thread "Kernel 5.15.11 won't
    boot". Nothing there helped me, and I haven't had time to investigate
    further, but there may be something for you.
    I recall reading some foobar with "simple framebuffer" cropping up and also I found this bug in case it helps with either of your machines:

    https://bugs.gentoo.org/821406

    I think there are possibly two separate issues going on here, at least
    for me.  I've been booting 5.16.1 and now 5.16.4 with no problems. 
    However, I recently tried booting 5.17-rc1 and rc2 (direct from
    kernel.org, no gentoo package yet) and they both just sat there forever
    after "Loading initial ramdisk."  Going back to 5.16.4, I noticed that
    there was far less logging to console than usual until some video switch happened.  Adding the simple framebuffer got all my logging back.  It
    also got a bunch of logging output with 5.17-rc2, but that still won't
    boot for me - which is something for a different thread.  When the
    system is just sitting there - try to ssh in.  It has probably actually
    booted just fine, it's just not putting anything out to the screen.

    Also, be careful - if you just search the config for "SIMPLE" it finds
    two FB related entries - you need one of them and not the other, but I
    am sitting at the wrong computer to check which.

    Jack

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Peter =?ISO-8859-1?Q?B=F6hm?=@21:1/5 to All on Thu Feb 3 16:50:01 2022
    Am Donnerstag, 3. Februar 2022, 16:08:26 CET schrieb Jack:
    Also, be careful - if you just search the config for "SIMPLE" it finds
    two FB related entries - you need one of them and not the other, but I
    am sitting at the wrong computer to check which.

    For this problem we have some articles in our Gentoo Forum.

    Between 5.10.x and 5.15.x there was a change:

    You dont have a "Simple FB" in your old directory (when doing "make menuconfig"); instead there is a new entry which leads to this in your .config:

    CONFIG_SYSFB_SIMPLEFB=y

    (Searching for "SIMPLE" in your .config gives you only this one + "CONFIG_DRM_SIMPLEDRM=y". If you have the old entry also in your .config, then you have not done "make oldconfig").

    The "new" simpleFB is here:

    Device Drivers --->
    Graphics support --->
    [*] Simple framebuffer driver

    The old one was here:

    Device Drivers --->
    Graphics support --->
    Frame buffer Devices --->
    [*] Support for frame buffer devices --->


    Kind Regards,
    --P

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Neil Bothwick@21:1/5 to Michael on Thu Feb 3 18:10:02 2022
    On Thu, 03 Feb 2022 08:17:06 +0000, Michael wrote:

    I have the same with one machine, see the thread "Kernel 5.15.11 won't boot". Nothing there helped me, and I haven't had time to investigate further, but there may be something for you.

    I recall reading some foobar with "simple framebuffer" cropping up and
    also I found this bug in case it helps with either of your machines:

    https://bugs.gentoo.org/821406

    That's it, thanks!

    I tried the FB settings but didn't expect it to work as the system really wasn't booting, as opposed to booting with do display.

    Setting CONFIG_GENERIC_CPU=y results in a boot. I had been using CONFIG_MNATIVE_AMD.


    --
    Neil Bothwick

    Windows - so intuitive you only need a meg of help files!

    -----BEGIN PGP SIGNATURE-----

    iQIzBAEBCAAdFiEE8k9T/rX16EJxEKG692eFu0QSMJgFAmH8DEIACgkQ92eFu0QS MJixuA/8D+LtOozeH4NVZnh8A0ce/LNQuTy5eefxj/hvFh1AKYaTZnx+mC/FNc5o EUttCqhbW8/wqVUIUwAI34OKTb5m6fGPXXY9zQLiWqwJZGjthjfJdtc3WOeWFJXP ON+CoKwfcQg6RvfSaeVkm20lpA2ozu2DrTXfXzV3OOgy1i58Qo5vv/dRsoKByF0g 1gwONhUaAZ2upVneG1/egnAf4CBSYX1ob6NkyP9yxmLiVeDy6mXmLctQy/Np0ISO JTeymTLZliRCd6xaw+mLzFgJNC54dwiRxlQhwb9404aWQOL9GuyztrD+atKWkn81 Ak6coxGqrKludfjG1Rnd5zWe+dlhDUmiQ1sCR1TW9EWHrH8a8+8NTKfGD1hN7wyu 3CBmMHK+PF7jfKcQY55Txdc3vnqigRf9kTRlAfKje/Bxb6w0Zjh2h3rlW3b3QFEx /sTuqtDzJs9M0Pdm/uwqVu+EnkAQaQPFaCGgEDgpPZr/vPoToXuEiU94ViOUy36I +HciM01mgMjwnFREc8N2woIWsh5GFcW9g6KRQzBlEtGMUCI+xOY10cxahm9zh5aq O8mR4zIDw7Vv0d/srwNiHnb6CQcjtzSCKdWqJ4GeX9C3pPaTzwWTG0q59ex3gO1I 21yKq9EPplGKaTxrS9qFvCCUrA/LHuoe3/OVHxS3zp/O2MbRMGA=
    =SDKj
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Neil Bothwick@21:1/5 to Neil Bothwick on Thu Feb 3 23:50:02 2022
    On Thu, 3 Feb 2022 17:09:22 +0000, Neil Bothwick wrote:

    On Thu, 03 Feb 2022 08:17:06 +0000, Michael wrote:

    I have the same with one machine, see the thread "Kernel 5.15.11
    won't boot". Nothing there helped me, and I haven't had time to investigate further, but there may be something for you.

    I recall reading some foobar with "simple framebuffer" cropping up and
    also I found this bug in case it helps with either of your machines:

    https://bugs.gentoo.org/821406

    That's it, thanks!

    I tried the FB settings but didn't expect it to work as the system
    really wasn't booting, as opposed to booting with do display.

    Setting CONFIG_GENERIC_CPU=y results in a boot. I had been using CONFIG_MNATIVE_AMD.

    CONFIG_MPILEDRIVER=y works too.


    --
    Neil Bothwick

    ASCII stupid question... get a stupid ANSI!

    -----BEGIN PGP SIGNATURE-----

    iQIzBAEBCAAdFiEE8k9T/rX16EJxEKG692eFu0QSMJgFAmH8WmUACgkQ92eFu0QS MJhj/g//UocvCdv+xqL0pr2m+nWx0N2kUBGQkI0rwOc5zbhTKld3WyvGC6v5A7+z PPPAd7/jP/4xmo2FzmtkY7SbM5BAKb66hCDX9sOMwIoKScuwjgnDLt6jZSk8szh8 wrA+lufSN+OIIzy4Oq5l63b1aGyd8WrmhYQJZEG1et5UQGUjM3cT6I8UaV76+OPA l25mQ9HqVzFVPaATF3bwrJ3IBsaJb1IoGWri+jRmJuSv0CzPC+M4uOVcOCZ7Eevo pguSTjR/l6APdGdJ3N6XATdspQeSdOF+rtCqRDMb1qhpt222TdrCzvZwWrkpB2BD ePBU+1W3wQwu7Dwmv1ntZxvmQ1RuoFOn2rvkVBxBnrp1WwNaZTOumTIU3m0jNEEn BpoLiwZtG7qjCouFV7n37LMzSylC/grOxXmK2d85IzeRWRbdAj0WCUMCJqYT1UWl /vJsoNC1zsaXU3LBbBxe/CDaQIqiCYm0jwKfhKsem6R/41AIts616u2XO1wK1AAL c4yF6+HHNfzFa5l3MDoAGg+yWKNm2PURpUqFTdJujRaMQy/p7MzIL00qvc7qYXs9 acdptzu27dUHeFRE4x7rmFmAJ4y32Cg3ea57KkFxoNNFZgM4hx0NuwoNqV5y9NDV 5StiXmGCAmP1S++iNU5K6kx3fM2tVZJj4Fw9vOTAllMFOyGf2zY=
    =2nbj
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Alan Grimes@21:1/5 to All on Fri Feb 4 04:00:01 2022
    Peter Böhm wrote:
    The "new" simpleFB is here:
    Device Drivers --->
    Graphics support --->
    [*] Simple framebuffer driver

    Shockingly enough, that worked.

    I shudder to think why this was allowed out without implementing an
    auto-patch for old configs...

    --
    Beware of Zombies. =O
    #EggCrisis #BlackWinter
    White is the new Kulak.
    Powers are not rights.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)