[opensuse-factory] rc2
Hello, Just tested the RC2 DVD (I work for a Novell partner) on a Core2Duo machine. I guess, I should have tested it earlier and not concentrate strictly on PPC... - installation from images (which is the default setting) has serious troubles: https://bugzilla.novell.com/show_bug.cgi?id=456337 For the rest I don't have now time to bugzilla, maybe in the evening... - nvidia binary drivers installed, 3D works fine, but Compiz can't be enabled on KDE4 (Desktop settings says, that Composite and Damage extensions are missing, which is true, as Composite is disabled in the /etc/X11/xorg.conf generated by sax2) - the machine reboots while coming back from hibernation (Intel G965 chipset, nVidia binary driver was not yet enabled, when tested). This led to a broken file system and a broken KDE4 desktop (only the START menu stayed in place, the rest moved or disappeared) - I installed to an extended partition (/dev/sda5). The default boot manager configuration is broken, as grub is only installed to an extended partition. This results in an unbootable system. It works fine when MBR is also used. Bye, CzP -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Am Donnerstag 04 Dezember 2008 schrieb Peter Czanik:
Hello,
Just tested the RC2 DVD (I work for a Novell partner) on a Core2Duo machine. I guess, I should have tested it earlier and not concentrate strictly on PPC...
- installation from images (which is the default setting) has serious troubles: https://bugzilla.novell.com/show_bug.cgi?id=456337 I'll look into the bug.
For the rest I don't have now time to bugzilla, maybe in the evening...
- nvidia binary drivers installed, 3D works fine, but Compiz can't be enabled on KDE4 (Desktop settings says, that Composite and Damage extensions are missing, which is true, as Composite is disabled in the /etc/X11/xorg.conf generated by sax2)
- the machine reboots while coming back from hibernation (Intel G965 chipset, nVidia binary driver was not yet enabled, when tested). This led to a broken file system and a broken KDE4 desktop (only the START menu stayed in place, the rest moved or disappeared)
- I installed to an extended partition (/dev/sda5). The default boot sda5 is usually a logical and not an extended partition.
manager configuration is broken, as grub is only installed to an extended partition. This results in an unbootable system. It works fine when MBR is also used.
From http://en.opensuse.org/Bootloader/Scenarios Loader itself can be installed to one (or more) of following master boot record of the primary disk boot sector of primary partition on primary disk holding one of ext2 or ext3 /dev/sda5 does not fit these requirements. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Hello, Stephan Kulow írta:
- I installed to an extended partition (/dev/sda5). The default boot
sda5 is usually a logical and not an extended partition.
Don't use x86 enough to remember the right terminology :)
manager configuration is broken, as grub is only installed to an extended partition. This results in an unbootable system. It works fine when MBR is also used.
From http://en.opensuse.org/Bootloader/Scenarios Loader itself can be installed to one (or more) of following master boot record of the primary disk boot sector of primary partition on primary disk holding one of ext2 or ext3
/dev/sda5 does not fit these requirements.
I know (use DOS from '89 and Linux from '94). But somebody, who installs openSUSE by accepting most default settings and without reading a wiki (most of the users...) will run into an unbootable system when using the defaults. Bye, CzP -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Am Donnerstag 04 Dezember 2008 schrieb Peter Czanik:
Hello,
Stephan Kulow írta:
- I installed to an extended partition (/dev/sda5). The default boot
sda5 is usually a logical and not an extended partition.
Don't use x86 enough to remember the right terminology :)
manager configuration is broken, as grub is only installed to an extended partition. This results in an unbootable system. It works fine when MBR is also used.
From http://en.opensuse.org/Bootloader/Scenarios Loader itself can be installed to one (or more) of following master boot record of the primary disk boot sector of primary partition on primary disk holding one of ext2 or ext3
/dev/sda5 does not fit these requirements.
I know (use DOS from '89 and Linux from '94). But somebody, who installs openSUSE by accepting most default settings and without reading a wiki (most of the users...) will run into an unbootable system when using the defaults.
Yast should not have proposed /dev/sda5 - we'd need your yast logs there. (You don't need to reinstall, just let yast create the proposal and then save_y2logs). Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Peter Czanik napsal(a):
Hello,
Stephan Kulow írta:
- I installed to an extended partition (/dev/sda5). The default boot
sda5 is usually a logical and not an extended partition.
Don't use x86 enough to remember the right terminology :)
manager configuration is broken, as grub is only installed to an extended partition. This results in an unbootable system. It works fine when MBR is also used.
From http://en.opensuse.org/Bootloader/Scenarios Loader itself can be installed to one (or more) of following master boot record of the primary disk boot sector of primary partition on primary disk holding one of ext2 or ext3
/dev/sda5 does not fit these requirements.
I know (use DOS from '89 and Linux from '94). But somebody, who installs openSUSE by accepting most default settings and without reading a wiki (most of the users...) will run into an unbootable system when using the defaults. Bye, CzP
This looks like missing check for supported scenarios (which if you doesn't have supported scenario write some red warning). And maybe also problem of proposal, which should propose overwrite MBR (also with warning, because rewrite MBR is done automatic if not detected some other bootloader (as windows)) if boot partition is logical. JR -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
josef reidinger wrote:
This looks like missing check for supported scenarios (which if you doesn't have supported scenario write some red warning). And maybe also problem of proposal, which should propose overwrite MBR (also with warning, because rewrite MBR is done automatic if not detected some other bootloader (as windows)) if boot partition is logical.
Why is there a distinction between installing GRUB into an MBR or not? Surely since MBR works in most cases, best, this would be better to have as the default. I think Daniel just said this *is* the case. If this is in fact the case then doesn't the XFS GRUB bug "not exist" anymore in the default proposal? GRUB manages absolutely fine to boot Windows if installed in the MBR, it would be a pretty crap bootloader if it couldn't. How does GRUB operate from the netinstall system (OpenSUSE-11.1-NET.exe on the DVD) and out of curiosity is this the same kind of installation system as Ubuntu/WUBI or just a clever way of booting off a "DVD" without burning one? -- Matt Sealey <matt@genesi-usa.com> Genesi, Manager, Developer Relations -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Thu, Dec 4, 2008 at 3:47 PM, Matt Sealey <matt@genesi-usa.com> wrote:
GRUB manages absolutely fine to boot Windows if installed in the MBR, it would be a pretty crap bootloader if it couldn't.
GRUB doesn't "boot" windows. It "chainloads". It basically passes control to the windows boot loader. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 2008/12/04 14:47 (GMT-0600) Matt Sealey composed:
Why is there a distinction between installing GRUB into an MBR or not?
Because the windoz installer won't tolerate it, it matters if the system is multiboot with doz or any DOS-like OS. Any time doz is installed, or _reinstalled_, any non-generic MBR code is replaced with generic MBR code, without the installer asking if you want it to do that. Generic boot code can boot any primary partition that is set active, while Grub can boot any partition anywhere. If your /boot or / is a primary, you don't need Grub on MBR. If you don't make Linux dependent on non-generic MBR code, and usually there's no need to, then installing doz won't result in a Linux that needs "repair". http://en.opensuse.org/Bugs/grub#How_does_a_PC_boot_.2F_How_can_I_set_up_a_w... http://fm.no-ip.com/install-doz-after.html -- "Unless the Lord builds the house, its builders labor in vain." Psalm 127:1 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Thursday 04 December 2008, Peter Czanik wrote:
- I installed to an extended partition (/dev/sda5). The default boot manager configuration is broken, as grub is only installed to an extended partition. This results in an unbootable system. It works fine when MBR is also used.
The behaviour of the grub installation changed during the betas/RCs. See this bug for the descibed issue: https://bugzilla.novell.com/show_bug.cgi?id=450963 Solution: in the menu of the bootloader configuration you now have to uncheck the checkbox which allowes writing code to the MBR. Then the MBR will be left untouched. In all other cases if grub is found in the MBR, it will be changed - even if you wanted to install grub only to the root-partition of your installation. Hope this answers your question. Ciao, Daniel -- J. Daniel Schmidt <jdsn@suse.de> SUSE Linux Products GmbH Research & Development Maxfeldstr. 5 GF: Markus Rex, HRB 16746 (AG Nürnberg) D-90409 Nürnberg -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
participants (7)
-
Felix Miata -
J. Daniel Schmidt -
josef reidinger -
Larry Stotler -
Matt Sealey -
Peter Czanik -
Stephan Kulow