---------- Original Message ---------------------------------- From: Ken Schneider Reply-To: suse-linux-e@suse.com Date: Tue, 01 Nov 2005 11:13:14 -0500

On Tue, 2005-11-01 at 03:54 -0800, Matt Stamm wrote:

...

---------- Original Message ---------------------------------- From: Peter Nikolic Date: Tue, 1 Nov 2005 11:41:07 +0000

...

On Tuesday 01 November 2005 11:32, Matt Stamm wrote:

...

Hello, Thank you all for the help on this so farThis is an update to a previous post/thread.I'm still unable to install Suse 10 on my brandnew PC. The PC has a AMD Sempron 64 cpu, 512 mem80gig SATA harddrive.

Based on the my prevoius post and your responses(thank you very much!) I beleive the problem isdue to GRUB and my SATA drive, but I am not anexpert in the area.

Sorry for the lengthy post, but I wanted to put as much info as possible

Here's what I've found...

- my SUSE 10 install fails on the initial boot after the first CD with "GRUB Loading stag1.5".

Just a couple of more questions. If you boot to install cd can you boot the installed system from there?

When I boot the install cd and then boot to the hard drive i get the "GRUB Loading Stage1.5" message and everything stops

Also How long have you been using linux, not necessarily just SuSE, but in general?

I've only use Suse, and have used Suse since 2002 when I installed 8.1. I've been using 8.1 ever since.

One thing that you can try, not sure if I recommended this already, boot to the rescue system and make a note of which kernel modules are loaded that give access to the SATA drive, if at all, (let us know if the drive is available in rescue mode).

Yes, the drive is available in rescue mode. I enter rescue mode, login as root, and using the command line I see what appears to be a normal linux file structure (/bin, /etc, /home, etc.)

This/these module(s) will need to be added to the initrd modules list so they are loaded during the initial boot sequence. This can be done from the rescue system using chroot to gain access to the installed system as though you booted to the installed system.

I don't understand. I've never used chroot

If you're installed system has /boot on a seperate partition it will need to be mounted after the root filesystem is mounted.

/boot is on the same system. Using the rescue system, when I go to /boot, its empty.

-- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998

-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com

Ken, thank for your response. I'm not sure what to do now?? Matt