Re: [gentoo-user] 6.1.53-gentoo-r1 kernel not booting

2023-10-01 Thread Lee
I found this:

https://www.reddit.com/r/Gentoo/comments/168qrbx/gentoosources_6146_kernel_reports_io_error/


Lee 

On Sun, Oct 1, 2023, 7:56 PM Håkon Alstadheim 
wrote:

>
> Den 01.10.2023 21:31, skrev Frank Steinmetzger:
> > Am Sat, Sep 30, 2023 at 11:25:46PM +0200 schrieb Håkon Alstadheim:
> >> Den 30.09.2023 22:57, skrev Valmor F. de Almeida:
> >>> Hello,
> >>>
> >>> For a while now (3 weeks or so) I have been upgrading the linux kernel
> >>> on a Dell XPS laptop starting from 6.1.41-gentoo (which is my current
> >>> working kernel) to 6.1.53-gentoo-r1. No kernel I have built since is
> >>> able to boot. I have been following the same method for many years:
> make
> >>> oldconfig, etc...
> >>>
> >>> The booting error starts at:
> >>>
> >>> [snip]
> >>>
> >>> * INIT: Entering runlevel: 3
> >>> [snip]
> >>> * Starting cronie ...
> >>> * Starting DHCP Client Daemon ...
> >>> * Starting laptop_mode ...
> >>> * Mounting network filesystems ...
> >>> /etc/init.d/netmount: line 45 /lib/rc/bin/ewend: Input/output error
> >>> /lib/rc/sh/rc-cgroup.sh: line 184: rmdir: command not found
> >>> INIT:
> >>> INIT: cannot execute "/sbin/agetty"
> >>> INIT: cannot execute "/sbin/agetty"
> >>> INIT: cannot execute "/sbin/agetty"
> >>>
> >>>
> >> Can you show /etc/fstab and the console-log for the entire boot? Seems
> /sbin
> >> is not readable. You sure you have the kernel modules loaded? Are you
> using
> >> an initramfs? If so, does that build without errors ?
> > The input/output error – to me – indicates a hardware problem. When you
> > mounted the FS by hand, can you read ewend? For instance with md5sum.
> >
> except it boots ok with older kernels. When you've eliminated the
> impossible, whatever remains, however improbable has to be a kernel
> config change (missing or erroneous and unintended) , or
> initramfs failing to build/install correctly. Check error output from
> your kernel build.
>
>


Re: [gentoo-user] 6.1.53-gentoo-r1 kernel not booting

2023-10-01 Thread Lee K
On Mon, Oct 02, 2023 at 02:29:05AM +0200, Håkon Alstadheim wrote:
> 
> Den 01.10.2023 21:31, skrev Frank Steinmetzger:
> > Am Sat, Sep 30, 2023 at 11:25:46PM +0200 schrieb Håkon Alstadheim:
> >> Den 30.09.2023 22:57, skrev Valmor F. de Almeida:
> >>> Hello,
> >>>
> >>> For a while now (3 weeks or so) I have been upgrading the linux kernel
> >>> on a Dell XPS laptop starting from 6.1.41-gentoo (which is my current
> >>> working kernel) to 6.1.53-gentoo-r1. No kernel I have built since is
> >>> able to boot. I have been following the same method for many years: make
> >>> oldconfig, etc...
> >>>
> >>> The booting error starts at:
> >>>
> >>> [snip]
> >>>
> >>> * INIT: Entering runlevel: 3
> >>> [snip]
> >>> * Starting cronie ...
> >>> * Starting DHCP Client Daemon ...
> >>> * Starting laptop_mode ...
> >>> * Mounting network filesystems ...
> >>> /etc/init.d/netmount: line 45 /lib/rc/bin/ewend: Input/output error
> >>> /lib/rc/sh/rc-cgroup.sh: line 184: rmdir: command not found
> >>> INIT:
> >>> INIT: cannot execute "/sbin/agetty"
> >>> INIT: cannot execute "/sbin/agetty"
> >>> INIT: cannot execute "/sbin/agetty"
> >>>
> >>>
> >> Can you show /etc/fstab and the console-log for the entire boot? Seems 
> >> /sbin
> >> is not readable. You sure you have the kernel modules loaded? Are you using
> >> an initramfs? If so, does that build without errors ?
> > The input/output error – to me – indicates a hardware problem. When you
> > mounted the FS by hand, can you read ewend? For instance with md5sum.
> >
> except it boots ok with older kernels. When you've eliminated the 
> impossible, whatever remains, however improbable has to be a kernel 
> config change (missing or erroneous and unintended) , or 
> initramfs failing to build/install correctly. Check error output from 
> your kernel build.
> 

