vanilla kernel----- go away

[PabloTwo]

I'm (attempting) a rebuild of kernel-2.6.38.2-14.fc15.src.rpm on my F12 32-bit system. My only problem, so far, is lack of sufficient disk space to complete the compile/build. With the SRPM installed, I'm left with only 3.0GB on my / partition.

I've uninstalled a few unwanted and or seldom used rpm packages, have gone through /var/log with an industrial strength cleaner, moved a couple of folders heavy in graphics and music files over to an ntfs partition for the time being to free up as much disk space as I know how to do without doing major surgery.

I'm fiddling with the spec file and adding several "--without something" options to the "rpmbuild -bb ....." line. The idea is to build only a single .i686 kernel package with only the attendant kernel-devel and kernel-headers files in tow. I've also disabled the building of the debuginfo packages, which consume massive amounts of space. I appear to accomplishing that, except the build also includes a "vanilla-<version>" along with the standard kernel build.

I believe the compile for the standard kernel completes (but I'm not totally sure of that) and the compile halts when the "vanilla" kernel BUILD folder reaches 483MB in size and the hdd available space hits 0%.

Can someone help me figure out how to twiddle the spec file and/or add include a command line option to the rpmbuild command to prevent the vanilla kernel from building? I believe that if I can kill vanilla then I might at least stand a chance to complete the build and packaging of the standard kernel. I'll even be willing to chop off the kernel-devel and kernel-headers packages if that's what it takes to get the job done.

The only reason for building this new a kernel on an F12 system is to get an updated "coretemp.ko" kmod (and the updated 'depmods' to that particular module). I'm not savy to a way to just build a new, updated, coretemp kmod for my existing kernel.

And the reason for wanting an updated coretmep kmod is to attempt to get lm_sensors (which I have already updated to the latest v3.3.0) to be able to read the cpu temperature on my new motherboard. Yes, I built a whole new computer a few days ago to replace my previous machine when it's MB died due to a short in the Audigy2 ZS audio card. Though I ordered a 500GB SATA3 and 1TB SATAII hdd for the new build, I'm currently just running it with the old 160GB SATA1.5 hdd installed. My next 'upgrade' of Fedora will have way more room to play in than my current 8.3GB /.

The new MB is an ASRock P67 Pro3, hosting an i5-2500k (Sandy Bridge). The F12 version of lm-sensors couldn't find a single thing on this new MB with "sensors-detect". The 3.3.0 version at least found the Intel cpu thermal interface and declared "coretemp" as the module to use, but it refuses to install, spitting out an error about "no device found".

Paul

[leigh123linux]

I'm (attempting) a rebuild of kernel-2.6.38.2-14.fc15.src.rpm on my F12 32-bit system. My only problem, so far, is lack of sufficient disk space to complete the compile/build. With the SRPM installed, I'm left with only 3.0GB on my / partition.

I've uninstalled a few unwanted and or seldom used rpm packages, have gone through /var/log with an industrial strength cleaner, moved a couple of folders heavy in graphics and music files over to an ntfs partition for the time being to free up as much disk space as I know how to do without doing major surgery.

I'm fiddling with the spec file and adding several "--without something" options to the "rpmbuild -bb ....." line. The idea is to build only a single .i686 kernel package with only the attendant kernel-devel and kernel-headers files in tow. I've also disabled the building of the debuginfo packages, which consume massive amounts of space. I appear to accomplishing that, except the build also includes a "vanilla-<version>" along with the standard kernel build.

I believe the compile for the standard kernel completes (but I'm not totally sure of that) and the compile halts when the "vanilla" kernel BUILD folder reaches 483MB in size and the hdd available space hits 0%.

Can someone help me figure out how to twiddle the spec file and/or add include a command line option to the rpmbuild command to prevent the vanilla kernel from building? I believe that if I can kill vanilla then I might at least stand a chance to complete the build and packaging of the standard kernel. I'll even be willing to chop off the kernel-devel and kernel-headers packages if that's what it takes to get the job done.

The only reason for building this new a kernel on an F12 system is to get an updated "coretemp.ko" kmod (and the updated 'depmods' to that particular module). I'm not savy to a way to just build a new, updated, coretemp kmod for my existing kernel.

And the reason for wanting an updated coretmep kmod is to attempt to get lm_sensors (which I have already updated to the latest v3.3.0) to be able to read the cpu temperature on my new motherboard. Yes, I built a whole new computer a few days ago to replace my previous machine when it's MB died due to a short in the Audigy2 ZS audio card. Though I ordered a 500GB SATA3 and 1TB SATAII hdd for the new build, I'm currently just running it with the old 160GB SATA1.5 hdd installed. My next 'upgrade' of Fedora will have way more room to play in than my current 8.3GB /.

The new MB is an ASRock P67 Pro3, hosting an i5-2500k (Sandy Bridge). The F12 version of lm-sensors couldn't find a single thing on this new MB with "sensors-detect". The 3.3.0 version at least found the Intel cpu thermal interface and declared "coretemp" as the module to use, but it refuses to install, spitting out an error about "no device found".

Paul
I don't bother tweaking the spec

rpmbuild --rebuild --with baseonly --without debuginfo --target=`uname -m` kernel-2.6.39-0.rc2.git3.0.fc16.src.rpmWhy does it matter about spare space on / , you should use your /home directory.

[Seve]

If you haven't already, check for any space that could be reclaimed from your /var/tmp -- /tmp and try

rpmbuild -ba kernel.spec && sed -i 's|{?_with_vanilla: 1}|{?_with_vanilla: 0}|' kernel.spec

or edit the original kernel.spec

You can also do/try the same for others you may also not want to build.

e.g.

%{?_without_debug: 0} %{?!_without_debug: 1}

%{?_without_debug: 1} %{?!_without_debug: 0}

[PabloTwo]

Thanks,

@Leigh, I'll try your method, except the use the kernel SRPM I've already got downloaded. Using standard LVM install of Fedora (since first install of FC5). My /home partition is under /, so whatever free disk space is displayed under /, is also available to what I'm doing in /home. I'm doing the rebuild in $HOME. I think on one of my several tries, I specified "--with baseonly", and it still tried to compile the vanilla kernel as well.

The kernel SRPM itself resides on a USB thumbdrive, so as not to take up hdd space itself.

@Seve, yes, I've been playing around with those "with" and "without" options and the 1's and 0's. I didn't touch the one you mentioned about "vanilla" though, although I had a hard look at that configuration line. Already cleaned up /var/tmp.

I may end up trying a combination of both, whatever works.

---------- Post added at 09:51 PM ---------- Previous post was at 07:32 PM ----------

Well, the bottom line: Just not enough available hdd space on my Linux / partition to complete this kernel build. I guess I miss guessed the thing with the "vanilla" kernel. Doing a listing on the BUILD folder shows that "vanilla" kernel comes early on. Tried various permutations of your suggestions and it always appears. Checking the hdd space consumption during the compile:
BASH:~/-> ls rpmbuild/BUILD/kernel-2.6.38.fc12/
linux-2.6.38.i686 vanilla-2.6.38
BASH:~/-> du -sh rpmbuild/BUILD/kernel-2.6.38.fc12/vanilla-2.6.38/
483M rpmbuild/BUILD/kernel-2.6.38.fc12/vanilla-2.6.38/ <== early in the compile
BASH:~/-> du -sh rpmbuild/BUILD/kernel-2.6.38.fc12/linux-2.6.38.i686/
1.5G rpmbuild/BUILD/kernel-2.6.38.fc12/linux-2.6.38.i686/
BASH:~/-> du -sh rpmbuild/BUILD/kernel-2.6.38.fc12/linux-2.6.38.i686/
2.2G rpmbuild/BUILD/kernel-2.6.38.fc12/linux-2.6.38.i686/
BASH:~/-> du -sh rpmbuild/BUILD/kernel-2.6.38.fc12/linux-2.6.38.i686/
2.4G rpmbuild/BUILD/kernel-2.6.38.fc12/linux-2.6.38.i686/
BASH:~/-> du -sh rpmbuild/BUILD/kernel-2.6.38.fc12/linux-2.6.38.i686/
2.6G rpmbuild/BUILD/kernel-2.6.38.fc12/linux-2.6.38.i686/
BASH:~/-> du -sh rpmbuild/BUILD/kernel-2.6.38.fc12/linux-2.6.38.i686/
2.9G rpmbuild/BUILD/kernel-2.6.38.fc12/linux-2.6.38.i686/
BASH:~/-> du -sh rpmbuild/BUILD/kernel-2.6.38.fc12/linux-2.6.38.i686/
3.1G rpmbuild/BUILD/kernel-2.6.38.fc12/linux-2.6.38.i686/
BASH:~/-> du -sh rpmbuild/BUILD/kernel-2.6.38.fc12/linux-2.6.38.i686/
3.2G rpmbuild/BUILD/kernel-2.6.38.fc12/linux-2.6.38.i686/
BASH:~/-> du -sh rpmbuild/BUILD/kernel-2.6.38.fc12/linux-2.6.38.i686/
3.4G rpmbuild/BUILD/kernel-2.6.38.fc12/linux-2.6.38.i686/
BASH:~/-> du -sh rpmbuild/BUILD/kernel-2.6.38.fc12/linux-2.6.38.i686/
3.5G rpmbuild/BUILD/kernel-2.6.38.fc12/linux-2.6.38.i686/ <== compile stops here

and in another attempt...

BASH:~/-> ls rpmbuild/BUILD/kernel-2.6.38.fc12/ <== immediately after starting the build
linux-2.6.38
BASH:~/-> ls rpmbuild/BUILD/kernel-2.6.38.fc12/ <== several seconds later
linux-2.6.38.i686 vanilla-2.6.38
BASH:~/-> du -sh rpmbuild/BUILD/kernel-2.6.38.fc12/vanilla-2.6.38/
483M rpmbuild/BUILD/kernel-2.6.38.fc12/vanilla-2.6.38/
BASH:~/-> rm -r rpmbuild/BUILD/kernel-2.6.38.fc12/vanilla-2.6.38 <== even tried this
BASH:~/-> ls rpmbuild/BUILD/kernel-2.6.38.fc12/
linux-2.6.38.i686
BASH:~/-> du -hs rpmbuild/BUILD/kernel-2.6.38.fc12/linux-2.6.38.i686/
2.2G rpmbuild/BUILD/kernel-2.6.38.fc12/linux-2.6.38.i686/
BASH:~/-> du -hs rpmbuild/BUILD/kernel-2.6.38.fc12/linux-2.6.38.i686/
2.4G rpmbuild/BUILD/kernel-2.6.38.fc12/linux-2.6.38.i686/
BASH:~/-> ls rpmbuild/BUILD/kernel-2.6.38.fc12/
linux-2.6.38.i686
BASH:~/-> du -hs rpmbuild/BUILD/kernel-2.6.38.fc12/linux-2.6.38.i686/
2.7G rpmbuild/BUILD/kernel-2.6.38.fc12/linux-2.6.38.i686/
BASH:~/-> du -hs rpmbuild/BUILD/kernel-2.6.38.fc12/linux-2.6.38.i686/
3.1G rpmbuild/BUILD/kernel-2.6.38.fc12/linux-2.6.38.i686/
BASH:~/-> du -hs rpmbuild/BUILD/kernel-2.6.38.fc12/linux-2.6.38.i686/
3.3G rpmbuild/BUILD/kernel-2.6.38.fc12/linux-2.6.38.i686/
BASH:~/-> du -hs rpmbuild/BUILD/kernel-2.6.38.fc12/linux-2.6.38.i686/
3.4G rpmbuild/BUILD/kernel-2.6.38.fc12/linux-2.6.38.i686/
BASH:~/-> du -hs rpmbuild/BUILD/kernel-2.6.38.fc12/linux-2.6.38.i686/
3.7G rpmbuild/BUILD/kernel-2.6.38.fc12/linux-2.6.38.i686/ <== ran out of disk space here

Looks like I'll have to wait until I get the new 500GB hdd installed and then equipped with a newer version of Fedora before I can find out if the latest kernel will help support the latest version of lm_sensors on my "bleeding edge" motherboard. At least I can easily check temperatures on my hdd(s) and on my new Nvidia graphics card. The kmod-nvidia I had in F12 didn't know what to do with the new card. Neither did nouveau. I was stuck with VESA until I installed the v270.26 driver from Nvidia's site.

Thanks again for your suggestions.

[leigh123linux]

Thanks,

@Leigh, I'll try your method, except the use the kernel SRPM I've already got downloaded. Using standard LVM install of Fedora (since first install of FC5). My /home partition is under /, so whatever free disk space is displayed under /, is also available to what I'm doing in /home. I'm doing the rebuild in $HOME. I think on one of my several tries, I specified "--with baseonly", and it still tried to compile the vanilla kernel as well.

The kernel SRPM itself resides on a USB thumbdrive, so as not to take up hdd space itself.

@Seve, yes, I've been playing around with those "with" and "without" options and the 1's and 0's. I didn't touch the one you mentioned about "vanilla" though, although I had a hard look at that configuration line. Already cleaned up /var/tmp.

I may end up trying a combination of both, whatever works.

---------- Post added at 09:51 PM ---------- Previous post was at 07:32 PM ----------

Well, the bottom line: Just not enough available hdd space on my Linux / partition to complete this kernel build. I guess I miss guessed the thing with the "vanilla" kernel. Doing a listing on the BUILD folder shows that "vanilla" kernel comes early on. Tried various permutations of your suggestions and it always appears. Checking the hdd space consumption during the compile:
BASH:~/-> ls rpmbuild/BUILD/kernel-2.6.38.fc12/
linux-2.6.38.i686 vanilla-2.6.38
BASH:~/-> du -sh rpmbuild/BUILD/kernel-2.6.38.fc12/vanilla-2.6.38/
483M rpmbuild/BUILD/kernel-2.6.38.fc12/vanilla-2.6.38/ <== early in the compile
BASH:~/-> du -sh rpmbuild/BUILD/kernel-2.6.38.fc12/linux-2.6.38.i686/
1.5G rpmbuild/BUILD/kernel-2.6.38.fc12/linux-2.6.38.i686/
BASH:~/-> du -sh rpmbuild/BUILD/kernel-2.6.38.fc12/linux-2.6.38.i686/
2.2G rpmbuild/BUILD/kernel-2.6.38.fc12/linux-2.6.38.i686/
BASH:~/-> du -sh rpmbuild/BUILD/kernel-2.6.38.fc12/linux-2.6.38.i686/
2.4G rpmbuild/BUILD/kernel-2.6.38.fc12/linux-2.6.38.i686/
BASH:~/-> du -sh rpmbuild/BUILD/kernel-2.6.38.fc12/linux-2.6.38.i686/
2.6G rpmbuild/BUILD/kernel-2.6.38.fc12/linux-2.6.38.i686/
BASH:~/-> du -sh rpmbuild/BUILD/kernel-2.6.38.fc12/linux-2.6.38.i686/
2.9G rpmbuild/BUILD/kernel-2.6.38.fc12/linux-2.6.38.i686/
BASH:~/-> du -sh rpmbuild/BUILD/kernel-2.6.38.fc12/linux-2.6.38.i686/
3.1G rpmbuild/BUILD/kernel-2.6.38.fc12/linux-2.6.38.i686/
BASH:~/-> du -sh rpmbuild/BUILD/kernel-2.6.38.fc12/linux-2.6.38.i686/
3.2G rpmbuild/BUILD/kernel-2.6.38.fc12/linux-2.6.38.i686/
BASH:~/-> du -sh rpmbuild/BUILD/kernel-2.6.38.fc12/linux-2.6.38.i686/
3.4G rpmbuild/BUILD/kernel-2.6.38.fc12/linux-2.6.38.i686/
BASH:~/-> du -sh rpmbuild/BUILD/kernel-2.6.38.fc12/linux-2.6.38.i686/
3.5G rpmbuild/BUILD/kernel-2.6.38.fc12/linux-2.6.38.i686/ <== compile stops here

and in another attempt...

BASH:~/-> ls rpmbuild/BUILD/kernel-2.6.38.fc12/ <== immediately after starting the build
linux-2.6.38
BASH:~/-> ls rpmbuild/BUILD/kernel-2.6.38.fc12/ <== several seconds later
linux-2.6.38.i686 vanilla-2.6.38
BASH:~/-> du -sh rpmbuild/BUILD/kernel-2.6.38.fc12/vanilla-2.6.38/
483M rpmbuild/BUILD/kernel-2.6.38.fc12/vanilla-2.6.38/
BASH:~/-> rm -r rpmbuild/BUILD/kernel-2.6.38.fc12/vanilla-2.6.38 <== even tried this
BASH:~/-> ls rpmbuild/BUILD/kernel-2.6.38.fc12/
linux-2.6.38.i686
BASH:~/-> du -hs rpmbuild/BUILD/kernel-2.6.38.fc12/linux-2.6.38.i686/
2.2G rpmbuild/BUILD/kernel-2.6.38.fc12/linux-2.6.38.i686/
BASH:~/-> du -hs rpmbuild/BUILD/kernel-2.6.38.fc12/linux-2.6.38.i686/
2.4G rpmbuild/BUILD/kernel-2.6.38.fc12/linux-2.6.38.i686/
BASH:~/-> ls rpmbuild/BUILD/kernel-2.6.38.fc12/
linux-2.6.38.i686
BASH:~/-> du -hs rpmbuild/BUILD/kernel-2.6.38.fc12/linux-2.6.38.i686/
2.7G rpmbuild/BUILD/kernel-2.6.38.fc12/linux-2.6.38.i686/
BASH:~/-> du -hs rpmbuild/BUILD/kernel-2.6.38.fc12/linux-2.6.38.i686/
3.1G rpmbuild/BUILD/kernel-2.6.38.fc12/linux-2.6.38.i686/
BASH:~/-> du -hs rpmbuild/BUILD/kernel-2.6.38.fc12/linux-2.6.38.i686/
3.3G rpmbuild/BUILD/kernel-2.6.38.fc12/linux-2.6.38.i686/
BASH:~/-> du -hs rpmbuild/BUILD/kernel-2.6.38.fc12/linux-2.6.38.i686/
3.4G rpmbuild/BUILD/kernel-2.6.38.fc12/linux-2.6.38.i686/
BASH:~/-> du -hs rpmbuild/BUILD/kernel-2.6.38.fc12/linux-2.6.38.i686/
3.7G rpmbuild/BUILD/kernel-2.6.38.fc12/linux-2.6.38.i686/ <== ran out of disk space hereLooks like I'll have to wait until I get the new 500GB hdd installed and then equipped with a newer version of Fedora before I can find out if the latest kernel will help support the latest version of lm_sensors on my "bleeding edge" motherboard. At least I can easily check temperatures on my hdd(s) and on my new Nvidia graphics card. The kmod-nvidia I had in F12 didn't know what to do with the new card. Neither did nouveau. I was stuck with VESA until I installed the v270.26 driver from Nvidia's site.

Thanks again for your suggestions.
Join fedoeproject (everyone is welcome) , this gives you access to koji:cool:.
Just upload the srpm and build it at koji.

[PabloTwo]

Join fedoeproject (everyone is welcome) , this gives you access to koji.
Just upload the srpm and build it at koji.
That's a great suggestion. But for me, with gruesomely slow dialup, it's not very practical. Take, for example, the kernel SRPM file I'm trying to rebuild, which is ~72MB in size. When things are working good, my download rate works out to be about 10MB per hour.. That would have taken in the neighborhood of 7 hours to download from koji from home.

Since my upload speed is always something slower than my download speed, I figure at least 8 hours to upload the SRPM file to koji from home. I downloaded the file in the first place while at the public library w/free wifi in a town 25 miles south of where I live on my wifes wifi enabled laptop. We generally only make a once a week trip into "town". As you can see, though doable, it just wouldn't be a very convenient setup. I'm thankful she bought herself that laptop, which at least gives us a once a week window for grabbing those biggish file downloads, saving hours and hours and hours of download time at home.

[vallimar]

If you have the spare memory, you can try to temporarily mount your rpm build directory as a tmpfs mount. That will cause it to use memory (up to 50% by default I believe) instead of your filesystem.
The way that the srpm works, you'll always have the vanilla and linux directories, though the vanilla directory is just there for patching against. I believe they are initially created as a hardlink copy to save space.

Also, if your usb drive is large enough, you could mount your build directory to that as well just for
the kernel build instead of using tmpfs.