On Thu, 29 Mar 2007 20:11:56 +1200
Volker Kuhlmann <[EMAIL PROTECTED]> wrote:

> On Thu 29 Mar 2007 10:10:45 NZST +1200, Steve Holdoway wrote:
> 
> > menu.lst entry. Cut and pasted from suse /boot/grub
> 
> > title           SuSE Linux 10.2
> > root            (hd0,6)
> > kernel          /boot/vmlinuz-2.6.18.8-0.1-default root=/dev/hda7 vga=0x314 
> > splash=silent showopts
> > initrd          /boot/initrd-2.6.18.8-0.1-default
> 
> Looks good. Just checking: there is no extra partition for /boot?
No
> Do the vmlinuz and initrd files exist?
Yes
> Is grub able to access them?
Given that it's booted the SuSE kernel, I'd say yes.
> 
> > Yes, and it booted fine when grub looked to partition 7 (SuSE), not 0
> >(Ubuntu).
> 
> You mean it worked once? That means the install worked and breakage
> occured later. Check for corrupted files: rpm -V kernel-default
> The initrd can't be verified, but easily recreated: mk_initrd
> That reads file(s) under /etc/sysconfig, eg what modules to include.
I mean it worked when I installed SuSE, and it took over the boot process and 
rewrote the mbr Unfortunately, 1) I do not want SuSE to control the boot 
process, and 2) It only picked up ubuntu and ignored the other releases on the 
machine. When I reset grub to look at ubuntu ( grub root (hd0,0) setup (hd0) ) 
, I can boot ubuntu, fedora 6, debian sarge and etch, freebsd, but NOT SuSE.
> 
> > The first problem was that I was sharing swap across linux distros,
> > and the default boot code has a resume=<swap device> option on the
> > boot line.
> 
> Good point, sharing suspend-to-swap between distros is pushing the
> button on thermonuclear meltdown.
> 
> > Now, I've got a line further, and the system locks up after the
> > successful 'Loading required kernel modules' message.
> 
> Is this before init runs? No, grep in /etc gives
> /etc/init.d/boot.loadmodules, which loads modules listed as mandatory in
> /etc/sysconfig/kernel
> 
> If it locks up during that, I'd say kernel module problem with whatever
> you're loading there. If just after, look in /etc/init.d/boot.d/ for
> whatever is run next.
> 
> Volker
> 
> -- 
> Volker Kuhlmann                       is list0570 with the domain in header
> http://volker.dnsalias.net/   Please do not CC list postings to me.
Well, I asked the question as I don't know what SusSE does that's different to 
all other mainstream linux distros, and freebsd. I've detailed exactly the 
point that the system locks up in, and can think of no reason for it to stop at 
this point. I'm booting SuSE, I'm partway through the boot process, and I lock 
up after the point mentioned above.

Any suggestions would be gratefully received.

Steve
Should I complain? It took over 24 hours for this post to be published.

Reply via email to