://mail.opensolaris.org/pipermail/xwin-discuss/attachments/20090428/ad2c0f2f/attachment.ksh
And (background information about) legacy sun4u doesn't matter, or what?
That's typical.
You have really fooled your previous workstation customers, who paid
up to 20K USD for a halfway properly configured Ultra 80 (until 2002),
Blade 2000 (until August 2004), or Blade 150 (until April 2006)
On 28/04/2009, at 5:45 PM, Martin Bochnig wrote:
And (background information about) legacy sun4u doesn't matter, or
what?
That's typical.
You have really fooled your previous workstation customers, who paid
up to 20K USD for a halfway properly configured Ultra 80 (until 2002),
Blade
The AMD64 libglx.so module in these packages has an incorrect library path,
so can't load on machines using the Mesa libglx (i.e. non-nvidia machines).
To fix it, run (as root or with pfexec):
elfedit -e 'dyn:runpath
...
Name: intel_drv.so.32
Type: application/octet-stream
Size: 666948 bytes
Desc: intel_drv.so.32
URL:
http://mail.opensolaris.org/pipermail/xwin-discuss/attachments/20090428/605506e3/attachment.obj
-- next part --
A non-text attachment was scrubbed...
Name: intel_drv.so.64
Edgar Merino wrote:
Hello,
a week ago I posted a message to this mailing list regarding the
same issue, but the conversation was kept private (erroneously),
that's why I'm reopening the post:
-- BEGIN ORIGINAL MESSAGE --
Today I upgraded my ram from 2gb to 4gb, to my surprise
I am sponsoring this case for John Martin and have marked it closed
approved automatic as it is a simple update of an externally controlled
interface to match the new standard version from a recognized standards
body. If anyone disagrees and wishes to have this case converted to
a fasttrack for
I'm sorry, I posted (on the forum) this was already solved, it was not a
solaris bug, but a motherboard one (updating bios fw did the trick).
Thanks anyway for the help.
Edgar Merino
John Martin escribi?:
Edgar Merino wrote:
Hello,
a week ago I posted a message to this mailing list
After a user complained today about not getting a response to his xwin-discuss
post I checked, and while it appears on
http://www.opensolaris.org/jive/forum.jspa?forumID=25 I don't remember seeing it
in e-mail and it's not in the archives at
The list to forum seems to work given the above showing up in the pipermail
archive as well as the forum. Let's see if this makes it to the list. If not,
you win today's broken jive gateway prize.
e.
--
This message posted from opensolaris.org
Deleted and reset. This should now work.
e.
--
This message posted from opensolaris.org
Elaine Ashton wrote:
Deleted and reset. This should now work.
Thanks for fixing so quickly.
--
-Alan Coopersmith- alan.coopersmith at sun.com
Sun Microsystems, Inc. - X Window System Engineering
n 04/28/09 19:18, Alan Coopersmith wrote:
I've never seen such an issue, but I always use dbx instead of gdb.
That is an option, but one gets used to a certain syntax :-) and if
you are cross developing for Linux it's nice to use the same debugger
on both platforms.
I don't have a build 103
Frank Middleton wrote:
n 04/28/09 19:18, Alan Coopersmith wrote:
I've never seen such an issue, but I always use dbx instead of gdb.
That is an option, but one gets used to a certain syntax :-)
I understand completely, which is why I use dbx, and get frustrated at
gdb, since I try to do stop
On Apr 28, 2009, at 7:33 PM, Alan Coopersmith wrote:
Elaine Ashton wrote:
Deleted and reset. This should now work.
Thanks for fixing so quickly.
We generally try to once people notice the problem. I wish there were
a way to detect it before folks notice it, but aside from screen-
Hello,
I have an issue with the X server not cleanly shutting down on either an init
0 or an init 6 or a shutdown/restart/reboot form the GUI
I can use the cde-login menu to select a command line login and it gos to my
laptops console text mode cleanly. But when I use the GUI as indicated in
Uros wrote:
Is there support for Mobility Radeon, too?
Yes, of course. Trace the support for the desktop GPU version.
What about Radeon HD4890?
This is supported properly in the xf86-video-radeonhd 1.2.5 and ati 6.12.2
drivers. OS 2009.06 uses the radeonhd 1.2.4 and ati 6.10.x driver. See Alan
There's support for whatever the Xorg community Radeon RadeonHD drivers
support - we don't change those. 2009.06 will include 6.10.0 of the
Radeon driver (xf86-video-ati) and 1.2.4 of the RadeonHD driver
(xf86-video-radeonhd).
Supported chipset lists for those can be seen at:
xf86-video-ati
I am sponsoring this case for Niveditha Rau of the X Window System
group and closing it as approved automatic as it simply tracks the
community addition of new protocol requests properties to the existing
RandR extension to the X protocol, and the corresponding API additions
to the libXrandr
19 matches
Mail list logo
