Mailing List Archive

On 10/7/23 12:13, Valmor F. de Almeida wrote:
>
> On 10/7/23 08:09, Peter Böhm wrote:
>> Am Samstag, 7. Oktober 2023, 08:28:01 CEST schrieb Valmor de Almeida:
>>

[snip]


>> For me the following questions would arise:
>>
>> a) How did you install the kernel 6.1.41 ? (genkernel; dist-kernel;
>> manual
>> approach)

Sorry I described the install for the 6.1.53-gentoo-r1 kernel. The
install for 6.1.41 was similar but I used the config file from the
earlier kernel which is 6.1.38 to start make oldconfig.

--
Valmor

>
> manual:
> 1) portage sync
> 2) make oldconfig in the new kernel directory for linux-6.1.53-gentoo-r1
>
> • Mitigations for speculative execution vulnerabilities
> *
> Mitigations for speculative execution vulnerabilities
> (SPECULATION_MITIGATIONS) [Y/n/?] y
>   Remove the kernel mapping in user mode (PAGE_TABLE_ISOLATION) [Y/n/?] y
>   Avoid speculative indirect branches in kernel (RETPOLINE) [Y/n/?] y
>     Enable return-thunks (RETHUNK) [Y/n/?] y
>       Enable UNRET on kernel entry (CPU_UNRET_ENTRY) [Y/n/?] y
>   Enable IBPB on kernel entry (CPU_IBPB_ENTRY) [Y/n/?] y
>   Enable IBRS on kernel entry (CPU_IBRS_ENTRY) [Y/n/?] y
>
> Up to here default is picked automatically; I don't have a choice.
> Next, I have tried with and without accepting the NEW features.
>
>   Mitigate speculative RAS overflow on AMD (CPU_SRSO) [Y/n/?] (NEW)
>   Mitigate Straight-Line-Speculation (SLS) [N/y/?] n
>   Force GDS Mitigation (GDS_FORCE_MITIGATION) [N/y/?] (NEW)
>
> 3) make menuconfig
> 4) make && make modules_install
> 5) make install
> 6) grub-mkconfig -o /boot/grub/grub.cfg
> 7) reboot
>
>> b) Did you make any kernel configuration changes in your 6.1.41 ?
> no; I use what is in /boot
>
> ->  ls /boot/
> config-6.1.41-gentoo     grub/        System.map-6.1.41-gentoo
> vmlinuz-6.1.41-gentoo
> config-6.1.53-gentoo-r1  lost+found/  System.map-6.1.53-gentoo-r1
> vmlinuz-6.1.53-gentoo-r1
>
>> c) Do you use a bootmanager ? (which ?; grub, refind ?)
>
> I use grub-2
>
> *  sys-boot/grub
>       Latest version available: 2.06-r9
>       Latest version installed: 2.06-r9
>
>
>> d) How did you update to 6.1.53 ? (every step)
>
> -> revdep-rebuild --ignore
> -> emerge --depclean
> -> eclean distfiles
> -> eclean packages
> -> emerge @preserved-rebuild
> -> emerge --sync
> -> etc-update
> -> env-update
> (run a script to source profile)
> -> emerge -vp --update --newuse --deep --tree --with-bdeps=y @world
> check conflicts etc., fetch files, then run without -vp
>
>>
>> To better understand your system, I would look at the output of
>> "parted -l" (complete),
>> "dmesg" (complete),
>> "lspci -k" and
>> "emerge --info"
>> (after you have booted 6.1.41).
>>
>> To clarify all this here via the mailing list might be difficult;
>> therefore I
>> would suggest to create a thread in our Gentoo support forum:
>
> I will give it shot.
>
>>
>> https://forums.gentoo.org/
>>
>> (I am there also; but we have also a lot of great experts there)
>>
>> If you create a thread in our forum, then please use wgetpaste for big
>> files:
>> https://wiki.gentoo.org/wiki/Wgetpaste
>>
>> Greetings,
>> Peter
>>
>
> Thanks,
> --
> Valmor

On Sat, Oct 7, 2023 at 9:18?AM Dale <rdalek1967@gmail.com> wrote:
<SNIP>
>
> My first kernel, emerge prechecks warned that it wasn't and might or
might not work. So, I went back to a version that it claims is supported.
I have to say tho, the nvidia site wasn't very helpful. The messages when
emerging nvidia-drivers was a lot more help. That said, it does load the
drivers. They are listed with lsmod. Given the kernel is on my main rig,
it's harder to test since I don't reboot often. At some point, I may start
a thread about it if a update or something doesn't fix it. After all,
current kernel is working just fine.
>
> I just thought it worthwhile to follow this problem since it might help
or give clues on things to look into. Might be related, might not.
>
Hi Dale,

