If I try to boot Linux from the hard disk, it will flash "Grub loading stage 1.5..." and then the screen goes black and it just sits there. What I meant by the two copies of stage2 was that fresh from an install, I ran the command: "md5sum /boot/grub/stage2 /usr/lib/grub/stage2" and it came back with two different hashes. I didn't think that was supposed to be the case. If I select "Windows" from the GRUB menu, XP comes up just fine. Linux, however, just sits. It seems to be something similar to this: https://bugzilla.novell.com/show_bug.cgi?id=223773 But I don't know if it is exactly or not... My menu.lst looks like this (for this email, I am not including all the YAST-inserted comments): default 0 timeout 8 gfxmenu (hd0,5)/boot/message title openSUSE 10.2 root (hd0,5) kernel /boot/vmlinuz-2.6.18-34-default root=/dev/sda title Windows rootnoverify (hd0,0) chainloader (hd0,0)+1 title Failsafe -- openSUSE 10.2 -- My device.map is fairly simple: (hd0,0) /dev/sda -- My grub.conf says: setup --stage2=/boot/grub/stage2 (hd0) (hd0,5) quit -- Again, any help is appreciated. --- "Joe Morris (NTM)" wrote:

Christopher Dick wrote:

...

I recently installed SuSE 10.2 on a couple of machines using SATA drives and they each seem to be exhibiting a similar problem.

Which are???

...

They won't boot unless I choose "Boot installed system" from the CD.

So you are booting from the cd/dvd? Are you booting from the mbr of your HDs? Is your BIOS pointing to the HD to boot from?

...

I did a check, and right from the get-go the two copies of Stage2 are not the same. MD5 comes up with a different hash for each, though I was under the impression that they were supposed to be the same.

...

GRUB definitely loads, but just stops cold after

...

Stage 1.5. AFTER? stage 1.5 is the stage it loads to read the file system to read

I believe they are specific for the system so that would be normal unless these are exactly the same hardware, etc., in both. the the rest of its info. This means it has to looking in the right place.

...

On the machine that also has Windows, the WinXP install comes up just fine. But Linux is dead.

This makes no sense to me. Does it start from grub? If so, this has to be after stage 2. Then the problem has to be in either your menu.lst or possibly your device.map. We would need more specific info to troubleshoot your problem, hopefully info that is not conflicting with itself. ;-)

-- Joe Morris Registered Linux user 231871 running openSUSE 10.2 x86_64

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

____________________________________________________________________________________ Don't pick lemons. See all the new 2007 cars at Yahoo! Autos. http://autos.yahoo.com/new_cars.html -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

--- frank nelson wrote:

--- Christopher Dick wrote:

...

My menu.lst looks like this (for this email, I am not including all the YAST-inserted comments):

default 0 timeout 8 gfxmenu (hd0,5)/boot/message

title openSUSE 10.2 root (hd0,5) kernel /boot/vmlinuz-2.6.18-34-default root=/dev/sda

Your problem is here. this dhould read;

root=/dev/sda6

and should have some other parameters like;

vga=0x317 selinux=0 resume=/dev/hda2 splash=verbose showopts

I'm trying not to top-post, so hopefully it will be easier to read and understand. Okay, well, I did a complete reinstall again and this is what Yast built for me: # Modified by YaST2. Last modification on Sun Feb 11 17:14:22 UTC 2007 default 0 timeout 8 gfxmenu (hd0,5)/boot/message ###Don't change this comment - YaST2 identifier: Original name: linux### title openSUSE 10.2 root (hd0,5) kernel /boot/vmlinuz-2.6.18.2-34-default root=/dev/sda6 vga=0x31a resume=/dev/sda5 splash=silent showopts initrd /boot/initrd-2.6.18.2-34-default ###Don't change this comment - YaST2 identifier: Original name: windows### title Windows rootnoverify (hd0,0) chainloader (hd0,0)+1 ###Don't change this comment - YaST2 identifier: Original name: failsafe### title Failsafe -- openSUSE 10.2 root (hd0,5) kernel /boot/vmlinuz-2.6.18.2-34-default root=/dev/sda6 vga=normal showopts ide=nodma apm=off acpi=off noresume nosmp noapic maxcpus=0 edd=off 3 initrd /boot/initrd-2.6.18.2-34-default --

...

My device.map is fairly simple:

(hd0,0) /dev/sda

This is also wrong: Should read

(hd0) /dev/sda

The device.map is now the way it should be according to your message.

...

-- My grub.conf says:

setup --stage2=/boot/grub/stage2 (hd0) (hd0,5) quit

This is correct.

My grub.conf is still the same. Unfortunately, its the same result. In order to boot Linux, I have to use the "boot installed system" option from either the rescue or installation on the CD and select /dev/sda6 as the boot partition. If I do that, it comes up just fine. If I select "OpenSuSE 10.2" from the menu booting without the CD, I get a black screen and it sits there. ____________________________________________________________________________________ 8:00? 8:25? 8:40? Find a flick in no time with the Yahoo! Search movie showtime shortcut. http://tools.search.yahoo.com/shortcuts/#news -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

--- Carl Hartung wrote:

On Sun February 11 2007 14:06, Christopher Dick wrote: <snip>

...

If I select "OpenSuSE 10.2" from the menu booting without the CD, I get a black screen and it sits there.

The good news is grub is installed correctly, otherwise you'd not be getting a boot menu. ;-)

The first repair ought to be:

Look under /boot to make sure these symbolic links exist:

vmlinuz --> vmlinuz-2.6.18.2-34-default initrd --> initrd-2.6.18.2-34-default

Then, in /boot/grub/menu.lst, point to the links instead. To do this:

Reduce 'vmlinuz-2.6.18.2-34-default' to 'vmlinuz' everywhere it occurs. Likewise, reduce all instances of 'initrd-2.6.18.2-34-default' to 'initrd'.

This way, booting via grub won't fail after you next update the kernel.

Sorry if this has already been posted, but while you're editing /boot/grub/menu.lst can you copy/paste and post your /etc/fstab?

Here is my fstab: /dev/sda6 / ext3 acl,user_xattr 1 1 /dev/sda7 /home ext3 acl,user_xattr 1 2 /dev/sda1 /windows/C ntfs ro,users,gid=users,umask=0002,nls=utf8 0 0 /dev/sda5 swap swap defaults 0 0 proc /proc proc defaults 0 0 sysfs /sys sysfs noauto 0 0 debugfs /sys/kernel/debug debugfs noauto 0 0 usbfs /proc/bus/usb usbfs noauto 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 ____________________________________________________________________________________ Bored stiff? Loosen up... Download and play hundreds of games for free on Yahoo! Games. http://games.yahoo.com/games/front -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

--- Carl Hartung wrote:

<snip>

Please boot into SUSE using your CD/DVD, open a shell, 'su' to superuser permissions, run 'fdisk -l /dev/sda' and copy/paste to post the results here.

regards,

Carl

Here is the output from fdisk: 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 4462 35840983+ 7 HPFS/NTFS /dev/sda2 4463 9729 42307177+ f W95 Ext'd (LBA) /dev/sda5 4463 4724 2104483+ 82 Linux swap / Solaris /dev/sda6 4725 6747 16249716 83 Linux /dev/sda7 6748 9729 23952883+ 83 Linux As near as I can tell, everything is just fine. But grub just doesn't like Linux on my system. Again, it may be related to this bug: https://bugzilla.novell.com/show_bug.cgi?id=223773 that was pointed out to me in the suselinuxsupport.de forums, but I don't know for sure. ____________________________________________________________________________________ Want to start your own business? Learn how on Yahoo! Small Business. http://smallbusiness.yahoo.com/r-index -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

--- Carl Hartung wrote:

On Sun February 11 2007 23:27, Christopher Dick wrote:

...

As near as I can tell, everything is just fine. But grub just doesn't like Linux on my system.

I agree. This stuff all looks fine.

...

Again, it may be related to this bug:

https://bugzilla.novell.com/show_bug.cgi?id=223773

There's an easy way to check this listed in the bug report... compare the md5sum of the 'active' stage2 against the original:

open a shell, 'su' to superuser permissions and:

'cd /boot/grub' 'md5sum stage2' (my result: 66797a774c25457f3b5e7c7f0920db9f stage2) 'md5sum /usr/lib/grub/stage2' (my result: 66797a774c25457f3b5e7c7f0920db9f /usr/lib/grub/stage2)

Well, I guess its not this bug, because: md5sum /boot/grub/stage2 /usr/lib/grub/stage2 66797a774c25457f3b5e7c7f0920db9f /boot/grub/stage2 66797a774c25457f3b5e7c7f0920db9f /usr/lib/grub/stage2 I guess its something else. Previous installations had different hashes, I know. Perhaps if I set the grub.conf to point to the /usr/lib/grub version instead of the /boot/grub version? ____________________________________________________________________________________ Have a burning question? Go to www.Answers.yahoo.com and get answers from real people who know. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

--- Carl Hartung wrote:

I don't think that's going to help, Christopher, I'm beginning to think there's something more elusive going on here. Questions are starting to run through my mind like... "Is the BIOS capable of addressing high addresses on that disk?" and "Has he verified the disk is being addressed using LBA and not CHS?" That sort of thing...

What the mainboard make, model and serial number?... or do you have a link to a data sheet on the manufacturer's website?

The system is a Shuttle XPC model sd32g2 with an Intel 945G+ICH7 chipset. The basic specs can be found at: http://hq1.shuttle.com/products_page03-spec.jsp?PLLI=9&PI=247 The drive is a Seagate SATA 3.0Gb/s model ST380811AS and I have a Lite-on PATA DVD burner. Based on what you wrote above, I went into the BIOS and checked the disk settings. My two choices for drive detection were "auto" and "large." It was on "auto." I set it to large, and again, Windows comes up fine, but Linux just sits. So I changed it back. ____________________________________________________________________________________ We won't tell. Get more on shows you hate to love (and love to hate): Yahoo! TV's Guilty Pleasures list. http://tv.yahoo.com/collections/265 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

--- Carl Hartung wrote:

On Mon February 12 2007 22:32, Christopher Dick wrote:

...

Shuttle XPC model sd32g2

Hi Christopher,

Can you please follow the instructions, below, then post the actual mainboard and any revision numbers?... also the BIOS version?

http://eu.shuttle.com/en/desktopdefault.aspx/tabid-396/629_read-871/searchca...

I tried figuring it out but don't have time this a.m. to make a project of it. ;-)

I have the SD32G2 with an FD32 v1.x motherboard. That's actually what it says on the motherboard... v1.x The BIOS revision is sd23s306, the latest. Thank you for helping me try to figure this out. ____________________________________________________________________________________ Don't pick lemons. See all the new 2007 cars at Yahoo! Autos. http://autos.yahoo.com/new_cars.html -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Mon, 12 Feb, 2007 at 19:32:53 -0800, Christopher Dick wrote:

--- Carl Hartung wrote:

...

I don't think that's going to help, Christopher, I'm beginning to think there's something more elusive going on here.

Just a quick "me too". I've had more or less the exact same thing happen with my first (and until now only) 10.2 install: * Start install 10.2, with a minimal package selection, no X, no nothing. * install goes according to plan, until initial reboot * system hangs at "grub stage 2.." (two dots) * after much mucking about, I finally installed an even more minimal 9.3 on a separate partition, and let *that* install grub, which worked. * adapted the 9.3 grub conf to boot 10.2 This is all from memory, and I have no time to check up on anything in the next couple of days either :P System is a "LexCom CV860A" Manuals etc do exist online (I know, I saw one once) but information is sparse at http://www.lex.com.tw

...

Questions are starting to run through my mind like... "Is the BIOS capable of addressing high addresses on that disk?" and "Has he verified the disk is being addressed using LBA and not CHS?" That sort of thing...

I have two more of these running 9.3 and neither have ever had similar problems. I cannot exclude the BIOS from being at fault, though I do suspect something is amiss with the 10.2 grub install process. Unfortunately I don't have access to a USB CDrom, so the only way for me to boot install- or rescue- systems is PXE, which takes... oh round about forever... which is why I haven't pursued the matter much further. Just thought I should chime in. oh yeah: disk and controller on my box are IDE, so I don't think SATA is a factor in this... /Jon -- YMMV -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org