Re: [oi-dev] [HEADSUP] X server update in OpenIndiana Hipster

2015-03-06 Thread Jean-Pierre André 

Hi Ken,

ken mays via oi-dev wrote:

Jean-Pierre,

Power Mgt in BIOS
1. pfexec pkg install
system/pciutils@3.2.0,5.11-2014.0.1.0:20140528T080827Z

2. Use setpci -s "" F4.B=## (where ## is BB=light, 77=med)


Unfortunately this has no effect :

$ pfexec setpci -s 0:2.0 F4.B=AA
setpci: Cannot find any working access method.
[oindiana@openindiana oindiana]$ su
Password:
# setpci -d 8086:116 F4.B=AA
# setpci -d 8086:116 F4.B=77
# setpci -s 0:2.0 F4.B=77

I have also tried these commands before starting X.
The brightness register is probably not at F4.

On Linux (and Intel driver), it is a two-byte register
which can be accessed through :
/sys/devices/pci:00/:00:02.0/drm/card0/card0-LVDS-1/intel_backlight

Does this location give a clue ?


Usually you can get the function keys on your laptop to do this if
programmed correctly (BIOS).


Unfortunately, they do not (with any OS).

Jean-Pierre



I set up VESA using 1280x1024 and 1920x1080 so it'll work if your setup
allows it.

Thanks,
Ken



On Thursday, March 5, 2015 3:32 AM, Jean-Pierre André
 wrote:


Hi Nikola,

Nikola M wrote:
 >
 > On 03/ 3/15 04:31 PM, Jean-Pierre André wrote:
 >> Hi Ken,
 >>
 >> ken mays via oi-dev wrote:
 >>> Hello,
 >>>
 >>> The lockdown (pkg freeze) is needed mainly on the XServer and Intel
 >>> driver.
 >>> You need to maintain Intel driver's 2.6.3 or 2.9.1 for XServer 1.7.7.
 >>
 >> I assume you mean Intel driver 2.9.1 is compatible with
 >> current Xorg server 1.7.7, but where is it to be found ?
 >>
 >> The latest hipster ships with 2.99.917 (not compatible
 >> with Xorg) and older one shipped with 2.6.3 (probably
 >> not compatible with my hardware). An intermediate
 >> version compatible with both Xorg server and hardware
 >> would be nice...
 >
 > Hi Jean-Pierre,
 >
 > Could you please also state what is your hardware, brand, model,
 > configuration and grahics card/integrated graphics model (included in
 > motherboard, chipset or inside cpu).

scanpci shows :

pci bus 0x cardnum 0x02 function 0x00: vendor 0x8086 device 0x0116
   Intel Corporation 2nd Generation Core Processor Family Integrated
Graphics Controller
   CardVendor 0x103c card 0x1894 (Hewlett-Packard Company, Card unknown)

On Windows 7 the card is displayed as "Intel(R) HD Graphics 3000"

Note : https://www.illumos.org/issues/5670
(from Ken) mentions
"Intel HD Graphics: 2000-6000" to be supported by the Intel
driver not ported to OI, which gives hope for the future.

Xorg.0.log shows on Hipster (any 2014 versions) :

(II) Module intel: vendor="X.Org Foundation"
 compiled for 1.7.7, module version = 2.6.3
 Module class: X.Org Video Driver
 ABI class: X.Org Video Driver, version 6.0
(II) LoadModule: "vesa"
(II) Loading /usr/lib/xorg/modules/drivers/amd64/vesa_drv.so
(II) Module vesa: vendor="X.Org Foundation"
 compiled for 1.7.7, module version = 2.3.0
 Module class: X.Org Video Driver
 ABI class: X.Org Video Driver, version 6.0
...
(II) UnloadModule: "intel"
(II) Unloading /usr/lib/xorg/modules/drivers/amd64/intel_drv.so

So Xorg tries to use the Intel driver 2.6.3 and gives up.
The vesa driver is used instead, which is not bad (I need
no 3D). The only problem is that I cannot adjust the
brightness, and maximum brightness is unbearable, hence
my initial question.

 >
 > How it behaves in hipster-2014.1 and maybe booting from live 20141010
 > DVD/USB?

Same result (no surprise, this is the same driver
and same xorg server).

 > Idea of freezing X and intel driver is if you freeze it in a working
 > state, before one updates rest of the system to hipster-2015 for testing
 > for new bugs. (Works for me for older intel graphics, e.g. 945)

I also tested hipster 2015. The Intel driver fails
because of undefined symbol RegionEmptyData. This is
probably the signature of Xorg server being incompatible
with Intel driver 99.99.917

 > If also in hipster-2014.1 you do not have your graphics working
 > correctly (explain how it works, does it display with low
 > resolution/VESA or something) you can then try installing/booting from
 > live DVDs of older Openindiana /dev and Hipster release DVDs.

Unfortunately this computer is not old enough (about
two years and a half), and it has always fallen back
to using the vesa driver. This appears to just be
caused by an unsupported graphic model.

I have also tried to configure /etc/X11/xorg.conf to
reject the vesa driver. This has only led to having no
graphics at all.

 > If with no previous release it worked for you, see that you report a bug
 > on it, too.
 > https://www.illumos.org/projects/openindiana/issues

The conclusion will be to wait for the new Xorg
server...

Ken mentioned an Intel driver 2.9.1 which I could test
if I found it somewhere.

For now, having a way to adjust the brightness through
the vesa driver wou

Re: [oi-dev] [HEADSUP] X server update in OpenIndiana Hipster

2015-03-05 Thread ken mays via oi-dev 
Jean-Pierre,
Power Mgt in BIOS
1. pfexec pkg install system/pciutils@3.2.0,5.11-2014.0.1.0:20140528T080827Z2. 
Use setpci -s "" F4.B=## (where ## is BB=light, 77=med)
Usually you can get the function keys on your laptop to do this if programmed 
correctly (BIOS).
I set up VESA using 1280x1024 and 1920x1080 so it'll work if your setup allows 
it.
Thanks,Ken
 

 On Thursday, March 5, 2015 3:32 AM, Jean-Pierre André 
 wrote:
   

 Hi Nikola,

Nikola M wrote:
>
> On 03/ 3/15 04:31 PM, Jean-Pierre André wrote:
>> Hi Ken,
>>
>> ken mays via oi-dev wrote:
>>> Hello,
>>>
>>> The lockdown (pkg freeze) is needed mainly on the XServer and Intel
>>> driver.
>>> You need to maintain Intel driver's 2.6.3 or 2.9.1 for XServer 1.7.7.
>>
>> I assume you mean Intel driver 2.9.1 is compatible with
>> current Xorg server 1.7.7, but where is it to be found ?
>>
>> The latest hipster ships with 2.99.917 (not compatible
>> with Xorg) and older one shipped with 2.6.3 (probably
>> not compatible with my hardware). An intermediate
>> version compatible with both Xorg server and hardware
>> would be nice...
>
> Hi Jean-Pierre,
>
> Could you please also state what is your hardware, brand, model,
> configuration and grahics card/integrated graphics model (included in
> motherboard, chipset or inside cpu).

scanpci shows :

pci bus 0x cardnum 0x02 function 0x00: vendor 0x8086 device 0x0116
  Intel Corporation 2nd Generation Core Processor Family Integrated 
Graphics Controller
  CardVendor 0x103c card 0x1894 (Hewlett-Packard Company, Card unknown)

On Windows 7 the card is displayed as "Intel(R) HD Graphics 3000"

Note : https://www.illumos.org/issues/5670 (from Ken) mentions
"Intel HD Graphics: 2000-6000" to be supported by the Intel
driver not ported to OI, which gives hope for the future.

Xorg.0.log shows on Hipster (any 2014 versions) :

(II) Module intel: vendor="X.Org Foundation"
        compiled for 1.7.7, module version = 2.6.3
        Module class: X.Org Video Driver
        ABI class: X.Org Video Driver, version 6.0
(II) LoadModule: "vesa"
(II) Loading /usr/lib/xorg/modules/drivers/amd64/vesa_drv.so
(II) Module vesa: vendor="X.Org Foundation"
        compiled for 1.7.7, module version = 2.3.0
        Module class: X.Org Video Driver
        ABI class: X.Org Video Driver, version 6.0
