SEO

Hi all,

I've spent ages (days) trying get X to run on a Sun Ultra 10 (Creator3D)
with a Sun Monitor GDM 17E10 (UPA Graphics port), using OpenBSD 3.4, but to
no avail. I've read and tried the various configs listed on the FreeBSD
site but the machine just reboots no matter what I do. I would have thought
that there would have been a log file created but I can't find any.

I'm totally at a loss now so if any one can help id very much appreciate it.
I've included the XF86Config file and the output from dmesg as well.

FYI I also have a Sun DP17M0 Monitor I can use as well, since the Machine
also has a VGA port.

-- XF86Config --

Section "ServerLayout"
Identifier "wsfb"
Screen 0 "Screen0" 0 0
InputDevice "wsmouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection

Section "Module"
Load "type1"
Load "freetype"
Load "glx"
Load "extmod"
EndSection

Section "Files"
RgbPath "/usr/X11R6/lib/X11/rgb"
FontPath "/usr/X11R6/lib/X11/fonts/misc/"
FontPath "/usr/X11R6/lib/X11/fonts/Type1/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/"
FontPath "/usr/X11R6/lib/X11/fonts/CID/"
EndSection

Section "InputDevice"
Identifier "Keyboard0"
Driver "Keyboard"
Option "Protocol" "wskbd"
Option "Device" "/dev/wskbd0"
Option "XkbRules" "xfree86"
Option "XkbLayout" "us"
EndSection

Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "wsmouse"
Option "Device" "/dev/wsmouse"
Option "Emulate3Buttons"
EndSection

Section "Monitor"
Identifier "Monitor"
VendorName "Unknown"
ModelName "Unknown"
HorizSync 31.5 - 60
VertRefresh 50-70
EndSection

Section "Device"
Identifier "Wsdisplay0"
Driver "wsfb"
Option "device" "/dev/ttyD0"
EndSection

Section "Screen"
Identifier "Screen0"
Device "Wsdisplay0"
Monitor "Monitor"
DefaultDepth 24
SubSection "Display"
Depth 8
Modes "640x480" "800x600" "1024x768"
EndSubSection
SubSection "Display"
Depth 16
Modes "640x480" "800x600" "1024x768"
EndSubSection
SubSection "Display"
Depth 24
Modes "640x480" "800x600" "1024x768"
EndSubSection
EndSection

-- End of XF86Config --

-- dmesg output --

console is keyboard/display
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.
Copyright (c) 1995-2003 OpenBSD. All rights reserved.
http://www.OpenBSD.org

OpenBSD 3.4 (GENERIC) #85: Tue Sep 16 14:01:29 MDT 2003
deraadt@sparc64.openbsd.org:/usr/src/sys/arch/sparc64/compile/GENERIC
total memory = 268435456
avail memory = 239910912
using 1638 buffers containing 13418496 bytes of memory
bootpath: /pci@1f,0/pci@1,1/ide@3,0/disk@0,0
mainbus0 (root): Sun Ultra 5/10 UPA/PCI (UltraSPARC-IIi 440MHz)
cpu0 at mainbus0: SUNW,UltraSPARC-IIi @ 440 MHz, version 0 FPU
cpu0: physical 32K instruction (32 b/l), 16K data (32 b/l), 2048K external
(64 b/l)
psycho0 at mainbus0 addr 0xfffc4000
SUNW,sabre: impl 0, version 0: ign 7c0 bus range 0 to 2; PCI bus 0
DVMA map: c0000000 to e0000000
IOTDB: 10f66000 to 10fe6000
pci0 at psycho0
ppb0 at pci0 dev 1 function 1 "Sun Simba PCI-PCI" rev 0x13
pci1 at ppb0 bus 1
ebus0 at pci1 dev 1 function 0 "Sun PCIO Ebus2" rev 0x01
auxio0 at ebus0 addr 726000-726003, 728000-728003, 72a000-72a003,
72c000-72c003, 72f000-72f003
power at ebus0 addr 724000-724003 ipl 37 not configured
SUNW,pll at ebus0 addr 504000-504002 not configured
sab0 at ebus0 addr 400000-40007f ipl 43: rev 3.2
sabtty0 at sab0 port 0
sabtty1 at sab0 port 1
comkbd0 at ebus0 addr 3083f8-3083ff ipl 41: layout 46
wskbd0 at comkbd0: console keyboard
com0 at ebus0 addr 3062f8-3062ff ipl 42, mouse: ns16550a, 16 byte fifo
lpt0 at ebus0 addr 3043bc-3043cb, 30015c-30015d, 700000-70000f ipl 34:
polled
fdthree at ebus0 addr 3023f0-3023f7, 706000-70600f, 720000-720003 ipl 39 not
configured
clock0 at ebus0 addr 0-1fff: mk48t59: hostid 80f4fd70
flashprom at ebus0 addr 0-fffff not configured
audioce0 at ebus0 addr 200000-2000ff, 702000-70200f, 704000-70400f,
722000-722003 ipl 35 ipl 36: nvaddrs 0
audio0 at audioce0
hme0 at pci1 dev 1 function 1 "Sun HME" rev 0x01: address 08:00:20:f4:fd:70
nsphy0 at hme0 phy 1: DP83840 10/100 media interface, rev. 1
hme0: using ivec 3021 for interrupt
vgafb0 at pci1 dev 2 function 0 "ATI Mach64 GP" rev 0x5c
wsdisplay0 at vgafb0
wsdisplay0: screen 0 added (std, sun emulation)
pciide0 at pci1 dev 3 function 0 "CMD Technology PCI0646" rev 0x03: DMA,
channel 0 configured to native-PCI, channel 1 configured to native-PCI
pciide0: using ivec 1820 for native-PCI interrupt
wd0 at pciide0 channel 0 drive 0: <ST39120A>
wd0: 16-sector PIO, LBA, 8693MB, 17662 cyl, 16 head, 63 sec, 17803297
sectors
wd0(pciide0:0:0): using PIO mode 4, DMA mode 2
atapiscsi0 at pciide0 channel 1 drive 0
scsibus0 at atapiscsi0: 2 targets
cd0 at scsibus0 targ 0 lun 0: <ATAPI, 44X CDROM, 3.30> SCSI0 5/cdrom
removable
cd0(pciide0:1:0): using PIO mode 4, DMA mode 2
ppb1 at pci0 dev 1 function 0 "Sun Simba PCI-PCI" rev 0x13
pci2 at ppb1 bus 2
ahc0 at pci2 dev 1 function 0 "Adaptec AHA-2940U" rev 0x00: ivec 10
ahc0: aic7880: Ultra Wide Channel A, SCSI Id=7, 16/255 SCBs
scsibus1 at ahc0: 16 targets
ahc0: target 9 synchronous at 20.0MHz, offset = 0x8
sd0 at scsibus1 targ 9 lun 0: <SEAGATE, ST19171W, 2219> SCSI2 0/direct fixed
ahc0: target 9 using tagged queuing
sd0: 8683MB, 5268 cyl, 20 head, 168 sec, 512 bytes/sec, 17783112 sec total
ahc0: target 10 synchronous at 20.0MHz, offset = 0x8
sd1 at scsibus1 targ 10 lun 0: <SEAGATE, ST19171W, 2219> SCSI2 0/direct
fixed
ahc0: target 10 using tagged queuing
sd1: 8683MB, 5268 cyl, 20 head, 168 sec, 512 bytes/sec, 17783112 sec total
ahc0: target 11 synchronous at 20.0MHz, offset = 0x8
sd2 at scsibus1 targ 11 lun 0: <SEAGATE, ST19171W, 2219> SCSI2 0/direct
fixed
ahc0: target 11 using tagged queuing
sd2: 8683MB, 5268 cyl, 20 head, 168 sec, 512 bytes/sec, 17783112 sec total
ahc0: target 12 synchronous at 20.0MHz, offset = 0x8
sd3 at scsibus1 targ 12 lun 0: <SEAGATE, ST19171W, 2219> SCSI2 0/direct
fixed
ahc0: target 12 using tagged queuing
sd3: 8683MB, 5268 cyl, 20 head, 168 sec, 512 bytes/sec, 17783112 sec total
ahc0: target 13 synchronous at 20.0MHz, offset = 0x8
sd4 at scsibus1 targ 13 lun 0: <SEAGATE, ST19171W, 2219> SCSI2 0/direct
fixed
ahc0: target 13 using tagged queuing
sd4: 8683MB, 5268 cyl, 20 head, 168 sec, 512 bytes/sec, 17783112 sec total
ahc0: target 14 synchronous at 20.0MHz, offset = 0x8
sd5 at scsibus1 targ 14 lun 0: <SEAGATE, ST19171W, 2219> SCSI2 0/direct
fixed
ahc0: target 14 using tagged queuing
sd5: 8683MB, 5268 cyl, 20 head, 168 sec, 512 bytes/sec, 17783112 sec total
creator0 at mainbus0 addr 0xfebee000: Creator3D, model SUNW,501-4788, dac 10
wsdisplay1 at creator0: console (std, sun emulation), using wskbd0
pcons at mainbus0 not configured
No counter-timer -- using %tick at 440MHz as system clock.
root on wd0a
rootdev=0xc00 rrootdev=0x1a00 rawdev=0x1a02

