| === TheMuso_ is now known as TheMuso | |
| === rikai__ is now known as rikai | |
| === macd_ is now known as macd | |
| === asac_ is now known as asac | |
| [13:59] <zul> BenC: ping | |
| [15:22] <sn9> zul: he's been idle for a day; i don't think he's near his computer | |
| [18:01] <BenC> zul: ? | |
| [18:07] <sn9> irc-tag... | |
| [18:08] <sn9> BenC: well, as long as you're here, remember Bug #88746? i did some testing, and i think i found what sets it off | |
| [18:08] <ubotu> Launchpad bug 88746 in linux-source-2.6.22 "ehci_hcd module causes I/O errors in USB 2.0 devices" [Undecided,Invalid] https://launchpad.net/bugs/88746 | |
| === doko_ is now known as doko | |
| [20:14] <sourcemaker_> is there a good book to understand the Linux Kernel. (Architecture, Development.. and so on)... | |
| [20:15] <sn9> just look at the o'reilly catalog and pick something | |
| === johanbr_ is now known as johanbr | |
| [23:29] <timing> hey | |
| [23:29] <sn9> ho | |
| [23:30] <timing> at my install, audio is working in an older 2.5.24 build. but not in the versions from -7 till -16 | |
| [23:30] <sn9> why 2.5? | |
| [23:30] <timing> 2.6.24-5 and before is where audio is working very good | |
| [23:30] <timing> uhh sorry 2.6 | |
| [23:30] <timing> confused with the -5 I wanted to type later on | |
| [23:31] <sn9> do you by any chance have a realtek audio chipset? | |
| [23:31] <timing> And now i'm wondering what those -5 -7 things mean | |
| [23:31] <timing> just a difference in compile flags? | |
| [23:31] <timing> 00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02) | |
| [23:32] <sn9> there is a changelog in /usr/share/doc/linux-image-2.6.24/ | |
| [23:32] <timing> thanks | |
| [23:32] <timing> but could it be in modules as well? | |
| [23:32] <timing> or somewhere total different? | |
| [23:32] <sn9> yes | |
| [23:33] <timing> but it could've changed in -6? But I don't have that version | |
| [23:33] <sn9> the changelog is a log, so it includes older versions | |
| [23:33] <timing> ok | |
| [23:33] <timing> * hda_intel suspend latency: shorten codec read | |
| [23:34] <timing> * config: Re-enable snd-hda-intel | |
| [23:34] <timing> hmm | |
| [23:34] <timing> o the latter one is way before -5 already | |
| [23:34] <sn9> it's in reverse-chronological order | |
| [23:34] <timing> uhm | |
| [23:35] <timing> it's date \n changes? | |
| [23:35] <timing> or changes \n date ? | |
| [23:35] <timing> the first line is from 2.6.24-5.8 | |
| [23:36] <timing> no idea if i have 2.6.24.7 .1.2.3.4.5 or so | |
| [23:36] <sn9> version, changes, date | |
| [23:37] <timing> the susped latency is changed in: | |
| [23:37] <timing> linux (2.6.24-5.8) hardy; urgency=low | |
| [23:38] <timing> sn9: the -5 -7 -8 numbering is changing compile flags? or different patches against 2.6.24 on kernel.org ? | |
| [23:39] <sn9> it's the changes you see in the log | |
| [23:39] <timing> OKay so that's like a lot :-) | |
| [23:40] <timing> So how can I help developers with fixing this? | |
| [23:40] <timing> a guy in #alsa said he fixed this already | |
| [23:40] <timing> but there is no bug number or no revision number for the fix he made | |
| [23:40] <sn9> did he say what version of alsa he fixed it in? | |
| [23:40] <timing> he said see the changelog, couldn't find it | |
| [23:41] <timing> he is very busy | |
| [23:41] <timing> so that's too bad | |
| [23:41] <sn9> did he remember how long ago he fixed it? | |
| [23:41] <timing> I can check my irclogs | |
| [23:42] <sn9> ok | |
| [23:42] <timing> where he said, 'okay fixed it' | |
| [23:42] <sn9> oh, so he fixed it while you were on irc? | |
| [23:44] <timing> yeah think so | |
| [23:44] <timing> i grepped on crimsun on my logfiles. these are 4 lines: | |
| [23:44] <timing> 02/Sat-23-02-#alsa.log:17:30:28< crimsun_> hmph, I think the patch_analog updates broke it | |
| [23:44] <timing> 02/Sat-23-02-#alsa.log:17:30:34< crimsun_> it's alsa-related | |
| [23:44] <timing> 02/Sat-23-02-#alsa.log:17:30:46< crimsun_> I'll try to update alsa-source today for it | |
| [23:44] <timing> 02/Sat-23-02-#alsa.log:17:32:13< crimsun_> because I'm looking at the changes. | |
| [23:44] <timing> o he is here as well! | |
| [23:44] <timing> haha didn't know that | |
| [23:45] <sn9> so, this was Feb 23? | |
| [23:45] <timing> yeah | |
| [23:46] <timing> and then I went back later: | |
| [23:46] <timing> 03/Mon-31-03-#ubuntu+1.log:22:44:33< crimsun> timing: that's already fixed upstream. | |
| [23:46] <timing> 03/Mon-31-03-#ubuntu+1.log:22:44:41< crimsun> (and has been for some time, I might add) | |
| [23:46] <timing> 03/Mon-31-03-#ubuntu+1.log:22:44:52< crimsun> not in Ubuntu yet. | |
| [23:46] <timing> then i stumbled upon him in #ubuntu+1 | |
| [23:46] <timing> He is everywhere :-) | |
| [23:49] <timing> o this is the bug btw: https://bugs.launchpad.net/bugs/209047 | |
| [23:49] <ubotu> Launchpad bug 209047 in linux "Sound did work in 2.6.24-5 but not in 2.6.24-7 till 2.6.24-16" [Undecided,Incomplete] | |
| [23:53] <timing> going to sleep now, bbl | |