From: David Kirkby on
I've got a Sun Ultra 80 (4 x 450 MHz, 4 GB RAM). I'm not sure what
frambuffer it has in it, but I know it has one. I installed Solaris 10
03/2005 via a serial line. So far I've only ever wanted to use it via
a serial line or ssh over ethernet.

Now I plugging in a Sun 17" (or so) CRT monitor, with the 13W3
connector on it, into the framebuffer. Nothing appears on the screen.
I'm pretty sure the screen is ok, as it has been recently used.

If I stick a serial line on the Sun, and keyboard, so I can see a
message on the serial line "screen not found" Anything I type on the
keyboard I see echoed on the serial line, but nothing appears on the
screen.

# fbconfig
fbconfig: Not a configurable device. Use -list for valid devices.
# fbconfig -list
fbconfig: Cannot read /dev/fbs/ directory.

The 'eeprom' command shows:

output-device=screen
input-device=keyboard

It's several years since I last used this on a screen. And that was
probably a TFT with a 13W3 -> VGA adapter (which I have mislaid). Two
possibilies that come to mind are:

* The output resolution is too high for the monitor. I tried using
stop-N, but I'm not convinced that actually done anything.

* The framebuffer has developed a faullt

Any thoughts?

Dave
From: David Kirkby on
On Sep 11, 12:44 am, David Kirkby <drkir...(a)gmail.com> wrote:
> I've got a Sun Ultra 80 (4 x 450 MHz, 4 GB RAM). I'm not sure what
> frambuffer it has in it, but I know it has one. I installed Solaris 10
> 03/2005 via a serial line. So far I've only ever wanted to use it via
> a serial line or ssh over ethernet.

Here's the output of prtconf

# prtconf
System Configuration: Sun Microsystems sun4u
Memory size: 4096 Megabytes
System Peripherals (Software Nodes):

SUNW,Ultra-80
scsi_vhci, instance #0
packages (driver not attached)
terminal-emulator (driver not attached)
deblocker (driver not attached)
obp-tftp (driver not attached)
disk-label (driver not attached)
SUNW,builtin-drivers (driver not attached)
sun-keyboard (driver not attached)
ufs-file-system (driver not attached)
chosen (driver not attached)
openprom (driver not attached)
client-services (driver not attached)
options, instance #0
aliases (driver not attached)
memory (driver not attached)
virtual-memory (driver not attached)
pci, instance #0
ebus, instance #0
auxio (driver not attached)
power, instance #0
SUNW,pll (driver not attached)
sc (driver not attached)
se, instance #0
su, instance #0
su, instance #1
ecpp (driver not attached)
fdthree (driver not attached)
eeprom (driver not attached)
flashprom (driver not attached)
SUNW,CS4231, instance #0 (driver not attached)
network, instance #0
scsi, instance #0
disk (driver not attached)
tape (driver not attached)
sd, instance #2
sd, instance #0 (driver not attached)
sd, instance #1 (driver not attached)
sd, instance #3 (driver not attached)
sd, instance #4 (driver not attached)
sd, instance #5 (driver not attached)
sd, instance #7 (driver not attached)
sd, instance #8 (driver not attached)
sd, instance #9 (driver not attached)
sd, instance #10 (driver not attached)
sd, instance #11 (driver not attached)
sd, instance #12 (driver not attached)
sd, instance #13 (driver not attached)
sd, instance #14 (driver not attached)
st, instance #0 (driver not attached)
st, instance #1 (driver not attached)
st, instance #2 (driver not attached)
st, instance #3 (driver not attached)
st, instance #4 (driver not attached)
st, instance #5 (driver not attached)
st, instance #6 (driver not attached)
ses, instance #0 (driver not attached)
ses, instance #1 (driver not attached)
ses, instance #2 (driver not attached)
ses, instance #3 (driver not attached)
ses, instance #4 (driver not attached)
ses, instance #5 (driver not attached)
ses, instance #6 (driver not attached)
ses, instance #7 (driver not attached)
ses, instance #8 (driver not attached)
ses, instance #9 (driver not attached)
ses, instance #10 (driver not attached)
ses, instance #11 (driver not attached)
ses, instance #12 (driver not attached)
ses, instance #13 (driver not attached)
ses, instance #14 (driver not attached)
ses, instance #15 (driver not attached)
scsi (driver not attached)
disk (driver not attached)
tape (driver not attached)
pci, instance #1
pci, instance #0
pci108e,1000 (driver not attached)
SUNW,qfe, instance #0
pci108e,1000 (driver not attached)
SUNW,qfe, instance #1
pci108e,1000 (driver not attached)
SUNW,qfe, instance #2
pci108e,1000 (driver not attached)
SUNW,qfe, instance #3
counter-timer (driver not attached)
SUNW,UltraSPARC-II (driver not attached)
SUNW,UltraSPARC-II (driver not attached)
SUNW,UltraSPARC-II (driver not attached)
SUNW,UltraSPARC-II (driver not attached)
pseudo, instance #0
From: Richard B. Gilbert on
David Kirkby wrote:
> On Sep 11, 12:44 am, David Kirkby <drkir...(a)gmail.com> wrote:
>> I've got a Sun Ultra 80 (4 x 450 MHz, 4 GB RAM). I'm not sure what
>> frambuffer it has in it, but I know it has one. I installed Solaris 10
>> 03/2005 via a serial line. So far I've only ever wanted to use it via
>> a serial line or ssh over ethernet.
>
> Here's the output of prtconf
>
> # prtconf
> System Configuration: Sun Microsystems sun4u
> Memory size: 4096 Megabytes
> System Peripherals (Software Nodes):
>
> SUNW,Ultra-80
> scsi_vhci, instance #0
> packages (driver not attached)
> terminal-emulator (driver not attached)
<snip>

