Upgrading using network install the boot configuration failed.I suspect that the fact I have a boot-device (/dev/hda6) where was the previous(11.0) suseboot folder mislead the installer because contrary to when I installed 11.0(exactly the same method) the installer seemed confused between kernel versions,the older and the new,and entered a loop of accusing error and I skipped the boot loader configuration and finished the installation,hoping to be able to configure the booting manually.But now do not know exactly the parameters to change the yaboot.conf file. I loaded the rescue system,but it´s for experts we need to know the commands. I´m thinking to load again from the network the installation system,and hope that it recognizes that only the boot loader configuration is needed and finishes correctly now that I erased the previous suseboot folder from the boot-device. Suggestions appreciated.Thanks. P.S. .../disk@0:7,/boot/vmlinux-2.6.25.18-0.2-default: unable to open file,Invalid device my Linux root is /dev/hda7,the above is the message I receive now,when booting.When I substitute the old kernel by thenew in the above OpenFirmware(BIOS) path the same message.So other changes are needed in the yaboot.conf file not only the new kernel name. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org