[00:18] <pgraner> ogasawara: how tyler working out for ya?
[00:21] <ogasawara> pgraner: good so far, I've started some builds on it already
[00:22] <pgraner> ogasawara: yea I noticed all 12 cpus are pegged
[00:22] <ogasawara> :)
[00:22]  * maco wonders how much of this channel will show up in #ubuntu-meeting in a half hour to support your comrades
[00:22]  * maco points at pgraner and manjo
[00:23] <lifeless> komrades
[00:23] <ogasawara> Ooo, is the ubuntu membership meeting happening?
[00:24] <maco> yes
[00:24] <maco> in 35 minutes
[00:24]  * ogasawara will try to be there then
[00:31]  * bjf done for today
[00:38] <crimsun> cnd: the intent is, but I'm afraid we need to work on it more. The current wait is too short.
[00:39] <crimsun> cnd: namely there are reports of it being worse with the newer driver snapshots, so it doesn't affect LTS currently.
[00:56] <manjo> pgraner, membership meeting starts in 5mts ? 
[00:56] <maco> manjo: oh so you ARE alive!
[00:56] <maco> manjo: 4 minutes now :)
[00:56] <manjo> ok
[00:56] <manjo> :)
[00:56] <pgraner> maco: yep
[00:57] <maco> pgraner: if you werent online, i was going to call your house
[00:58] <pgraner> maco: why?
[01:00] <manjo> pgraner, you on ubuntu-meeting ? 
[01:00] <pgraner> manjo: yep
[01:00] <maco> pgraner: so you wouldnt miss the meeting?
[01:12] <ogasawara> pgraner: tyler cranks out builds quick!
[01:12] <pgraner> ogasawara: sweet... its dead quiet
[01:13] <pgraner> ogasawara: once we get emerald redone I might send this one on to you
[01:13] <ogasawara> pgraner: nice :)
[01:13] <pgraner> ogasawara: you need it more than I do
[01:14] <bjf> pgraner, is it like the one you are going to send me or is that yet another?
[01:15] <manjo> ogasawara, pgraner I made it 
[01:15] <ogasawara> manjo: yep, congrats!
[01:15] <pgraner> manjo: congrats
[01:15] <manjo> thanks yall
[01:16] <akgraner> partah time for manjo!  \o/ \o/ woo hoo!!!
[01:16] <manjo> akgraner, thanks for the wiki clean up ... owe you a drink of choice 
[01:16] <manjo> akgraner, and the nice reco
[01:17] <akgraner> :-)  you are most welcome! 
[01:18] <jjohansen> back on later
[01:20] <maco> pgraner: your wiki page makes me think ive only met half the kernel team. or at least only been introduced to half of them by name
[01:20] <pgraner> maco: there are 27 now
[01:21] <maco> WOW
[01:34] <pgraner> ogasawara: your a whimp... tgardner had tyler at 35 load ave. today your at 13.75
[01:39] <ogasawara> pgraner: damn.  I wonder what he was doing.
[01:40] <pgraner> ogasawara: running stress and builds at the same time
[01:40] <pgraner> ogasawara: :-)
[01:40] <ogasawara> pgraner: that's cheating
[01:40] <pgraner> ogasawara: if you ain't cheatin' you aint trying
[01:40] <ogasawara> heh
[01:41] <pgraner> ogasawara: and if you get caught you ain't trying hard enough :-)
[02:11] <pgraner> ogasawara: awww I'm touched :-)
[02:16] <ogasawara> pgraner: congrats!  /me goes to eat dinner
[02:17] <pgraner> ogasawara: thanks :-)
[02:40] <mrec> I figured out why my pc randomly reboots
[02:40] <mrec> it's fvdr
[02:40] <mrec> vdr
[02:40] <mrec> why vdr does that I don't know
[02:43] <cnd> crimsun: what do you mean by "it doesn't affect LTS"?
[02:43] <cnd> Ubuntu 10.04 LTS?
[02:51] <RAOF> Thanks for that Xorg.0.log; nouveau isn't working, but the fallbacks are successfully kicking in, which they didn't do earlier in the Lucid cycle.
[07:00] <stenten> Am I correct in thinking that installing the two header files for the mainline PPA kernels will let you install restricted drivers through jockey?
[07:00] <RAOF> stenten: Sometimes.
[07:04] <stenten> i'm trying to troubleshoot someone's kernel problems :(. Should the lts-backport-maverick kernel Tim Gardner posted in kernel-ppa for the LTS Backport Kernel idea work?
[07:05] <RAOF> It depends on whether or not the restricted driver's kernel component will build against the new kernel.  I know that fglrx doesn't, I'm unsure about nvidia.
[07:08] <stenten> Ah, that makes sense. It's the Broadcom Wireless driver. I'm thinking they just didn't install the header files correctly, so it should be moot.
[07:10] <stenten> Is there anything special in the ubuntu-specific (default) kernels that would affect restricted drivers, or is all that handled by the header files?
[07:15] <Sarvatt> stenten: grab bcmwl-kernel-source from maverick
[08:22]  * apw aches
[08:25] <smb> apw, Hey morning. Before I forget this (because I did already many times), I got one interesting case of being unusually hot for an old thinkpad. Those things pretend to have a floppy drive even when not attached. And I noted it running quite hot. After blacklisting floppy its now down to a sensible temp on idle.
[08:26] <amitk> heheh, overheating due to floppy driver hallucinations
[08:27] <smb> Nearly. :) More to trying to access it over and over agai
[08:28] <smb> Some part of the basic installation tried to find out what is on the non-existing floppy in the non-existing drive. And seemed not to take a nothing for an answer
[08:28] <apw> smb, i wonder what the thing was doing
[08:29] <smb> apw, Not sure it came from userspace (as cd polling used to be) or from the driver to check there is a media present
[08:30] <smb> First thought its the lack of any frequency scaling (a quite old hw, T21 I think)
[08:31] <smb> But wanted to get rid of this anyoing "read error on fd0" messages
[08:31] <smb> and surprise, after blacklisting temp went down from 80 to 50C
[08:31] <apw> smb, yeah ... 
[08:32] <apw> smb, i am almost supprised if it was that busy that you could remove it at all
[08:32] <smb> apw, I could not
[08:32] <smb> blacklisted and rebooted
[08:32] <smb> cking, \o
[08:34] <apw> smb, ahhh interesting, i bet waiting for status or something from the interface chipset
[08:36] <smb> apw, That would be my guess. But thats probably just something that happens not very often. I don't think any reasonably modern TPs will try to fake a floppy drive
[08:36] <apw> smb, is it faking it for hot plug ?
[08:37] <cking> morning, (yawn)
[08:37] <smb> Yes, afaik. You were able to replace the cd drive with a floppy drive (after some magic to disable the ide bus) and on older models you could attach a floppy later
[08:38]  * smb places a cup of coffee into cking 's hand
[08:39]  * abogani2 waves
[08:39] <apw> abogani2, moin
[08:39]  * smb waves back
[08:39] <apw> smb, nasty but must be the trigger ...
[08:39] <abogani2> cnd, apw: http://kernel.ubuntu.com/git?p=abogani/ubuntu-lowlatency-maverick.git;a=summary lowlatency branch
[08:39] <abogani2> cnd, apw: http://kernel.ubuntu.com/git?p=abogani/ubuntu-lowlatency-maverick-meat.git;a=summary lowlatency branch
[08:40] <apw> cking, morning, its tooo hot here again
[08:40] <abogani2> *meta
[08:42] <smb> apw, cking You actually see this bright thing in the sky? Its magically bright here but enough clouds and only 15°C
[08:43] <apw> yeah only 13c here so far, but its not going to stay cool for long i can feel it
[08:43] <apw> smb, and where is your 'degrees' button on your keyboard
[08:44] <smb> Above the ^ key :-P
[08:44] <smb> which is left of 1
[08:44] <apw> not something i would have expected you to have an actual key for, no such key for me
[08:45] <apw> smb, so is that also the key which adds a flying circle over the top of vowels ?
[08:46] <smb> Its not considered that useful to do it
[08:46] <smb> I bet there is some magic to make it behave like ~
[08:46] <smb> But now thats instant
[08:47] <smb> apw, Probably amitk 's keyboard does that
[08:48] <amitk> no flying circles on the finnish keyboard
[08:49] <amitk> though there is a key for 'A' with the flying circle (used in norwegian, i think)
[08:54]  * smb wonders whether abogani2 currently plays with his PPA
[08:56] <abogani2> smb: No
[08:57] <cking> man it's sunny today - and it's near a UK holiday
[08:57] <smb> abogani2, Hrm, I just tried to get the sources for the linux-rt packages from it and the orig.tar.gz appears lost to me
[08:57] <smb> cking, Its a trap. As soon as you go out there will be water
[08:59] <cking> smb, I need the rain to water my garden, so it's no big loss ;-)
[09:00] <smb> cking, Well no, but you don't want it on *you*, do you?
[09:00]  * smb had his share of cold water from above yesterday
[09:00] <abogani2> smb: Mhhhh
[09:24] <abogani2> smb: I surely have did a mistake: apologize for this. It is my fault haven't did enough tests. So I have investigated and _seems_ that orig.tar.gz is the same of the previous version (if I don't recall wrong I almost sure to have used "debuild -S -sd"). In any case I'll upload again to an other PPA to be sure. Sorry again. :-(
[09:28] <smb> abogani2, Ah, ok. In theory the orig.tar.gz would be a clean 2.6.31 linux tree, so I should also be able to use that. But I wanted to be sure. Just let me know when it has been uploaded. No need to wait for the build for me. :)
[09:31] <abogani2> smb: Ok thanks. I'm _really_ sorry.
[09:31]  * abogani2 doesn't like waste time of UKT members...
[09:32] <smb> abogani2, Bah, compared to the time you had to wait on me thats nothing.
[09:55] <abogani2> smb: I have found the files which I used to first upload. I have just re-uploaded and again orig.tar.gz is unavailable :-(
[09:55] <smb> abogani2, Ok, cool. Some PPA as before, right?
[09:55] <smb> err
[09:56] <smb> I should open my eyes this morning
[09:56] <abogani2> smb: No because same PPA don't accept to build the same version two times.
[09:56] <abogani2> smb: Is it debdiff enough for you?
[09:57] <smb> abogani2, I would want to try to extract in and look at things. Hm, have you an account on zinc?
[09:57] <abogani2> smb: Sure.
[09:57] <smb> abogani2, Then just dump the files there. :)
[09:59] <abogani2> smb: Also orig.tar.gz ?
[10:00] <smb> abogani2, Is that just a linux-2.6.31.tar.gz? (Like from kernel.org)? In that case probably just add a text file with the md5sum of it and I make one here.
[10:00] <smb> I just want to be sure to take the same orig.tar.gz when playing with it
[10:01] <abogani2> smb: It could be Karmic orig.tar.gz. In any case Zinc seems go fast now so I'm uploading it too,
[10:02] <smb> abogani2, right, which is in turn just the plain Linus tree. But perfect. Seems you got a good uplink. :)
[10:28] <abogani2> smb: I have just uploaded the classic triple (diff, dsc, orig), debdiff (only for safety) and the two files for meta. At the moment the only issue that I know is the section which is settled to "lucid" (I suspect "lucid-updates" should be used instead).
[10:28] <apw> lucid-proposed probabally
[10:28] <smb> abogani2, Make that 'lucid-proposed" 
[10:28] <smb> yeah
[10:29] <smb> after release (at least the packages we do) is uploaded to proposed and then later archive copied to updates
[10:30] <smb> abogani2, I will have a look next and reply anything I think to your original email
[10:30] <abogani2> smb: Ok. Thanks!
[10:59] <michiel_e> hello
[11:00] <michiel_e> is there a difference in module loading/features used between normal and recovery mode?
[11:01] <michiel_e> because I have a server in here who is shutting down itself after 1 minute or so
[11:01] <michiel_e> but in recovery mode it doesn't do that
[11:01] <michiel_e> even when I manually go in recovery mode and then start runlevel 2
[11:02] <michiel_e> so even when the same applications are running, it doesn't shutdown in recovery mode but does in normal mode
[11:02] <michiel_e> so I try to pinpoint the problem
[11:06] <michiel_e> could it be that a kernel module reacts on cpu fans not running (at least 0RPM in sensor data) but in recovery mode ignores that?
[11:08] <kro> have a look at /boot/grub/grub.conf to see which kernel options differ in your case
[11:10] <michiel_e> quiet splash in normal, and single without quiet splash in recovery mode
[11:11] <michiel_e> even when I disable splash and quiet on boot it shutsdown
[11:13] <kro> and no reason for the shutdown in the logs? is it really a shutdown or rather a crash?
[11:14] <michiel_e> it could be a crash
[11:14] <michiel_e> but I think a shutdown
[11:14] <michiel_e> because I see, when running top, flush and mdadm stopping it's devices
[11:15] <michiel_e> but I cannot find a shutdown reason in the logs
[11:16] <michiel_e> the only error I can find, but I really thing that is not the problem, is: svc: failed to register lockdv1 RPC service (errno 97)
[11:16] <michiel_e> using the nfs kernel server
[11:23] <michiel_e> can I use some kind of verbose logging?
[11:24] <michiel_e> more verbose then removing quiet
[11:26] <kro> try replacing "quiet" with "debug"
[11:26] <kro> and maybe stuff your logs into some pastebin and paste the link here :-)
[11:26] <kro> that is, syslog and maybe dmesg
[11:26] <michiel_e> ok
[11:27] <michiel_e> udev-worker add_inotify failed couldn't be the cause now could it?
[11:30] <michiel_e>  /var/log/messages, right?
[11:33] <joaopinto> michiel_e, that was a bug during development on which a shutdown was performed because the fsck from mountall was running on the background, and the script was invoking the *after file system check* reboot when the system was running, that bug is expected to be fixed now, I am just wondering
[11:35] <michiel_e> joaopinto, lucid-updates is set as repo as well as multiverse and universe
[11:35] <michiel_e> and fully upgraded via dist-upgrade
[11:36] <michiel_e> joaopinto, you know how I can confirm that is that bug?
[11:36] <joaopinto> mv /etc/init/mountall-reboot.conf /etc/init/mountall-reboot.conf.disable
[11:36] <michiel_e> or have a launchpad link?
[11:36] <joaopinto> that would make sure the mountall rebook will not be invoked
[11:37] <joaopinto> but this really a wild guess assuming it's a reboot and not a crash
[11:37] <joaopinto> is
[11:37] <michiel_e> yeah well, it looks like a crash, but looking at the processes it just flushes to the disk
[11:37] <michiel_e> so I actually don't know
[11:38] <michiel_e> the system doesn't give a shutdown message
[11:38] <michiel_e> but it seems like the kernel knows it's shutting down
[11:40] <apw> michiel_e, most fan control is bios level
[11:41] <michiel_e> the mountall-reboot.conf doesn't get invoked
[11:41] <michiel_e> so it's not that bug I guess
[11:41] <michiel_e> apw, but Ubuntu is using the sensor limits, right?
[11:41] <apw> michiel_e, and one minute seems a bit quick to overheat anyhow
[11:42] <michiel_e> apw, yeah but it's not even overheating
[11:42] <apw> michiel_e, you can find out what they are, but most actual control is done in the bios
[11:42] <apw> i suspect its more likely something else, a panic or something
[11:42] <apw> if you can see the console, then i would boot without quiet and without splash
[11:42] <apw> and see if you see anything on the console to aid debug
[11:43] <michiel_e> the sensor data: http://pastebin.com/3akr24m4
[11:44] <michiel_e> I'm worried if the system reacts on the fan RPM's being 0
[11:44] <michiel_e> this is the system information: http://pastebin.com/NUTt6T6W
[11:44] <apw> michiel_e, i don't know of any support there that is not builtin, and therefore would behave the same
[11:45] <apw> in recovery and normal modes
[11:49] <michiel_e> I am going to test with recovery mode, going through normal boot process
[11:49] <michiel_e> in debug mode
[11:53] <apw> michiel_e, sounds like a sound plan
[11:55] <kro> michiel_e: 2.6.34-020634-generic is that your own kernel? maybe try to compare if the same thing happens with the lucid kernel?
[11:58] <apw> kro, thats a mainline 2.6.34 kernel from the archive (i suspect)
[11:59] <abogani2> Cool! The ondemand governor freezes an old P4!
[11:59] <apw> but yes, it would be good to know if the same issue appears with the stock lucid kernels as well
[12:00] <apw> abogani2, is that in the stock kernel or -rt ?
[12:00] <abogani2> apw: Stock kernel.
[12:01] <abogani2> apw, Karmic and Lucid.
[12:01] <apw> abogani2, lovely
[12:01] <apw> abogani2, so does it freeze when we switch after login ?
[12:02] <abogani2> apw: No. Randomly.
[12:02] <apw> abogani2, not helpful, does it panic or just lock up hard
[12:03] <abogani2> apw: Very hard lock up. No Sysreq keys works, Only removing the battery.
[12:03] <apw> abogani2, woh, well i can only really say i've not heard of that before
[12:04]  * abogani2 too
[12:04] <apw> it is likely that freq control is different on P4 so i could imagine it being only broken there and few people even have them to notice now
[12:04]  * abogani2 agrees
[12:04] <apw> abogani2, i assume if you leave it in performance everything is fine?  other that it being a bad idea
[12:04] <abogani2> apw: After a week it still runs.
[12:05] <abogani2> No freeze at all.
[12:05] <abogani2> No useful log neither through network nor through serial.
[12:06] <abogani2> So a sort of magic :-)
[12:06] <abogani2> apw: It is P4 _*_Mobile_ *_
[12:08] <amitk> cooloney: thanks for the sbuild write
[12:08] <amitk> up
[12:10] <michiel_e> apw, same issue appears with stock kernel as well
[12:10] <michiel_e> apw, which do you like I debug, 2.3.34-* (which is indeed from ppa archive) or the stock?
[12:15] <cooloney> amitk: no problem, man. I think it is a good benchmark for our hardware machine.
[12:16] <cooloney> amitk and apw, it still took me 3 hrs to build the whole package.
[12:16] <cooloney> my server is not so powerful
[12:16] <amitk> cooloney: 3 hrs is still better than 7 hr on buildd and then fail :)
[12:17] <cooloney> amitk: aha, yeah, much better. 
[12:24] <apw> michiel_e, likely matters not if the issue is in both
[12:25] <apw> abogani2, hrm
[12:26] <apw> cooloney, yeah and we'll get that put up on emerald once its rebuilt
[12:26] <apw> amitk, bah he has gone
[12:26] <abogani2> apw. I'm about to disable ACPI_CPUFREQ and enable P4 CLOCKMODE instead.
[12:26] <apw> was going to say, and if its a local build you can 'continue it' by
[12:27] <apw> removing the build stamps
[13:38] <michiel_e> there is in the boot process something running /sbin/poweroff
[13:38] <michiel_e> that's why it crashes
[13:38] <michiel_e> saw it with ps aux
[13:38] <michiel_e> although no parent process so hard to trace currently
[13:39] <michiel_e> maybe still the mountall bug
[13:50] <smb> Hm, somehow calling poweroff sounds like some sort of thermal emergency action. Unfortunately I am missing the details but I thought machine check events might be involved. On the other hand I don't see why things should be different in recovery mode (if there are no special options for the kernel in /boot/grub/grub.cfg). And in mine there only seems to be single instead of quiet splash...
[13:53] <soren> ls -l
[13:54] <soren> Yeah, that'll work :(
[13:56] <smb> soren, It better does not. :)
[14:03] <crocket> HI
[14:03] <jessicaNatalie> hello guys. i am trying to recompile the ubuntu kernel because i need to add support to toshiba laptops. I cant find this option when make menucofig. some help please
[14:04] <crocket> I want to file a bug report about recognition of my laptop keyboard by linux kernel.
[14:04] <crocket> All versions of linux kernel don't recognize my LG E300 built-in laptop keyboard.
[14:04] <crocket> It is a known problem.
[14:04] <crocket> But there is no relevant bug report as far as I know.
[14:04] <crocket> Where should I file a bug report about this?
[14:05] <michiel_e> /sbin/poweroff -fp
[14:05] <michiel_e> where the heck does that come from?
[14:05] <michiel_e> it has no parent process
[14:05] <Conficker-> bagaimana cara mendapatkan shell ya ?
[14:05] <Conficker-> yes how do I get a shell ?
[14:06] <crocket> michiel_e, "dpkg -S /sbin/poweroff" says it is included in upstart package.
[14:06] <crocket> Conficker- : Is that english?
[14:06] <michiel_e> this is my process list http://pastebin.com/neRdDPyi
[14:06] <michiel_e> ah ok
[14:07] <JFo> jessicaNatalie, what sort of support?
[14:07] <crocket> michiel_e, problem solved?
[14:07] <crocket> Somebody tell me about my problem
[14:07] <michiel_e> crocket, not yet, I need to find out why it's running poweroff
[14:07] <crocket> michiel_e, What's running it?
[14:08] <Conficker-> I could not ask for his shell ?
[14:08] <michiel_e> crocket, I think upstart, but not shure
[14:08] <jessicaNatalie> JFo i mean, i am runnig toshset  and i am receiving this message "required kernel toshiba support not enabled."
[14:08] <michiel_e> crocket, no parent process
[14:08] <JFo> interesting, where do you see that jessicaNatalie?
[14:09] <crocket> michiel_e, Does it appear no matter how many times you reboot?
[14:09] <JFo> crocket, I'm not sure what you mean by where should you file it/
[14:09] <jessicaNatalie> JFo: in console, when executing toshset
[14:09] <crocket> I think of filing a bug in bugzilla.kernel.org
[14:09] <crocket> I don't know which section of bugzilla.kernel.org I should file a bug in.
[14:10] <jessicaNatalie> JFo the truth is that i am doing this because i am having a very weird behavior in this laptop: when i boot ubuntu, the cooler is always off, unless I put the laptop to sleep and awake it again...
[14:11] <JFo> so the fans aren't working?
[14:11] <JFo> hmmm
[14:11] <Conficker-> why ?
[14:11] <JFo> jessicaNatalie, do you have a bug I can take a look at?
[14:11] <Conficker-> woy tahede
[14:12] <jessicaNatalie> JFo a bug? you can look at all you want, but no idea what you mean... some log file or something?
[14:13] <michiel_e> crocket, it appears al the time, but not in recovery mode
[14:13] <michiel_e> crocket, I think upstart is just running /etc/rc0.d/halt or something
[14:13] <michiel_e> crocket, but not sure though
[14:13] <JFo> nou, I mean have you filed one that I can look at and provide the team to work on?
[14:13] <JFo> jessicaNatalie, ^
[14:13] <crocket> michiel_e, it doesn't have to be upstart that's running poweroff -fp
[14:14] <michiel_e> crocket, indeed it doesn't
[14:14] <michiel_e> crocket, maybe fgrep would give me some info
[14:14] <jessicaNatalie> JFo mmm no i havent... sorry for my ignorance
[14:14] <JFo> no problem :)
[14:15] <JFo> I just need one before we can start looking at the problem in-depth
[14:15] <JFo> jessicaNatalie, mind filing one?
[14:15] <jessicaNatalie> JFo I understand. So i will do it
[14:15] <jessicaNatalie> thanks a lot!
[14:16] <JFo> jessicaNatalie, my pleasure :)
[14:17] <JFo> Conficker, I'm not sure I understand what your questions are?
[14:17] <JFo> do you have a bug i can look at?>
[14:19] <JFo> crocket, I know you probably have already, but did you search against the kernel bugzilla for your laptop model to see if someone has already filed something?
[14:20] <crocket> JFo : I just checked and nobody reported such a bug.
[14:20] <JFo> ok
[14:20] <crocket> What section of bugzilla.kernel.org should I file a bug report in?
[14:21] <JFo> not sure what you mean by section
[14:22] <crocket> There is no section assigned to keyboards.
[14:22] <JFo> ah, right
[14:22] <crocket> I mean
[14:22] <crocket> a category
[14:22] <crocket> There is no category assigned to keyboards.
[14:23] <JFo> I think those are some sort of internal USB keyboard oddity from my conversation with smb
[14:24] <JFo> are you able to run lsinput crocket?
[14:24] <jessicaNatalie> JFo one last question: do you know where is this toshiba support option when recompiling the kernel???? I am sure I have seen it, but cant find it now... :)
[14:25] <crocket> JFo : Is it a command?
[14:25] <JFo> jessicaNatalie, I don't, unfortunately
[14:25] <JFo> crocket, yes
[14:25] <crocket> JFo : are you a kernel developer?
[14:25] <JFo> crocket, do you have an LP bug open?
[14:25] <JFo> crocket, I'm the bug triager
[14:25] <crocket> What's an LP bug?
[14:26] <jessicaNatalie> JFo mmm all right... I continue looking for it. thanks a lot!
[14:26] <JFo> launchpad bug
[14:26] <JFo> jessicaNatalie, my pleasure
[14:26] <crocket> JFo : I filed that bug somewhere in launchpad years ago, but nobody cared.
[14:26] <JFo> ah
[14:26] <crocket> Maybe it was a wrong place to file a report.
[14:26] <JFo> no it is, there are just so many that get opened
[14:26] <crocket> I think bugzilla.kernel.org is the right place
[14:27] <JFo> crocket, is the keyboard detected at all?
[14:27] <crocket> or better
[14:27] <JFo> is it misbehaving?
[14:27] <crocket> Let me pastebin for you
[14:27] <JFo> ok
[14:27] <crocket> I already have a USB keyboard plugged in.
[14:28] <JFo> I see
[14:28] <crocket> An external USB keyboard works.
[14:28] <JFo> but the internal doesn't at all?
[14:28] <crocket> JFo, http://pastebin.org/288193 <-- the result of lsinput
[14:28] <crocket> I don't know how to interpret the result.
[14:29] <crocket> There are some USB devices that don't have human-readable names.
[14:29] <crocket> "AT Translated Set 2 keyboard" may be the external USB keyboard.
[14:29]  * JFo looks
[14:30] <smb> No that seems to be the internal one
[14:30] <crocket> smb : do you think "AT Translated Set 2 keyboard" is the internal keyboard?
[14:30] <smb> Its connected to the i8042 controller, which is usually the internal one
[14:30] <crocket> Damn
[14:30] <smb> It might be that hid device
[14:31] <smb> #
[14:31] <smb> /dev/input/event6
[14:31] <smb> #
[14:31] <smb>    bustype : BUS_USB
[14:31] <smb> #
[14:31] <smb>    vendor  : 0x566
[14:31] <crocket> If I add "i8042.nopnp i8042.dumbkbd" in kernel boot parameters of GRUB, the keyboard works, but Num Lock and Caps Lock toggle LEDs don't blink at all, so I can't check the status of Caps Lock and Num Lock.
[14:31] <smb> #
[14:31] <smb>    product : 0x3002
[14:31] <smb> #
[14:31] <smb>    version : 272
[14:31] <smb> #
[14:31] <crocket> smb : don't flood man
[14:31] <smb>    name    : "HID 0566:3002"
[14:31] <smb> #
[14:31] <smb>    phys    : "usb-0000:00:13.0-2/input0"
[14:31] <smb> #
[14:31] <smb>    uniq    : ""
[14:31] <smb> #
[14:31] <smb>    bits ev : EV_SYN EV_KEY EV_MSC EV_LED EV_REP
[14:31] <smb> gah
[14:31] <JFo> hmmm
[14:31] <smb> my bad
[14:31] <JFo> wonder why it doublespaced
[14:32] <crocket> JFo : How come does it get recognized and not work at all?
[14:32] <JFo> crocket, good question
[14:32] <smb> well, that points to that that
[14:32] <JFo> I'm not sure
[14:32] <crocket> ha
[14:32] <JFo> the HID device smb?
[14:32] <smb> The driver might try to communicate with it and fail at some point
[14:33] <smb> I believe that is the usb keyboard
[14:33] <crocket> i8042.nopnp & i8042.dumbkbd kernel options make it work
[14:33] <smb> lsusb could verify that
[14:33] <smb> mus be some device at 00:13.0-2
[14:33] <JFo> crocket, mind running lsusb for us?
[14:34] <JFo> more for smb than for me :)
[14:34] <crocket> This is the result of sudo lsusb ---> http://pastebin.org/288208
[14:35] <crocket> Why do I have to specify i8042.nopnp and i8042.dumbkbd?
[14:35] <crocket> I didn't have those options myself. Others found them for me.
[14:35] <smb> I need to check with those options
[14:35] <smb> But my guess is
[14:35] <smb> that the keyboard has some special ps2 protocol extensions variations
[14:36] <crocket> smb : In windows vista, it's recognized as a PS2 keyboard.
[14:36] <smb> and by telling it to use sumkbd the used commands on the protocol are more generic and simpler
[14:36] <crocket> What driver should I install?
[14:36] <crocket> or put in kernel?
[14:37] <smb> the driver is in the kernel. i8042, its just that this keybard might need special treatment by it
[14:37] <smb> dumbkbd: Do not try to control the state leds
[14:38] <smb> crocket, Have you once tried with only nopnp?
[14:38] <Kano> hi, could somebody add rt3090.bin
[14:38] <smb> I mean i8042.nopnp
[14:38] <crocket> smb : I tried, but don't remember the result now.
[14:38] <Kano> rt3071.bin is missing too
[14:38] <Kano> http://packages.debian.org/sid/firmware-ralink
[14:39] <Kano> there it is already packaged
[14:39] <crocket> I hate LG laptops.
[14:39] <smb> From the docs the nopnp does not do any plug and play to detect the keyboard, I assume it brute force looks at the common io ports
[14:39] <crocket> I called LG today, and the engineer there said no LG laptops have 64bit OS.
[14:39] <smb> The other option will prohibit any commands that control the leds
[14:40] <mjg59> The kernel will do that anyway if there's no pnp devices described
[14:40] <smb> So no blinking, and so on
[14:40] <crocket> no blinking, dumb keyboard
[14:40] <mjg59> But Windows depends upon there being something in the PNP tables, so if the keyboard appears in Windows, requiring nopnp is a Linux bug
[14:40] <pgraner> ***Notice*** All kernel team members, emerald is about be shutdown for upgrades at the top of the hour. Let me know if you need anything off of it. Thanks
[14:40] <crocket> Is it a common practice to build a PS2 keyboard in laptops?
[14:41] <mjg59> Yes
[14:41] <crocket> pgraner : your english is confusing.
[14:41] <smb> I have not yet seen anything else
[14:41] <mjg59> The only people who don't are Apple
[14:41] <smb> mjg59, you?
[14:41] <smb> Ah ok, apple
[14:41] <pgraner> crocket: how so?
[14:41] <crocket> Why do other laptops' PS2 keyboards work fine?
[14:42] <crocket> pgraner : "about to be shut down" may be correct, but I don't know what you tried to say.
[14:42] <crocket> pgraner, Plus, emerald is a windows manager of compiz fusion.
[14:42] <smb> crocket, To talk to it the ps2 protocol is used. You can make hardware that strictly uses the standard or not...
[14:43] <pgraner> crocket: sorry if it confused you it was meant for the kernel team members, and emerald is our build server
[14:43] <crocket> smb : what do you mean?
[14:43] <smb> mjg59, Do you know of your head what category bz uses for the input layer
[14:44] <crocket> pgraner, you just send commands to the server and the server build it?
[14:44] <crocket> What's bz?
[14:44] <pgraner> crocket: this is an internal canonical server
[14:44] <smb> crocket, You tell pgraner his english is strange. The same can happen on a protocol
[14:44] <smb> crocket, buzilla
[14:44] <crocket> ha
[14:44] <smb> bugzilla
[14:45] <crocket> What category in bugzilla should I file a bug report in?
[14:45] <crocket> I want the right people to see this
[14:45] <crocket> This is as nasty as a real bug.
[14:46] <apw> crocket, if those options you mentioned make it work, then a linux bug is appropriate
[14:46] <apw> and make sure the report has that information in it
[14:46] <crocket> Not just LG E300 but also Dell Vostro 1510, and other external PS/2 keyboards and mice don't work either.
[14:47] <smb> crocket, I would boot with the usb keyboard attached, without nopnp and dumbkbd but with i8042.debug=1
[14:47] <crocket> smb : And where's the debug information?
[14:47] <crocket> how can I extract it into a text file?
[14:47] <mjg59> smb: Not off-hand, sorry
[14:47] <smb> then use dmesg  >dmesg.log and atach that file
[14:47] <crocket> dmesg would print logs that date back to days or even weeks.
[14:48] <crocket> I need to narrow it down to the last boot.
[14:48] <smb> crocket, no dmesg is in memory
[14:48] <crocket> ok
[14:48] <smb> so only things since boot
[14:48] <crocket> I just saw dmesg log file and it was way too large
[14:48] <crocket> I thought it was cumulative
[14:48] <smb> its a ring buffer in memory
[14:49] <crocket> smb : Does it change even after I log in gdm?
[14:49] <smb> crocket, yes
[14:49] <crocket> smb : tell me the category where I should file a bug report.
[14:49] <smb> Its the kernel log, it always changes as long as your machine is running
[14:50] <crocket> I also posted a bug report in bugzilla
[14:50] <crocket> https://bugzilla.kernel.org/show_bug.cgi?id=16065
[14:50] <ubot2> bugzilla.kernel.org bug 16065 in Video(Other) "linux 2.6.34 keeps ranting that it can't retrieve EDID from my old LCD monitor." [Normal,New]
[14:51] <crocket> what?
[14:51] <crocket> Are you the smart bot?
[14:51] <crocket> smb : Do you have no clue as to what category?
[14:52] <JFo> we are looking now
[14:52] <crocket> The severity must be "blocking"
[14:53] <crocket> Since it paralyzes the computer completely.
[14:53] <smb> crocket, I thing cat is drivers but not blocking
[14:53] <smb> blocking would mean your project is blocked
[14:54] <crocket> smb : You should look at the severity dropdown box.
[14:54] <crocket> bugzilla.kernel.org -> New -> Severity
[14:55] <smb> I see it, still blocking is the highest severity
[14:55] <smb> crocket, you are not on fire, are you?
[14:56] <crocket> If I was out without usb keyboard, I would be.
[14:56] <crocket> ok
[14:56] <crocket> Then I set it high
[14:57] <crocket> Nobody seems to be looking
[14:57] <smb> crocket, I would leave it at normal
[14:58] <crocket> Why? It's a source of frustration for lots of people.
[14:58] <crocket> Some would even think linux just doesn't work at all on their computers and abandon it.
[14:58] <crocket> I was about to abandon linux when it happened.
[14:58] <crocket> Normal problems should be something like https://bugzilla.kernel.org/show_bug.cgi?id=16065.
[14:59] <ubot2> bugzilla.kernel.org bug 16065 in Video(Other) "linux 2.6.34 keeps ranting that it can't retrieve EDID from my old LCD monitor." [Normal,New]
[14:59] <crocket> Linux keeps ranting, but I don't have to deal with it since it doesn't penetrate X window session and keeps ranting.
[15:00] <crocket> dmesg is severely ridden with no EDID error messages.
[15:00] <apw> crocket, there are many many bugs, 'my' bug isn't always the most severe that upstream has to look at.  i had my machine overheating for 3 months till i had time to fix it
[15:01] <crocket> apw, what now?
[15:01] <amitk> lag: great improvement idea to editconfigs. :)
[15:01] <apw> lag, i think the layout of the change is a little odd and we can improve it, but the idea seems ok
[15:02] <lag> amitk, apw: It doesn't work yet, but I'm working on it
[15:02] <lag> I thought it did, but I came across problems
[15:02] <apw> lag, i think you call out of the outer for arch in arch loop for editconfigs and run a for arch in arch loop in the function and exit
[15:02] <apw> that seems odd.  i think you should just check before the outer loop
[15:03] <apw> and go off into your function
[15:04] <amitk> isn't it scary I actually understood this: "call out of the outer for arch in arch loop for editconfigs and run a for arch in arch loop in the function "
[15:04] <crocket> smb, I have two candidate categories. One is IO/storage -> other and the other is Other -> other.
[15:04] <lag> I exit too early
[15:04] <smb> crocket, rather other
[15:04] <lag> And don't do any of the code after the final arch loop
[15:04] <crocket> other -> other?
[15:05] <smb> crocket, input devices might be another candicdate, but sthey seem to only think of mice there
[15:05] <crocket> all right.
[15:05] <crocket> Then it's other -> other.
[15:05] <crocket> I shoud reboot with i8042.debug=1 now.
[15:11] <lag> apw: With regards to your arch stuff, that should be fine. It will just over-write the variable. This isn't a problem, as it's not used again.
[15:16] <apw> yeah but its rather ugly flow wise
[15:16] <apw> anyhow when you've reworked it and got it working i'll have anohter look
[15:16] <lag> apw: No probs
[15:16] <apw> in my mind i see you adding a preloop which asks which to do and which to skip
[15:17] <apw> and use that result in the inner loop to skip running menuconfig for the ones we don't want
[15:17] <apw> and leave the remainder of the processing in place and untouched
[15:17] <apw> and to a large degree the split processing relies on all the configs being generated, even if in some cases you do not touch them
[15:18] <apw> lag^^
[15:18] <lag> apw: ack
[15:22] <smb> tgardner, Have you already worked through your mail to my mail about compat-wireless-2.6.34 in lucid?
[15:23] <tgardner> smb, I'm just looking at it now. it looks like I kinda screwed the pooch.
[15:24] <smb> tgardner, It smelled like that. But good to know youre on it
[15:27]  * cking wrestles with his PPA
[15:30] <apw> cking, always fun
[15:30] <crocket> hi
[15:30] <apw> anyone know what in userspace might be touching the CPUFREQ, someone with kubuntu is reporting this error being tripped:
[15:30] <apw> CPUFREQ: Per core ondemand sysfs interface is deprecated - up_threshold
[15:30] <crocket> I just posted a new kernel bug report --- > https://bugzilla.kernel.org/show_bug.cgi?id=16069
[15:30] <crocket> https://bugzilla.kernel.org/show_bug.cgi?id=16069
[15:30] <ubot2> bugzilla.kernel.org bug 16069 in Other "All versions of linux don't recognize LG E300 laptop built-in PS/2 keyboard." [High,New]
[15:31] <apw> crocket, add the link to the launchpad bug, then it will get tracked
[15:32] <crocket> apw, Actually I didn't file a bug report in launchpad, but somebody else did.
[15:32] <crocket> I posted the report in ubuntu forum.
[15:32] <apw> JFo, i have a bug which is not a linux bug but i have no idea yet where the bug belongs
[15:33] <apw> JFo, do we have (or should we have) a tag like kernel-not-kernel which is for bugs we should be trying to get rid of ?
[15:33] <JFo> we don't but we should apw
[15:33] <JFo> got the bug number
[15:33] <JFo> ?
[15:33] <apw> JFo, kernel-not-kernel smacks of captain-my-captain and therefore appleas
[15:33] <JFo> heh
[15:34] <JFo> works for me
[15:34] <apw> bug #585747
[15:34] <ubot2> Launchpad bug 585747 in linux (Ubuntu) "CPUFREQ: Per core ondemand sysfs interface is deprecated - up_threshold (affects: 1) (heat: 6)" [Medium,Triaged] https://launchpad.net/bugs/585747
[15:34] <apw> its possible a patched kernel could tell us which process triggered the issue
[15:34] <apw> but till then we have little to go on, unless someone just knows
[15:34] <JFo> hmmm
[15:35] <apw> JFo, i am liking the kernel-<subsystem> kernel-need-review process, lets me nibble at it
[15:37] <JFo> yep, I think it will work well
[15:37] <JFo> you always have the same place to go for things and the list is dynamic
[15:37] <JFo> so there is minimal work to maintain it
[15:37] <apw> even though i am reviewing two categories, its just two quick clicks from the Tagging page
[15:40] <lag> apw: Do you know who wrote this script in the first place?
[15:45] <JFo> smb, do you know if we are pulling the ATI 10.5 drivers into Lucid as SRU?
[15:45] <JFo> I have a bug that it seems to fix several people in
[15:45] <JFo> bug 574848
[15:45] <ubot2> Launchpad bug 574848 in linux (Ubuntu) "Suspend-Resume Regression in 10.04 on Dell Studio 1555 with Radeon HD 4500 (affects: 25) (dups: 1) (heat: 154)" [Undecided,Confirmed] https://launchpad.net/bugs/574848
[15:46] <amitk> mpoirier: regarding your email...
[15:47] <smb> JFo, Pulling in complete driver replacements sounds rather unlikely for SRU ... But I don't know for real
[15:47] <amitk> mpoirier: versatile is a different kernel flavour, nothing to do with omap
[15:47] <mpoirier> amitk: hello
[15:47] <mpoirier> amitk: ok will stay way - what is it for ?
[15:47] <manjo> JFo, HBD!
[15:47] <JFo> thanks manjo :)
[15:48] <amitk> mpoirier: as kernel for an arm qemu environment (used for test building, rootstrapping, etc.)
[15:48] <mpoirier> amitk: ok, will definitely stay away.
[15:48] <amitk> mpoirier: well, it is useful at time
[15:48] <mpoirier> amitk: how about udeb files ?
[15:48] <amitk> s
[15:49] <JFo> apw, the PPC port is no longer supported? or am i wrong?
[15:49] <amitk> mpoirier: use Bryan's newly posted instructions to the wiki regarding sbuild to build the udebs
[15:49] <JFo> I wonder if we need to change arsenal scripts to detect PPC bugs
[15:49] <amitk> (you can subscribe to wiki pages)
[15:51] <mpoirier> amitk: what is the link to Bryan's wiki ?
[15:53] <amitk> mpoirier: http://wiki.ubuntu.com/KernelTeam/KernelMaintenanceStarter?action=diff&rev1=49&rev2=50
[15:53] <amitk> you should subscribe to all pages under KernelTeam
[15:54] <mpoirier> Ok, I'll read his page.  
[15:54] <mpoirier> yes, I'll subscribe - thanks.
[15:54] <JFo> amitk, hopefully those pages will be moving over to Kernel/ soon
[15:54] <JFo> so they will become archived
[15:54] <amitk> JFo: right
[15:55] <amitk> once we can break up kernel building into smaller steps
[15:56] <bjf> mpoirier, to subscribe to all kernel wiki pages (even ones that don't exist yet) follow the "user preferences" link on any wiki.ubuntu.com page
[15:57] <mpoirier> bjf: very well thanks.
[15:57] <bjf> mpoirier, there is a "Subscribed wiki pages" box towards the bottom that will take regular expressions
[15:58] <bjf> mpoirier, I have ".*KernelTeam.*" as one of my regexes
[15:58] <mpoirier> bjf: let me look at it and I'll get back to you if need be.
[16:03] <apw> JFo, ppc is now a 'ports' kernel, which as i understand things means its a community effort
[16:03] <apw> that said we do maintain the config for it in lucid and later
[16:03] <JFo> I see
[16:03] <JFo> hmmm
[16:09] <ogasawara> JFo: will we have a bug call Monday?  Just curious since it's a holiday for US.
[16:09] <JFo> ooh, good point
[16:09] <JFo> I'd rather not in that case :-P
[16:10] <ogasawara> JFo: heh, I'd rather sleep in :)  but I can make the call if you have it.
[16:10] <JFo> nah, I want to sleep too
[16:10] <JFo> I think we should reschedule though
[16:10] <JFo> can we fit it into Tuesday?
[16:11] <ogasawara> JFo: I could do tues
[16:11] <JFo> cool
[16:11] <JFo> apw, cool with a Tuesday bug call?
[16:11] <JFo> err apw smb manjo et Al that is
[16:11] <JFo> cnd ^^
[16:11] <manjo> JFo, yeah I am 
[16:11] <JFo> cool
[16:13] <apw> JFo, monday is a holiday in the UK also 
[16:13] <JFo> cool, Tues good for you?
[16:13]  * apw reminds you that the weekly #u-m meeting is then
[16:35] <cnd> JFo: as long as it's not 10-11 am EDT
[16:36] <JFo> right, wasn't planning on munging the meeting time
[16:36] <JFo> is it ok to do it after?
[16:41] <cnd> JFo: sure
[16:41] <bencer> hi all, i was using custom-binary flavours to build a patched kernel with hardy, now i'm trying to upgrade this package to lucid but seems that custom-binary are not used anymore, do i have to build my own source package like linux-rt or linux-ec2 ?
[16:42] <smb> bencer, yes. If  you look at the git repo and there at the ec2 branch this shows how this is relatively simply being done
[16:43] <bencer> smb: ubuntu linux packaging git repo ?
[16:44] <bencer> http://kernel.ubuntu.com/git-repos/ubuntu/ubuntu-lucid.git
[16:44] <smb> The lucid kernel repo gti://kernel.ubuntu.com/ubuntu/ubuntu-lucid.git
[16:44] <smb> bencer, yep the same
[16:45] <smb> s/gti/git/
[16:47] <bencer> smb: do you have any documentation on the workflow you follow ? or just the usual git packaging
[16:47] <smb> bencer, trying to find something...
[16:48] <smb> bencer, Hope this helps https://wiki.ubuntu.com/KernelTeam/AbstractedDebian
[16:49] <smb> bencer, There might be slight deviations from when that was written, but hopefully still accurate enough
[16:58] <pgraner> apw: https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/502433
[16:58] <ubot2> Launchpad bug 502433 in linux (Ubuntu) (and 1 other project) "Lucid: b43 fatal DMA error on Dell Mini 9 (affects: 23) (heat: 146)" [Medium,Triaged]
[17:26] <JFo> <-need food brb
[17:29]  * manjo lunch
[18:01] <blue_anna> Can someone help me with the em28xx kernel module on lucid ?
[18:02] <blue_anna> the version of the module packaged in lucid is a few years old apparently, and only in the ones in the apst 3 years does it support my card
[18:02] <blue_anna> but the em28xx module doesn't compile on my system http://pastebin.ws/a020d9 -- I get those errors following instructions specifically for lucid
[18:03] <blue_anna> http://odracirls.blogspot.com/2010/04/compilacion-y-instalacion-drivers.html
[18:03] <blue_anna> I downloaded the em28xx source from launchpad just to be sure, and no, my card is not in there. only in the ones since 2007
[18:05] <blue_anna> I'm thinking maybe I need to rebuild the kernel with i2c support modularized. but I don't entirely feel comfortable doing that -- its been agood while since I did a kernel compile by myself
[18:05] <blue_anna> and then I'm alsooo going to have to rebuild the kernel again in a few months when 10/10 comes around
[18:10] <bjf> mpoirier, https://edge.launchpad.net/ubuntu/+filebug
[18:11] <ogasawara> mpoirier, bjf:  note that will file the bug against ubuntu as a whole, if you want it package specific, eg linux, https://edge.launchpad.net/ubuntu/+source/linux/+filebug
[18:12] <bjf> ogasawara, thanks
[18:12] <apw> ogasawara, i thought that page had the package box on it
[18:12] <blue_anna> are kernel modules discussed here?
[18:12] <bjf> apw, it does eventually ask which package to file against
[18:13] <blue_anna> or just the monolithic part of the kernel
[18:13] <ogasawara> bjf, apw: yah, I think it eventually asks, but most don't know so don't put anything and it gets lost in the black hole of bugs filed against ubuntu
[18:13] <pgraner> blue_anna: all matters kernel are discussed here
[18:13] <apw> ogasawara, heh yeah i bet
[18:14]  * BenC wonders if he will be accepted for ubuntu-kernel-team membership
[18:14] <ogasawara> BenC: heh, you're not already a member?
[18:14] <BenC> ogasawara: I was surprised as well :)
[18:14] <tgardner> BenCI'll bet it expired
[18:15] <pgraner> BenC: ask tgardner he can do it
[18:15] <BenC> probably, I only barely saw the notice of my ubuntu-core-dev membership about to expire
[18:15] <blue_anna> pgraner: do you think you could help me with my question just a minute ago? I'm in need of some help with it from someone who has some familiarity with the ubuntu kernel in 10.04
[18:16] <ogasawara> blue_anna: just ask what you're wanting, if someone knows the answer they'll speak up
[18:16] <pgraner> ogasawara: its there in the scroll back
[18:16]  * ogasawara scrolls back
[18:16] <pgraner> ogasawara: we seem to have an old em28xx module
[18:16] <BenC> blue_anna: just comment out the line in that file that sets i2c_driver.id
[18:17] <BenC> should work
[18:17] <BenC> blue_anna: line 728 in em28xx_i2c.c
[18:17] <pgraner> ogasawara: what did we decide with the em28xx module for M? is it getting updated?
[18:18] <ogasawara> pgraner: I don't think we discussed it so I'd assume it's not getting updated
[18:18]  * pgraner was nodding off in ogasawara's riveting  kernel delta session
[18:18] <BenC> blue_anna: and setting LANG=C would go a long way to getting help from en speaking ppl :)
[18:18] <pgraner> ogasawara: we might need to look if its indeed that old
[18:19] <bjf> ogasawara, pgraner looks like we have what is currently upstream
[18:19] <blue_anna> BenC: sorry :P what in that make output wasn't in english anyway ?
[18:19] <pgraner> bjf: then whats blue_anna talking about then?
[18:19] <BenC> make[1]: se ingresa al directorio `/home/roberto/Código/em28xx-new.de_launchpad/em28xx-new'
[18:19] <bjf> pgraner, this driver seems to have a sordid past, disagreements between maintainers
[18:19] <BenC> blue_anna: it didn't hurt in this case, but just a good note
[18:20] <blue_anna> BenC: ooh ..ok -- I don't even see the make steppings output anymore, my mind just skips straight to the compiler :)
[18:20] <BenC> tgardner: thanks
[18:20] <bjf> pgraner, not sure what version blue_anna is trying to get to work or where they got it from
[18:20] <tgardner> BenC: np
[18:21] <blue_anna> BenC: 	if (client->driver->id == I2C_DRIVERID_TUNER && dev->has_inttuner == 1) { -- that's line 728
[18:21] <BenC> blue_anna: if (dev->has_inttuner == 1) {
[18:22] <BenC> blue_anna: no guarantee, but try that
[18:22] <blue_anna> bjf: I have both versions on my system in source right now .. em28xx from launchpad, that's the current version , you know? .. that works just fine
[18:22] <blue_anna> bjf: and em28xx-new, from 2007
[18:22] <blue_anna> bjf:  that's the version that supports my card
[18:22] <BenC> blue_anna: id may be embedded elsewhere, so that might not work correctly
[18:23] <bjf> blue_anna, i'll look at launchpad
[18:23] <blue_anna> it really trips me out that the instructions in em28xx-new go out of their way to say that this works for lucid, and it doesnt :)
[18:23] <BenC> if em28xx-new still has problems with the i2c_device.id change, then it's not really maintained either
[18:23] <blue_anna> bjf: well you can look there but that's not where there is an issue -- here let me get you the grep you'll need
[18:24] <BenC> that change in the i2c subsystem is years old
[18:24] <bjf> blue_anna, no, i want to look at the one in LP, you are saying the one we carry is very old
[18:25] <blue_anna> bjf: yeah
[18:26] <blue_anna> bjf: here, this is the USB_DEVICE line that was added in 2007: { USB_DEVICE(0x1d2c, 0x1012), .driver_info = EM2883_BOARD_EQUINUX_TUBESTICK_ATSC }
[18:26] <bjf> blue_anna, do you have a link to the one in launchpad?
[18:26] <blue_anna> thats in em28xx-cards.c
[18:26] <BenC> blue_anna: if all you need is a new device line, I suggest just adding that to the current driver...maybe that will work
[18:27] <pgraner> bjf: http://launchpadlibrarian.net/35049921/em28xx-new.tar.gz
[18:27] <blue_anna> BenC: I tried, that's not defined in the .h either so I'd have to hack all the functionality into the driver
[18:28] <bjf> pgraner, thanks
[18:28] <blue_anna> bjf: hg clone http://linuxtv.org/hg/v4l-dvb I think should work
[18:29] <blue_anna> I just canned my history and the only em28xx I have from launchpad is the em28xx-new that doesnt compile: wget http://launchpadlibrarian.net/35049921/em28xx-new.tar.gz
[18:29] <blue_anna> so I must have clsoed my term before that
[18:29] <blue_anna> ** scanned
[18:30] <blue_anna> I *think* the problem with the em28xx not compiling is because i2c-core is not a module in 10.04
[18:30] <blue_anna> it's monolithic
[18:31] <BenC> blue_anna: no, that's not the problem
[18:31] <BenC> blue_anna: I just looked at the source, make the change that I suggested and it should work
[18:31] <bjf> blue_anna, the reason lucid is "older" is because none of that code has made it upstream
[18:31] <bjf> blue_anna, i suggest trying what BenC is telling you
[18:32] <blue_anna> bjf:  I just found a bug about this: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/489353
[18:32] <ubot2> Launchpad bug 489353 in linux (Ubuntu) "em28xx-new should be added to repository (affects: 1) (heat: 8)" [Medium,Confirmed]
[18:32] <blue_anna> I didnt know I wasn't the only one :) I?ve been trying to get help on ubuntu forums and #ubuntu for the past month :P
[18:33] <blue_anna> I'll consider it a crash course in ubuntu from the dev-side :)
[18:33] <BenC> blue_anna: after I made that change, the driver(s) compiled just fine
[18:33] <BenC> with no errors in missing symbols, so it should load fine as well
[18:34] <blue_anna> BenC: I'll try it :) thank you
[18:34] <blue_anna> I'm just worried that that will change the functionality quite a lot .. but still, it's completely worth it to try
[18:34] <vanhoof> JFo: happy birthday :)
[18:35] <JFo> thanks vanhoof :)
[18:35] <JFo> I feel old
[18:35] <BenC> blue_anna: it does not change it at all for you, since your device doesn't define has_inttuner, so that whole if statement is a no-op anyway
[18:36] <vanhoof> JFo: another year wiser ;)
[18:36] <JFo> I need more wisdom than one year alone could impart :)
[18:36] <blue_anna> BenC: :) lolo , that works for me
[18:38] <blue_anna> BenC: it compiles! and loads,  but it is misbehaving when I plug in the usb device: http://pastebin.ws/ahv11z
[18:39] <blue_anna> BenC: and you were right about what you said before so that's a different problem in the driver :P
[18:39] <BenC> blue_anna: you have some mix-matched modules being loaded
[18:39] <BenC> blue_anna: make sure to install all the drivers from your build (./build.sh install)
[18:40] <blue_anna> it did
[18:40] <BenC> I would reboot then
[18:40] <blue_anna> sudo make install said "running ./build.sh install"
[18:40] <BenC> or manually unload all the modules
[18:40] <blue_anna> ooo yeah
[18:40] <blue_anna> good idea
[18:40] <blue_anna> :) lol -- thank BenC, wish me luck
[18:40]  * BenC holds his breath
[18:43] <BenC>         #FIXME Why not just do make install here?
[18:43] <BenC> the build script makes a good point...
[18:44] <apw> heh ... don't you just love those sorts of comments
[18:45] <BenC> and I feel sorry for blue_anna because that build.sh install just rm -rf'd a lot of stock modules from his system...hopefully nothing important
[18:45] <BenC> s/his/their/
[18:45] <apw> real name was roberto ... 
[18:46] <blue_anna> BenC: same errors on boot :S
[18:47] <BenC> blue_anna: find /lib/modules/`uname -r`/ -name em28xx\*
[18:47] <blue_anna> can you explain to me your thinking on the conflicts? I want to understand why you thought that
[18:47] <blue_anna> ok, just a sec
[18:47] <BenC> blue_anna: it said it in your pastebin "disagrees about symbols"
[18:50] <BenC> blue_anna: have you built new videodev modules on your system (v4l2/video4linux2)?
[18:50] <blue_anna> BenC: http://pastebin.ws/8eprrl
[18:50] <BenC> blue_anna: or do you have any weird header conflicts?
[18:51] <blue_anna> BenC: the normal em28xx would load without these issues, just the nem28xx-new that is having troubles
[18:51] <BenC> blue_anna: I know, but what it seems to show is that the videodev modules on your system do not agree with the headers that em28xx-new was compiled against
[18:51] <blue_anna> I don't know that I built the v4l2 stuff, you can see in the output I do have some v4l loaded, which maybe is the conflict ?
[18:52] <BenC> v4l has to be loaded since em28xx uses it
[18:52] <blue_anna> my pastebin has my lsmod grepped to v4l
[18:52] <blue_anna> there is both (??) v4l and v4l2 related modules loaded
[18:53] <BenC> blue_anna: videodev is what you want to grep for
[18:53] <blue_anna> thanks, I'll grep t
[18:53] <blue_anna> *it
[18:53] <BenC> blue_anna: and more importantly can you pastebin "ls -lR /lib/modules/`uname -r`/"
[18:54] <blue_anna> that's a lot of output
[18:55] <blue_anna> waiting for my webbrowsser to recover from the paste :)
[18:55] <blue_anna> the only other videodev that loaded is videodev itself
[18:55] <BenC> right, it appears to not match your kernel headers
[18:56] <blue_anna> man that smashed firefox :P
[18:56] <blue_anna> still at 100%cpu
[18:57] <blue_anna> let me try oepra, it's less buggy
[18:58] <BenC> hehe, I guess you could just do "ls -lR /lib/modules/`uname -r`/ | grep video"
[18:58] <BenC> might be a bit easier
[18:58] <blue_anna> ok :)
[18:59] <blue_anna> http://pastebin.ws/5c08oc
[19:00] <BenC> yeah, you definitely screwed up your system
[19:00] <BenC> rm -rf /lib/modules/`uname -r`/empia
[19:00] <blue_anna> what do you mean? 
[19:00] <blue_anna> ok
[19:00] <blue_anna> htat's scary but ok
[19:00] <BenC> rm -rf /lib/modules/`uname -r`/kernel/drivers/media
[19:01] <BenC> blue_anna: you've installed a new version of v4l, which is breaking your system
[19:01] <blue_anna> that's more scary .. I'm going to move that instead
[19:01] <blue_anna> ok
[19:01] <BenC> apt-get --reinstall install linux-image-2.6.32-21-powerpc64-smp
[19:01] <BenC> then rebuild and install em28xx-new
[19:02] <blue_anna> ok, just a minute
[19:02] <BenC> blue_anna: we could have saved a ton of time if you had told me you did that
[19:02] <blue_anna> sorry, ..
[19:03] <blue_anna> .. by my mind this hasnt been a ton of time, but I told you I've been working on this for a month so, to me it would take a few days before we got there :P
[19:04] <BenC> well, by my time, we spent nearly 30 minutes tracking down a problematic symbol mis-match, and that's about 50% of the time I've spent helping you :)
[19:04] <blue_anna> I am still getting a ton of warnings 
[19:04] <blue_anna> but it built
[19:04] <BenC> modprobe -r videodev
[19:05] <BenC> then insert your usb device
[19:05] <blue_anna> çWOOOHOO!
[19:06] <blue_anna> well it loaded, and it .. I'm getting messages like the device is being attached to the driver but MeTV didnt find it .. let me post you the log
[19:07] <blue_anna> BenC: just tell me if the driver looks like it is working? I'll take on MeTv myself if it is :)
[19:07] <blue_anna> http://pastebin.ws/g8t6fw
[19:08] <BenC> blue_anna: looks good to me
[19:08] <blue_anna> BenC: thank you that's the first time in a month I made progress .. and it happened all at once :)
[19:08] <BenC> blue_anna: I'd try some basic v4l apps to see if you can get it working there before going to a specialized program
[19:08] <BenC> blue_anna: vlc/mplayer perhaps
[19:08] <BenC> blue_anna: glad I could help
[20:37] <blue_anna> is there any general way that a kernel module finds the right firmware file to load?
[20:38] <tgardner> blue_anna, request_firmware() looks first in /lib/firmware/`uname -r`, then in /lib/firmware
[20:39] <blue_anna> tgardner: thanks
[20:40] <tgardner> blue_anna, its a function of /lib/udev/firmware_helper
[22:40] <blue_anna> can anyone tell me what good em28xx-dvb is in here: wget http://launchpadlibrarian.net/35049921/em28xx-new.tar.gz
[22:41] <blue_anna> it looks like the dvb extension god garbled in this version of the source, its just a bunch of attributes now
[22:44] <blue_anna> *got
[23:33] <stenten> If I'm trying to triage someone's Kernel Oops, should I just tell them to install linux-crashdump and be done with it?
[23:34] <stenten> There's all kinds of crazy oopses in kern.log, but they're all different and I'm not sure which one is responsible for the crash.