On Sun, Jan 17, 2010 at 05:08:55PM +0100, Frans Pop wrote: > On Sunday 17 January 2010, Jurij Smakov wrote: > > Comments/Problems: > > Now that http://bugs.debian.org/562594 is fixed, I was able to > > continue the installation and it all went fine until the end. > > However, after finishing the installation machine fails to boot [...] > > As the installation itself works fine I would guess this is not an > installer problem, but a kernel issue. Maybe it leaves the hardware in an > incorrect state for the reboot. > > Have you tried a cold boot of the installed system?
Adding kernel team for comment: it looks like the value returned by uname -m has changed from 'sparc64' in kernel 2.6.26 to 'sparc' in 2.6.30 (and, probably, later ones). This breaks SILO, which uses this value to determine what first-stage bootloader to install, as a result the sparc machines installed with current daily installer builds turn unbootable by the end of installation. Please confirm that this change is not a result of some Debian-specific patch or build procedure, as it should be reported upstream if that's not the case. For reference: ju...@debian:~$ uname -a Linux debian 2.6.26-2-sparc64-smp #1 SMP Thu Nov 5 03:34:29 UTC 2009 sparc64 GNU/Linux ju...@debian:~$ uname -m sparc64 ~ # uname -a Linux debian 2.6.30-2-sparc64 #1 Sat Sep 26 07:26:31 UTC 2009 sparc GNU/Linux ~ # uname -m sparc I've confirmed that forcing the machine type by running 'silo -u -f' makes the machine bootable again. Best regards, -- Jurij Smakov ju...@wooyd.org Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org