sparc64/82262: Critical Sparc64 Bug Init Binkley Kernel 5.4
Ultra2 Sun4U 400 Ultra SCSI Jump
penguin at unixdevil.org
Fri Jun 17 00:40:29 GMT 2005
The following reply was made to PR sparc64/82262; it has been noted by GNATS.
From: "James Cornell" <penguin at unixdevil.org>
To: bug-followup at FreeBSD.org
Subject: Re: sparc64/82262: Critical Sparc64 Bug Init Binkley Kernel 5.4
Ultra2 Sun4U 400 Ultra SCSI Jump
Date: Thu, 16 Jun 2005 14:32:26 -0700 (PDT)
Someone needs to recompile and repackage freebsd 5.4 sparc64 isos then.
It's a waste of space otherwise. I tried playing with OBP environment
variables, no dice on 5.3. Since it is hard to get serial cables in this
area, and I require direct access for most things, I will wait until 5.4
is fixed. The drawback of having a type 6 is apparent. I won't settle
with buying another keyboard just because this one can't type though, that
wouldn't make sense. Looks like a waiting game then. I'd rather be using
FreeBSD on there then Solaris for various reasons, including the archaic
path setting absurdness required to implement a half functional lamp on
the sparc64 platform with Solaris, and questionable dependency
requirements for basic system components. E-mail me directly if a new
release is put out. Thanks guys.
> On 16/06/2005, at 3:50 AM, James Cornell wrote:
>> The following reply was made to PR sparc64/82262; it has been noted by
>> From: "James Cornell" <penguin at unixdevil.org>
>> To: bug-followup at FreeBSD.org,
>> penguin at unixdevil.org
>> Subject: Re: sparc64/82262: Critical Sparc64 Bug Init Binkley Kernel
>> Ultra2 Sun4U 400 Ultra SCSI Jump
>> Date: Wed, 15 Jun 2005 07:41:48 -0700 (PDT)
>> I had to manually type all of this.
>>>> FreeBSD/sparc64 boot block
>> Boot path: /sbus at 1f,0/SUNW,fas at e,8800000/sd at 6,0:f
>> Boot loader: /boot/loader
>> Console: Open Firmware console
>> Boot path set to /sbus at 1f,0/SUNW,fas at e,8800000/sd at 6,0:a
>> FreeBSD/sparc64 bootstrap loader, Revision 1.0
>> (root at binkley.cse.buffalo.edu, Sun May 8 07:16:15 UTC 2005)
>> bootpath="/sbus at 1f,0/SUNW,fas at e,8800000/sd at 6,0:a"
>> Loading /boot/defaults/loader.conf
>> /boot/kernel/kernel data=0x3d8908+0x47c78
>> Hit [Enter] too boot immediately, or any other key for command prompt.
>> Booting [/boot/kernel/kernel]...
>> nothing to autoload yet.
>> jumping to kernel entry at 0xc004000.
>> Then it freezes.
> This matches the results of not finding a console - FreeBSD 5.3 has
> ofw_console, so will use any device as a console, but FreeBSD 5.4 only
> has native serial console in the default kernel. To get FreeBSD onto an
> E250, I had to install FreeBSD 5.3, cvsup to 5.4 and use a custom
> kernel with "device ofw_console".
>> I tried FreeBSD 5.3-RELEASE (Sparc64) and it actually boots up. The
>> problem is the keymaps for Type 6 and possibly other Sun keyboards is
>> messed up, and changing options at the console layout prompt have no
>> effect, the install program comes up in b&w and is unnavigatable. The
>> screen corrupts the view of any menu accessed, which can only be done
>> strange key combinations. The partitioner sees the disk though,
>> not being able to read through the garble. The system is running OBP
>> OBP Banner:
>> Sun Ultra 2 UPA/SBus (2x UltraSparc-II 400MHz), Keyboard Present
>> OpenBoot 3.11, 512MB memory installed, Serial #8435438.
>> Ethernet address 8:0:20:80:b6:ee, Host ID: 8080b6ee.
>> Additional Information:
>> Using a Creator3D Card
>> 9.1GB Fujitsu Ultra2 SCSI
>> That's about it.
>> freebsd-sparc64 at freebsd.org mailing list
>> To unsubscribe, send any mail to
>> "freebsd-sparc64-unsubscribe at freebsd.org"
More information about the freebsd-sparc64