Thread: [SSI] Building ssil
Brought to you by:
brucewalker,
rogertsang
From: Ramanath P. <ram...@wi...> - 2002-02-15 12:31:54
Attachments:
InterScan_Disclaimer.txt
|
Hello, While building the SSI on linux kernel 2.4.10-ac4, I am facing some problems. I followed the steps below. 1. Added the patch-2.4.10-ac4 onto the kernel 2.4.10 2. Then added the ssi patch "ssi-linux-2.4.10-ac4-v0.5.2.patch" 3. make menuconfig 4. make bzImage modules 5. make modules_install All the steps complete without errors. But after "make modules_install" the kernel modules are not copied into /lib/modules/2.4.10-ac4/kernel.... As a result, the ramdisk set up using mkinitrd.ssi fails. Can somebody give me hints on how to get the "make modules_install" work properly . I'm using a newly installed Red Hat 7.2 system. Many thanks Ramanath Pai |
From: John B. <joh...@co...> - 2002-02-15 18:13:49
|
Ramanath Pai wrote: > > Hello, > > While building the SSI on linux kernel 2.4.10-ac4, I am facing some > problems. > I followed the steps below. > > 1. Added the patch-2.4.10-ac4 onto the kernel 2.4.10 > 2. Then added the ssi patch "ssi-linux-2.4.10-ac4-v0.5.2.patch" > 3. make menuconfig > 4. make bzImage modules > 5. make modules_install > > All the steps complete without errors. But after "make modules_install" > the kernel modules are not copied into > /lib/modules/2.4.10-ac4/kernel.... > As a result, the ramdisk set up using mkinitrd.ssi fails. > > Can somebody give me hints on how to get the "make modules_install" work > properly . > I'm using a newly installed Red Hat 7.2 system. > > Many thanks > Ramanath Pai Nothing really springs to mind as to why this would fail without it spitting obvious error messages. (Except maybe that you didn't build *any* modules.) Could you send along your config file? Also, could you capture the output of "make modules_install" and send it to me? (Don't forget to redirect stderr, too.) John |
From: Ramanath P. <ram...@wi...> - 2002-02-18 03:49:58
|
Hello John, Please find attached the files .config and make_modules_install.out Thanks Ramanath John Byrne wrote: > Ramanath Pai wrote: > > > > Hello, > > > > While building the SSI on linux kernel 2.4.10-ac4, I am facing some > > problems. > > I followed the steps below. > > > > 1. Added the patch-2.4.10-ac4 onto the kernel 2.4.10 > > 2. Then added the ssi patch "ssi-linux-2.4.10-ac4-v0.5.2.patch" > > 3. make menuconfig > > 4. make bzImage modules > > 5. make modules_install > > > > All the steps complete without errors. But after "make modules_install" > > the kernel modules are not copied into > > /lib/modules/2.4.10-ac4/kernel.... > > As a result, the ramdisk set up using mkinitrd.ssi fails. > > > > Can somebody give me hints on how to get the "make modules_install" work > > properly . > > I'm using a newly installed Red Hat 7.2 system. > > > > Many thanks > > Ramanath Pai > > Nothing really springs to mind as to why this would fail without it > spitting obvious error messages. (Except maybe that you didn't build > *any* modules.) Could you send along your config file? Also, could you > capture the output of "make modules_install" and send it to me? (Don't > forget to redirect stderr, too.) > > John |
From: Kai-Min S. <Kai...@co...> - 2002-02-18 09:58:00
|
Hi Ramanath, Looking at your .config file, it seems like the only kernel modules you selected to build were the dummy and loop devices (they have =m beside them). Your scsi and network devices are selected to be built into the kernel. I don't think this should be a problem when you run the cluster_mkinitrd script, as long as you don't use the --with=<network_module> option, because it'll complain it can't find the module. If you're still having problems, please send us the output from your cluster_mkinitrd command. -Kai Ramanath Pai wrote: > Hello John, > > Please find attached the files .config and make_modules_install.out > > Thanks > Ramanath > > John Byrne wrote: > > > Ramanath Pai wrote: > > > > > > Hello, > > > > > > While building the SSI on linux kernel 2.4.10-ac4, I am facing some > > > problems. > > > I followed the steps below. > > > > > > 1. Added the patch-2.4.10-ac4 onto the kernel 2.4.10 > > > 2. Then added the ssi patch "ssi-linux-2.4.10-ac4-v0.5.2.patch" > > > 3. make menuconfig > > > 4. make bzImage modules > > > 5. make modules_install > > > > > > All the steps complete without errors. But after "make modules_install" > > > the kernel modules are not copied into > > > /lib/modules/2.4.10-ac4/kernel.... > > > As a result, the ramdisk set up using mkinitrd.ssi fails. > > > > > > Can somebody give me hints on how to get the "make modules_install" work > > > properly . > > > I'm using a newly installed Red Hat 7.2 system. > > > > > > Many thanks > > > Ramanath Pai > > > > Nothing really springs to mind as to why this would fail without it > > spitting obvious error messages. (Except maybe that you didn't build > > *any* modules.) Could you send along your config file? Also, could you > > capture the output of "make modules_install" and send it to me? (Don't > > forget to redirect stderr, too.) > > > > John > > |
From: Ramanath P. <ram...@wi...> - 2002-02-19 07:11:26
Attachments:
InterScan_Disclaimer.txt
|
Hi, I modularised the drivers - tlan, cpqfc and sym53c8xx during make menuconfig and I was able to setup the ramdisk using : mkinitrd.ssi --with=tlan /boot/initrd-2.4.X-ssi.img 2.4.X But the new kernel panics while booting. The last few console messages are : ----------- ds: no socket drivers created ! request_module[block-major-1]: Root fs not mounted VFS: Cannot open root device 100 or 01:00 Please append a correct "root=" boot option Kernel panic: VFS: unable to mount root fs on 01:00 ------------ The new stanza that I have added for ssil in lilo.conf is : image=/boot/vmlinuz-2.4.10-ssi initrd=/boot/initrd-2.4.10-ssi.img root=/dev/ram0 label=ssi-nogfs ramdisk=7000 append="init=/linuxrc" read-write The hardware setup that I use is -Compaq proliant system with 4.2GB x 2 scsi HDDs -FCAL for shared scsi storage. -Servernet for internode communication. Please give some inputs to correct this problem. Thanks Ramanath Kai-Min Sung wrote: > Hi Ramanath, > Looking at your .config file, it seems like the only kernel modules you > selected to build were the dummy and loop devices (they have =m beside them). > Your scsi and network devices are selected to be built into the kernel. I > don't think this should be a problem when you run the cluster_mkinitrd script, > as long as you don't use the --with=<network_module> option, because it'll > complain it can't find the module. > If you're still having problems, please send us the output from your > cluster_mkinitrd command. > > -Kai > > Ramanath Pai wrote: > > > Hello John, > > > > Please find attached the files .config and make_modules_install.out > > > > Thanks > > Ramanath > > > > John Byrne wrote: > > > > > Ramanath Pai wrote: > > > > > > > > Hello, > > > > > > > > While building the SSI on linux kernel 2.4.10-ac4, I am facing some > > > > problems. > > > > I followed the steps below. > > > > > > > > 1. Added the patch-2.4.10-ac4 onto the kernel 2.4.10 > > > > 2. Then added the ssi patch "ssi-linux-2.4.10-ac4-v0.5.2.patch" > > > > 3. make menuconfig > > > > 4. make bzImage modules > > > > 5. make modules_install > > > > > > > > All the steps complete without errors. But after "make modules_install" > > > > the kernel modules are not copied into > > > > /lib/modules/2.4.10-ac4/kernel.... > > > > As a result, the ramdisk set up using mkinitrd.ssi fails. > > > > > > > > Can somebody give me hints on how to get the "make modules_install" work > > > > properly . > > > > I'm using a newly installed Red Hat 7.2 system. > > > > > > > > Many thanks > > > > Ramanath Pai > > > > > > Nothing really springs to mind as to why this would fail without it > > > spitting obvious error messages. (Except maybe that you didn't build > > > *any* modules.) Could you send along your config file? Also, could you > > > capture the output of "make modules_install" and send it to me? (Don't > > > forget to redirect stderr, too.) > > > > > > John > > > > |
From: Aneesh K. K.V <ane...@di...> - 2002-02-19 07:16:42
|
Hi, I guess there is still some issue with the kernel you built. Check the network driver. BTW you should enable support of inital ramdisk and loop back. I guess you are not having the ramdisk driver check that also. -aneesh On Tue, 2002-02-19 at 12:42, Ramanath Pai wrote: > Hi, > > I modularised the drivers - tlan, cpqfc and sym53c8xx during make menuconfig and > I was able to setup the ramdisk using : > mkinitrd.ssi --with=tlan /boot/initrd-2.4.X-ssi.img 2.4.X > > But the new kernel panics while booting. > The last few console messages are : > ----------- > ds: no socket drivers created ! > request_module[block-major-1]: Root fs not mounted > VFS: Cannot open root device 100 or 01:00 > Please append a correct "root=" boot option > Kernel panic: VFS: unable to mount root fs on 01:00 > ------------ > > The new stanza that I have added for ssil in lilo.conf is : > > image=/boot/vmlinuz-2.4.10-ssi > initrd=/boot/initrd-2.4.10-ssi.img > root=/dev/ram0 > label=ssi-nogfs > ramdisk=7000 > append="init=/linuxrc" > read-write > > > The hardware setup that I use is > -Compaq proliant system with 4.2GB x 2 scsi HDDs > -FCAL for shared scsi storage. > -Servernet for internode communication. > > Please give some inputs to correct this problem. > > Thanks > Ramanath > > > Kai-Min Sung wrote: > > > Hi Ramanath, > > Looking at your .config file, it seems like the only kernel modules you > > selected to build were the dummy and loop devices (they have =m beside them). > > Your scsi and network devices are selected to be built into the kernel. I > > don't think this should be a problem when you run the cluster_mkinitrd script, > > as long as you don't use the --with=<network_module> option, because it'll > > complain it can't find the module. > > If you're still having problems, please send us the output from your > > cluster_mkinitrd command. > > > > -Kai > > > > Ramanath Pai wrote: > > > > > Hello John, > > > > > > Please find attached the files .config and make_modules_install.out > > > > > > Thanks > > > Ramanath > > > > > > John Byrne wrote: > > > > > > > Ramanath Pai wrote: > > > > > > > > > > Hello, > > > > > > > > > > While building the SSI on linux kernel 2.4.10-ac4, I am facing some > > > > > problems. > > > > > I followed the steps below. > > > > > > > > > > 1. Added the patch-2.4.10-ac4 onto the kernel 2.4.10 > > > > > 2. Then added the ssi patch "ssi-linux-2.4.10-ac4-v0.5.2.patch" > > > > > 3. make menuconfig > > > > > 4. make bzImage modules > > > > > 5. make modules_install > > > > > > > > > > All the steps complete without errors. But after "make modules_install" > > > > > the kernel modules are not copied into > > > > > /lib/modules/2.4.10-ac4/kernel.... > > > > > As a result, the ramdisk set up using mkinitrd.ssi fails. > > > > > > > > > > Can somebody give me hints on how to get the "make modules_install" work > > > > > properly . > > > > > I'm using a newly installed Red Hat 7.2 system. > > > > > > > > > > Many thanks > > > > > Ramanath Pai > > > > > > > > Nothing really springs to mind as to why this would fail without it > > > > spitting obvious error messages. (Except maybe that you didn't build > > > > *any* modules.) Could you send along your config file? Also, could you > > > > capture the output of "make modules_install" and send it to me? (Don't > > > > forget to redirect stderr, too.) > > > > > > > > John > > > > > > > > > ---- > > **************************Disclaimer************************************ > > Information contained in this E-MAIL being proprietary to Wipro Limited > is 'privileged' and 'confidential' and intended for use only by the > individual or entity to which it is addressed. You are notified that any > use, copying or dissemination of the information contained in the E-MAIL > in any manner whatsoever is strictly prohibited. > > > ******************************************************************** |
From: Brian J. W. <Bri...@co...> - 2002-02-19 19:03:11
|
Ramanath Pai wrote: > -Servernet for internode communication. SSI for Linux doesn't support Servernet. Currently, it only runs over TCP/IP, ala NSC 7.1.1b. > Please give some inputs to correct this problem. Can you send me your ramdisk image? -- Brian Watson | "Now I don't know, but I been told it's Linux Kernel Developer | hard to run with the weight of gold, Open SSI Clustering Project | Other hand I heard it said, it's Compaq Computer Corp | just as hard with the weight of lead." Los Angeles, CA | -Robert Hunter, 1970 mailto:Bri...@co... http://opensource.compaq.com/ |
From: John B. <joh...@co...> - 2002-02-19 19:25:15
|
"Brian J. Watson" wrote: > > Ramanath Pai wrote: > > -Servernet for internode communication. > > SSI for Linux doesn't support Servernet. Currently, it only runs over > TCP/IP, ala NSC 7.1.1b. > > > Please give some inputs to correct this problem. > > Can you send me your ramdisk image? > Also, your /etc/modules.conf, /etc/fstab, and your latest .config would help. John |
From: Ramanath P. <ram...@wi...> - 2002-02-20 12:18:07
Attachments:
InterScan_Disclaimer.txt
|
Hello, I was able to boot the node with the new ssi kernel. "Brian J. Watson" wrote: > Ramanath Pai wrote: > > -Servernet for internode communication. > > SSI for Linux doesn't support Servernet. Currently, it only runs over > TCP/IP, ala NSC 7.1.1b. > > > Please give some inputs to correct this problem. > > Can you send me your ramdisk image? > > -- > Brian Watson | "Now I don't know, but I been told it's > Linux Kernel Developer | hard to run with the weight of gold, > Open SSI Clustering Project | Other hand I heard it said, it's > Compaq Computer Corp | just as hard with the weight of lead." > Los Angeles, CA | -Robert Hunter, 1970 > > mailto:Bri...@co... > http://opensource.compaq.com/ > > _______________________________________________ > ssic-linux-devel mailing list > ssi...@li... > https://lists.sourceforge.net/lists/listinfo/ssic-linux-devel |
From: Ramanath P. <ram...@wi...> - 2002-02-20 12:32:01
Attachments:
InterScan_Disclaimer.txt
|
Hello, I just was able to boot the node with the new ssi kernel ! I have just selected the following items to be built into the kernel in addition to the configuration file I had previously mailed : SCSI generic support SCSI logging facility Thank you all for the assistance extended to me. +Ramanath "Brian J. Watson" wrote: > Ramanath Pai wrote: > > -Servernet for internode communication. > > SSI for Linux doesn't support Servernet. Currently, it only runs over > TCP/IP, ala NSC 7.1.1b. > > > Please give some inputs to correct this problem. > > Can you send me your ramdisk image? > > -- > Brian Watson | "Now I don't know, but I been told it's > Linux Kernel Developer | hard to run with the weight of gold, > Open SSI Clustering Project | Other hand I heard it said, it's > Compaq Computer Corp | just as hard with the weight of lead." > Los Angeles, CA | -Robert Hunter, 1970 > > mailto:Bri...@co... > http://opensource.compaq.com/ > > _______________________________________________ > ssic-linux-devel mailing list > ssi...@li... > https://lists.sourceforge.net/lists/listinfo/ssic-linux-devel |
From: Brian J. W. <Bri...@co...> - 2002-02-19 18:59:45
|
"Aneesh Kumar K.V" wrote: > > Hi, > > I guess there is still some issue with the kernel you built. Check the > network driver. BTW you should enable support of inital ramdisk and > loop back. I guess you are not having the ramdisk driver check that > also. > > -aneesh I think he already has initial ramdisk and loopback mounts enabled. CONFIG_BLK_DEV_INITRD is a prerequisite for enabling CONFIG_SSI, and mkinitrd.ssi would bomb if CONFIG_BLK_DEV_LOOP weren't enabled. -- Brian Watson | "Now I don't know, but I been told it's Linux Kernel Developer | hard to run with the weight of gold, Open SSI Clustering Project | Other hand I heard it said, it's Compaq Computer Corp | just as hard with the weight of lead." Los Angeles, CA | -Robert Hunter, 1970 mailto:Bri...@co... http://opensource.compaq.com/ |