Changes between Initial Version and Version 1 of Ticket #14242, comment 10
- Timestamp:
- Oct 31, 2018, 8:56:21 AM (6 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #14242, comment 10
initial v1 1 @tidux Let's go straight for the 'extended' kernel messages; with some luck it will be like a cheat sheet, allowinga fairly quick fix.1 @tidux Let's go straight for better tracing options; with some luck it will be like a cheat sheet, leading to a fairly quick fix. 2 2 3 3 I've found this page [https://www.kernel.org/doc/html/latest/sound/hd-audio/notes.html]. It mentions a few hints. Here's those that seem most interesting to me; the first one might not be so easy, if so proceed to the next ones: … … 11 11 (those seem to be C++ defines, meaning you need to recompile the linux driver ?) 12 12 13 Seems it's possible to get a direct, simple, dump of init verbs:13 Seems it's possible to get pin configs directly from terminal; unfortunately the init_verbs can probably not get retrieved, but pin configs might be interesting anyway: 14 14 15 15 {{{ … … 21 21 }}} 22 22 23 So presumably you would retrieve the verbs/payloads describe above by typingthis in a terminal/xterm:23 The document mentions "hwC0D0" in the path, whereas your dmesg output mentions "hdaudioC0D0". So some adapting might be needed. Anyway presumably you would retrieve the data by typing something like this in a terminal/xterm: 24 24 25 25 {{{ … … 28 28 29 29 30 This is the tracing that seems hopeful:30 This is the tracing that seems most hopeful to me: 31 31 32 32 {{{ … … 40 40 41 41 I likely can decode the output by hand, the "hda-decode-verb" stuff mentionned below might not be necessary. 42 43 I wonder if it retro-actively includes tracing produced by the hda driver during boot-up though. If it does not, maybe it's possible to trigger a re-init of the driver, by hand, using the "reconfig" trick described in the document, after activating tracing.