Kernel and ticrate problem

[BehaartesEtwas]

Quote:WARNING: Couldn't open directory /lib/modules/2.6.36-zen1: No such file or directory

I don't understand why the modules directory for your new kernel does not get created. as I understand you do run the make commands as root, so it should be writeable.

maybe your virtual hard disk is full? "df -h" gives you the amount of free space... also try creating that missing directory by hand (normally make modules_install should do this):

Code:

mkdir /lib/modules/2.6.36-zen1

(as root of course)

[taavi56]

No hard wasn't full. 10gb free.

[taavi56]

Same thing, it doesn't find any hard disk's and same error like before if i want install. Similar error like there i forget to write down real error

[root@test linux-2.6.36]# make install modules_install
sh /usr/src/linux-2.6.36/arch/x86/boot/install.sh 2.6.36-zen1 arch/x86/boot/bzImage \
System.map "/boot"
WARNING: Couldn't open directory /lib/modules/2.6.36-zen1: No such file or directory
FATAL: Could not open /lib/modules/2.6.36-zen1/modules.dep.temp for writing: No such file or

[BehaartesEtwas]

what happens if you do:

Code:

mkdir /lib/modules/2.6.36-zen1

[taavi56]

It installs the kernel and everything seems to be ok but in reboot kernel doesn't find hard drive.

[BehaartesEtwas]

ok, then you need to look at your kernel configuration. I wrote a howto recently how to avoid this problem:

http://wiki.fragaholics.de/index.php/EN:Kernel_Configuration_avoid_initrd

let me know whether you find it useful and if it worked for you...

[taavi56]

I tryd that but no success, same shit. I dont know what i do wrong but i before tested many kernels without any problems and now nothing works

[BehaartesEtwas]

can you please post your kernel config as attachment (don't post it directly, it's too long)? and also post here the output of the commands "mount" (without any options) and "lspci" executed in your system with a working kernel.

[taavi56]

Kernel current config http://pastebin.com/ajQU6B1t (post to an attatchment is not allowed, bad filetype)

mount

Code:

[root@alienservers boot]# mount
/dev/mapper/VolGroup00-LogVol00 on / type ext3 (rw)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
/dev/sdb1 on /boot type ext3 (rw)
tmpfs on /dev/shm type tmpfs (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)

lspci

Code:

[root@alienservers boot]# lspci
00:00.0 Host bridge: Intel Corporation 5500 I/O Hub to ESI Port (rev 13)
00:01.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 1 (rev 13)
00:03.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 3 (rev 13)
00:07.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 7 (rev 13)
00:08.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 8 (rev 13)
00:09.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 9 (rev 13)
00:0a.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 10 (rev 13)
00:13.0 PIC: Intel Corporation 5520/5500/X58 I/O Hub I/OxAPIC Interrupt Controller (rev 13)
00:14.0 PIC: Intel Corporation 5520/5500/X58 I/O Hub System Management Registers (rev 13)
00:14.1 PIC: Intel Corporation 5520/5500/X58 I/O Hub GPIO and Scratch Pad Registers (rev 13)
00:14.2 PIC: Intel Corporation 5520/5500/X58 I/O Hub Control Status and RAS Registers (rev 13)
00:14.3 PIC: Intel Corporation 5520/5500/X58 I/O Hub Throttle Registers (rev 13)
00:16.0 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 13)
00:16.1 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 13)
00:16.2 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 13)
00:16.3 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 13)
00:16.4 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 13)
00:16.5 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 13)
00:16.6 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 13)
00:16.7 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 13)
00:1a.0 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #4
00:1a.1 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #5
00:1a.2 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #6
00:1a.7 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI Controller #2
00:1c.0 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express Root Port 1
00:1c.4 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express Root Port 5
00:1c.5 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express Root Port 6
00:1d.0 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #1
00:1d.1 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #2
00:1d.2 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #3
00:1d.7 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI Controller #1
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 90)
00:1f.0 ISA bridge: Intel Corporation 82801JIR (ICH10R) LPC Interface Controller
00:1f.3 SMBus: Intel Corporation 82801JI (ICH10 Family) SMBus Controller
00:1f.5 IDE interface: Intel Corporation 82801JI (ICH10 Family) 2 port SATA IDE Controller #2
01:00.0 VGA compatible controller: ASPEED Technology, Inc. ASPEED Graphics Family (rev 10)
02:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection
03:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection
08:00.0 RAID bus controller: 3ware Inc 9690SA SAS/SATA-II RAID PCIe (rev 01)

[BehaartesEtwas]

firstly, you have your file system driver (ext3) is compiled as a module, that does not work. compile it fixed into the kernel with a [*].
secondly, you have a raid controller and apparently use it for your boot disk. I don't exactly know how to compile all necessary drivers fixed into the kernel, but your config doesn't look like you did that right either.

that's what the howto was trying you to tell... maybe you should read it again ;-)

[taavi56]

ok i read that again