I found this: 

https://www.reddit.com/r/Gentoo/comments/168qrbx/gentoosources_6146_kernel_reports_io_error/

-- 
Lee



Re: [gentoo-user] 6.1.53-gentoo-r1 kernel not booting

2023-10-01 Thread Håkon Alstadheim



Den 01.10.2023 21:31, skrev Frank Steinmetzger:

Am Sat, Sep 30, 2023 at 11:25:46PM +0200 schrieb Håkon Alstadheim:

Den 30.09.2023 22:57, skrev Valmor F. de Almeida:

Hello,

For a while now (3 weeks or so) I have been upgrading the linux kernel
on a Dell XPS laptop starting from 6.1.41-gentoo (which is my current
working kernel) to 6.1.53-gentoo-r1. No kernel I have built since is
able to boot. I have been following the same method for many years: make
oldconfig, etc...

The booting error starts at:

[snip]

* INIT: Entering runlevel: 3
[snip]
* Starting cronie ...
* Starting DHCP Client Daemon ...
* Starting laptop_mode ...
* Mounting network filesystems ...
/etc/init.d/netmount: line 45 /lib/rc/bin/ewend: Input/output error
/lib/rc/sh/rc-cgroup.sh: line 184: rmdir: command not found
INIT:
INIT: cannot execute "/sbin/agetty"
INIT: cannot execute "/sbin/agetty"
INIT: cannot execute "/sbin/agetty"



Can you show /etc/fstab and the console-log for the entire boot? Seems /sbin
is not readable. You sure you have the kernel modules loaded? Are you using
an initramfs? If so, does that build without errors ?

The input/output error – to me – indicates a hardware problem. When you
mounted the FS by hand, can you read ewend? For instance with md5sum.

except it boots ok with older kernels. When you've eliminated the 
impossible, whatever remains, however improbable has to be a kernel 
config change (missing or erroneous and unintended) , or 
initramfs failing to build/install correctly. Check error output from 
your kernel build.




Re: [gentoo-user] Switching from desktop to desktop without function keys.

2023-10-01 Thread Dale
Frank Steinmetzger wrote:
> Am Sat, Sep 30, 2023 at 10:47:31PM +0100 schrieb Peter Humphrey:
>> On Saturday, 30 September 2023 20:59:04 BST Dale wrote:
>>
>>> Is there a way with the keyboard to switch to a desktop above 10?  Even
>>> if it just switches up one at a time, that would work.  Say switch to 10
>>> and then keep hitting a set of keys to go to 11, then 12, then 13 etc
>>> etc.  Eventually, I get to the one I want. 
>> You can set up a key combination to switch one desktop to the right and 
>> another to switch one to the left. It's under Shortcuts, where you select 
>> KWin, then scroll the right-hand panel down to Walk through Desktop List, 
>> where I've put what used to be the default value: CTRL-ALT-right. Then down 
>> one to the next entry and enter CTRL-ALT-left. The defaults are left blank 
>> nowadays.
> Also note that a good while ago Plasma switched from using the Alt key to 
> the Super key for everything Window-managerial. So these days, if you create 
> a new user from scratch, it’s Ctrl+Super instead of Ctrl+Alt.
>


