see comment #8 in problem 22775 Reproducible: Always Steps to Reproduce: 1.boot live cd version 1.4 rc4 or rc5 2.after SILO loads type "gentoo" and hit enter 3.says "Loading initial ramdisk...." then "Fast Data Acess MMU Miss" Actual Results: I was returned back to the open boot prompt, and gentoo did not boot Expected Results: gentoo should have booted the kernel, after having set up the initial ramdisk see comment #8 in problem 22775
The error you are seeing is probably due to the initrd being too large for your machine to handle. There will be a new sparc64 livecd coming out soon called 2004.0, which may fix your problems. I will add another comment when it is available, but it should be sometime this week.
The 2004.0 livecd is now available at http://gentoo.oregonstate.edu/releases/sparc/2004.0/livecd/sparc64/ or your local Gentoo mirror. Please test and let us know how you make out.
Created attachment 27072 [details] log file from attempted boot of 2004.0 in terminal mode Tried booting Gentoo SPARC Linux 2004.0 Universal I don't get the "fast data access mmu miss" anymore, but doesn't get much further.... After typing in
Created attachment 27072 [details] log file from attempted boot of 2004.0 in terminal mode Tried booting Gentoo SPARC Linux 2004.0 Universal I don't get the "fast data access mmu miss" anymore, but doesn't get much further.... After typing in ?gentoo? I see the following: Loading initial ramdisk?? Remapping kernel?..done Booting Linux. And then my screen went blank for a few seconds, then I see a bunch of white lines on a black background with the lower left corner blinking and some garbage scrolling on the right side while the cd is being accessed?.then it stops. Noticed my resolution was set to 1024x768x70 so I tried 1024x768x60 per the help screen and the same thing happens but all I get is a blank screen. I tried disconnecting the keyboard and booted it in terminal mode?.. It actually is getting farther but still not quite making it. I have tried to attach a log file from my terminal program to show you what it did. I actually found a version of SUSE that I was able to install this way but never could get the normal display working (new to Linux and SPARC) and I don?t believe SUSE is supporting Linux on SPARC anymore so you guys are my last chance at getting some use out of this machine!
The error you described indicate a wrong setting for your PROM framebuffer. What sparc system do you have? Maybe we can give you verified-to-work settings. Trying a native Sun resolution would be worth a try (setenv output-device screen:r1152x900x60).
The setting of (setenv output-device screen:r1152x900x60) did not make a difference. My board was made by Pinnacle Data Systems Inc. and is called the XIP-650. It is based on the Netra AX1105 board series by SUN and is also similar to the blade 100 When I check the version at the open boot prompt I get the following: Firmware CORE Release 1.0.9 created 2003/6/4 14:27 Release 4.0 Version 12 Created 2003/06/04 15:13 cPOST version 1.0.5 created 2002/7/26 CORE 1.0.9 2003/06/04 14:27 The board has the following specs: UltraSPARC IIe 650MHz with 512KB L2 cache 4 memory slots (filled with total 2GB RAM) Dual bussed EIDE Dual bussed SCSI Floppy drive support Two 10/100 base T Ethernet ports Two Serial Two dual USB ports Parallel port PS/2 keyboard and mouse headers Rage XL VGA Audio One Firewire port Three PCI slots I currently have a USB mouse and keyboard attached. I have successfully installed Solaris 9 with no issues but I only have a trial version and need to remove it.
P.S. If this helps any....here are my openboot settings ok printenv Variable Name Value Default Value ras-shutdown-enabled? false false sys-shutdown-temp 70 70 sys-warning-temp 65 65 cpu-shutdown-temp 85 85 cpu-warning-temp 80 80 env-monitor disabled disabled diag-passes 1 1 diag-continue? 0 0 diag-targets 0 0 diag-verbosity 0 0 scsi-initiator-id 7 7 #power-cycles 1130 No default system-board-serial# No default system-board-date No default ttyb-rts-dtr-off false false ttyb-ignore-cd true true ttya-rts-dtr-off false false ttya-ignore-cd true true ttyb-mode 9600,8,n,1,- 9600,8,n,1,- ttya-mode 9600,8,n,1,- 9600,8,n,1,- pcia-probe-list 8,5,6,7 8,5,6,7 pcib-probe-list 7,c,3,d,5,2,8 7,c,3,d,5,2,8 keyboard-click? false false keymap watchdog-timeout 0 63 watchdog-enable? false false mfg-mode off off diag-level max max fcode-debug? false false output-device screen:r1152x900x60 screen input-device keyboard keyboard load-base 16384 16384 auto-boot-retry? false false boot-command boot boot auto-boot? false true watchdog-reboot? false false diag-file diag-device hd net boot-file boot-device hd:a hd cdromide net disk net local-mac-address? true true net-timeout 0 0 ansi-terminal? true true screen-#columns 80 80 screen-#rows 34 34 silent-mode? false false use-nvramrc? false false nvramrc security-mode none No default security-password No default security-#badlogins 0 No default oem-logo 02 3a 00 05 83 06 10 68 ... No default oem-logo? false false oem-banner No default oem-banner? false false hardware-revision No default last-hardware-update No default diag-switch? false false ok
Tried booting over serial? Maybe the framebuffer is just not supported by the kernel.
Yes I have tried booting over serial.......I attached a log file from the terminal window to show you what happend back on 8 March 04.
Can you try using a serial console, and giving silo: gentoo serial console=ttyS0
Closing since 2004.3 is out and it introduces many many fixes in silo, specially those mmu errors :) Serial console should be autodetected too, so no need to pass parameters. Feel free to reopen otherwise, thanks.
