• Welcome to Overclockers Forums! Join us to reply in threads, receive reduced ads, and to customize your site experience!

Compling Kernel Issues

Overclockers is supported by our readers. When you click a link to make a purchase, we may earn a commission. Learn More.

Shelnutt2

Overclockers Team Content Editor
Joined
Jun 17, 2005
Location
/home/
First off I'll say I'm trying to compile the kerrighed kernel. (It's the latest 2.6.30 git, git://mirrors.git.kernel.org/cluster/kerrighed/kernel master ) However the issue I'm running into, I've never seen before and it might not be directly related to the kerrighed patches. I sent in to the dev mailing list but I figure no harm in posting here to see if someone else has had this problem with the 2.6.30 kernel.

It keeps saying I'm out of space when I'm compiling this. I've never run out of space when compiling a kernel something seems wrong. (I run gentoo, so I've compiled my far share of kernels). I'm compiling this from my home directory which is /dev/sda4 . Before I ran "make -j3" I had 1.8 gigs free. After, and when it tells me I'm out of room there is still 285mb left. But that fact that it takes 1.6 gigs and it's not compiled, tells me something is very wrong here.


Code:
  CC      drivers/video/efifb.o                                                             
  CC      drivers/video/output.o                                                            
  LD      drivers/video/fb.o                                                                
  LD      drivers/video/built-in.o                                                          
  LD      drivers/built-in.o                                                                
  LD      vmlinux.o                                                                         
vmlinux.o: final close failed: No space left on device                                      
make: *** [vmlinux.o] Error 1                                                               
shelnutt@gentoo-64:~/kerrighed/kernel/master$ df -m                                         
Filesystem           1M-blocks      Used Available Use% Mounted on                          
/dev/sda8                16276      9387      6064  61% /                                   
udev                        10         1        10   2% /dev                                
/dev/sda4                10077      9280       285  98% /home                               
/dev/sda1                30726     29097      1630  95% /mnt/windows                        
/dev/sda3               166793    134825     31968  81% /mnt/storage                        
/dev/sda7                11265     10198       496  96% /mnt/debian                         
shm                        498         1       498   1% /dev/shm                            
/dev/sda6                  342        85       240  27% /boot                               
shelnutt@gentoo-64:~/kerrighed/kernel/master$ make clean                                    
  CLEAN   /home/shelnutt/kerrighed/kernel/master                                            
  CLEAN   arch/x86/kernel/acpi/realmode
  CLEAN   arch/x86/kernel/cpu
  CLEAN   arch/x86/kernel
  CLEAN   arch/x86/vdso
  CLEAN   drivers/char
  CLEAN   drivers/video/logo
  CLEAN   firmware
  CLEAN   init
  CLEAN   kernel
  CLEAN   lib
  CLEAN   usr
  CLEAN   .tmp_versions
shelnutt@gentoo-64:~/kerrighed/kernel/master$ df -m
Filesystem           1M-blocks      Used Available Use% Mounted on
/dev/sda8                16276      9387      6064  61% /
udev                        10         1        10   2% /dev
/dev/sda4                10077      7706      1860  81% /home
/dev/sda1                30726     29097      1630  95% /mnt/windows
/dev/sda3               166793    134825     31968  81% /mnt/storage
/dev/sda7                11265     10198       496  96% /mnt/debian
shm                        498         1       498   1% /dev/shm
/dev/sda6                  342        85       240  27% /boot
shelnutt@gentoo-64:~/kerrighed/kernel/master$