So assuming I understand your situation, you built nvidia-drivers to work
with
6.1.55 - but got no GUI. The build told you it might not work and it didn't.

You went back to an earlier kernel and it does work.

I don't think you shared what NVidia card is in this machine, and
I don't think you shared what version of NVidia drivers worked
with the old kernel and what version didn't work with the new kernel?

- Mark

Mark Knecht wrote:
>
>
> On Sat, Oct 7, 2023 at 9:18?AM Dale <rdalek1967@gmail.com
> <mailto:rdalek1967@gmail.com>> wrote:
> <SNIP>
> >
> > My first kernel, emerge prechecks warned that it wasn't and might or
> might not work.  So, I went back to a version that it claims is
> supported.  I have to say tho, the nvidia site wasn't very helpful. 
> The messages when emerging nvidia-drivers was a lot more help.  That
> said, it does load the drivers.  They are listed with lsmod.  Given
> the kernel is on my main rig, it's harder to test since I don't reboot
> often.  At some point, I may start a thread about it if a update or
> something doesn't fix it.  After all, current kernel is working just
> fine.
> >
> > I just thought it worthwhile to follow this problem since it might
> help or give clues on things to look into.  Might be related, might not.
> >
> Hi Dale,
>
> So assuming I understand your situation, you built nvidia-drivers to
> work with 
> 6.1.55 - but got no GUI. The build told you it might not work and it
> didn't.
>
> You went back to an earlier kernel and it does work.
>
> I don't think you shared what NVidia card is in this machine, and
> I don't think you shared what version of NVidia drivers worked
> with the old kernel and what version didn't work with the new kernel?
>
> - Mark


Actually, I went to the latest version in the tree, 6.5, and got the
message it likely won't work.  I went back to a version the message said
should work, 6.1.  It still doesn't work.  It may be the driver, it may
not be.  I could have left something new out in the kernel that it needs
but I didn't know it.  It could be any number of things.  At some point
when I got time to mess with it, I'm going to boot into the kernel that
doesn't work and save the log files, sddm, Xorg etc.  Then maybe it will
have a clue as to the problem. 

Until then I just want to sort of follow this to see if it might help
with my problem.  If not, oh well. 

Dale

:-)  :-) 

P. S.  My pack of drives arrived early.  Running SMART test on them
now.  :-D

On Sat, 7 Oct 2023 13:55:05 -0500, Dale wrote:

> Actually, I went to the latest version in the tree, 6.5, and got the
> message it likely won't work.  I went back to a version the message said
> should work, 6.1.  It still doesn't work.  It may be the driver, it may
> not be. 

What does /var/log/Xorg.0.log tell you?


--
Neil Bothwick

What do you have when you have six lawyers buried up to their necks in
sand? Not enough sand.

On Sat, 7 Oct 2023 12:13:58 -0400, Valmor F. de Almeida wrote:

> 2) make oldconfig in the new kernel directory for linux-6.1.53-gentoo-r1
>
> • Mitigations for speculative execution vulnerabilities
> *
> Mitigations for speculative execution vulnerabilities
> (SPECULATION_MITIGATIONS) [Y/n/?] y
> Remove the kernel mapping in user mode (PAGE_TABLE_ISOLATION)
> [Y/n/?] y Avoid speculative indirect branches in kernel (RETPOLINE)
> [Y/n/?] y Enable return-thunks (RETHUNK) [Y/n/?] y
> Enable UNRET on kernel entry (CPU_UNRET_ENTRY) [Y/n/?] y
> Enable IBPB on kernel entry (CPU_IBPB_ENTRY) [Y/n/?] y
> Enable IBRS on kernel entry (CPU_IBRS_ENTRY) [Y/n/?] y
>
> Up to here default is picked automatically; I don't have a choice.

Those are settings you already have in your existing confid, shown to
give context to the following NEW settings.

You can change them, but with make config, not oldconfig.


--
Neil Bothwick

Love is grand. Divorce is a few grand more.

Neil Bothwick wrote:
> On Sat, 7 Oct 2023 13:55:05 -0500, Dale wrote:
>
>> Actually, I went to the latest version in the tree, 6.5, and got the
>> message it likely won't work.  I went back to a version the message said
>> should work, 6.1.  It still doesn't work.  It may be the driver, it may
>> not be. 
> What does /var/log/Xorg.0.log tell you?
>
>


I was in a hurry so I didn't look.  When I got time, I'll reboot and
save the logs so I can see them and look for clues or if I can't see
anything, post to see if someone else does. 

It could be that my particular card has a issue with that driver version
and kernel version.  Maybe a update later will fix that.  I dunno.  I
just went back to my older kernel and got my system up and running
again.  I got quite a bit going on at the moment so it may be a while
before I get back around to it.  I been trying to update to a newer
kernel for over a year now.  o_O  Always something. 

Dale

:-)  :-)