...
(II) UnloadModule: "intel"
(II) Unloading /usr/lib/xorg/modules/drivers/amd64/intel_drv.so

So Xorg tries to use the Intel driver 2.6.3 and gives up.
The vesa driver is used instead, which is not bad (I need
no 3D). The only problem is that I cannot adjust the
brightness, and maximum brightness is unbearable, hence
my initial question.

>
> How it behaves in hipster-2014.1 and maybe booting from live 20141010
> DVD/USB?

Same result (no surprise, this is the same driver
and same xorg server).

> Idea of freezing X and intel driver is if you freeze it in a working
> state, before one updates rest of the system to hipster-2015 for testing
> for new bugs. (Works for me for older intel graphics, e.g. 945)

I also tested hipster 2015. The Intel driver fails
because of undefined symbol RegionEmptyData. This is
probably the signature of Xorg server being incompatible
with Intel driver 99.99.917

> If also in hipster-2014.1 you do not have your graphics working
> correctly (explain how it works, does it display with low
> resolution/VESA or something) you can then try installing/booting from
> live DVDs of older Openindiana /dev and Hipster release DVDs.

Unfortunately this computer is not old enough (about
two years and a half), and it has always fallen back
to using the vesa driver. This appears to just be
caused by an unsupported graphic model.

I have also tried to configure /etc/X11/xorg.conf to
reject the vesa driver. This has only led to having no
graphics at all.

> If with no previous release it worked for you, see that you report a bug
> on it, too.
> https://www.illumos.org/projects/openindiana/issues

The conclusion will be to wait for the new Xorg
server...

Ken mentioned an Intel driver 2.9.1 which I could test
if I found it somewhere.

For now, having a way to adjust the brightness through
the vesa driver would be enough.

Jean-Pierre



___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

   ___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] [HEADSUP] X server update in OpenIndiana Hipster

2015-03-05 Thread Jean-Pierre André 

Hi Nikola,

Nikola M wrote:


On 03/ 3/15 04:31 PM, Jean-Pierre André wrote:

Hi Ken,

ken mays via oi-dev wrote:

Hello,

The lockdown (pkg freeze) is needed mainly on the XServer and Intel
driver.
You need to maintain Intel driver's 2.6.3 or 2.9.1 for XServer 1.7.7.


I assume you mean Intel driver 2.9.1 is compatible with
current Xorg server 1.7.7, but where is it to be found ?

The latest hipster ships with 2.99.917 (not compatible
with Xorg) and older one shipped with 2.6.3 (probably
not compatible with my hardware). An intermediate
version compatible with both Xorg server and hardware
would be nice...


Hi Jean-Pierre,

Could you please also state what is your hardware, brand, model,
configuration and grahics card/integrated graphics model (included in
motherboard, chipset or inside cpu).


scanpci shows :

pci bus 0x cardnum 0x02 function 0x00: vendor 0x8086 device 0x0116
 Intel Corporation 2nd Generation Core Processor Family Integrated 
Graphics Controller

 CardVendor 0x103c card 0x1894 (Hewlett-Packard Company, Card unknown)

On Windows 7 the card is displayed as "Intel(R) HD Graphics 3000"

Note : https://www.illumos.org/issues/5670 (from Ken) mentions
"Intel HD Graphics: 2000-6000" to be supported by the Intel
driver not ported to OI, which gives hope for the future.

Xorg.0.log shows on Hipster (any 2014 versions) :

(II) Module intel: vendor="X.Org Foundation"
compiled for 1.7.7, module version = 2.6.3
Module class: X.Org Video Driver
ABI class: X.Org Video Driver, version 6.0
(II) LoadModule: "vesa"
(II) Loading /usr/lib/xorg/modules/drivers/amd64/vesa_drv.so
(II) Module vesa: vendor="X.Org Foundation"
compiled for 1.7.7, module version = 2.3.0
Module class: X.Org Video Driver
ABI class: X.Org Video Driver, version 6.0
...
(II) UnloadModule: "intel"
(II) Unloading /usr/lib/xorg/modules/drivers/amd64/intel_drv.so

So Xorg tries to use the Intel driver 2.6.3 and gives up.
The vesa driver is used instead, which is not bad (I need
no 3D). The only problem is that I cannot adjust the
brightness, and maximum brightness is unbearable, hence
my initial question.



How it behaves in hipster-2014.1 and maybe booting from live 20141010
DVD/USB?


Same result (no surprise, this is the same driver
and same xorg server).


Idea of freezing X and intel driver is if you freeze it in a working
state, before one updates rest of the system to hipster-2015 for testing
for new bugs. (Works for me for older intel graphics, e.g. 945)


I also tested hipster 2015. The Intel driver fails
because of undefined symbol RegionEmptyData. This is
probably the signature of Xorg server being incompatible
with Intel driver 99.99.917


If also in hipster-2014.1 you do not have your graphics working
correctly (explain how it works, does it display with low
resolution/VESA or something) you can then try installing/booting from
live DVDs of older Openindiana /dev and Hipster release DVDs.


Unfortunately this computer is not old enough (about
two years and a half), and it has always fallen back
to using the vesa driver. This appears to just be
caused by an unsupported graphic model.

I have also tried to configure /etc/X11/xorg.conf to
reject the vesa driver. This has only led to having no
graphics at all.


If with no previous release it worked for you, see that you report a bug
on it, too.
https://www.illumos.org/projects/openindiana/issues


The conclusion will be to wait for the new Xorg
server...

Ken mentioned an Intel driver 2.9.1 which I could test
if I found it somewhere.

For now, having a way to adjust the brightness through
the vesa driver would be enough.

Jean-Pierre



___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] [HEADSUP] X server update in OpenIndiana Hipster

2015-03-04 Thread Nikola M 


On 03/ 3/15 04:31 PM, Jean-Pierre André wrote:

Hi Ken,

ken mays via oi-dev wrote:

Hello,

The lockdown (pkg freeze) is needed mainly on the XServer and Intel 
driver.

You need to maintain Intel driver's 2.6.3 or 2.9.1 for XServer 1.7.7.


I assume you mean Intel driver 2.9.1 is compatible with
current Xorg server 1.7.7, but where is it to be found ?

The latest hipster ships with 2.99.917 (not compatible
with Xorg) and older one shipped with 2.6.3 (probably
not compatible with my hardware). An intermediate
version compatible with both Xorg server and hardware
would be nice...


Hi Jean-Pierre,

Could you please also state what is your hardware, brand, model, 
configuration and grahics card/integrated graphics model (included in 
motherboard, chipset or inside cpu).


How it behaves in hipster-2014.1 and maybe booting from live 20141010 
DVD/USB?


Idea of freezing X and intel driver is if you freeze it in a working 
state, before one updates rest of the system to hipster-2015 for testing 
for new bugs. (Works for me for older intel graphics, e.g. 945)


If also in hipster-2014.1 you do not have your graphics working 
correctly (explain how it works, does it display with low 
resolution/VESA or something) you can then try installing/booting from 
live DVDs of older Openindiana /dev and Hipster release DVDs.


If with no previous release it worked for you, see that you report a bug 
on it, too.

https://www.illumos.org/projects/openindiana/issues


___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] [HEADSUP] X server update in OpenIndiana Hipster

2015-03-03 Thread Jean-Pierre André 

Hi Ken,

ken mays via oi-dev wrote:

Hello,

The lockdown (pkg freeze) is needed mainly on the XServer and Intel driver.
You need to maintain Intel driver's 2.6.3 or 2.9.1 for XServer 1.7.7.


I assume you mean Intel driver 2.9.1 is compatible with
current Xorg server 1.7.7, but where is it to be found ?

The latest hipster ships with 2.99.917 (not compatible
with Xorg) and older one shipped with 2.6.3 (probably
not compatible with my hardware). An intermediate
version compatible with both Xorg server and hardware
would be nice...

Jean-Pierre



If you've updated to hipster-2014.1, you've done well enough.

Thanks,
Ken