Looking at my keyboard, I have a key that looks like a Microsoft thing. 
It looks like a window that is moving and I think is sometimes called a
Microsoft key and might be called the meta key in Linux.  I have that
key on both sides of my keyboard space bar.  I have another key only on
the right side between the Ctrl and the flying window key that looks
like a document with a mouse pointer on it.  What are these keys called
nowadays?  Is one of those the super key you mention?  What is that key
with the mouse pointer on it called?  I don't recall ever using that key
for anything.  Don't know if it does anything either but it might. 

Thanks.

Dale

:-)  :-) 





Re: [gentoo-user] 6.1.53-gentoo-r1 kernel not booting

2023-10-01 Thread Frank Steinmetzger
Am Sat, Sep 30, 2023 at 11:25:46PM +0200 schrieb Håkon Alstadheim:
> 
> Den 30.09.2023 22:57, skrev Valmor F. de Almeida:
> > 
> > Hello,
> > 
> > For a while now (3 weeks or so) I have been upgrading the linux kernel
> > on a Dell XPS laptop starting from 6.1.41-gentoo (which is my current
> > working kernel) to 6.1.53-gentoo-r1. No kernel I have built since is
> > able to boot. I have been following the same method for many years: make
> > oldconfig, etc...
> > 
> > The booting error starts at:
> > 
> > [snip]
> > 
> > * INIT: Entering runlevel: 3
> > [snip]
> > * Starting cronie ...
> > * Starting DHCP Client Daemon ...
> > * Starting laptop_mode ...
> > * Mounting network filesystems ...
> > /etc/init.d/netmount: line 45 /lib/rc/bin/ewend: Input/output error
> > /lib/rc/sh/rc-cgroup.sh: line 184: rmdir: command not found
> > INIT:
> > INIT: cannot execute "/sbin/agetty"
> > INIT: cannot execute "/sbin/agetty"
> > INIT: cannot execute "/sbin/agetty"
> > 
> > 
> Can you show /etc/fstab and the console-log for the entire boot? Seems /sbin
> is not readable. You sure you have the kernel modules loaded? Are you using
> an initramfs? If so, does that build without errors ?

The input/output error – to me – indicates a hardware problem. When you 
mounted the FS by hand, can you read ewend? For instance with md5sum.

-- 
Grüße | Greetings | Salut | Qapla’
Please do not share anything from, with or about me on any social network.

“If wishes were horses we’d all be eating steak.” – Jayne, Firefly


signature.asc
Description: PGP signature


Re: [gentoo-user] Switching from desktop to desktop without function keys.

2023-10-01 Thread Frank Steinmetzger
Am Sat, Sep 30, 2023 at 10:47:31PM +0100 schrieb Peter Humphrey:
> On Saturday, 30 September 2023 20:59:04 BST Dale wrote:
> 
> > Is there a way with the keyboard to switch to a desktop above 10?  Even
> > if it just switches up one at a time, that would work.  Say switch to 10
> > and then keep hitting a set of keys to go to 11, then 12, then 13 etc
> > etc.  Eventually, I get to the one I want. 
> 
> You can set up a key combination to switch one desktop to the right and 
> another to switch one to the left. It's under Shortcuts, where you select 
> KWin, then scroll the right-hand panel down to Walk through Desktop List, 
> where I've put what used to be the default value: CTRL-ALT-right. Then down 
> one to the next entry and enter CTRL-ALT-left. The defaults are left blank 
> nowadays.

Also note that a good while ago Plasma switched from using the Alt key to 
the Super key for everything Window-managerial. So these days, if you create 
a new user from scratch, it’s Ctrl+Super instead of Ctrl+Alt.

-- 
Grüße | Greetings | Salut | Qapla’
Please do not share anything from, with or about me on any social network.

Detours widen your local knowledge.


signature.asc
Description: PGP signature


