[01:15] <hcfd> Hi. I'm trying to solve a problem with a multiport serial card. I had it working under latest Ubuntu 10.10, stock kernel but under 10.04LTS, latest kernel, I cannot get it configured and working properly. I am using kernel parameter 8250.nr_uarts=8 to allow me use of both onboard ports and the 6 on a PCI card. I tried to replicate my 10.10 setserial config under 10.04 and no joy at all. Could this be a kernel issue?
[14:44] <hallyn> latest 2.6.38-3 kernel seems to not create good ad-hoc networks.  booting 2.6.27-12 works.  Gotta try a few more times to be sure it's the kernel, but so far it seems to be
[15:05] <hallyn> (that is separate from an apparent inability of the free broadcom brcm80211 driver to do ad-hoc, which is in itself unfortunate - is the b43 driver really meant to be blacklisted or was that my fault in the past?)
[15:30] <hyperair> probably your fault. it doesn't look like it's blacklisted on my system
[15:30] <hyperair> and i don't have a broadcom chip
[17:12] <ohsix> i'll just edit them in place, thankfully it's only a pin for firefox and aptitude so far; and i don't see having more than 8 or so ever
[17:17] <ohsix> that's it, moving this channel to its own window :D
[17:25] <kumaanki> hi everyone..
[17:26] <kumaanki> which package contains the header files linux/init.h ?
[17:26] <mjg59> The kernel source
[17:27] <mjg59> Are you trying to build userspace or a kernel module?
[17:27] <kumaanki> i have downloaded the kernel source and now i was trying to build a single funsoft driver file..
[17:29] <kumaanki> so how should i build it?
[17:31] <mjg59> If you want to build it against your current kernel then you need linux-headers
[17:31] <mjg59> Don't try to build it against unconfigured kernel source unless you're building your own kernel as well
[17:32] <kumaanki> can i not compile individual modules from kernel source..?
[17:33] <mjg59> Not in any meaningful way
[17:34] <ohsix> copying the config for the running kernel and using the same compiler isn't enough? (i've never had it work the few times i tried, never looked into why)
[17:34] <kumaanki> hmm...ok. i mean say if some of the drivers are updated in upcoming kernels, will i have to re-install the whole kernel( i mean building the whole kernel itself?)
[17:35] <mjg59> Typically, yes
[17:35] <mjg59> Unless the driver has been backported to an older kernel
[17:36] <kumaanki> oh ok.
[17:37] <ohsix> mjg59: any idea why it doesn't work? need the deps in tree? it says symbols are missing, typically; even if you run depmod and use the same config
[17:38] <ohsix> is it because patches are missing or something, cuz i tried it out of the apt-get source tree once; didn't use the debian/* stuff to build it though
[17:40] <kumaanki> mjg59: even after installing the linux headers, the linux/init.h file is not found.
[17:41] <mjg59> kumaanki: What, precisely, are you trying to do?
[17:41] <kumaanki> I am inside the kernel source dir ubuntu-maverick/drivers/usb
[17:42] <kumaanki> i am inside the kernel source directory ubuntu-maverick/drivers/usb
[17:42] <mjg59> That's not going to work
[17:42] <kumaanki> why..?
[17:42] <mjg59> Because the build system doesn't work that way
[17:43] <kumaanki> but it should be able to build it if the linux headers are present
[17:43] <mjg59> To a first approximation, you can't build drivers from different kernel versions
[17:43] <kumaanki> the funsoft.c file does not demand anything else than linux headers from the current kernel
[17:44] <kumaanki> the source code is for the same kernel version
[17:44] <mjg59> So why isn't it included already?
[17:45] <kumaanki> the kernel headers might not be part of standard installation i guess
[17:45] <ohsix> i think he means the funsoft module
[17:46] <ohsix> ie. why do you need to build it yourself
[17:46] <kumaanki> ohsix: yes.
[17:47] <kumaanki> was trying to learn how the driver code builds and compiles and the code for funsoft seems understandable so thought of compiling it
[17:47] <ohsix> ah
[17:47] <ohsix> well it's not straight forward if you don't start with your own kernel already
[17:47] <mjg59> You can't just gcc a kernel module
[17:47] <mjg59> You need to use the kernel buildsystem
[17:48] <mjg59> So, from the top of the kernel source tree, you can do make drivers/usb/serial/funsoft.ko
[17:48] <mjg59> And that will build the kernel module against the configuration of the source tree
[17:48] <kumaanki> oh, let me try this then.. )
[17:48] <mjg59> Which may not match the configuration of the kernel you're running
[17:48] <mjg59> So you may end up with a module you can't load
[17:51] <kumaanki> ok. i want to try my hands on kernel code.
[17:53] <ohsix> you might want to play with qemu and your own kernel tree :D it can run images directly, and it's a virtual machine; less disruptive
[17:53] <kumaanki> cool. i am able to build the .ko file now. but the insmod on the generated funsoft.ko fails. probably that's because of the mismatch in kernel versions
[17:54] <mjg59> dmesg will tell you what the failure is
[17:54] <mjg59> If you want to build against a kernel with a longer version string, then you'll need to do something like make EXTRAVERSION=-2-686 drivers/usb/serial/funsoft.ko
[17:55] <kumaanki> dmesg does not log any messages pertaining to the error in insmod 
[17:55] <kumaanki> i checked the output of dmesg