On Monday, March 2, 2015 6:43 AM, Nikola M  wrote:



On 02/28/15 04:22 PM, Jean-Pierre André wrote:
 > Hi Alexander,
 >
 > Alexander Pyhalov wrote:
 > [...]
 >> I think we can look at downgrading
 >> intel drivers to something like 2.9 (or even 2.6) which still supported
 >> UMS until KMS work is ready. I don't know how much work it'll take to
 >> make this crap work with new Xorg server, so no promises on time frame
 >> for now. Until then you can use vesa.
 >
 > I have a computer with Intel graphics and Hipster
 > 20140701 installed. Xorg refuses to use intel_drv.so
 > and falls back on using vesa_drv.so, I understand
 > this is not going to improve soon.
 >
 > The fall back to vesa is totally unusable because the
 > brigthness is forced to maximum and hurts the eyes and
 > the slider for brightness on "Power Management" has no
 > effect.
 >
 > Is there another way to adjust the brightness level with
 > the vesa driver ?
 >
 > Jean-Pierre
Hello, Jean-Pierre,

I found a workaround that could be used, if everyone declares that newer
packages in hipster-2015
will not depend on newer X and Intel driver that is non working yet.
(and that could allow testing if it is needed when things improve.

You update to latest hipster-2014.1 or install from 20141010 ISO if it
is new install,
or in a working BE for your intel hardware,
and you enter: (with pfexec or sudo)
pfexec pkg freeze consolidation/X/X-incorporation
pfexec pkg freeze x11/server/xorg/driver/xorg-video-intel

And then add new repository (pkg set-publisher-g , -G to remove old) if
needed, and update (pkg update -v).

That way , if new packages you have installed does not depend on newer X
and intel driver that does not work, you get same packages as
hipster-2015 except X and intel driver consolidations.
And hopefully newer packages won't depend on them, until it is once
solved in illumos and you unfreeze them.



___
oi-dev mailing list
oi-dev@openindiana.org 
http://openindiana.org/mailman/listinfo/oi-dev




___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev






___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] [HEADSUP] X server update in OpenIndiana Hipster

2015-03-02 Thread ken mays via oi-dev 
Hello,
The lockdown (pkg freeze) is needed mainly on the XServer and Intel driver.You 
need to maintain Intel driver's 2.6.3 or 2.9.1 for XServer 1.7.7.
If you've updated to hipster-2014.1, you've done well enough.
Thanks,Ken

 

 On Monday, March 2, 2015 6:43 AM, Nikola M  wrote:
   

 
On 02/28/15 04:22 PM, Jean-Pierre André wrote:
> Hi Alexander,
>
> Alexander Pyhalov wrote:
> [...]
>> I think we can look at downgrading
>> intel drivers to something like 2.9 (or even 2.6) which still supported
>> UMS until KMS work is ready. I don't know how much work it'll take to
>> make this crap work with new Xorg server, so no promises on time frame
>> for now. Until then you can use vesa.
>
> I have a computer with Intel graphics and Hipster
> 20140701 installed. Xorg refuses to use intel_drv.so
> and falls back on using vesa_drv.so, I understand
> this is not going to improve soon.
>
> The fall back to vesa is totally unusable because the
> brigthness is forced to maximum and hurts the eyes and
> the slider for brightness on "Power Management" has no
> effect.
>
> Is there another way to adjust the brightness level with
> the vesa driver ?
>
> Jean-Pierre
Hello, Jean-Pierre,

I found a workaround that could be used, if everyone declares that newer 
packages in hipster-2015
will not depend on newer X and Intel driver that is non working yet. 
(and that could allow testing if it is needed when things improve.

You update to latest hipster-2014.1 or install from 20141010 ISO if it 
is new install,
or in a working BE for your intel hardware,
and you enter: (with pfexec or sudo)
pfexec pkg freeze consolidation/X/X-incorporation
pfexec pkg freeze x11/server/xorg/driver/xorg-video-intel

And then add new repository (pkg set-publisher-g , -G to remove old) if 
needed, and update (pkg update -v).

That way , if new packages you have installed does not depend on newer X 
and intel driver that does not work, you get same packages as 
hipster-2015 except X and intel driver consolidations.
And hopefully newer packages won't depend on them, until it is once 
solved in illumos and you unfreeze them.


___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

   ___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] [HEADSUP] X server update in OpenIndiana Hipster

2015-03-02 Thread Nikola M 


On 02/28/15 04:22 PM, Jean-Pierre André wrote:

Hi Alexander,

Alexander Pyhalov wrote:
[...]

I think we can look at downgrading
intel drivers to something like 2.9 (or even 2.6) which still supported
UMS until KMS work is ready. I don't know how much work it'll take to
make this crap work with new Xorg server, so no promises on time frame
for now. Until then you can use vesa.


I have a computer with Intel graphics and Hipster
20140701 installed. Xorg refuses to use intel_drv.so
and falls back on using vesa_drv.so, I understand
this is not going to improve soon.

The fall back to vesa is totally unusable because the
brigthness is forced to maximum and hurts the eyes and
the slider for brightness on "Power Management" has no
effect.

Is there another way to adjust the brightness level with
the vesa driver ?

Jean-Pierre

Hello, Jean-Pierre,

I found a workaround that could be used, if everyone declares that newer 
packages in hipster-2015
will not depend on newer X and Intel driver that is non working yet. 
(and that could allow testing if it is needed when things improve.


You update to latest hipster-2014.1 or install from 20141010 ISO if it 
is new install,

or in a working BE for your intel hardware,
and you enter: (with pfexec or sudo)
pfexec pkg freeze consolidation/X/X-incorporation
pfexec pkg freeze x11/server/xorg/driver/xorg-video-intel

And then add new repository (pkg set-publisher-g , -G to remove old) if 
needed, and update (pkg update -v).


That way , if new packages you have installed does not depend on newer X 
and intel driver that does not work, you get same packages as 
hipster-2015 except X and intel driver consolidations.
And hopefully newer packages won't depend on them, until it is once 
solved in illumos and you unfreeze them.



___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] [HEADSUP] X server update in OpenIndiana Hipster

2015-02-28 Thread Jean-Pierre André 

Hi Alexander,

Alexander Pyhalov wrote:
[...]

I think we can look at downgrading
intel drivers to something like 2.9 (or even 2.6) which still supported
UMS until KMS work is ready. I don't know how much work it'll take to
make this crap work with new Xorg server, so no promises on time frame
for now. Until then you can use vesa.


I have a computer with Intel graphics and Hipster
20140701 installed. Xorg refuses to use intel_drv.so
and falls back on using vesa_drv.so, I understand
this is not going to improve soon.

The fall back to vesa is totally unusable because the
brigthness is forced to maximum and hurts the eyes and
the slider for brightness on "Power Management" has no
effect.

Is there another way to adjust the brightness level with
the vesa driver ?

Jean-Pierre


___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] [HEADSUP] X server update in OpenIndiana Hipster

2015-02-27 Thread Nikola M 


On 02/27/15 09:06 PM, Warren Marts wrote:

quoting Nikola :
> without solution for all existing users.

That's just not always possible -- I think dropping a bunch of Intel 
chipsets that are 6-10 years old and adding support for some of the 
newest ones is a good trade off.
I think it is not, if you don't have solution for current installs. and 
not a stable distro built in meantime.

And one gets nothing if even new driver does not work yet..


An Nvidia graphics card of the same vintage, say an 8400gt, is I think 
still supported by current drivers very well. Outside of the MS 
Windows sphere, Nvidia has always been the only safe choice for 
graphics. Intel and ATI/AMD have had incomplete, generally 
buggy solutions.


If this topic goes on, it's best to consider what the appropriate 
platforms are given available or potential talent and time.
Intel was always open source and supported well. People using Nvidia 
binary drivers are not part of the story, yet many more laptops sold in 
previous 10 years have Intel grahics.


I today did 'pkg freeze' on 20141010 (latest hipster-2014.1 before 
hipster-2015)
freezing consolidation/X/X-incorporation and 
x11/server/xorg/driver/xorg-video-intel .


Then I managed to update fine to today's hipster-2015.