Re: [gentoo-user] 6.1.53-gentoo-r1 kernel not booting

2023-10-01 Thread Valmor F. de Almeida

On 10/1/23 07:29, Michael wrote:

On Sunday, 1 October 2023 05:56:02 BST Valmor F. de Almeida wrote:

On 9/30/23 17:25, Håkon Alstadheim wrote:

Den 30.09.2023 22:57, skrev Valmor F. de Almeida:

Hello,

For a while now (3 weeks or so) I have been upgrading the linux kernel
on a Dell XPS laptop starting from 6.1.41-gentoo (which is my current
working kernel) to 6.1.53-gentoo-r1. No kernel I have built since is
able to boot. I have been following the same method for many years:
make oldconfig, etc...

The booting error starts at:

[snip]

* INIT: Entering runlevel: 3
[snip]
* Starting cronie ...
* Starting DHCP Client Daemon ...
* Starting laptop_mode ...
* Mounting network filesystems ...
/etc/init.d/netmount: line 45 /lib/rc/bin/ewend: Input/output error
/lib/rc/sh/rc-cgroup.sh: line 184: rmdir: command not found
INIT:
INIT: cannot execute "/sbin/agetty"
INIT: cannot execute "/sbin/agetty"
INIT: cannot execute "/sbin/agetty"


Can you show /etc/fstab and the console-log for the entire boot? Seems
/sbin is not readable. You sure you have the kernel modules loaded? Are
you using an initramfs? If so, does that build without errors ?


Here is fstab:

/dev/nvme0n1p2  /boot   ext2defaults0 2
/dev/nvme0n1p3  noneswapsw  0 0
/dev/nvme0n1p4  /   ext4noatime,discard
 0 1
/dev/cdrom  /mnt/cdrom  autonoauto,user 0 0

I have not changed anything from 6.1.41-gentoo (which compiles and
boots) except updating the config file for compiling the new kernel.
Then I do: make && modules_install. Which runs without errors. After
that: grub-mkconfig -o /boot/grub/grub.cfg.
I am not using initramfs.

I don't know how to save the boot messages; it seems that if I turn on
the logger in openrc, it will log the openrc messages but not sysinit
runlevels?

Thanks,
--
Valmor


I think the error messages you're getting indicate inability to access your
rootfs.  Have you perhaps changed the fs drivers in the latest kernels, from
built in to modules?

Have you diff'ed your 6.1.41-gentoo .config file against the latest kernels'
.config files to see what might have changed/missing?

You can set up a netconsole to check boot time messages:

https://www.kernel.org/doc/Documentation/networking/netconsole.txt
https://wiki.ubuntu.com/Kernel/Netconsole

In summary, build netconsole in the new kernel, or as a module, change GRUB's
default CMDLINE from "quiet splash" to "debug" and add netconsole in the
kernel command line:

netconsole=@/,[PORT]@[DEST_IP]

Then at the destination PC launch netcat/socat/telnet; e.g.

nc -u -l -p [PORT]

and reboot the PC you want to debug with the latest kernel, while watching the
output on the destination PC's terminal with nc.


Here is the diff for the config files:

->  diff config /boot/config-6.1.41-gentoo
3c3
< # Linux/x86 6.1.53-gentoo-r1 Kernel Configuration
---
> # Linux/x86 6.1.41-gentoo Kernel Configuration
5c5
< CONFIG_CC_VERSION_TEXT="gcc (Gentoo 13.2.1_p20230826 p7) 13.2.1 20230826"
---
> CONFIG_CC_VERSION_TEXT="gcc (Gentoo 12.3.1_p20230526 p2) 12.3.1 20230526"
7c7
< CONFIG_GCC_VERSION=130201
---
> CONFIG_GCC_VERSION=120301
455d454
< CONFIG_CPU_SRSO=y
457d455
< # CONFIG_GDS_FORCE_MITIGATION is not set
646d643
< CONFIG_ARCH_HAS_CPU_FINALIZE_INIT=y
3136d3132
< CONFIG_VIDEO_V4L2_SUBDEV_API=y
3139,3140d3134
< CONFIG_V4L2_FWNODE=m
< CONFIG_V4L2_ASYNC=m
3236c3230,3233
< CONFIG_VIDEO_CAMERA_SENSOR=y
---
>
> #
> # Camera sensor devices
> #
3295a3293
> # end of Camera sensor devices

