OpenBSD 3.8 X.org on Sun Blade 100

classic Classic list List threaded Threaded
15 messages Options
Reply | Threaded
Open this post in threaded view
|

OpenBSD 3.8 X.org on Sun Blade 100

Simon Morgan
Hi,

I have a Sun Blade 100 and have just installed OpenBSD 3.8 on it and so far I'm
very impressed. NetBSD, the supposed king of multi-platform, doesn't
even support the keyboard! This is 5 year old hardware!

Anyway, the problem I'm having is with X.org. Whenever I try and run it my
monitor spits out an "out of sync" error and the only way (AFAIK to regain a
usable console is to shutdown the machine and boot it up again. Depending
on the settings I use I'll either get a sub-error bitching about the frequencies
or about the resolution (it complains that it's "> 1280x1024", which it isn't).

I've trawled the mailing list archives and tried all the suggestions (mainly
setting reference_clock) to no avail and was hoping that somebody here who
knows more about X and/or Sun hardware could offer some insight.

I've uploaded my xorg.conf and Xorg.0.log to
http://16hz.net/~simon/SunBlade100/ in the hope that it will be of some use.
If I've neglected to mention any pertinent information then please do say
and I'll be happy to give it.

Many thanks.

Simon

Reply | Threaded
Open this post in threaded view
|

Re: OpenBSD 3.8 X.org on Sun Blade 100

Brian A. Seklecki
Wait...1280x1024 or 1600x1200 w/ 8MB of RAM?  Is that right? Onboard
video only occupies 8MB?

(II) ATI(0): Using Block 1 MMIO aperture at 0x00426000.
(II) ATI(0): MMIO write caching enabled.
(--) ATI(0): 8192 kB of SDRAM (1:1) detected (using 8191 kB).
(WW) ATI(0): Cannot shadow an accelerated frame buffer.
(II) ATI(0): Engine XCLK 115.000 MHz;  Refresh rate code 10.
(--) ATI(0): Internal programmable clock generator detected.
(--) ATI(0): Reference clock 29.500 MHz.

Try adding "DefaultDepth    24"  to your "Screen" section?

It doesn't seem to automatically be picking a modeline.

Xorg/XFree don't shine.

~BAS

On Wed, 2005-11-16 at 18:35, Simon Morgan wrote:

> Hi,
>
> I have a Sun Blade 100 and have just installed OpenBSD 3.8 on it and so far I'm
> very impressed. NetBSD, the supposed king of multi-platform, doesn't
> even support the keyboard! This is 5 year old hardware!
>
> Anyway, the problem I'm having is with X.org. Whenever I try and run it my
> monitor spits out an "out of sync" error and the only way (AFAIK to regain a
> usable console is to shutdown the machine and boot it up again. Depending
> on the settings I use I'll either get a sub-error bitching about the frequencies
> or about the resolution (it complains that it's "> 1280x1024", which it isn't).
>
> I've trawled the mailing list archives and tried all the suggestions (mainly
> setting reference_clock) to no avail and was hoping that somebody here who
> knows more about X and/or Sun hardware could offer some insight.
>
> I've uploaded my xorg.conf and Xorg.0.log to
> http://16hz.net/~simon/SunBlade100/ in the hope that it will be of some use.
> If I've neglected to mention any pertinent information then please do say
> and I'll be happy to give it.
>
> Many thanks.
>
> Simon

Reply | Threaded
Open this post in threaded view
|

Re: OpenBSD 3.8 X.org on Sun Blade 100

Simon Morgan
On 17/11/05, Brian A. Seklecki <[hidden email]> wrote:
> Wait...1280x1024 or 1600x1200 w/ 8MB of RAM?  Is that right? Onboard
> video only occupies 8MB?

1280x1024. I should have mentioned in my original post that I'm using
a Sony TFT and its maximum/optimum resolution is 1280x1024.

> (II) ATI(0): Using Block 1 MMIO aperture at 0x00426000.
> (II) ATI(0): MMIO write caching enabled.
> (--) ATI(0): 8192 kB of SDRAM (1:1) detected (using 8191 kB).
> (WW) ATI(0): Cannot shadow an accelerated frame buffer.
> (II) ATI(0): Engine XCLK 115.000 MHz;  Refresh rate code 10.
> (--) ATI(0): Internal programmable clock generator detected.
> (--) ATI(0): Reference clock 29.500 MHz.
>
> Try adding "DefaultDepth    24"  to your "Screen" section?

I added that along with Modes "1280x1024" (which I've added before at
various stages) and now, instead of an error from my monitor, I just
get a black screen. I've uploaded the latest copies of xorg.conf and
Xorg.0.log for anyone that may be interested.

