There was an article? I might need to check back a few posts...

Another build is in progress. I'm going to figure this out yet.

Thanks for everyone's help so far.

Okay, update time...

I've been gone for a while, so I haven't been able to work on this until now. Even using a previous config file, no change in status.

So, I'm wondering, might it be that there's no /boot/initrd.img-3.2.11-custom file on my drive? In fact, there's no mention of init or initrd anywhere in the process of building and installing the kernel... I'm starting to wonder if there could be an issue with that.

From what I know about init, off the top of my head, I think this file looks like something that would tell init how to load the kernel or modules. Is this correct? If so, maybe init isn't loading everything. So, how would I get an initrd image for my kernel?

Old config files are just a start. You can use them as is but should, if you want to get the features of the new kernel, add more features by make menuconfig.

Can you post a step by step of how you are trying to do this? It may help to see if you are missing any important steps.

1 members found this post helpful.

Okay, here's how I'm trying to do this:

1. Download and extract the source tarball. If I'm compiling source that I already have, I skip this step.

2. In a terminal, start the configuration with make menuconfig. I go around, selecting anything that might apply. When using a previous config file, I ran make menuconfig and used the "Load alternate configuration file" to load the file I needed. I then fine tuned it.

3. I then run make to compile the kernel.

4. Then I run the command "make modules && sudo make modules_install" to compile and install the modules.

5. Then, to install the kernel, I run make install. I then have three new files in /boot for my kernel.

6. To let the boot loader know there's a new kernel on my hard drive, I run sudo update-grub. I then reboot into my not-exactly-functioning kernel.

OK try this for step 2, cp /boot/config-WHATEVERYOURKERNELVERSIONIS .config and then make menuconfig. Be aware you need to be in the appropriate folder and you change the name of the bolded section to the name of your old config file.

For step 3 try this. fakeroot make-kpkg --jobs=2 --initrd --append-to-version=-custom --revision=insertdatehere kernel_image kernel_headers modules_image

At this stage I would just try and let it compile with the old config in place. If that doesn't work then try adding features. I suspect that what is happening is you are changing the config and either accidently removing something or not applying the old config correctly.

Let us know how you go.

Okay, sorry it took a while, but my computer crashed before the first compile attempt finished, and on try two there was an error. Same error for try 3. Here it is:

I have no idea what that means. But there are two new .deb files in my downloads folder. Although I think it wouldn't be a good idea to install them, unless you say it's okay.

I'll do a compile on my system and see what happens. If it works ok I'll post a complete step by step for you. It may take a while so don't expect anything until the end of the weekend.

Okay, I'll keep a watch on this thread. Thanks for your help.

I should be working but the tv is showing a repeat of motor racing from a few weeks ago is on TV so I'm watching the v8 utes racing while I compiled 3.2.11

OK here is the process I followed.
1. cd into the extracted folder.
2. cp /boot/config-3.2.0-2-amd64 .config
3. make menuconfig
4. select exit on make menuconfig, unless you need to enable things like non-free drivers etc in which case you will need to go through the lists and select the things you need. Make sure you save the config after enabling anything.
5. fakeroot make-kpkg --jobs=2 --initrd --append-to-version=-custom --revision=yyyymmdd kernel_image kernel_headers modules_image Change the bold to suit your purpose, append-to-version=-custom is what you want to call it mine is called cobber make sure you keep the - infront of the name. revision= is the date you compile on write it in this order year month date yyyymmdd.
6. let it work through the process and if there are no errors listed at the end install the debs.

I just went through this with 3.2.11 and it works a treat apart from the fact I didn't do my wireless driver which I will do now.

I've got a problem over here. My computer complained that it didn't know what the jobs option was. So I omitted it. But then, that Alsa module failed again. I forgot to mention that I omitted it last time, too.

So, I guess I have a problem. If that jobs option is important, the Alsa module won't work without it. But nothing works when I do use it.

The jobs just means if you have a dual core you can do 2 jobs, if you have a quad core yo can do 4 jobs.

I'm at a loss as to why alsa is failing, unless I see a complete (and they are extremely long) log for the job I doubt I can offer any more help.

Yeah, the log was pretty long... maybe I should save it as a file and send you a download link?

ok save the log and post the link, I'll look at it when I can

I've been a bit slow with remembering something. From memory Ubuntu doesn't use alsa anymore it uses Pulse Audio. You may be able to use the new debs anyway.

In that case, I guess I'll try it. If it fails, I can always try posting the log.

I'll report back when done...

Edit:

Exact same error as before. I'm starting to think the build method is irrelevant here, I think I need to check the configuration a little more. However, because I'm using the same configuration as a known working kernel, I'm not sure.
It's getting late, so I guess I'll have to think up a solution in the morning. But I will find a solution.
Maybe I need to go at this a different way. I mean, what if it's Ubuntu that is the problem? Perhaps I should install Debian on this free space I have on my hard drive left over from a Linux Mint installation, and then build MATE and Linux 3.2 on top of that.