-- End of dmesg output --


--
Thanks

William.

In article <aQzHb.203349$Y72.76396@news-lhr.blueyonder.co.uk>, William wrote:
> I've spent ages (days) trying get X to run on a Sun Ultra 10 (Creator3D)
> with a Sun Monitor GDM 17E10 (UPA Graphics port), using OpenBSD 3.4, but to
^^^^^^^

> no avail. I've read and tried the various configs listed on the FreeBSD
^^^^^^^

> site but the machine just reboots no matter what I do. I would have thought
> that there would have been a log file created but I can't find any.

Typo or just plain... well. whatever.


> Section "Monitor"
> Identifier "Monitor"
> VendorName "Unknown"
> ModelName "Unknown"
> HorizSync 31.5 - 60
> VertRefresh 50-70
> EndSection

You'll want to verify this.


> Section "Device"
> Identifier "Wsdisplay0"
> Driver "wsfb"
> Option "device" "/dev/ttyD0"
> EndSection

This looks strange to me, but I'm not familiar with OpenBSD on U10.


> Section "Screen"
> Identifier "Screen0"
> Device "Wsdisplay0"
> Monitor "Monitor"
> DefaultDepth 24
> SubSection "Display"
> Depth 8
> Modes "640x480" "800x600" "1024x768"
> EndSubSection
> SubSection "Display"
> Depth 16
> Modes "640x480" "800x600" "1024x768"
> EndSubSection
> SubSection "Display"
> Depth 24
> Modes "640x480" "800x600" "1024x768"
> EndSubSection
> EndSection

You'll want to check that your monitor _really_ supports those modes.
I would not be surprised if the lower ones were not.

[snip dmesg]

If only you'd include the XFree86 log, which should include the actual
error messages and a clue _why_ it doesn't work...


--
j p d (at) d s b (dot) t u d e l f t (dot) n l .

On Sun, 28 Dec 2003 12:16:06 +0000, William wrote:

> Section "Monitor"
> Identifier "Monitor"
> VendorName "Unknown"
> ModelName "Unknown"
> HorizSync 31.5 - 60
> VertRefresh 50-70
> EndSection

A Google search for "Sun Monitor GDM 17E10 specification"
produced this result from a website called monitormania.com:

<QUOTE>

17 INCH SONY (GDM 17E10/16E10) OEM BY SUN COLOR MONITOR 16E10

USD45.00

· 17 Inch Sony tube OEM by SUN (GDM17e10)

· .26 dpi

· HSCAN: 30-80 Khz; VSCAN: 48-160Hz

· Maximum resolution: 1600 x 1200

· This monitor is a multi-sync and is compatible with PC
and MAC (For MAC you do require an adaptor)

· Fully refurbished

· Power Supply: 100-240VAC

· User Controls: Power on/off reset brightness contrast

· Horizontal Size and centering vertical size and
centering raster rotation color.



· Please note that the horizontal size of this unit
will not go all the way so it will give you a viewable
size of 15 inch (even though the actual viewable size
is 16 inch)

</QUOTE>

I'm always suspicious of ads that claim to have "fully
refurbished" anything more complicated than a spatula
for only $45, but there were similar specs on another
site (etech4sale.com).

If they are correct, then the monitor specification in
your XF86Config file is wrong. Your monitor's horizontal
and vertical bandwidths are both considerably larger than
indicated in the spec file. Try changing them to
correspond to the monitor's specs and see if that fixes
things. Here's a sample:


