Re: [oi-dev] Phoronix again

2017-08-03 Thread Adam Števko
Hello Ken, testing on VMWare or in public clouds won't help you at all as they are not emulating new hardware. The 'exotic' hardware we are talking here about is supposed to be for high-performance desktop/workstation systems and was released in May i.e. nearly 3 months ago. Sure, it sucks

Re: [oi-dev] Phoronix again

2017-08-03 Thread ken mays via oi-dev
You can use the Phoronix forums in relation to the article.Also, the OI wiki provides a way to report on our own 'test analysis' on compatible OI-related hardware. Phoronix is just another independent test and review website. Anyone can report and test on what 'works for them' to challenge

Re: [oi-dev] Phoronix again

2017-07-31 Thread Aurélien Larcher
It needs 3 things - hardware, engineer and time. AFAIK right now there are > 2 companies behind illumos who have more direct relations with hardware - > Joyent and Nexenta and those companies are still most likely interested > about the server class hardware. > > Anything else is really about the

Re: [oi-dev] Phoronix again

2017-07-31 Thread Aurélien Larcher
On Mon, Jul 31, 2017 at 1:46 PM, Igor Kozhukhov wrote: > for these issues i’d like recommend prepare and use some images with DEBUG > illumos and probably boot menu with -kvd > where you can see panic and more info if beet process failed. > > just like idea. > Yes that

Re: [oi-dev] Phoronix again

2017-07-31 Thread ken mays via oi-dev
You are correct. There is a 'test text install ISO, based on illumos-4ac9cfc that works on legacy hardware like the previous snapshots versus the 2017.04 release. Alex just fixed libusb and some other issues so we may want to wait till another test ISO snapshot is released. Recent test boot

Re: [oi-dev] Phoronix again

2017-07-31 Thread Aurélien Larcher
On Mon, Jul 31, 2017 at 4:37 PM, ken mays wrote: > Ref: > > https://wiki.openindiana.org/oi/2017.04+Release+notes > > https://wiki.openindiana.org/oi/2016.10+Release+notes > > The official name varies (i.e. 2017.04) from their directory naming: > >

Re: [oi-dev] Phoronix again

2017-07-31 Thread ken mays via oi-dev
Ref: https://wiki.openindiana.org/oi/2017.04+Release+notes https://wiki.openindiana.org/oi/2016.10+Release+notes The official name varies (i.e. 2017.04) from their directory naming: http://dlc.openindiana.org/isos/hipster/20170502/ ~K On Monday, July 31, 2017, 7:08:14 AM PDT, Aurélien Larcher

Re: [oi-dev] Phoronix again

2017-07-31 Thread Aurélien Larcher
On Mon, Jul 31, 2017 at 3:57 PM, ken mays via oi-dev wrote: > Actually... > > There was a respin due on the 20170502 images to resolve a boot issue on > specific hardware that worked with the 20161030 images. > Were these images announced? I do not remember them. > >

Re: [oi-dev] Phoronix again

2017-07-31 Thread Igor Kozhukhov
for these issues i’d like recommend prepare and use some images with DEBUG illumos and probably boot menu with -kvd where you can see panic and more info if beet process failed. just like idea. and - it is hardly to say more info without access to hw, but not at all hw has remote access like

Re: [oi-dev] Phoronix again

2017-07-31 Thread Toomas Soome
> On 31. juuli 2017, at 13:41, Aurélien Larcher > wrote: > > Hi, > again Michael Larabel attempted a review and could boot on his hardware: > > http://phoronix.com/scan.php?page=news_item=OpenIndiana-7900X-Hipster >

[oi-dev] Phoronix again

2017-07-31 Thread Aurélien Larcher
Hi, again Michael Larabel attempted a review and could boot on his hardware: http://phoronix.com/scan.php?page=news_item=OpenIndiana-7900X-Hipster Obviously, instead of contacting us, he wrote directly an article to state the fact. Last time this happened I contacted him to find out what caused