[00:03] i think it's dir where main Makefile is, so just kernel source path [00:08] But it's clearly not set in your pastebin example - otherwise ld wouldn't be looking for /ubuntu/omnibook/sections.ids, it'd be looking for /usr/src/linux-source-2.6.32/ubuntu/omnibook/sections.ids (and not failing). [00:15] that's call from Makefile.standalone "$(MAKE) -C /usr/src/linux-source-2.6.32 SUBDIRS=$(PWD) modules" [00:17] and that's how PWD is set - looks ok for me "PWD = $(shell pwd)" [00:18] Yeah. But at the point of the ld call, it's become "", which isn't very useful :) [00:28] ok, got it... it sets PWD only if makefile is called directly [00:31] so, the way to fix it is to move PWD out of "ifeq ($(KERNELRELEASE),)" or some better way but i'm poor coder so i've no idea [02:17] ive installed the 2.6.32.3 kernel on my karmic system from http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.32.3/ but these kernels dont have the staging drivers kompiled. is there any way to do this afterwards? [02:18] i.e. how do i compile a module that is located in linux-source-2.6.32/drivers/staging/et131x and load it in a precompiled kernel from the kernel-ppa ? [02:19] is this possible or do i have to recompile the whole kernel? [02:44] hi anyone here [02:45] aahicnow, that's a tough question [02:45] lol [02:46] i was looking for help with internet stick in 9.10 and wasw told to come here [02:47] anyone had any success getting them working with 9.10 [02:48] aahicnow, your best bet is to check in the hardware databases, that can tell you if others had success with it, I don't really know what internet stick is :) [02:49] celluar based internet modem [02:50] it was working in easypeasy(8.0)??? and 9.04 but will not work in 9.10 === MTeck-ricer is now known as MTecknology === SEJeff_ is now known as SEJeff_home === asac__ is now known as asac === asac__ is now known as asac === Whoopie_ is now known as Whoopie [12:48] hi! is there a howto for packaging single kernel modules? got some dvb-s2 usb device that ships with a GPLv2 driver which isn't in the kernels v4l driver collection, so i'd like to package that one. [13:56] do kernel builds on any architectures still need to know where to find /boot? [14:41] lamont: huh? [14:41] that's grub's job [14:59] RoyK: it wasn't always... hence the question === yofel_ is now known as yofel === chris-qBT__ is now known as chris-qBT