[04:49] <proverse> I think I have a regression between 2.6.36-rc7 and -rc8 regarding wifi, not sure where to writeup the bug or what would be needed
[04:49] <proverse> anyone avail to help?
[04:52] <proverse> also what is drm-intel-next ?
[07:59] <papillon81> ikepanhc: hi, I tested ideapad-laptop. Almost all special buttons worked. what did not was the wifi/BT switch and the Play/Pause, Stop, FF, REW buttons
[08:03] <ikepanhc> papillon81: I guess the brightness/volumn control, touchpad switch, works fine
[08:04] <ikepanhc> papillon81: those key enabled because of BIOS (DSDT) or they will generate an keycode
[08:05] <ikepanhc> papillon81: they are not enabled by ideapad-laptop yet
[08:05] <papillon81> ikepanhc: yes, they work
[08:05] <papillon81> IIRC, the Camera switch is also working without ideapad-laptop
[08:05] <papillon81> ...let me check
[08:05] <ikepanhc> papillon81: ya
[08:06] <ikepanhc> papillon81: the camera key just power on/off the camera, you can try to press the key and use dmesg to check
[08:07] <ikepanhc> papillon81: usb camera will disappear and reappear
[08:10] <papillon81> ikepanhc: well, it looks like most of it works without the driver already
[08:10] <papillon81> the play/pause... keys do not as they produce no key event
[08:11] <papillon81> wifi produces an event, but no connection/disconnection happens
[08:12] <ikepanhc> papillon81: how you see the event? from dmesg which says unknown scancode?
[08:12] <papillon81> ikepanhc: yes
[08:13] <ikepanhc> papillon81: oh, some ideapad model will report scancode when hotkey pressed, but not all of the ideapad
[08:17] <papillon81> BRB
[08:34] <lag> Morning smb
[08:34] <lag> Hi ikepanhc :)
[08:34] <smb> lag, morning
[08:34] <ikepanhc> good morning .eu
[08:34] <lag> :)
[08:35] <lag> Are you packed and ready for UDS
[08:35] <ikepanhc> me? not yet
[08:36] <ikepanhc> I am used to pack 6hrs before departure
[08:36] <ikepanhc> and hope nothing missed
[08:36] <ikepanhc> s/hope/pray for/
[08:41]  * abogani waves all
[08:44] <lag> :)
[08:54]  * apw waves to ikepanhc 
[08:55] <apw> ikepanhc, can you point me to the oem public trees
[08:55] <ikepanhc> git://kernel.ubuntu.com/hwe/oem-master.git
[08:55] <apw> ikepanhc, thanks :)
[08:56] <ikepanhc> apw: :)
[09:00] <abogani> By the way the natty-meta package contain a typo in README file at line 6.
[10:12]  * smb spots gkh signs
[13:38] <apw> boing
[13:40] <smb> Not so much "boing" than "whoosh" (or how would a erupting volcano sound?)
[13:41] <cking> eh?
[13:42]  * smb is causing confusion by merging two statements hours apart on irc
[13:46] <tgardner> apw, are you working on a 2.6.36 final for natty? I can do it if you're busy. then we can leave natty alone for a few weeks.
[13:52] <smallfoot-> when put 2.6.36 in ubuntu?
[13:52] <smallfoot-> when put in ppa?
[13:54] <apw> tgardner, will do it :)
[14:07] <lag> JFo: 
[14:07] <JFo> lag
[14:07] <JFo> :)
[14:07] <lag> What do we do?
[14:07] <lag> Where do we go?
[14:07] <JFo> no idea
[14:07] <smb> clueless
[14:07] <JFo> was wondering that myself
[14:07] <smb> as the rest of us
[14:07] <lag> Good job we had this test :)
[14:08] <JFo> indeed
[14:08] <lag> This could have been the real thing
[14:08] <lag> smb: No
[14:08] <lag> smb: We have a video conf call
[14:08] <smb> lag, "We" have not
[14:08] <smb> :)
[14:08] <JFo> lol
[14:09] <JFo> lag, you see that ping?
[14:10] <JFo> just invited you lag
[14:11] <komputes> JFo: I would like to compile my own kernel as MTecknology posted on his latest blog post. Are you or is anyone able to walk me through this or point me to a guide which tells me the best way to do this on Ubuntu?
[14:12] <komputes> MTecknology: btw, I can't find the .config for kernel options on http://profarius.com/content/what-you-need-do-after-installing-ubuntu-1010
[14:12] <JFo> komputes, there should be some information in the /Kernel wiki pages at wiki.ubuntu.com/Kernel
[14:12] <JFo> let me know if you have trouble finding them
[14:13] <komputes> JFo: ok, wel thanks to ogasawara and the LPI201 study guide, I know the basics. But I will try my best to do this without being too much of a pain. :-)
[14:14] <JFo> heh, no problem :)
[16:30] <sconklin> the maverick distro master branch has been updated with the merge of the security release. Thanks to Brad for doing this.
[16:33] <MTecknology> komputes: ?
[16:33] <MTecknology> oh
[16:33] <MTecknology> komputes: http://profarius.com/sites/profarius.com/files/kernel.config
[16:33] <MTecknology> komputes: keep in mind that it's created by a psycho
[16:34] <MTecknology> komputes: It wasn't listed at the bottom of the page for you?
[16:34] <komputes> MTecknology: wow, right on time. cheers and congrats on the engagement
[16:34] <komputes> nope
[16:36] <MTecknology> komputes: thanks :)
[16:36] <MTecknology> I'll look into why.
[16:37] <komputes> MTecknology: do you recommend any particular build method from here for doing this: https://wiki.ubuntu.com/Kernel/Dev
[16:37] <komputes> MTecknology: if you can add the commands you used to your post, I would find it extremely helpful.
[16:38] <MTecknology> komputes: make menuconfig; make all install
[16:39] <MTecknology> komputes: I said phsycho :P If you're looking to do it the 'right' way, then you probably want to not follow my advice :P
[16:39] <komputes> MTecknology: where to I place the config, can I see your config file in curses menu view?
[16:39] <komputes> I'm experimenting, no worries
[16:40] <MTecknology> ls -a
[16:41] <komputes> MTecknology: are you asking for a listing of the kernel source dir?
[16:41] <MTecknology> komputes: no
[16:41] <komputes> k
[16:41] <MTecknology> komputes: that's where the .config is
[16:42] <komputes> err. where?
[16:42] <komputes> top level of the kernel source?
[16:43] <komputes> sorry, I'm a virgin at this
[16:44] <komputes> many attempts, never success
[16:49] <komputes> JFo: MTecknology: "make menuconfig" returns the error "Requires ncurses-devel" but the correct package name is libncurses5-dev
[16:50] <MTecknology> komputes: actually.. ncurses-dev
[16:50] <komputes> oh, ok
[16:52] <komputes> MTecknology: ncurses-dev is purely vityual pounting to libncurses5-dev ;)
[16:52] <komputes> virtual*
[16:53] <komputes> should we report to make a change to the error (from ncurses-devel to ncurses-dev)
[16:53] <MTecknology> komputes: it's not an error
[16:53] <MTecknology> komputes: other package managers use the virtual package ncurses-devel, for some that is the package
[16:54] <komputes> ok
[16:54] <smoser> hey. so, i'm trying to figure out what changed between 'linux-image-2.6.32-308-ec2 2.6.32-308.16' and 'linux-image-2.6.32-309-ec2 2.6.32-309.18'
[16:54] <MTecknology> You're not dealing with something that's ubuntu-centric, it's linux-centric :)
[16:54] <smoser> looking a the changelog for the newer version http://changelogs.ubuntu.com/changelogs/pool/main/l/linux-ec2/linux-ec2_2.6.32-309.18/changelog
[16:54] <smoser> it does not even include 2.6.32-308.16
[16:54] <komputes> understood.
[16:57] <smoser> i'm guessing that the entries for 2.6.32-309.17 and 2.6.32-309.18. but programmatically, that would be difficult to determine since i can't locate the source version in the changelog
[16:57] <smb> smoser, Some upload versions can get eradicated when security replaces a version in proposed
[16:57] <smoser> it seems that that entry got dropped
[16:57] <smoser> the changelog entry got dropped though
[16:57] <smoser> both those versions did exist
[16:58] <smoser> http://changelogs.ubuntu.com/changelogs/pool/main/l/linux-ec2/linux-ec2_2.6.32-308.16/changelog 
[16:58] <smb> If it did not leave proposed it did not officially exist
[16:58] <smoser> it did leave proposed
[17:00] <smoser> (it made it into an image created 20100923 that do not include -proposed in their sources.list)
[17:01] <smb> smoser, Hm, right. .16 would actually have been a security release
[17:01] <smoser> i'm guessing its just human error, and also that only the changelog entry for 2.6.32-308.16 was dropped, and not actually the changes.
[17:03] <smb> If I am not wrong and the .16 was a security update, then those changes should normally not get dropped when rebasing to a newer version of the master kernel
[17:04] <smoser> 308.16 was a security release. 
[17:04] <smb> Yes, so I am quite confident that this is just an error within the changelog
[17:04] <smoser> i'm not trying to be accusing, i'm just wanting to make sure that there isn't a hole in the process that dropped those security fixes.
[17:05] <smoser> and ideally, that in the future, even the changelogs wouldn't get dropped
[17:05] <smoser> i'm trying to write a tool that shows me what differed between two builds, and want to grab new changelog entries.
[17:06] <smb> Right. The rebasing itself is safer than the changelog because that needs manual intervention to get it right
[17:06] <smoser> right. humans are incompetent
[17:06] <smoser> :)
[17:07] <smb> Agreed :) But in general it could get difficult to compare changelogs
[17:07] <smb> Its already sometimes confusing for the master tree. But rebase branches are worse
[17:08] <komputes> MTecknology: My docs says Kernel configuration settings are stored in a file named .config. Historically, this file was saved within your kernel source to /usr/src/linux or /usr/src/linux-kernel-version, but this is no longer the case. Older applications (based on the standard libc) required /usr/src/linux, but the introduction of a new library, glibc, eliminated that dependency. So I simply placed it in the linux-2.6.35-MTeck/ dir and r
[17:08] <komputes> an "make menuconfig" and I'm now going through all the changes you made. Very cool :-)
[17:09] <komputes> Especially cool with split screen terminal
[17:10] <smoser> thanks smb . just kindly take note of my "please try to get changelog entries correct" request.
[17:10] <MTecknology> komputes: there's also make xconfig, but I think menuconfig is better
[17:10] <smb> smoser, note taken
[17:10] <smb> :)
[17:11] <komputes> MTecknology: I'm aware of these ways to do it: make config, make menuconfig, and make xconfig
[17:11] <komputes> MTecknology: menu is still my favorite
[17:20] <komputes> MTecknology: few questions about disabled configurations: pass kernel param to init, LZO vs Gzip kernel compression, POSIX msg queue, BSD process accounting, export task, namespaces - how can i better understand what these are and what is the result of disabling them?
[17:21] <MTecknology> komputes: look at the help for it
[17:21] <MTecknology> komputes: then look at the code or online
[17:22] <komputes> MTecknology: ok, help wasn't working, but I found it - not quite english, but I kind of understand
[17:23] <komputes> MTecknology: do you remove upstart from your system and simply use init?
[17:23] <MTecknology> komputes: nope, upstart is still there
[17:24] <komputes> MTecknology: and disabling CONFIG_INIT_PASS_ALL_PARAMS does not mess that up?
[17:27] <MTecknology> komputes: I didn't say upstart still worked the way it's supposed to :P
[17:30] <komputes> muahahaha
[18:09] <maakri>    
[19:30] <anarsoul> hi there
[19:30] <anarsoul> what's sane way to load custom DSDT table in ubuntu 10.10?
[19:31] <anarsoul> DSDT table for my laptop is broken (thermal and battery methods are incorrect) and so I need to load my custom DSDT
[19:31] <apw> anarsoul, as i recall things there is no offical way to do that, as you can brick your laptop
[19:31] <mjg59> anarsoul: Incorrect in what way?
[19:32] <apw> i believe the approved approach is to quirk round the deficienies
[19:32] <anarsoul> mjg59: thermal provides incorrect info about CPU temperature (sometimes stick at 70C and fan works all this time)
[19:33] <anarsoul> and battery method provides some heuristic info about capacity instead of get this info from smart controller
[19:33] <anarsoul> so it's dangerous to use laptop on battery with default DSDT table
[19:33] <mjg59> apw: Well, approved approach is for people to either get the bugs fixed in Linux or, if Windows has the same behaviour, return the hardware for being broken
[19:33] <anarsoul> as it can kill battery because it can't detect correctly when it's broken
[19:34] <anarsoul> mjg59: windows has the same behaviour
[19:34] <apw> mjg59, well put
[19:34] <anarsoul> and I can't return this hardware
[19:34] <mjg59> anarsoul: Your hardware's broken, then!
[19:34] <anarsoul> it's 3year old laptop
[19:34] <mjg59> There's an interface in debugfs that lets you override individual ACPI methds
[19:34] <anarsoul> mjg59: wrong answer
[19:34] <anarsoul> it works with fixed DSDT table
[19:35] <anarsoul> mjg59: yeah, I know, it does not fit
[19:35] <mjg59> Then you get to build your own kernel
[19:35] <anarsoul> as it can override only methods
[19:35] <anarsoul> but I need to override OperationRegion aswell
[19:36] <anarsoul> mjg59: I remember there was a patch that allowed to load custom dsdt from initramfs
[19:36] <anarsoul> why it was removed?
[19:36] <mjg59> anarsoul: It got rejected upstream
[19:36] <anarsoul> so what?
[19:36] <apw> anarsoul, because people would load random dsdt's into their system
[19:36] <anarsoul> ubuntu keeps much their custom patches
[19:36] <apw> anarsoul, where someone on a bug suggested a mod for a different system
[19:37] <anarsoul> why not to keep another one?
[19:37] <apw> anarsoul, and as you can do genuine dammage to your system 
[19:37] <apw> anarsoul, it was seen as too dangerous
[19:37] <anarsoul> apw: you can damage your system by overriding acpi method via debugfs
[19:37] <apw> anarsoul, indeed that is also true
[19:38] <apw> but that was the reason the patch wasn't maintained
[19:39] <apw> too easy for a naieve user to follow instructions to try and modded dsdt on the wrong laptop
[19:41] <anarsoul> apw: oh, it's easy to do "sudo dd if=/dev/urandom of=/dev/mem"
[19:42] <mjg59> anarsoul: If you're competent to modify ACPI tables then you're competent to rebuild your kernel
[19:45] <apw> anarsoul, yep you can shoot self in the foot a number of ways, but people seemed to like loading random dsdts that fixed things for other people
[19:45] <anarsoul> mjg59: yeah, but it takes my and cpu's time
[19:45] <apw> anarsoul, its all a balance
[19:46] <anarsoul> mjg59: and I can't react on each security update
[19:59] <ppetraki> hi all
[19:59] <ppetraki> quick question
[20:00] <ppetraki> is  echo 1 > /proc/sys/kernel/panic_on_oops supposed to work?
[20:00] <ppetraki> cuz it's not panicing :)
[20:04] <tgardner> ppetraki, try /proc/sysrq-trigger
[20:05] <komputes> MTecknology: at the end of the compilation, I get many errors relating to ndiaswrapper. Do you know which path in the menu config I need to go to disable the ndis (module?).
[20:05] <ppetraki> tgardner, Tim, the goal is to panic on some mysterious oops we've been seeing, the systems are unattended
[20:05] <MTecknology> komputes: press / and search
[20:06] <tgardner> ppetraki, well, I think you can do that from user space. see Documentation/kdump/kdump.txt in the kernel tree
[20:07] <ppetraki> tgardner, I'll take a closer look, thanks
[20:08] <komputes> MTecknology: found it but once i press exit i do not know the path to get to it
[20:08] <komputes> MTecknology: it brings me the help page only - can't turn it on/off
[20:08] <MTecknology> komputes: you need to follow the path it gives you
[20:09] <komputes> MTecknology: awesome, thanks
[20:32]  * ogasawara lunch
[20:53] <komputes> MTecknology: OK! :-)   I finally finished compiling, no errors. I had to change compression (gzip) and strip out rtl and ndis networking extras. So what now?
[20:54] <MTecknology> komputes: you installed it?
[21:29] <komputes> MTecknology: well I did "make all install" not quite sure what that accomplishes, but it looks like it finally compiled without errors
[21:29] <MTecknology> update-grub2
[21:29] <MTecknology> reboot
[21:29] <MTecknology> you should read the Makefile
[21:29] <komputes> orly? nice...
[21:30] <MTecknology> don't remove the generic kernel until you really know what you're doing and know how to fix things when it breaks
[21:30] <komputes> no, i don't inted to remove the ubuntu stock kernels at all
[21:31] <komputes> and this is a scratch box
[21:31] <komputes> MTecknology: I'm reading the makefile, you actually understand this?
[21:31] <MTecknology> :P
[21:48] <komputes> MTecknology: rebooted, kernel won't boot properly, when i run it in recovery mode I quickly see an error regarding VBIOS table
[21:48] <komputes> it makes two short beep noises
[21:49] <MTecknology> komputes: yup, that's the fun in compiling your own kernel :)
[21:49] <MTecknology> komputes: look on the gentoo install manual and it'll help you start to understand it better
[21:49] <komputes> MTecknology: will do. thanks for all your help today, what an adventure
[21:49] <MTecknology> komputes: np, make sure to enjoy
[22:10] <savasci> hi. I am taking an OS class in university, we did some kernel manipulation( adding a system call), after installing the new kernel, for every boot it says " starting up Uncompressing Linux... Ok, booting the kernel". does that means any problem, any way to avoid this uncompressing stage?
[22:15] <komputes> MTecknology: I'm guessing it's one of the first three here: http://www.google.com/search?q=gentoo+install+manual
[22:16] <sconklin> savasci: it's normal, and you want to leave it that way. The kernel in memory has a lot of zero-filled data, and compressing it makes it a lot smaller on disk
[22:16] <sconklin> http://www.ibm.com/developerworks/library/l-linuxboot/index.html
[22:57] <hyperair> hi. where can i find out more about ubuntu dropping support for things below i686?
[22:57] <hyperair> it seems the lubuntu folk are pretty upset about this.
[23:56] <JFo> ogasawara, just responded on that e-mail you forwarded
[23:56] <JFo> sorry for overlooking that :-/
[23:56] <ogasawara> JFo: no worries.  not sure how much help he'll turn out to be.
[23:57] <JFo> every bit helps :)