If not making packages inthe future that explicitly depend on newer (non 
working) Intel driver and newer X,
then it could be solution for continued testing of Hipster-2015 if 
updating from 20141010.


Alternatively, I vote for older X and intel driver to be instead inside 
hipster-2015, since they actually work.


___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] [HEADSUP] X server update in OpenIndiana Hipster

2015-02-27 Thread Warren Marts 
quoting Nikola :
> without solution for all existing users.

That's just not always possible -- I think dropping a bunch of Intel
chipsets that are 6-10 years old and adding support for some of the newest
ones is a good trade off.

An Nvidia graphics card of the same vintage, say an 8400gt, is I think
still supported by current drivers very well. Outside of the MS Windows
sphere, Nvidia has always been the only safe choice for graphics. Intel and
ATI/AMD have had incomplete, generally buggy solutions.

If this topic goes on, it's best to consider what the appropriate platforms
are given available or potential talent and time.

On Fri, Feb 27, 2015 at 3:53 AM, Jim Klimov  wrote:

> 27 февраля 2015 г. 10:21:17 CET, Jonathan Adams 
> пишет:
> >Is it impossible to "sticky" the intel driver, or is it incompatible
> >with
> >other new components?
> >
> >Jon
> >
> >On 27 February 2015 at 00:47, Nikola M  wrote:
> >
> >>
> >> On 02/24/15 11:44 AM, ken mays via oi-dev wrote:
> >>
> >>  No, we didn't. You'll see that it was all worth it. Ingenuity is
> >risky
> >> business - just own it, and embrace it.
> >> Either breathe fire or blow smoke signals - or stand still.
> >>
> >>  ~K
> >>
> >> We have large majority of already working installs with borked X.
> >> It needs ability to use existing working Intel driver in one way or
> >> another , (as I mentioned in lengthy mail) because it is currently
> >busted
> >> and we can't afford to ship busted X/Intel in any form (it ruins
> >experience
> >> for large enough of people to just drop usage and testing.. en
> >masse).
> >>
> >>
> >> ___
> >> oi-dev mailing list
> >> oi-dev@openindiana.org
> >> http://openindiana.org/mailman/listinfo/oi-dev
> >>
> >
> >
> >
> >
> >___
> >oi-dev mailing list
> >oi-dev@openindiana.org
> >http://openindiana.org/mailman/listinfo/oi-dev
>
> I think new xorg dropped support for bits that enabled old drivers to
> function. Martin took care to use (and\or backport?) a border version of
> xorg with most supported devices.
> --
> Typos courtesy of K-9 Mail on my Samsung Android
>
> ___
> oi-dev mailing list
> oi-dev@openindiana.org
> http://openindiana.org/mailman/listinfo/oi-dev
>
___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] [HEADSUP] X server update in OpenIndiana Hipster

2015-02-27 Thread Jim Klimov 
27 февраля 2015 г. 10:21:17 CET, Jonathan Adams  пишет:
>Is it impossible to "sticky" the intel driver, or is it incompatible
>with
>other new components?
>
>Jon
>
>On 27 February 2015 at 00:47, Nikola M  wrote:
>
>>
>> On 02/24/15 11:44 AM, ken mays via oi-dev wrote:
>>
>>  No, we didn't. You'll see that it was all worth it. Ingenuity is
>risky
>> business - just own it, and embrace it.
>> Either breathe fire or blow smoke signals - or stand still.
>>
>>  ~K
>>
>> We have large majority of already working installs with borked X.
>> It needs ability to use existing working Intel driver in one way or
>> another , (as I mentioned in lengthy mail) because it is currently
>busted
>> and we can't afford to ship busted X/Intel in any form (it ruins
>experience
>> for large enough of people to just drop usage and testing.. en
>masse).
>>
>>
>> ___
>> oi-dev mailing list
>> oi-dev@openindiana.org
>> http://openindiana.org/mailman/listinfo/oi-dev
>>
>
>
>
>
>___
>oi-dev mailing list
>oi-dev@openindiana.org
>http://openindiana.org/mailman/listinfo/oi-dev

I think new xorg dropped support for bits that enabled old drivers to function. 
Martin took care to use (and\or backport?) a border version of xorg with most 
supported devices.
--
Typos courtesy of K-9 Mail on my Samsung Android

___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] [HEADSUP] X server update in OpenIndiana Hipster

2015-02-27 Thread Nikola M 


On 02/27/15 11:02 AM, Jonathan Adams wrote:



On 27 February 2015 at 09:56, Nikola M > wrote:



On 02/27/15 10:21 AM, Jonathan Adams wrote:

Is it impossible to "sticky" the intel driver, or is it
incompatible with other new components?

Jon

Seems like it is just version-updated to non-working one without
consulting testing.
Or at least without solution for all existing users.


Sorry, I thought that that was what hipster was for ... I thought I 
was doing the testing ...


Jon

Atually you are right. It is for testing while using it.

It is a problem we currently as community don't patch ouselfs in enough, 
to produce also something else (suitable for wider audience testing)


It can be used also for everyday use ,while testing, yet also versioned 
changes are needed to be able to step back before changes that get 
breakage in some areas.
If having 20141010 (2014.1) BE alive, one can use that for now if 
graphics not working.

(yet udating that has stopped for now).

___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] [HEADSUP] X server update in OpenIndiana Hipster

2015-02-27 Thread Jonathan Adams 
On 27 February 2015 at 09:56, Nikola M  wrote:

>
> On 02/27/15 10:21 AM, Jonathan Adams wrote:
>
>  Is it impossible to "sticky" the intel driver, or is it incompatible
> with other new components?
>
>  Jon
>
> Seems like it is just version-updated to non-working one without
> consulting testing.
> Or at least without solution for all existing users.
>

Sorry, I thought that that was what hipster was for ... I thought I was
doing the testing ...

Jon
___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] [HEADSUP] X server update in OpenIndiana Hipster

2015-02-27 Thread Nikola M 


On 02/27/15 10:21 AM, Jonathan Adams wrote:
Is it impossible to "sticky" the intel driver, or is it incompatible 
with other new components?


Jon
Seems like it is just version-updated to non-working one without 
consulting testing.

Or at least without solution for all existing users.

Cleaning up hipster-2015 to the old one with old version, seems nicest 
solution,

with ability to add new one for testing.
Even if it start suddenly working with illumos patched with KMS, it is 
not solution for present installs and all with not newest Intel graphics.

Yet, Ken has all that in mind.


On 27 February 2015 at 00:47, Nikola M > wrote:



On 02/24/15 11:44 AM, ken mays via oi-dev wrote:

No, we didn't. You'll see that it was all worth it. Ingenuity is
risky business - just own it, and embrace it.
Either breathe fire or blow smoke signals - or stand still.

~K

We have large majority of already working installs with borked X.
It needs ability to use existing working Intel driver in one way
or another , (as I mentioned in lengthy mail) because it is
currently busted and we can't afford to ship busted X/Intel in any
form (it ruins experience for large enough of people to just drop
usage and testing.. en masse).


___
oi-dev mailing list
oi-dev@openindiana.org 
http://openindiana.org/mailman/listinfo/oi-dev




___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev


___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] [HEADSUP] X server update in OpenIndiana Hipster

2015-02-27 Thread Alexander Pyhalov 

On 02/27/2015 12:21, Jonathan Adams wrote:

Is it impossible to "sticky" the intel driver, or is it incompatible with
other new components?



Old driver is incompatible with new Xorg.

--
Best regards,
Alexander Pyhalov,
system administrator of Southern Federal University IT department

___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] [HEADSUP] X server update in OpenIndiana Hipster

2015-02-27 Thread Jonathan Adams 
Is it impossible to "sticky" the intel driver, or is it incompatible with
other new components?

Jon

On 27 February 2015 at 00:47, Nikola M  wrote:

