=== blahdeblah_ is now known as blahdeblah [10:24] Hi all [10:25] I've this kernel version: 5.15.0-60-generic #66-Ubuntu SMP Fri Jan 20 14:29:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux [10:26] cloned repository in my area: [10:26] git clone git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy kenel-ubuntu [10:28] I suppose that my actual running version "5.15.0-60-generic #66-Ubuntu" is the same on repository "Ubuntu-5.15.0-60.66", can someone confirm? [10:31] do you read my messages? [11:19] We read the messages, yeah [17:59] claudio, that's right. we tag all the versions [18:00] and usually you just need to match major version (5.15.0 in this case), ABI number (60) and flavor (generic) [18:01] .66 in this case is just an upload number that we only bump (while keeping the same ABI number) if something really went bad (ie, the initial version of that ABI doesn't build for reason) [18:27] @mhcerri, Thank you for the info [18:29] @mhcerri, do you know how can be identified a driver(module)? [18:30] claudio, what do you mean exactly? [18:30] I supposed was present a version number [18:30] what module? [18:30] but when I do a modinfo I get this: [18:30] modinfo snd_usb_audio [18:30] filename: /lib/modules/5.15.0-60-generic/kernel/sound/usb/snd-usb-audio.ko [18:30] license: GPL [18:30] description: USB Audio [18:30] author: Takashi Iwai [18:30] srcversion: DC685E98913EC0BF1B7D41E [18:31] No vermagic? [18:31] name: snd_usb_audio [18:31] vermagic: 5.15.0-60-generic SMP mod_unload modversions [18:31] in fact [18:31] vermagic identifies the source [18:32] So I know that I've to get the repo [18:32] put in checkout mu actual (kernel) version [18:33] Than in git I can discover what wersion of that driver is implemented [18:33] am I rigth? [18:33] vermagic identifies the headers the source was built with [18:33] and srcversion? [18:34] the source code ? [18:34] I am not sure, vermagic identifies the kernel headers that are used when compiling [18:35] claudio: Are you planning on patching that module? [18:35] to be honest I would [18:35] this is my first time... [18:35] but currently I've to understand where is the problem [18:36] because I've a DAC that sometimes loose the connection [18:36] So, I noticed that the version implemented is the last-1 [18:36] Is there an upstream patch that fixes it? [18:37] on linux master repo [18:37] I suppose that the problem isn't solved also with the last [18:37] but is my opinion [18:38] @Jeremy31, when you want to debug something where you look? [18:38] log? [18:38] rebuild a module with debug enable... [18:39] if you have a suggestion I would appreciate [18:40] about the version... I'm on UBUNTU: Ubuntu-5.15.0-60.66 [18:40] If you don't have Nvidia graphics you could test the newest kernel at https://kernel.ubuntu.com/~kernel-ppa/mainline/ [18:42] the version in use is with the commit NOV 11 2022 [18:43] so it is recent [18:43] Or you could search for your DAC model and linux, see if others found a solution using a module parameter [18:43] Other than that you could run> sudo dmesg -w [18:44] In terminal and see what happens in terminal during the disconnect [18:48] I made a mistake [18:48] on linux kernel that version is the last [18:48] so... we're on the last version [18:49] @Jeremy31, thank you for the suggestion [18:49] for sure I'll [18:51] Anyway I suppose that the problam stays on that module but.. I'm not sure...