[01:30] <infinity> zequence: Around?
[01:31] <infinity> zequence: We had to respin Q and R for a regression.   You have new tracking bugs for lowlatency.
[12:07] <apw> rtg, yo ... did you rng-tools build ok
[12:08] <rtg> apw, yeah, as far as I know.
[12:08] <rtg> apw, yep, looks like -4 is published
[12:09] <rtg> apw, just idle curiosity ?
[12:09] <apw> rtg, yeah just curiosity, it was up in the air when i quit last night
[12:10] <rtg> apw, the biggest question was TPM support. since that is now in the kernel kees was OK with removing the TPM cruft from -2
[12:10] <apw> rtg, ahh ok good
[12:11] <rtg> apw, you working on the linux-tools naming scheme ?
[12:11] <apw> yeah, just trying to slip in this other thing in the middle
[12:14]  * henrix -> lunch
[13:18] <purezen> Hey guys..! I am a long time Linux enthusiast and have been using Ubuntu since long.. and would like to know if features from kernels with revisions advanced than the ones being used in Ubuntu are backported to ones used by Ubuntu by the Ubuntu team.. Like the 3.11 is supposed to bring DPM to AMD Graphics card.. and shall such features be ported to 3.10, slated to be used by Ubuntu 13.10..? Thanks..!
[13:19] <rtg> purezen, 13.10 will be based on the 3.11 kernel
[13:23] <apw> kamal, yo .. this cpufreq thing, which arches is is known to 
[13:23] <apw> build with
[13:23] <purezen> rtg: Hey..! Well, that'd be great..!
[13:24] <apw> purezen, indeed it already has an early 3.11 kernle in it
[13:24] <purezen> apw: Oh well..:-)
[13:25] <purezen> Though guys, I would like to know if the kernels that Ubuntu releases officially, I mean that the users get as updates and all.. do really get it with 'backported' components..
[13:26] <purezen> I hope that my use of the word 'backported' implies features from advanced versions, ported over to previous versions..:-)
[13:26] <apw> purezen, rarely, we tend to provide newer kernels en-toto where that is appropriate
[13:26] <rtg> purezen, sometimes we'll backport drivers, or parts of drivers, but rarely do we backport features.
[13:29] <apw> kamal, this seems pretty intel specific
[13:29] <rtg> tseliot, what is the difference between nvidia-graphics-drivers-304-updates and nvidia-graphics-drivers-experimental-304 ? The latter incorrectly depends on 'linux-headers-generic | linux-headers'
[13:29] <tseliot> rtg: which Ubuntu release are you referring to?
[13:29] <purezen> apw, rtg: Well.. Thanks for the info guys..! Also, great to see 3.11 making it to 13.10.. Needed it for DPM on AMD..!
[13:29] <rtg> tseliot, precise
[13:30] <tseliot> rtg: nvidia-graphics-drivers-experimental-304 is going away, as per bug #1198942
[13:30] <ubot2`> Launchpad bug 1198942 in nvidia-prime (Ubuntu Precise) "Hybrid Graphics and general enablement for fglrx and nvidia in Precise for 12.04.3" [Undecided,Fix committed] https://launchpad.net/bugs/1198942
[13:31] <rtg> tseliot, does that mean the source package will be reaped from the archive ?
[13:32] <tseliot> rtg: we'll have transitional packages to migrate nvidia-graphics-drivers-experimental-304 to nvidia-graphics-drivers-304-updates
[13:33] <rtg> tseliot, is that happening pretty soon ? the linux-headers dependency is causing some problems.
[13:34] <tseliot> rtg: I'm trying to have the packages moved into -updates ASAP (they're already in -proposed) so that I can finally go on holiday. So the answer is yes ;)
[13:34] <rtg> tseliot, good. I assume you are regularly hassling folks in the release channel ?
[13:35] <tseliot> rtg: yep, every day
[13:35] <rtg> arges, ^^
[13:35]  * arges reading
[13:36] <rtg> arges, getting rid of nvidia-graphics-drivers-experimental-304 will solve part of the problem, i.e., the bogus dependency
[13:37] <arges> rtg: yes
[13:40] <rtg> tseliot, fglrx has the same problem:
[13:40] <rtg> fglrx-installer-8.960/debian/control: linux-headers-generic | linux-headers, , ${xviddriver:Depends}
[13:41] <tseliot> rtg: I'm not updating that driver but feel free to file a bug report about that (using a different SRU)
[14:10] <apw> ogra_, yo ... can you remind me where to find the panda board docs we had, particularly how to enable a console on the serial console
[14:11] <ogra_> apw, just copy the serial script in place on the first partition of the SD
[14:11] <ogra_> (there is a bootscript that has all you need, you just need to cpp it over the one without the -serial tag)
[14:11] <ogra_> *cp
[14:15] <apw> ogra_, sounds good, where is the -serial one hiding in the filesystem
[14:15] <ogra_> nowhere ... its only on the first vfat partition ... put in place when the image is made bootable
[14:16] <apw> ogra_, ok this is too old an image then to have that, it is my buildder which is being all non-booty
[14:16] <ogra_> sudo mount /dev/mmcblk0p1 /mnt ... 
[14:16] <apw> ogra_, yeah i have done that, and have a boot.script, but no other
[14:16] <ogra_> oh
[14:16] <ogra_> ok
[14:16] <apw> boot.scr  MLO  u-boot.bin  uImage  uInitrd
[14:17] <ogra_> yeah, so you want to edit boot.scr
[14:17] <ogra_> copy it to be boot.script ...open in vim and remove the garbage at the front
[14:17] <ogra_> then add a console=ttyO2 to the cmdline 
[14:18] <apw> yep
[14:18] <ogra_> mkimage -A arm -O linux -T script -n boot.script boot.sc
[14:18] <ogra_> r
[14:18] <ogra_> that should add the header then
[14:19] <apw> Segmentation fault (core dumped)
[14:19] <apw> oops
[14:21] <apw> ogra_, does not work on either raring or saucy it seems
[14:22] <ogra_> well, if it wouldnt work we wouldnt have image releases for them :)
[14:22] <ogra_> the image build scripts dont use anything else 
[14:22] <apw> ogra_, heh that was at release
[14:22] <apw> ogra_, this is _now_ when, they coredump
[14:23] <ogra_> thats the x86 version of mkimage ?
[14:23] <ogra_> (also probably the line above was wrong ... i havent touched any panda in over a year ... (and dont plan to))
[14:24] <apw> ogra_, that is indeed x86
[14:24] <ogra_> well, file a bug :)
[14:25] <ogra_> not sure who from fooundations does arm now though 
[14:25] <ogra_> probably adam
[14:25] <apw> mkimage -A arm -O linux -T script -d boot.script boot.scr
[14:25] <apw> that at least didn't explode and made something similar
[14:26] <ogra_> heh, yeah
[14:26] <ogra_> it was my fault 
[14:26] <ogra_> -n is name 
[14:26] <ogra_> and indeed you need input data (-d)
[14:30] <apw> ogra_, well i have more on the console, this is encouraging :)
[14:30] <ogra_> :D
[14:30] <apw> ogra_, nothing much to be happy about as yet
[14:30] <apw> but ... hey 
[14:30] <apw> sudo: unable to resolve host localhost.localdomain
[14:30] <apw> she is not feeling too well i think
[14:31] <ogra_> are you sure this was properly installed ?
[14:31] <ogra_> sounds like the installer didnt run 
[14:31] <apw> hmmm
[14:31]  * apw wonders if he has the wrong card, might be
[14:31] <ogra_> (we luckily dropped the preinstalled images a while ago, for panda, so this cant happen anymore)
[14:34] <apw> this thing did get drug into the office one time, so i might have gotten them mixed up
[14:46] <apw> ogra_, is there a nice howto to install a nice shiney saucy image on this thing, whats on here is all sick
[14:48] <ogra_> apw, all newer images need a target disk ... (USB disk) ... 
[14:49] <ogra_> but if you have that, sure, there are d-i images 
[14:49] <apw> ogra_, hrm ... ok
[14:49]  * apw goes and find some h/w
[14:51] <ogra_> apw, http://ports.ubuntu.com/dists/saucy/main/installer-armhf/current/images/omap4/netboot/boot.img-serial.gz ... unzip and dd to SD card, then boot ... the rest is a server netinstall via serial
[14:51] <apw> ogra_, that sounds ... believable :)  will let you know
[14:56] <apw> ogra_, i have d-i ness on there :)
[15:07] <apw> ogra_, so does flash-whatsit know i have a split bootloader in the new world order, with uboot or whatever on mmc ?
[15:17] <ogra_> apw, its still the same ... MLO and u-boot.bin ... 
[15:17] <ogra_> on a vfat 
[15:17] <ogra_> and yeah the panda HW can only boot from MMC
[15:17] <ogra_> so you need it as "bootfloppy"
[15:32] <bjf> brendand, new Quantal and Raring kernels are ready for testing. the lts-backport-[raring/quantal] kernels just got uploaded and are building
[15:34] <brendand> bjf, yeah testing is under way
[15:34] <bjf> brendand, sweet!
[16:14] <tjaalton> i've just upgraded my desktop machine to saucy, but the kernel panics on boot. mainline 3.10-rc7 at least worked fine
[16:14] <tjaalton> and raring
[16:15] <tjaalton> kms isn't initialized yet, so there's not much on the screen to report
[16:18] <tjaalton> huh, now it worked
[16:22] <tjaalton> dropping quiet from cmdline makes it boot, weird
[16:36] <apw> rtg, ok i pushed the bits of the linux-tools fixups upto and including kamal's bits, the actual name fixes
[16:36] <apw> i am redoing now on the top and testing to confirm
[16:36] <apw> tjaalton, hrm ... odd
[16:39] <tjaalton> it seems to boot 3.11 fine after a successful boot with an earlier kernel, but not after a fresh start
[16:39] <tjaalton> doesn't matter what options it has, which makes sense
[16:39] <tjaalton> some acpi related issue
[16:39] <tjaalton> but this is an ivybridge SDP so doesn't matter that much I guess
[16:50] <manjo> tjaalton, do you have virtual box drivers installed ? 
[16:51] <tjaalton> manjo: no, and it panics 2s into boot, so it's quite early :)
[16:51] <manjo> ok
[16:51] <manjo> I had issues with panics on SR with vboxdrv loaded so asked 
[16:53] <tjaalton> ok
[21:50] <PhoeniXYZ> Hi everyone. Is there a way to find out whats wrong (some kind of log maybe) if my pc just freezes after the "loading kernel image" and "loading initram" messages (sorry if this is not the right place to ask about this)?