[00:06] can someone take a look at this error? [00:06] http://pastebin.ca/1492112 [00:30] its a problem with kernel-package with nvidia-common thats been around for a looong time billybigrigger [00:33] were there changes to usb in 2.6.31 that need updated userland support or something? been having alot of problems with usb devices after 2.6.30 [00:34] my camera, ipod, and videocamera all work good [00:34] its just the webcam [00:34] but that could probably because they're all recognized as mass storage [00:34] i see usbfs moved over to CONFIG_EMBEDDED, dont know if we use that before [00:36] my webcam and android phone stopped working [00:39] Sarvatt, no dice [00:40] thanks for checking [00:40] its there [00:40] but webcam not working [00:41] billybigrigger@cabo:/proc/bus/usb$ ls [00:41] billybigrigger@cabo:/proc/bus/usb$ [00:41] empty, but its there [00:43] oh so usbfs was used in .30 where it was working before? [00:43] hmm [00:44] funny thing, i have sound in flash on this kernel :P [00:49] my Android phone works fine with 2.6.31 [00:49] my webcam behaves a bit funny though, but I'm not sure if that's the kernel's fault [00:50] i get a flood of error messages in dmesg while its plugging in without enabling mass storage on the phone (like when i'm just charging it) [00:51] seems to work for me [00:55] the webcam is definitely screwed up, though: http://nullinfinity.org/tmp/screenshot6.png [00:55] (I am actually not a smurf) [00:55] johanbr, nvidia user? [00:55] yep [00:55] looks like the nvidia hue -1000 bug [00:55] :) [00:56] oh [00:56] do you have a launchpad link? [00:56] yup lemme dig it up [00:56] yeah change the saturation under 0 in nvidia-settings then save, then back up to 0 and save [00:56] Sarvatt, funny thing was, i was affected by it, and my hue was at 0 [00:56] just -1000 in vlc [00:56] they changed the xv saturation ranges in the driver and our old nvidia-settings doesnt copy with it [00:56] yeah because it isnt really at 0 [00:56] so it might be on an app to app basis [00:56] billybigrigger, you're absolutely right [00:56] thanks [00:56] ooooooh [00:57] it thinks its at 0 but its really at 4096 from the old ranges [00:57] I hadn't noticed that regular video had funny colours too [00:57] https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-180/+bug/395476 [00:57] Malone bug 395476 in totem "nvidia sets HUE to -1000" [Low,Triaged] [00:57] things that use their own saturation settings arent affected but things that use nvidia-settings ones are [00:57] bugabundo started that one, but im pretty sure it should be against nvidia-glx-180 and not totem [00:58] Sarvatt, that makes sense [01:27] Sarvatt, will i be able to file bugs under my custom kernel? [01:27] or will they have to be done upstream to the package maintainers [01:34] just file the bug on the ubuntu kernel since its the same [01:34] ok === bjf is now known as bjf_afk === Omegamoon is now known as Omegamoon|away === Sarvatt__ is now known as Sarvatt_ [16:05] I have a question; any reason 2.6.30.1 hasn't shown up in the mainline PPA ? [18:13] git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git [18:14] Sarvatt, that is where i pulled the latest kernel source [18:14] so when i want to update it... [18:14] git pull from the same source right? [18:14] "git pull" [18:14] 10-4 [18:14] there is life in here! :P [18:19] thrice`, and that won't compile just the new stuff [18:19] it will pull whatever is new, and recompile the whole shebang again right? [18:19] yep [18:19] compiling is not related to obtaining of the source [18:20] no, thats separate [18:22] fatal: Not a git repository (or any of the parent directories): .git [18:23] are you inside the dir? [18:23] no, was one above it [18:24] ok now i get an error that i didn't tell git what branch i wanted to merge with [18:24] http://pastebin.ca/1492879 [18:25] just do "git pull" on its own [18:25] oh [18:41] ooh, 2.6.31.1 seems to break jfs booting from grub1 :( [18:42] that's probably why it's not in the PPA :> [18:44] thrice`: wrong [18:44] that has been broken since at least hardy [18:45] and probably gutsy [18:50] huh? [18:50] 2.6.29 boots my jfs just fine, as does 2.6.30 [18:51] it is not a kernel issue [18:51] grub1 is bitrotted [18:51] of course :) [18:51] if grub cannot read the fs, the kernel is never loaded, regardless of version [18:52] i'm trying to say that 2.6.30.1 introduced a specific failure [18:52] it did not; that failure has been there for some time [18:52] hey... I wanted to ask what I can do about the following problem: [18:52] you know which I'm talking about sn9 ? [18:52] it is why i have an ext3 /boot on this laptop [18:53] with the new kernel it seems to [18:53] support cpufreq for the via cpu... but in a strange [18:53] way... before it was always at max speed... now it [18:53] looks like it changes speed but I think it's not... I [18:53] can't even get it to run at full speed [18:53] anymore... compared the performace with the two [18:53] kernel versions [18:53] oops... sry for the line breaks [18:54] sn9: I am specifically referring to: http://bugs.archlinux.org/task/15416 [18:54] reto`: is the same governor used? [18:55] git commit 206f0f05bdc291a9358ba59248e2bc44e8b3127d [18:55] sn9: uh... the old kernel doesn't support cpufreq [18:55] reto`: which via? c7? [18:55] sn9: I can try any governor or freq setting with the new kernel [18:56] sn9: it doesn't change anything [18:56] sn9: c7-m [18:57] thrice`: the bug report is wrong; jfs has been unreadable by grub for quite some time [18:57] what are you talking about??? [18:57] I boot jfs from 2.6.29.6 right now [18:59] thrice`: how big is the fs? [18:59] sn9: should I report this somewhere or how is the situation with the VIA? [18:59] size does not matter [19:04] reto`: are you using the longhaul driver, or e_powersaver? [19:04] thrice`: then why has jfs booting consistently failed for me on every machine after feisty? [19:05] I don't know. I promise that it works with 2.6.29.x , and even 2.6.30 :) [19:05] the bug I mentioned was a specific change to 2.6.30.1 regarding the creation of an initrd [19:05] sn9: hmm... I think the longhaul... it's displaying some message about that one though on boot [19:06] the grub people told me this bug has been there since 2004 [19:06] reto`: check through the /sys tree [19:06] ok, i'm not really interrested in arguing :( My system booted just fine this morning with jfs on / === MobileMyles6o7 is now known as TwoToneSpirit [19:09] thrice`: the real solution would be for ubuntu to take the bold step of dumping grub1 as a default [19:09] or lilo :> [19:09] sn9: it's using the longhaul... but I think it's displaying an error message on boot about that... just didn't know what it is... [19:10] reto`: HTH [19:10] thrice`: lilo would actually work [19:11] sn9: ok, let me fetch that [19:18] sn9: the message is: APIC detected. Lonhaul ist currently broken in this configuration. [19:19] what about e_powersaver? [19:21] sn9: I would have to try... how can I disable the longhaul? [19:23] is it a module? [19:25] sn9: how can I find out? [19:25] sudo rmmod longhaul [19:26] if there's no error, try loading e_powersaver [19:26] module isn't found [19:26] it's in the kernel then? [19:26] must be [19:27] I can load e_powersaver with the old kernel though [19:27] unless it just didn't load [19:27] modinfo longhaul e_powersaver [19:28] it din't find the longhaul but e_ [19:29] does it load? [19:29] no I get an error [19:30] longhaul seems to be loaded somehow but not working correctly [19:30] wonder why it is loaded when it knows "it is broken" [19:31] bug? [19:32] looks like longhaul went into the kernel with .31 [19:33] karmic fail [19:33] can I disable it somehow? [19:33] not without another kernel build [19:33] OTOH, there is "noapic"... [19:34] yeah... hmm... might try that one [19:43] hmm... no use... it still loads longhaul [19:43] ah well... at least the machine is not hollering at full speed [19:49] reto`: echo "blacklist longhaul" > /etc/modprobe.d/die_longhaul_die && update-initramfs -u && reboot [19:49] reto`: That should stop it from being loaded. [19:50] infinity: no; it's compiled in, not a module, rendering that useless [19:51] sn9: Oh. Didn't notice that. Seriously, though [19:51] ? [19:51] We shoudln't be compiling any of that in. :/ [19:51] as i said: [19:51] [Sun 12 Jul 2009 11:33:01 AM PDT] karmic fail [21:01] ok... I've checked it out... with e_powersaver the scaling is working... I'm not 100% sure but I think longhaul has been in the kernel even before .31 (.28) but with 31.2 there seems to be a bug where longhaul is loaded even when it is detected to be broken [21:31] I'm writing a bug report on launchpad for this problem. Any suggestions? [21:33] just that it should not be a module [21:33] i mean [21:33] just that it should not be not a module [21:34] :) ... ok [21:54] Sarvatt, ping [21:54] what other optimizations can i make when compiling kernel? [21:54] besides not compiling for intel [21:58] i seen there was some more v4l2 stuff changed today [21:59] thought i'd give it another go [22:30] anyone built today's kernel? [22:30] i get this error [22:30] http://pastebin.ca/1493055 [22:30] when trying to compile from git [22:45] ill just remove wireless modules from menuconfig then :P [22:45] thanks guys :P [22:45] no need on a desktop anywho [22:46] where can i find my make log from my last compile? do i have to specify one for it to be outputted? [22:46] make-kpkg blah > log? [22:48] CONCURRENCY_LEVEL=3 fakeroot make-kpkg --initrd -append-to-version=-billybigrigger kernel_image kernel_headers kernel_source > make.log [22:48] does that look right? [22:53] you probably want to call it billybigrigger2 because you already have a billybigrigger and use >whatever.log 2>&1 [22:53] do it in screen and control+a d the tail -f whatever.log to watch it :) [22:54] tailing it now [22:54] and have it named billy-07.12 [22:55] :P [22:55] thanks though [22:55] * billybigrigger_ crosses fingers :P some more v4l2 stuff updated today [22:58] Sarvatt, you till convinced its udev and usb problems though? [23:18] drivers/net/wireless/wl3501_cs.c:384: note: ‘tmp’ was declared here [23:19] make[1]: *** [drivers] Error 2 [23:19] :( still wireless driver errors, i didn't include any wirelss modules though