On Mon, 12 Dec 2022 20:42:44 +1030
Tim via users wrote:
> Do you have any AKmods installed? If it's rebuilding something when a
> new kernel boots, versus romping straight into it at other times, that
> might explain a timing difference.
I always let the akmods finish building before I reboot,
Tim:
>> Odd that it's kernel reboots only. I wonder if there's some timing
>> issue that's different then?
Tom Horsley:
> My best theory is that the kernel doesn't properly reset the device
> from scratch, but assumes it was left in some state which the old
> kernel didn't leave it in. But
On Sun, Dec 11, 2022 at 6:45 PM Tom Horsley wrote:
> My best theory is that the kernel doesn't properly reset the device
> from scratch, but assumes it was left in some state which the old
> kernel didn't leave it in. But that's just a wild guess (and I've never
> worked up the energy to try
On Mon, 12 Dec 2022 09:58:07 +1030
Tim via users wrote:
> Odd that it's kernel reboots only. I wonder if there's some timing
> issue that's different then?
My best theory is that the kernel doesn't properly reset the device
from scratch, but assumes it was left in some state which the old
On Sun, 2022-12-11 at 17:54 -0500, Tom Horsley wrote:
> Shutting down the system then powering back up also fixes the keyboard
> but briefly fiddling with the dongle is much faster.
I saw USB hub somewhere which had a button on each port. It was a
temporary power killer to the nearby port, to
On Sun, 11 Dec 2022 16:39:12 -0600
Roger Heflin wrote:
> My logi wireless keyboard/dongle works to get into the bios. So there
> would not appear to be any driver needed to operate it, so that would make
> me suspect the reboot is more of the cause than anything else.
Yea, it always speaks to
My logi wireless keyboard/dongle works to get into the bios. So there
would not appear to be any driver needed to operate it, so that would make
me suspect the reboot is more of the cause than anything else.
And usb chipsets/connections in my experience aren't the most reliable
devices depending
On Mon, 2022-12-12 at 09:00 +1030, Tim via users wrote:
> You could try setting a USB port to "always on." Alternatively,
> perhaps you need the opposite? So the USB port switches off then on
> again during a reboot, and resets the dongle.
Oops...
On motherboards with jumpers you have choices
On Sun, 2022-12-11 at 14:45 -0500, Tom Horsley wrote:
> Just got kernel 6.0.12-300.fc37.x86_64, and after rebooting to
> get it loaded, my Logitech wireless keyboard dongle wasn't
> talking. Unplugged it, plugged it back in, and the keyboard
> works again.
>
> Every few months this happens on a
On Sun, 2022-12-11 at 14:45 -0500, Tom Horsley wrote:
> Just got kernel 6.0.12-300.fc37.x86_64, and after rebooting to
> get it loaded, my Logitech wireless keyboard dongle wasn't
> talking. Unplugged it, plugged it back in, and the keyboard
> works again.
>
> Every few months this happens on a
On Sun, 11 Dec 2022 15:13:37 -0500
Go Canes wrote:
> but perhaps
> you would have fewer issues using a non-external-hub port
Nah, it happened just as (in)frequently when I had it plugged
directly into the computer. I moved it to the hub after I got tired
of having to walk around to the back of
On Sun, Dec 11, 2022 at 2:46 PM Tom Horsley wrote:
>
> Just got kernel 6.0.12-300.fc37.x86_64, and after rebooting to
> get it loaded, my Logitech wireless keyboard dongle wasn't
> talking. Unplugged it, plugged it back in, and the keyboard
> works again.
>
> Every few months this happens on a
Just got kernel 6.0.12-300.fc37.x86_64, and after rebooting to
get it loaded, my Logitech wireless keyboard dongle wasn't
talking. Unplugged it, plugged it back in, and the keyboard
works again.
Every few months this happens on a kernel update (not on all
kernel updates though). At least I have
13 matches
Mail list logo