Thanks for the reply and suggestions. On Sun, 4 Jan 2015, Ruben wrote:

If everything is installed just run gpart and reload the MBR Edit fstab as needed.

What was booting your system before? GRUB or Windows?

Grub2, as established by the Linux install.

read over this as well

http://dedoimedo.com/computers/grub-2.html

I have this feeling that your Partition table has been changed to gpart format

But why would the installer do that if the bios states Legacy Support (rather than UEFI)? I had to reinstall Win-7 (What a pain!!!). It is working again. The os 13.2 install disk still does _not_ have the two missing menu options. It does not matter if Legacy Sopport is enabled or disabled, or whether the Linux disk (/dev/sdb) is attached or not. Joe -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Basil, On Mon, 5 Jan 2015, Basil Chupin wrote:

On 05/01/15 06:21, Joseph Comfort wrote:

...

I am trying to install os 13.2 on my HP 6305 desktop. I have problems which continue to get worse. The computer came with Win-7 on disk /dev/sda (in 4 patitions). I added a second disk (sdb) and installed os 13.1. The partitions were formatted with ext4, and 'boot' was part of the root (/). The 6305 bios has Legacy Support enabled and Secure Mode disabled. Installation of 13.1 was not a problem, and all ran fine.

Problem 1: Booting the downloaded os 13.2 DVD, there are no entries for either 'Boot installed system' or for 'memtest.' Actually, this is also true for the downloaded os 13.1 disk (used to install that system).

[pruned]

Both 13.1 and 13.2 *DO* have those entries. There are 6 options:

Boot from Hard Disk

Installation

Upgrade

Rescue System

Check Installation Media

Memory Test

So which, exactly, "disk" you used to install - the full DVD or the Live disk?

Yes, I know all 6 options are on the disk -- it is the full 4.4 GB DVD. All 6 *do* show up on my laptop and the old desktop. But they do not show up on the HP 6305. The story is the same for 13.1. The behavior is independent of the 'Legacy Support' enable/disable option in the bios, which controls the use of UEFI, and also whether my Linux disk (/dev/sdb) is connected or not. Joe

BC

-- Using openSUSE 13.1, KDE 4.14.3 & kernel 3.18.1-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX660 GPU

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

В Mon, 05 Jan 2015 11:28:25 +1100 Basil Chupin пишет:

Both 13.1 and 13.2 *DO* have those entries. There are 6 options:

Boot from Hard Disk

Only on legacy BIOS - not when booted in EFI mode.

Installation

Upgrade

Rescue System

Check Installation Media

Memory Test

So which, exactly, "disk" you used to install - the full DVD or the Live disk?

BC

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

В Mon, 05 Jan 2015 16:34:19 +1100 Basil Chupin пишет:

But is this right? I mean, you insert the DVD to be able to install oS, and well *before* you select "Installation" something has already decided that: 1) you cannot Boot from Hard Drive; 2) you cannot Check the Media; 3) you cannot do a Memory Test.

1) under EFI "Boot from Hard Drive" is meaningless and even if possible most likely does not do what you would expect it to do 2) I did not look in details how media check is implemented, but yes, under EFI media organization may make it hard to implement 3) memtest86+ is for legacy BIOS only. If you are aware about memtest or similar tool with suitable license that can be used for EFI - by all means, tell developers so it can be integrated. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

В Mon, 05 Jan 2015 02:01:07 -0500 Ruben пишет:

...

3) memtest86+ is for legacy BIOS only. If you are aware about memtest or similar tool with suitable license that can be used for EFI - by all means, tell developers so it can be integrated.

http://www.passmark.com/forum/showthread.php?4315-Memtest86-Version-5-Beta-%...

http://technet.microsoft.com/en-us/library/cc766223%28v=WS.10%29.aspx

You probably missed the "suitable license". But if you know that either of them can be freely redistributed by openSUSE - file feature request on https://features.opensuse.org/. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

В Mon, 05 Jan 2015 08:30:35 +0100 Per Jessen пишет:

Andrei Borzenkov wrote:

...

В Mon, 05 Jan 2015 02:01:07 -0500 Ruben пишет:

...

...

3) memtest86+ is for legacy BIOS only. If you are aware about memtest or similar tool with suitable license that can be used for EFI - by all means, tell developers so it can be integrated.

http://www.passmark.com/forum/showthread.php?4315-Memtest86-Version-5-Beta-%...

...

You probably missed the "suitable license". But if you know that either of them can be freely redistributed by openSUSE - file feature request on https://features.opensuse.org/.

memtest v5 "free edition" seems to come with a license of "Free".

Adobe Reader or Oracle Java are "free" as well, which does not make it legal to redistribute them, at least unconditionally. In any case, IANAL - there is legal team; whoever is interested enough should open bug requesting to verify whether product can be included as part of openSUSE. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 01/05/2015 01:45 AM, Andrei Borzenkov wrote:

В Mon, 05 Jan 2015 16:34:19 +1100 Basil Chupin пишет:

...

But is this right? I mean, you insert the DVD to be able to install oS, and well *before* you select "Installation" something has already decided that: 1) you cannot Boot from Hard Drive; 2) you cannot Check the Media; 3) you cannot do a Memory Test.

1) under EFI "Boot from Hard Drive" is meaningless and even if possible most likely does not do what you would expect it to do

2) I did not look in details how media check is implemented, but yes, under EFI media organization may make it hard to implement

3) memtest86+ is for legacy BIOS only. If you are aware about memtest or similar tool with suitable license that can be used for EFI - by all means, tell developers so it can be integrated. Starting from MemTest86 v5, the code was re-written to support self booting from the newer UEFI platform. UEFI is able to provide additional services http://memtest86.com/technical.htm#new that is unavailable in BIOS, such as graphical, mouse and file system support. The software (Free Edition http://memtest86.com/download.htm#free) still remains free to use without restrictions. For advanced/enthusiast users or commercial applications, a professional version http://memtest86.com/features.htm is available for users that require additional customizability and advanced features that may be more suitable for their testing needs. A comparison of the different versions can be found here http://memtest86.com/features.htm -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Sun, 4 Jan 2015, Neil Rickert wrote:

On 01/04/2015 01:21 PM, Joseph Comfort wrote:

...

Problem 1: Booting the downloaded os 13.2 DVD, there are no entries for either 'Boot installed system' or for 'memtest.'

I'm pretty sure that you booted the DVD in UEFI mode rather than legacy mode. And that is the cause of your problems.

If you want to only use legacy mode, then you must disable UEFI mode in the BIOS settings. Otherwise there are two ways of booting the DVD (and other install media). One of my UEFI boxes will list both as boot choices when I hit F12 during boot. My other UEFI box will only list one, depending on my BIOS settings.

Booting the install media in UEFI mode, there is no option to boot the installed system and no memory check option. The installer will select "grub2-efi", will want "/boot/efi", and may well repartition your drive with GPT partitioning. If you had booted in legacy mode, then the option to boot the installed system would be there, and so would the memory check option. And no "/boot/efi" would have been configured.

There seems to be agreement that I must be booting in UEFI mode. But as I wrote, the behavior is independent on whether I set the BIOS to use Legacy Support (bios) or not (UEFI). I checked again after doing a full reinstall of Win-7. Furthermore, by using a system analysis program (HWinfo64), I see a listing "UEFI boot: not present." I could only get this when the bios was set to Legacy Support because Win-7 would not boot at all if I disabled the option (i.e., tried to use UEFI). After the reinstall, only the MS bootloader is known to the system; the Linux disks are not seen. The arguments and rationale above that I must be booting with UEFI certainly make sense. They are what we would expect. But there is an alternative: that the code and procedures on the Linux 13.2 install disk have bugs such that they do not correctly see (or interpret) the bios configuration, or that there is an assumption that all boots must be under UEFI with gpart partitioning. The evidence seems to point to this altermnative, and that leaves me very much concerned. Along with the reinstall, I also updated the BIOS firmware to the latest version. The main change pertained to Win-8 (encryption on hard disks), which was irrelevant to me. The only change was that booting to Win-7 in UEFI mode now fails entirely. Joe -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

В Sun, 4 Jan 2015 23:02:48 -0700 (MST) Joseph Comfort пишет:

...

There seems to be agreement that I must be booting in UEFI mode. But as I wrote, the behavior is independent on whether I set the BIOS to use Legacy Support (bios) or not (UEFI).

Please make a photo of menu you get after booting from DVD and upload to http://susepaste.org/. I checked again after doing a full

reinstall of Win-7. Furthermore, by using a system analysis program (HWinfo64), I see a listing "UEFI boot: not present."

Do not you think that it may simply show you which mode was used to boot current OS instance?

The arguments and rationale above that I must be booting with UEFI certainly make sense. They are what we would expect. But there is an alternative: that the code and procedures on the Linux 13.2 install disk have bugs such that they do not correctly see (or interpret) the bios configuration,

There is no way to run bootloader built for EFI on BIOS. It is simply impossible. It will not be able to display a single character even if it manages to proceed that far. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org