=== asac_ is now known as asac === asac_ is now known as asac === superm1|away is now known as superm1 === philwyett_ is now known as philwyett === nellery_ is now known as nellery === maks is now known as maks_ === rikai_ is now known as rikai [10:36] hi, I've a problem with lib/firmware when trying to compile/install vanilla kernel on ubuntu via the git/debian way... [10:36] I think the main problem is that dpkg -i linux-image tries to install firmware in /lib/firmware instead of /lib/firmare/$(uname -r) [10:36] thats correct [10:36] the uname hack is ubuntu specific [10:36] can I configure this somewhere under the debian control directory? [10:37] and not used in intrepid anymore [10:37] you need a patched udev in order to use that uname -r dir anyway - or at least one with changed config, when you compare it to debian [10:38] it is non standard [10:38] Kano: ok so shall I go for /lib/firmware then [10:38] ? [10:38] lib/firmware works for any kernel [10:39] on any distro [10:39] ok thanks [10:39] when you try to use /lib/firmware/$(uname -r) with debian you have lost already [10:39] ok thanks [10:40] if you dont know that is is non standard and requires a udev config change [10:40] so I revert my changes to the Makefile ;) [10:41] anyway I guess my problem was just because I'm not very familiar with debian/ubuntu dpkg [10:42] when I tried to install a newer (minor) version of my newly build 2.6.27-rc3 kernel I wasn't able to install it [10:43] because dpkg was not happy with that: [10:43] trying to overwrite `/lib/firmware/edgeport/boot2.fw', which is also in package linux-image-2.6.27-rc2-custom [10:44] dpkg-deb: subprocess paste killed by signal (Broken pipe) [10:44] well unisntall the other package [10:44] hmmm [10:45] basically I would like to have it as a rescue kernel version [10:45] as thats your only other kernel? [10:45] no no [10:45] it is not [10:45] then you have got enough rescue kenrnels ;) [10:45] hehe [10:45] yeah ok [10:45] I will go on with that [10:46] i am playing around with ubuntu git + update to kernel git. that new e1000e update is fully crap [10:46] but for example if you are tweaking with some drivers I definitely would like to be able to have different minor version [10:46] which is patched in, just disabled it and recompile [10:47] is is so buggy that the nic did not even work after reboot with another kernel [10:53] also the zd1211rw seens to be broken [10:54] in standard kernel tree [10:58] mcadetg: do you use nvidia or fglrx driver? [11:01] intel [11:02] Mobile 945GM/GMS [11:04] gah still not sorted out the /lib/firmware prob. The kernel doesn't want to load firmware from /lib/firmware but when I put firmware manually in /lib/firmware/$(uname -r) then it works [11:05] how does the firmware get loaded [11:05] is it via an udev rule? [11:06] couldn't find anything in /etc/udev/* [11:16] well ubuntu patched udev internally, i use a debian udev + firmware search change [11:20] Kano: thanks a lot [11:22] hello i have a question regarding to patch for the mac80211 core [11:24] this patch im talking about makes it possible to perform fragmentation attack with the aircrack-ng suite === rikai_ is now known as rikai [14:13] hi rtg [15:37] hi BenC [15:38] there are some problems with e1000e, it seems the newer version is not better than the kernel built in [15:53] also zd1211rw can lockup a system === superm1 is now known as superm1|away [16:15] Kano: I noticed that the e1000e we put in covers too many PCI ID's, so I'm going to cut them down. Can you be more specific about "not better"? [16:20] well for one tester his e1000e chip does not work anymore, not even with old kernels, dont know how that could happen [16:23] also i disalbed gfs, as it is still broken,not only the inclues, but 2 other things missing [16:23] i dont need it anyway... [16:24] somebody gets a lockup with his zd1211rw === superm1|away is now known as superm1 [17:01] i thought .26 was going to be for demo purposes only? === mkrufky is now known as mkrufky-lunch [18:25] on second thought, im stupid and recalled benC's ubuntu-next incorrectly [18:46] Hi! Could someone please check on Bug 256629? Now that I've got enough information and done some research I found out that the specific WLan-Card (IntelĀ® Wireless WiFi Link 5100 WLAN) is not supported under Kernel 2.6.24, but will be supported in 2.6.26. What is the correct status to set this bug to? Fix-Released? [18:50] Ampelbein: Intel is working on backporting the iwlwifi 5K driver to Hardy. It might be awhile yet. [18:54] rtg: so the correct status would be "in progress" until the driver comes out working? [18:58] Ampelbein: sounds about right. 'In Progress' bugs should also have someone assigned to them. I would do it but LP seems to be flakey today. I think I'll go have lunch and try again later. [21:13] now with linux-image-2.6.24-21-generic in hardy-updates, do I have to install it manually, or is update-manager waiting for some meta-package to be updated and pull in -21? [21:14] tormod: wait until linux-meta gets uploaded. the update-manager will annoy you when everything is consistent. [21:15] rtg: thanks [21:15] uptime [21:15] -EBADWINDOW === emma_ is now known as emma