I think what you want is:

fbconfig

See the man page.

You might also wish to peruse "Solaris Handbook for Sun Frame Buffers"
P/N 805-4441.

You might also look at
Frame Buffer FAQ
http://www.sunhelp.org/faq/FrameBuffer.htm
From: Richard B. Gilbert on
David Kirkby wrote:
> On Sep 11, 12:44 am, David Kirkby <drkir...(a)gmail.com> wrote:
>> I've got a Sun Ultra 80 (4 x 450 MHz, 4 GB RAM). I'm not sure what
>> frambuffer it has in it, but I know it has one. I installed Solaris 10
>> 03/2005 via a serial line. So far I've only ever wanted to use it via
>> a serial line or ssh over ethernet.
>
> Here's the output of prtconf
>
> # prtconf
> System Configuration: Sun Microsystems sun4u
> Memory size: 4096 Megabytes
> System Peripherals (Software Nodes):
>
> SUNW,Ultra-80
> scsi_vhci, instance #0
> packages (driver not attached)
> terminal-emulator (driver not attached)
> deblocker (driver not attached)
> obp-tftp (driver not attached)
> disk-label (driver not attached)
> SUNW,builtin-drivers (driver not attached)
> sun-keyboard (driver not attached)
> ufs-file-system (driver not attached)
> chosen (driver not attached)
> openprom (driver not attached)
> client-services (driver not attached)
> options, instance #0
> aliases (driver not attached)
> memory (driver not attached)
> virtual-memory (driver not attached)
> pci, instance #0
> ebus, instance #0
> auxio (driver not attached)
> power, instance #0
> SUNW,pll (driver not attached)
> sc (driver not attached)
> se, instance #0
> su, instance #0
> su, instance #1
> ecpp (driver not attached)
> fdthree (driver not attached)
> eeprom (driver not attached)
> flashprom (driver not attached)
> SUNW,CS4231, instance #0 (driver not attached)
> network, instance #0
> scsi, instance #0
> disk (driver not attached)
> tape (driver not attached)
> sd, instance #2
> sd, instance #0 (driver not attached)
> sd, instance #1 (driver not attached)
> sd, instance #3 (driver not attached)
> sd, instance #4 (driver not attached)
> sd, instance #5 (driver not attached)
> sd, instance #7 (driver not attached)
> sd, instance #8 (driver not attached)
> sd, instance #9 (driver not attached)
> sd, instance #10 (driver not attached)
> sd, instance #11 (driver not attached)
> sd, instance #12 (driver not attached)
> sd, instance #13 (driver not attached)
> sd, instance #14 (driver not attached)
> st, instance #0 (driver not attached)
> st, instance #1 (driver not attached)
> st, instance #2 (driver not attached)
> st, instance #3 (driver not attached)
> st, instance #4 (driver not attached)
> st, instance #5 (driver not attached)
> st, instance #6 (driver not attached)
> ses, instance #0 (driver not attached)
> ses, instance #1 (driver not attached)
> ses, instance #2 (driver not attached)
> ses, instance #3 (driver not attached)
> ses, instance #4 (driver not attached)
> ses, instance #5 (driver not attached)
> ses, instance #6 (driver not attached)
> ses, instance #7 (driver not attached)
> ses, instance #8 (driver not attached)
> ses, instance #9 (driver not attached)
> ses, instance #10 (driver not attached)
> ses, instance #11 (driver not attached)
> ses, instance #12 (driver not attached)
> ses, instance #13 (driver not attached)
> ses, instance #14 (driver not attached)
> ses, instance #15 (driver not attached)
> scsi (driver not attached)
> disk (driver not attached)
> tape (driver not attached)
> pci, instance #1
> pci, instance #0
> pci108e,1000 (driver not attached)
> SUNW,qfe, instance #0
> pci108e,1000 (driver not attached)
> SUNW,qfe, instance #1
> pci108e,1000 (driver not attached)
> SUNW,qfe, instance #2
> pci108e,1000 (driver not attached)
> SUNW,qfe, instance #3
> counter-timer (driver not attached)
> SUNW,UltraSPARC-II (driver not attached)
> SUNW,UltraSPARC-II (driver not attached)
> SUNW,UltraSPARC-II (driver not attached)
> SUNW,UltraSPARC-II (driver not attached)
> pseudo, instance #0

