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

On Sep 11, 12:44=A0am, David Kirkby <drkir...@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

David Kirkby wrote:
> On Sep 11, 12:44 am, David Kirkby <drkir...@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

David Kirkby wrote:
> On Sep 11, 12:44 am, David Kirkby <drkir...@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

#

On Sep 11, 1:41=A0am, "Richard B. Gilbert" <rgilber...@comcast.net>
wrote:
> David Kirkby wrote:
> > On Sep 11, 12:44 am, David Kirkby <drkir...@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: =A0Sun Microsystems =A0sun4u
> > Memory size: 4096 Megabytes
> > System Peripherals (Software Nodes):
<SNIP>
> > =A0 =A0 SUNW,UltraSPARC-II (driver not attached)
> > =A0 =A0 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 =A0(Sun monitor)
> Monitor possible resolutions: 1024x768x77, 1024x800x84, 1152x900x66,
> =A0 =A0 =A0 =A0 =A01152x900x76, 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

Richard B. Gilbert wrote:
> # 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
> 
> #


# fbconfig -prconf
fbconfig: Not a configurable device.  Use -list for valid devices.


I recall later, it is a Creator3D in this thing.

According to the document you pointed me to (Solaris Handbook for Sun 
Frame Buffers)

http://dlc.sun.com/pdf/806-6054-10/806-6054-10.pdf

there should be a command

# ffbconfig

for the Creator3D, but I don't have such a command. I tried to check if 
the software for the framebuffer was included, but I seem to get a 
problem doing that too:

# pkginfo
system      SUNW1251f                        Russian 1251 fonts
system      SUNW1394                         Sun IEEE1394 Framework
system      SUNW1394h                        Sun IEEE1394 Framework 
Header FilesALE         SUNW5ttf                         Traditional 
Chinese (BIG5) True Type Fonts Package
ALE         SUNW5xmft                        Traditional Chinese (BIG5) 
X Windows Platform minimum required Fonts Package
system      SUNWGlib                         GLIB - Library of useful 
routines for C programming
<SNIP>
pkginfo: ERROR: pkginfo file is corrupt or missing

I'm not going to lose sleep over this. I'll just reinstall Solaris. 
There was nothing of value on the machine. I only set it up quickly to 
test if a bit of software worked on the first release of Solaris 10.

-- 
I respectfully request that this message is not archived by companies as
unscrupulous as 'Experts Exchange' . In case you are unaware,
'Experts Exchange'  take questions posted on the web and try to find
idiots stupid enough to pay for the answers, which were posted freely
by others. They are leeches.

On 2009-09-12, Dave <foo@coo.com> wrote:
> Richard B. Gilbert wrote:
>> # 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
>> 
>> #
>
>
> # fbconfig -prconf
> fbconfig: Not a configurable device.  Use -list for valid devices.
>
>
> I recall later, it is a Creator3D in this thing.
>
> According to the document you pointed me to (Solaris Handbook for Sun 
> Frame Buffers)
>
> http://dlc.sun.com/pdf/806-6054-10/806-6054-10.pdf
>
> there should be a command
>
> # ffbconfig
>
> for the Creator3D, but I don't have such a command. I tried to check if 
> the software for the framebuffer was included, but I seem to get a 
> problem doing that too:
>
> # pkginfo
> system      SUNW1251f                        Russian 1251 fonts
> system      SUNW1394                         Sun IEEE1394 Framework
> system      SUNW1394h                        Sun IEEE1394 Framework 
> Header FilesALE         SUNW5ttf                         Traditional 
> Chinese (BIG5) True Type Fonts Package
> ALE         SUNW5xmft                        Traditional Chinese (BIG5) 
> X Windows Platform minimum required Fonts Package
> system      SUNWGlib                         GLIB - Library of useful 
> routines for C programming
><SNIP>
> pkginfo: ERROR: pkginfo file is corrupt or missing
>
> I'm not going to lose sleep over this. I'll just reinstall Solaris. 
> There was nothing of value on the machine. I only set it up quickly to 
> test if a bit of software worked on the first release of Solaris 10.
>

What I think is happening is that when the machine was installed it did not 
have the framebuffer support packages installed at that time.

You might want to hunt down the install media and make sure you install all
of the framebuffer support packages for your framebuffer.

wschaub@steubentech.com wrote:
> On 2009-09-12, Dave <foo@coo.com> wrote:
>> Richard B. Gilbert wrote:
>>> # 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
>>>
>>> #
>>
>> # fbconfig -prconf
>> fbconfig: Not a configurable device.  Use -list for valid devices.
>>
>>
>> I recall later, it is a Creator3D in this thing.
>>
>> According to the document you pointed me to (Solaris Handbook for Sun 
>> Frame Buffers)
>>
>> http://dlc.sun.com/pdf/806-6054-10/806-6054-10.pdf
>>
>> there should be a command
>>
>> # ffbconfig
>>
>> for the Creator3D, but I don't have such a command. I tried to check if 
>> the software for the framebuffer was included, but I seem to get a 
>> problem doing that too:
>>
>> # pkginfo
>> system      SUNW1251f                        Russian 1251 fonts
>> system      SUNW1394                         Sun IEEE1394 Framework
>> system      SUNW1394h                        Sun IEEE1394 Framework 
>> Header FilesALE         SUNW5ttf                         Traditional 
>> Chinese (BIG5) True Type Fonts Package
>> ALE         SUNW5xmft                        Traditional Chinese (BIG5) 
>> X Windows Platform minimum required Fonts Package
>> system      SUNWGlib                         GLIB - Library of useful 
>> routines for C programming
>> <SNIP>
>> pkginfo: ERROR: pkginfo file is corrupt or missing
>>
>> I'm not going to lose sleep over this. I'll just reinstall Solaris. 
>> There was nothing of value on the machine. I only set it up quickly to 
>> test if a bit of software worked on the first release of Solaris 10.
>>
> 
> What I think is happening is that when the machine was installed it did not 
> have the framebuffer support packages installed at that time.
> 
> You might want to hunt down the install media and make sure you install all
> of the framebuffer support packages for your framebuffer.

It might be easier just to do a full install of Solaris.  That way you 
will have everything you need and everything you don't think you will need.

There are a FEW situations where you should only install the minimum 
that you need.  If your's is not one of them, it's far better to waste a 
little disk space and install everything.  Disk space is cheap.  Your 
time is not!