Re: (no subject)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



Update: Thanks everyone for helping me think! Finally, I discovered that all three of my USB devices were broken. A fourth one finally connected. I should've known when dmesg did not see anything at all, that they were broken.

On 3/24/20 11:27 PM, Robin Martijn wrote:
Thanks everyone for thinking with me! However, I have indeed rebooted many times, and I have verified my versions. I am, with no doubt, on the right kernel.

On 3/24/20 11:02 PM, Maarten de Vries via arch-general wrote:
On Tue, 24 Mar 2020 at 22:57, Andy Pieters <arch-general@xxxxxxxxxxxxxxxxx>
wrote:

On Tue, 24 Mar 2020 at 21:38, mick howe via arch-general <
arch-general@xxxxxxxxxxxxx> wrote:

you have rebooted since update? Every time updates generate a new
startup?


I concur: in many cases you need to reboot after doing a kernel update in
order to recognise devices that were not plugged in before the update


Indeed.

To also explain why this happens: the relevant kernal modules hadn't been
loaded yet, and the modules on disk are for the newly upgraded kernel while you're still running an older kernel. In that case, `pacman -Qi linux` and
`uname -r` will also show different version information.

-- Maarten




[Index of Archives]     [Linux Wireless]     [Linux Kernel]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Share Photos]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]

  Powered by Linux