[00:13] hggdh: confirmed [00:15] jjohansen: should I open a bug for that? [00:16] hggdh: no not yet, I'll poke at it or at the least poke smb when he comes on [00:17] jjohansen: thank you [00:30] so now that i've grabbed the stacktrace, is there anything i can do to help with the debugging of bug 784335? [00:30] Launchpad bug 784335 in linux "Heavy network utilization with r8169 leads to kernel panic" [Undecided,Confirmed] https://launchpad.net/bugs/784335 === jjohansen is now known as jj-afk [00:33] back on later === jk-- is now known as jk- [04:37] Dose the current kernel support packet injection? [04:37] more specific. Will it support it for the ath9k drivers? [04:49] sorry, did anyone reply? [05:05] sorry, i kewp getting disconneted [05:05] any awnsers that i missed? === _LibertyZero is now known as LibertyZero === smb` is now known as smb [08:28] * apw yawns [08:30] hey apw & smb [08:30] moin jk- [08:31] morning jk- === yofel_ is now known as yofel [09:04] morning apw :D [09:06] hi all, since I upgraded to 11.04, my mic jack no longer works [09:06] I searched the bugs, but didn't find anyone else reporting this [09:06] what do i need to do to report a useful bug? [09:08] eagles0513875, hi [09:08] how goes it apw [09:08] valorie, thinking [09:09] eagles0513875 suggested I ask here [09:09] smb, can you remember what we file sound bugs against, alsa something something [09:09] apw: it was my suggestion to have her ask here as we thought it might be a kernel issue [09:09] me im kinda having a similar issue with usb webcam with mic and pulse audio [09:09] mic doesn't work either, but it never has [09:09] apw, Something like that... could it be alsa-driver or so? [09:09] I think [09:10] very likely a kernel issue, and reporting it against the right package is the key [09:10] and before my first coffee i can't think what its called [09:10] apw: should we have her try the proposed 38-9 kernel [09:10] I'll be around for another hour or so [09:10] valorie, Do you know what sound hardware you're using? [09:10] * valorie serves coffee around the chan [09:10] awilkins, i was just going to mention your fix [09:11] * awilkins grins [09:11] im wondering if his fix woudl apply to usb webcams that have mics then again im not sure what that fix is [09:11] not off the top of my head [09:11] Probably not to a USB webcam with integrated mic [09:11] what's the command to find out? [09:11] valorie: a simple lspci should tell ya [09:11] mines a Audio device: Intel Corporation N10/ICH 7 Family High Definition Audio Controller (rev 01) [09:11] [09:11] valorie: lspci on command line and find the line that says audio :D [09:12] i think before it worked with my other motherboard which had a realtek audio chipset this has an intel one : ( [09:12] valorie, i think its "ubuntu-bug audio" [09:12] 00:14.2 Audio device: ATI Technologies Inc SBx00 Azalia (Intel HDA) [09:12] * apw thinks people have been chanigng things on us [09:12] 01:05.1 Audio device: ATI Technologies Inc RS780 Azalia controller [09:12] Intel HDA... so that might be affected by that fix [09:13] Intel HDA is an abstraction for a bunch of different chipsets from what I can gather [09:13] awilkins, your change was to the codec side wasn't it ? remember which one? [09:13] AD1988 [09:13] valorie, Do us a `dmesg | grep hda` [09:13] And tell us what the line with hda_codec says [09:14] valorie: did you check ur settings in the bios [09:14] if you dont have it set to use hd you need to [09:15] http://paste.ubuntu.com/612193 [09:15] no line with hda_codec [09:15] how do I check the setting in the bios? [09:16] I've done that before, but years ago [09:16] valorie, You'd have to play that by ear - reboot, watch your power up messages for the key for "setup", and hunt around in your menus [09:16] ya [09:16] BIOS setup usually requires you to make an affirmative choice to save settings also [09:17] i checked my bios and i dont have any settings in mine [09:17] this is hopefully a temp motherboard i have [09:17] till i rma my higher end motherboard [09:17] But there are too many nonstandard variants for us to walk you through it, probably in the "PCI devices" area [09:17] actually im thinking my issue is more with skype itself [09:17] well, this is my laptop/work/main computer [09:17] cuz i use mumble [09:17] and my mic works just fine :( [09:18] oh weird [09:18] ya [09:18] i know [09:18] well, skype used to work [09:18] i know [09:18] now the mic doesn't [09:18] valorie: sme issue [09:18] same* [09:18] but I don't remember if that was a different lappy or this one [09:18] apw: who would we need to contact to report this as skype is in the ubuntu partner repo [09:18] BUT: soundrecorder doesn't work either [09:18] eagles0513875: HA! [09:18] like Microsoft will care [09:18] the funny thing [09:19] the older static libs on the skype site work just fine [09:19] even the version in 10.10 worked [09:19] * eagles0513875 needs to develop an alternative to skype before it gets destroyed [09:19] Skype works just fine on pulse now [09:19] skype hasn't worked for me for at least the last 3 versions of kubuntu [09:19] awilkins: i have no mic input [09:19] but I've not had a problems with the headphones for a long, long time [09:19] it works fine but no mic [09:20] awilkins: how did you manage to get it to work [09:20] jack worked until upgrade, and then it didn't [09:20] eagles0513875, Neither did I - previously suffered from #593018, then from #776964 [09:21] skype says to go into the pulseaudio settings and i have no idea where those are [09:21] veromix will do it [09:21] valorie, I had the same thing - but before I had to flip-flop the input selector to get the mic working, but then it stopped [09:21] awilkins: its saying i have to use the local mixer to adjust settings but kmix doesnt have my cam mic listed [09:21] or pavucontrol [09:22] eagles0513875: does alsamixer have it listed? [09:22] eagles0513875, Well, it sounds like the driver for your cam mic isn't working, or isn't present [09:22] in kmix my logitech quick cam is listed [09:22] sec [09:22] valorie, Since your hardware previously worked, more chance of working out what's wrong [09:24] skype is bugged [09:24] i installed pavucontrol and mic is picking up sound there [09:24] skype for some reason isnt [09:25] Which version of Skype? I'm presuming latest [09:25] Specifically, I have 2.2 beta and it works fine with GNOME / Pulseaudio. [09:26] If you can record sound from your mic, eagles0513875, it's not really a kernel problem, and I would suggest you'd have more luck in a channel devoted to userland software. [09:26] ya [09:26] awilkins: version of skype taht is in the partner repo [09:27] eagles0513875, AFAIK that's the same as the one straight from the skype website. Mine says 2.2.0.25 in it's "About" box [09:27] ya [09:27] might uninstall it [09:28] and use the static package from the site [09:29] yay, you got your sound working though! [09:29] eagles0513875, Try cleaning out it's settings first, move the ~/.Skype folder out of the way, start it up, and try a test call [09:29] I don't have time to restart tonight, but tomorrow when I start up, I'll look in the bios and see if I find anything suspicious [09:30] valorie, The other tool I found useful was http://www.alsa-project.org/main/index.php/HDA_Analyzer [09:30] valorie, That lets you mess directly with the codec parameters [09:31] valorie, In my case, my mic input pin was not set up right - it needed it's VREF setting to be 80, but the driver wasn't initializing it correctly [09:31] See : https://bugs.launchpad.net/ubuntu/natty/+source/linux/+bug/776964 [09:31] Launchpad bug 776964 in linux "p5n32e-plus HDA Nvidia AD1988B microphone input not working" [Low,In progress] [09:32] awilkins: still nothing [09:32] i dont have time to hack at this right now [09:32] valorie, We've not really discovered what your sound hardware is yet - HDA Intel hides a bunch of implementations and your dmesg didn't tell us what it was either [09:33] That tool will probably be more informative, at least [09:33] any way to dig deeper? [09:33] http://www.alsa-project.org/main/index.php/Help_To_Debug_Intel_HDA [09:33] oh, hda analyzer [09:33] which is a script to run [09:33] Yes, you have to run it as root [09:33] * eagles0513875 wants my original motherboard back so badly [09:33] sudo python run.py [09:33] not sure I can make heads or tails of it [09:33] my original motherboard works so much better then this one [09:34] would probably require a linux reinstall though :( [09:34] I'm a writer, not a devel [09:34] valorie, It just gives you direct access to all those little switches that you see in a recording studio [09:34] valorie, Instead of one big volume knob [09:35] awilkins: usually i stick with the nvidia nforce chipsets [09:35] those have realtek which i have never had any issues with [09:35] not to mention i can use fully my 5.1 atm down to 2.1 with this motherboard [09:35] eagles0513875, I have an nforce, but my sound is an Analog Devices [09:36] would love to take advantage of the spdif the other motherboard has [09:39] valorie, If you have HDAAnalyzer running, what's the name on the first AUD_OUT device? [09:41] awilkins, this thing should be packaged and installed by default [09:42] apw, The HDAAnalyzer thing downloads components of itself, but I suppose you could install the bootstrap script. I would guess that [09:42] i think i would be happier if someone packaged the bits [09:42] as its a bit scarey to download some random stuff and run it as root [09:42] I would guess that HDA Intel is probably responsible for quite a few bugs because of the myriad of implementations [09:43] But the actual implementation inside seems to hide well [09:44] lspci for me does not reflect that the codec is an AD1988B, neither does HDAAnalyzer either, to be true [09:44] Apart from some of the node names [09:44] for HDAanalyzer, just download snd-hda-tools from ppa:diwic/ppa and run "sudo hda_analyzer" [09:45] dmesg reports it, but valorie doesn't seem to have that so maybe there is an inconsistent level of logging in the various codec implementations in the drivers [09:45] oh, rather that wgetting it? [09:45] I was opening the /proc/asound/card0/ and looking at it [09:45] valorie, yeah, I packaged it and a few other hda tools up [09:45] (i e if you were asking me) [09:46] valorie, The first line of /proc/asound/card0/codec#0 seems to be the information we seek [09:46] At least, in my case [09:47] Codec: IDT 92HD71B7X [09:47] On the plus side, that's marvellously specific [09:47] On the downside, it's not the thing we have recently fixed [09:48] snd-tools is installing [09:48] So it worked in Maverick but not Natty? [09:48] yes [09:48] ok, what do you need from that analyzer? [09:49] valorie, I can't think of anything specific... but what you can do is try to find your Mic input pin [09:49] So you should have a bunch of PIN nodes [09:49] in node editor, or text dump? [09:49] Node editor [09:49] On the left in the tree there are a bunch of PIN nodes [09:50] oooh [09:50] If you look in the Config default section on the right, you will see some description of each node [09:50] Find the one your Mic is plugged into [09:50] Press Detect [09:50] Headphone Drive [09:50] Output [09:50] first pin [09:50] I found the "Jack color" and "Jack location" bits helpful locating it [09:51] mic jack is pink! [09:51] e.g. mine is PIN 0x17 Jack type : Mic Jack location : Ext Jack location2 : Rear [09:51] That's the one [09:51] What's it's Wiget control section say? [09:52] boxes are all unchecked [09:52] VREF HIZ below that [09:52] Ok, check "IN" and change the VREF to 80 [09:52] done [09:53] I think that's the jack for an external mic [09:53] Now open Sound recorder or something with a VU meter ( `pavumeter --record` ) and try it out [09:53] let me get one [09:53] or I guess I can use my headphones [09:53] Ah, what' the input for the Mic you are actually using [09:53] That one was probably not initialized if you weren't using it on purpose [09:54] Esp. if it has "input sense" [09:54] I was trying to get the internal mic working [09:54] Probably another pin [09:54] Press Detect [09:54] Input [09:54] VREF_HIZ [09:54] VREF_50 [09:54] VREF_GRD [09:54] VREF_80 [09:54] but it would be cool to get this one working too [09:55] internal mics are sometimes on the same plug as the external and connected when the jack is not [09:55] True, you might want to try that VU meter anyway [09:55] did, and nothing [09:56] just dead [09:56] ok, another pin [09:56] valorie, btw, regardless if you get somewhere or not, will you file a bug (unless you already did) for it, e g "using ubuntu-bug audio"? [09:56] thanks! [09:57] Pins are just the start, alas, the whole chain of things has to work.... I found the thing that draws an SVG diagram of your codec useful [09:57] Jack connection: Fixed [09:57] Jack type: Mic [09:57] awilkins, codecgraph is also packaged in snd-hda-tools [09:57] Jack location: Ext [09:57] Jack location2: Top [09:57] Jack connector: Digital [09:57] Jack color: Black [09:57] No presence [09:57] is another [09:57] And I was already reasonably familiar with the control set on my codec because I had to monkey around with the selectors to get it to work with Maverick [09:57] well, I will file one, but I wanted decent details [09:57] "it doesn't work" isn't very helpful [09:57] valorie, That one is probably an audio out [09:58] Stereo [09:58] Output Amplifier [09:58] you're right [09:58] You want ones that have the PIN cap "Input" [09:58] valorie, that's great although "ubuntu-bug audio" will include some relevant files that can help us analyze the problem [09:58] diwic, do you use hda analyser ? [09:59] apw, sometimes, yes [09:59] diwic, next time we are in the same place, you have to show us how to interterpret its output [09:59] Jack connection: Jack [09:59] Jack type: HP Out [09:59] Jack location: Ext [09:59] Jack location2: Front [09:59] Jack connector: 1/8 [09:59] Headphones out [09:59] Jack color: Green [09:59] is headphones [10:00] Headphone Drive [10:00] Output [10:00] apw, maybe it's time for another audio triaging session [10:00] widget control has nothing selected [10:00] apw, I saw JFo wanted more of that as well [10:00] valorie, Paste the contents of your /proc/asound/card0/codec#0 file to the pastebin [10:00] diwic, yeah i'd like to listen in on one again, there is more tooling now than i remember [10:01] apw, we could do one hda driver specific [10:01] yeah, as that is our primary pain point [10:01] http://paste.ubuntu.com/612205 [10:01] valorie, I think node 0x18 is your baby [10:02] valorie, Select node 0x18 and check the VREF value [10:02] Jack connection: Fixed [10:02] Jack type: Mic [10:02] Jack location: Ext [10:02] Jack location2: Top [10:02] Jack connector: Digital [10:02] Jack color: Black [10:02] No presence [10:02] there is none [10:02] in is checked [10:02] but no vref value [10:03] Hmm, from this file, node 0x18 should be "Internal Mic Capture Volume" [10:03] But no VREF [10:03] yes, that's the name [10:03] Bah [10:03] but no vref [10:03] awilkins, digital mics usually don't have VREF_80 and that stuff because the connection between the dmic and the codec is digital [10:03] maybe it never DID work [10:04] sec, gotta take the old dog outside [10:04] diwic, Thanks... I'm just an amateur [10:04] awilkins, and we need more helpful amateurs :-) and help them become more qualified [10:05] Gah, I had that codec grapher somewhere [10:06] blind, deaf, and when he's gotta go, he's gotta go [10:06] diwic, if you haven't met awilkins hes definatly a potential contributer on the debugging audio side [10:06] nice! [10:07] * diwic shakes hands with awilkins [10:07] * awilkins shakes hands back [10:07] awilkins, meet diwic our sound expert [10:08] awilkins, the codecgraph utility is packaged and ready in the snd-hda-tools package in ppa:diwic/ppa [10:09] diwic, Yup, installed [10:09] (or ppa:diwic/maverick for 10.10) [10:09] awilkins, so what I would do in this case is to take the codec a ride through hda-emu and see if the automuting does what it should [10:10] auto-switching between int and ext mic [10:10] valorie, when you posted that codec file, was anything plugged into the mic? [10:10] awilkins, potentially try a newer alsa-driver as well [10:10] hmm [10:11] I don't think so [10:11] I plugged in to test [10:11] I think the relevant nodes are ... nodes 0x18 (the mic pin) 0x1c (audio selector) and 0x12 (audio input) [10:11] and then just now, plugged in earphones to test [10:11] earphones are really why I'm here [10:12] as it is unknown whether or not the mic ever worked [10:12] laptop isn't that old, but [10:12] don't know [10:12] awilkins, hmm, I /think/ it is 0x18 - 0x1d - 0x13 because that's stream 0, but better double-check in hda-emu [10:13] so the headphones textdump is at http://paste.ubuntu.com/612209 [10:13] diwic, What's the significance of dotty lines over solid ones - I was tending to follow solid ones when I was debugging my own issue [10:14] awilkins, dotty lines are generally unconnected but could potentially be connected if one changes that in the driver or hda-emu [10:15] awilkins, or in hda-analyzer I mean [10:15] and here is the codec#0 with definitely nothing plugged in: http://paste.ubuntu.com/612210 [10:16] awilkins, ok so it is 0x18 - 0x1c - 0x12 actually [10:17] valorie, you don't happen to have an ATI controller, do you? [10:17] yes [10:17] valorie, you might be suffering from bug 741825 then [10:17] Launchpad bug 741825 in alsa-driver "ATI controllers [1002:4383] and [1002:4383] (rev 40): Intermittent record and jack sense failure" [Undecided,Incomplete] https://launchpad.net/bugs/741825 [10:18] gah! [10:19] valorie, and if so the recommended solution is https://wiki.ubuntu.com/Audio/InstallingLinuxAlsaDriverModules as we think this was finally fixed a few days ago [10:19] If your first one was plugged and your second one was not, then I would concur [10:19] 01:05.1 Audio device: ATI Technologies Inc RS780 Azalia controller [10:19] Because they are identical [10:19] apw, we should just see some more testing of this fix and then make it into a Natty SRU [10:20] apw, I think it needs two different commits to fix [10:20] diwic, big and ugly ? [10:21] apw, no, but potentially affecting a lot of machines, that's my only hesitation...but in this case I think it's worth it [10:21] ok, installing [10:21] and for this, I will restart [10:24] o/ [10:25] I just had a major crash of the whole system, ended up with this: http://wstaw.org/m/2011/05/24/2011-05-24_11-37-17_362_Oulu.jpg [10:25] any help ? [10:25] apw, i e affecting all ATI HDA machines [10:26] is there anything else I can get now (after a restart) that would help diagnose this? [10:29] jussi, hmmm another cpuidle_idle_call explosion [10:29] what kernel is that? [10:29] jussi@squirrel:~$ uname -a [10:29] Linux squirrel 2.6.38-8-generic #42-Ubuntu SMP Mon Apr 11 03:31:24 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux [10:31] ok I'll be away for lunch for a while, see you later! [10:32] apw: Im aroundish with this PC for the next ~4 hours. If there is anything else you need, please ask. Ill go file a bug in the meantime. [10:37] jussi: did you have your whole system lock up on u and freeze nastily [10:38] when you maximize konsole or certain other apps? [10:38] eagles0513875: no. [10:38] ok just checking cuz that is a super nasty bug which boils down to an nvidia driver issue [10:39] eagles0513875: given I dont have nvidia... [10:39] ahh [10:39] * eagles0513875 retreats to the amarok channel [10:40] bug 787442 [10:40] Launchpad bug 787442 in linux "Complete machine crash (kernel panic?) " [Undecided,New] https://launchpad.net/bugs/787442 [10:40] apw: ^^ [10:42] jussi: i was having those with atheros wifi card in my netbook [10:42] here goes nothing, restarting..... [10:43] gd luck valorie [10:43] jussi, you had a photo, could you attach that pls [10:44] apw: its attached - first attachment. [10:44] stupid launchpad, hiding the important one [10:44] heh [10:46] jussi, i've updated the subject. if this is reproducible you could try the -propsoed kernel which as a heap of stable updates (-9 [10:46] apw: I havent managed to reproduce :/ [10:47] i think i've seen 3 reports of something ismilar, one was put in my hands at UDS, but nothing common about them [10:47] apw: there was my issue with kernel panicing and my atheros wifi card which is fixed in proposed [10:48] apw: I had this bug earlier: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/775432 - I put it in someones hands at UDS. [10:48] Launchpad bug 775432 in linux "rtl8169 kernel panic" [Undecided,Confirmed] [10:49] thank you SO MUCH! [10:49] I now have earphones again [10:49] if you give me that bug report, I'll comment on it if necessary [10:50] jussi, that one is definatly different [10:50] apw: yeah. [10:50] apw: it was your hands (and Leann's) that I put it into iirc [10:51] Anywya, If I manage to reproduce, Ill let you know. [10:51] jussi, quite likely :) i had a lot of machines put in my hands over the week its hard to keep anything striaght [10:51] apw: :) [10:51] jj-afk, hggdh FYI: I am able to reproduce the maverick ec2 fail locally. The "close blk" is normal though. It seems to be a very early lockup though. As I see 100% cpu usage but no dmesg output at all. [10:53] valorie, bug 741825 [10:53] Launchpad bug 741825 in alsa-driver "ATI controllers [1002:4383] and [1002:4383] (rev 40): Intermittent record and jack sense failure" [Undecided,Incomplete] https://launchpad.net/bugs/741825 [11:01] also, my mic seems to work now [11:01] at least the volume meter is showing activity [11:01] \o/ [11:04] and SKYPE WORKS TOO! [11:04] y'all are miracle workers [11:05] valorie, one of the many advantages of open source ... one can fix it [11:06] kub. packagers are working on some free alternatives [11:06] I hope we come up with something as good [11:06] or better [11:09] awilkins: could ur fix possibly fix my issue with my webcam mic if it fixed it for valorie [11:13] eagles0513875, An integrated webcam mic would be a USB driver problem [11:14] ok [11:14] eagles0513875, Mine didn't fix valories, she had a jack sensing issue, and my issue was a codec initialization issue [11:14] ahh ok [11:14] i guess ill have to take a look at the bios [11:14] valorie has been fixed by another patch though [11:14] ok [11:15] I think if you can actually record sound from that mic it's not so much a kernel problem [11:15] ok [11:15] software as in skype issue [11:17] eagles0513875, Don't know - you might consider trying a GNOME session (or Unity) to see if it works there [11:17] eagles0513875, I don't know enough about KDE / phonon / whatever to speculate [11:17] ok no worries [12:37] what am I doing wrong if I try to boot from a live Natty USB stick and get the error "Unable to find a medium containing a live file system"? [12:38] and dropped to a busybox shell [12:42] ok; switched usb slot, that helped [13:32] hello everyone! are there known boot problems with oneiric and intel hd graphics? my boot 'fails' 4 out of 5 times (i can ssh into the machine). [13:32] i sometimes see the plymouth text theme (kms problem?), but most of the time it's just a black screen with a blinking cursor. not happening with nvidia on the same notebook. === ihateyou1oo is now known as elmo [14:25] htorque, nothing known, i use the kernel on my systems here and haven't seen that myself [14:26] but i am not using oneiric userspace with them [14:27] apw, thanks. the only weird thing i noticed when ssh'd into the machine, was the short output of lsmod: http://paste.ubuntu.com/612274/ [14:27] htorque, does lsmod complete ? [14:28] i got a new prompt, so i guess yes (i didn't check the return value) [14:29] a prompt is enough for me [14:29] so i'd say we're only half booted [14:32] apw, would you say that looks like a kernel issue? i would then try to bisect [14:33] very hard to say, i would try with the last natty kerenl on your userspace [14:33]