I guess I could explore some of this difference.
I have not changed the way I compile the kernel and I typically try to 
have everything built in (only a few modules).

Thanks for the netconsole info.
--
Valmor



Re: [gentoo-user] 6.1.53-gentoo-r1 kernel not booting

2023-10-01 Thread Håkon Alstadheim



Den 01.10.2023 06:56, skrev Valmor F. de Almeida:

On 9/30/23 17:25, Håkon Alstadheim wrote:


Den 30.09.2023 22:57, skrev Valmor F. de Almeida:


Hello,

For a while now (3 weeks or so) I have been upgrading the linux 
kernel on a Dell XPS laptop starting from 6.1.41-gentoo (which is my 
current working kernel) to 6.1.53-gentoo-r1. No kernel I have built 
since is able to boot. I have been following the same method for 
many years: make oldconfig, etc...


The booting error starts at:

[snip]

* INIT: Entering runlevel: 3
[snip]
* Starting cronie ...
* Starting DHCP Client Daemon ...
* Starting laptop_mode ...
* Mounting network filesystems ...
/etc/init.d/netmount: line 45 /lib/rc/bin/ewend: Input/output error
/lib/rc/sh/rc-cgroup.sh: line 184: rmdir: command not found
INIT:
INIT: cannot execute "/sbin/agetty"
INIT: cannot execute "/sbin/agetty"
INIT: cannot execute "/sbin/agetty"


Can you show /etc/fstab and the console-log for the entire boot? 
Seems /sbin is not readable. You sure you have the kernel modules 
loaded? Are you using an initramfs? If so, does that build without 
errors ?



Here is fstab:

/dev/nvme0n1p2  /boot   ext2 defaults    0 2
/dev/nvme0n1p3  none    swap sw  0 0
/dev/nvme0n1p4  /   ext4 noatime,discard    0 1
/dev/cdrom  /mnt/cdrom  auto noauto,user 0 0

I have not changed anything from 6.1.41-gentoo (which compiles and 
boots) except updating the config file for compiling the new kernel. 
Then I do: make && modules_install. Which runs without errors. After 
that: grub-mkconfig -o /boot/grub/grub.cfg.

I am not using initramfs.

I can't see anything fishy in fstab, no network-mounts that might have 
failed. From the original message it looks like your network interface 
is not being set up correctly, but you should still be able to boot. 
Also "rmdir: command not found" probably means your PATH does not get 
set, or else you don't have execute permissions on rmdir. Odd  that this 
should be dependent on kernel version. You should go over and verify 
that the transfer of your linux .config went OK. Then verify that the 
new config does in fact enable modules for your network card, and enable 
the necessary settings for your init system (looks like you are using 
openrc?)




Re: [gentoo-user] Network throughput from main Gentoo rig to NAS box.