>
> On 02/24/15 11:44 AM, ken mays via oi-dev wrote:
>
>  No, we didn't. You'll see that it was all worth it. Ingenuity is risky
> business - just own it, and embrace it.
> Either breathe fire or blow smoke signals - or stand still.
>
>  ~K
>
> We have large majority of already working installs with borked X.
> It needs ability to use existing working Intel driver in one way or
> another , (as I mentioned in lengthy mail) because it is currently busted
> and we can't afford to ship busted X/Intel in any form (it ruins experience
> for large enough of people to just drop usage and testing.. en masse).
>
>
> ___
> oi-dev mailing list
> oi-dev@openindiana.org
> http://openindiana.org/mailman/listinfo/oi-dev
>
___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] [HEADSUP] X server update in OpenIndiana Hipster

2015-02-26 Thread Nikola M 


On 02/24/15 11:44 AM, ken mays via oi-dev wrote:
No, we didn't. You'll see that it was all worth it. Ingenuity is risky 
business - just own it, and embrace it.

Either breathe fire or blow smoke signals - or stand still.

~K

We have large majority of already working installs with borked X.
It needs ability to use existing working Intel driver in one way or 
another , (as I mentioned in lengthy mail) because it is currently 
busted and we can't afford to ship busted X/Intel in any form (it ruins 
experience for large enough of people to just drop usage and testing.. 
en masse).


___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] [HEADSUP] X server update in OpenIndiana Hipster

2015-02-25 Thread Alexander Pyhalov 

On 02/25/2015 19:25, Nikola M wrote:


There are 2 issues that arise from this:
First is wither we should maintain our own patches of illumos (for KMS
and other new things needed) because it seems every other distro
maintain some of their own patches and later moves to push them
upstream. (wither it is in form of applying patches to illumos before
build)
Upstream illumos is (understandably) conservative about accepting
patches and if waiting for things to become available with upstream
illumos, it could be long time waiting.

Second, Intel drivers work on 20141010 so maybe there could be another
update path from there, leaving drivers in place and updating only rest
of the updates since then, so that testing of changes could continue.
Maybe Call it hipster-2015-intel or something else, and update both
-2015-intel and -2015 with same changes, so that testing of everything
else could continue depending on used hardware?
If that publisher could be devised, I could test it.

There could also be a third path, leaving also from 20141010 toward
updates that could make it upgradeable from /dev to it, that could
include as much updates it can (and sort of going toward to some stable
release).



If someone wants to support alternative branch (e.g. /hipster-stable or 
/hipster-obsolete), he has to

a) create build server using old ISO (and not updating any package),
create new branch at 94c63b33550c4fee818b1423a16eb5c3a775681a, rebuild 
repository and support alternative build server for this branch.

b) support this branch (at least backport security fixes from the main one)

Are there any volunteers?

As for patches for illumos-gate, we support them, but only small and 
really necessary. Even if we got KMS patch (and we don't have it), it 
should be adopted by illumos, as it's the only way to ensure that it's 
properly supported.



--
Best regards,
Alexander Pyhalov,
system administrator of Southern Federal University IT department

___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] [HEADSUP] X server update in OpenIndiana Hipster

2015-02-25 Thread Nikola M 


On 02/24/15 10:51 AM, ken mays via oi-dev wrote:
There's no source code that follows OpenSXCE releases, correct me if I 
am wrong.


---> Martin mentioned he'd provide source code to his supporters. This 
is mentioned on his distro release and was in a previous blog. Also, 
some of his work pulled from existing consolidation source models. 
Just ask him

what his current process is if you want it.
I believe then there needs to be some funding to support he's work then, 
since I remember he said,

he's supporters , should be able to support him financially.
And there were very little support as it is displayed in he's text files 
about he's distro.

Maybe also it could be thought of coming back for him to OI mailing lists.

That would not be the case IF Hipster would have "entire" package 
numbered on every update,

so that user can update to specific point in time in Hipster updates,
to debug what change break what already working function of an OS.
You always get "latest" Hipster , with no way of turning a step back 
and think if update was introducing more bugs of fixing existing ones.


With Boot Environments on top of ZFS, we using and testing OI have 
best possible solutions for testing it is just that we don't use what 
we have to the full.


---> Good points. There was work on this effort, and maybe we need to 
have better checkpoints in place.
Only question is if "entire" locks to consolidations and consolidations 
are not there,
there entire would lock to many packages then instead. (so that updating 
"entire" gives exact state of packages for it).




We'd like to support your Intel GPU-based laptop and desktop needs - 
and respect your opinions. Just that we made some hard decisions to 
get us to this point. Its nice to know faithful people users are using 
the OI distro for this long, so we'll work on resolving some of issues 
mentioned...
Thanks, I appreciate this words from you //, different needs could be 
met under the same roof, if human resources we all posses are used in 
the right direction.


___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] [HEADSUP] X server update in OpenIndiana Hipster

2015-02-25 Thread Nikola M 


On 02/24/15 11:04 AM, Alexander Pyhalov wrote:


Nikola, Ken.

This time we seriously fucked up with intel drivers. Sorry, but I 
didn't have intel video adapter and couldn't test it. Intel 2.9.1 
driver wasn't working with new Xorg, so I updated it to 2.18, which is 
what is in XstreamOS and hoped that if it worked for them, it could 
work for us. Unfortunately, it wasn't true. I understand that KMS work 
will not land to illumos-gate in the nearest time. I think we can look 
at downgrading intel drivers to something like 2.9 (or even 2.6) which 
still supported UMS until KMS work is ready. I don't know how much 
work it'll take to make this crap work with new Xorg server, so no 
promises on time frame for now. Until then you can use vesa.


There are 2 issues that arise from this:
First is wither we should maintain our own patches of illumos (for KMS 
and other new things needed) because it seems every other distro 
maintain some of their own patches and later moves to push them 
upstream. (wither it is in form of applying patches to illumos before build)
Upstream illumos is (understandably) conservative about accepting 
patches and if waiting for things to become available with upstream 
illumos, it could be long time waiting.


Second, Intel drivers work on 20141010 so maybe there could be another 
update path from there, leaving drivers in place and updating only rest 
of the updates since then, so that testing of changes could continue.
Maybe Call it hipster-2015-intel or something else, and update both 
-2015-intel and -2015 with same changes, so that testing of everything 
else could continue depending on used hardware?

If that publisher could be devised, I could test it.

There could also be a third path, leaving also from 20141010 toward 
updates that could make it upgradeable from /dev to it, that could 
include as much updates it can (and sort of going toward to some stable 
release).



___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] [HEADSUP] X server update in OpenIndiana Hipster

2015-02-24 Thread ken mays via oi-dev 
No, we didn't. You'll see that it was all worth it. Ingenuity is risky business 
- just own it, and embrace it.Either breathe fire or blow smoke signals - or 
stand still.
~K
 

 On Tuesday, February 24, 2015 2:04 AM, Alexander Pyhalov  
wrote:
   

 On 02/24/2015 12:51, ken mays via oi-dev wrote:
> Nikola,
>
>  On Tuesday, February 24, 2015 12:03 AM, Nikola M  wrote:
>
>  On 02/24/15 01:18 AM, ken mays via oi-dev wrote:
>
>    Nikolai,

Nikola, Ken.

This time we seriously fucked up with intel drivers. Sorry, but I didn't 
have intel video adapter and couldn't test it. Intel 2.9.1 driver wasn't 
working with new Xorg, so I updated it to 2.18, which is what is in 
XstreamOS and hoped that if it worked for them, it could work for us. 
Unfortunately, it wasn't true. I understand that KMS work will not land 
to illumos-gate in the nearest time. I think we can look at downgrading 
intel drivers to something like 2.9 (or even 2.6) which still supported 
UMS until KMS work is ready. I don't know how much work it'll take to 
make this crap work with new Xorg server, so no promises on time frame 
for now. Until then you can use vesa.
-- 
Best regards,
Alexander Pyhalov,
system administrator of Southern Federal University IT department

___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev


   ___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] [HEADSUP] X server update in OpenIndiana Hipster

2015-02-24 Thread Alexander Pyhalov 

On 02/24/2015 12:51, ken mays via oi-dev wrote:

Nikola,

  On Tuesday, February 24, 2015 12:03 AM, Nikola M  wrote:

  On 02/24/15 01:18 AM, ken mays via oi-dev wrote:

   Nikolai,