Another thing I should have mentioned originally is that when I run
startx and I get an error from my monitor or the black screen or
whatever and I look at the process list from within an SSH session, X
is nowhere to be found. This would seem to indicate why Ctrl+Alt+Del
do nothing and thus the need to shutdown the machine.

Reply | Threaded
Open this post in threaded view
|

Re: OpenBSD 3.8 X.org on Sun Blade 100

Simon Morgan
In reply to this post by Brian A. Seklecki
On 17/11/05, Brian A. Seklecki <[hidden email]> wrote:
> Wait...1280x1024 or 1600x1200 w/ 8MB of RAM?  Is that right? Onboard
> video only occupies 8MB?

Sorry, yes. AFAIK the onboard video is 8MB.

Reply | Threaded
Open this post in threaded view
|

Re: OpenBSD 3.8 X.org on Sun Blade 100

Paul Heinlein
In reply to this post by Simon Morgan
On Thu, 17 Nov 2005, Simon Morgan wrote:

> I added that along with Modes "1280x1024" (which I've added before
> at various stages) and now, instead of an error from my monitor, I
> just get a black screen. I've uploaded the latest copies of
> xorg.conf and Xorg.0.log for anyone that may be interested.

I haven't used OpenBSD for some time (can't seem to get around to
unsubscribing from the list...), but I'm interested to know what
version of X.org you're using. There's an unresolved bug in 6.8.2 that
affects a number of ATI cards. I know it impacts the Radeon series,
but I'm unsure whether Rage users have reported similar symptoms. Take
a look at ticket #170008 at bugzilla.redhat.com for some background.

-- Paul Heinlein <[hidden email]>

Reply | Threaded
Open this post in threaded view
|

Re: OpenBSD 3.8 X.org on Sun Blade 100

Brian A. Seklecki
In reply to this post by Simon Morgan
I had a U5 270? 330? Mhz for a year or two; the only way to get into
1280x1024 (the max res of the monitor that it shipped with) was to drop
into 8bpp.  At 16/24 bpp, with the 8mb integrated ATI Rage 64 something
something garbag, you had to use m64config(8) and put the frambuffer in
...1152x1024?  1152x768? Something like that.  Your X.log shows those
available...try them.

I just dont see 8mb video cards making it to 1280x1024 at 24/16bpp

Also, doe the log really stop at:

(EE) xf86OpenSerial: Cannot open device /dev/mouse
  Operation not permitted.
(EE) Mouse0: cannot open input device
(EE) PreInit failed for input device "Mouse0"

...is it possible X is crashing/core'ing at this state?  Normally it will
passively fail to open the mouse device, but who knows.

Try:

-allowNonLocalModInDev allow changes to keyboard and mouse settings
-allowMouseOpenFail    start server even if the mouse can't be initialized

Also 2:

(--) Using wscons driver
_XSERVTransmkdir: ERROR: euid != 0,directory /tmp/.X11-unix will not be
created.
_XSERVTransSocketUNIXCreateListener: mkdir(/tmp/.X11-unix) failed, errno =
2
_XSERVTransMakeAllCOTSServerListeners: failed to create listener for local

Is /tmp mounted MFS or so?  Is it mode 777?

~BAS

On Thu, 17 Nov 2005, Simon Morgan wrote:

> On 17/11/05, Brian A. Seklecki <[hidden email]> wrote:
>> Wait...1280x1024 or 1600x1200 w/ 8MB of RAM?  Is that right? Onboard
>> video only occupies 8MB?
>
> Sorry, yes. AFAIK the onboard video is 8MB.
>

l8*
  -lava

x.25 - minix - bitnet - plan9 - 110 bps - ASR 33 - base8

Reply | Threaded
Open this post in threaded view
|

Re: OpenBSD 3.8 X.org on Sun Blade 100

Simon Morgan
On 17/11/05, Brian A. Seklecki <[hidden email]> wrote:
>
> I had a U5 270? 330? Mhz for a year or two; the only way to get into
> 1280x1024 (the max res of the monitor that it shipped with) was to drop
> into 8bpp.  At 16/24 bpp, with the 8mb integrated ATI Rage 64 something
> something garbag, you had to use m64config(8) and put the frambuffer in
> ...1152x1024?  1152x768? Something like that.  Your X.log shows those
> available...try them.
>
> I just dont see 8mb video cards making it to 1280x1024 at 24/16bpp

I've now managed to get a display up. Many thanks to you and everyone
else who offered advice. Unfortunately the mouse is still completely
non-functional. I don't suppose you or anybody else have any ideas?
Latest conf and log in usual place.

> Also, doe the log really stop at:
>
> (EE) xf86OpenSerial: Cannot open device /dev/mouse
>         Operation not permitted.
> (EE) Mouse0: cannot open input device
> (EE) PreInit failed for input device "Mouse0"

Yup, before I tried your allowNonLocalModInDev and allowMouseOpenFail
suggestions it would stop right at that point.

> ...is it possible X is crashing/core'ing at this state?  Normally it will
> passively fail to open the mouse device, but who knows.

I really wouldn't be suprised seeing as it left the monitor in a
messed up state and a bunch of dot files in /tmp that prevented X from
starting until you rm'd them. Once I get X fully functional I will
attempt to look into it further.

> Also 2:
>
> (--) Using wscons driver
> _XSERVTransmkdir: ERROR: euid != 0,directory /tmp/.X11-unix will not be
> created.
> _XSERVTransSocketUNIXCreateListener: mkdir(/tmp/.X11-unix) failed, errno =
> 2
> _XSERVTransMakeAllCOTSServerListeners: failed to create listener for local
>
> Is /tmp mounted MFS or so?  Is it mode 777?

$ mount | grep tmp
/dev/wd0d on /tmp type ffs (local, nodev, nosuid)
$ ls -ld /tmp/
drwxrwxrwt  2 root  wheel  512 Nov 17 14:59 /tmp/

Reply | Threaded
Open this post in threaded view
|

Re: OpenBSD 3.8 X.org on Sun Blade 100

Simon Morgan
In reply to this post by Paul Heinlein
On 17/11/05, Paul Heinlein <[hidden email]> wrote:
> I haven't used OpenBSD for some time (can't seem to get around to
> unsubscribing from the list...), but I'm interested to know what
> version of X.org you're using.

X Window System Version 6.8.2
Release Date: 9 February 2005
X Protocol Version 11, Revision 0, Release 6.8.2
Build Operating System: OpenBSD 3.8 sparc64 [ELF]
Current Operating System: OpenBSD SunBlade100.16hz.net 3.8 GENERIC#607 sparc64
Build Date: 02 September 2005

> There's an unresolved bug in 6.8.2 that affects a number of ATI cards. I
> know it impacts the Radeon series, but I'm unsure whether Rage users
> have reported similar symptoms. Take a look at ticket #170008 at
> bugzilla.redhat.com for some background.

I'm assuming that since I've got a display up that I'm unaffected by this bug.

Reply | Threaded
Open this post in threaded view
|

Re: OpenBSD 3.8 X.org on Sun Blade 100

Brian A. Seklecki
In reply to this post by Simon Morgan
On Thu, 17 Nov 2005, Simon Morgan wrote:

> On 17/11/05, Brian A. Seklecki <[hidden email]> wrote:
>>
>> I had a U5 270? 330? Mhz for a year or two; the only way to get into
>> 1280x1024 (the max res of the monitor that it shipped with) was to drop
>> into 8bpp.  At 16/24 bpp, with the 8mb integrated ATI Rage 64 something
>> something garbag, you had to use m64config(8) and put the frambuffer in
>> ...1152x1024?  1152x768? Something like that.  Your X.log shows those
>> available...try them.
>>
>> I just dont see 8mb video cards making it to 1280x1024 at 24/16bpp

Reply | Threaded
Open this post in threaded view
|

Re: OpenBSD 3.8 X.org on Sun Blade 100

Brian A. Seklecki
In reply to this post by Simon Morgan
On Thu, 17 Nov 2005, Simon Morgan wrote:

> On 17/11/05, Brian A. Seklecki <[hidden email]> wrote:
>>


>> I just dont see 8mb video cards making it to 1280x1024 at 24/16bpp
>
> I've now managed to get a display up. Many thanks to you and everyone
> else who offered advice. Unfortunately the mouse is still completely


Errr jumped the gun...was it the resolution at 1152 something...or was it
something else?

Reply | Threaded
Open this post in threaded view
|

Re: OpenBSD 3.8 X.org on Sun Blade 100

Simon Morgan
On 17/11/05, Brian A. Seklecki <[hidden email]> wrote:
> Errr jumped the gun...was it the resolution at 1152 something...or was it
> something else?

http://16hz.net/~simon/SunBlade100/xorg.conf

It's not exactly pushing my monitor to its limits but it works and
theres not much poing tweeking it until I get the mouse sorted.

Reply | Threaded
Open this post in threaded view
|

Re: OpenBSD 3.8 X.org on Sun Blade 100

Austin Murphy
On 11/17/05, Simon Morgan <[hidden email]> wrote:
> On 17/11/05, Brian A. Seklecki <[hidden email]> wrote:
> > Errr jumped the gun...was it the resolution at 1152 something...or was it
> > something else?
>
> http://16hz.net/~simon/SunBlade100/xorg.conf
>
> It's not exactly pushing my monitor to its limits but it works and
> theres not much poing tweeking it until I get the mouse sorted.

Your config says:

        HorizSync    28-80
        VertRefresh  48-75
...
        DefaultDepth 16

Just for laughs, you might want to try setting Horiz to 35-100, Vert
to 60, DefaultDepth to 8 and Modes to "1280x1024".   It *probably*
won't hurt your LCD, especially if Vert is fixed at 60.

You might also try using an older version of X, like XFree86 3.3.

Just some thoughts...

Austin

Reply | Threaded
Open this post in threaded view
|

Re: OpenBSD 3.8 X.org on Sun Blade 100

Matthieu Herrb
In reply to this post by Simon Morgan
Simon Morgan wrote:

> On 17/11/05, Brian A. Seklecki <[hidden email]> wrote:
>
>>Errr jumped the gun...was it the resolution at 1152 something...or was it
>>something else?
>
>
> http://16hz.net/~simon/SunBlade100/xorg.conf
>
> It's not exactly pushing my monitor to its limits but it works and
> theres not much poing tweeking it until I get the mouse sorted.

You did read /usr/X11R6/README, did you ? use


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

for the USB mouse on a Blade-100.
--
Matthieu Herrb

Reply | Threaded
Open this post in threaded view
|

Re: OpenBSD 3.8 X.org on Sun Blade 100

Simon Morgan
On 17/11/05, Matthieu Herrb <[hidden email]> wrote:
> You did read /usr/X11R6/README, did you ? use

Evidently not. I do remember reading about that file (I did read the
FAQ) but got a bit sidetracked and forgot about it. Sorry.

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

The mouse is working now. Thanks.

Reply | Threaded
Open this post in threaded view
|

Re: OpenBSD 3.8 X.org on Sun Blade 100

Johan Zandin
In reply to this post by Simon Morgan
On Thu, 17 Nov 2005, Simon Morgan wrote:
> http://16hz.net/~simon/SunBlade100/xorg.conf

Thanks a lot! The following line under Section "Device" also
solved my problems with the Sun GDM-20D10 monitor and Blade 100:
   Option  "reference_clock" "28.636MHz"

I had tested every modeline I could find for the GDM-20D10, and with all
kinds of sync settings, but I never got the monitor sync with the ati
driver. Using the wsfb driver instead worked fine, but then I was
limited to 8-bit graphics in 1152x900 (or something like that).
Now I can choose between lots of resolutions, and all in 24-bit.
(See the xorg.conf extract below.)

/Johan Zandin



Extract from my xorg.conf:

# Sun GDM-20D10 Monitor
Section "Monitor"
         Identifier   "Monitor"
         VendorName   "Sun"
         ModelName    "GDM-20D10"
         Option       "DPMS"
         HorizSync    40-82
         VertRefresh  50-180
         Modeline  "640x480"    50      640  648  696  832   480  481  484  509 +hsync +vsync
         Modeline  "720x540"    55      720  728  776  912   540  541  544  569 +hsync +vsync
         Modeline  "720x600"    55      720  728  776  912   600  600  603  631 +hsync +vsync
         Modeline  "800x600"    65      800  816  880 1048   600  600  603  631 +hsync +vsync
         Modeline  "1024x768"  110     1024 1056 1184 1360   768  770  774  805
         Modeline  "1152x864"  105     1152 1192 1352 1440   864  865  875  895
         Modeline  "1152x900"  110.87  1152 1224 1352 1552   900  901  904  940  Composite
         Modeline  "1280x1024" 141.82  1280 1376 1512 1744  1024 1025 1028 1070  Composite
         Modeline  "1600x1200" 162     1600 1664 1856 2160  1200 1201 1204 1250
EndSection

# ATI FrameBuffer
Section "Device"
         Identifier      "FrameBuffer"
         Driver          "ati"
         BusID           "PCI:0:19:0"
         Option          "reference_clock" "28.636MHz"
EndSection

# FrameBuffer + Monitor
Section "Screen"
         Identifier "Screen0"
         Device     "FrameBuffer"
         Monitor    "Monitor"
         DefaultDepth 24
         SubSection "Display"
                 Depth   8
                 Modes   "1600x1200" "1280x1024" "1152x900" "1152x864" "1024x768" "800x600" "720x600" "720x540" "640x480"
         EndSubSection
         SubSection "Display"
                 Depth     24
                 Modes   "1600x1200" "1280x1024" "1152x900" "1152x864" "1024x768" "800x600" "720x600" "720x540" "640x480"
         EndSubSection
EndSection