Had a LOT of trouble getting an Ultra5 to boot until I found this (http://forums.gentoo.org/viewtopic-t-519998.html) forum... After getting a usable root fs and kernel setup, and emerging silo and installing silo (all with no errors,) the machine would hang indefinately during boot after trying to access the boot-blocks (wherever i put them) on the HD .... ie. instead of printing the S in SILO the machine would just hang after momentarily accessing the HD. Reproducible: Always Steps to Reproduce: 1. emerge bash >3.2 then emerge silo 2. install silo boot-blocks (silo or silo -f -C /boot/silo.conf, something like that) 3. reboot machine, telling it via any method (default boot-device or manual forcing) to boot from the HD you just installed a bootloader on Actual Results: The machine hangs after trying to access the bootloader Expected Results: The machine SHOULD boot SILO See forum link above... I didn't try all available versions of bash, but I tried a few, and all the ones i tried above 3.2 didn't work, while the ones below did... All of this came from a 'by the handbook' new install on my Ultra5 ... If no-one knows what the problem is, the higher versions of bash should at least (IMHO) be keyworded so that new-installs work... I had a bit of an idea what info i was looking for, but a LOT of searching was needed to find this solution....
reassigning to sparc team. Definitely not Gentoo/Alt.
emerge --info would be nice. Also this was fixed in silo-1.4.13-r1, so next time try searching in bugs.gentoo.org...
Portage 2.1.2.9 (default-linux/sparc/sparc64/2007.0, gcc-4.1.1, glibc-2.5-r2, 2.6.20-gentoo-r4 sparc64) ================================================================= System uname: 2.6.20-gentoo-r4 sparc64 sun4u Gentoo Base System release 1.12.9 Timestamp of tree: Sat, 28 Jul 2007 01:50:01 +0000 dev-lang/python: 2.4.4 dev-python/pycrypto: 2.0.1-r5 sys-apps/sandbox: 1.2.17 sys-devel/autoconf: 2.61 sys-devel/automake: 1.9.6-r2, 1.10 sys-devel/binutils: 2.17 sys-devel/gcc-config: 1.3.14 sys-devel/libtool: 1.5.23b virtual/os-headers: 2.6.21 ACCEPT_KEYWORDS="sparc" AUTOCLEAN="yes" CBUILD="sparc-unknown-linux-gnu" CFLAGS="-O2 -mcpu=ultrasparc -pipe" CHOST="sparc-unknown-linux-gnu" CONFIG_PROTECT="/etc" CONFIG_PROTECT_MASK="/etc/env.d /etc/gconf /etc/terminfo" CXXFLAGS="-O2 -mcpu=ultrasparc -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="distlocks metadata-transfer sandbox sfperms strict" GENTOO_MIRRORS="http://ftp.swin.edu.au/gentoo ftp://ftp.planetmirror.com/pub/gentoo/ http://gentoo.gg3.net/ http://ftp.ucsb.edu/pub/mirrors/linux/gentoo/ http://ftp.gentoo.or.kr/" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages --filter=H_**/files/digest-*" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://spacecadet/gentoo-portage" USE="bitmap-fonts cli cracklib cups dri fortran gdbm gpm iconv isdnlog libg++ midi mudflap nptl nptlonly openmp pcre ppds pppd reflection session sparc spl truetype-fonts type1-fonts unicode xorg" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mulaw multi null plug rate route share shm softvol" ELIBC="glibc" INPUT_DEVICES="keyboard mouse evdev" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" USERLAND="GNU" VIDEO_CARDS="dummy fbdev glint mach64 mga r128 radeon sunbw2 suncg14 suncg3 suncg6 sunffb sunleo tdfx v4l voodoo" Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, LINGUAS, MAKEOPTS, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS, PORTDIR_OVERLAY [ebuild R ] app-shells/bash-3.2_p17 USE="(-afs) -bashlogger -nls -vanilla" 0 kB [ebuild R ] sys-boot/silo-1.4.13-r1 USE="(-hardened)" 0 kB
Sorry about the category and not finding the other bug... I'm not real good at working bugzilla yet... Nevertheless, the problem still exists on my system... It works if i downgrade bash then rebuild and re-install silo, but not if i upgrade bash and rebuild then re-install silo...
You did run "silo -f" after upgrading didn't you? Otherwise there's not much to do here, i can't reproduce and the people that reported this issue in bug #186204 have it solved for them...
Definately reinstalled the boot-stuff... thismorning before the emerge --info i went from a working/booting system with bash <3.2 , emerge bash silo (checking that the versions were the new and up to date ones,) silo -f (tried with -C /boot/silo.conf too... both silo.conf's are the same, but i don't know if silo hardcodes something when you install) then it didn't work... got lazy with all the slow emerge's so i just copied the /boot/*.b from the livecd (/mnt/cdrom/boot/*.b) over my ones and it worked again (that was a workaround listed in the other bug, from memory...) I'm partway through re-building world... Thee whole thing was up to date about a month ago when I started having problems and couldn't find a solution.... Now theres a bunch of stuff, including a gcc and other build-related stuff... If you think it will make a difference I can try to reproduce the problem yet again after all the updates finish... could be a couple days tho... Maybe you can tell me an easier way of testing the .b files without rebooting, getting stuck and having to livecd/chroot... Maybe the broken ones (at least with the problem that already seems to be fixed for other people) have a distinctive something at the start of them ? That way i could try a few different combinations of versions much more quickly...
Just to clarify, to fix things after breaking them again, I copied the *.b files from the livecd AND silo -f 'd...
Yes, it was second.b being broken IIRC. Other than glibc headers and linux-headers it doesn't use much to build against. You can give a spin at upgrading glibc and then re-emerging silo to see if it's related.
Ok... the big emerge system/world should be done, err, sometime between now and the end of the week... I'll try again then
O.k... So glibc wouldn't upgrade (to -r4)... something about GNU 'as' segfault... I tried rebuilding a few build-deps to make glibc go, but it wouldn't... so I emerge -e glibc and it worked... Then I rebuild bash and silo and they both worked too... So I figure either my system had a problem during the install emerge's or the stage-file i downloaded had a minor problem... either way, my problem is solved... Thankyou for your attention, and sorry for wasting your time.