# fbconfig -prconf

--- Hardware Configuration for /dev/fb ---
Type: double-buffered FFB2+ with Z-buffer
Board: rev 2 (Vertical)
PROM Information: @(#)ffb2p.fth 2.6 97/10/02
FBC: version 0x3241906d
DAC: Brooktree 9070, version 1 (Pac2)
3DRAM: Mitsubishi 130a, version 1
EDID Data: Not Available
Monitor Sense ID: 6 (Sun monitor)
Monitor possible resolutions: 1024x768x77, 1024x800x84, 1152x900x66,
1152x900x76, 1280x1024x67, 1280x1024x76, 960x680x112s, 960x680x108s
Current resolution setting: 1024x768x70

#
From: David Kirkby on
On Sep 11, 1:41 am, "Richard B. Gilbert" <rgilber...(a)comcast.net>
wrote:
> David Kirkby wrote:
> > On Sep 11, 12:44 am, David Kirkby <drkir...(a)gmail.com> wrote:
> >> I've got a Sun Ultra 80 (4 x 450 MHz, 4 GB RAM). I'm not sure what
> >> frambuffer it has in it, but I know it has one. I installed Solaris 10
> >> 03/2005 via a serial line. So far I've only ever wanted to use it via
> >> a serial line or ssh over ethernet.
>
> > Here's the output of prtconf
>
> > # prtconf
> > System Configuration:  Sun Microsystems  sun4u
> > Memory size: 4096 Megabytes
> > System Peripherals (Software Nodes):
<SNIP>
> >     SUNW,UltraSPARC-II (driver not attached)
> >     pseudo, instance #0
>
> # fbconfig -prconf
>
> --- Hardware Configuration for /dev/fb ---
> Type: double-buffered FFB2+ with Z-buffer
> Board: rev 2 (Vertical)
> PROM Information: @(#)ffb2p.fth 2.6 97/10/02
> FBC: version 0x3241906d
> DAC: Brooktree 9070, version 1 (Pac2)
> 3DRAM: Mitsubishi 130a, version 1
> EDID Data: Not Available
> Monitor Sense ID: 6  (Sun monitor)
> Monitor possible resolutions: 1024x768x77, 1024x800x84, 1152x900x66,
>          1152x900x76, 1280x1024x67, 1280x1024x76, 960x680x112s, 960x680x108s
> Current resolution setting: 1024x768x70
>
> #

Thank you, I'll try that. I later confirmed the monitor was ok on an
Ultra 60.,

I recall the frambuffer is a Creator3D. It has a late PROM revision on
this (I think that was needed for 1600x1200), so this would possibly
be set for 1600x1200x60 output. But I would have expected the boot
messages (machine name, memory etc, to appear, even if X would not
display.)

Dave
 |  Next  |  Last
Pages: 1 2
Prev: Auditreduce problems
Next: Destroying a zfs pool