=== chuck is now known as zul [02:39] in the package linux-backport-modules does the debian/config/0list file apply to all arches ? [02:40] or must i change debian/config/{i386,amd64,etc etc etc} === infinity2 is now known as infinity === asac_ is now known as asac === asac_ is now known as asac [08:05] moin === asac__ is now known as asac === ajmitch_ is now known as ajmitch === thom_ is now known as thom === asac_ is now known as asac === zul_ is now known as zul === asac_ is now known as asac === doko_ is now known as doko [16:15] freaking power outages its like living in the 3rd world again [16:18] zul: You're Canadian, right? We had outages all around Halifax last night. [16:18] johanbr: yeah its like a regular occurence in ottawa these days [16:18] Same here... [16:22] and i was just in the middle of a rediffing too [16:48] kylem: around ? === asac___ is now known as asac_ === asac_ is now known as asac [18:12] BenC: 121978... does a -updates upload of lrm make sense for that? [18:13] lamont: yeah [18:13] BenC: want me to do it? [18:13] lamont: sure [18:14] and is there anything else that should go in? [18:19] lamont: for lrm, there's a bug about invisible files not getting removed in nvidia-glx packages [18:20] Bug #106217 [18:20] Launchpad bug 106217 in linux-restricted-modules-2.6.20 "Hidden file does not get removed when switching from nvidia-glx-new/nvidia-glx-legacy to nvidia-glx causing X not to start due to mismatch of versions" [Undecided,Confirmed] https://launchpad.net/bugs/106217 [18:20] there's a patch [18:20] rock [18:21] applying provided patches is about my effort level today [18:23] BenC: the one that went to the kernel team last week? [18:25] lamont: that bug report has a patch to fix the hidden files remaining [18:28] right [18:35] * lamont notes in passing that his definition of "test" for this lrm upload consists of making sure it compiles on gutsy/i386 [18:36] sounds about right :) [18:38] * lamont then needs to debug his laptops video regression with gutsy === ember_ is now known as ember === ember_ is now known as ember [19:11] hi all [19:11] I'd like to build latest fglrx driver [19:11] but (like every time) I have to fight with the kernel headers [19:12] it says that the UTS release doesn't match current version: 2.6.22.9 [19:12] in gutsy [19:12] why that? should kernel version be 2.6.22-14-generic? [19:12] should NOT kernel version be 2.6.22-14-generic? [19:21] kylem or BenC : would you mind having a look at bug #129910 please ? [19:21] Launchpad bug 129910 in linux-source-2.6.22 "tty[1-6] are active but display nothing in Gutsy" [Undecided,New] https://launchpad.net/bugs/129910 [19:21] zasf: sudo apt-get install linux-headers-generic [19:22] BenC: I have that installed [19:22] Lutin: I don't have time to look at it yet [19:22] BenC: ok [19:22] zasf: then you have some local problem, or fglrx has a broken build setup [19:23] zasf: maybe force the kernel directory somehow [19:23] Should point to /usr/src/linux-headers-2.6.22-14-generic [19:23] zasf: are you building an old fglrx? [19:23] zasf: and why not use the one we include? [19:23] (this bug is mistakenly shown as new, it's set as critical on initramfs-tools) [19:24] because 8.42.3 brings aiglx support :D [19:24] It could be my fault, but I make-kpkg modules_image doesn't work [19:24] Lutin: 129910 is a .config story [19:24] The UTS Release version in include/linux/version.h [19:24] "2.6.22-14-generic" [19:24] does not match current version: [19:24] "2.6.22.9" [19:25] how does it get 2.6.22.9 as the current version? [19:25] I just remove the package and reinstalled it (linxu-headers-generic) [19:25] zasf: what does "uname -a" show? [19:25] # uname -a [19:25] Linux gutsy 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 GNU/Linux [19:25] maks_: don't catch why :/ [19:26] Lutin: fb not build modular, BenC had been asked to revert that change irc [19:26] that happened before in feisty and edgy. I always have to do a combination of 'make-kpkg debian', make scripts, etc to get it working [19:27] and editing include/linux/version.h [19:27] maks_: s/revert/re-apply our local patch/ [19:27] I like installing kernel modules with "make-kpkg modules_image" and not using mod-ass [19:27] maks_: stock kernel doesn't let you build vga16fb modular [19:28] /boot/config-2.6.23-rc9-amd64:CONFIG_FB_VGA16=m [19:28] maks_: it's modular. the issue is that it's not in /lib/modules/whatever/initrd and that the modprobe option used to load the modules in the initrd scripts is different, from what I've read [19:28] s/initrd/initramfs-tools/2 [19:28] maks_: maybe it's vesafb that can't be modular then [19:28] one of them we've been patching forever and a day [19:31] yes we kicked the b0rked Xu vesafb patch :P [19:34] * Lutin doesn't understand if what happens to the fb in gutsy is wanted or not [19:39] Lutin my logs have this [19:39] 21:22 maks_: yeah, but here is the point :) in ubuntu the scripts for an [19:39] y *fb) module. which can't be found, as the framebuffer is not a module in gutsy [19:39] :)21:22 Because somebody changed the config for no obvious reason [19:39] 21:23 BenC: I thought you were changing that back? :) [19:39] #ubuntu-kernel.2007-09-28.log [19:41] Yes, that was supposed to get changed back [19:44] maks_: well now that's module, but stilln vesafb and fbcon aren't in /lib/modules/whatever/initrd , which still causes them not to be loaded, unless I'm mistaken [19:45] mjg59: yeah, rtg got the modular patch back in [19:45] check /usr/share/initramfs-tools/hooks/kernelextras [19:45] Lutin also update-initramfs has a "-v" switch [19:46] tells you exactly whats added to initramfs [19:47] maks_: it tells me it doesn't load it in the initrd [19:51] well then this hook is faulty [19:54] maks_: not sure ... ${MODULESDIR}/initrd/* refers to /lib/modules/$(uname -r)/initrd, right ? [19:55] Lutin have not the ubuntu hook under the eyes, but below there should be other stuff [19:57] maks_: after that there's a case which loads some extra modules, depending on the content of ${MODULESDIR}/initrd/ [19:58] hence my question :) [19:58] BenC, what is the policy about adding FS's to linux-backport-modules , as the name implied i assume it can be done post release ... [19:59] there must be something wrong in debian/ruleset/modules.mk, since it keeps saying that I have 2.6.22.9 [19:59] imbrandon: generally that package isn't for adding things, it's mainly for updating hardware drivers [20:00] * Nafallo wants to shrink an xfs :-/ [20:00] imbrandon: what fs are you talking about? [20:00] fatx probably [20:00] fatx , i have been working with zul to get the patches right, its being looked at upstream and fedora has it [20:00] hehe. imbrandon wants xbox format still ;-) [20:01] Nafallo, well thanks to zul we got it working ;) [20:01] BenC: ive added the patch to linux-ubuntu-modules but not backport [20:01] boxbuntu :-P [20:01] BenC, if not thats cool, i can deal with just trying to get it in for hardy [20:01] i was just wondering [20:02] maks_: yep, that's it. comes from fbcon and vesafb not being in /lib/modules/$(uname -r)/initrd [20:03] imbrandon: oh, we can get it in for hardy in linux-ubuntu-modules (backports-modules is for post-release updates that are too intrusive for linux-source/lum) [20:03] BenC: ill send a patch tonight then [20:03] ahh sounds great, i was just hopeing ;) i'll keep poking zul then and we'll just target hardy [20:04] * zul is swiss cheese [20:04] zul, btw i'll leave that .img file up too incase someone wants to test it without an xbox [20:04] at the same url [20:04] sure [20:05] i was looking too fatx is VERY similar to fat32 [20:05] lol [20:05] to bad it couldent have "just worked"(tm) [21:55] hello [21:55] can somebody tell how can I blacklist a restricted driver? [21:55] I mean, to not be loaded on boot time [21:56] what is the file that I need to modify? [22:04] Nobody knows it? [22:06] /etc/modprobe.d/blacklist-* ? [22:06] (don't know, just guessing) [22:08] I've found it googling it's /etc/default/linux-restricted-modules-common [22:08] Thanks anyway [23:47] Hi, I was wondering if someone could please give an answer regarding a) The reasoning behind the changes that caused, and b) The most "proper" way to go about fixing Bug #129910. (I'd be very grateful to the person who gives me my consoles back...) [23:47] Launchpad bug 129910 in linux-source-2.6.22 "tty[1-6] are active but display nothing in Gutsy" [Undecided,New] https://launchpad.net/bugs/129910 [23:47] (Note the _17_ duplicates too) [23:51] tonyyarusso: asked the channel before, got no real answer. although the causes of the bug are well known, there doesn't to be a hurry about fixing that bug [23:51] Lutin: :( [23:52] Well, I'll wait and see what I can learn for now at least. [23:53] I'd be happy to work on a patch if needed, and even more to get a real answer. the fact that it got no answer while being set as critical for a month is quite disappointing [23:53] Remove vga= from your kernel command line [23:55] mjg59: That results in a completely unusable console resolution. [23:55] mjg59: or fox on you system, I know. what I don't get is why no one in the team even bothered answering to the bug. if you don't want to support fb, I can't get why don't you tell it and close the bug [23:55] fix* [23:56] mjg59: It works for an occasional cp or whatever, but trying to run irssi or anything else meaningful is a lost cause.