Problem on New Kernel Installation
hello,
i am a new user to Red Hat Linux Enterprise Edition 4.1 I am trying to install a new kernel 2.6.15.6 on my Linux. I have compiled the kernel and copied bzImage to /boot partition. Also I have modified the grub.conf file it is listed as # grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. # root (hd0,2) # kernel /vmlinuz-version ro root=/dev/sda6 # initrd /initrd-version.img #boot=/dev/sda default=2 timeout=5 splashimage=(hd0,2)/grub/splash.xpm.gz hiddenmenu title Red Hat Enterprise Linux 2.6.15.6 root (hd0,2) kernel /vmlinuz-2.6.15.6.img ro root=LABEL=/ rhgb quiet initrd /initrd-2.6.15.6.img title Red Hat Enterprise Linux AS (2.6.9-5.ELsmp) root (hd0,2) kernel /vmlinuz-2.6.9-5.ELsmp ro root=LABEL=/ rhgb quiet initrd /initrd-2.6.9-5.ELsmp.img title Red Hat Enterprise Linux AS-up (2.6.9-5.EL) root (hd0,2) kernel /vmlinuz-2.6.9-5.EL ro root=LABEL=/ rhgb quiet initrd /initrd-2.6.9-5.EL.img title windows xp rootnoverify (hd0,0) chainloader +1 this is listing of /dev/sda [root@localhost grub]# fdisk /dev/sda Command (m for help): p Disk /dev/sda: 80.0 GB, 80026361856 bytes 255 heads, 63 sectors/track, 9729 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sda1 * 1 2550 20482843+ c W95 FAT32 (LBA) /dev/sda2 2551 5100 20482875 c W95 FAT32 (LBA) /dev/sda3 5101 5138 305235 83 Linux /dev/sda4 5139 9729 36877207+ 5 Extended /dev/sda5 5139 7688 20482843+ 83 Linux /dev/sda6 7689 8963 10241406 83 Linux /dev/sda7 8964 9090 1020096 82 Linux swap /dev/sda8 9091 9729 5132736 83 Linux I am unable to understand the problem. Could anybody please help??? |
OK, you compiled kernel 2.6.15 and modified grub.conf. Kernel 2.6.15 compiled successfully and assuming you installed the modules along with the kernel. Changes to grub.conf seem right. All right ! Now WHERE IS THE PROBLEM ? You never mentioned any !!?
Is it that you don't get the option to boot into the new kernel or is it that the new kernel boots but panics at some stage or ......... ???? |
Thanks for th reply.
after uncompressing the kernel it gives me error message as follows insmod : error inserting 'lib/ata_piix.ko' -1 mkrootdev : label / not found umount /sys failed : 16 mount : error 2 mounting ext3 mount : error 2 mounting none here is a screen shot of my /etc/fstab # This file is edited by fstab-sync - see 'man fstab-sync' for details LABEL=/ / ext3 defaults 1 1 LABEL=/boot /boot ext3 defaults 1 2 none /dev/pts devpts gid=5,mode=620 0 0 none /dev/shm tmpfs defaults 0 0 LABEL=/home /home ext3 defaults 1 2 LABEL=/opt /opt ext3 defaults 1 2 none /proc proc defaults 0 0 /dev/sda1 /mnt/win_1 auto defaults 0 0 /dev/sda2 /mnt/win_2 auto defaults 0 0 none /sys sysfs defaults 0 0 LABEL=SWAP-sda7 swap swap defaults 0 0 /dev/fd0 /media/floppy auto pamconsole,fscontext=system_u:object_r:removable_t,exec,noauto,managed 0 0 ~ |
Recheck your configuration i.e your /usr/src/linux/.config file. You root filesystem is on a SCSI or SATA disk, therefore, you should either have the SATA and/or SCSI support compiled in the kernel or if you are using initrd to boot, you should create a new initrd image for the new kernel.
Looking into grub.conf file from you first posting and the error messages you've posted, the problem seems to be 'lib/ata_piix.ko' module. Check your initrd for this module and make sure it exists, if not, create another to include the required libs not just ata_piix.ko . Otherwise recompile kernel to include the necessary support into the kernel itself. |
I have already created a initrd file using mkinitrd command.
As I am new to this PC in my company, i am unaware whether its SATA or PATA. Is there any way to check this out? I am currently running Red Hat Linux Enterprise 4 with 2.6.9.5 kernel. The problem will be - i am not accessible to the hardware :( not allowed to open the cabinet of CPU. |
I managed to find out my hardware.
I have SCSI hard disk installed on my PC. so I have now enabled the SCSI support in the configuration. But now this has given rise to new error solving the previous ones... the last message that appears on the screen when i boot is Enforcing mode requested but no policy loaded.Halting Now Kernel Panic : No syncing : Attempted to kill init !!! Please help... |
can anyone please help me with this ???
|
Sure...
(1) The LABEL= syntax has never worked for me. I simply identify devices by their address. (2) "Attempting to kill init" really means that the init process died, which it is not allowed to do. The reasons will be found in the messages that precede this one. |
I am unable to understand the reason.
Can you please tell me that how to trace that from which file the statement got printed. Then maybe I will be able to get it out. The error was... Enforcing the mode requested but not policy loaded. Halting now. What is really meaning of this??? |
Hey guys,
thanx a lot for all your support. I have cracked the problem. It was due to SELinux. I disabled SELinux in /etc/selinux/config file. And now my installation worked perfectly fine :) Thanks a lot.... |
All times are GMT -5. The time now is 04:29 AM. |