I ran into an odd problem when putting 10.3 on my x86_64 desktop: during installation, when the computer restarts for the first reboot, the system would just hang when trying to boot from the hard drive. It seems like the MBR had somehow become corrupted, but there was no error message. It took me a while to figure out how to proceed. I already had a working 10.1 partition on the same hard drive, but the "Boot installed system" option from the CD grub menu seems to redirect to the HD's MBR, which was broken. After some web browsing I picked up the strange tip to boot from the installation CD, abort the installation, which drops me into a ncurses menu, when you can find another "Boot installed system" option that does not rely on the MBR. First off, it would be nice if that option would be much easier to get to. This way I managed to boot my 10.1 system, and fix the MBR by reinstalling grub in the MBR. By adding the 10.3 partition to the grub menu I was finally able to boot into the new system. Everything seems to work fine now, but there remains one problem: I cannot change the bootloader while using the 10.3 system. When I make any changes in the "Boot Loader" section of Yast and apply them, simply nothing changes. I do not get an error message, and /var/log/Yast2/y2log is so verbose that it's hard to make sense of it if you don't know what you are looking for. The funny thing is that I can change the bootloader just fine while I am working in the 10.1 system on the same hard drive. I can edit grub setting in Yast, which take effect immediately. Does anybody know what might be behind all this, or where I should start looking for potential error messages? I am not too worried since everything is working well right now, but it would be odd to keep the 10.1 partition alive just in case I ever have to change the bootloader. Lutz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org