Section "Monitor"
Identifier "GDM_17E10"
VendorName "Sun"
ModelName "GDM_17E10"
HorizSync 30 - 80
VertRefresh 48-160
EndSection

If you can, double check your monitor's specs in a manual
first. While it's unlikely, bad specifications in this
section can cause monitor damage, or so I'm told.

Craig Orsinger wrote:

> On Sun, 28 Dec 2003 12:16:06 +0000, William wrote:
>
>> Section "Monitor"
>> Identifier "Monitor"
>> VendorName "Unknown"
>> ModelName "Unknown"
>> HorizSync 31.5 - 60
>> VertRefresh 50-70
>> EndSection


> I'm always suspicious of ads that claim to have "fully
> refurbished" anything more complicated than a spatula
> for only $45, but there were similar specs on another
> site (etech4sale.com).
>
> If they are correct, then the monitor specification in
> your XF86Config file is wrong. Your monitor's horizontal
> and vertical bandwidths are both considerably larger than
> indicated in the spec file. Try changing them to
> correspond to the monitor's specs and see if that fixes
> things. Here's a sample:
>
>
> Section "Monitor"
> Identifier "GDM_17E10"
> VendorName "Sun"
> ModelName "GDM_17E10"
> HorizSync 30 - 80
> VertRefresh 48-160
> EndSection
>
> If you can, double check your monitor's specs in a manual
> first. While it's unlikely, bad specifications in this
> section can cause monitor damage, or so I'm told.

Thanks Craig, I'll change the config file are suggested, but what about the
rest of the file. But how do I set it up to use this Monitor and not the
UPA one that (I assume) it's currently attempting to use.

In my original post I said that I'd tried the configs as listed on the
FreeBSD site, which is in fact incorrect. What I should have said was that
I'd tried the config suggestions as listed in the /usr/X11R6/README as
suggested on the site.

The XF86Config I originally provided was based on the README for OpenBSD, so
I see no real reason (apart from my stupidity factor) as to why they won't
work.

Can anyone tell me where the log file for a crash is written to? So I can
double check that I'm looking in the right place.

--
Thanks again

William.

On Mon, 29 Dec 2003 07:27:19 +0000, William wrote:

> Thanks Craig, I'll change the config file are suggested, but what about the
> rest of the file. But how do I set it up to use this Monitor and not the
> UPA one that (I assume) it's currently attempting to use.

That would be controlled by the "Device" section, but
since I'm not familiar with XFree86 on Ultrasparcs, I can offer
no more suggestions. This link appears to explain your options:

http://www.xfree86.org/4.3.0/Status33.html

In order to make a correct configuration, you must have
the correct video driver in the "Device" section, and the correct
monitor specs in the "Monitor" section. Once you've done that, it
should work. Check around the XFree86 site for documentation on
how to set up this file. The basic procedure's the same whether
you're running Linux or one of the BSDs, as long as XFree86 is
your X server.

> In my original post I said that I'd tried the configs as listed on the
> FreeBSD site, which is in fact incorrect. What I should have said was that
> I'd tried the config suggestions as listed in the /usr/X11R6/README as
> suggested on the site.
>
> The XF86Config I originally provided was based on the README for OpenBSD, so
> I see no real reason (apart from my stupidity factor) as to why they won't
> work.
>
> Can anyone tell me where the log file for a crash is written to? So I can
> double check that I'm looking in the right place.

I believe you'll find it at /var/log/XFree86.X.log,
or some similar path, where X is your display number.
Unfortunately, I don't have an OpenBSD system at hand to
verify this, but it should be where all the syslog logs are.

Hi All,

Well I've now got X working after all the screwing around it turned
out to be a badly configured mouse. But my problems aren't over yet.

When I terminate this session I know the machine is going to go down
and reboot. When I view the log it tells me:

.... snipped
(--) Depth 24 pixmap format is 32 bpp
(EE) wsfb(0): error saving colormap Inappropriate ioctl for device
(==) wsfb(0): Backing store disabled
.... snipped
(II) XINPUT: Adding extended input device "commouse0" (type: MOUSE)
(WW) fcntl(10, F_SETOWN): Inappropriate ioctl for device

My question really is what's wrong here? And what device is it
referring to? Is it the mouse, keyboard or video? Can anyone help
point me in the right direction please.

--
Thanks

William