2023-10-01 Thread Dale
Tsukasa Mcp_Reznor wrote:
> There are quite a few things to tweak that can lead to much smoother 
> transfers, so I'll make an unordered list to help.
>
> mount -o nocto,nolock,async,nconnect=4,rsize=1048576,wsize=1048576
> rsize and wsize are very important for max bandwidth, worth checking with 
> mount after linked up
> nocto helps a bit, the man page has more info
> nconnect helps reach higher throughput by using more threads on the pipe
> async might actually be your main issue, nfs does a lot of sync writes, so 
> that would explain the gaps in your chart, needs written to physical media 
> before replying that it's been committed so more data can be sent.
>
> sysctl.conf mods
> net.ipv4.tcp_mtu_probing = 2
> net.ipv4.tcp_base_mss = 1024
>
> if you use jumbo frames, that'll allow it to find the higher packet sizes.
>
> fs.nfs.nfs_congestion_kb = 524288
>
> that controls how much data can be inflight waiting for responses, if it's 
> too small that'll also lead to the gaps you see.
>
> subjective part incoming lol
>
> net.core.rmem_default = 1048576
> net.core.rmem_max = 16777216
> net.core.wmem_default = 1048576
> net.core.wmem_max = 16777216
>
> net.ipv4.tcp_mem = 4096 131072 262144
> net.ipv4.tcp_rmem = 4096 1048576 16777216
> net.ipv4.tcp_wmem = 4096 1048576 16777216
>
> net.core.netdev_max_backlog = 1
> net.ipv4.tcp_fin_timeout = 15
> net.ipv4.tcp_limit_output_bytes = 262144
> net.ipv4.tcp_max_tw_buckets = 262144
>
> you can find your own numbers based on ram size.  Basically those control how 
> much data can be buffered PER socket, big buffers improve bandwidth usage to 
> a point, after that point they can lead to latency being added, if most of 
> your communication is with that NAS, you basically ping the NAS to get the 
> average latency then divide your wire speed by it to see how much data it 
> would take to max it out.  Also being per socket means you can have lower 
> numbers than I use for sure, I do a lot of single file copies, so my workload 
> isn't the normal usage.
> .
>


I finished my OS updates and started my weekly backup updates.  I
mounted using your options and this is a decent improvement.  I'm not
sure which option makes it faster but it is faster, almost double.  A
few examples using fairly large file sizes for good results. 


3,519,790,127 100%   51.46MB/s    0:01:05
3,519,632,300 100%   51.97MB/s    0:01:04
3,518,456,042 100%   51.20MB/s    0:01:05


It may not look like much, still slower than just a straight copy with
no encryption, but given previous speeds, this is a nice improvement.  I
think before I was getting about 25 to 30MB/s before.  This is the
settings shown by the mount command now, which should be what it is using. 


root@fireball / # mount | grep TV
10.0.0.7:/mnt/backup on /mnt/TV_Backup type nfs4
(rw,relatime,vers=4.0,rsize=1048576,wsize=1048576,namlen=255,hard,nocto,proto=tcp,nconnect=4,timeo=600,retrans=2,sec=sys,clientaddr=10.0.0.4,local_lock=none,addr=10.0.0.7)
root@fireball / #


I think it took all your options and is using them.  If you have ideas
that would speed things up more, I'm open to it but this is a nice
improvement.  I still think the encryption slows things down some,
especially on the NAS end which is much older machine and is likely
fairly CPU intensive.  A newer CPU that has the same clock speed and
number of cores would likely do much better, newer instruction support
and all.  I think I read somewhere that newer CPUs have extra stuff to
speed encryption up.  I might be wrong on that.

Thanks much.  Any additional ideas are welcome, from anyone who has
them.  If it matters, both rigs are on UPSs.

Dale

:-)  :-) 

P. S.  Those who know I garden, my turnip and mustard greens are popping
up.  My kale and collards are not up yet.  I watered them again to help
them pop up.  Kinda dry here and no rain until the end of the next week,
they think.  They never really know what the weather is going to do
anyway. 



Re: [gentoo-user] 6.1.53-gentoo-r1 kernel not booting

