View Single Post

   
  #4 (permalink)  
Old 02-20-2008, 07:22 AM
+Alan Hicks+
 
Posts: n/a
Default Re: VIP (Very Interesting Problem)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

In alt.os.linux.slackware, Handover Phist dared to utter,
> Relevant lilo.conf entries in Slack:


<snip>
> image = /boot/vmlinuz_2.6.8.1
> root = /dev/sda1
> label = Linux
> other = /dev/hda1
> label = Windows
> boot-as = 0x80
> image = /vmlinuz
> root = /dev/sda1
> label = Experimental
> image = /boot/vmlinuz-2.4.21-4.EL
> root = /dev/hdb1
> label = RH_Devel


I don't see anything wrong provided all your kernels are under /boot on
the Slackware install, but I would suggest removing the ide-scsi
things, as they are bad form with 2.6 kernels.

> and 2.4.21 in RHEL, but modules for each system are stored on separate
> drives.


Alright, let's try this. Since you've already got that 2.4 kernel for
RHEL in place under /boot, copy it's modules over to
/lib/modules/2.4.whatever and setup lilo.conf such that Slackware uses
that kernel instead of 2.6.8.1, reboot, and see what happens.
Alternatively, you could attempt to start RHEL with your 2.6.8.1 kernel
and see what it does.

> Sda is my boot device. Bios hands off to it and lilo in the MBR takes
> over. no other bootloader is installed. Kernels for any linux system I
> run get copied to the /boot directory of / (/dev/sda1) manually after
> the other linux is installed because either lilo is braindead or I
> haven't done my homework properly.


Question. Is /boot it's own partition and have you be any chance
confirmed that you have free space there? Perhaps your kernel is
corrupted somehow?

> There is no initrd in use in the Slack system, all needed drivers
> are compiled directly into the kernel, including ext[23] support. Slack
> then mounts sda1 as root, and RHEL mounts hdb1. At this point all is
> good, except that Slack then cant execute scripts needed to set basic
> params and such. I have no way of knowing at this point what exactly is
> missing in the boot process since that kernel is monolithic.


Like I said above, try another kernel. Shoot, try using the sata.i
kernel from the 10.1 install disks or something. That might get you a
good bit further.

- --
It is better to hear the rebuke of the wise,
Than for a man to hear the song of fools.
Ecclesiastes 7:5
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFCTvx0vgVcFKpJf4gRAgeHAJ0bfbrciKvjINJrhfYw7u MTcBE8ZwCffkfu
1wLlsLT4Bd70eODWQtXmPt0=
=V8hD
-----END PGP SIGNATURE-----
Reply With Quote