Nikola, Ken.

This time we seriously fucked up with intel drivers. Sorry, but I didn't 
have intel video adapter and couldn't test it. Intel 2.9.1 driver wasn't 
working with new Xorg, so I updated it to 2.18, which is what is in 
XstreamOS and hoped that if it worked for them, it could work for us. 
Unfortunately, it wasn't true. I understand that KMS work will not land 
to illumos-gate in the nearest time. I think we can look at downgrading 
intel drivers to something like 2.9 (or even 2.6) which still supported 
UMS until KMS work is ready. I don't know how much work it'll take to 
make this crap work with new Xorg server, so no promises on time frame 
for now. Until then you can use vesa.

--
Best regards,
Alexander Pyhalov,
system administrator of Southern Federal University IT department

___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] [HEADSUP] X server update in OpenIndiana Hipster

2015-02-24 Thread ken mays via oi-dev 
Nikola,

 On Tuesday, February 24, 2015 12:03 AM, Nikola M  wrote:
  
 On 02/24/15 01:18 AM, ken mays via oi-dev wrote:
  
  Nikolai, 
   
 Hi, my name is Nikola (without 'i') ;)
 
  As far as Intel DRM work for illumos, that is proposed for GSoC 2015 
development which ends Q4 2015.  
 It is great to know. 
 It is then unknown what people with Intel graphics will do with their 
hardware, that want to install on and test Hipster in meantime?
 Also removing support for older graphics is never discussed anywhere as I know 
(we were just hit by update and people started reporting disastrous effects to 
their desktops). It is just done without asking.
 Maybe reconsider of leaving supported Xorg and drivers in their place or with 
an old/new name so it could be auto recognized and used?
 
  
 > They can use previous releases. There are many times when a new OS 
release drops support for previous hardware (or software) - without much 
forewarning to existing customers. But, we actually did mention it and it is 
mentioned if you follow the X release notes (and previous implementations and 
updates of Solaris X implementations and blogs/news/articles). There was a five 
year history to this discussion of moving to a newer X infrastructure for OI. 
You can only boil an egg so long before it cracks...

 As far as Martin, there is Martin's OpenSXCE distro. He currently mentioned a 
new release.  
 
 There's no source code that follows OpenSXCE releases, correct me if I am 
wrong.
 
---> Martin mentioned he'd provide source code to his supporters. This is 
mentioned on his distro release and was in a previous blog. Also, some of his 
work pulled from existing consolidation source models. Just ask him what his 
current process is if you want it.
 
  Also, there is Tribblix. Both distros are desktop-centric and support older 
Intel GPU chipsets (but not the newer ones). There is still the 
Hipster-20141010 ISO release you use today. 
   
 
 So you suggest moving from OI Hipster to other distro if wanting to continue 
using existing hardware?
 
---> No, we'd like for you to stay. But, I do mention similar alternatives that 
may meet your needs today or use of the officially provided OI 'releases'. 
 It is funny to call Hipster ISOs - releases, because it could be said that 
then publishers that are installed with them could receive updates and support?
 Which I am not sure it right, because actual reason ISOs and freezes of 
Hipster exist is because Hipster re-build all packages all the time and because 
updating takes longer and longer, there is need for starting from blank history 
of updates, so that installing packages dont' consume so much RAM and takes so 
long, not tend to give support?
 Also ISOs are there in Hipster to be able to install it on bare metal/hardware 
, because updating from /dev to Hipster last time worked almost 2 years ago and 
no one actually care to have release that could update from /dev.
 
---> There is no official release yet. The lead release manager usually tests 
migration to the latest ISO release and backward compatibility. But that is due 
to workload and volunteer resources available to handle that. 
  
  As far as Hipster, there are the supported ISO releases. The Hipster-2015 IPS 
repo is a moving target (considered 'dev', bleeding edge, or 'hair on fire' 
development) not for general production or day-to-day operations. There are 
other snapshots that may produce 'tested' package releases - which is really 
what you are discussing. True development releases are never for the general 
public (aka users) - if untested by 'QA'.  
 
 We need then something that actually IS for end users as a product of an 
effort.
 Hipster is not that kind of product, and yes, there is need for tested product.
 
 As I used Hipster for exactly everyday work for a long time (and reported all 
bugs I could on IRC and lists) , I must confess I have seen accumulation of 
bugs without fixing.
 Is it better "updating everything and not caring for introduced bugs" or "have 
working  AND development releases separate from each other", with clear intent 
that updates work - is maybe better solution?
 
 
  
  If you are tracking new releases from Hipster Dev which happens to plunge 
your desktop environment into a dark abyss, remember the rule: Either press the 
panic button or don't do it!!!  
 That would not be the case IF Hipster would have "entire" package numbered on 
every update,
 so that user can update to specific point in time in Hipster updates, 
 to debug what change break what already working function of an OS.
 You always get "latest" Hipster , with no way of turning a step back and think 
if update was introducing more bugs of fixing existing ones.
 
With Boot Environments on top of ZFS, we using and testing OI have best 
possible solutions for testing it is just that we don't use what we have to the 
full.

 ---> Good points. There was work on this effort, and maybe we need to have 
better ch

Re: [oi-dev] [HEADSUP] X server update in OpenIndiana Hipster

2015-02-24 Thread Nikola M 


On 02/24/15 01:18 AM, ken mays via oi-dev wrote:

Nikolai,


Hi, my name is Nikola (without 'i') ;)
As far as Intel DRM work for illumos, that is proposed for GSoC 2015 
development which ends Q4 2015.

It is great to know.
It is then unknown what people with Intel graphics will do with their 
hardware, that want to install on and test Hipster in meantime?
Also removing support for older graphics is never discussed anywhere as 
I know (we were just hit by update and people started reporting 
disastrous effects to their desktops). It is just done without asking.
Maybe reconsider of leaving supported Xorg and drivers in their place or 
with an old/new name so it could be auto recognized and used?


As far as Martin, there is Martin's OpenSXCE distro. He currently 
mentioned a new release.


There's no source code that follows OpenSXCE releases, correct me if I 
am wrong.


Also, there is Tribblix. Both distros are desktop-centric and support 
older Intel GPU chipsets (but not the newer ones). There is still the 
Hipster-20141010 ISO release you use today.


So you suggest moving from OI Hipster to other distro if wanting to 
continue using existing hardware?


It is funny to call Hipster ISOs - releases, because it could be said 
that then publishers that are installed with them could receive updates 
and support?
Which I am not sure it right, because actual reason ISOs and freezes of 
Hipster exist is because Hipster re-build all packages all the time and 
because updating takes longer and longer, there is need for starting 
from blank history of updates, so that installing packages dont' consume 
so much RAM and takes so long, not tend to give support?
Also ISOs are there in Hipster to be able to install it on bare 
metal/hardware , because updating from /dev to Hipster last time worked 
almost 2 years ago and no one actually care to have release that could 
update from /dev.




As far as Hipster, there are the supported ISO releases. The 
Hipster-2015 IPS repo is a moving target (considered 'dev', bleeding 
edge, or 'hair on fire' development) not for general production or 
day-to-day operations. There are other snapshots that may produce 
'tested' package releases - which is really what you are discussing. 
True development releases are never for the general public (aka users) 
- if untested by 'QA'.


We need then something that actually IS for end users as a product of an 
effort.
Hipster is not that kind of product, and yes, there is need for tested 
product.


As I used Hipster for exactly everyday work for a long time (and 
reported all bugs I could on IRC and lists) , I must confess I have seen 
accumulation of bugs without fixing.
Is it better "updating everything and not caring for introduced bugs" or 
"have working  AND development releases separate from each other", with 
clear intent that updates work - is maybe better solution?




If you are tracking new releases from Hipster Dev which happens to 
plunge your desktop environment into a dark abyss, remember the rule: 
Either press the panic button or don't do it!!!
That would not be the case IF Hipster would have "entire" package 
numbered on every update,

so that user can update to specific point in time in Hipster updates,
to debug what change break what already working function of an OS.
You always get "latest" Hipster , with no way of turning a step back and 
think if update was introducing more bugs of fixing existing ones.