Lastly, something else. I was told on the mailing list that the i386 and x86_64 were merged into just x86. This was done in the 2.6.24 linux kernel? I googled and apparently thats so. However in my gentoo 2.6.29 sources I have both a x86 and a x86_64. If there is only a x86. How do I know if I am compiling for 64bit or not? (Kerrighed does support 64bit and it's been the main branch for over a year)
 
Last edited:
arch/x86_64/boot/bzImage is a symlink to arch/x86/boot/bzImage. Not sure whether that is standard kernel behavior or part of Gentoo patches. Either way, the actual kernel you're copying to /boot is in /usr/src/linux/arch/x86/boot. Not sure how your build could possibly require 1GB disk space, though.

What does du tell you?
Code:
fsl linux # pwd -P
/usr/src/linux-2.6.29-gentoo-r5
fsl linux # ls -l arch/x86_64/boot
total 0
lrwxrwxrwx 1 root root 22 Jul 28 15:41 bzImage -> ../../x86/boot/bzImage
fsl linux # du -sh
596M    .
fsl linux # du -sh ./*
20K     ./COPYING
96K     ./CREDITS
14M     ./Documentation
4.0K    ./Kbuild
112K    ./MAINTAINERS
60K     ./Makefile
312K    ./Module.symvers
20K     ./README
4.0K    ./REPORTING-BUGS
1.5M    ./System.map
121M    ./arch
1.5M    ./block
6.3M    ./crypto
0       ./diff
243M    ./drivers
2.4M    ./firmware
55M     ./fs
20M     ./include
472K    ./init
656K    ./ipc
7.8M    ./kernel
3.7M    ./lib
4.0M    ./mm
16K     ./modules.order
32M     ./net
108K    ./samples
3.0M    ./scripts
1.2M    ./security
43M     ./sound
208K    ./usr
116K    ./virt
6.7M    ./vmlinux
9.8M    ./vmlinux.o

How to tell whether your kernel is 64-bit I'm not sure, but in my .config there are these lines:
Code:
CONFIG_64BIT=y
# CONFIG_X86_32 is not set
CONFIG_X86_64=y
CONFIG_X86=y
CONFIG_ARCH_DEFCONFIG="arch/x86/configs/x86_64_defconfig
 
Last edited:
First off I'll say I'm trying to compile the kerrighed kernel. (It's the latest 2.6.30 git, git://mirrors.git.kernel.org/cluster/kerrighed/kernel master ) However the issue I'm running into, I've never seen before and it might not be directly related to the kerrighed patches. I sent in to the dev mailing list but I figure no harm in posting here to see if someone else has had this problem with the 2.6.30 kernel.

It keeps saying I'm out of space when I'm compiling this. I've never run out of space when compiling a kernel something seems wrong. (I run gentoo, so I've compiled my far share of kernels). I'm compiling this from my home directory which is /dev/sda4 . Before I ran "make -j3" I had 1.8 gigs free. After, and when it tells me I'm out of room there is still 285mb left. But that fact that it takes 1.6 gigs and it's not compiled, tells me something is very wrong here.


Lastly, something else. I was told on the mailing list that the i386 and x86_64 were merged into just x86. This was done in the 2.6.24 linux kernel? I googled and apparently thats so. However in my gentoo 2.6.29 sources I have both a x86 and a x86_64. If there is only a x86. How do I know if I am compiling for 64bit or not? (Kerrighed does support 64bit and it's been the main branch for over a year)

I cant speak to gentoo but I can tell you that 2.5 gigs of space on CentOS does not work. I actually had to mount an empty partition into the /usr/src partition just to get it to work. All told the compiling took about 5 gigs of space if I remember correctly but the actual rpms were small when they were finished.

From what I could tell it expanded all the source before making the rpm
 
Apparently it needed ~3 gigs to compile

Code:
shelnutt@gentoo-64:/mnt/storage/linux/kernel$ du -sh
3.3G    .

I moved it to a large partition.

Now however I'm getting a weird error, that I've never encountered before. It involves USB.

Code:
generic-usb: probe of 0003:1038:0100.0004 failed with error -22

This is right after it detects my keyboard on 003:1038:0100.0003 . Maybe there is a new USB setting in 2.6.30 compared to 2.6.29, that I missed?
 
Back