On Thu, Jan 23, 2003 at 10:57:00PM +0100, Daniel van Eeden wrote: > SILO boot: linux > Uncompressing image... > PROMLIB: obio_ranges 1 > bootmem_init: Scan sp_banks, init_bootmem(spfn[1fa],bpfn[1fa],mlpfn[3faa]) > free_bootmem: base [0] size[3faa000] > reserve_bootmem: base[0] size[1fa000] > reserve_bootmem: base[1fa000] size[7f8] > Booting Linux... > > Watchdog Reset > Type help for more information > ok > > I used kernel-image-2.4.20. The old 2.2 kernel works... > It's a sparcstation4 (sparc32, sun4m) > with two addon boards: a soundcard (CS4231) and a TurboGX framebuffer. > I'm running unstable (aka sid) > I tried a vanilla kernel....also didn't work.
I had a similar problem with an SS5 (which as I understand it is practically the same system board). The fix (for me) was quite silly. So. here goes ... how much RAM do you have installed, and in which slots? My SS5 has 8 RAM slots; when I had only four DIMMs I had to install them in slots 0300 through 0303. When I got the machine the DIMMs were in slots 0400 through 0403; I've noticed most people put DIMMs in starting at slot 0403, which is the slot closest to the HDD. The slots are numbered from back to front which probably isn't the most intuitive thing ever. If that isn't your problem, try a kernel which doesn't have initrd enabled (CONFIG_BLK_DEV_INITRD). I'm still trying to figure that one out, but I have another SS5 that will not boot if initrd is compiled into the kernel. HTH, -- Nathan Norman - Incanus Networking mailto:[EMAIL PROTECTED] Great minds discuss ideas, average minds discuss events, small minds discuss people. -- Laurence J. Peter