With Boot Environments on top of ZFS, we using and testing OI have best 
possible solutions for testing it is just that we don't use what we have 
to the full.


The drop of support for the older Intel driver is by design of the 
newer X infrastructure - not us. We are moving to the newer Xorg Intel 
driver(s) and when Intel DRM for illumos is in place - we will strike 
the iron while hot...

So as I understand, Intel support for OI Hipster will never come back,
and there is nothing to do, but to roll separate distro or use other 
distro but OI Hipster so that graphics could continue to work? (Or wait 
for 2 years for illumos DRM to land...)


I think it is _much_ more important for OI in general to actually 
support present and existing users and hardware at a moment.
It is all great to have newer hardware support but I think that removing 
driver and Xorg support for existing widespread grahics hardware, will 
toss away new users from testing "bleading edge" development releases, 
and is disastrous to the future of OI Hipster project.


I suggest there could be solution of leaving Xorg and driver support 
where it is for existing intel graphics users. I don't see any benefit 
of tossing it away.


Thing is, I have been wrestling with Hipster for a very long time now 
and I don't see a point of it anymore.
There are no formed teams, there are  no pointed and publicly discussed 
goals for a project.


___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.or

Re: [oi-dev] [HEADSUP] X server update in OpenIndiana Hipster

2015-02-23 Thread Marcel Telka 
On Tue, Feb 24, 2015 at 12:18:14AM +, ken mays via oi-dev wrote:
> As far as Hipster, there are the supported ISO releases. The Hipster-2015 IPS
> repo is a moving target (considered 'dev', bleeding edge, or 'hair on fire'
> development) not for general production or day-to-day operations. There are
> other snapshots that may produce 'tested' package releases - which is really
> what you are discussing. True development releases are never for the general
> public (aka users) - if untested by 'QA'.
>
> If you are tracking new releases from Hipster Dev which happens to plunge
> your desktop environment into a dark abyss, remember the rule: Either press
> the panic button or don't do it!!!
>
> The drop of support for the older Intel driver is by design of the newer X
> infrastructure - not us. We are moving to the newer Xorg Intel driver(s) and
> when Intel DRM for illumos is in place - we will strike the iron while
> hot... 

http://wiki.illumos.org/display/illumos/On+the+Quality+Death+Spiral

-- 
+---+
| Marcel Telka   e-mail:   mar...@telka.sk  |
|homepage: http://telka.sk/ |
|jabber:   mar...@jabber.sk |
+---+

___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] [HEADSUP] X server update in OpenIndiana Hipster

2015-02-23 Thread ken mays via oi-dev 
Nikolai,
As far as Intel DRM work for illumos, that is proposed for GSoC 2015 
development which ends Q4 2015.
As far as Martin, there is Martin's OpenSXCE distro. He currently mentioned a 
new release.Also, there is Tribblix. Both distros are desktop-centric and 
support older Intel GPU chipsets (but not the newer ones). There is still the 
Hipster-20141010 ISO release you use today. 
As far as Hipster, there are the supported ISO releases. The Hipster-2015 IPS 
repo is a moving target (considered 'dev', bleeding edge, or 'hair on fire' 
development) not for general production or day-to-day operations. There are 
other snapshots that may produce 'tested' package releases - which is really 
what you are discussing. True development releases are never for the general 
public (aka users) - if untested by 'QA'.
If you are tracking new releases from Hipster Dev which happens to plunge your 
desktop environment into a dark abyss, remember the rule: Either press the 
panic button or don't do it!!!
The drop of support for the older Intel driver is by design of the newer X 
infrastructure - not us. We are moving to the newer Xorg Intel driver(s) and 
when Intel DRM for illumos is in place - we will strike the iron while hot... 
~ Ken 

 On Monday, February 23, 2015 10:58 AM, Nikola M  wrote:
   

 
On 02/22/15 05:56 PM, Alexander Pyhalov wrote:
> Hi.
> Unfortunately, we hit an issue, when older Intel video drivers don't 
> compile with newer Xorg and newer one require DRM update.
> Until kernel drm work is done vesa driver can be used with Intel chips.
> This sounds awful, but I don't have better sollution now.
>
> https://www.illumos.org/issues/5637

Is there any time frame for DRM update , anyone doing work on this also 
on other illumos desktop distros or we are looking at the dark here?

If issue was known prior to updates, could it be considered to have 
other (older) Xorg packages as current workaround? (And maybe 
auto-selected during update from 20141010 if problem with Intel graphics 
is already known ?)

Intel graphics could be considered as very huge user base problem for 
anyone trying to install Hipster then, I can suppose this can only turn 
more people off.
As I am not to be expected to use OI Hipster for everyday tasks on my 
hardware with current state of drivers, but could keep updating BE and 
try debugging and testing whenever asked.


___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev


   ___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] [HEADSUP] X server update in OpenIndiana Hipster

2015-02-23 Thread Nikola M 


On 02/23/15 02:27 AM, ken mays via oi-dev wrote:

xrandr | grep maximum

Hi,

$ xrandr | grep maximum
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 800 x 600, current 1024 x 768, maximum 1024 x 768


___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] [HEADSUP] X server update in OpenIndiana Hipster

2015-02-22 Thread ken mays via oi-dev 
Hello,
Try: xrandr | grep maximum
Thanks,Ken
 

 On Sunday, February 22, 2015 7:49 AM, Nikola M  wrote:
   

 On 02/15/15 05:13 AM, Alexander Pyhalov wrote:
> Hello.
> We are ready to announce Xorg update in OpenIndiana Hipster.
> X server was updated to 1.12.4, x11/server/xdmx server was added.
> Xvnc was rebuilt on the base of the new X server.
> xorg-video-intel 2.18.0

As mentioned on intel 945, resolution is locked to 1024X768, therefore 
unusable and also LCD panel brightness is not able to be set wiith GNOME 
panel addon.


___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev


___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] [HEADSUP] X server update in OpenIndiana Hipster

2015-02-22 Thread Jim Klimov 
22 февраля 2015 г. 17:56:36 CET, Alexander Pyhalov  пишет:
>Nikola M писал 22.02.2015 18:48:
>> On 02/15/15 05:13 AM, Alexander Pyhalov wrote:
>>> Hello.
>>> We are ready to announce Xorg update in OpenIndiana Hipster.
>>> X server was updated to 1.12.4, x11/server/xdmx server was added.
>>> Xvnc was rebuilt on the base of the new X server.
>>> xorg-video-intel 2.18.0
>> 
>
>Hi.
>Unfortunately, we hit an issue, when older Intel video drivers don't 
>compile with newer Xorg and newer one require DRM update.
>Until kernel drm work is done vesa driver can be used with Intel chips.
>This sounds awful, but I don't have better sollution now.
>
>https://www.illumos.org/issues/5637
>---
>System Administrator of Southern Federal University Computer Center
>
>
>
>___
>oi-dev mailing list
>oi-dev@openindiana.org
>http://openindiana.org/mailman/listinfo/oi-dev

IIRC, Martin did a big work to get the most comprehensive set of video drivers 
in OpenSXCE... maybe making friends with him to cooperate, or retracing his 
steps, is more feasible? ;)
--
Typos courtesy of K-9 Mail on my Samsung Android

___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] [HEADSUP] X server update in OpenIndiana Hipster

2015-02-22 Thread Alexander Pyhalov 

Nikola M писал 22.02.2015 18:48:

On 02/15/15 05:13 AM, Alexander Pyhalov wrote:

Hello.
We are ready to announce Xorg update in OpenIndiana Hipster.
X server was updated to 1.12.4, x11/server/xdmx server was added.
Xvnc was rebuilt on the base of the new X server.
xorg-video-intel 2.18.0




Hi.
Unfortunately, we hit an issue, when older Intel video drivers don't 
compile with newer Xorg and newer one require DRM update.

Until kernel drm work is done vesa driver can be used with Intel chips.
This sounds awful, but I don't have better sollution now.

https://www.illumos.org/issues/5637
---
System Administrator of Southern Federal University Computer Center



___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] [HEADSUP] X server update in OpenIndiana Hipster

