[00:21] hello, I've been trying to build the mainline kernel (from kernel.org) and even though it compiles every time I boot it hangs at "loading ramdisk", when I boot with nomodeset the system boots, but the resolution is messed up [00:22] I'm using nouveau, is there anything ubuntu specific that I need to do besides fakeroot make-kpkg --initrd --append-to-version=-some-string-here kernel-image kernel-headers [00:22] ? [00:23] the 3.6 kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.6.2-quantal/ works fine [07:10] * smb yawns === henrix_ is now known as henrix === henrix is now known as henrix_ === henrix_ is now known as henrix === doko_ is now known as doko [11:14] * henrix -> lunch [11:30] hey all. I just read about the "new" send/receive feature of btrfs and asked myself if there are any apps in development to use this feature for fast backups? [11:31] black_puppydog: offtopic for this channel =) as you are asking about userspace tools.... [11:32] yeah, I thought that too, but xouldnt come up with the right channel for this. any pointers? [11:34] black_puppydog: #ubuntu or #ubuntu-server [11:35] ok, #ubuntu seemed too general, but why #ubuntu-server ? [11:35] I am talking abouta normal desktop machine [11:35] well, laptop actually, still.... [12:11] http://codepad.org/0eVoe3vI kernel module, http://codepad.org/tkbUSE6r user code, http://codepad.org/C2fxD5Yv make file : I am trying to write a simple char driver, using mmap in user space. The problem is my code is working fine for 20 - 4K bytes, but I want to mmap 10024 bytes. At this value (BUFF_LEN 10024 and +) it is crashing. Any idea how to make it work for 10024 ? or any hint or suggestions ? [12:59] black_puppydog: you can try #ubuntu-desktop. #ubuntu-server has more poweruser crowd who are more lickely to take backups =) === Guest98741 is now known as balloons === balloons is now known as Guest27823 === Guest27823 is now known as balloons_ === BenC__ is now known as BenC === balloons_ is now known as balloons === yofel_ is now known as yofel [14:41] apw: are you around? [14:41] ppisati, yep [14:41] apw: cool, is your panda hooked up? [14:42] ppisati, its off and not where i am right now, what do you need? [14:42] apw: nothing, just a check [14:43] ppisati, i can boot and update it tonight if that is useful [14:43] apw: do you connect it to an hdmi or dvi monitor? [14:44] i use the connector nearest the edge of the board [14:45] apw: and your monitor? [14:45] apw: do you remember if you are using an hdmi->dvi cable or hdmi->hdmi cable? [14:45] ppisati, i cannot visualise it right now, monitor has both [14:46] i'd have to look at it in the flesh [14:46] apw: ok, anyhow, if you can try beta2 on it that would be nice [14:46] ppisati, rather than the release ? [14:46] apw: yeah, you should get a black (or blue) screen before installer comes up [14:47] apw: at least, it happens to me and jsalisbury [14:47] apw: bot to ogra and rsalveti [14:47] *not [14:47] odd [14:47] apw: this while using the hdmi output on the board and an hdmi->dvi cable [14:50] ppisati, I see it when using the DVI output and an hdmi->dvi cable [14:51] jsalisbury: right [14:51] apw, I've got 3.7-rc1 rebased and am finding the configs generation to be quite tedious. I know you've had a slicker way of doing this in the past. Care to share ? [14:52] rtg_, as in how do i do the update configs part ? [14:53] apw, right, I keep having to repeast many of the same answers for each flavour/arch [14:53] rtg_, i do that via "script" [14:53] rtg_, so i run script, in the contained shell i make updateconfigs [14:53] rtg_, then i answer for one arch [14:54] rtg then i give up, and ^C and exit the script [14:54] apw, then append your answers to the common config ? [14:55] rtg_, then i use chinstrap:~apw/config2rules on that file [14:56] rtg_, and put that in debian.master/config/OVERRIDES, then run updateconfigs [14:56] making sense ? [14:57] apw, OVERRIDES is what I was looking for. [14:57] rtg_, then i do the same next arch adding to OVERRIDES until done [14:58] apw, yep, makes sense [15:04] ppisati: so it seems there are a lot to test actually [15:04] dvi alone, hdmi alone, dvi+hdmi cable, hdmi+dvi cable and different board revs [15:04] rsalveti: ? [15:05] because with my setup, and with my boards, I'm not able to reproduce this issue at all [15:05] I just need to find a hdmi->dvi cable here [15:05] rsalveti: that's why i'm trying to get more people to test it [15:05] rsalveti: so far, me and jsalisbury can reproduce it [15:05] rsalveti: you and ogra no [15:05] ppisati: please also document at the bug all the board revs you tested [15:05] rsalveti: done [15:05] great, thanks [15:07] is there a way to kick a QA test? [15:08] * jsalisbury needs to reboot. brb [15:08] ogra_: ^ [15:08] ppisati, what exactly are you asking? [15:08] bjf: that they take a panda, and try to reproduce lp 1065902 [15:08] Launchpad bug 1065902 in linux-ti-omap4 "black/blue screen before installer, tty switch fixes it" [Medium,Confirmed] https://launchpad.net/bugs/1065902 [15:09] bjf: with their hw setup [15:09] ppisati, you can ask hggdh, i know they have several [15:09] bjf: if they have more setups, better [15:09] hggdh: ^ [15:09] ppisati, hggdh would know what testing they are currently doing with them [15:10] ppisati, yeah, what bjf said [15:17] ppisati: sorry, was in a meeting [15:18] ppisati: what do you need there? [15:18] hggdh: we would like to ask you to try and reproduce lp 1065902 [15:18] Launchpad bug 1065902 in linux-ti-omap4 "black/blue screen before installer, tty switch fixes it" [Medium,Confirmed] https://launchpad.net/bugs/1065902 [15:18] hggdh: how many panda setups wo you have in the QA lab? [15:19] hggdh: just dd beta2 img on an sd card, pop into your panda, boot it and wait a couple of minutes [15:20] hggdh: if the desktop doesn't show up (you get a black/blue screen) you hit that bug [15:20] ppisati: where is the beta2 image? [15:20] hggdh: else it's ok [15:20] hggdh: it's all written in that lp bug [15:20] ppisati: if it helps any, I already reproduced it locally [15:20] hggdh: good to know [15:20] ogra_: rsalveti ^ [15:20] (my setup is similar to yours, HDMI->DVI connection [15:20] then it's not just me and jsalisbury [15:21] ppisati: IIRC, I also added the bug to the ISO QA list -- don't really remember, though, ran a truckload of tests during the weekend [15:22] hggdh: nice, thanks [15:23] yeah, I added it to the ISO results [15:29] ppisati: were you able to reproduce it with a real hdmi connector/monitor? [15:29] or with the dvi->dvi [15:31] rsalveti: hdmi on the board, dvi on the lcd -> i get it [15:31] rsalveti: hdmi on the board, hdmi input (e.g my tv) -> it's ok [15:34] ppisati: and dvi->dvi? [15:38] rsalveti: dvi output on the board, hdm9 [15:38] rsalveti: hdmi->dvi cable to my lcd (ok, but crappy resolution) [15:39] ok, thanks [15:39] brb [15:46] ogasawara, is there an ETA on when the release notes updates from kernel team will be done? [15:48] skaet: doing it now [15:48] skaet: 20min? [15:48] thanks. :) that'll help. [16:00] * ppisati -> gym [16:04] ogasawara: hey, have a second for a PM? [16:05] JoseeAntonioR: busy at the moment, feel free to message me and I'll get to it when I can [16:05] thanks [17:48] * rtg -> lunch [18:42] hi [18:43] every one! i have question regarding tcrypt module [18:47] any one used trcrypt [20:11] * henrix -> EOD [20:32] * rtg_ -> EOD === henrix is now known as henrix_