2023-10-01 Thread Michael
On Sunday, 1 October 2023 05:56:02 BST Valmor F. de Almeida wrote:
> On 9/30/23 17:25, Håkon Alstadheim wrote:
> > Den 30.09.2023 22:57, skrev Valmor F. de Almeida:
> >> Hello,
> >> 
> >> For a while now (3 weeks or so) I have been upgrading the linux kernel
> >> on a Dell XPS laptop starting from 6.1.41-gentoo (which is my current
> >> working kernel) to 6.1.53-gentoo-r1. No kernel I have built since is
> >> able to boot. I have been following the same method for many years:
> >> make oldconfig, etc...
> >> 
> >> The booting error starts at:
> >> 
> >> [snip]
> >> 
> >> * INIT: Entering runlevel: 3
> >> [snip]
> >> * Starting cronie ...
> >> * Starting DHCP Client Daemon ...
> >> * Starting laptop_mode ...
> >> * Mounting network filesystems ...
> >> /etc/init.d/netmount: line 45 /lib/rc/bin/ewend: Input/output error
> >> /lib/rc/sh/rc-cgroup.sh: line 184: rmdir: command not found
> >> INIT:
> >> INIT: cannot execute "/sbin/agetty"
> >> INIT: cannot execute "/sbin/agetty"
> >> INIT: cannot execute "/sbin/agetty"
> > 
> > Can you show /etc/fstab and the console-log for the entire boot? Seems
> > /sbin is not readable. You sure you have the kernel modules loaded? Are
> > you using an initramfs? If so, does that build without errors ?
> 
> Here is fstab:
> 
> /dev/nvme0n1p2  /boot   ext2defaults0 2
> /dev/nvme0n1p3  noneswapsw  0 0
> /dev/nvme0n1p4  /   ext4noatime,discard
> 0 1
> /dev/cdrom  /mnt/cdrom  autonoauto,user 0 0
> 
> I have not changed anything from 6.1.41-gentoo (which compiles and
> boots) except updating the config file for compiling the new kernel.
> Then I do: make && modules_install. Which runs without errors. After
> that: grub-mkconfig -o /boot/grub/grub.cfg.
> I am not using initramfs.
> 
> I don't know how to save the boot messages; it seems that if I turn on
> the logger in openrc, it will log the openrc messages but not sysinit
> runlevels?
> 
> Thanks,
> --
> Valmor

I think the error messages you're getting indicate inability to access your 
rootfs.  Have you perhaps changed the fs drivers in the latest kernels, from 
built in to modules?

Have you diff'ed your 6.1.41-gentoo .config file against the latest kernels' 
.config files to see what might have changed/missing?

You can set up a netconsole to check boot time messages:

https://www.kernel.org/doc/Documentation/networking/netconsole.txt
https://wiki.ubuntu.com/Kernel/Netconsole

In summary, build netconsole in the new kernel, or as a module, change GRUB's 
default CMDLINE from "quiet splash" to "debug" and add netconsole in the 
kernel command line:

netconsole=@/,[PORT]@[DEST_IP]

Then at the destination PC launch netcat/socat/telnet; e.g.

nc -u -l -p [PORT]

and reboot the PC you want to debug with the latest kernel, while watching the 
output on the destination PC's terminal with nc.


signature.asc
Description: This is a digitally signed message part.


Re: [gentoo-user] Switching from desktop to desktop without function keys.

2023-10-01 Thread Peter Humphrey
On Sunday, 1 October 2023 01:17:12 BST Dale wrote:

> I found it.  Kwin was the key I was missing.

Yes, I had to search for it too.

> I did check the wrap around, it was already set to wrap.  Still, now I know
> it will since I checked it. 
> 
> This is going to help a lot when the plasma thing decides to take a
> short nap.  I suspect that if I reset to a blank KDE config and started
> over, it would work like it should.  It's been a few years since I did
> that and I really need to give it a fresh start.  To be honest, it might
> fix a few quirks I'm seeing at times. 

Well, what with switching between stable and testing systems from time to 
time, I do it fairly often - create a new user account, that is. The process 
has become much easier since I started using my LAN server as an IMAP host, 
the way it's meant to be. It saves a lot of work in recovering my email 
history.

> Thanks much. 

Pleasure. It's a nice change not being the one asking for help.  :)

-- 
Regards,
Peter.