2015-02-22 Thread Nikola M 

On 02/15/15 05:13 AM, Alexander Pyhalov wrote:

Hello.
We are ready to announce Xorg update in OpenIndiana Hipster.
X server was updated to 1.12.4, x11/server/xdmx server was added.
Xvnc was rebuilt on the base of the new X server.
xorg-video-intel 2.18.0


As mentioned on intel 945, resolution is locked to 1024X768, therefore 
unusable and also LCD panel brightness is not able to be set wiith GNOME 
panel addon.



___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] [HEADSUP] X server update in OpenIndiana Hipster

2015-02-16 Thread Aurélien Larcher 
Hi,
Systems also updated and no problem with Nividia GT218 and Nvidia Quadro FX
3800.
Thank you,

Aurelien

On Sun, Feb 15, 2015 at 11:45 AM, Andreas Wacknitz 
wrote:

>
> Am 15.02.15 05:13, schrieb Alexander Pyhalov:
>
>  Hello.
>> We are ready to announce Xorg update in OpenIndiana Hipster.
>> X server was updated to 1.12.4, x11/server/xdmx server was added.
>> Xvnc was rebuilt on the base of the new X server.
>>
>> X server device drivers were updated to the following versions:
>> xorg-input-acecad 1.5.0
>> xorg-input-hotkey 0.5.11 (later version from Oracle)
>> xorg-input-keyboard 1.8.0
>> xorg-input-mouse 1.9.1
>> xorg-input-synaptics 1.8.1
>> xorg-input-vmmouse 13.0.0
>> xorg-input-void 1.4.0
>> xorg-video-ast 1.0.1
>> xorg-video-ati 6.14.6
>> xorg-video-cirrus 1.5.2
>> xorg-video-dummy 0.3.7
>> xorg-video-intel 2.18.0
>> xorg-video-mach64 6.9.4
>> xorg-video-mga 1.6.3
>> xorg-video-nv 2.1.20
>> xorg-video-openchrome 0.3.3
>> xorg-video-r128 6.9.2
>> xorg-video-radeonhd 1.3.0
>> xorg-video-savage 2.3.7
>> xorg-video-trident 1.3.6
>> xorg-video-vesa 2.3.3
>> xorg-video-vmware 13.1.0
>>
>> The following device drivers were removed (as these devices are rather
>> old and drivers were 32-bit only):
>> xorg-video-apm
>> xorg-video-ark
>> xorg-video-chips
>> xorg-video-glint
>> xorg-video-i128
>> xorg-video-i740
>> xorg-video-neomagic
>> xorg-video-rendition
>> xorg-video-s3
>> xorg-video-s3virge
>> xorg-video-siliconmotion
>> xorg-video-sis
>> xorg-video-tdfx
>> xorg-video-tga
>> xorg-video-tseng
>>
>> X-consolidation (a meta-package, installing all X Window packages) was
>> marked obsolete as a rudiment of XNV gate.
>> To install typical desktop system you are supposed to use
>> metapackages/gui-install meta-package.
>>
>> Great thanks to Alan Coopersmith and Ken Mays, without them it would be
>> hardly possible.
>>
>> Also we are greatful to Oracle corporation for open x-s12-clone gate.
>>
>> Please update your systems and report any issues.
>>
>>  System updated and no problems so far (NVIDIA Quadro 600).
>
> Andreas
>
>
>
> ___
> oi-dev mailing list
> oi-dev@openindiana.org
> http://openindiana.org/mailman/listinfo/oi-dev
>



-- 
---
LARCHER Aurélien  | KTH, School of Computer Science and
Communication
Work: +46 (0) 8 790 71 42 | Lindstedtsvägen 5, Plan 4, 100 44 Stockholm,
SWEDEN
---
___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] [HEADSUP] X server update in OpenIndiana Hipster

2015-02-15 Thread Andreas Wacknitz 


Am 15.02.15 05:13, schrieb Alexander Pyhalov:

Hello.
We are ready to announce Xorg update in OpenIndiana Hipster.
X server was updated to 1.12.4, x11/server/xdmx server was added.
Xvnc was rebuilt on the base of the new X server.

X server device drivers were updated to the following versions:
xorg-input-acecad 1.5.0
xorg-input-hotkey 0.5.11 (later version from Oracle)
xorg-input-keyboard 1.8.0
xorg-input-mouse 1.9.1
xorg-input-synaptics 1.8.1
xorg-input-vmmouse 13.0.0
xorg-input-void 1.4.0
xorg-video-ast 1.0.1
xorg-video-ati 6.14.6
xorg-video-cirrus 1.5.2
xorg-video-dummy 0.3.7
xorg-video-intel 2.18.0
xorg-video-mach64 6.9.4
xorg-video-mga 1.6.3
xorg-video-nv 2.1.20
xorg-video-openchrome 0.3.3
xorg-video-r128 6.9.2
xorg-video-radeonhd 1.3.0
xorg-video-savage 2.3.7
xorg-video-trident 1.3.6
xorg-video-vesa 2.3.3
xorg-video-vmware 13.1.0

The following device drivers were removed (as these devices are rather 
old and drivers were 32-bit only):

xorg-video-apm
xorg-video-ark
xorg-video-chips
xorg-video-glint
xorg-video-i128
xorg-video-i740
xorg-video-neomagic
xorg-video-rendition
xorg-video-s3
xorg-video-s3virge
xorg-video-siliconmotion
xorg-video-sis
xorg-video-tdfx
xorg-video-tga
xorg-video-tseng

X-consolidation (a meta-package, installing all X Window packages) was 
marked obsolete as a rudiment of XNV gate.
To install typical desktop system you are supposed to use 
metapackages/gui-install meta-package.


Great thanks to Alan Coopersmith and Ken Mays, without them it would 
be hardly possible.


Also we are greatful to Oracle corporation for open x-s12-clone gate.

Please update your systems and report any issues.


System updated and no problems so far (NVIDIA Quadro 600).

Andreas


___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

[oi-dev] [HEADSUP] X server update in OpenIndiana Hipster

2015-02-14 Thread Alexander Pyhalov 

Hello.
We are ready to announce Xorg update in OpenIndiana Hipster.
X server was updated to 1.12.4, x11/server/xdmx server was added.
Xvnc was rebuilt on the base of the new X server.

X server device drivers were updated to the following versions:
xorg-input-acecad 1.5.0
xorg-input-hotkey 0.5.11 (later version from Oracle)
xorg-input-keyboard 1.8.0
xorg-input-mouse 1.9.1
xorg-input-synaptics 1.8.1
xorg-input-vmmouse 13.0.0
xorg-input-void 1.4.0
xorg-video-ast 1.0.1
xorg-video-ati 6.14.6
xorg-video-cirrus 1.5.2
xorg-video-dummy 0.3.7
xorg-video-intel 2.18.0
xorg-video-mach64 6.9.4
xorg-video-mga 1.6.3
xorg-video-nv 2.1.20
xorg-video-openchrome 0.3.3
xorg-video-r128 6.9.2
xorg-video-radeonhd 1.3.0
xorg-video-savage 2.3.7
xorg-video-trident 1.3.6
xorg-video-vesa 2.3.3
xorg-video-vmware 13.1.0

The following device drivers were removed (as these devices are rather 
old and drivers were 32-bit only):

xorg-video-apm
xorg-video-ark
xorg-video-chips
xorg-video-glint
xorg-video-i128
xorg-video-i740
xorg-video-neomagic
xorg-video-rendition
xorg-video-s3
xorg-video-s3virge
xorg-video-siliconmotion
xorg-video-sis
xorg-video-tdfx
xorg-video-tga
xorg-video-tseng

X-consolidation (a meta-package, installing all X Window packages) was 
marked obsolete as a rudiment of XNV gate.
To install typical desktop system you are supposed to use 
metapackages/gui-install meta-package.


Great thanks to Alan Coopersmith and Ken Mays, without them it would be 
hardly possible.


Also we are greatful to Oracle corporation for open x-s12-clone gate.

Please update your systems and report any issues.

--
System Administrator of Southern Federal University Computer Center

___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev