on a 4500 ultrasparc with 8GB ram and 8 CPUs, when i boot from livecd 2005.1, i get Silo's boot prompt and when i enter 'gentoo-2.4', i get following error: boot: gentoo-2.4 Could not find any available memory for initial ramdisk Fatal error: You do not have enough continuous available memory for such initial ramdisk. Program terminated {0} ok Any help please.... thanks.
*** Bug 121610 has been marked as a duplicate of this bug. ***
Are you running the latest version of OBP for the E4500?
(In reply to comment #2) > Are you running the latest version of OBP for the E4500? I am running older version (3.2.28), below is the output. Can you pls confirm based on your knowledge (i am new to both sun and gentoo). Thnx. Also, i have donwloaded patch jar file (103346-30.jar) which supposedly contains the path to upgrade the OBP to OBP 3.2.30. But don't know how i can update it? Can you help (i have solaris 2.10 running on the box) me with instructions on how to? thnx. ============ result ============== {0} ok .VERSION Slot 0 - CPU/Memory OBP 3.2.28 2000/12/20 12:24 POST 3.9.28 2000/12/20 12:29 Slot 1 - I/O Type 4 FCODE 1.8.28 2000/12/20 12:22 iPOST 3.4.28 2000/12/20 12:28 Slot 2 - CPU/Memory OBP 3.2.28 2000/12/20 12:24 POST 3.9.28 2000/12/20 12:29 Slot 4 - CPU/Memory OBP 3.2.28 2000/12/20 12:24 POST 3.9.28 2000/12/20 12:29 Slot 6 - CPU/Memory OBP 3.2.28 2000/12/20 12:24 POST 3.9.28 2000/12/20 12:29 8-slot Sun Enterprise E4500/E5500, No Keyboard OpenBoot 3.2.28, 8192 MB memory installed, Serial #14987737. Copyright 2000 Sun Microsystems, Inc. All rights reserved Ethernet address 8:0:20:e4:b1:d9, Host ID: 80e4b1d9.
http://sunsolve.sun.com/search/document.do?assetkey=1-21-103346-30-1 Latest rev is 3.2.30. There's a couple of things you can try. Long story short is that we must use an older silo version for the livecd for compatibility purposes, and the old silo can be causing this if you have >4GB. 1- Try with memory <=4GB for installation purposes, after you're done with the livecd you can get the memory back in (you could just remove processor cards to avoid the hassle too). 2- Try upgrading the OBP to the latest rev - i'm of the opinion this won't help, but then it won't break anything either. Just be careful when doing the upgrade, IIRC you must upgrade every processor board. Feedback is welcome, we've got a couple of reports like this one in the forums but people never came back to us with results about it.
(In reply to comment #4) > http://sunsolve.sun.com/search/document.do?assetkey=1-21-103346-30-1 > Latest rev is 3.2.30. > There's a couple of things you can try. Long story short is that we must use an > older silo version for the livecd for compatibility purposes, and the old silo > can be causing this if you have >4GB. > 1- Try with memory <=4GB for installation purposes, after you're done with the > livecd you can get the memory back in (you could just remove processor cards to > avoid the hassle too). > 2- Try upgrading the OBP to the latest rev - i'm of the opinion this won't > help, but then it won't break anything either. Just be careful when doing the > upgrade, IIRC you must upgrade every processor board. > Feedback is welcome, we've got a couple of reports like this one in the forums > but people never came back to us with results about it. First of all thank you very much for your guidance. I did the firmware upgarde (and have attached the how-to at the end of this for others to use). But that did not help with booting the livecd. then i pulled out 2 of the boards as you suggested that did boot the livecd. However, fdisk is not recognizing any of my disk drives livecd ~ # fdisk /dev/sda Unable to open /dev/sda I have 14 disk drives attached to the machine. Under OPB solaris they are shown as c0t32d0 to c0t38d0 c0t48d0 to c0t54d0 Can you suggest as how could i do that thanks. ========== ls /dev is here ================== livecd dev # ls cdrom pty ptyc1 ptye3 ptyq5 ptys7 ptyu9 ptywb ptyyd ram9 cdroms ptya0 ptyc2 ptye4 ptyq6 ptys8 ptyua ptywc ptyye raminitrd console ptya1 ptyc3 ptye5 ptyq7 ptys9 ptyub ptywd ptyyf random cua ptya2 ptyc4 ptye6 ptyq8 ptysa ptyuc ptywe ptyz0 rd cua0 ptya3 ptyc5 ptye7 ptyq9 ptysb ptyud ptywf ptyz1 root cua1 ptya4 ptyc6 ptye8 ptyqa ptysc ptyue ptyx0 ptyz2 rtc cua2 ptya5 ptyc7 ptye9 ptyqb ptysd ptyuf ptyx1 ptyz3 scsi cua3 ptya6 ptyc8 ptyea ptyqc ptyse ptyv0 ptyx2 ptyz4 sg fb ptya7 ptyc9 ptyeb ptyqd ptysf ptyv1 ptyx3 ptyz5 sg0 fd ptya8 ptyca ptyec ptyqe ptyt0 ptyv2 ptyx4 ptyz6 shm floppy ptya9 ptycb ptyed ptyqf ptyt1 ptyv3 ptyx5 ptyz7 sr full ptyaa ptycc ptyee ptyr0 ptyt2 ptyv4 ptyx6 ptyz8 sr0 ide ptyab ptycd ptyef ptyr1 ptyt3 ptyv5 ptyx7 ptyz9 stderr initctl ptyac ptyce ptyp0 ptyr2 ptyt4 ptyv6 ptyx8 ptyza stdin initrd ptyad ptycf ptyp1 ptyr3 ptyt5 ptyv7 ptyx9 ptyzb stdout kmem ptyae ptyd0 ptyp2 ptyr4 ptyt6 ptyv8 ptyxa ptyzc sunmouse log ptyaf ptyd1 ptyp3 ptyr5 ptyt7 ptyv9 ptyxb ptyzd tts loop ptyb0 ptyd2 ptyp4 ptyr6 ptyt8 ptyva ptyxc ptyze tty loop0 ptyb1 ptyd3 ptyp5 ptyr7 ptyt9 ptyvb ptyxd ptyzf tty0 loop1 ptyb2 ptyd4 ptyp6 ptyr8 ptyta ptyvc ptyxe ram0 ttyS0 loop2 ptyb3 ptyd5 ptyp7 ptyr9 ptytb ptyvd ptyxf ram1 ttyS1 loop3 ptyb4 ptyd6 ptyp8 ptyra ptytc ptyve ptyy0 ram10 ttyS2 loop4 ptyb5 ptyd7 ptyp9 ptyrb ptytd ptyvf ptyy1 ram11 ttyS3 loop5 ptyb6 ptyd8 ptypa ptyrc ptyte ptyw0 ptyy2 ram12 urandom loop6 ptyb7 ptyd9 ptypb ptyrd ptytf ptyw1 ptyy3 ram13 usb loop7 ptyb8 ptyda ptypc ptyre ptyu0 ptyw2 ptyy4 ram14 vc mem ptyb9 ptydb ptypd ptyrf ptyu1 ptyw3 ptyy5 ram15 vcc misc ptyba ptydc ptype ptys0 ptyu2 ptyw4 ptyy6 ram2 vcs mouse ptybb ptydd ptypf ptys1 ptyu3 ptyw5 ptyy7 ram3 vcsa null ptybc ptyde ptyq0 ptys2 ptyu4 ptyw6 ptyy8 ram4 zero openprom ptybd ptydf ptyq1 ptys3 ptyu5 ptyw7 ptyy9 ram5 port ptybe ptye0 ptyq2 ptys4 ptyu6 ptyw8 ptyya ram6 ptmx ptybf ptye1 ptyq3 ptys5 ptyu7 ptyw9 ptyyb ram7 pts ptyc0 ptye2 ptyq4 ptys6 ptyu8 ptywa ptyyc ram8 ============ how to update PROM on E4500 under solaris 2.10 =========== 1. su to root. 2. make sure your path has usr/sfw/bin:/usr/ccs/bin. 3. smpatch download -i xxxxx-xx. <=== this will download the jar file. 4. jar xf xxxxx-xx.jar <=== this will extract the jar file. 5. cd xxxxx-xx 6. chmod a+x update-flash-xx <=== whatever the file is 7. make sure you read all the instructions in the directory 8. ./update-flash-xx <=== this will start the update follow the instructions.
(In reply to comment #5) > However, fdisk is not recognizing any of my disk drives > livecd ~ # fdisk /dev/sda > Unable to open /dev/sda > I have 14 disk drives attached to the machine. Under OPB solaris they are shown > as > c0t32d0 to c0t38d0 > c0t48d0 to c0t54d0 > Can you suggest as how could i do that thanks. I did further digging and found that all of the disk drives are attached via Fiber channel in Sun Storage array 5100. How could load a driver after booting from Livecd so that those drives are accessible. Thnaks.
You'll need to modprobe for socal or soc depending on which controller you have. Last time we tried internal FC-AL disks didn't really work, so YMMV with the external array since it's FC-AL too.
Same problem here, Blade 2000, sparc64 universal install CD, Gentoo 2006.0 -- I'll try the hardware-removing workaround.
Removed 4GB of 8GB RAM, got a root login now. If this can't be fixed soon, please add a message to SILO :) Thanks!
You are running into the same problem I encountered last November. http://forums.gentoo.org/viewtopic-t-224575.html While I did actually get in touch with the person who wrote the script necessary to get the soc driver (and presumably socal as well), he never followed up with a reply on why the script simply does not work. I may followup my old thread in the near future as a I have several terabyte arrays just itching to be used under gentoo... > then i pulled out 2 of the boards as you > suggested that did boot the livecd. > > However, fdisk is not recognizing any of my disk drives > livecd ~ # fdisk /dev/sda > Unable to open /dev/sda > I have 14 disk drives attached to the machine. Under OPB solaris they are shown > as > c0t32d0 to c0t38d0 > c0t48d0 to c0t54d0
Can you try the experimental livecd @ http://dev.gentoo.org/~gustavoz/sparc/experimental/ ? It should solve the >4GB RAM issues.
No response, we'll assume this is fixed in 2006.1 media with the new silo.
