[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [SOLVED] Take 3: sparc64 CDs work?



In the U5/10 systems, memory must be installed in pairs, for 256MBm
and 4 DIMMS that
he says he has, each will be 64MB.   It may have been just reseating
the memory that
made it happy.


On Wed, 16 Jun 2004 13:19:25 +0100, Gary Parker <g.j.parker@lboro.ac.uk> wrote:
> 
> Well, it certainly used to be the case on Ye Olde SPARCs (talking IPX and
> +1's here) that the size of kernel and/or initrd you could boot from
> depended on the size of the first two memory modules in the machine and it
> was therefore essential to have the two largest modules at the beginning of
> the memory map.
> 
> I have no idea if this is still the case on the SPARC64 architecture but it
> would be my first guess as to why this fixed your problem.
> 
> Gary
> 
> > -----Original Message-----
> > From: Frederik Dannemare [mailto:frederik@dannemare.net]
> > Sent: 16 June 2004 13:00
> > To: debian-boot@lists.debian.org
> > Cc: debian-sparc@lists.debian.org;
> > sparclinux@vger.kernel.org; Patrick Finnegan; Joshua Kwan; Ben Collins
> > Subject: Re: [SOLVED] Take 3: sparc64 CDs work?
> >
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > On Wednesday 09 June 2004 20:20, Frederik Dannemare wrote:
> > > On Wednesday 09 June 2004 18:09, Patrick Finnegan wrote:
> > > > On Wednesday 09 June 2004 08:50, Frederik Dannemare wrote:
> > [ snip ]
> > >
> > >
> > *********************************************************************
> > > Sun Ultra 5/10 UPA/PCI (UltraSPARC-IIi 333MHz), No Keyboard
> > OpenBoot
> > > 3.15, 256 MB memory installed, Serial #10816948.
> > > Ethernet address 8:0:20:a5:d:b4, Host ID: 80a50db4.
> > >
> > >
> > >
> > > Initializing Memory
> > > Initializing Memory
> > >   Rebooting with command: boot cdrom
> > > Boot device: /pci@1f,0/pci@1,1/ide@3/cdrom@2,0:f  File and args:
> > > SILO Version 1.4.5
> > >
> > >
> > >                   Welcome to Debian GNU/Linux sarge!
> > >
> > > This is a Debian installation CDROM, built on 20040604.
> > > Keep it once you have installed your system, as you can
> > boot from it
> > > to repair the system on your hard disk if that ever becomes
> > necessary.
> > >
> > > WARNING: You should completely back up all of your hard disks before
> > >   proceeding. The installation procedure can completely and
> > > irreversibly erase them! If you haven't made backups yet,
> > remove the
> > > rescue CD from the drive and press L1-A to get back to the OpenBoot
> > > prompt.
> > >
> > > Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
> > > permitted by applicable law.
> > >
> > > [ ENTER - Boot install ]   [ Type "rescue" - Boot into rescue mode ]
> > > boot: linux cdrom devfs=nomount ramdisk_size=8192 rootfstype=ext2
> > > root=/dev/hda1
> > > Allocated 8 Megs of memory at 0x40000000 for kernel Loaded kernel
> > > version 2.4.26 Loading initial ramdisk (1865444 bytes at
> > 0x0lx phys,
> > > 0x10C00000 virt)...
> > >
> > > Remapping the kernel... done.
> > > Booting Linux...
> > > PROMLIB: Sun IEEE Boot Prom 3.15.2 1998/11/10 10:35 Linux version
> > > 2.4.26-sparc64 (root@june.voxel.net) (gcc version 3.3.3 (Debian
> > > 20040401)) #1 Sat Apr 24 01:43:10 EDT 2004
> > > ARCH: SUN4U
> > > Ethernet address: 08:00:20:a5:0d:b4
> > > initrd extends beyond end of memory (0x0000000020dc76e4 >
> > > 0x000000001ff14000)
> > > disabling initrd
> > [ snip ]
> >
> > After having spent some time last week reading up on initrd,
> > how to create my own, and then rebuilding the
> > sarge-sparc-netinst.iso with a minimalistic initrd, I still
> > wasn't able to get past the initrd issue.
> >
> > I thought to myself that I was probably doing something wrong
> > since working with initrd and building sparc isos is all new
> > to me, so I just gave up after a dusin tries or so.
> >
> > Then today (don't know why this idea came to me) I decided to
> > open up the box and juggle around with the memory sticks. And
> > voila! Moving the two sticks from DIMM3 and DIMM4 to DIMM1
> > and DIMM2 made the initrd issue go away (booted with default
> > SILO parameters). Dunno why Sarge is picky, when Woody,
> > Solaris, and some old SuSE is not.
> >
> > - --
> > Frederik Dannemare | mailto:frederik@dannemare.net GnuPG key:
> > search for 'dannemare' on http://pgpkeys.mit.edu Key
> > fingerprint: BB7B 078A 0DBF 7663 180A  F84A 2D25 FAD5 9C4E
> > B5A8 http://frederik.dannemare.net |
> > http://www.linuxworlddomination.dk
> > -----BEGIN PGP SIGNATURE-----
> > Version: GnuPG v1.2.4 (GNU/Linux)
> >
> > iD8DBQFA0DYyLSX61ZxOtagRAsB3AJ4it7jW/kvfdUyQzsWWXX6uxCRomACeMMXg
> > h3KTpXQwrtBRdkCGJd/XsEw=
> > =WVwf
> > -----END PGP SIGNATURE-----
> >
> >
> 
> --
> To UNSUBSCRIBE, email to debian-sparc-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> 
> 
> --
> To UNSUBSCRIBE, email to debian-boot-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> 
>



Reply to: