Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Ferrari 4000

5 views
Skip to first unread message

dac...@gmail.com

unread,
Jun 30, 2005, 3:41:04 PM6/30/05
to
Casper or whoever:

Im trying to install solaris cr b16 on my ferrari 4000 using the video
configuration modes Xorg, vesa, 1400x1050 and its not starting but I
read that you had them working in those modes. Anything special I
should be doing? Thanks.

Casper H.S. Dik

unread,
Jun 30, 2005, 3:47:44 PM6/30/05
to
dac...@gmail.com writes:

>Casper or whoever:


Well, I'm using b17; what you'll probably see is the mouse not working.

Does it work when you plug in a USB mouse?

If that's the case, add the following line to

/boot/solaris/devicedb/master

SYN1003 mouse ptr all none "Synaptics Touchpad"

This is a bug introduced by newboot; it's fixed in b17 or b18.

Casper
--
Expressed in this posting are my opinions. They are in no way related
to opinions held by my employer, Sun Microsystems.
Statements on Sun products included here are not gospel and may
be fiction rather than truth.

dac...@gmail.com

unread,
Jun 30, 2005, 3:52:06 PM6/30/05
to
Well, I'm trying to get it to work on the install which may be my
problem. I guess I should try it after the install. Thanks for the
response, I will try that
Aside from that, one error I am getting on install is devid_cache file
not found error when its about to reboot after the first cd.

Casper H.S. Dik

unread,
Jun 30, 2005, 3:53:17 PM6/30/05
to
dac...@gmail.com writes:

I think that's a known bug.

dac...@gmail.com

unread,
Jun 30, 2005, 3:55:38 PM6/30/05
to
Alright.

dac...@gmail.com

unread,
Jun 30, 2005, 5:05:28 PM6/30/05
to
What do you use for horizontal and vert or monitor settings?

S.Chang

unread,
Jun 30, 2005, 5:21:12 PM6/30/05
to
Casper H.S. Dik wrote:
> dac...@gmail.com writes:
>
>
>>Casper or whoever:
>
>
>>Im trying to install solaris cr b16 on my ferrari 4000 using the video
>>configuration modes Xorg, vesa, 1400x1050 and its not starting but I
>>read that you had them working in those modes. Anything special I
>>should be doing? Thanks.
>
>
>
> Well, I'm using b17; what you'll probably see is the mouse not working.
>
> Does it work when you plug in a USB mouse?
>
> If that's the case, add the following line to
>
> /boot/solaris/devicedb/master
>
> SYN1003 mouse ptr all none "Synaptics Touchpad"
>
> This is a bug introduced by newboot; it's fixed in b17 or b18.
>
> Casper

Any plan to get ATI to release graphics driver for Solaris x86? would be
nice if the X700 in the Ferarri 4000 can work properly with OpenGL support.

S.Chang

Casper H.S. Dik

unread,
Jun 30, 2005, 5:48:28 PM6/30/05
to
"S.Chang" <shu....@mapson.ieee.org> writes:

>Any plan to get ATI to release graphics driver for Solaris x86? would be
>nice if the X700 in the Ferarri 4000 can work properly with OpenGL support.

We can all dream.

Casper

Casper H.S. Dik

unread,
Jun 30, 2005, 5:47:39 PM6/30/05
to
dac...@gmail.com writes:

>What do you use for horizontal and vert or monitor settings?

Nothing; just using the vesa driver in 1400x1050.


BTW< I'm assuming you downloaded the ethernet driver from
www.broadcom.com?

Casper

Bruno Delbono

unread,
Jun 30, 2005, 6:06:32 PM6/30/05
to

But can Sun do something to make it come true? I'm surprised that a
company like Sun cannot get ATI to produce graphic drivers for Solaris x86.

Come on Casper! Shake someone at upper management to call ATI and yell
at them!

S.Chang

unread,
Jun 30, 2005, 6:14:17 PM6/30/05
to
I just been told by a laptop manufacturer's PM most of them will bring
out a few products with NVIDIA PCI-E graphics card, I think I will hold
back for a 64-bits laptop until then.

S.Chang

Message has been deleted

Casper H.S. Dik

unread,
Jul 1, 2005, 4:05:39 AM7/1/05
to
Tim <tbu...@dev.null> writes:

>What about XiG? Does anyone know if they're going to try and support some
>of the more popular laptops for Solaris x86?

Ask them.

>I chose my current laptop based on what they supported, and will do the
>same for my next one if there are current ones they support.

I have no choice in laptops, they just keep sending me Ferrari's :-)

With the Xorg in build 19 of S11 I am able to use the ATI driver
(non accelerated) in 1600x1050 mode, so there's some progress.

Casper

Stuart Biggar

unread,
Jul 1, 2005, 8:20:32 AM7/1/05
to
Tim wrote:

> What about XiG? Does anyone know if they're going to try and support some
> of the more popular laptops for Solaris x86?
>

> I chose my current laptop based on what they supported, and will do the
> same for my next one if there are current ones they support.
>

> tim

I asked about support for the ATI in a new IBM (Lenovo) T43p. IBM
calls it an ATI Mobility FireGL V3200/PCI Express x 16 / 128 MB GDDR1
memory. It is paired with a 15" 1600x1200 UXGA TFT. The particular
T43p I'm evaluating has a 2.13 GHz Pentium M with 2 MB of cache.

I got the following answer from Xi tech support:
--------------------
Hi Stuart,
We don't yet have support for that ATI chip. Hopefully late this Summer
or early Fall - both for Linux and Solaris.
--------------------

I'm planning on purchasing a copy of Summit Platinum when they support
the new chip. Like Tim, I've been using Summit on a notebook - mine
is just way older than what he is using.

Stuart

dac...@gmail.com

unread,
Jul 1, 2005, 9:52:44 AM7/1/05
to
nice, i can't wait.

dac...@gmail.com

unread,
Jul 1, 2005, 12:24:41 PM7/1/05
to
Casper:

This is what I'm getting when trying to start X:

(EE) VESA(0): No matching modes.
Screens found, but none have a usable configuration.

Heres parts of my xorg.conf:

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

Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
EndSection

Section "Device"
### Available Driver options are:-
### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
### <string>: "String", <freq>: "<f> Hz/kHz/MHz"
### [arg]: arg optional
#Option "ShadowFB" # [<bool>]
#Option "DefaultRefresh" # [<bool>]
Identifier "Card0"
Driver "vesa"
VendorName "ATI Technologies Inc"
BoardName "Radeon Mobility X700 (PCIE)"
BusID "PCI:1:0:0"
EndSection

Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
SubSection "Display"
Viewport 0 0
Depth 1
Modes "1400x1050"
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 4
Modes "1400x1050"
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 8
Modes "1400x1050"
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 15
Modes "1400x1050"
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 16
Modes "1400x1050"
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1400x1050"
EndSubSection

Casper H.S. Dik

unread,
Jul 1, 2005, 3:00:28 PM7/1/05
to
This one kinda works for 1400x1050 (for some reason the vesa driver
ignores all mode lines I throw at it)


Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection

Section "Files"
RgbPath "/usr/X11/lib/X11/rgb"
ModulePath "/usr/X11/lib/modules"
FontPath "/usr/X11/lib/X11/fonts/TrueType/"
FontPath "/usr/X11/lib/X11/fonts/Type1/"
FontPath "/usr/X11/lib/X11/fonts/Type1/sun/"
FontPath "/usr/X11/lib/X11/fonts/F3bitmaps/"
FontPath "/usr/X11/lib/X11/fonts/misc/"
FontPath "/usr/X11/lib/X11/fonts/100dpi/"
FontPath "/usr/X11/lib/X11/fonts/75dpi/"
EndSection

Section "Module"
Load "IA"
Load "Xst"
Load "dbe"
Load "extmod"
Load "record"
Load "xtrap"
Load "glx"
Load "bitstream"
Load "type1"
EndSection

Section "InputDevice"
Identifier "Keyboard0"
Driver "keyboard"
EndSection

Section "InputDevice"
Identifier "Mouse"
Driver "mouse"
Option "Protocol" "VUID"
Option "Device" "/dev/mouse"
Option "SendCoreEvents"
EndSection

Section "Monitor"
Identifier "Monitor0"
#DisplaySize 330 210 # mm
Modeline "1680x1050" 121.0 1680 1704 1792 1876 1050 1051 1054 1065 -hsync +vsync
EndSection

Section "Device"


Identifier "Card0"
Driver "vesa"
VendorName "ATI Technologies Inc"
BoardName "Radeon Mobility X700 (PCIE)"
BusID "PCI:1:0:0"
EndSection

Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
SubSection "Display"
Viewport 0 0
Depth 1

Modes "1680x1050" "1400x1050" "1024x768"


EndSubSection
SubSection "Display"
Viewport 0 0
Depth 4

Modes "1680x1050" "1400x1050" "1024x768"


EndSubSection
SubSection "Display"
Viewport 0 0
Depth 8

Modes "1680x1050" "1400x1050" "1024x768"


EndSubSection
SubSection "Display"
Viewport 0 0
Depth 15

Modes "1680x1050" "1400x1050" "1024x768"


EndSubSection
SubSection "Display"
Viewport 0 0
Depth 16

Modes "1680x1050" "1400x1050" "1024x768"


EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24

Modes "1680x1050" "1400x1050" "1024x768"
EndSubSection
EndSection

dac...@gmail.com

unread,
Jul 1, 2005, 5:13:04 PM7/1/05
to
Hey I tried your config and still a no go. Here's the error and my
full xorg.conf file:

(EE) VESA(0): No matching modes
(EE) Screen(s) found, but none have a usable configuration.
Fatal server error:
no screens found

xorg.conf:

Section "Monitor"
Identifier "Monitor0"
Modeline "1400x1050" 121.0 1680 1704 1792 1876 1050 1051 1054
1065 -hsync +vsync
EndSection

Section "Device"


### Available Driver options are:-
### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
### <string>: "String", <freq>: "<f> Hz/kHz/MHz"
### [arg]: arg optional
#Option "ShadowFB" # [<bool>]
#Option "DefaultRefresh" # [<bool>]

Identifier "Card0"
Driver "vesa"
VendorName "ATI Technologies Inc"
BoardName "Radeon Mobility X700 (PCIE)"
BusID "PCI:1:0:0"
EndSection

Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
SubSection "Display"
Viewport 0 0
Depth 1

Modes "1400x1050"


EndSubSection
SubSection "Display"
Viewport 0 0
Depth 4

Modes "1400x1050"


EndSubSection
SubSection "Display"
Viewport 0 0
Depth 8

Modes "1400x1050"


EndSubSection
SubSection "Display"
Viewport 0 0
Depth 15

Modes "1400x1050"


EndSubSection
SubSection "Display"
Viewport 0 0
Depth 16

Modes "1400x1050"


EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24

Modes "1400x1050"
EndSubSection
EndSection

Thanks for the help.

dac...@gmail.com

unread,
Jul 1, 2005, 5:15:04 PM7/1/05
to
wow, that really messed up the formatting.

Casper H.S. Dik

unread,
Jul 1, 2005, 5:18:15 PM7/1/05
to
dac...@gmail.com writes:

>Hey I tried your config and still a no go. Here's the error and my
>full xorg.conf file:


Which exact version did you try? You may need to specify HorizSync
and VertRefresh if it can't figure out your modem.

Casper

dac...@gmail.com

unread,
Jul 1, 2005, 5:24:26 PM7/1/05
to
I tried the one you specified above, all depths.

Do you know the valdi HorizSync and Vert? Couldnt find specs on it
anywhere.

dac...@gmail.com

unread,
Jul 1, 2005, 5:44:44 PM7/1/05
to
spcecified HorizSync 31.5 - 64.3 and VertRefresh 60-160
but no luck.

Casper H.S. Dik

unread,
Jul 2, 2005, 7:35:16 AM7/2/05
to
dac...@gmail.com writes:

>spcecified HorizSync 31.5 - 64.3 and VertRefresh 60-160
>but no luck.

The HorizSync should be more like 30-160 to catch a wide
range of monitors; and VertRefresh something like 50-75.

I would check the /var/log/Xorg.0.log file and see why
it doesn't accept several different modes.

Casper

dac...@gmail.com

unread,
Jul 2, 2005, 10:34:06 AM7/2/05
to
the only information that file gives me is the errors:

(WW) Warning, couldn't open module keyboard
(II) UnloadModule: "keyboard"
(EE) Failed to load module "keyboard" (module does not exist, 0)

and then very far down at the end of the file:

(II) VESA(0): No matching modes


(EE) Screen(s) found, but none have a usable configuration.
Fatal server error:
no screens found

dac...@gmail.com

unread,
Jul 2, 2005, 10:37:21 AM7/2/05
to
i changed keyboard to kbd and that fixed the keyboard error. no luck
on the other part.

Casper H.S. Dik

unread,
Jul 2, 2005, 10:49:14 AM7/2/05
to
dac...@gmail.com writes:

>the only information that file gives me is the errors:

>(WW) Warning, couldn't open module keyboard
>(II) UnloadModule: "keyboard"
>(EE) Failed to load module "keyboard" (module does not exist, 0)

This error can be ignored.

>and then very far down at the end of the file:

>(II) VESA(0): No matching modes

It should have listed a bunch of modes and the reasons why
it rejected them.

Casper

Casper H.S. Dik

unread,
Jul 2, 2005, 10:50:39 AM7/2/05
to
dac...@gmail.com writes:

>i changed keyboard to kbd and that fixed the keyboard error. no luck
>on the other part.

Don't change the keyboard driver; ignore the error, it always
occurs; but look for:

Not using default mode "640x350" (vrefresh out of range)


etc.

Casper

dac...@gmail.com

unread,
Jul 5, 2005, 5:53:23 PM7/5/05
to
alright. in the Xorg.0.log file it never gives any error simliar to
"Not using default mode "640x350" (vrefresh out of range)", just the
errors about no screens found.

Casper H.S. Dik

unread,
Jul 6, 2005, 3:26:41 AM7/6/05
to
dac...@gmail.com writes:

>alright. in the Xorg.0.log file it never gives any error simliar to
>"Not using default mode "640x350" (vrefresh out of range)", just the
>errors about no screens found.

Which device driver are you using? Vesa?

Have you tried configuring Vesa under Xsun?

Casper

dac...@gmail.com

unread,
Jul 6, 2005, 9:09:10 AM7/6/05
to
Yes, using VESA and ATI VESA, tried both (xorg and xsun) with a bunch
of different resolutions.

Trond Norbye

unread,
Jul 7, 2005, 5:25:17 PM7/7/05
to
dac...@gmail.com wrote:
> Yes, using VESA and ATI VESA, tried both (xorg and xsun) with a bunch
> of different resolutions.
>

Well, I just got my Ferrari 4000 and have the same problem.. Did you
manage to get it to work? or do we have to wait until build 19 arrives ;)

Trond Norbye

Alan Coopersmith

unread,
Jul 8, 2005, 2:16:34 AM7/8/05
to
Trond Norbye <trond....@gmail.com> writes in comp.unix.solaris:

The Xorg ATI driver in build 19 is basically what was in Xorg CVS a few
weeks ago, so you could download the latest CVS head or a recent
6.8.99.* snapshot and try building it yourself.

--
________________________________________________________________________
Alan Coopersmith * al...@alum.calberkeley.org * Alan.Coo...@Sun.COM
http://www.csua.berkeley.edu/~alanc/ * http://blogs.sun.com/alanc/
Working for, but definitely not speaking for, Sun Microsystems, Inc.

dac...@gmail.com

unread,
Jul 8, 2005, 12:58:44 PM7/8/05
to
I have not managed to get it to work, I guess we will need build 19.

Casper H.S. Dik

unread,
Jul 8, 2005, 2:02:40 PM7/8/05
to
dac...@gmail.com writes:

>I have not managed to get it to work, I guess we will need build 19.


I think Vesa worked for me in B17 or 18; so I am somewhat surprised it does
not work for you.

Did you add the Mouse driver line to /boot/solaris/devicedb/master as
I suggested? With that, the xorg.conf I posted should work.

Casper

dac...@gmail.com

unread,
Jul 8, 2005, 2:05:52 PM7/8/05
to
Yes I did add the line, but will double check all.

dac...@gmail.com

unread,
Jul 11, 2005, 7:39:42 PM7/11/05
to
everything is as it should be to work.

Trond Norbye

unread,
Jul 24, 2005, 8:59:18 AM7/24/05
to
Alan Coopersmith wrote:

> The Xorg ATI driver in build 19 is basically what was in Xorg CVS a few
> weeks ago, so you could download the latest CVS head or a recent
> 6.8.99.* snapshot and try building it yourself.
>

Finally the summer vacation is over, and I can get back to my computer
:D I have downloaded and compiled up the latest version from Xorg today,
and I think I have made some progress :) Now It blanks my screen, and
probably displays an unsupported video mode. In Xorg.log.0 I find
entries like:

Not using default mode "..." (hsync out of range)
Not using default mode "..." (bad mode clock/interlace/doublescan)

The problem is... what am I support to insert into my xorg.conf file ;)

Could you please post your complete xorg.conf you are using Casper?

Trond

Casper H.S. Dik

unread,
Jul 25, 2005, 6:02:25 AM7/25/05
to
Trond Norbye <trond....@gmail.com> writes:

>Finally the summer vacation is over, and I can get back to my computer
>:D I have downloaded and compiled up the latest version from Xorg today,
>and I think I have made some progress :) Now It blanks my screen, and
>probably displays an unsupported video mode. In Xorg.log.0 I find
>entries like:


This is what I use for the Monitor:

Section "Monitor"
Identifier "Monitor0"
VendorName "SEC"
ModelName "0"


Modeline "1680x1050" 121.0 1680 1704 1792 1876 1050 1051 1054 1065 -hsync +vsync
EndSection

And this for the device; (the meta modes are still experimental and they don't work well)

Absolutely necessary options:

MonitorLayout
Panelsize

Section "Device"
Option "MonitorLayout" "LVDS,CRT"

Option "MergedFB" "true"
Option "CRT2HSync" "30-100"
Option "CRT2VRefresh" "40-75"
Option "CRT2Position" "Clone"
Option "PanelSize" "1680x1050"
Option "MetaModes" "1680x1050-1280x1024 1680x1050-1024x768 1280x1024-1024x768 1280x1024-1280x1024 1024x768-1024x768"
Identifier "Card0"
Driver "ati"


VendorName "ATI Technologies Inc"
BoardName "Radeon Mobility X700 (PCIE)"
BusID "PCI:1:0:0"
EndSection

Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
SubSection "Display"
Viewport 0 0
Depth 1

Modes "1680x1050" "1400x1050" "1280x1024" "1024x768"


EndSubSection
SubSection "Display"
Viewport 0 0
Depth 4

Modes "1680x1050" "1400x1050" "1280x1024" "1024x768"


EndSubSection
SubSection "Display"
Viewport 0 0
Depth 8

Modes "1680x1050" "1400x1050" "1280x1024" "1024x768"


EndSubSection
SubSection "Display"
Viewport 0 0
Depth 15

Modes "1680x1050" "1400x1050" "1280x1024" "1024x768"


EndSubSection
SubSection "Display"
Viewport 0 0
Depth 16

Modes "1680x1050" "1400x1050" "1280x1024" "1024x768"


EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24

Modes "1680x1050" "1400x1050" "1280x1024" "1024x768"
EndSubSection
EndSection

Trond Norbye

unread,
Jul 25, 2005, 3:24:03 PM7/25/05
to
Thank you :D

Now I am able to execute Xorg by hand! Now I just have to figure out why
it failes to start during the system startup, or how I am able to get a
window manager running ;)

Trond

Casper H.S. Dik

unread,
Jul 26, 2005, 5:39:28 AM7/26/05
to
Trond Norbye <trond....@gmail.com> writes:

>Thank you :D

Make sure you install the config file as /etc/X11/xorg.conf;
also, run kdmconfig and pick "Xorg" as your X server.

For some reason, when you run Xorg w/o configuration in will default
to output over on of the other interfaces (VGA or DVI).

Perhaps the fact that the Ferrari 4000 has a flatpanel, and three
other connectors: VGA, DVI and S-Video, confuses the driver.

Trond Norbye

unread,
Jul 26, 2005, 7:59:03 AM7/26/05
to
Casper H.S. Dik wrote:
> Trond Norbye <trond....@gmail.com> writes:
>
>
>>Thank you :D
>
>
>>Now I am able to execute Xorg by hand! Now I just have to figure out why
>>it failes to start during the system startup, or how I am able to get a
>>window manager running ;)
>
>
> Make sure you install the config file as /etc/X11/xorg.conf;
> also, run kdmconfig and pick "Xorg" as your X server.
>
> For some reason, when you run Xorg w/o configuration in will default
> to output over on of the other interfaces (VGA or DVI).
>
> Perhaps the fact that the Ferrari 4000 has a flatpanel, and three
> other connectors: VGA, DVI and S-Video, confuses the driver.
>
> Casper

Now it is working for me :D

If anyone else have problems, this is what I did...

I downloaded xorg-x11-6.8.99.15.tar, and added the following lines to
config/cf/host.def:
#define ProjectRoot /opt/Xorg-6.8.99.15
#define NothingOutsideProjectRoot YES

and compiled and installed the software. Renamed /usr/X11 to
/usr/X11.solaris, and linked /usr/X11 and /usr/X11R6 to my version in
/opt/Xorg-6.8.99.15

The next I did was to modify the /etc/X11/xorg.conf to look like Casper
said, and I was able to start Xorg by issuing the command:
# /opt/Xorg-6.8.99.15/bin/Xorg

Still I was unable to get X to start by: svcadm restart dtlogin, but I
found out by using truss -f on svc.startd that it was trying to start X
by using Xserver. This file is not included in the Xorg-distribution, so
I copied the file to /opt and tried again.. but with no luck. I modified
the Xserver script to look like:

ptree $$ > /tmp/ptree
truss -rall -wall -f -o /tmp/truss -a $Xserver :$DISPLAY $ALLARGS

And I found out that dtlogin starts Xserver with the -nobanner option
that Xorg doesn't like...

Well, I copied /usr/dt/config/Xservers to /etc/dt/config/Xservers, and
removed -nobanner.. Now I have X running on my ferrari :D

Thank you _VERY_ much for your time Casper!

Trond

Jason Fiset

unread,
Aug 12, 2005, 11:04:32 AM8/12/05
to

I have been trying to compile the latest RC Xorg (6.8.99.900)
monolithic tree to no avail. I'm trying to do this to get better
support for my laptop's ATI Radeon Xpress 200M graphics chip. The
radeon driver that ships with Solaris causes a garbled login screen and
JDS (I tried to blindly login thinking maybe it was a dtlogin bug).

I'm using Sun Studio 10 for Open Solaris running on Solaris Nevada
Build 19.

Here is what my PATH variable is set to (I mention this because if
/usr/ucb is in your PATH, you can get other errors too):

bash-3.00$ echo $PATH
/usr/bin:/usr/openwin/bin:/usr/ccs/bin:/opt/SUNWspro/bin

This is what I have in xc/config/cf/host.def file:

bash-3.00$ cat config/cf/host.def
#define ProjectRoot /opt/Xorg-6.8.99.900
#define NothingOutsideProjectRoot YES


When I issue a make World, it compiles for a while but then I get this
error:

making all in lib/GL/mesa/shader/grammar...
rm -f ../../../../../lib/GL/mesa/shader/grammar/grammar_mesa.o
cc -c -xO4 -xbuiltin=%all -xlibmil -xstrconst -xpentium
-xregs=no%frameptr -Xa -v -z lazyload -z combreloc -xstrconst
-xildoff -mt -I../../../../../extras/Mesa/src/mesa/main
-I../../../../../extras/Mesa/src/mesa/math
-I../../../../../extras/Mesa/src/mesa/glapi
-I../../../../../extras/Mesa/src/mesa/shader/grammar
-I../../../../../extras/Mesa/src/mesa
-I../../../../../extras/Mesa/src/mesa/
-I../../../../../extras/Mesa/include -I../../../include
-I../../../../../exports/include/X11 -I../../../../..
-I../../../../../exports/include -Dsun -Di386 -DSVR4 -D__EXTENSIONS__
-D__i386 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DXTHREADS
-DXUSE_MTSAFE_API -DXUSE_NETDB_R_API -DMALLOC_0_RETURNS_NULL -Kpic
../../../../../lib/GL/mesa/shader/grammar/grammar_mesa.c
"grammar_mesa.c", [get_string]:ube: internal error
cc: ube failed for
../../../../../lib/GL/mesa/shader/grammar/grammar_mesa.c
*** Error code 2
make: Fatal error: Command failed for target
`../../../../../lib/GL/mesa/shader/grammar/grammar_mesa.o'
Current working directory
/export/home/jasonf/xc/lib/GL/mesa/shader/grammar

Anyone have any suggestions? This is a bit beyond my C programming
capabilities.

Thanks!

Jason

Jason Fiset

unread,
Aug 12, 2005, 12:24:30 PM8/12/05
to
I got it sorted out. I needed the Sun Performance Library installed
and some patches. It now builds cleanly.

Alan Coopersmith

unread,
Aug 12, 2005, 1:38:34 PM8/12/05
to
"Jason Fiset" <jason...@gmail.com> writes in comp.unix.solaris:

|../../../../../lib/GL/mesa/shader/grammar/grammar_mesa.c
|"grammar_mesa.c", [get_string]:ube: internal error
|cc: ube failed for
|../../../../../lib/GL/mesa/shader/grammar/grammar_mesa.c

Known bug in Studio 10 compilers:
6223325 '[get_emits]:ube: internal error' when compiling Xorg/Mesa w/ -xO4

Fixed in patch 117846-01 and later. You can get it and other relevant
Studio 10 patches at:
http://developers.sun.com/prodtech/cc/downloads/patches/ss10_patches.html

(I build Xorg CVS almost daily on Solaris 10 x86 with the Studio 10
compilers, so I usually quickly find and report (and even sometimes fix)
any bugs that pop up with compiling that combination.)

0 new messages