1 |
On 3/13/22 14:34, Neil Bothwick wrote: |
2 |
> On Sun, 13 Mar 2022 14:04:59 -0600, thelma@×××××××××××.com wrote: |
3 |
> |
4 |
>> On 3/13/22 13:21, thelma@×××××××××××.com wrote: |
5 |
>>> Upgraded to: gentoo-sources-5.10.103 |
6 |
>>> and kernel will not boot, not even recovery mode. |
7 |
>>> |
8 |
>>> I'm getting some strange looping/scrolling message on the screen: |
9 |
>>> |
10 |
>>> Kscan: watching read 1 fsk983s.... |
11 |
>>> |
12 |
>>> I followed standard procedure: |
13 |
>>> |
14 |
>>> emerge -avq =sys-kernel/gentoo-sources-5.10.103 |
15 |
>>> cd /usr/src/ |
16 |
>>> eselect kernel set 3 (this is: linux -> linux-5.10.103-gentoo) |
17 |
>>> cd linux |
18 |
>>> cp ../linux-old_kernel/.config . |
19 |
>>> mount /boot/ |
20 |
>>> |
21 |
>>> make oldconfig |
22 |
>>> make |
23 |
>>> make modules_prepare |
24 |
>>> make modules_install |
25 |
>>> make install |
26 |
>>> |
27 |
>>> grub-mkconfig -o /boot/grub/grub.cfg |
28 |
>>> reboot |
29 |
>>> |
30 |
>>> ( did the same on my other boxes and this kernel is booting OK on |
31 |
>>> other installations) |
32 |
>> |
33 |
>> Solved. |
34 |
> |
35 |
> Please post the solution. Otherwise anyone with a similar problem |
36 |
> searching for an answer will find only the question and a tease that it |
37 |
> can be fixed but not telling how. |
38 |
|
39 |
Simple human error :-/ |
40 |
|
41 |
When I did: |
42 |
cd linux |
43 |
cp ../linux-old_kernel/.config . |
44 |
mount /boot/ |
45 |
make oldconfig |
46 |
|
47 |
New entries showed up. Instead of pressing "enter" I made a mistake and press "Y" several times. |
48 |
This enabled some feature in the new kernel that shouldn't be there; example: "CONFIG_KCSAN = y" |
49 |
|
50 |
Redoing the process just by hitting "enter" soled the problem; new kernel boot as it should. |